1 |
On Wed, Jan 12, 2011 at 10:57 AM, Michael Sullivan <msulli1355@×××××.com> wrote: |
2 |
> On Wed, 2011-01-12 at 10:28 -0600, Paul Hartman wrote: |
3 |
>> On Wed, Jan 12, 2011 at 10:11 AM, Michael Sullivan <msulli1355@×××××.com> wrote: |
4 |
>> > Why is it not being mapped correctly? Is the rule above not correct? |
5 |
>> > I've tried to read tutorials about writing udev rules, but the example |
6 |
>> > rules in the tutorials look nothing like the above rules, and I didn't |
7 |
>> > write those. I think they were created when udev was installed... |
8 |
>> |
9 |
>> I guess you don't really have 6 optical drives installed? :) |
10 |
>> |
11 |
>> Some of those have -ide- in the device name, did you change form IDE |
12 |
>> to ATA kernel driver at some point (like most everyone else did)? |
13 |
>> Maybe that's why. New entries are generated for drives that don't |
14 |
>> match existing rules, which is probably why you see your SOHC-5236K |
15 |
>> down at cdrom5 as well... |
16 |
>> |
17 |
>> If you delete the file and reboot, it'll create a new one based on |
18 |
>> your currently-installed hardware config. Hopefully that'll solve it |
19 |
>> or at least clean up that file to the point where you can manage the |
20 |
>> changes more easily. |
21 |
>> |
22 |
> |
23 |
> I deleted /etc/udev/rules.d/70-persistent-cd.rules and rebooted the |
24 |
> system. The file is still gone, and still no /dev/cdrom: |
25 |
> camille ~ # ls /etc/udev/rules.d/ |
26 |
> 10-zaptel.rules 70-bluetooth.rules 70-libsane.rules |
27 |
> 90-hal.rules hsf.rules |
28 |
> 30-svgalib.rules 70-libgphoto2.rules 70-persistent-net.rules |
29 |
> 99-btnx.rules |
30 |
> camille ~ # ls /dev/cdrom* |
31 |
> ls: cannot access /dev/cdrom*: No such file or directory |
32 |
> |
33 |
> |
34 |
> What should I do now? |
35 |
|
36 |
I saw from your other post that you're using an old kernel, maybe |
37 |
you're using an old udev too. I'm using 164-r1 and |
38 |
70-persistent-cd.rules is auto-generated by this rule: |
39 |
|
40 |
/lib/udev/rules.d/75-cd-aliases-generator.rules |
41 |
|
42 |
which really just runs /lib/udev/write_cd_rules script, you could also |
43 |
try to run manually if that exists in your system. |