| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The file "0020-slackware_multilib-current-x86_64.sxz" (for Slackware64-current)
or "0020-slackware_multilib-14.2-x86_64.sxz" (for Slackware64 14.2) can be
extracted from the ISO afterwards and distributed separately and independently
from the Slackware Live ISOs.
If you want to add multilib to your persistent USB version of Slackware Live,
you just copy the above squashfs module into the /liveslak/addons/ directory
of the liveslak partition on the stick (this enables multilib by default).
or else copy it to /liveslak/optional/ if you want to enable multilib on boot
manually by adding a "load=multilib" boot parameter.
|
| |
|
|
|
|
| |
In 'make_slackware_live.conf' you can give that variable "LIVEUID" another
value than the default "live" if you want to create a Live Edition where
the Live user account is not called "live".
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
New parameter '-M' to the "make_slackware_live.sh" script will add
a squashfs module "0020-slackware_multilib-VERSION-ARCH.sxz" to the iso,
its contents based on the ./pkglists/multilib.* package repo definitions.
Only for the x86_64 architecture of course.
If you already have a USB Live, you can simply copy this module into the
directory "/liveslak/addons" to transform your pure 64bit Slackware Live
Edition into a multilib variant.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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).
|
| |
|
|
|
| |
You can define SMP32="YES" in the script or in its .conf file,
if you want your Live ISO to boot the 32bit SMP kernel instead.
|
| | |
|
| |
|
|
|
|
| |
The "dialout" group is required for working with 3G USB modems and
ppp connections. If the user wants to play UNIX games, then the "games"
group membership is needed. And "disk" group was added for good measure.
|
| |
|
|
|
|
|
|
| |
We need to maintain strict size requirements to keep the maximum size
of the XFCE ISO below 737.280.000 bytes (703 MB) so that it fits on CDROM.
You can always add optional/addons modules later if you create a USB Live
medium out of the ISO.
|
| | |
|
| |
|
|
|
|
| |
For some people, an ISO generated with xorriso instead of using
mkisofs/isohybrid is more compatible with other tools or hardware.
You need to install xorriso separately, it is not included with Slackware.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
In order to successfully generate a 32bit ISO of the small XFCE variant,
the variable SMP32 needs to be set to "NO" because the package for the SMP
kernel will not be added (due to size constraints).
Example commandline to achieve this:
SMP32=NO ./make_slackware_live.sh -d XFCE -a i586
|
| |
|
|
|
| |
The URLs mentioning 'taper' instead of 'bear' will still work because
the webserver on taper will do automatic redirection to bear.
|
| |
|
|
| |
I think this 'liveslak' product is in a pretty stable state now.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
Provided by GigglesUK, thanks.
|
| |
|
|
| |
And it is ready for a stable 1.0.0 version if no further bugs are uncovered.
|
| |
|
|
|
| |
See the README.txt for instructions on how to use the 'pxeserver' script
and what it can do for you.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
The resulting ISO will boot on real hardware as well as in virtualizers
like QEMU, VirtualBox and VMWare Player, despite the warning shown by
isohybrid that the ISO has more than 1024 cilynders and not all BIOSes
will be able to boot it.
Specifying sectors/heads to stay "standard compliant" will generate ISO
files that fail to boot in VirtualBox if the ISO filesize is larger
than roughly 1 GB, spitting out the error "VERR_NOT_SUPPORTED".
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
New parameter:
-O outfile => Full path to a custom filename for the ISO.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
A new file 'setup2hd.local' has been added to the liveslak sources.
If you do not touch that one, it will be copied to:
/usr/share/${LIVEMAIN}/setup2hd.$DISTRO.sample and serve as just that,
a sample script.
If on the other hand you rename the file to 'setup2hd.$DISTRO' before
generating your ISO image ($DISTRO being the name of your own distro,
like 'CINELIVE'), then this file will be installed in the ISO as
/usr/share/${LIVEMAIN}/setup2hd.$DISTRO and this will be sourced
by 'setup2hd' providing you a custom post-install customization hook
for your own Live distro.
Usage instructions are inside 'setup2hd.local'.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This shrinks the initrd back from 22 to 17 MB in size.
Also, a redundant copy of the initrd was removed from the
'0000-slackware_boot' module, reducing the ISO size with an
additional 17 MB.
These two modifications compensate for the increased size due to
addition of network modules and firmware (which are needed for
network boot).
Goal reached: the XFCE ISO still fits on CDROM media.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 the predefined console font (CONSFONT variable) was not found
on the system, the make_slackware_live.sh script would abort with an error.
|
Eric Hameleers