Re: Make ipconfig.c work as a loadable module.

On Fri, Mar 07, 2003 at 09:42:35AM +0000, Russell King wrote:

On Fri, Mar 07, 2003 at 01:29:05AM +0000, Chris Dukes wrote:

quoted

That's nice.  Would you mind explaining to us where that would be a
benefit?  Aside from dead header space in elf executables, I'm at
a loss as to how a usermode implementation must be significantly
larger than kernel code.

If you're suggesting above that "5MB isn't significantly larger than
the size Linux can do this" then I think I've just proven you wrong.

The 5Mb example is AIX.

Lets see - building an ramdisk to mount a root filesystem out of existing
binaries would require from my exisitng systems probably something like:

I said userspace.  I did not say existing binaries.
[Size comparison of the kitchen sink vs kernel code deleted because 
it's comparing apples and oranges].

Which version is overly bloated?
Which version is huge?
Which version is compact?

You are asserting aesthetics instead of benefits.  I asked about benefits.
Specifically, what is the benefit of compact?
I'm sure you have a very good technical or business benefit to compact, 
but those of us in the world of workstations and servers have zero clue 
what it may be.

Another individual has already indicated a very valid technical merit to
having it all in one file.  I have the same problem myself.  AIX and *BSD
have a working approach to that problem.

Even the klibc ipconfig version is significantly larger than the in-kernel
version - and klibc and its binaries are written to be small.

User space solution is not the same as a solution implemented with
multiple user space apps.

Note: I *do* agree that ipconfig.c needs to die before 2.6 but I do not
agree that today is the right day.

Perhaps you could explain why today is not the day.
(ie, soon to be shipping product that requires it.  desire to see a viable
userspace solution working before it is removed).

-- 
Chris Dukes
I tried being reasonable once--I didn't like it.