From: carl.lowenstein@gmail.com (Carl Lowenstein)
Subject: [TUHS] 386BSD on Bochs & Qemu...
Date: Sun, 25 Apr 2010 10:32:51 -0700 [thread overview]
Message-ID: <z2o5904d5731004251032v132115b7w13c7236543009037@mail.gmail.com> (raw)
In-Reply-To: <5a7c3451f8bbb8efaaa6b9c809214a55.squirrel@webmail.xs4all.nl>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1408 bytes --]
On Sun, Apr 25, 2010 at 2:28 AM, Jacob Goense <dugo at xs4all.nl> wrote:
>>> It got me curious about where 386BSD ended though. Did anyone save
>>> the 386BSD Reference CD-ROM Release 1.0 from /dev/null?
>>
>> Yes, I have a copy. It was pretty much useless. All the
>> documentation was in some Microsoft format, and I couldn't read it.
>> Unfortunately Dr Dobbs has a copyright on it, or I could upload it for
>> the curious.
Using tools that were not available 15 years ago, Google search for
"windows+help+file+reader" leads me to, among others:
<http://helpexplorer.software.informer.com/> which looks promising.
Of course I don't have anything to try exercising it on.
> That's about what I understood from as well from reading this column
> at http://www.cfcl.com/rdm/tin/P/199503.shtml
>
> "The 386BSD release CD-ROM includes a mixture of BSD and Jolitz code,
> articles, and what have you. The files are hyperlinked with a global
> glossary and index to illustrate the structure and interdependence in
> the discussion of the system files.
>
> The stuff in WinHelp format being useless, ok, but what about the
> system on the CD, did you ever try booting and installing it?
Maybe WinHelp format has not changed over the decades.
carl
--
carl lowenstein marine physical lab u.c. san diego
clowenstein at ucsd.edu
next prev parent reply other threads:[~2010-04-25 17:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-17 5:12 Jason Stevens
2010-04-17 19:10 ` Natalia Portillo
2010-04-18 1:12 ` Jason Stevens
2010-04-24 14:28 ` Jacob Goense
2010-04-24 18:06 ` Jason Stevens
2010-04-24 20:59 ` Tom Ivar Helbekkmo
2010-04-25 2:29 ` Greg 'groggy' Lehey
2010-04-25 9:28 ` Jacob Goense
2010-04-25 17:32 ` Carl Lowenstein [this message]
2010-04-25 17:36 ` Jason Stevens
2010-04-26 3:23 ` Greg 'groggy' Lehey
2010-04-26 5:22 ` Jason Stevens
2010-05-04 19:37 ` Jacob Goense
2010-05-04 19:41 ` Natalia Portillo
2010-05-04 18:26 ` Jacob Goense
2010-04-26 7:03 ` Wesley Parish
2010-04-26 8:07 ` Greg 'groggy' Lehey
2010-04-26 9:33 ` Wesley Parish
2010-04-26 17:52 ` Jason Stevens
2010-04-28 2:30 ` Cyrille Lefevre
2010-04-30 7:58 ` [TUHS] UniFlex Jose R. Valverde
2010-04-30 15:38 ` Brad Spencer
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=z2o5904d5731004251032v132115b7w13c7236543009037@mail.gmail.com \
--to=carl.lowenstein@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;
as well as URLs for NNTP newsgroup(s).