Borsenkow Andrej <[EMAIL PROTECTED]> writes: [...]
> > it's devfsd which take care of this. It would be nice if it would also create > > the /dev/dvd link... [...] > no. Folks, you really have strange notion what exactly devfsd is :-) IMO devfsd should not be olddev-compatibility stuff only. We already have /dev/cdrom handled magically. Why not /dev/dvd? > > Pixel, just create link in /lib/dev-state at installation time. > > Anybody can just do > > ln -s cdroms/cdrom0 /dev/dvd > > At any time. What's wrong with it? if it's not a dvd, it's ugly. > > We also could enter it into devfsd.conf. I do not like it because if we > are going to do it this way we really must finally switch to devfsd > configuration *directory* That would be nice for modularity & local config (since modifying devfsd.conf means breaking upgrades of course) > where installer (or kudzu or harddrake ...) > would just put line > > REGISTER ^ide/host0/.../cd$ CFUNCTION GLOBAL mksymlink $devname dvd that would do, agreed (though i would still prefer it handled magically by devfsd) > > titi, you hack this in devfsd? > > > > No. It is abuse of devfsd. Everything can be done in user space easily. devfsd is userspace ;p > Let's add > > OPTIONAL_INCLUDE /etc/sysconfig/devfsd.d > > And let installer put file dvd with above contents there. And then we > could finally put symlink for mouse there and get rid of error messages > on bootup. And much more really ... for the mouse case, what about a dev-state that would only be copied, but never modified magically by devfsd?
