slackware-current/isolinux
Patrick J Volkerding 05ec45c9c9 Thu Oct 26 19:55:16 UTC 2023
a/kernel-firmware-20231024_4ee0175-noarch-1.txz:  Upgraded.
a/kernel-generic-6.1.60-x86_64-1.txz:  Upgraded.
a/kernel-huge-6.1.60-x86_64-1.txz:  Upgraded.
a/kernel-modules-6.1.60-x86_64-1.txz:  Upgraded.
a/shadow-4.14.1-x86_64-1.txz:  Upgraded.
d/kernel-headers-6.1.60-x86-1.txz:  Upgraded.
k/kernel-source-6.1.60-noarch-1.txz:  Upgraded.
  Hey folks, if you've been following LQ you know I've talked before about
  dropping the huge kernel and moving the distribution to use only the generic
  kernel plus an initrd. After mulling this over for a few months, I think I
  was looking at the problem in the wrong way. First of all, it's clear that
  some Slackware users have been using the huge kernel all along, without an
  initrd, and are (to say the least) unhappy about the prospect of a new
  requirement to start using one. I've been recommending the generic kernel for
  some time, and a major reason is that we've been using the same set of kernel
  modules with two slightly different kernels. Because of this, there have
  always been a few (generally seldom used) kernel modules that won't load into
  the huge kernel. These are things that aren't built into the huge kernel, but
  because of a difference in some kernel module dependency, they won't load.
  The conclusion that I've come to here is that rather than drop the huge
  kernel, or slap a LOCALVERSION on it and provide a whole duplicate tree of
  kernel modules especially for the huge kernel, it would be better to make the
  generic kernel more huge, and minimize the differences between the two kernel
  configs.
  That's what I've done here.
  Shown below are the differences between the previous generic kernel config
  and the one shipping in this update. You'll notice that most of the popular
  filesystems are built in. At this point the main difference it that the huge
  kernel has a couple of dozen SCSI drivers built into it. The modules for those
  drivers won't load into the huge kernel, but they're fully built in so that
  doesn't matter. If you find any other modules that will not load into the huge
  kernel, please make a note about it on LQ and I'll see what can be done.
  So, tl;dr - what does this change mean?
  Unless your root device is on SCSI, if you were able to use the huge kernel
  without an initrd previously, you should now be able to use the generic
  kernel without an initrd. The kernel is a bit bigger, but we probably have
  enough RAM these days that it won't make a difference.
  Enjoy! :-)
  -CIFS_SMB_DIRECT n
   9P_FS m -> y
   9P_FSCACHE n -> y
   BTRFS_FS m -> y
   CIFS m -> y
   CRYPTO_CMAC m -> y
   CRYPTO_CRC32 m -> y
   CRYPTO_XXHASH m -> y
   CRYPTO_ZSTD m -> y
   EFIVAR_FS m -> y
   EXFAT_FS m -> y
   EXT2_FS m -> y
   EXT3_FS m -> y
   EXT4_FS m -> y
   F2FS_FS m -> y
   FAILOVER m -> y
   FAT_FS m -> y
   FSCACHE m -> y
   FS_ENCRYPTION_ALGS m -> y
   FS_MBCACHE m -> y
   HW_RANDOM_VIRTIO m -> y
   ISO9660_FS m -> y
   JBD2 m -> y
   JFS_FS m -> y
   LZ4HC_COMPRESS m -> y
   LZ4_COMPRESS m -> y
   MSDOS_FS m -> y
   NETFS_SUPPORT m -> y
   NET_9P m -> y
   NET_9P_FD m -> y
   NET_9P_VIRTIO m -> y
   NET_FAILOVER m -> y
   NFSD m -> y
   NLS_CODEPAGE_437 m -> y
   NTFS3_FS m -> y
   NTFS_FS m -> y
   PSTORE_LZ4_COMPRESS n -> m
   PSTORE_LZO_COMPRESS n -> m
   PSTORE_ZSTD_COMPRESS n -> y
   QFMT_V2 m -> y
   QUOTA_TREE m -> y
   REISERFS_FS m -> y
   RPCSEC_GSS_KRB5 m -> y
   SMBFS m -> y
   SQUASHFS m -> y
   UDF_FS m -> y
   VFAT_FS m -> y
   VIRTIO_BALLOON m -> y
   VIRTIO_BLK m -> y
   VIRTIO_CONSOLE m -> y
   VIRTIO_INPUT m -> y
   VIRTIO_MMIO m -> y
   VIRTIO_NET m -> y
   VIRTIO_PCI m -> y
   VIRTIO_PCI_LIB m -> y
   VIRTIO_PCI_LIB_LEGACY m -> y
   VIRTIO_PMEM m -> y
   XFS_FS m -> y
   ZONEFS_FS n -> m
   ZSTD_COMPRESS m -> y
  +NFS_FSCACHE y
  +PSTORE_LZ4_COMPRESS_DEFAULT n
  +PSTORE_LZO_COMPRESS_DEFAULT n
  +PSTORE_ZSTD_COMPRESS_DEFAULT n
