Aunt Tillie builds a kernel (was Re: ISA hardware discovery --the elegant solution)
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 4 lines · Marco Colombo
Alan, Eric (and others, too), please.
Of course the autoconfigurator is an useful piece of software. And of course Eric is posting to the wrong list here. Kernel developers don't need any autoconfigurator at all (yes, it's just "extra state").
The main discussion was in kbuild-devel list.
Quoted 4 lines
Eric, Aunt Tillie doesn't need any custom-made, untested, probably not working kernel. QA comes at a price. The lastest VM fix may take a while to reach mainstream kernels. That's life.
Maybe this force kernel maintainer to merge the tested and trusted distribution patches into the main kernel's branches.
Anyway, the target of Linux changes. If was a toy for hacker 10 year ago, maybe in future will be the toy for Aunt Tillies. So:
Forget aunts and the other scenarios of Eric.
Let talk about what autoconfigure can do yet (aka the creation of a /proc/drivers (better in /dev) with a list of all running kernel drivers. aka how the modules will be in the next months)
giacomo
Quoted 5 lines · Giacomo Catenazzi
Marco Colombo wrote:
Quoted 7 lines
Quoted 4 lines
Alan, Eric (and others, too), please.
Of course the autoconfigurator is an useful piece of software. And of course Eric is posting to the wrong list here. Kernel developers don't need any autoconfigurator at all (yes, it's just "extra state").The main discussion was in kbuild-devel list.
Uh, my mailbox hurts just at the thought of even more posting on the suject.
Quoted 6 lines
Quoted 3 lines
Eric, Aunt Tillie doesn't need any custom-made, untested, probably not working kernel. QA comes at a price. The lastest VM fix may take a while to reach mainstream kernels. That's life.
Maybe this force kernel maintainer to merge the tested and trusted distribution patches into the main kernel's branches.
Which means, in Alan's (and Yoda's) words, even more perturbations of the Source. I don't really like the idea of kernel maintainers forced into anything...
Kernel tarballs are for hackers. Marcelo can't test any configuration the autoconfigurator can produce. So basically it means an untested kernel. Running untested kernel isn't a job for Joe User, and never will be.
Some distro vendor may be interested in an easy, do-it-yourself kernel compilation & customization tool. It brings almost nothing to kernel developers.
Vendors and kernel developers have different goals. That horrible hack that fixes some bug or misbehavior fits fine into a vendor kernel, and has no place in Marcelo's tree; the same for that C++ written, cross OS crap driver for hardware XYZ. Users want it, vendors provide it. Different goals, different targets.
Quoted 6 lines
Anyway, the target of Linux changes. If was a toy for hacker 10 year ago, maybe in future will be the toy for Aunt Tillies. So:
Forget aunts and the other scenarios of Eric.
Let talk about what autoconfigure can do yet (aka the creation of a/proc/drivers(better in /dev) with a list of all running kernel drivers. aka how the modules will be in the next months)
Creating .config (or whatever) is an userland issue, IMHO. /proc/driver and the like is another issue, as it can be useful in general.
Autoconfiguration is nice. But please move the topic elsewhere.
.TM.
Signature · 5 lines
____/ ____/ /
/ / / Marco Colombo
___/ ___ / / Technical Manager
/ / / ESI s.r.l.
_____/ _____/ _/ [email protected]Quoted 6 lines · Marco Colombo
Quoted 3 lines
The main discussion was in kbuild-devel list.
Uh, my mailbox hurts just at the thought of even more posting on the suject.
In kbuild: less people, less traffic, more discussion, less flames
Quoted 4 lines
Kernel tarballs are for hackers. Marcelo can't test any configuration the autoconfigurator can produce. So basically it means an untested kernel. Running untested kernel isn't a job for Joe User, and never will be.
Also what are the stable series?
But you think your distribution test the kernel in all possible use? With all possible hardware configuration? Autoconfiguration will configure a compile and booting kernel. (but on old machine). Neither vendor can assure you that the kernel will work for a particolar permutation of hardware, and mainly it is indipendent from configuration.
Quoted 5 lines
Vendors and kernel developers have different goals. That horrible hack that fixes some bug or misbehavior fits fine into a vendor kernel, and has no place in Marcelo's tree; the same for that C++ written, cross OS crap driver for hardware XYZ. Users want it, vendors provide it. Different goals, different targets.
Change distribution. In Debian/unstable developers and distribution are hardly linked!
Why do you need someone in the 'layer' between developers and user?
Quoted 1 line
Autoconfiguration is nice. But please move the topic elsewhere.
Right. Let stop it
giacomo
Quoted 14 lines · Giacomo Catenazzi
Quoted 6 lines · Marco Colombo
Quoted 3 lines
The main discussion was in kbuild-devel list.
Uh, my mailbox hurts just at the thought of even more posting on the suject.
In kbuild: less people, less traffic, more discussion, less flames
Quoted 7 lines
Quoted 4 lines
Kernel tarballs are for hackers. Marcelo can't test any configuration the autoconfigurator can produce. So basically it means an untested kernel. Running untested kernel isn't a job for Joe User, and never will be.
Also what are the stable series?
The *starting* point to build a working solution. And stable != supported. The "working solution" being a distro kernel (well, the whole thing really), which happens to be supported (and supportable), too...
Quoted 2 lines
But you think your distribution test the kernel in all possible use? With all possible hardware configuration?
They *virtually* do. Why do they have (slightly) DIFFERENT hardware compatibility lists? I don't care if they do really test a given HW configuration as long as they support it. You can't ask Marcelo to actively support any HW conf. I'd expect him to "support" just the HW he uses to build tarballs.
Quoted 4 lines
Autoconfiguration will configure a compile and booting kernel. (but on old machine). Neither vendor can assure you that the kernel will work for a particolar permutation of hardware, and mainly it is indipendent from configuration.
Uh? After autoconfiguration you *hope* the kernel boots. In late 2.2 times, vanilla 2.2 used to be almost useless for just less-than-naive users. Think of RAID @ redhat, or ReiserFS @ suse.
BTW, if I buy a RH Linux CD set (+support), and install it on a PC made by parts all included in RH HW compatibility list, I expect:
1) it to work;
2) failing 1), Red Hat to solve any problem when I call them for support;
3) failing 2), Red Hat to return the money for the CDs. That's what vendors are for.
Quoted 9 lines
Quoted 5 lines
Vendors and kernel developers have different goals. That horrible hack that fixes some bug or misbehavior fits fine into a vendor kernel, and has no place in Marcelo's tree; the same for that C++ written, cross OS crap driver for hardware XYZ. Users want it, vendors provide it. Different goals, different targets.
Change distribution. In Debian/unstable developers and distribution are hardly linked!
Are you suggesting that Joe User should run Debian/*unstable*? What it Debian/stable for, then?
Quoted 2 lines
Why do you need someone in the 'layer' between developers and user?
The user isn't expected to do any QA. And Marcelo and other kernel maitainers aren't, either.
Quoted 3 lines
Quoted 1 line
Autoconfiguration is nice. But please move the topic elsewhere.
Right. Let stop it
No problem for me. Feel free to answer me privately, as the above is hardly kernel-related (it applies to any other piece of software).
Quoted 2 lines
giacomo
.TM.
Signature · 5 lines
____/ ____/ /
/ / / Marco Colombo
___/ ___ / / Technical Manager
/ / / ESI s.r.l.
_____/ _____/ _/ [email protected]