3.1.0 | CD |
-- Clonezilla Live updated to version 1.2.3-27
+- Clonezilla Live updated to version 1.2.4-28-686
- SystemRescueCD updated to version 1.4.0
- Super Grub Disk updated to version 0.9799
- Added Super Grub Disk 2 version 1.30
@@ -301,7 +301,7 @@
Download [^]
Installation package: create-clonezilla-sysresccd-3.1.0.tar.gz [~ 1.7 MB]
-ISO file: clonezilla-sysresccd-full-mod-3.1.0.iso [~ 366 MB]
+ISO file: clonezilla-sysresccd-full-mod-3.1.0.iso [~ 370 MB]
md5sum file: md5sum.txt
ISO file md5sum:
Can I help? [^]
@@ -543,35 +543,49 @@
The boot parameters you can use are:
- General boot options
- - setkmap=xx: if you don't want to be asked for the keymap, you can choose which keymap to load automatically. Replace
xx with your keymap (for example: setkmap=de for german keyboards)
- - docache: this option is very useful if you need to insert another disc in the CD drive after booting. The CD-ROM will be fully loaded into memory, and you will be able to remove the disc from the drive. The
docache option requires 400MB of memory if you want to cache everything (including the bootdisks and isolinux directories). You can add the lowmem option if you have less that 400MB of memory of to prevent these directories to be copied into memory.
- - root=xxx: the root=<device> option lets you boot an existing linux system. For example, if you have a linux gentoo installed on
/dev/sda6 , you can type rescuecd root=/dev/sda6 and Gentoo Linux will be started instead of the system that is on the CD-ROM. Keep in mind that you must use a 64bits kernel if your system is made of 64bits programs. For instance, you can boot a 64bits linux system installed on /dev/sda6 with rescue64 root=/dev/sda6 . From SystemRescueCd-1.0.4, this option works with LVM disks, so you can write something like rescuecd root=/dev/VolGroup00/LogVol00 . SystemRescueCd-1.0.4 and newer versions also supports root=auto , that will scan all the block devices of the computer to find a linux system. The first linux system found on the disks will be started. So with root=auto let you start the system installed from the CD-ROM in case you have problem with your boot loader or with your kernel for instance. You can have more details about that option.
- - initscript=service:action: This options allows you to automatically start/stop a service at boot time. For instance if you need the samba service to be started, you can boot with the following option:
initscript=samba:start . This does the same thing as /etc/init.d/samba start . You can use this option several times with different services. All the action that are supported by an initscript can be used. This option is available with SystemRescueCd-1.0.2 and newer.
- - backstore=xxx: SystemRescueCd-1.1.x comes with support for the backing-stores. Basically, a backing-store is a loopback filesystem which saves all the changes you can make in SystemRescueCd when you use it. In other words it allows you to save all the files which changes in SystemRescueCd while you use it, so that you keep these changes the next time you boot it. By default, sysresccd automatically scan all your removable devices (eg: usb sticks) at boot time and uses the first backing-store it finds if there is one. A backing-store is not mandatory and it the scan fails it will just store the files which change in memory. To disable the disks scan at boot time you can specify
backstore=off on the boot command line. If you want to save your backing-store file on an harddisk, you will have to boot with backstore=alldev so that it scans all devices not just removable devices. The default place for backing-stores file is any file named sysrcd.bs located at the root of a disk which is often an USB key. You can change the path by using an option such as backstore=/sysrcd/mybackstore.bs and then sysresccd will try to find a file named mybackstore.bs located in /sysrcd in any block-device (partition, USB-stick, ...). You can find more information about on the page about backing-stores.
+ General boot options
+Press <TAB> to add additional options.
+
+- docache: causes the CD-ROM will be fully loaded into memory. A slower start but once complete, programs start faster and the CD drive will be released allowing normal access to other CDs. This requires 400MB of memory to cache everything (including the
bootdisks and isolinux directories). Add lowmem if you have less that 400MB of memory of to prevent these directories to be copied.
+
+During boot you will be prompted for the keyboard configuration, avoid this by using
+
+- setkmap=kk: which defines the keymap to load where
kk (example: setkmap=de for German keyboards)
+ - root=/dev/xdnp: the root=<device> option boots an existing linux system. For example, if you have linux Gentoo installed on
/dev/sda6 , use rescuecd root=/dev/sda6 to start it. Keep in mind that you must use a 64bit kernel if your system is made of 64bit programs. This option works with LVM volumes. Use rescuecd root=/dev/VolGroup00/LogVol00 . Support is also provided for root=auto , which scans all the block devices tfor a linux system. The first linux system found will be started. So with root=auto let you start the system installed from the CD-ROM in case you have problem with your boot loader or kernel. It's also possible to specify a partition using its filesystem label or filesystem uuid . If the label of the partition where linux is installed is mylinux , then boot it using rescuecd root=LABEL=mylinux . Similarly root=UUID=b3d3bec5-997a-413e-8449-0d0ec41ccba7 . See more details.
+ - initscript=service:action: This options allows start/stop a service at boot time. For instance if you need the samba service to be started, you can boot with:
initscript=samba:start . This does the same thing as /etc/init.d/samba start . Use this option multiple times for different services. All the actions that are supported by an initscript can be used.
+ - backstore=xxx: SystemRescueCd comes with support for the backing-stores. A backing-store saves all the changes you can make. so that you keep these changes the next time you boot it. By default, sysresccd automatically scan removable devices (eg: USB sticks) at boot time and uses the first backing-store it finds. A backing-store is not mandatory and it the scan fails it will store the files which change in memory. To disable the disks scan at boot time specify
backstore=off on the boot command line. If you want to save your backing-store file on an harddisk, boot with backstore=alldev to scan all devices (not just removable devices). The default location for backing-stores file is any file named sysrcd.bs located at the root of a disk which is often an USB stick. Change the path by using backstore=/sysrcd/mybackstore.bs . See backing-stores.
+ - isoloop=xxx: Grub2 (currently in development: grub-1.98) provides a new feature to boot from an ISO image which is stored from the hard disk. If you put a copy of
systemrescuecd-x86-x.y.z.iso on a partition that Grub2 can read then you can boot SystemRescueCd directly from the ISO image stored on your hard drive. This is very convenient if you frequently update SystemRescueCd and you want to boot it directly from Grub2. Grub2 knows what an ISO image is and it will load the kernel image (rescuecd/rescue64) and the initramfs (initram.igz) from the ISO into memory. It will then do its normal job and execute the kernel. The SystemRescueCd init script must then be aware that its sysrcd.dat file is in an ISO and not directly on the partition. For that reason, this isoloop=xxx boot option is required so you must use it in your grub.cfg . This option is only supported in SystemRescueCd-1.4.0 and more recent. This option specifies the path of the ISO image in the partition that grub considers as its root partition. It's important to understand that the path of the ISO image may be different from the path on your linux system. If you have a separate boot partition mounted on /boot and if you copy this ISO image to /boot/sysrcd/systemrescuecd-x86-x.y.z.iso then the option has to be isoloop=/sysrcd/systemrescuecd-x86-x.y.z.iso . This is because the boot partition is what Grub2 will consider as its root partition during the boot process. Please read the section about isoloop for more details.
+
+ Hardware, drivers and troubleshooting options
+- dodebug: Enables verbose messages in linuxrc
+
+- doload=xxx: loads needed modules, multiple occurrences are permitted (example:
doload=3c59x )
+ - noload=xxx: prevents loading modules, multiple occurrences are permitted (example:
noload=3c59x ). Use this option if you have a problem when the system loads a particular module.
+ - nonet: this will disable the network auto detection at startup
+
+- scandelay=x: pauses x seconds during the startup to allow slow devices to initialize. This is required when you boot an USB device. A delay of only few seconds should be enough.
+
+- doxdetect: Since version 0.3.5 the auto-configuration is done in X.Org itself, mkxf86config is disabled by default. This option forces the system to run the mkxf86config startup script and to run the hardware auto-detection from this script. Use this option if you have problems with the graphical environment configuration. This option replaces the option
noxdetect that was useful in previous versions.
+ - nodetect: prevents generic hardware auto-detection. Use this option if you have problems with the hardware auto-detection.
+
+- dostartx: load the X.Org graphical environment.
+
- forcevesa: Forces X.Org to use the safe VESA driver instead of the best video driver detected for your video card. Use this option if you cannot get the graphical environment working with the default options.
+
- forcevesa=xxx: The
startx command will load the Xvesa server instead of Xorg , and use the screen resolution given as parameter (eg: 1024x768 , 1280x1024x32 ).
- Hardware, drivers and troubleshooting options
-
Clonezilla Live boot parameters [^]
|
@@ -602,11 +631,12 @@
The following info comes from the page titled The boot parameters for Clonezilla live.
Clonezilla live is based on Debian live with clonezilla installed. Therefore there are 2 kinds of boot parameters:
-- Boot parameters from live-initramfs. You can refer to this manual of live-initramfs.
+
- Boot parameters from live-initramfs. You can refer to this manual of live-initramfs.
- Boot parameters specially for Clonezilla. All of them are named as "ocs_*", e.g. ocs_live_run, ocs_live_extra_param, ocs_live_batch, ocs_lang.
- ocs_live_run is the main program to run in Clonezilla live to save or restore. or other command. Available program: ocs-live-general, ocs-live-restore or any command you write. Use the Absolute path in Clonezilla live.
- e.g. ocs_live_run="ocs-live-general"
+ e.g. ocs_live_run="ocs-live-general"
+ //NOTE// You might have to use "sudo" command inside your own script, or you can assign it like: ocs_live_run="sudo bash /my-clonezilla"
- ocs_live_extra_param will be used only when ocs_live_run=ocs-live-restore (not for ocs-live-general or any other), then it will be passed to ocs-sr. Therefore these parameters are actually those of ocs-sr.
e.g. ocs_live_extra_param="-b -c restoredisk sarge-r5 hda"
- ocs_live_keymap is for keymap used in Clonezilla live. Man install-keymap for more details.
@@ -620,7 +650,17 @@
- ocs_daemonon, ocs_daemonoff, ocs_numlk, ocs_capslk.
Ex. for the first 2 parameters, ocs_daemonon="ssh", then ssh service will be turned on when booting. For the last 2 parameters, use "on" or "off", e.g. ocs_numlk=on to turn on numberlock when booting.
- ocs_prerun, ocs_prerun1, ocs_prerun2... is for you to run a shell script before Clonezilla is started. E.g. ocs_prerun="/live/image/myscript.sh". If you have more commands to run, you can assign them in the order: ocs_prerun=..., ocs_prerun1=..., ocs_prerun2=.... If more than 10 parameters, remember to use ocs_prerun01, ocs_prerun02..., ocs_prerun11 to make it in order.
-
- ocs_live_run_tty. This option allows you to specify the tty where $ocs_live_run is run. By default $ocs_live_run is run on /dev/tty1 only. (It was also on /dev/ttyS0 before, but since Clonezilla live >= 1.2.3-22 no more this due to a problem). If you want to use ttyS0, for example, add live-getty and console=ttyS0,38400n81 in the boot parameter.
+
- ocs_live_run_tty. This option allows you to specify the tty where $ocs_live_run is run. By default $ocs_live_run is run on /dev/tty1 only. (It was also on /dev/ttyS0 before, but since Clonezilla live >= 1.2.3-22 no more this due to a problem). If you want to use ttyS0, for example, add live-getty and console=ttyS0,38400n81 in the boot parameter.
+ //NOTE//
+
+ - This parameter was added in Clonezilla live 1.2.3-22 or later.
+
- If "live-getty console=$tty,38400n81" are assigned in the boot parameters, ocs_live_run_tty will honor $tty, even other value is assigned to ocs_live_run_tty in boot parameter.
+
- It's recommended to assign ocs_lang and ocs_live_keymap in the boot parameters too.
+
+ - ip, this option allows you to specify the network parameters for network card. In Clonezilla live a patched live-initramfs is used, which is different from the original live-initramfs so that you can assign DNS server, too. Its format is: ip=ethernet port,IP address, netmask, gateway, DNS. E.g. If you want to assing eth0 with IP address 10.0.100.1, netmask 255.255.255.0, gateway 10.0.100.254, DNS server 8.8.8.8, you can assign the following in the boot parameter:
+ip=eth0,10.0.100.1,255.255.255.0,10.0.100.254,8.8.8.8
+If more than one network card, you can use ":" to separate them, e.g.:
+ip=eth0,10.0.100.1,255.255.255.0,10.0.100.254,8.8.8.8:eth1,192.168.120.1,255.255.255.0,192.168.120.254,,
- Besides, "live-netdev" (yes, not ocs_live_netdev) can be used when using PXE booting, you can force to assign the network device to get filesystem.squashfs. This is useful when there are two or more NICs are linked. E.g. live-netdev="eth1" allows you to force the live-initramfs to use eth1 to fetch the root file system filesystem.squashfs.
@@ -3148,9 +3188,9 @@
In SystemRescueCD
Type
-less /mnt/livecd/README.txt
+less /livemnt/boot/README.txt
or
-links /mnt/livecd/README.html
+links /livemnt/boot/README.html
to view the html pages in links web browser.
Searching for text [^]
|
|