| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
New parameter to the script:
-l|--lukshome <name> Custom path to the containerfile for your LUKS
encrypted /home (slhome by default).
Note: not only (just as with the persistence container) can you choose
a custom name for the the LUKS container file but you can also create it
in a subdirectory instead of in the filesystem root now.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
* iso2usb.sh: added '-r' parameter to refresh an existing USB Live stick
with data from a new Live ISO.
* boot: added 'nop=wipe' parameter which will cause all persistent data
(in the persistence directory or a persistent data container) to be
erased. This allows you to repair a case of corrupted persistent
data which can occur after you modified files that are part of a
squashfs module.
Note that this boot option will leave an encrypted /home un-touched!
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-r|--refresh =>
Refresh an existing Live USB stick with new ISO content.
The refresh option "-r" can be used when you have a Live USB stick and you
want to update the liveslak files with new versions on an ISO image file
which you downloaded/created.
The USB stick will not be formatted in this case, and user modifications
like LUKS-encrypted homedirectory or persistence data will not be touched.
The "system" squashfs modules will be replaced with the versions on the ISO
file and any squashfs module not present in the system/ directory of the ISO
will be deleted.
The "optional" and "addons" directories are treated a bit differently:
The files in there that you added yourself will not be deleted when
the content of these directories is refreshed with the content from the ISO
(unless of course your added files have the same name as one of the files
in the ISO).
The content of the /boot and /EFI directories will both be replaced with
whatever is on the ISO image.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
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.
|
| |
|
|
|
|
| |
It appears that other distros do not always contain "iso-info" which
is part of "libcdio". The "isoinfo" program ion the other hand,
which is part of "cdrtools" is more widely used.
|
| | |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
| |
Allows the user to start the SSH server, now that it is disabled by default.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
Default behaviour of makemod is to overwrite the destination squashfs module
without asking. When adding the '-i' switch to the 'makemod' command,
the script will ask explicitly whether it is allowed to overwrite an
existing file.
Also added is a '-h' switch which shows help on using the script.
Bugfix: add "-noappend" to the squashfs command in the script to avoid
adding new data to an existing squashfs module.
|
| |
|
|
| |
Provided by GigglesUK, thanks.
|
| | |
|
| | |
|
| |
|
|
| |
And it is ready for a stable 1.0.0 version if no further bugs are uncovered.
|
| | |
|
| |
|
|
| |
The number '14' used in the script could be any (unique) low-range number.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Packages added:
+ netkit-ftp
+ netkit-routed
|
Eric Hameleers