[4453] in testers
Re: linux [8.4.1]: kernel/initrd
daemon@ATHENA.MIT.EDU (Greg Hudson)
Mon Jun 12 23:58:51 2000
Message-Id: <200006130358.XAA13940@small-gods.mit.edu>
To: Jonathon Weiss <jweiss@MIT.EDU>
Cc: Greg Hudson <ghudson@MIT.EDU>, testers@MIT.EDU
In-Reply-To: Your message of "Mon, 12 Jun 2000 23:56:21 EDT."
<200006130356.XAA00700@stratton-three-o-six.mit.edu>
Date: Mon, 12 Jun 2000 23:58:45 -0400
From: Greg Hudson <ghudson@MIT.EDU>
> Ah, I'd thought we'd put enough brains into the kernel update
> process that there weren't known configuration that would update to
> an unbootable system.
We solved a different problem. The update isn't smart enough to
ensure a bootable system for a system we don't support booting on.
> What creates the initrd image? IE., what would it take to create an
> image, both in my individual case, and in the generic case of any
> scsi machien that needed it (I'm sure there are other SCSI machines
> running IS linux athena)?
mkinitrd, probably invoked in a stock Red Hat installation by the Red
Hat install process and by anaconda (the Red Hat update agent).