[I have been cleaning folder]
> > - there is someting strange with ide-scsi CDs; instead of creating
link
> to
> > /dev/scsi/... plain block device is created:
> >
> > filr-xr-xr-x 1 root root 33 ??? 1 1970 cdrom0 ->
> > ../ide/host0/bus1/target0/lun0/cd
> > brw-rw-rw- 1 root root 11, 0 ??? 1 1970 cdrom1
> >
> > I do not know if it may have some side-effect; in any case,
permisions
> from
> > pam_console are not applied here so you get world-readable device.
It
> may be
> > considered a problem. OTOH canonical path has correct permissions:
> >
> > {pts/1}% ll /dev/scsi/host0/bus0/target0/lun0/cd
> > brw-rw---- 1 bor cdwriter 11, 0 ??? 9 23:15
> > /dev/scsi/host0/bus0/target0/lun0/cd
> >
> > as tey should be. I have no idea who does it.
>
> booh :-(
It again the result of our "restoring of devfs state" in rc.sysinit.
Basically, when registering /dev/cdroms/* entry cdrom drivers check real
device name is registered. But it is *not* registered - it is tried, but
existing devfs entry for scsi/host0/bus0/target0/lun0/cd is found so
nothing gets registered. Contrary to the expectation (but
understandable), registering devfs entry from within a kernel is *not*
the same as doing mknod on devfs. So cdrom driver gives up and just
created file instead of link.
How many times have I said "restoring devfs state is evil Evil EVIL" :(
-andrej
