From: Steve Kotsopoulos steve@ecf.toronto.edu
Subject: whereis 68020/9nextstation
Date: Thu, 1 Aug 1996 12:17:58 -0400 [thread overview]
Message-ID: <19960801161758.QmbT2Fe3JbVG8ZXlHFx6_WsiWPd7H7JYgRPnigMwUKk@z> (raw)
Gregory Charles Wuller <greg@phoenix.CSc.CAlpoly.EDU> wrote:
>I have what I believe to be the current distribution of the Plan9 CDROM,
>unfortunately I don't see the boot file for a NeXTStation which I
>thought was /68020/9nextstation.
>
>Am I missing something or was there more than one distribution??
Some filenames get remapped (due to long names, or strange chars in the name),
according to the /_conform.map file on the cdrom. If you mount the cdrom
under plan9, the mapping is taken care of by the 9660 driver,
but if you mount it under Unix, the correct filename will not be seen.
% grep 9nextstation _conform.map
F000036 9nextstationdisk
F000037 9nextstation
F000038 9nextstationnofs
So, if you get a listing of /68020, you'll find f000037 is the file you want.
--
Steve Kotsopoulos M.Eng. steve@ecf.toronto.edu
Systems Analyst Engineering Computing Facility, University of Toronto
http://www.ecf.toronto.edu/~steve/
reply other threads:[~1996-08-01 16:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19960801161758.QmbT2Fe3JbVG8ZXlHFx6_WsiWPd7H7JYgRPnigMwUKk@z \
--to=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).