Академический Документы
Профессиональный Документы
Культура Документы
=======================================
Boot parameters (also known as cheatcodes) are used to affect the
booting process of Porteus. The cheatcodes listed here are only those
that are specific to Porteus (see the final note for information on
cheatcodes that apply to all linux distributions, including Porteus).
You can use these parameters to disable desired kinds of hardware
detection, start Porteus from a specific location, load additional
modules, etc.
Reboot your computer and wait several seconds until the graphical
Porteus logo appears with a boot menu. Choose your desired menu
entry and hit Tab, which will allow you to edit the command line.
Add your desired boot argument from the list below to affect booting
the way you like.
Here's an example of what the boot line would look like, adding the
noauto and copy2ram cheatcodes to a standard Porteus boot option
(which already has some other cheatcodes by default):
APPEND initrd=initrd.xz changes=/porteus/ noauto copy2ram
These cheatcodes can also be added to the APPEND line of your
/boot/syslinux/porteus.cfg entries (or other bootloader config files)
to apply them automatically on every boot.
--------------------------------------List of available cheatcodes in alphabetical order:
NOTE: Example cheatcodes are sometimes listed below inside single
quotes (e.g. 'example=somevalue') for clarity in the documentation.
When you enter these cheatcodes during boot time or in your
porteus.cfg, you should not use these quote marks.
base_only
... This cheatcode will prevent the system from loading any
modules at startup other than the 'base' modules included
with the default ISO (000-kernel.xzm, 001-core.xzm, etc).
This is useful in debugging to see if problems you are
having are associated with some module you've added to the
system.
changes=/dev/device
changes=/path/
changes=/path/file.dat
... All changes made in Porteus are kept in memory until you reboot.
With this boot parameter, you tell Porteus to use a device
(or a file or directory) other than your memory for storing
changes. You can, for example, format your disk partition
/dev/sdb2 with some Linux filesystem (eg. xfs) and then use
'changes=/dev/sdb2' to store all changes to that partition.
This way you won't lose your changes after reboot.
... If you use a file image instead of a device, and the image
contains a valid filesystem, Porteus will mount it on a loop
device and will store changes to it.
... If you use a directory, Porteus will save changes to it (it
will make a 'changes' subdirectory there). This should only
from=/dev/device
from=/path/folder
from=/path/porteus.iso
... Loads Porteus from the specified device, folder or ISO file.
Examples:
'from=/dev/sdb2' will attempt to load unpacked Porteus ISO from
the second partition on your second drive.
'from=/mnt/sda2/linux-testing' will attempt to load unpacked ISO
from the 'linux-testing' folder placed on the second partition.
'from=/linux-ISO/porteus.iso' will attempt to load the Porteus
data from an ISO file placed inside the 'linux-ISO' folder.
If the destination partition is not provided with this
cheatcode, the booting script will search through all available
devices for your data.
fsck
... Enables a filesystem check for ext(2,3,4) and reiserfs
partitions during boot time before anything is mounted by
Porteus. XFS does not need fsck as a check is performed
automatically during the mount operation.
NOTE: On some systems, you will need to use the 'delay='
cheatcode in order to allow your devices to settle up.
This should only be needed to fsck usb flash drives.
guiexec=my_script
guiexec=firefox;pidgin
... Execute specified command(s) in runlevel 4, when the graphical
interface is loaded; unlike 'cliexec' this cheatcode can be
used to start graphical applications.
Use semicolons (;) as command separators with no spaces.
... If you need to use spaces in the command line, replace them
with '~'.
Example: 'guiexec=firefox~kernel.org' will open the firefox
browser on the 'kernel.org' website.
kmap=keyboardmap
kmap=keyboardmap1,keyboardmap2,keyboardmap3
kmap=keyboardmap:variant
... Specifies the preferred keyboard layout for KDE/LXDE/XFCE or
other desktop. A full list of supported layouts can be found in
the /etc/X11/xkb/symbols folder. Up to 3 layouts are supported.
Example: 'kmap=ara,us' will set the arabic keyboard layout at
startup. 'kmap=ara,us' will keep arabic layout as default
with possibility of switching to 'us' by 'alt+shift' key
combination.
Keyboard layout variants are also supported.
Example: 'kmap=pl:qwertz' will set the polish keyboard layout
with 'qwertz' as a variant.
load=module
load=module[1];module[n]
... Load optional modules from /optional/ directory on the booting
media. Additional modules can be listed, separated
rammod=module[1];module[n];folder[1];folder[2]
... Specify module(s) or folder(s) containing modules which should
be copied to RAM when using the 'copy2ram' cheatcode. This
allows you to have the speed benefit of 'copy2ram' for the
modules you use the most, without occupying your RAM with those
modules that you make use of less often. Any modules that are
not specified will be mounted in place on the block device, so
your device will remain mounted while Porteus is running.
You can use a full or partial names for your search string,
but keep in mind that all modules and folders that match your
string will be loaded into RAM; if you have extra modules in a
folder named 'lxde' and you use 'rammod=lxde', then the module
003-lxde.xzm from /porteus/base will be loaded in addition to
all modules in the 'lxde' folder.
NOTE: 'rammod' cannot be used without 'copy2ram', and it also
will not load modules from /porteus/optional or external
locations unless you also specify these modules with the
'load=' or 'extramod=' cheatcodes.
Examples:
'rammod=001;002;004;firefox'
'extramod=/mnt/sdb3/porteus/gimp rammod=001;002;gimp'
rootcopy=/path/to_folder/with_files
... Copy files from specified directory directly to the live
filesystem. This directory will be used instead of the
traditional /porteus/rootcopy.
Example: 'rootcopy=/mnt/sda5/porteus-files'
sgnfile=some_name.sgn
... This cheatcode specifies the *.sgn file which Porteus will
search for. This is useful when you want to store several
Porteus editions on one disk/disc.
Example: 'sgnfile=porteus-usb.sgn'
storage=/path/folder
storage=/path/file.dat
... This cheatcode takes action only when used together with the
'pxe' cheatcode. It tells the server to store persistent
changes from the clients in a specified folder. Changes must
be saved on a real and writable filesystem (wont work with
aufs).
Separate folders for each client will be created with the name
'/path/folder/client-xxxx' where xxxx is the last 4 characters
of the clients' NIC MAC address.
This cheatcode should be used on the server side.
Example: 'storage=/mnt/sda3/pxe-clients'
timezone=region/zone
... Tell Porteus the correct timezone for your location. By default,
this assumes that your hardware clock is set to localtime. To use
a timezone with a hardware clock set to UTC time instead, also
add the 'utc' cheatcode.
because they are unique to your device, and your data will be found
and properly mapped on different hardware configurations.
Every cheatcode which contains a /path can take advantage of 'UUID:'
and 'LABEL:' extensions.
Examples:
changes=UUID:STrING-0F-ChARACtERS/path/file.dat
extramod=LABEL:YourLabelName/path/to_folder/with_modules
from=UUID:STrING-0F-ChARACtERS/path/folder
rootcopy=LABEL:YourLabelName/path/to_folder/with_files
SPECIAL NOTE FOR USING CHANGES CHEATCODE WITH 'EXIT:' extension:
The 'EXIT:' extension tells the 'changes=' cheatcode to keep all
of the files that have been added/deleted/modified during the
live session stored in memory until you reboot/shutdown. Your
RAM works as a buffor which gets dumped on the drive only once,
when the session is finished.
'changes=EXIT:' cheatcode has following advantages:
- Porteus works as fast as in 'Always Fresh' mode as all modifications
to files and folders are performed in RAM.
- reduced number of read/write cycles should extend the life of SSD
drives and usb sticks.
The only disadvantage of the 'EXIT:' extension is that the session
does not get saved in cases where you experience a hang (kernel crash)
or power interrupt.
Please use with caution!
While you are running a session with changes=EXIT, you can use the
'dump-session' command (run as root from the command line) to move all
of your changes from RAM to your storage media. This will reduce the
risk of data loss and free up your RAM.
Examples:
changes=EXIT:/dev/device
changes=EXIT:/path/
changes=EXIT:UUID:STrING-0F-ChARACtERS/path/file.dat
NOTE FOR THE LILO USERS:
If the LILO bootloader has been installed, you will get a text menu
with the standard boot options (KDE, LXDE, Always Fresh, etc).
Use your arrow key to highlight your desired entry (if you are using
the first entry (KDE), press down, then up to highlight KDE).
The name of your boot option is added to the 'boot:' line, and you can
type your cheatcodes after that.
For example:
boot: KDE debug noauto
would boot into KDE with all of the standard codes used for KDE, plus
debug and noauto. If you want to use LILO with custom cheatcodes at
every boot without manually entering them each time, you must modify
the /boot/syslinux/lilo.conf and then repeat installation by running
/boot/Porteus-installer-for-Linux.com utility as LILO must reload it's
configuration.
FINAL NOTE:
The cheatcodes listed above are those that are unique to Porteus.
There are literally hundreds of other kernel boot parameters
that can be used. For more information on these parameters visit:
http://www.kernel.org/doc/Documentation/kernel-parameters.txt
Thanks for reading!