On Fri, 20 Apr 2001, David Douthitt wrote:
> George Metz wrote:
>
> > The final result is as follows:
> >
> > 1. Kernel is no longer able to mount filesystem images on the loopback
> > device.
>
> This is something that Oxygen takes advantage of quite a bit; it's not
> required, but even in the boot process it can be used as desired.
> Oxygen has the ability to read the entire disk into memory FIRST, then
> load from that image - and this uses the loopback interface. I've
> also used the loopback to mount disk images as desired.
>
> How much does this save you in 2.4? How much in 2.2?
I haven't touched 2.2 in a while - since I released the 2.2.18 kernel, in
fact. (Trots off for a quick 'make bzImage'...)
Okay. This is with Network and Loopback Block Devices and Serial support
compiled in. Just the PCI Database has been pulled.
-rw-r--r-- 1 wolfstar root 495k Apr 20 13:17 kernel.standard
-rw-r--r-- 1 wolfstar root 428k Apr 20 13:17 kernel.upx
So we're looking at about 18K for the UPX'd version. Since I'm going to be
releasing the one with serial added back in, and this adds an extra 6K, I
might as well.
Can ANYONE see a reason for Network Block Devices to be allowable as
anything other than a module? I can't even get a good idea of what they're
used for, as it specifically states that you can use NFS/Coda/et al
without it.
--
George Metz
Commercial Routing Engineer
[EMAIL PROTECTED]
"We know what deterrence was with 'mutually assured destruction' during
the Cold War. But what is deterrence in information warfare?" -- Brigadier
General Douglas Richardson, USAF, Commander - Space Warfare Center
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
