mirror of
git://slackware.nl/current.git
synced 2025-01-06 05:25:20 +01:00
ba4a3a1379
a/kernel-generic-5.10.5-x86_64-1.txz: Upgraded. a/kernel-huge-5.10.5-x86_64-1.txz: Upgraded. a/kernel-modules-5.10.5-x86_64-1.txz: Upgraded. d/kernel-headers-5.10.5-x86-1.txz: Upgraded. d/meson-0.56.1-x86_64-1.txz: Upgraded. k/kernel-source-5.10.5-noarch-1.txz: Upgraded. We'll turn off the silent stream feature as there's a known deadlock bug that remains in 5.10.5. Perhaps we'll restore it once that's patched... but we made it this far without the feature so I'll probably wait for a case to be made for it. Thanks to Petri Kaukasoina. Also build the intelfb module. This doesn't have anything to do with the lockups occurring on Intel systems, but we might as well provide the module. It remains blacklisted by default. FB_INTEL n -> m SND_HDA_INTEL_HDMI_SILENT_STREAM y -> n +FB_INTEL_DEBUG n +FB_INTEL_I2C y l/imagemagick-7.0.10_56-x86_64-1.txz: Upgraded. x/ibus-table-1.12.3-x86_64-1.txz: Upgraded. xap/mozilla-firefox-78.6.1esr-x86_64-1.txz: Upgraded. This release contains a security fix: A malicious peer could have modified a COOKIE-ECHO chunk in a SCTP packet in a way that potentially resulted in a use-after-free. We presume that with enough effort it could have been exploited to run arbitrary code. For more information, see: https://www.mozilla.org/en-US/firefox/78.6.1/releasenotes/ https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16044 (* Security fix *) isolinux/initrd.img: Rebuilt. kernels/*: Upgraded. usb-and-pxe-installers/usbboot.img: Rebuilt. |
||
---|---|---|
.. | ||
a | ||
ap | ||
d | ||
e | ||
f | ||
installer | ||
k | ||
kde | ||
l | ||
n | ||
t | ||
tcl | ||
x | ||
xap | ||
xfce | ||
y | ||
buildlist-from-changelog.sh | ||
make_world.sh | ||
README.TXT |
This is the source used for Slackware. To look for a particular bit of source (let's say for 'cp'), first you would look for the full path: fuzzy:~# which cp /bin/cp Then, you grep for the package it came from. Note that the leading '/' is removed: fuzzy:~# grep bin/cp /var/log/packages/* /var/log/packages/cpio-2.4.2.91-i386-1:bin/cpio /var/log/packages/fileutils-4.1-i386-2:bin/cp /var/log/packages/gcc-2.95.3-i386-2:usr/bin/cpp /var/log/packages/gnome-applets-1.4.0.5-i386-1:usr/bin/cpumemusage_applet From this, you can see that 'cp' came from the fileutils-4.1-i386-2 package. The source will be found in a corresponding subdirectory. In this case, that would be ./a/bin. Don't be fooled into thinking that the _bin.tar.gz in this directory is the package with the source code -- anything starting with '_' is just a framework package full of empty files with the correct permissions and ownerships for the completed package to use. Many of these packages now have scripts that untar, patch, and compile the source automatically. These are the 'SlackBuild' scripts. Moving back to the example above, you can figure out which package the bin/cp source came from by examining the SlackBuild script. Have fun! --- Patrick J. Volkerding volkerdi@slackware.com