PING Howto (English)

 

HOWTO — Documentation

 

The documentation is simple and straight forward. Just start with the Introduction and follow the install steps. Make sure to read the Annex, where you'll find a big FAQ section.

  1. Introduction

  2. Overview of PING features

  3. Prerequisites

  4. Configuring a PC to serve as a host for your images

  5. Downloading and burning the PING ISO

  6. Installing your own PXE Server to allow network hosts to boot PING

  7. Using PING

  8. Storing an image on a bootable ISO

  9. Annex – Exhaustive list of supported parameters + FAQ

  10. Support

  11. License

 

Introduction

The following installation steps will let you to backup and restore whole systems through your network or removable media (e.g. CDs, DVDs, and USB mass storage devices).

 

At the end of the installation, you should be able to boot any computer on a CD/DVD or your network and press the F12 key during the boot process to launch the PING software (PXE). Using this tool, you should be able either to backup, or to restore systems and partitions. Think of it as a Ghost-like process.

 

Overview of PING Features

PING is more than a Ghost™ alternative. PING is a highly-customizable cloning application, adapted to a wide range of hardware configurations, and it can also be seen as a handy toolbox for any system admin to have.

 

Here's a brief enumeration of PING's most used features…:

 

Prerequisites

Using PING on a Directly Attached Hard Drive:

 

Using PING Over a Network:

 

It's almost nothing to prepare. Yet, make sure to test your share if you make a new one, and make sure the user you plan to use to map the share has sufficient rights.

 

 

 

Configuring a PC to serve as a host for your images

SKIP this step if all you want is a locally-stored backup of your system.

 

Directory names are given here as samples. Adapt the following according to your specific needs and configuration.

  1. Open C:\ and make a new directory, called PartImage.
  2. Right-click on the C:\PartImage folder and share it. Set the permissions as suits you. Just keep in mind that you'll have to be able to write on this shared folder from any host on your network. Create a user if necessary, and… test it J

 

 

 

Downloading and Burning the PING ISO

SKIP this step if you only want to setup a PXE server.

 

 

 

 

Installing your PXE Server to allow network hosts to boot PING (Optional step)

SKIP this step if you only want a backup of your system stored locally or on removable media.

 

Directory names are given here as samples. Adapt the following according to your specific needs and configuration.

 

[OSChooser]

 

Description = "PING X.YZ (Partimage Is Not Ghost)"

 

Help = ""

 

LaunchFile = "Setup\English\Images\PING\i386\templates\pxelinux.0"

 

ImageType = Flat

 

Version="X.YZ"

 

 

DEFAULT default

 

PROMPT 1

 

TIMEOUT 26

 

DISPLAY boot.msg

 

 

LABEL default

 

KERNEL kernel

 

APPEND vga=normal devfs=nomount pxe ramdisk_size=33000 load_ramdisk=1 init=/linuxrc prompt_ramdisk=0 initrd=initrd.gz root=/dev/ram0 rw noapic nolapic lba combined_mode=libata ide0=noprobe nomce pci=nommconf pci=nomsi irqpoll quiet

 

 

LABEL dummy

 

KERNEL kernel

 


 

DEFAULT default

 

PROMPT 1

 

TIMEOUT 26

 

DISPLAY boot.msg

 

 

LABEL default

 

APPEND vga=normal devfs=nomount pxe ramdisk_size=33000 load_ramdisk=1 init=/linuxrc prompt_ramdisk=0 initrd=initrd.gz root=/dev/ram0 rw noapic nolapic lba combined_mode=libata ide0=noprobe nomce pci=nommconf pci=nomsi irqpoll quiet

 

 

LABEL dummy

 

KERNEL kernel

 

 

If you've got several network cards in your computer, you'll have to choose in the server interface area the one that communicates with your other LAN hosts.

Configure your DHCP Server here. Booting with PXE is not possible unless you define it. A common network configuration is to have addresses like 192.168.0.x with 192.168.0.1 as the router (often a workstation connected both to the internet, both to the LAN, and sharing the internet connection on the LAN).

Nothing special here.

 

 

 

In the following section, we'll be booting from a CD, made by burning the PING ISO. But this should give exactly the same result.

 

Please note that some screenshots might not be up to date, for PING is frequently improved.

 

 

Using PING

Choose to boot on the CD you've burnt with the PING ISO.

