From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5.61 (Yes, there are still Alpha users out there. :-) )
Date: Thu, 20 Feb 2003 12:36:24 +0100 [thread overview]
Message-ID: <20030220113624.GP351@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.3.96.1030220060638.14551A-101000@gatekeeper.tmr.com>
[-- Attachment #1: Type: text/plain, Size: 2536 bytes --]
On Thu, 2003-02-20 06:23:46 -0500, Bill Davidsen <davidsen@tmr.com>
wrote in message <Pine.LNX.3.96.1030220060638.14551A-101000@gatekeeper.tmr.com>:
> On Thu, 20 Feb 2003, Jan-Benedict Glaw wrote:
> > On Wed, 2003-02-19 15:39:44 -0500, Bill Davidsen <davidsen@tmr.com>
> > > If you have simple needs that's fine. I build for multiple groups of
> > > machines, and with a working mkinitrd I can just build a file for the boot
> > > controller on each type of machine, and only build a single kernel which
> > > will run anywhere with the proper initrd file.
> >
> > I do it the other way around - I've collected a number of .config files
> > (one for each machine) which includes everything the machine needs to
> > *boot*.
>
> But... if you have it in .config, then you have to rebuild the kernel each
> time. Maybe on an Alpha that doesn't matter, on anything I use a kernel
Guess, I do rebuilds nearly every time Linus releases a new full kernel
or one of his bk snapshots. So that doesn't really matter...
At times, even cross compiles succeed. On a dual Athlon (1.4GHz each),
building kernels doesn't really take thaaaaat long:-) Esp. if you can
keep all the kernel sources and a dozend compilers in memory:-P
> > Any additional features (LVM/DM, filesystems, iptables, ...)
> > ships as modules. Things which require a distinct order are placed into
> > /etc/modules (Debian's list of modules which need to be loaded in given
> > order), all the rest is done via alias/install lines in
> > modules.conf/modprobe.conf.
> >
> > This is, you do keep a machine's local config in its initrd, I do keep
> > it on the machine itself.
>
> Okay, now I see what you are doing, I guess you just have enough system
> power to invest the time and disk space in building a kernel for each
> config. When there was a working mkinitrd I was happily able to use fewer
> of my resources to generate boot setups for all my systems, at least of a
> given arch.
This reminds me that I wanted to have a look at an additional feature -
building the kernel _not_ within its source tree. So I wouldn't need to
place 10 copies of the kernel onto disk / into memory...
Haven't I seen patches flyin' around? Anyone?
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur
fuer einen Freien Staat voll Freier Bürger" | im Internet!
Shell Script APT-Proxy: http://lug-owl.de/~jbglaw/software/ap2/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-02-20 11:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 11:25 2.5.61 (Yes, there are still Alpha users out there. :-) ) Oliver Pitzeier
2003-02-17 12:14 ` Jan-Benedict Glaw
2003-02-17 15:39 ` Fred K Ollinger
2003-02-17 21:29 ` Jan-Benedict Glaw
2003-02-19 18:00 ` Bill Davidsen
2003-02-19 19:55 ` Jan-Benedict Glaw
2003-02-19 20:39 ` Bill Davidsen
2003-02-20 6:23 ` Jan-Benedict Glaw
2003-02-20 11:23 ` Bill Davidsen
2003-02-20 11:36 ` Jan-Benedict Glaw [this message]
2003-02-20 17:21 ` Sam Ravnborg
2003-03-03 22:10 ` Andy Isaacson
-- strict thread matches above, loose matches on Subject: below --
2003-02-17 18:07 Jim Lucas
2003-02-17 11:19 Oliver Pitzeier
[not found] <3E4FEF47.8010207@i-55.com>
2003-02-17 10:16 ` Oliver Pitzeier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030220113624.GP351@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).