From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat Mainlinglist <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] some comments on draft-ietf-tsvwg-byte-pkt-congest-10.txt
Date: Mon, 24 Jun 2013 02:46:48 +0300 [thread overview]
Message-ID: <1037381F-B294-405C-BE83-42C16704F9EB@gmail.com> (raw)
In-Reply-To: <CAA93jw7N=pEX_1mwfCtQBCPs7r-6CYo9MMz-+FrTdRJivF_Whg@mail.gmail.com>
On 17 Jun, 2013, at 10:40 pm, Dave Taht wrote:
> Anybody got a 68020 or slower to play with?
As a follow-up to this, I just found somewhere to plug in my 486, and it does indeed still work - even the RTC was only about a month off. Booting from a floppy (tomsrtbt) confirms that all of the hardware seems to be in working order, including the 3c509B - the other NIC is an NE2000 clone of some sort, somewhat newer than the 3com card.
However, it needs a fresh install of Linux, which might still take some time to arrange, considering that it won't boot directly from CD, nor will the BIOS directly recognise any hard disk over 528MB. Even tomsrtbt is too old to support the STROKE protocol for determining the real size of a modern hard disk - if 40GB can be considered "modern" - otherwise I could have used it to unpack a Gentoo stage. Back in the day, I used a smaller disk which could be supported via a BIOS extender in the boot sector.
I think I will need to squeeze a 3.x series kernel onto a floppy disk, and use another machine to build up the rootfs on the hard disk. Luckily, a 486 doesn't need many device drivers, but recent kernels seem to be a lot bigger in the core than older ones.
- Jonathan Morton
prev parent reply other threads:[~2013-06-23 23:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 19:40 Dave Taht
2013-06-18 3:40 ` Jonathan Morton
2013-06-23 23:46 ` Jonathan Morton [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1037381F-B294-405C-BE83-42C16704F9EB@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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