SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a Sony DVD-RW which used to show up as /dev/s[rg]? (ie /dev/sr0 and /dev/sg0). I don't use it all that often anymore, and haven't noticed that in one of my -current upgrades towards 10.2 it has most likely become broken.
My /etc/udev/rules.d/10-local.rules is as follows:
This works great for the Memory Stick and Palm Treo, but for the DVD-rom it doesn't create the symlink. I've read the "udev howto" and used the varios udev tools to get the SYSFS information used above, but I still have two problems:
1. I would like the alias (/dev/cdrom->/dev/s[rg]?) to be created, and the fact that it isn't is a symptom that something else is wrong
2. k3b no longer recognizes/finds any DVD players, even though I've used it to burn multiple CDs and DVDs before (although that's a couple of months ago)
I have also tried to run this as root, without any further additional success.
I had a similar problem, ie my own udev rule for my DVD-R and DVD-ROM, and neither was created by udev. My solution was to comment out my custom udev rules and just let the make_extra_nodes.sh script create them for me. In the past this script never created the proper symlinks, which is the reason for my own udev rules, but now it seems to work perfectly.
I had the problem with zenwalk, the link to the cd writer/dvd was not added. For the first time, /dev/hdc didn't exist!
- I appended udev option to the kernel boot options.
- I edited /etc/fstab and changed /dev/cdrom to /dev/hdd and added a reference to my cd writer /dev/hdc.
- I rebooted, the links are created, hdc was now in the /dev directory and the symlinks to dvd and cdrom were there.
I didn't mess a lot with udev configuration and the extra nodes script. It wasn't working for me anyway. sg0 means you are using scsi emulation i think and it is not required for kernel 2.6.X.
How do you make the "make_extra_nodes.sh" script run in 10.2 ?
As for the SCSI driver, my DVD-RW is a SCSI-system with a USB interface, and thus it will not function without SCSI support. It is the same thing under Windows XP, and according to Sony (who make the most horrible, awful software interfaces on this planet!), there's no way around SCSI on this one.
It would be interesting to find out the exact source of my problem though, as my custom udev rule is clearly being used - it sets the correct group and permissions, but for some reason does NOT create the symlink...
I know it sounds like I'd like to eat the cake and still have it, but one of the reasons why I run Slackware is because I like to know exactly what happens on my system and why.
Originally posted by Yalla-One Thanks for the answers guys!
How do you make the "make_extra_nodes.sh" script run in 10.2 ?
Nothing, it runs automatically. If you have a rule that "conflicts" with the "rules" set up in it, there can be problems. "Theoretcially" udev should take your local rules and apply them first, if you put your rules in a file named 10-local.rules in /etc/udev/rules.d, and should ignore rules that apply to that device. The make_extra_nodes.sh, however, has a section that applies to CD/DVD drives and I it "conflicted" with my local rules.
Originally posted by Yalla-One As for the SCSI driver, my DVD-RW is a SCSI-system with a USB interface, and thus it will not function without SCSI support. It is the same thing under Windows XP, and according to Sony (who make the most horrible, awful software interfaces on this planet!), there's no way around SCSI on this one.
USB drives should ALWAYS be set up as SCSI devices, that's how it is supposed to work. Unless you have that horrid UB *thing* set up in the kernel and then they probably wouldn't work at all. They would be recognized as ubx rather than sdx.
Originally posted by Yalla-One It would be interesting to find out the exact source of my problem though, as my custom udev rule is clearly being used - it sets the correct group and permissions, but for some reason does NOT create the symlink...
The make_extra_nodes.sh script also sets group and permissions the same as what your local rule sets them. That's why I suggested you comment out your local rules to see what happens.
Originally posted by Yalla-One I know it sounds like I'd like to eat the cake and still have it, but one of the reasons why I run Slackware is because I like to know exactly what happens on my system and why.
Nope, sounds like to me you're the typical "Slacker" . Take a look at the /etc/udev/scripts/make_extra_nodes.sh script and you can get a better understanding of what it is doing in regards to not only you CD devices but LOTS of other stuff too.
I have removed my own rule from 10-local.rules, and when I run udevstart manually, it creates the /dev/cdrom -> /dev/sg0 and /dev/cdrom0 -> /dev/sg0 symlinks. However, when I reboot, these symlinks are not created and thus it does not work..
I find this weird to say the least, as according to /etc/rc.d/rc.udev, udevstart is exactly what's run when the system boots. Is this perhaps caused by some kind of race condition, or is it (more likely) yet a configuration error on my part?
Originally posted by Yalla-One I have removed my own rule from 10-local.rules, and when I run udevstart manually, it creates the /dev/cdrom -> /dev/sg0 and /dev/cdrom0 -> /dev/sg0 symlinks. However, when I reboot, these symlinks are not created and thus it does not work..
Is /etc/rc.d/rc.udev executable? If it isn't then it won't start when you reboot. Check the file settings by using ls:
Make sure that the -rwxr-xr-x is EXACTLY as it is above. If the output is different, then use the chmod command to set the rc.udev script to execute at startup. You do this from a terminal, or from the command line, logged in as root:
chmod +x /etc/rc.d/rc.udev
Now when you reboot udev will run and all should be "right with the world" again.
rc.udev is executable - if not I wouldn't have had the other devices either, and it wouldn't have been running my custom 10-local.rules.
So while rc.udev is starting just fine, the make_extra_nodes.sh is either not running, or not _functioning_ when I boot. I have no trouble accessing the CD through /dev/sr0, but it's annoying that it won't auto-create the cdrom alias...