kde/plasma-workspace-5.27.9.1-x86_64-1.txz:  Upgraded.
l/glib2-2.78.1-x86_64-1.txz:  Upgraded.
l/netpbm-11.04.03-x86_64-1.txz:  Upgraded.
l/newt-0.52.24-x86_64-1.txz:  Upgraded.
n/gpgme-1.23.0-x86_64-1.txz:  Upgraded.
n/p11-kit-0.25.1-x86_64-1.txz:  Upgraded.
n/php-8.2.12-x86_64-1.txz:  Upgraded.
  This is a bugfix release.
  For more information, see:
    https://www.php.net/ChangeLog-8.php#8.2.12
x/xorg-server-21.1.9-x86_64-1.txz:  Upgraded.
  This update fixes security issues:
  OOB write in XIChangeDeviceProperty/RRChangeOutputProperty.
  Use-after-free bug in DestroyWindow.
  For more information, see:
    https://lists.x.org/archives/xorg-announce/2023-October/003430.html
    https://www.cve.org/CVERecord?id=CVE-2023-5367
    https://www.cve.org/CVERecord?id=CVE-2023-5380
  (* Security fix *)
x/xorg-server-xephyr-21.1.9-x86_64-1.txz:  Upgraded.
x/xorg-server-xnest-21.1.9-x86_64-1.txz:  Upgraded.
x/xorg-server-xvfb-21.1.9-x86_64-1.txz:  Upgraded.
x/xorg-server-xwayland-23.2.2-x86_64-1.txz:  Upgraded.
  This update fixes a security issue:
  OOB write in XIChangeDeviceProperty/RRChangeOutputProperty.
  For more information, see:
    https://lists.x.org/archives/xorg-announce/2023-October/003430.html
    https://www.cve.org/CVERecord?id=CVE-2023-5367
  (* Security fix *)
xap/mozilla-thunderbird-115.4.1-x86_64-1.txz:  Upgraded.
  This release contains security fixes and improvements.
  For more information, see:
    https://www.mozilla.org/en-US/thunderbird/115.4.1/releasenotes/
    https://www.mozilla.org/en-US/security/advisories/mfsa2023-47/
    https://www.cve.org/CVERecord?id=CVE-2023-5721
    https://www.cve.org/CVERecord?id=CVE-2023-5732
    https://www.cve.org/CVERecord?id=CVE-2023-5724
    https://www.cve.org/CVERecord?id=CVE-2023-5725
    https://www.cve.org/CVERecord?id=CVE-2023-5726
    https://www.cve.org/CVERecord?id=CVE-2023-5727
    https://www.cve.org/CVERecord?id=CVE-2023-5728
    https://www.cve.org/CVERecord?id=CVE-2023-5730
  (* Security fix *)
