| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
The addons/ and optional/ directory will be searched for *.sxz modules
even if they live in subdirectories. This allows you to organize your
modules instead of dumping them all into a single directory.
If a module fails to load (because it is corrupted for instance) liveinit
will mention this on screen and write the modulename to a file
'/mnt/live/modules/failed'.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As documented in file "/usr/share/X11/xkb/rules/xorg.lst":
lv3 Key to choose 3rd level
lv3:ralt_switch_multikey Right Alt, Shift+Right Alt key is Compose
And as explained in https://help.ubuntu.com/community/ComposeKey :
There are four levels of keyboard entry. Selecting a level involves holding
a set of modifier keys down, this changes the function of all the other keys
on the keyboard. The levels are, by default:
Level Modifier Keys produced
-------------------------------
1 None Lowercase letters, numbers, etc.
2 Shift Uppercase letters, symbols printed on keyboard, etc.
3 AltGr Extra symbols not printed on the keyboard, some dead keys.
4 AltGr-Shift Even more symbols, more dead keys.
Dead keys are keys that appear to do nothing at first; they apply an accent
to the next letter you type.
Third and fourth level choosers:
Holding down the AltGr key and pressing another key will produce a third level
character. Holding down the AltGr and Shift keys (the order can be important)
and pressing another key will produce a fourth level character.
Note that some combinations are dead keys; an additional key-press is required
whereupon a diacritic will be added to the final character keyed.
Compose key:
Keying the combination Shift+AltGr (in that order), releasing these keys,
then entering two other keys will produce a special character.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Variable XKB can be set to "XkbLayout,XkbVariant,XkbOptions".
For example "xkb=ch,fr,compose:sclk,grp:alt_shift_toggle"
Note that the XkbOptions can be several comma-separated values.
The XkbLayout and XkbVariant values must not contain commas.
You can still set just the XkbVariant by adding something like "kbd=ch xkb=,fr"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some explanation about what the 'debug' boot parameter does:
'debug=1' => enable some strategic pauses during boot while showing 'mount'
and 'blkid' output, so you can scroll back and inspect the proceedings
(just 'debug' also enables level 1).
'debug=2' => enable verbose script execution in addition to the above pause
moments.
'debug=3' => verbose script execution but without the mount/blkid info during
the strategically placed pauses.
'debug=4' => dumps you into a debug shell right before the switch_root.
No other pauses other debugging aids are offered like with levels 1, 2 or 3.
But you can check the health of your Live system before Slackware boots up.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the user loads a non-system squashfs module (for instance from the
optional or addons subdirectories) and this contains kernel modules,
then the kernel must be made aware using a "depmod -a" call.
The previous implementation did this at the end of rc.local but
that was too late in the boot process: the kernel needs to be aware
of the new modules straight from the start, so that udev can enable
the hardware which is supported by these new kernel drivers on time.
So the depmod call was moved to the live init script (inside the initrd).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Sometimes your Slackware Live develops issues because the persistent data
storage is conflicting with new packages or data which you added to the
Live OS. This can be fixed by erasing persistent data, thereby reverting
the Live OS to its initial state - i.e. when the USB stick was booted
for the first time.
For this purpose the functionality of the existing "nop" boot parameter
was extended to allow the '=' and specifying a value of 'wipe'.
Note that the persistent data will be wiped before the Live OS boots, and
it does not matter if you are using a persistence directory or a container
file for storing persistent data.
This wipe includes all your persistent personal data in /home/
unless you have moved your /home into a container file on the USB stick.
|
|
|
|
|
|
| |
After doing your debug checks you can then type "exit" to exit
the debug shell. The init script will continue with the switch_root
and boot the OS.
|
|
|
|
|
| |
We bind-mount /run if we started dhcpcd - so it can not be un-mounted
at the end of the init.
|
|
|
|
|
| |
In case of network boot, do not kill the network, umount NFS prematurely
or stop udevd on shutdown.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The passwords for users 'live' and 'root' are easy to guess.
When you use the Slackware Live Edition on a public network,
you do not want people to use an exposed SSH login.
If you still want to have the SSH daemon enabled on boot, use the
'tweak' boot parameter and provide a 'ssh' value as follows:
"tweak=ssh"
This can be combined with other tweaks of course, all comma-separated.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The functionality of the old "nga" parameter is now implemented as a "tweak".
Tweaks are customizations that cater to specific hardware needs.
Syntax: tweaks=tweak1[,tweak2,[,...]]
Example: tweaks=nga,tpb
Currently implemented tweaks:
- nga => no glamor acceleration (X.Org tweak).
- tpb => enable TrackPoint scrolling while holding down middle mouse button.
- syn => start the syndaemon for better support of Synaptics touchpads.
|
|
|
|
| |
Provided by GigglesUK, thanks.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This default behaviour can be prohibited by applying an extended 'hostname'
boot parameter as follows:
hostname=your_custom_hostname,fixed
The qualifier 'fixed' after the comma will prevent the hostname from being
changed to something else than 'your_custom_hostname'.
|
| |
|
| |
|
|
|
|
|
|
|
| |
New boot parameter:
dhcpwait=<numseconds>
Maximum wait time for the DHCP client to configure a network interface
(new default: 20 seconds, was 10 seconds).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It is now possible to PXE-boot the Slackware Live Edition.
Extract the content of the ISO to (for instance) a new directory
called 'slackware-live' below your TFTP server's /tftproot directory
and then add lines like this to your pxelinux.cfg/default file:
label liveslak
kernel slackware-live/boot/generic
append initrd=slackware-live/boot/initrd.img load_ramdisk=1 prompt_ramdisk=0 rw printk.time=0 kbd=us tz=Europe/Amsterdam locale=us_EN.utf8 nfsroot=192.168.0.1:/tftpboot/slackware-live hostname=pxelive
Two new boot parameters have been added to support a NFS root:
* nfsroot => mandatory parameter defines the IP address of the NFS server
and the path to the extracted content of Slackware Live Edition.
* nic => parameter defining the driver for the network card (optional
and usually not needed because UDEV will figure out the driver for you),
the interface name (optional),
the IP configuration method (static IP or DHCP),
and in case of a static IP, the required parameters ipaddress, netmask
and an optional gateway.
Note that the 'nic' parameter is optional if you have a DHCP server in
your LAN: Slackware Live will figure out what the interface name is.
Syntax of these parameters:
nfsroot=ip.ad.dr.ess:/path/to/liveslak
nic=<driver>:<interface>:<dhcp|static>[:ipaddr:netmask[:gateway]]
Example use of these parameters:
nfsroot=192.168.1.1:/tftproot/slackware-live
nic=auto:eth0:static:10.0.0.21:24:
nic=:eth1:static:192.168.1.6:255.255.255.248:192.168.1.1
|
|
|
|
|
|
|
| |
The 'setup2hd' script will use this readonly overlay to install to your
harddrive. However, this readonly overlay still contained the Live
customizations which you do not want copied over to your harddrive.
This update fixes the logical fallacy so that 'setup2hd' works properly now.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the original version of the script, the squashfs modules' contents
would be extracted one after the other.
However this disregards any package or file deletions inbetween modules.
As a result, e.g. a PLASMA5 installation to disk using 'setup2hd' would
leave several artefacts in removed_scripts and removed_packages and probably
in other locations too.
The overlay is now constructed somewhat differently, so that 'setup2hd' can
access the full read-only filesystem properly; it will copy this content
to the harddisk using rsync. A progress indicator will show the stats of
files that are actually being transferred.
At the same time, the 'setup2hd' script's language settings are now
hard-coded by setting 'LC_ALL' and LANG to "C". Slackware's setup scripts
parse command output and expect english texts there, but when you selected
a different language when booting your Live OS, this would confuse e.g.
'liloconfig' to the extent that it failed to find the Linux partitions.
|
| |
|
|
|
|
|
| |
If you have a large number of addon modules, 96 may still be too low.
This value can be changed on boot-time by the 'maxloops=' boot parameter.
|
|
|
|
|
|
|
|
|
|
| |
Boot parameter "livemedia=" has been expanded;
Generic syntax for explicitly defining your live media:
livemedia=/dev/sdX
The syntax for pointing the initrd to an ISO image of Slackware Live Edition
instead of a partition or DVD media expands on the above:
livemedia=/dev/sdX:/path/to/slackwarelive.iso
Note: this functionality is yet untested ;-)
|
| |
|
|
|
|
|
|
|
| |
New boot option 'nga' (which stands for 'no glamor acceleration')
adds a configuration file to X.Org. This disables the (now default) glamor
acceleration which causes a X startup failure with the error:
"EGL_MESA_drm_image required; (EE) modeset(0): glamor initialization failed".
|
|
|
|
| |
X.Org in a QEMU VM will refuse to start if glamor is used for 2D acceleration.
|
|
|
|
| |
Was there from the beginning... glad someone noticed it, thanks SangDae.
|
| |
|
|
|
|
|
| |
If we mounted the media partition in the Live OS, an I/O error will
be the result when the user removes the boot media from the computer.
|
| |
|
|
|
|
|
|
| |
Also, make sure that we do not try and make any persistent writes when 'toram'
was specified as a boot parameter, since 'toram' means that the user intends
to remove the boot media afterwards.
|
|
|
|
|
|
| |
- fix detection of german (de) keyboard layout to configure Compose Key,
- actually use field #6 of the languages file (X Keyboard layout & variant)
when generating the grub and syslinux boot configuration files.
|
|
|
|
|
|
|
| |
Examples:
+ livemedia=08d500da-9538-435c-94fc-c97b1c96d1b1
+ livemedia=LIVESLAK
+ livemedia=/dev/sde1
|
|
|
|
|
|
|
| |
Based on feedback, use Scroll Lock instead of AltGr as the Compose Key.
Also, use 'de-latin1-nodeadkeys' instead of 'de-latin1' for console keyboard
layout, 'de_DE@euro' instead of 'de_DE.utf8' as language definition and
'nodeadkeys' as the X keyboard variant.
|
| |
|
|
|
|
|
|
|
|
| |
Any kernel modules mentioned here will be added to the modprobe blacklist.
This will help out people who need to blacklist the nouveau driver,
for instance if they have a too-new computer.
Syntax:
blacklist=mod1[,mod2[,...]]
|
|
|
|
| |
Only relevant if the user added the 'toram' boot option.
|
|
|
|
| |
This gets rid of quite some code duplication.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows the user to remove the bootable Live media afterwards, because
the complete OS will been copied to RAM and run from there when adding
the boot commandline parameter 'toram'.
This feature works nicely for the XFCE ISO since that one is fairly small.
Untested for the bigger ISOs; you need more patience while the squashfs
modules are being copied to RAM, and available RAM decreases a lot.
Realistically speaking, your computer would need 1 or 2 GB of RAM for
the XFCE variant, 2 or 4 GB RAM for the Mate variant, and 4 to 8 GB RAM
for the KDE4 and Plasma5 variants.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds an option to store persistent data in a container file instead of
a directory in the USB stick's Linux filesystem.
Theoretically, this would allow the Slackware Live files to be copied to
a VFAT partition on a stick without erasing it, as long as the stick is
made bootable and the Live kernel & initrd are added to the boot menu.
To create a USB stick from the Live ISO which uses a persistence file instead
of a persistence directory, run the 'iso2usb.sh' script with a new parameter:
-P|--persistfile Use a 'persistence' container file instead of
a directory (for use on FAT filesystem).
The following example creates a 750 MB LUKS-encrypted container file
'slhome.img' which will contain /home ; as well as a file '/persistence.img'
in the root of the USB's Linux partition which will be used to store the
Live OS' persistent data:
./iso2usb.sh -i slackware64-live-current.iso -o /dev/sdX -c 750M -P
NOTE:
The persistence container file will be created as a 'sparse' file which
starts as an empty file not using up any disk space, but is allowed to
grow dynamically to consume a maximum value of 90% of the free disk space
on the Linux partition of the USB stick.
|
|
|
|
|
|
| |
The /home would end up read-only if the "nop" parameter was passed
on the boot commandline in order to disable persistence for the session.
So, remount the media as writable earlier during init.
|