mirror of
git://slackware.nl/current.git
synced 2025-01-17 18:12:36 +01:00
a5f767fffe
a/sysvinit-scripts-15.1-noarch-3.txz: Rebuilt.
rc.6: support an optional rc.firewall_shutdown script. Most firewall scripts
don't need a formal shutdown, but in some cases it can be useful. If your
rc.firewall script supports a stop parameter, the shutdown script should just
contain "/etc/rc.d/rc.firewall stop", or rc.firewall_shutdown could also be
a symlink to the rc.firewall script in that case. But how the script works
is (like the rc.firewall script support) completely up to the admin.
Thanks to metaed for the suggestion.
Please note that contrary to the request, I placed this *after* the network
is shut down to avoid removing firewall protection while the interfaces are
still active. Whether it'll work in this place for metaed's (or anyone
else's) needs, I'm not sure. It's a start. Feel free to weigh in on the LQ
thread if you have any ideas for improvement, but the goal here is to keep
this support as simple and flexible as possible.
d/nasm-2.16-x86_64-1.txz: Upgraded.
d/parallel-20221222-noarch-1.txz: Upgraded.
n/bind-9.18.10-x86_64-1.txz: Upgraded.
n/curl-7.87.0-x86_64-1.txz: Upgraded.
xap/mozilla-thunderbird-102.6.1-x86_64-1.txz: Upgraded.
This release contains a security fix and improvements.
For more information, see:
https://www.mozilla.org/en-US/thunderbird/102.6.1/releasenotes/
https://www.mozilla.org/en-US/security/advisories/mfsa2022-54/
https://www.cve.org/CVERecord?id=CVE-2022-46874
(* Security fix *)
xfce/xfce4-screenshooter-1.10.0-x86_64-1.txz: Upgraded.
|
||
|---|---|---|
| .. | ||
| 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, and ^ and $ mark the beginning and end of the pattern to match: fuzzy:~# grep ^bin/cp$ /var/lib/pkgtools/packages/* /var/lib/pkgtools/packages/coreutils-9.0-x86_64-3:bin/cp From this, you can see that 'cp' came from the coreutils-9.0-x86_64-3 package. The source will be found in a corresponding subdirectory. In this case, that would be ./a/coreutils/. All of these packages have scripts that extract, patch, and compile the source automatically. These are the 'SlackBuild' scripts. Have fun! --- Patrick J. Volkerding volkerdi@slackware.com