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.
I have an empty /sys directory on my system. What's it for?
I tried the forum search and googled for it but did not find anything. (How can I tell Google to search for "/sys" without ignoring the slash?) There's also nothing about it in the FHS it seems.
I also have a "lost+found" directory in / and /home, both are empty, what exactly is their purpose?
Just wondering, not planning to delete them or anything. ;-)
If you have a /sys in / , as far as I know, its not needed. As for the lost&found directories, those are created after your system will perform a fsck on the partitions at bootup, etc.
Sysfs is intended to be a replacement for procfs. It's incomplete at the moment, but it was originally created for acpi so it should work with that. (I don't notice any difference, but it might be the limitations of my laptop).
/sys was probably created by a package in slackware-current. It's a mandatory compile in for the 2.6 kernels (i.e. there's no sysfs option in .config). So if your running 2.6, all you have to do is mount it. To fstab, add: "none /sys sysfs defaults 0 0"
Ah, ok, thanks for the info. I compiled some 2.6* kernels a while ago but returned to my 2.4.26 because of problems with 2.6, so it could also be a leftover from that.
/sys was probably created by a package in slackware-current
Running the 2.6 kernel will not create the directory. It was probably created by one of the new system packages. After that I think it's automatically mounted at boot, there's no need to add it to fstab.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.