Re: Announce: modutils 2.3.11 is available - the debugger's helper

From: willy@thepuffingroup.com
Date: Fri Apr 21 2000 - 17:19:05 EDT

  • Next message: jamal: "Re: P-MTU discovery"

    On Fri, Apr 21, 2000 at 01:41:54PM -0600, Richard Gooch wrote:
    > willy@thepuffingroup.com writes:
    > > On Fri, Apr 21, 2000 at 11:00:26AM -0500, Stefan Monnier wrote:
    > > > >>>>> "Keith" == Keith Owens <kaos@ocs.com.au> writes:
    > > > > * Add ieee1394 directory, requested by Andreas Bombe.
    > > >
    > > > I know this has been mentioned before, but I'd like to reiterate
    > > > my request for a way to just look in *every* subdirectory.
    > > > I does not have to be the default, but it should be at least possible
    > > > to get this behavior with some /etc/modules.conf editing.
    > >
    > > I'm not entirely sure why the modules are segregated into separate
    > > directories anyway. The namespace collision already happens at
    > > build time (when they're all symlinked into /usr/src/linux/modules)
    > > and modprobe is invoked (by me anyway) with just the name of the
    > > module, so why pretend it's not a flat namespace? Eschew
    > > obfuscation.
    >
    > Because a flat directory is harder to view for the human. When I ask
    > myself "do I have the ne2k-pci module", it's obvious to just look in
    > the "net" directory.

    surely

    ls *ne2k*

    is not too hard for someone who wants to know the answer to that question?

    > The subdirectories are a natural categorisation
    > that makes life easier. It's not about pretending there is a
    > hierarchical namespace.

    but it makes life somewhat more complex than necessary for the kernel
    build scripts and for modutils.

    -
    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 : Fri Apr 21 2000 - 16:32:15 EDT