| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Thanks to GigglesUK for pointing it out.
|
| | |
|
| | |
|
| |
|
|
| |
To accompany the release of Slackware 15.0 stable!
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The firewall will be configured and installed only when you use setup2hd
to install the Live OS to your hard drive.
The scripts are not particular to Slackware Live; you can easily copy
the resulting files /usr/sbin/myfwconfig, /etc/rc.d/rc.firewall
and /var/lib/pkgtools/setup/setup.firewall out of the installed system
and use them anywhere on a Slackware-compatible OS.
- The 'myfwconfig' script will ask a few simple questions and generate the
ipv4 and ipv6 configuration in /etc/firewall/.
- The 'rc.firewall' script will load/save its iptables/ip6tables
configuration from /etc/firewall/ files.
- The 'setup.firewall' script is a convenient way to call the firewall
configurator from pkgtools or during Slackware's installation to harddisk.
|
| | |
|
| | |
|
| |
|
|
| |
The non-SMP kernels refuse to start the init script in initramfs since 5.15.x
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Read the updates in the README for more background and guidance.
User notice:
As a one-time action the very first time you boot a Secure Boot enabled
liveslak ISO, you will have to enroll the liveslak certificate
(/EFI/BOOT/liveslak.der) with which the Slackware boot-up binaries
(grub and kernel) were signed into your computer's MOK (Machine Owner Key
database).
This enrollment request will show on-screen during initial boot,
just follow the prompts to 'enroll from disk'. Afterwards the computer
will reboot and from then on, your liveslak will boot without any
user intervention on your Secure Boot computer.
Note:
liveslak uses Fedora's initial boot loader (the 'shim') which
has been signed by Microsoft. In future we may get our own
signed shim for liveslak and/or Slackware, but don't hold your breath.
|
| |
|
|
|
| |
Goal is to keep the XFCE image below 700 MB (CDROM size) while adding
programs that are needed.
|
| |
|
|
|
| |
Micro version bump for the DAW Live ISO respin to address icu4c and llvm
library updates in -current,
|
| | |
|
| | |
|
| |
|
|
|
| |
Using rc.local to post-configure the kernel was nice,
but this solution is cleaner and less lines of code.
|
| |
|
|
|
| |
Micro version bump for the DAW Live ISO,
which will get a full pre-emptive kernel.
|
| |
|
|
|
|
| |
The old way was not wrong, until I added the possibility to liveslak
to use a package in ./testing . This part of the code needed an overhaul
as a result of that, and now it looks cleaner than before.
|
| |
|
|
|
| |
Note: this was enabled in kernel 5.14.15 in Slackware-current.
On older / non-preemptive kernels the above will do nothing.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Excerpt from RFC 8375 (https://tools.ietf.org/html/rfc8375):
Users and devices within a home network (hereafter referred to as
"homenet") require devices and services to be identified by names
that are unique within the boundaries of the homenet [RFC7368]. The
naming mechanism needs to function without configuration from the
user. While it may be possible for a name to be delegated by an ISP,
homenets must also function in the absence of such a delegation.
This document reserves the name 'home.arpa.' to serve as the default
name for this purpose, with a scope limited to each individual
homenet.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
We will catch the error anyway and invoke chpasswd with different syntax.
|
| | |
|
| |
|
|
|
|
|
|
| |
According to bug report, this is now needed on Slackware 14.2 when
generating a -current Live ISO. PAM is probably to blame:
>chpasswd: (user root) pam_chauthtok() failed, error:
>Authentication token manipulation error
>chpasswd: (line 1, user root) password not changed
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This uses two squashfs modules that are currently only found in the
LEAN and XFCE images: 'min' and 'noxbase'.
These two provide a functional console-only Slackware with a lot of useful
programs. It will connect to a DHCP server automatically and it also
contains the 'setup2hd' script to be able to install Slackware from a network
mirror.
And since the Console OS gets loaded into RAM, you can remove your USB stick
after booting and use that stick for other purposes.
Use-case:
- You have one computer with a network connection and one USB stick, and want
to create a persistent Slackware Live on USB.
- Download an ISO supporting 'Console OS' to the computer's hard drive, and
transfer the ISO to the USB stick using the computer's ISO imaging tools,
making the stick bootable but not persistent.
- Boot from the USB stick, select the "Console OS in RAM" option.
- After you logged into the Console Slackware, mount the computer's hard drive.
- Use the 'iso2usb.sh' script that comes with liveslak to extract the ISO
content to the USB stick, making it persistent. See the README.txt for
instructions.
-----------------------------------------------------------------------------
Implemented as an extension of the liveslak 'toram' boot parameter.
Adding 'toram=core' to the boot commandline will load circa 500 MB of squashfs
modules into RAM and boot into a sparse but functional console environment.
For supported Live variants (currently LEAN and XFCE) the script
'make_slackware_live.sh' will automatically add a menu item "Console OS in RAM"
to the Syslinux and Grub bootloaders, using this 'toram=core' parameter.
TODO: add this as an option to all liveslak variants. Not so trivial to do.
|
| | |
|
| |
|
|
|
| |
Implementing LuckyCyborg's proposal from this post: https://www.linuxquestions.org/questions/slackware-14/requests-for-current-14-2-15-0-a-4175620463/page432.html#post6206168
Let's see whether this works.
|
Eric Hameleers