You are not logged in.
Either this got introduced with the latest kernel upgrade, or I just happened to catch it now during the boot cycle. At the very end, I get the following error, also present in the /var/log/boot file:
Wed Mar 28 13:23:55 2012: ln: failed to create symbolic link `/dev/cdrom': File exists
Does anyone know which service/process tries to create a symbolic link for /dev/cdrom...?
To make matters more interesting - there is a /dev/cdrom lin, dated at the time of reboot, so something must have created it already. But it's slightly different than the links for /dev/dvd and /dev/cdrw:
[root@abc dev]# ls -l
total 0
...
lrwxrwxrwx 1 root root 3 Mar 28 13:23 cdrom -> sr0
lrwxrwxrwx 1 root root 8 Mar 28 13:23 cdrw -> /dev/sr0
...
lrwxrwxrwx 1 root root 8 Mar 28 13:23 dvd -> /dev/sr0
lrwxrwxrwx 1 root root 8 Mar 28 13:23 dvdrw -> /dev/sr0
Any ideas?
Last edited by twelveeighty (2012-03-30 17:09:13)
Offline
You probably have a symlink creation specified in /etc/rc.local. This is no longer needed for /dev/cdrom.
Burninate!
Offline
Yes! You are right. Now, this sounds so familiar. I vaguely remember doing this when I originally installed Arch on this laptop, but I must have done it as part of the "beginners guide" procedure. I guess this explains it:
https://wiki.archlinux.org/index.php?ti … did=168068
Now, I take it from this that I safely remove ALL the symlinks from my rc.local?
rc.local:
ln -s /dev/sr0 /dev/cdrom
ln -s /dev/sr0 /dev/cdrw
ln -s /dev/sr0 /dev/dvd
ln -s /dev/sr0 /dev/dvdrw
Offline
You can safely remove the "ln -s /dev/sr0 /dev/cdrom" line. The /dev/cdrom symlink is automatically created during boot now.
The symlinks for cdrw, dvd and dvdrw aren't however. So if you have a general use for those; you can safely leave them in there.
Burninate!
Offline