If you don't see the option in your boot sequence, you'll probably have to modify your BIOS settings.

Note that a PXE Server is needed to boot from the network.

The Linux distribution is starting.

Press ENTER to proceed.

If you don't want to use our menu-driven wizard, press x and ENTER to get a shell. The root user account has no password.

Read the warnings carefully and press ENTER to proceed.

Choose what should happen at the end of the backup or restoration process. You might want to get a shell to access the log. The command line instruction is "vi /tmp/x.log".

You can backup to and restore from a local partition or a network drive.

 

These illustrations will start with a local backup.

All available partitions should be enumerated here, with either a NTFS label or the first few directories.

 

If you want to restore an image to the workstation, select the first option.

Otherwise, select all partitions you want to backup. Be aware that you should leave at least one partition unselected, as PING won't store a partition onto itself.

An Exception: if you've got only one partition, you'll be able to select it, and the script will suggest splitting the partition into two partitions. Although this works, you may want to repartition the drive before running PING.

Now, choose where to store the image.

 

In our example, we had the C: part on /dev/hda1 and a D: part on /dev/hda5 (which Windows always stores in an extended /dev/hda2 partition). We'll store an image of C: on D:.

If you've prepared a \Partimage directory on your destination partition, enter it here.

 

In our case, we had not, and so we entered the root directory (and our first image will be stored on D:\).

 

It's a good idea to have everything stored in a dedicated directory.

Here, you'll find the list of available images. They are stored in the directory we've just chosen. Choosing one image will restore the computer with it, thus erasing all your hard disk.

 

Apart the images themselves, you'll always find 2 special choices,

obviously necessary to let you ask for an image (or blank Windows administrator password, if needed.)

In our example, we had chosen the D:\ directory, and D:\ was empty. That's why you can see a "System Volume Information" directory, present on any NTFS partition. (We should have created a D:\Partimage directory and chosen it for the example to be clearer – sorry.)

Now, let's explain what should have happened if we had chosen to store the image onto a Network Share rather than a Local Partition…

Remember where we were…

 

When choosing this option, the script will try to get an IP through DHCP. If this fails, you'll have the possibility to give manual parameters, as in next screenshots.

Give your IP address.

…and your netmask…

…and finally your gateway.

Note : the following shows accessing a SMB (Microsoft Netbios) network share. But PING has been developed and now supports also NFS, FTP (and, somewhat, SSH). Same idea.

We need to know where to save the image.

Give the IP of the computer you've shared the PartImage folder on (as explained in the prerequisites).

Now, the name of the share.

Example: \\mydomain\temp => the share is called temp.

Now, the user name on the network.

It might also be a local account (eg.: administrator).

(You'll be asked for the password afterwards, and it won't be displayed when typing it.)

All connected hard disk drives, USB mass storage devices included, will be scanned and all available partitions should be enumerated here, with either a NTFS label, or first found directories.

 

If you want to restore an image to the workstation, check the first option.

Elsewhere, choose all the partitions you want to backup. You can choose all of them.

Now, the directory path, from the share to the PartImage directory.

Example: if you created C:\PartImage on server Billy, and shared it, then your resource should be \\billy\partimage. So, IP is Billy's IP, share is partimage, and directory is nothing.

Example: if you created C:\temp\PartImage on server Billy, but shared the temp directory, then your resource should be \\billy\temp\partimage. So, IP is Billy's IP, share is temp, and the directory is \partimage.

Here, you'll find the list of available images. In the example, "T1" and "T1_Bis" are two available images. They are stored in the directory we've just chosen. Choosing one image will restore the computer with it, thus erasing part of or all your hard disk.
  • The Create_New_Image option is obviously not an image, but a choice permitting to create a new one out of the system you've booted on.
  • If you need to blank the password of your local administrator, choose Blank_Local_Admin_Passwd.
  • Note that partitionning
    can be customized through a HDD_Target.txt file. Go to the Annex for details.

We're back again to common trunk of the documentation, whether you chose to store the image onto a Network Share or onto a Local Partition.

Finally, tell the wizard what to name your new image.

In this example, PING will create a new \PartImage\System_20070624 directory on the destination drive, and store the backup in it.

That's all.

In this screenshot, BIOS settings are being saved…

Then, the partitions…

When the process is over, we get the shell we asked for.

On the directory we've stored the image into, you should get this kind of directory listing if you use the dir command in the Windows Command Prompt.

