9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Uriel <uriel99@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] the old floppy set
Date: Sat,  8 Aug 2009 19:05:10 +0200	[thread overview]
Message-ID: <5d375e920908081005k3974ad49q38ef36ca76c8664f@mail.gmail.com> (raw)
In-Reply-To: <7d3530220908072149j791a06ahe046f7249408807e@mail.gmail.com>

On Sat, Aug 8, 2009 at 6:49 AM, John Floren<slawmaster@gmail.com> wrote:
> On Fri, Aug 7, 2009 at 2:15 AM, Steve Simon<steve@quintile.net> wrote:
>> As Anthony says it is very very old, but I might
>> be fun if you had the time on your hands. The 2nd edition
>> books/cdrom are nolonger available but you might find
>> a set seccond hand (abebooks.com etc).
>>
>> The floppys are here:
>> /n/sources/contrib/steve/historic/2nd-edition/pcdist/
>>
>> I found a complete mirror of the old 2nd edition site
>> and I think uriel has copied it to cat-v.org.
>>
>> You will need 16Mb to install and 8Mb to run a terminal
>> though It will work at 640x480x1 resolution.
>>
>> The 4th edition should run on a 486, though you will need
>> (say) 128Mb of ram - much more if you want to recompile gs(1).
>>
>> -Steve
>>
>>
>
> With a little help from FreeDOS, I am now successfully running 2e on a
> 66MHz 486 with 32 MB of RAM and little bitty hard drive (< 300 MB).
> It's fun; on the surface, it's not a lot different, although 800x600x1
> makes things interesting (I like it, actually... rio hacking time?).
>
> I'd kill for the full CD, which I guess would have to go on my other
> 486, since I seem to recall that the full system needs 500 MB.
> However, given licensing, I suppose it's out of reach for the time
> being--anybody with experience in this sort of thing, is there a point
> in time when it could be distributed freely, or will it be stuck in
> the "You can't have 2e without a license, and you can't have a
> license" state forever?

If you follow the insane rules of copyright, you will have to wait at
least 90 years or so before it falls into the public domain. And by
then they probably will have expanded copyright terms by another extra
hundred years, so 'forever' seems about right.

uriel



  parent reply	other threads:[~2009-08-08 17:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-07  4:55 John Floren
2009-08-07  5:04 ` Anthony Sorace
2009-08-07  5:12   ` John Floren
2009-08-07 18:47     ` Lyndon Nerenberg
2009-08-07 19:49       ` Anthony Sorace
2009-08-07  9:15   ` Steve Simon
2009-08-07 10:11     ` erik quanstrom
2009-08-07 11:06     ` Uriel
2009-08-07 14:46       ` Benjamin Huntsman
2009-08-08  4:36     ` lucio
2009-08-08  4:49     ` John Floren
2009-08-08 14:48       ` Anthony Sorace
2009-08-08 15:45         ` ron minnich
2009-08-08 17:11           ` Anthony Sorace
2009-08-08 18:23             ` erik quanstrom
2009-08-08 18:53             ` Benjamin Huntsman
2009-08-09  2:31             ` Tim Newsham
2009-08-08 17:05       ` Uriel [this message]
2009-08-13 14:11       ` michael block
2009-08-13 14:23         ` John Floren
2009-08-13 14:26           ` erik quanstrom
2009-08-13 15:11           ` michael block
2009-08-13 15:27             ` erik quanstrom

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=5d375e920908081005k3974ad49q38ef36ca76c8664f@mail.gmail.com \
    --to=uriel99@gmail.com \
    --cc=9fans@9fans.net \
    /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).