Joerg Schilling writes:
> >From [EMAIL PROTECTED] Thu Feb 11 21:51:13 1999
> >In the case I noticed recently, I think it was done correctly. Someone
> >upgraded the FORE ATM drivers on a system (the new drivers use
> >different /dev entries), booted with -r and the old device entries in
> >/dev were still around. This caused much confusion.
>
> >It may be a bug due to FORE not doing something right (like adding to
> >one of those scripts), but either way, it points to a bug/design flaw
> >in Solaris. Problems like this should not happen. Linux devfs doesn't
> >suffer from this problem.
>
> This definitely must be a FORE bug. They then seem not to provide a correct
> /etc/devlink.tab which is needed to make devlinks work properly.
> I know that there are other bugs in the FORE installation.
That may well be. My point is that I consider such a system
fragile. It also puts the same information in two places: in the
kernel and in the scripts. This is one of the things I dislike with
the existing Linux device number scheme: there are two separate
repositories of the same information, one in the kernel sources and
one in MAKEDEV (or /dev if you prefer). Things can get out of sync.
No, I don't consider Documentation/devices.txt to be the
repository. It may be *intended* that way, but it is not how it
works. The *real* repositories are in the kernel sources and the
source to MAKEDEV (or in /dev).
Linux devfs does away with this problem (and many more).
Regards,
Richard....
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
