Re: UUIDs (and devfs and major/minor numbers)
H. Peter Anvin (hpa@transmeta.com)
Fri, 18 Jun 1999 06:49:40 -0700
David Woodhouse wrote:
>
> Matthew.Wilcox@genedata.com said:
> > On Fri, Jun 18, 1999 at 05:39:20AM -0700, H. Peter Anvin wrote:
> > > Actually, I don't see much difference between this and an initrd on
> > > romfs.
> > The difference is that the Multiboot Standard requires that the
> > bootloader handles this whereas the kernel handles initrd & romfs.
>
> You have an embedded system, which is short of RAM. You choose - you can put
> this in the bootloader where it gets dropped on booting, or you can put it in
> the kernel where it takes up non-pageable RAM all the time. I know which I'd
> choose.
>
> If that's not a simple enough choice for you, factor in some other discussions
> that have shown up on this list recently...
>
> What I'd like to see in the long term is for the kernel to lose the distinction
> between compiling drivers as a module and statically linking them.
>
> I'd also like to remove the large amounts of driver-specific code/tables in
> places like drivers/net/Space.c and init/main.c - they can be replaced with a
> solution which allows drivers to be distributed as single pieces of code,
> without patching the 'core' kernel.
>
Actually, the kernel init code is dropped after kernel is booted.
-hpa
--
"The user's computer downloads the ActiveX code and simulates a 'Blue
Screen' crash, a generally benign event most users are familiar with
and that would not necessarily arouse suspicions."
-- Security exploit description on http://www.zks.net/p3/how.asp
-
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/