> back then the argument (not mine btw) was that /usr on a lot of machines
> is RO (I think debian has an option for that) so that sysadmins there
and because of that (among other reasons) my other report about
compiling outside of the source directory...
> compile stuff in /root. /lib/modules however IS standardized and needs
> to be writable to install a new kernel so making a symlink to the real
Only while installing a new kernel. And you install the kernel on the
box it needs to run on, which is not necessarily the box it's compiled
> place there isn't too bad. In addition it already is the only directory
> with per kernel files.. adding a second one was judged not needed. It
Only for stand-alone machines which only ever compile and run one
kernel. You don't need a data center to violate that, you just need
the fairly usual three-boxes home network (one of which is mainly a
router/firewall which has no development environment if only for
security reasons, or because it's a scavenged '486).
> has to be somewhere. /lib/modules/ or /usr/src.. who cares. Linus made
> the final call and everybody complies with it since then, just because
> it doesn't matter THAT much. It just needs to be SOMEWHERE standard and
> /lib/modules suffices so far it seems.
Frankly, I think the main reason is that Linus doesn't care at all
about the kernel build process. We've had a _much_ better solution
already in the 2.5 cycle which was rejected for completely bogus
formal reasons coupled with an explicit "why do we need this at all",
even though it was pointed out over and over again what is broken
currently (or was back then, granted it has improved but not as much
as is desirable and possible).
This blatantly erroneous decision just smells of a blind spot or
carelessness more than careful consideration.
 it's about of the same category as the original Unix' designers
putting utmp and wtmp in /etc. Linus would never have approved _that_.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jan 23 2003 - 22:00:27 EST