Roman Zippel writes:
> Hi,
>
> On Thu, 6 Dec 2001, Richard Gooch wrote:
>
> > Two possibilities:
> >
> > - the module is trying to register "unknown" twice. The old devfs core
> > was forgiving about this (although it was always a driver bug to
> > attempt to create a duplicate). The new core won't let you do that.
> > Error 17 is EEXIST. Please fix the driver
> >
> > - something in user-space created the "unknown" inode before the
> > driver could create it. This is a configuration bug.
>
> Option 3:
> Turn a user generated entry into a kernel generated one and return
> 0. Prepopulating devfs was a valid option so far, you cannot simply
> change this during a stable kernel release.
Well, no, it was never a valid option. It was always a bug. In any
case, the stricter behaviour isn't preventing people from using their
drivers, it's just issuing a warning. The user-space created device
node still works.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Dec 07 2001 - 21:00:39 EST