File Descriptions:

  • bios stores a copy of your bios settings, and will be restored too. If you don't want to restore or store your BIOS settings, delete this file.
  • hda stores the first sector of the first hard disk drive. The file might be called sda if SCSI or S-ATA. The Master Boot Record (MBR) should be inside.
  • hda1.000 and hda1.001 (or sda1.000 if SCSI/S-ATA) are the partimage image files of the first partition of the first hard disk drive. Delete these files if you don't want this partition to be restored.
  • hda1.first_sectors (or sda1.first_sectors if SCSI/S-ATA) stores the 20 first sectors of the first partition of the first hard disk drive. They will be restored before the partimaged image, to ensure any boot sector stored in a partition rather than in the MBR will be restored. The LVM structure of a partition (Linux-context only) is also stored here.
  • HDD_Look.txt stores the list of hard disk drives and partitions that have been found on the box you've written an image from. It's not used at this time.

 

 

Storing an image on a Bootable ISO

Storing an image on a LAN computer is nice, but sometimes, you may want to burn this image on a bootable DVD. It can be useful to bring such a media to a remote site, and regenerate a computer. It can also be considered as a practical way to backup a whole system.

Directory names are given here as samples. Adapt the following according to your specific needs and configuration.

  1. We suppose you've recorder an image within the C:\PartImage\ directory. The image is called My_Image_2008-12-25.
  2. Download initrd.gz, kernel, isolinux.bin, logo.16 and boot.msg and save these files within the C:\PartImage\My_Image_2005-12-25\ directory.
  3. Create a text file, called isolinux.cfg, within the C:\PartImage\My_Image_2005-12-25\ directory, containing (be careful that the APPEND line must not have linefeeds! It's only one line) :
DEFAULT default

 

PROMPT 1

 

TIMEOUT 26

 

DISPLAY boot.msg

 

 

LABEL default

 

KERNEL kernel

 

APPEND vga=normal devfs=nomount pxe ramdisk_size=33000 load_ramdisk=1 init=/linuxrc prompt_ramdisk=0 initrd=initrd.gz root=/dev/ram0 rw noapic nolapic lba combined_mode=libata ide0=noprobe nomce pci=nommconf pci=nomsi irqpoll quiet

 

 

LABEL dummy

 

KERNEL kernel

 
  1. Download CDR Tools 2.0.1. Install the EXE (there's an embedded MSI) on your computer.
  2. Open a DOS Prompt and go to your image directory:

  3. Use mkisofs (from CDR Tools) to generate a bootable ISO:


    mkisofs -r -b isolinux.bin -boot-info-table -no-emul-boot -boot-load-size 4 -o ../BurnMe.iso .

    /!\ Don't forget the trailing dot. If you're not familiar with DOS, remember that mkisofs.exe has to be stored somewhere in your PATH for this command to work. Why not store it in your C:\WINDOWS\SYSTEM32 directory ?

  4. The ISO generation should start…:

  5. And you should get a full working C:\PartImage\BurnMe.iso image.

  6. Burn the ISO. That's all.

Note: You might use Ahead Nero or any third-party software to generate a bootable ISO. Your mileage might vary.

 

 

Annex

Notes :

 

Special features / FAQ :

 

 

If you're bored with always having to re-type network and share settings…

 

 

1. Boot PING on a machine that has at least 256 MB of RAM

2. Get a shell when proposed to, by typing 'x' and Enter

3. Login as root, no password

4. Connect to your network:

- If there's a DHCP server, type: dhcpcd eth0

- Else, type (adjust to your config):

- ifconfig eth0 192.168.0.26 netmask 255.255.255.0 up

- route add default gw 192.168.0.1

5. Mount a remote share (where your initrd.gz file can be found):

- mount.smbfs //192.168.0.1/d\$ /mnt/smbfs –o

username=domain\\username

(or just username=username if this is a local user)

6. Assuming both your initrd.gz and ping.conf files are located

in the root of the share, type:

- gzip -d /mnt/smbfs/initrd.gz

- mount -o loop /mnt/smbfs/initrd /mnt/loop

- mkdir /tmp/rootfs

- cd /tmp/rootfs

- tar xvfj /mnt/loop/rootfs.tar.bz2

- cp /mnt/smbfs/ping.conf /tmp/rootfs/etc/ping.conf

- tar cvf – * |bzip2 -9 – >/mnt/loop/rootfs.tar.bz2

- umount /mnt/loop

- gzip -9 /mnt/smbfs/initrd

 

Remember that Linux's shell is case-sensitive.

 

From PING 2.00 RC8, it's possible to avoid having to modify the image to get the same result. Every key=value setting contained in the ping.conf file can be passed directly to the kernel at boot time. To do this, simply edit your isolinux.cfg file (if CD/DVD, pxelinux.cfg\DEFAULT if PXE), and modify the APPEND line accordingly. Be careful that DOS linefeeds will cause problems – so, either edit the sample file available from the download section of the PING web site, or use a unix-friendly editor like Ultra-Edit (tks Fubar Bundy for the tip).

 

For example, to have PING leave you to a shell after job completion, you'd add the string After_Completion=Shell to the APPEND line. Note that the syntax key="value" is accepted, allowing space chars to be passed too. Note also that backslashes (i.e. \) are escaping chars; if you need it for a path, or a domain\username combo, use a slash rather. If you really need a backslash, type two backslashes (the first one will escape the second one). E.g.: User="mydomain\\john". E.g.: User="mydomain/john".

 

If the ping.conf file has been customized, you still can pass keys/values to the kernel at boot time. They'll be given priority over ping.conf's data.

 

List of currently supported settings :

 

 

 

Key name

Possible Values / Examples

Description

Client network configuration

IP

Ex.: 192.168.0.1

The IP address you want the client to be assigned. Pass no IP if you've got a DHCP and want to use it.

Netmask

Ex.: 255.255.255.0

The netmask corresponding to the IP.

Gateway

Ex.: 192.168.0.1

The gateway corresponding to the IP.

DHCP_Timeout

Ex.: 15

If you need to set a non-default timeout for DHCP, set it here in seconds.

Images location section

Server

Ex.: 192.168.0.1

 

Ex.: /dev/hda2,/dev/sda2

The IP of the host where images made with PING are located.

 

The images can also be stored on a local partition; in such a case, mention it. If the images can be stored on different partitions, use commas to give several possible choices.

Share

Ex.: MyShare

Name of the MS Share.

User

Ex.: administrator

User to use (can be domain/user).

Passwd

Ex.: secret

Password to send.

Directory

Ex.: /Partimage

If you've made a directory in your share, give it here (in the example, the complete path was \\192.168.0.1\MyShare\Partimage).
 

Automating the image choice

Image_To_Restore

Ex.: My_Image_20071225

Specify here the name of the image to restore. This means that in Directory "/Partimage", to be found in share "//192.168.0.1/MyShare", there will be have to be subfolder called "My_Image_20071225".

New_Image_Name

Ex.: My_Local_Backup

In the case you would like to automatize the creation of a new image, set Image_To_Restore to Create_New_Image. If you also want to force the name of that future image, use the New_Image_Name parameter. You may also set now the names of the partitions you'll want PING to store.

Parts_To_Backup

Ex.: sda1,sda2,sdb1

If you set Image_To_Restore to "Create_New_Image", you can now define the partitions that will be stored. Note that if you want the 1st part to be stored, and you don't know if the device will be IDE or SATA, you might set Parts_To_Backup to "hda1,sda1" – and nothing bad will happen if /dev/sda1 can't be found.

Already_Existing_Image

Ex.: Update,Rename

Finally, if there's already an image in your Directory called after the New_Image_Name you have set, you might define here what PING should do with the Already_Existing_Image parameter. Set it either to "Replace" (old dir will be removed), or to "Rename" (old dir will be renamed to xxx.OLD.YYYYMMDDHHMMSS), or to "Update". The Update choice is only possible when the preexisting image has been made with version 3.00 or greater of PING, and if a xxxx.RecFiles.txt have been recorded (ex.: sda1.RecFiles.txt for partition /dev/sda1), containing the sizes and checksums of all files found on the part's filesystem. And if you set Already_Existing_Image to "Update,Replace", PING will try to update, but Replace if there's no xxxx.RecFiles.txt. "Update,Rename" is the last possible choice.
 

Misc

Repart

Y or N

If Repart is set to Y, and if you've got only one partition on your local hard disk drive and want to store an image of it locally, then this unique partition will be splitted for you. If set to N, PING will simply exit. And if commented, you'll be asked for what to do. May we suggest you'd better partition yourself for this kind of situation.

After_Completion

Shell or Reboot or Shutdown

What will PING do after the job is finished ? if Shell, you'll be dropped to a Linux shell. Useful if you want to check the /tmp/x.log log.

Replace_BIOS

Y or N

Will we replace the BIOS if a "bios" file is found ? Note that you can simply delete this "bios" file before making your restorations to avoid having your bios params modified, but in some cases, you might want to have the bios settings recorded, and to restore them on a selection of target stations.

CIFS_Preferred

Y or N

To map a MS share, SAMBA can use either SMBFS or CIFS. For some reasons, it has been constated that CIFS can be much faster than SMBFS on some types of networks. And the contrary is true, too!

NFS_Preferred

Y or N

Will use Sun's NFS protocol instead of Microsoft's SMB to mount the network share. Note that in this case, parameters Username and Passwd are useless.

FTP_Preferred

Y or N

Will use the FTP protocol to map a distant share. Parameters Username, Passwd, Server and Directory are used, but not the Share parameter. Note that you can only restore an image by FTP, but not create one (yet).

Zsplit_Preferred

Y or N

Set this to Y if you want zsplit, which is a dd-like utility, to be used instead of partimage. Most users should use partimage, and therefore set this param to N.

Tarball_Preferred

Y or N

In some situations, you might want a tarball to be preferred to partimage. Note that making such an archive is only useful when you want to store files for a backup purpose. Restoring a PING image with tarballs will usually result in a system unable to boot (unless you fix the boot sector). Be aware also that NTFS ACLs cannot be archived by PING (yet). Most users should use partimage, and therefore set this param to N.

No_Shell

Y or N

Set this option to Y if you don't want PING to propose the user to get a shell.

Note that if you have also set the After_Completion key to Shell, the user will finally be given a shell. If the After_Completion key is not set at all, then the user won't be proposed to get a shell at the end of PING's job.

Minimize_Before_Storing

Y or N

It can be interesting to reduce the size of the partition before storing it. Thus, it's possible to restore it later into a smaller partition. Note that even if we decide later to restore into a equally-big or bigger partition, PING will always try to maximize the size of the filesystem at the end.

You are strongly advised to have a full working backup of your system before choosing this option.

AUTO

Y or N

If you want NO QUESTION to be raised, no popup at all, set this value to Y. It's equivalent to creating an empty AUTO file on the root of a PING CD/DVD (which is now deprecated, yet still supported for backwards compatibility).

Cmd_1

  

Cmd_1 is a shell command for PING to execute before the first blue welcome screen.

Cmd_2

  

Cmd_2 is a shell command for PING to execute after the mounting of SMB shares.

Cmd_3

  

Cmd_3 is a shell command for PING to execute at the end (before giving a shell or reboot or shutdown).

Force_Dirty_NTFS_Mount

Y or N

If set to Y, we'll mount R/W NTFS filesystems even if they have the dirty flag set. It's not recommended, of course, but it might help sometimes. If not set, the question will be raised.

Its_HDA_Stupid

Y or N

When trying to restore an image made on a PATA drive (called for example by linux hda) to a SATA drive (called sda), first versions of PING would complain and leave. Now, if the expected target device cannot be found, PING will propose to choose among detected HDDs. If there's only one possible choice and you don't want any possible interaction to be given to the user, set this parameter to Y.

Extend_Parts_Whenever_Possible

Y or N

Sometimes, you'll restore images to a bigger drive. Sometimes, there will be empty space after or between parts. Set this parameter to Y if you want PING to extend partitions and contained filesystems each time it's possible. If the param is not set, PING will ask the user.

Dont_Warn_Me

Y or N

Users will have to validate a screen warning if there's data on the disk and it's going to be overwritten — except if AUTO mode is set on, or if the param Dont_Warn_Me is set on.

Compression_Type

Ex.: gzip

Set the compressor to be used. Else, will be asked. Can be set to 'gzip', 'bzip2' or 'no compression'.

Store_MD5

Y or N

You can have PING store all names, sizes and MD5 checksums of files contained in a partition you store. In this case, this information will be stored in a file called sda.RecFiles.txt and stored in your image directory. The presence of this file will make it possible for you to have PING update this image later.

 

(Note: it's not really an update, because partimage and zsplit-stored files cannot be addressed, but modified or added files will be stored in an archive, added to the partimage/zsplit files).

Verbosity

Verbosity

0, 1 or 2

Defines the verbosity level (still, everything stored in /tmp/x.log)

0 = no verbosity at all

1 = only warnings and errors

2 = everything (default)

Unique_Message

Some text

If Verbosity is set to 0, it's a good idea to tell users that PING is still working on the system. Customize the message there.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Directory of E:\Partimage\T1_Bis

 

24/06/2007 06:38 384 bios

24/06/2007 06:38 512 hda

24/06/2007 06:55 660 588 216 hda1.000

24/06/2007 06:56 32 518 458 hda1.001

24/06/2007 06:38 10 240 hda1.first_sectors

24/06/2007 06:56 1 024 hda2.first_sectors

24/06/2007 06:56 10 240 hda5.first_sectors

24/06/2007 10:43 38 hda2_0.spl.zp

24/06/2007 09:30 660 616 876 hda5_0.spl.zp

24/06/2007 09:38 660 615 020 hda5_1.spl.zp

24/06/2007 09:45 660 613 560 hda5_2.spl.zp

24/06/2007 09:53 660 618 499 hda5_3.spl.zp

24/06/2007 10:05 310 638 295 hda5_4.spl.zp

13 File(s) 3 646 231 362 bytes

 

 

 

Directory of E:\Partimage\T1_Bis

 

24/06/2007 06:38 384 bios

24/06/2007 06:38 512 hda

12/06/2007 10:37 4 164 232 kernel

25/06/2007 19:46 0 MULTI

24/06/2007 06:55 660 588 216 hda1.000

24/06/2007 06:56 438 213 hda5.000

24/06/2007 06:56 32 518 458 hda1.001

15/02/2007 11:44 10 932 isolinux.bin

22/06/2007 20:33 199 isolinux.cfg

24/06/2007 06:38 10 240 hda1.first_sectors

24/06/2007 06:56 1 024 hda2.first_sectors

24/06/2007 06:56 10 240 hda5.first_sectors

25/06/2007 14:10 22 766 432 initrd.gz

24/06/2007 10:43 38 hda2_0.spl.zp

24/06/2007 09:30 660 616 876 hda5_0.spl.zp

24/06/2007 09:38 660 615 020 hda5_1.spl.zp

24/06/2007 09:45 660 613 560 hda5_2.spl.zp

24/06/2007 09:53 660 618 499 hda5_3.spl.zp

24/06/2007 10:05 310 638 295 hda5_4.spl.zp

19 File(s) 3 673 611 370 bytes

 

 

 

Directory of E:\Partimage\T1_Bis

 

24/06/2007 06:38 384 bios

24/06/2007 06:38 512 hda

12/06/2007 10:37 4 164 232 kernel

25/06/2007 19:46 0 MULTI

24/06/2007 06:55 660 588 216 hda1.000

24/06/2007 06:56 32 518 458 hda1.001

15/02/2007 11:44 10 932 isolinux.bin

22/06/2007 20:33 199 isolinux.cfg

24/06/2007 06:38 10 240 hda1.first_sectors

24/06/2007 06:56 1 024 hda2.first_sectors

25/06/2007 14:10 22 766 432 initrd.gz

24/06/2007 10:43 38 hda2_0.spl.zp

12 File(s) 720 060 667 bytes

 

 

 

Directory of E:\Partimage\T1_Bis

 

25/06/2007 19:46 0 MULTI

24/06/2007 06:56 10 240 hda5.first_sectors

24/06/2007 09:30 660 616 876 hda5_0.spl.zp

3 File(s) 660 627 116 bytes

 

(Note: you'll call mkisofs this way (no boot): mkisofs -r -o ../Image_2.iso .)

 

 

 

Directory of E:\Partimage\T1_Bis

 

25/06/2007 19:46 0 MULTI

24/06/2007 09:38 660 615 020 hda5_1.spl.zp

2 File(s) 660 615 020 bytes

 

 

 

Directory of E:\Partimage\T1_Bis

 

25/06/2007 19:46 0 MULTI

24/06/2007 09:45 660 613 560 hda5_2.spl.zp

2 File(s) 660 613 560 bytes

 

 

 

Directory of E:\Partimage\T1_Bis

 

25/06/2007 19:46 0 MULTI

24/06/2007 09:53 660 618 499 hda5_3.spl.zp

2 File(s) 660 618 499 bytes

 

 

 

Directory of E:\Partimage\T1_Bis

 

24/06/2007 10:05 310 638 295 hda5_4.spl.zp

1 File(s) 310 638 295 bytes

 

 

 

 

 

 

 

 

 

 

 

Disk /dev/hda: 8589 MB, 8589934592 bytes
255 heads, 63 sectors/track, 1044 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1        1044     8385898+   7  HPFS/NTFS

 

 

 

ntfsresize v2.0.0 (libntfs 10:0:0)

Device name : /dev/hda1

NTFS volume version: 3.1

Cluster size : 4096 bytes

Current volume size: 8587153920 bytes (8588 MB)

Current device size: 8587160064 bytes (8588 MB)

New volume size : 5999993344 bytes (6000 MB)

Checking filesystem consistency …

100.00 percent completed

Accounting clusters …

Space in use : 1577 MB (18.4%)

Collecting resizing constraints …

Needed relocations : 0 (0 MB)

WARNING: Every sanity check passed and only the dangerous operations left.

Make sure that important data has been backed up! Power outage or computer

crash may result major data loss!

Are you sure you want to proceed (y/[n])?

 

 

 

Disk /dev/hda: 8589 MB, 8589934592 bytes

255 heads, 63 sectors/track, 1044 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

 

Device Boot Start End Blocks Id System

/dev/hda1 * 1 730 5863693+ 7 HPFS/NTFS

/dev/hda2 731 1044 2522205 83 Linux

 

 

 

Filesystem 1K-blocks Used Available Use% Mounted on

/dev/hdc 19582 19582 0 100% /mnt/cdrom

/dev/hda1 5859368 1539268 4320100 27% /mnt/dos

/dev/hda2 2482556 69304 2287144 3% /mnt/linux

 

 

 

 

boot = /dev/hda

map = /mnt/dos/map

prompt

timeout = 150

vga = normal

lba32

delay = 30

read-only

large-memory

root = current

 

other = /dev/hda1

label = windows

 

image = /mnt/linux/kernel append="
vga=normal devfs=nomount pxe ramdisk_size=33000 load_ramdisk=1 init=/linuxrc prompt_ramdisk=0 initrd=initrd.gz root=/dev/ram0 rw noapic nolapic lba combined_mode=libata ide0=noprobe nomce pci=nommconf pci=nomsi irqpoll"

label = restoration

initrd = /mnt/linux/initrd.gz

 

 

 

Added windows *

Added restoration

 

 

 

 

boot = /dev/hda2

map = /mnt/dos/map

prompt

timeout = 150

vga = normal

lba32

delay = 0

read-only

large-memory

root = current

ignore-table

 

image = /mnt/linux/kernel append="
vga=normal devfs=nomount pxe ramdisk_size=33000 load_ramdisk=1 init=/linuxrc prompt_ramdisk=0 initrd=initrd.gz root=/dev/ram0 rw noapic nolapic lba combined_mode=libata ide0=noprobe nomce pci=nommconf pci=nomsi irqpoll"

label = restoration

initrd = /mnt/linux/initrd.gz

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Support

 

Like most admin tools, PING has been made easy enough to start with, but you might come across special, complex configurations and needs.

 

We are committed to improving PING as much as we can, and questions from users are often a useful feedback that makes it easier for us to find bugs to fix, or to develop smart new features.

 

For this reason, support can often be obtained for free on the PING forum : http://www.windowsdream.com/forum/viewforum.php?f=7 .

 

Yet, in some cases, you might need dedicated support, which could be consultancy days or mail/telephone support. Such a service is available, yet not free. For more information, please contact us :

 

        EFFITEK SSII

        4-10 rue Henri Murger

        75019 Paris, France

        +33 6 6550 2992

        PING_Support@effitek.fr

 

 

 

License

 

PING is released under the same economic and licensing model as MySQL. Just like MySQL, you may download and use for free the Community Version of PING, released under the well-known GPL license.

 

Yet, if you own a business and need to include PING in paying software, you'll have to acquire the Enterprise Version of PING. Included with this version, you'll benefit from dedicated support from the dev' team, and more information. Most important, you'll also show your involvement for the community, by supporting a great opensource project.

Posted on janvier 9, 2011 at 13 h 29 min by Fabrice Scemama · Permalink
In: Ingénierie du Poste de Travail · Tagged with: , , , , , , ,

Leave a Reply

You must be logged in to post a comment.