Hi,
On Sat, 10 Jun 2006, Michael Tokarev wrote:
> >> But I see a reason for kinit *now*, in its current form - it's
> >> compatibility. Later on, maybe the whole stuff can be removed entirely,
> >> to rely on external tools for booting.
> >
> > The compatibility code is already in the kernel, just don't call it if
>
> Isn't kinit/klibc intended to *replace* that whole code in the kernel?
Well, that's the basic idea, but slowly I'm wondering whether anyone has
really figured out how to do this.
Being able to produce small binaries is part of it, but it somehow also
has to work together with the rest of system, e.g. how can be configured
(by the user, distribution, ...) or how can it be extended.
We need to know where we are going, otherwise it's hard to know whether
we're on the right path.
bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
