| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
The squashfs-tools are an essential package when using 'setup2hd',
the Slackware Live OS' harddisk installer.
The XFCE ISO does not contain setup2hd at all (it only gets added
to ISOs with a huge kernel) but if someone creates a custom Live OS
containing a huge kernel but based on the minimal XFCE variant,
this custom Live OS requires the presence of unsquashfs,
or else 'setup2hd' will fail.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
When changes need to be made to README.txt and its Wiki version at
http://docs.slackware.com/slackware:liveslak I want to be able to
diff the two easily.
|
|
|
|
|
| |
If the predefined console font (CONSFONT variable) was not found
on the system, the make_slackware_live.sh script would abort with an error.
|
|
|
|
|
|
|
|
|
|
|
| |
This requires functionality in grub which is currently not enabled
in Slackware's grub package.
If you want a 32-bit Live ISO that boots on UEFI computers, you need
to recompile Slackware's grub with the patch for grub.SlackBuild which
you can find in the ./patches subdirectory.
Then you need to set the variable "EFI32" to "YES" in the
'make_slackware_live.sh' script and (re-)generate your 32-bit ISO.
The resulting 32-bit Live ISO will be UEFI-bootable.
|
|
|
|
|
| |
Not that 32bit EFI support is anywhere useful... but some people
requested this.
|
|
|
|
|
|
|
|
|
| |
The 'make_slackware_live.sh' script now has two extra parameters:
-a arch
Specify machine architecture (default: 'x86_64').
Use i586 for a 32bit ISO, x86_64 for 64bit.
-z version
Specify the Slackware version (default: 'current').
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
After installation to harddisk using the 'setup2hd' script, this
marker file is a Live OS left over and will only cause confusion.
|
|
|
|
|
| |
The grep command used so far would find "vim-gvim" when searching for "vim"
because it did not try to match from the beginning of the string.
|
| |
|
|
|
|
| |
During setup, a custom keyboard mapping may have been selected.
|
|
|
|
| |
Thanks to SangDae YU for pointing it out.
|
|
|
|
| |
Was there from the beginning... glad someone noticed it, thanks SangDae.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The 'setup2hd' script is a modified version of 'setup' in the Slackware
installer, taken straight from the initrd.
The SOURCE selection has been removed since the script knows where to
find the Live media.
Except for the actual extraction of Slackware Live content to your
hard drive, the other hard disk installation steps are unmodified from
the stock Slackware installer.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The script was mixing relative and absolute paths which is confusing.
In the chroot, we do not have to work with relative paths as is the
case with some original Slackware scripts.
|
|
|
|
|
| |
No idea how to do this for grub2 though. The Slackware option in the EFI
boot menu "Detect/boot any installed operating system" doesn't work for me.
|
| |
|
| |
|
|
|
|
| |
It is a requirement to have the Slackware mirror available locally in advance.
|
| |
|
| |
|
| |
|