xfce/thunar-4.18.8-x86_64-1.txz:  Upgraded.
isolinux/initrd.img:  Rebuilt.
kernels/*:  Upgraded.
usb-and-pxe-installers/usbboot.img:  Rebuilt.
2023-10-26 23:09:17 +02:00
..
sbootmgr Slackware 13.0 2018-05-31 22:41:17 +02:00
f2.txt Slackware 14.1 2018-05-31 22:57:36 +02:00
iso.sort Slackware 13.0 2018-05-31 22:41:17 +02:00
isolinux.cfg Slackware 14.1 2018-05-31 22:57:36 +02:00
message.txt Thu Oct 26 19:55:16 UTC 2023 2023-10-26 23:09:17 +02:00
README.TXT Wed Feb 2 22:22:22 UTC 2022 2022-02-04 00:29:06 +01:00
README_SPLIT.TXT Slackware 13.0 2018-05-31 22:41:17 +02:00
setpkg Mon Dec 7 21:49:58 UTC 2020 2020-12-08 08:59:51 +01:00

HOW TO MAKE A BOOTABLE SLACKWARE DVD ISO IMAGE

To make a bootable Slackware install DVD, get into the top level Slackware
directory (The one with ChangeLog.txt in it) and issue a command like this
to build the ISO image in /tmp:

xorriso -as mkisofs \
  -iso-level 3 \
  -full-iso9660-filenames \
  -R -J -A "Slackware Install" \
  -hide-rr-moved \
  -v -d -N \
  -eltorito-boot isolinux/isolinux.bin \
  -eltorito-catalog isolinux/boot.cat \
  -no-emul-boot -boot-load-size 4 -boot-info-table \
  -isohybrid-mbr /usr/share/syslinux/isohdpfx.bin \
  -eltorito-alt-boot \
  -e isolinux/efiboot.img \
  -no-emul-boot -isohybrid-gpt-basdat \
  -m 'source/' \
  -volid "SlackDVD" \
  -output /tmp/slackware-dvd.iso \
  .

On my system, here's the command I'd use to burn the resulting DVD ISO:

growisofs -speed=2 -dvd-compat -Z /dev/sr0=slackware-dvd.iso

If your burner is not /dev/sr0, replace the device with the one your
system uses.

I find discs burned at 2x are more reliable than ones burned at higher
speeds, but you may see completely different results depending on media
and burner type.  The -dvd-compat option is also used so that a complete
lead-out is written to the media for maximum compatibility.

To write the ISO image to a USB stick use a command such as this (replace
/dev/sdX with the device name for your USB stick):

dd if=/tmp/slackware-dvd.iso of=/dev/sdX bs=1M

Or, you can burn directly from the Slackware tree to a DVD(-/+)R(W):

xorriso -as mkisofs \
  -iso-level 3 \
  -full-iso9660-filenames \
  -R -J -A "Slackware Install" \
  -hide-rr-moved \
  -v -d -N \
  -eltorito-boot isolinux/isolinux.bin \
  -eltorito-catalog isolinux/boot.cat \
  -no-emul-boot -boot-load-size 4 -boot-info-table \
  -isohybrid-mbr /usr/share/syslinux/isohdpfx.bin \
  -eltorito-alt-boot \
  -e isolinux/efiboot.img \
  -no-emul-boot -isohybrid-gpt-basdat \
  -m 'source/' \
  -volid "SlackDVD" \
  -output - \
  . \
  | xorrecord -v dev=/dev/sr0 speed=2 fs=8m blank=as_needed -

Note that the source code directory will not be included on these DVD
images in order to keep them under the limit for a single-layer disc.
If you are using double layer DVD media and want to burn the complete
tree to your disc, remove the -m option line from the command.


HOW TO MAKE A SET OF BOOTABLE / INSTALLABLE CDROMS

This is a little bit more tricky.  Step one will be to split the tree into
portions that will fit on the media that you plan to burn to.  The first
disc must contain these directories:

/isolinux/
/kernels/
/slackware/

You'll need to make other /slackware/ directories on discs 2, 3, and maybe
more, moving some of the disc series from disc 1 to other discs to make
things fit.  It is also possible to split a series to make more efficient
use of the CD media.  See the README_SPLIT.TXT example and instructional
file in this directory for details about how to set that up.

The rest of the splitting up of discs is left as an exercise for the reader.

To make the first (bootable) ISO, a command like this is used within the
directory where the disc tree is.  Let's say the directory is 'd1' and you
wish to output the ISO image in /tmp:

cd d1
xorriso -as mkisofs \
  -iso-level 3 \
  -full-iso9660-filenames \
  -R -J -A "Slackware Install 1" \
  -hide-rr-moved \
  -v -d -N \
  -eltorito-boot isolinux/isolinux.bin \
  -eltorito-catalog isolinux/boot.cat \
  -no-emul-boot -boot-load-size 4 -boot-info-table \
  -isohybrid-mbr /usr/share/syslinux/isohdpfx.bin \
  -eltorito-alt-boot \
  -e isolinux/efiboot.img \
  -no-emul-boot -isohybrid-gpt-basdat \
  -volid "SlackCD1" \
  -output /tmp/slackware-install-1.iso \
  .

Making a non-bootable disc is similar.  Just omit a few options:

cd d2
xorriso -as mkisofs \
  -iso-level 3 \
  -full-iso9660-filenames \
  -R -J -A "Slackware Install 2" \
  -hide-rr-moved \
  -v -d -N \
  -volid "SlackCD2" \
  -output /tmp/slackware-install-2.iso \
  .

To burn an ISO image to CD-R(W), the cdrecord command is used.  For complete
instructions, see the man page ('man cdrecord').  On my own machine where
the burner is /dev/cdrw, disc one would be burned with the following command:

cat /tmp/slackware-install-1.iso | cdrecord -v dev=/dev/cdrw speed=10 fs=8m -tao -eject -data -

As before, it's possible to burn from the disc trees without the intermediate
step of creating iso images by piping the output directly to cdrecord:

cd d1
xorriso -as mkisofs \
  -iso-level 3 \
  -full-iso9660-filenames \
  -R -J -A "Slackware Install 1" \
  -hide-rr-moved \
  -v -d -N \
  -eltorito-boot isolinux/isolinux.bin \
  -eltorito-catalog isolinux/boot.cat \
  -no-emul-boot -boot-load-size 4 -boot-info-table \
  -isohybrid-mbr /usr/share/syslinux/isohdpfx.bin \
  -eltorito-alt-boot \
  -e isolinux/efiboot.img \
  -no-emul-boot -isohybrid-gpt-basdat \
  -volid "SlackCD1" \
  -output - \
  . | cdrecord -v dev=/dev/cdrw speed=10 fs=8m -tao -eject -data -


-----

NOTES:
  The isolinux/isolinux.boot file will be created on the disc;  it's not
  supposed to be in the source tree.  I mention this only because so many
  people report the "missing" isolinux/isolinux.boot file as a bug.

  The "-boot-load-size 4" is actually not large enough to hold the isolinux
  boot loader, but many BIOS implementations are broken and will *only*
  accept "4".  Evidently many newer, more correct BIOS implementations
  expect this and will continue to load the boot loader file until the
  EOF is reached.  Anyway, previous uses of larger values were correct, but
  led to the Slackware ISO not booting on some machines which contained
  broken BIOS implementations.  It is my hope that by using the incorrect
  value of 4 sectors that the ISO will boot on most (if not all) machines
  that are supposed to be able to boot from an ISO image.

  I don't know how to create a bootable Slackware ISO on operating systems
  other than Linux, but it should be easy to burn the Linux-created ISO with
  most CD burning software on any operating system.

Enjoy!

 -P.