Kernel 2.6.11.10 destroying /dev

AxXium · 05-23-2005, 08:06 AM

What in the world is going on here?

After configuring, compiling & installing kernel 2.6.11.10

over half the contents of my /dev directory vanishes into thin air, including my second optical drive.

It just disappears.

What would cause that?

2.6.11.9 didn't do that.

keefaz · 05-23-2005, 08:10 AM

Did you configure your kernel from the 2.6.11.9 config file ?

acid_kewpie · 05-23-2005, 08:13 AM

we'd have to assume some cahnge in kernel option. did you build in udev support?

abisko00 · 05-23-2005, 08:23 AM

I think 2.6.11.10 requires a newer version of udev. I get some udev errors even on 2.6.11.7, but it still works.

AxXium · 05-23-2005, 08:38 AM

I did not configure my kernel from the 2.6.11.9 .config file.

I don't know if I included support for udev.

That's the scary part.

Would lack of support for udev done this?

How could I check to see if it was supported?

How can I fix it?

I don't care if I have to reinstall everything. I am in a learning phase right now and there is nothing important on the computer anyway. I'm just trying to learn as much as I can.

AxXium · 05-23-2005, 09:01 AM

You know what I didn't do?

I installed Slackware Current 05/16/2005.

I assumed that the latest udev version would be included.

Maybe it isn't. Maybe that's what happened. I was really carefull when configuring the kernel and I selected everything that was recommened. I use make xconfig so that I could see all of the recomendations. I bet there's an old udev in the slack current iso.

keefaz · 05-23-2005, 10:14 AM

May I suggest you to save the .config file after each compile
if you don't use the built-in .config feature ?

This way you just make config from the previous config file
when you upgrade the kernel, more fast, less errors

Croaker · 05-23-2005, 10:49 PM

I had the same problem too when compiling the 2.6.11.9 kernel. My cdrom (hdc) was not showing up at all. Looked in /dev and my cdrom sym link was pointing to hdd, my dvd drive. And my dvd sym link was pointing to hdd as well. I reset the links and permissions, but on my next boot, everything was reset. After doing that a couple of times, I removed udev from my system. Haven't had any problems since.

AxXium · 05-24-2005, 07:47 AM

Croaker,

Please explain how you reset the permissions. That's one of the things I don't know how to do.

shilo · 05-24-2005, 04:22 PM

This may be helpful.

http://www.linuxquestions.org/questi...13#post1453013

Croaker · 05-24-2005, 05:09 PM

What shilo has is one way of doing things. Me, personally, I just removed udev from my system by going to '/var/log/packages' and typing 'removepkg udev-whatever'. Then I went into /dev and removed the old sym links and created new ones pointing where I wanted. And I changed the group from root to cdrom for both of them. How you want to do it depends on personal preferences.

MMYoung · 05-24-2005, 10:10 PM

What Croaker has is one way of doing things. Me, personally, I just learned how to use udev from various sources on the 'net. Created my own udev rules, made the change that Shilo mentions in the /etc/udev/scripts/make_extra_nodes.sh script and now I have much more control over my system than the "willy-nilly" /dev of old. Udev is the future, devfs has already be obsoleted. Resistance is futile, prepare to be assimilated!!!

Seriously, udev ain't that hard to learn, if a hillbilly from Arkansas like me can learn it anybody can. Not saying the "old way" doesn't work, matter of fact I did EXACTLY as Croaker did initially, but I also knew that I might as well use udev so I just got busy and did my homework. After you "tinker" with it for a little while, it gets much easier.

Later,
MMYoung