From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Grant Taylor <gtaylor@tnetconsulting.net>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Pre-init initialization
Date: Fri, 9 Aug 2019 20:23:08 -0400 [thread overview]
Message-ID: <20190810002308.GB8368@mit.edu> (raw)
In-Reply-To: <ccdd93f2-2cc9-d3f4-757a-24fc0efd3da6@spamtrap.tnetconsulting.net>
On Thu, Aug 08, 2019 at 07:52:04PM -0600, Grant Taylor via TUHS wrote:
> That's before my time. If I remember correctly, by the time I was creating
> boot+root disks it was the kernel plus something—I don't remember if it was
> an initramfs or an initrd—concatenated together. I also remember having to
> use a utility to update the kernel to tell it where the something started.
> Which was really based on how big the kernel was as padding before the
> something started. That was probably 2.<something> on Slackware in '99.
In 1993 Fred van Kempen (who did the original Linux TCP stack before I
got rewritten by Alan Cox's Net-2 stack) added a patch to the ramdisk
code which so the root file system would be loaded from a second
floppy into the ramdisk. That was because he wanted to fit more into
stuff into the root file system, and by using a second floppy, the
full 1.44MB could be used for the root file system in the ramdisk. As
I recall the kernel was also getting bigger than 512k, too.
In '95, Slackware started releasing on CD-ROM's, and while there may
have been boot/root floppies, I suspect more and more they were used
as rescue media, since installing from a CD-ROM was *way* more
convenient.
I'm guesing what you were doing was creating a kernel plus initramfs
which was sufficient to mount a root file system elsewhere as an
emergency "boot this failsafe kernel off the floppy", perhaps? I
don't think a kernel+initramfs on a single 1.44MB floppy would have
been sufficient for use as an install medium by '99. Or were you
making an emergency USB thumb-drive as a rescue device, maybe?
Cheers,
- Ted
next prev parent reply other threads:[~2019-08-10 0:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 23:46 Grant Taylor via TUHS
2019-08-07 1:22 ` Andrew Warkentin
2019-08-07 13:04 ` Clem Cole
2019-08-07 16:40 ` Warner Losh
2019-08-08 13:31 ` Theodore Y. Ts'o
2019-08-09 1:52 ` Grant Taylor via TUHS
2019-08-10 0:23 ` Theodore Y. Ts'o [this message]
2019-08-10 2:28 ` Grant Taylor via TUHS
2019-08-10 4:21 ` Kevin Bowling
2019-08-10 4:50 ` Grant Taylor via TUHS
2019-08-10 4:52 ` Adam Thornton
2019-08-08 13:43 ` Clem Cole
2019-08-08 18:59 ` Warner Losh
2019-08-09 1:46 ` Grant Taylor via TUHS
2019-08-09 2:15 ` Warner Losh
2019-08-09 6:43 ` Kevin Bowling
2019-08-10 1:45 ` Chris Hanson
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=20190810002308.GB8368@mit.edu \
--to=tytso@mit.edu \
--cc=gtaylor@tnetconsulting.net \
--cc=tuhs@minnie.tuhs.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).