> However, let me summarize my lack of knowledge here so I don't get too
> far off track.
>
> 1. Don't mess with dev (don't create symlinks in it manually)
>
No quite. Once upon a time the only way to restore /dev state after reboot
(i.e. your own files, permissions etc) was to copy it over from some backing
store. It proved to lead to many problems. Now devfsd properly preserves and
restores those links and special files you create in /dev. So, it really
does not matter. For most people creating a symlink is much more easier.
What you should never do - is manually create any device name or symlink
that are managed by devfs(d). This includes any compatibility names like
/dev/hdc etc. They must just work. If they do not it means a bug in devfs,
devfsd or in the way they are used on your system.
But because the distinction is quite obscure for average user the best
advice is to simply do not touch it at all.
> 2. I THINK I use /etc/devfsd.conf to create the entries in /dev when
> the device has an event happen to it?. So what I should do to create
> the autochanger is go to /etc/devfsd.conf and put in something like the
> CD line to create a symlink. I should have done that for the tape, too
> but somehow it got created anyway. Is this correct - use
> /etc/devfsd.conf for creating /dev entries.
>
See above. If you absolutely need to do with devfsd.conf as exercise:
REGISTER ^scsi/host1/bus0/target1/lun0/generic$ CFUNCTION GLOBAL
mksymlink $devname auto_changer0
Replace numbers with your real numbers of course.
In your case it would have benefit of recreating autochanger on reboot,
which just proves my point - if it does not work there is a bug lurking
somewhere :)
-andrey
|