udev issue

hubabuba · 10-13-2008, 03:36 PM

Hi there,

I've installed slack 12.1, downloaded, installed and recompile 2.6.24.7-smp kernel from slackware-current. I also removed udev-128 and installed udev-130.

Now I get the following messages when linux boots:

Quote:

...
cp: cannot remove `/dev/X0R': Read-only file system
cp: cannot remove `/dev/core': Read-only file system
cp: cannot remove `/dev/fd': Read-only file system
cp: cannot remove `/dev/initctl': Read-only file system
cp: cannot remove `/dev/null': Read-only file system
cp: cannot remove `/dev/ppp': Read-only file system
cp: preserving times for '/dev/shm': Read-only file system
cp: cannot remove `/dev/stderr': Read-only file system
cp: cannot remove `/dev/stdin': Read-only file system
cp: cannot remove `/dev/stdout': Read-only file system
cp: cannot remove `/devzero': Read-only file system
Starting udevd: /sbin/udevd --daemon
mkdir: cannot create directory '/dev/.udev/queue': Read-only file system
Triggering udev events: /sbin/udevtrigger
/etc/rc.d/rc.udev: line 95: /sbin/udevtrigger: No such file or directory
...

I tried seaching, but could not find anything relevant.

Do you why I get the messages and how to fix it?

Thanks

Alien Bob · 10-13-2008, 03:46 PM

(1) do not install random stuff from slackware-current on top of a stable release.

(2) if upgrading a Slackware package always look for files that get installed with the .new extension (especially packages that install files in /etc/). Your UDEV is broken because you forgot to rename /etc/rc.d/rc.udev.new into /etc/rc.d/rc.udev ..

Also good to repeat again - slackware-current is DEVELOPMENT stuff. If you want to run slackware-current we assume you are capable of repairing your computer when Slackware breaks it. If you are not up to that, stick to a Slackware stable release like 12.1 and use the patches that are released regularly to keep your system in proper condition.

Not meant to be harsh here - just hope you and others realize the difference between a development snapshot and a stable release.

Eric

hubabuba · 10-13-2008, 04:40 PM

Ok, thanks.

Quote:

you forgot to rename /etc/rc.d/rc.udev into /etc/rc.d/rc.udev ..

So, I should call it /etc/rc/.d/rc.udev .. ? I don't understand.

niels.horn · 10-13-2008, 05:27 PM

- Fire up your favorite live-CD (like the Slackware DVD)
- mount your partition with Slackware installed
- cd to (your-mount-point)/etc/rc.d
and type:

Code:

mv rc.udev{,.orig} && mv rc.udev{.new,}

After this your Slackware should boot again.

Alien Bob · 10-13-2008, 05:27 PM

Quote:

Originally Posted by hubabuba

Ok, thanks.

So, I should call it /etc/rc/.d/rc.udev .. ? I don't understand.

Mea culpa - I made a typo there. I meant to say:

You should rename /etc/rc.d/rc.udev.new into /etc/rc.d/rc.udev (which means, overwrite the old file with the content of the .new file).

Eric

T3slider · 10-13-2008, 05:27 PM

Rename /etc/rc.d/rc.udev.new to /etc/rc.d/rc.udev

The following command as root should do the trick:

Code:

# mv /etc/rc.d/rc.udev.new /etc/rc.d/rc.udev

See this thread and this thread for more information. A simple search of the forums would have given you the answer -- also, that first linked thread is on the first page of the forums (or maybe the second page if I've set the number of threads displayed on each page to be higher).

[edit]Wow, a flurry of posts, ending with mine -- all at the same time. Very nice.[/edit]

tobyl · 10-13-2008, 05:27 PM

read it like this

you forgot to rename /etc/rc.d/rc.udev.new into /etc/rc.d/rc.udev

tobyl

edit: oops two posts before my reply!

hubabuba · 10-13-2008, 05:46 PM

I have gone back to 2.6.24.5-smp from slack12.1. Also, installed udev 128 from slack12.1.
Now I get the following message just scrolling at boot before eventually getting to the login prompt.

Quote:

udevd[1037]: delete_path: rmdir(/dev/.udev) failed: Read-only file system