lkml.org 
[lkml]   [1999]   [Jan]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: proper place to discuss kernel 'bloatedness'?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Perhaps I need to re-iterate the problem...

I'm not concerned about speed issues nor other issues... Simple the huge
footprint the kernel has. Many people (like myself) run Linux on small
systems where popping open a 40MB tarball would overfill the disks. And
even if you 'clean out' stuff manually you'll probably not have enough
space to compile it and you run the risk of messing up the kernel...

Below is df -h from my largest system running x86 Linux here
Filesystem Size Used Avail Capacity Mounted on
/dev/hda1 382M 315M 48M 87% /

As you can see there's no way Linux could be compiled. This system will be
effectively stuck at 2.0.35 forever.

Below is a direct cut-n-paste from a response I wrote::

I'm not saying necesarily (sp? I'm a programmer not an english major) that
the main distro needs to be ripped up in this manner, but that maybe some
sort of collective effort at establishing a de-facto mode-of-operations
where drivers include some sort of standard-ish INFO file that could be
used for an automated system. I don't have the resources to host anything
but I'd be willing to give a go of it if someone is willing to give it a
host and if people are willing to try it.

- --
Michael Loftis

Normally I'd put something of great profoundness in here, but for now I am
lacking profundity.


-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.5.3i for non-commercial use <http://www.pgpi.com>

iQA/AwUBNrKA0av+wuhQJ9hxEQKWoACg2HezSvCzu8MWUmv+DCQiO9I8KcUAoJIl
ecIX0En9AfWpWeGM8junWYeQ
=vxzz
-----END PGP SIGNATURE-----


-
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/

\
 
 \ /
  Last update: 2005-03-22 13:50    [W:0.104 / U:0.068 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site