GentooThis forum is for the discussion of Gentoo 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'm having some trouble with my fresh Gentoo install. I'm running Gnome, kernel 2.6.30 on a Core i7. Everything's pretty standard and most of it works fine. However, the Gnome automount doesn't work. I use USB drives constantly and it's really a hassle.
The problem is that I've been using Fedora for a few years, so I'm not used to setting these things up myself. The kernel is compiled properly according to http://www.gentoo.org/doc/en/udev-guide.xml and udev is installed. However, I noticed that udev wasn't in my default runlevel, so when I tried to run "/etc/init.d/udev start" I got this:
* The udev init-script is written for baselayout-2!
* Please do not use it with baselayout-1!.
So I started wondering if that had something to do with it. I could be completely wrong. Anyone got some ideas to nudge me in the right direction?
I haven't ever see this problem, but what the error tells you is that baselayout is too old, for whatever reason. You could update it, but I'd rather try to discover why the heck is udev pulling an unstable dependency. What version of udev are you using?
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] sys-fs/udev-141 USE="(-selinux)" 0 kB
Total: 1 package (1 reinstall), Size of downloads: 0 kB
Also, everything is up-to-date as of last night. I did an emerge --sync and updated everything to the latest version.
Also, everything is up-to-date as of last night. I did an emerge --sync and updated everything to the latest version.
Yes, and I see you are in stable, so there's either strange here or I am missing something simple. Either way, udev is the default way to manage everything now, so you shouldn't really need to do anything special to set it up. devfs is deprecated so unless you are managing your /dev statically yourself you are into udev as far as I understand it.
A simple way to tell if you are running it is this:
Code:
ps -A|grep udevd
If the output is not empty, then it's running and you shouldn't need to worry about anything else. Anything having to do with gnome probably is either related to hal or gnome-vfs, which is the gnome sus--system which handles all the mounting and that stuff.
I am not sure, I am not a gnome user so I can't really speak from experience or test things for you to try.
You can try recompiling gnome-vfs. I also remember that somewhere in gnome you could find a place to configure the gnome-vfs stuff, but it's been years since I have that window in front of my face.
All I can tell you is that I see similar complains from time to time from gnome users, there seem to be something wrong with gnome (I can't tell you if only in Gentoo or if it's a common thing). On a quick search I found this one, but I am sure that you can find many more.
A possible cause could be that some package broke when updating some other, like hal or udev.
As a rule of thumb, to preserve the system health, always run "revdep-rebuild" after updating anything. If those three commands are everything you ran, it's very probable that it was the revdep-rebuild which fixed your problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.