SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
All of the links in /run/udev/watch are broken. I ran a script that changes each link to point to the correct file in /run/udev/data. I haven't a clue whether or not that needs to work or what it does. With udev absorped into systemd, all bets are off.
(That was a one-time temporary kludge. I stumbled up that while looking for something else.)
The folder /run/udev/watch contains links to each file in /run/udev/data as if they were in the same directory. If initramfs doesn't copy those to /run/udev/data, I must have a broken initramfs. Thing is, initramfs is a fedora/redhat nom de guerre; slackware uses initrd. It is my understanding that their contents are different. /boot/initrd-tree is somewhat different than lsinitramfs last time I looked (init is a link to /usr/lib/systemd/systemd). Initrd does mount /proc /sys /run and /dev, but leaves populating those to udev. I guess I need to fix a udev.d/rules file in /etc to find out why udev leaves /run/udev/watch in situ with no links in /run/udev/data.
Thanks for your help, bartgymnast!
Obquote: "I'm an idiot, but I'm ok." -apologies to Colonel Torvalds.
[Now if I can just figure out why Thunar segfaults with error 4....]
What? Me worry? I know /var/run and/or /run is a tempfs, but it's the principal of the thing. An entire directory filled with nothing but broken links? It's just the 'b' data. The data files contain two numbers, one is the name of the broken link and the other is a hash. They used to pay me a lot of money to fret such minutia, but now, it's just another junior programmer without a B.S. or M.S. in Computer Science or Computer Systems Engineering. I worry over the morning cuppa whether to go fly fishing or go to the stadium to watch a ball game. ;-)
(Things like rc.udev deleting /dev/shm with a note that it will put it back later, only to put back /dev/pts and forget about /dev/shm. XFCE won't even make a splash page without it. Time for my nap.)