LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 10-13-2008, 03:36 PM   #1
hubabuba
Member
 
Registered: Jan 2002
Location: UK
Distribution: Slack 14.1
Posts: 193

Rep: Reputation: 30
udev issue


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
 
Old 10-13-2008, 03:46 PM   #2
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,379

Rep: Reputation: Disabled
(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

Last edited by Alien Bob; 10-13-2008 at 05:25 PM. Reason: rename /etc/rc.d/rc.udev.new into /etc/rc.d/rc.udev
 
Old 10-13-2008, 04:40 PM   #3
hubabuba
Member
 
Registered: Jan 2002
Location: UK
Distribution: Slack 14.1
Posts: 193

Original Poster
Rep: Reputation: 30
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.
 
Old 10-13-2008, 05:27 PM   #4
niels.horn
Senior Member
 
Registered: Mar 2007
Location: Rio de Janeiro - Brazil
Distribution: Slackware64-current
Posts: 1,004

Rep: Reputation: 89
- 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.
 
Old 10-13-2008, 05:27 PM   #5
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,379

Rep: Reputation: Disabled
Quote:
Originally Posted by hubabuba View Post
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
 
Old 10-13-2008, 05:27 PM   #6
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,297

Rep: Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722
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]

Last edited by T3slider; 10-13-2008 at 05:28 PM.
 
Old 10-13-2008, 05:27 PM   #7
tobyl
Member
 
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 743

Rep: Reputation: 51
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!
 
Old 10-13-2008, 05:46 PM   #8
hubabuba
Member
 
Registered: Jan 2002
Location: UK
Distribution: Slack 14.1
Posts: 193

Original Poster
Rep: Reputation: 30
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
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
current users - udev-128 - don't forget rc.udev.new! tobyl Slackware 3 10-08-2008 04:28 AM
A rather irritating udev issue Jykke Linux - Hardware 5 07-12-2007 05:15 PM
USB udev issue: yotux Slackware 8 04-11-2007 06:55 PM
udev issue tauro_kpo Linux - General 3 04-10-2007 11:46 PM
slackware-current, udev 0.96, and custom udev rules not working rignes Slackware 6 08-10-2006 04:43 AM


All times are GMT -5. The time now is 02:58 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration