mirror of
git://slackware.nl/current.git
synced 2024-11-16 07:48:02 +01:00
b689ecb882
a/kernel-generic-6.1.22-x86_64-1.txz: Upgraded. a/kernel-huge-6.1.22-x86_64-1.txz: Upgraded. a/kernel-modules-6.1.22-x86_64-1.txz: Upgraded. a/mkinitrd-1.4.11-x86_64-32.txz: Rebuilt. Add /lib/firmware directory to _initrd-tree.tar.gz. Thanks to walecha. d/cmake-3.26.2-x86_64-1.txz: Upgraded. d/kernel-headers-6.1.22-x86-1.txz: Upgraded. d/llvm-16.0.0-x86_64-1.txz: Upgraded. Shared library .so-version bump. Thanks to Heinz Wiesinger for the assistance. Compiled with -DLLVM_BUILD_LLVM_DYLIB=ON -DLLVM_LINK_LLVM_DYLIB=ON -DCLANG_LINK_CLANG_DYLIB=ON. I think we'll get 16.0.1 next week if we need to make any adjustments. d/ruby-3.2.2-x86_64-1.txz: Upgraded. This update fixes security issues: ReDoS vulnerability in URI. ReDoS vulnerability in Time. For more information, see: https://www.ruby-lang.org/en/news/2023/03/28/redos-in-uri-cve-2023-28755/ https://www.ruby-lang.org/en/news/2023/03/30/redos-in-time-cve-2023-28756/ https://www.cve.org/CVERecord?id=CVE-2023-28755 https://www.cve.org/CVERecord?id=CVE-2023-28756 (* Security fix *) k/kernel-source-6.1.22-noarch-1.txz: Upgraded. kde/kdevelop-22.12.3-x86_64-2.txz: Rebuilt. Recompiled against llvm-16.0.0. l/openexr-3.1.7-x86_64-1.txz: Upgraded. l/qt5-5.15.8_20230325_c1a3e988-x86_64-1.txz: Upgraded. Compiled against llvm-16.0.0. l/spirv-llvm-translator-16.0.0-x86_64-1.txz: Upgraded. Compiled against llvm-16.0.0. Thanks to Heinz Wiesinger for finding the fix for -DBUILD_SHARED_LIBS=ON. n/pssh-2.3.5-x86_64-1.txz: Upgraded. n/samba-4.18.1-x86_64-1.txz: Upgraded. This update fixes security issues: An incomplete access check on dnsHostName allows authenticated but otherwise unprivileged users to delete this attribute from any object in the directory. The Samba AD DC administration tool, when operating against a remote LDAP server, will by default send new or reset passwords over a signed-only connection. The fix in 4.6.16, 4.7.9, 4.8.4 and 4.9.7 for CVE-2018-10919 Confidential attribute disclosure via LDAP filters was insufficient and an attacker may be able to obtain confidential BitLocker recovery keys from a Samba AD DC. Installations with such secrets in their Samba AD should assume they have been obtained and need replacing. For more information, see: https://www.samba.org/samba/security/CVE-2023-0225.html https://www.samba.org/samba/security/CVE-2023-0922.html https://www.samba.org/samba/security/CVE-2023-0614.html https://www.cve.org/CVERecord?id=CVE-2023-0225 https://www.cve.org/CVERecord?id=CVE-2023-0922 https://www.cve.org/CVERecord?id=CVE-2023-0614 (* Security fix *) x/mesa-23.0.1-x86_64-2.txz: Rebuilt. Recompiled against llvm-16.0.0 and spirv-llvm-translator-16.0.0. xap/seamonkey-2.53.16-x86_64-1.txz: Upgraded. This update contains security fixes and improvements. For more information, see: https://www.seamonkey-project.org/releases/seamonkey2.53.16 (* Security fix *) isolinux/initrd.img: Rebuilt. kernels/*: Upgraded. testing/packages/rust-1.68.2-x86_64-2.txz: Rebuilt. Use the bundled LLVM rather than the system LLVM. This version of Rust actually does compile with llvm-16.0.0, but since it bundles LLVM 15 let's let it use that for now. usb-and-pxe-installers/usbboot.img: Rebuilt. |
||
---|---|---|
.. | ||
sbootmgr | ||
f2.txt | ||
iso.sort | ||
isolinux.cfg | ||
message.txt | ||
README.TXT | ||
README_SPLIT.TXT | ||
setpkg |
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.