| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- use $DIALOG instead of calling dialog; hopefully we can use Xdialog
at some time
- warn user if terminal is too small to display fdisk/gdisk interfaces
- improve installation time of squashfs modules to harddisk with a factor 6,
by using a different way to show progress
- tweak dialogs so that they show less empty space
- if possible, set sane default selections in menu's to make the installation
process smoother
- fix many small bugs in user account creation, password dialog, user config
extraction, removal of redundant configuration questions etc
|
| |
|
|
|
|
|
|
|
| |
DAW configuration is now properly copied
Extracting the Live OS to hard disk is roughly 10 times faster now,
after abandoning the fancy progress bar and just showing the rsync status.
Use an enhanced Slackware SeTpasswd to add a non-root user and set
the root password.
Various syntax and logic errors removed.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The setup2hd script is a modified Slackware installer. For liveslak I had
originally removed all the usual SOURCE selections and only allowed for
the installation of the Live OS to harddisk.
However, requests were sent to also support a regular installation
of Slackware using the Live ISO. That is why I have now re-added all the
Slackware network install choices (via NFS, HTTP, FTP or Samba mirror).
I still left out the Slackware installation using local media;
the Live ISO does not contain regular Slackware packages so that
would not make sense.
|
| |
|
|
|
|
|
|
|
| |
This affects:
- pxeserver
- setup2hd
Both have been renamed with extension '.tpl' as indication that they are
templates. The 'make_slackware_live.sh' script performs a series of
substitutions on them to produce the actual scripts inside 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'.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
| |
After installation to harddisk using the 'setup2hd' script, this
marker file is a Live OS left over and will only cause confusion.
|
| |
|
|
| |
During setup, a custom keyboard mapping may have been selected.
|
| | |
|
|
|
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.
|
Eric Hameleers