Re: A module bug in 2.2.1?

Adam J. Richter (adam@yggdrasil.com)
Thu, 4 Feb 1999 10:05:24 -0800 (PST)


>> As
>> > the purpose of the shell is to invoke insmod on unix.o (modprobe uses
>> > system() to facilitate shell expansion of entries from modules.conf), the
>> > module is finally inserted and processing continues.

>I don't know the modutils package, but if as you write the sole
>purpose of using the shell is to use the shell expansion there is a
>better way: wordexp. Also new in glibc 2.1.

Why not glob(3)?

I think it is important that modutils not be dependent on glibc2,
because the legal problems with glibc2/libio may force Yggdrasil to
switch back to libc5.

Anyhow, there are many ways to solve this either in modutils
or in a system's boot scripts, and getting the shell out of modprobe
will make it run faster anyhow. As long as executing an arbitrary
binary does not always cause the loading of a module, it is not a
C library issue.

Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 104
adam@yggdrasil.com \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."

-
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/