SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Plus, I don't use LILO and I hate tinkering with a grub.cfg just to check it and make sure the initrd is included.
If you are using grub, you can fix the omission in your next boot without a rescue disk. (That's why I use grub on most of my machines, anyways.)
If you are using grub2, you can still fix the omission in your next boot without a rescue disk and you can use the 09_slackware_linux script that I've posted in the forum a few times to allow you to run grub-mkconfig to build the proper grub config for you.
I think that slackpkg could be improved to ask if you'd like to run the mkinitrd_command_generator and then ask if you'd like to edit lilo.conf prior to asking if you'd like to run lilo on a kernel change.
Use one of the provided generic kernels for daily use. Do not report
bugs until/unless you have reproduced them using one of the stock
generic kernels. You will need to create an initrd in order to boot
the generic kernels - see /boot/README.initrd for instructions.
The huge kernels are primarily intended as "installer" and "emergency"
kernels in case you forget to make an initrd.
Sigh - If only people would read the documentation,
Please consider updating /etc/rc.d/rc.pulseaudio in the following way:
Code:
--- rc.pulseaudio 2016-01-08 04:59:30.000000000 +0100
+++ /etc/rc.d/rc.pulseaudio 2016-08-16 01:07:53.301984531 +0200
@@ -14,10 +14,11 @@
pulse_start() {
if [ -x /usr/bin/pulseaudio ]; then
- echo "Starting system PulseAudio daemon: /usr/bin/pulseaudio --system --disallow-module-loading &"
+ echo "Starting system PulseAudio daemon: /usr/bin/pulseaudio --system"
rm -rf /var/lib/pulse
# Any errors/warnings will go to the log files:
- /usr/bin/pulseaudio --system --disallow-module-loading 1> /dev/null 2> /dev/null &
+ /usr/bin/pulseaudio --system --disable-shm --enable-memfd \
+ --disallow-module-loading --exit-idle-time=-1 --disallow-exit --daemonize
fi
}
I've always preferred using the software builtin daemoninzing method rather than '&'.
The few more flags make the daemon start without issuing warnings, so there's no reason to redirect stdin/stderr.
Use of memfd might need investigation, but it worked for me.
I also tried to use pulseaudio --kill in pulse_stop() function, but had no luck making it work.
I started looking at the source code, but then decided I have better things to do ;-)
As a side note, rc.pulseaudio stop seems to be not called anywhere in the shutdown scripts.
Is it deliberate or have I missed some update (-current -> -14.2)?
There's an issue in libdvdread.SlackBuild about documentation.
The slackbuild installs documentation files (ie. AUTHORS, ChangeLog,...) in /usr/doc/libdvdread-5.0.3 and shrink the file Changelog, if present, to save some space. However, the Makefile also installs these documentation files in /usr/share/doc/libdvdread by default :
Code:
$ ls /usr/doc/libdvdread*
/usr/doc/libdvdread:
AUTHORS COPYING ChangeLog NEWS README TODO
/usr/doc/libdvdread-5.0.3:
AUTHORS COPYING ChangeLog NEWS README TODO
Here is a patch to fix this :
Code:
--- libdvdread.SlackBuild.orig 2016-08-17 10:25:41.543233030 +0200
+++ libdvdread.SlackBuild 2016-08-17 10:25:41.543233030 +0200
@@ -74,6 +74,7 @@
./configure \
--prefix=/usr \
--libdir=/usr/lib${LIBDIRSUFFIX} \
+ --docdir=/usr/doc/$PKGNAM-$VERSION \
--sysconfdir=/etc \
--localstatedir=/var \
--disable-static \
@@ -83,11 +84,6 @@
make $NUMJOBS || make || exit 1
make install-strip DESTDIR=$PKG || exit 1
-mkdir -p $PKG/usr/doc/$PKGNAM-$VERSION
-cp -a \
- AUTHORS COPYING* NEWS README* TODO \
- $PKG/usr/doc/$PKGNAM-$VERSION
-
# If there's a ChangeLog, installing at least part of the recent history
# is useful, but don't let it get totally out of control:
if [ -r ChangeLog ]; then
--
Seb
Last edited by phenixia2003; 08-17-2016 at 04:45 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.