From: Adam Thornton <athornton@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Pre-init initialization
Date: Fri, 9 Aug 2019 21:52:47 -0700 [thread overview]
Message-ID: <CAP2nic2Tv5is8_V7k6QpJSGXv0bMEz8TiaZHf-hp1wvOtkZtAQ@mail.gmail.com> (raw)
In-Reply-To: <CAK7dMtA6fe3MAtRaLMOrt_Vk1=4xJCiJNV0o2mYm+YKq_f=jqQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1722 bytes --]
MCA support came pretty late, so that's not terribly surprising.
As did booting-from CD-ROM, for that matter. I think I remember a fairly
long period where the CD-ROM hung off the SoundBlaster, not the IDE bus.
Adam
On Fri, Aug 9, 2019 at 9:22 PM Kevin Bowling <kevin.bowling@kev009.com>
wrote:
> Yup I remember doing a boot/root floppies with Slackware as late as the
> early 2000s on an IBM PS/2 Model 95.
>
> On Fri, Aug 9, 2019 at 7:29 PM Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
> wrote:
>
>> On 8/9/19 6:23 PM, Theodore Y. Ts'o wrote:
>> > 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.
>>
>> The boot & root floppies were how you booted Slackware for a long time.
>> The CD-ROM was unbootable for quite a while. You booted off of floppy
>> and the installation scripts would ask you which drive had the CD-ROM in
>> it to mount and install from.
>>
>> > 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?
>>
>> It was a re-roll of the above boot & root disk set. It was not rescue
>> media per-say. Though the standard boot & root disk set did get used
>> for rescue purposes in addition to installation.
>>
>>
>>
>> --
>> Grant. . . .
>> unix || die
>>
>>
[-- Attachment #2: Type: text/html, Size: 2531 bytes --]
next prev parent reply other threads:[~2019-08-10 4:53 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
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 [this message]
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=CAP2nic2Tv5is8_V7k6QpJSGXv0bMEz8TiaZHf-hp1wvOtkZtAQ@mail.gmail.com \
--to=athornton@gmail.com \
--cc=tuhs@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).