On Sun, 14 May 2000, Russell King wrote:
> Alan Cox writes:
> > > So put the initialization of driver after the procfs one. It's not a
> > > problem in procfs, it's problem in the driver. It has no business
> > > registering the stuff in procfs before the thing is initialized, to start
> > > with.
> >
> > Looks like procfs is initialised way too late then. I think procfs is the
> > one that needs moving, not all the drivers. In order to meet these
> > requirements in fact procfs must be initialised before basically any block or
> > char driver.
>
> Alan & Al,
>
> Please see my fs/Makefile patch posted earlier on this subject that re-orders
> the initcall order to fix this problem.
Works for me... Just watch for the filesystems that might want to do odd
things on driver initialization (NWFS wanted to scan the partitions, IIRC,
but I'm not sure at which point that was supposed to happen).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon May 15 2000 - 21:00:24 EST