Linus Torvalds writes:
> On Thu, 27 Jul 2000, Alan Cox wrote:
> > Symlinks are wonderful things
> >
> > /lib/modules/2.2.14/build
>
> I like this one. It puts the thing in the same tree as the modules
> themselves, so it's self-contained. Let's _document_ it as a symlink, and
> make "make modules_install" do that part too (I don't use modules so I'd
> rather somebody else sent me the tested - likely one-liner - patch to do
> this).
Let's think about this a little more carefully. IMHO, making
"modules_install" is the wrong place to do this:
1. When we haven't compiled any modules, we're not going to make
modules_install in addition to make install. Therefore this
link will not be set up.
2. What if the machine you're making modules_install on isn't the
machine that you're compiling other kernel modules packages on?
In this case, the compilation machine has no sight of the
symlink.
However, its fine for your single-box only setup where your kernel is
compiled on the same machine that its run on.
Or am I missing something fundamental here?
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King rmk@arm.linux.org.uk --- ---
| | | | http://www.arm.linux.org.uk/~rmk/aboutme.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
-
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 Jul 31 2000 - 21:00:24 EST