Re: [Rule-list] Kernel subproject

[Marco Fioretti]

On Sat, Feb 09, 2002 21:01:48 at 09:01:48PM -0500, Chris Kloiber wrote:
> 
> Unless you want to burn cycles backporting many needed things (I'm
> thinking iptables for starters) stick to an Official Red Hat kernel.

Excellent point. Starting from an official kernel, however, which
settings could we adjust to make it work more nicely on low-end HW?
> 
> I was thinking that the easiest thing to do would be to have an
> installer that only partitions, formats and mounts the hard drive, then
> copies a very small (basically an i386 kernel, glibc, rpm, rhn_register,
> up2date, a shell and any other required things) installed image to the

I am fine with this, and have the feeling that this is already the way
we are going anyway, judging by the more specialistic messages here.

> drive. Then the user can boot into that, register with Red Hat Network
> and install anything he/she wants with up2date, which can handle
> dependencies as needed.
> 
This must be possible for upgrades and further customization of course, but
not be part of  the installation itself ( by "installation" I mean modified
installer + kickstart + whatever post-install script(s) are needed).

That process must work even when only the RH CDs are available, and put in the
 PC all the packages that we will find needed for basic desktops. The
main reason for this is that, as I mentioned somewhere else, most of
the functionality is achieved by installing on disk standard rpms
(mutt, procmail, emacs.....) and then rewriting their config files so
that all these tool work from the first moment at max speed, connected
to each other. If we put a connectivity dependent phase in the middle
it will complicate the whole process.

        Ciao,
        
        Marco Fioretti
-- 
I doni ricevuti dal Padreterno, servono se utilizzati: chi li contempla
gode, ma chi ne fa uso probabilmente aiuta altri a godere.