Re: How does "alias ethX drivername" in modules.conf work?
Josh Wyatt (jdwyatt@Bellsouth.net)
Tue, 07 Aug 2001 19:06:19 -0400
Tim Jansen wrote:
>
> On Tuesday 07 August 2001 23:46, Mark Atwood wrote:
> > Userspace init scripts point the finger at kernel, saying "there is no
> > good and no well documented mapping method". Kernel points its finger
> > at userspace, saying "this is the way we do it" and "we cant guarantee
> > a perfect 100% mapping solution, so we're not even going to try for
> > 90%" and "futz with your drivers and modules.conf and init scripts
> > till you get something that works".
>
> I'm working on one a possible solution, the Device Registry
> (www.tjansen.de/devreg). It solves this problem by assigning device ids to
> physical devices. This allows you to identify a physical device, even after
> you changed tge port.
Sounds interestingly like the solaris solution to the problem,
/etc/path_to_inst.
Thanks,
Josh
-
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/