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.
Proposing a simple patch to /etc/rc.d/rc.mysqld to avoid terminating other mysql instances. This is particularly true when running akonadi which runs its own mysqld instance on user's account and is affected by 'killall mysqld' upon '/etc/rc.d/rc.mysqld stop'.
Pat, thank you for accepting this patch. That 'for second in $(seq 0 60)' was a nice catch, too.
On LUKS+LVM installation, when I generate initrd.gz with mkinitrd everything is fine. After I create LVM snapshot of root LV, I cannot boot into the system anymore. The reason is that dm-snapshot module is never included by mkinitrd script, so the root partition with active snapshot cannot be mounted on boot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.