9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Uriel <uriell@binarydream.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 386
Date: Sat, 29 Oct 2005 22:07:20 +0100	[thread overview]
Message-ID: <20051029210720.GB23235@server4.lensbuddy.com> (raw)
In-Reply-To: <12f7bf2af3e9fd212dd65a508a614428@plan9.bell-labs.com>

On Sat, Oct 29, 2005 at 04:01:36PM -0400, jmk@plan9.bell-labs.com wrote:
> We're testing a rewrite of the x86 VM system and invlpg
Will that fix the issues with certain BIOS/mobos that wont boot with AGP
video cards? That would be very nice, I got a couple of such boards.

> I'd actually like to go further and only support processors
> that have the CPUID instruction (that includes the plain
> Pentium otherwise my home machine would need to be replaced).
That sounds reasonable. We have had people in #plan9 ask if they can't
run on a 486 or such, but we had to turn them down because they can't
run the installer on such system(not enough RAM).

As auth or fs servers it might make sense, but people that would use
them as such should have no problem getting an old/custom kernel built
for it.

This days it's not hard to find >P100 in junkyards if you look for them.

> We could provide instructions for what to do if someone
> desperately wanted to run the system on deprecated hardware,
> it's not hard but I feel it's not worth keeping the support
> in the main tree.
Agreed.

> Also, I can't find the old AT&T Safari and Gateway Nomad laptops I
> kept around for testing 386 and 486 compatibility so we've no way to
> test on those any more.
If you want I got an old 486 thinkpad lying around I never had time to
do anything with it, it's pretty cool, but probably shipping would be
more expensive than getting a new one from Ebay.

uriel


  parent reply	other threads:[~2005-10-29 21:07 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29 15:08 Russ Cox
2005-10-29 15:26 ` Lucio De Re
2005-10-29 19:07 ` William Josephson
2005-10-29 20:01   ` jmk
2005-10-29 20:06     ` Lucio De Re
2005-10-29 21:07     ` Uriel [this message]
2005-10-29 21:18       ` jmk
2005-10-29 21:51     ` Ronald G Minnich
2005-10-29 22:31       ` Francisco J Ballesteros
2005-10-30  0:50         ` Ronald G Minnich
2005-10-30  5:41           ` Jack Johnson
2005-10-30 16:15             ` Ronald G Minnich
2005-10-30 20:02             ` jmk
2005-10-30 20:12               ` Uriel
2005-10-30 20:34                 ` Devon H. O'Dell
2005-10-30 20:52                   ` jmk
2005-10-30 21:15                     ` Devon H. O'Dell
2005-10-30 22:56                       ` jmk
2005-10-31  0:20                         ` Ronald G Minnich
2005-10-31  0:49                           ` Russ Cox
2005-10-31 21:26                             ` Dave Eckhardt
2005-10-30 21:27                     ` Mike Haertel
2005-10-31 10:06                       ` Charles Forsyth
2005-10-30 22:11                     ` Ronald G Minnich
2005-10-30 21:16                       ` Francisco J Ballesteros
2005-10-30 21:53               ` Ronald G Minnich
2005-10-29 23:45       ` John DeGood
2005-10-30  0:04         ` William Josephson
2005-10-30 12:59       ` Brantley Coile
2005-10-30  1:14     ` geoff
2005-10-29 20:22 ` Christopher Nielsen

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=20051029210720.GB23235@server4.lensbuddy.com \
    --to=uriell@binarydream.org \
    --cc=9fans@cse.psu.edu \
    /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).