>>> Note, though, that it is **very** important that
>>> /usr/include/linux and /usr/include/asm correspond to the
>>> default kernel that you are booting.
>> Ted, you are assuming people will build stuff on the machine
>> they are running from. Its certainly a convenient assumption for
>> the majority of uses but a lot of big have all their kernel
>> building/images in one place not around machines.
>> I'm not convinced /usr/include/linux is sufficient. Perhaps we
>> need a more explicit naming ?
> I agree that for more complicated situations you will need to
> have a way of explicitly specifying which kernel source tree to
> find the right set of include files. For those folks, forcing
> them to edit a Makefile or change a config.mk to specify the
> correct header file seems acceptable for me.
> The vast majority of users won't be doing something this
> complicated, and they are also the people for whom we should
> make the building and installation experience as simple as
> possible.
To me, the obvious answer to this is the one I proposed over a year
ago - have the kernel stored in linux-`uname -r` by default. It was
thrown out because Linus considered that change to be too much work on
his part, or so I was told.
Personally, I would say that this topic can be debated until kingdom
come, but it won't make the slightest difference unless and until
Linus decides to do something about it.
Best wishes from Riley.
PS: The kernel versions page is now back online at the URL below, and
includes separate sublists both for each kernel series, and for
each year of development.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* http://www.memalpha.cx/Linux/Kernel/
-
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/