From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: migieger@vsnl.com, 9fans@cse.psu.edu
Subject: Re: [9fans] plan9v3 won't start (PBS...Bad format or I/O error)
Date: Thu, 13 Jul 2000 16:43:19 -0400 [thread overview]
Message-ID: <200007132043.QAA11368@smtp3.fas.harvard.edu> (raw)
If it installed its own MBR there should be MBR...
before PBS... You may need pbslba instead of pbs.
That is,
disk/format -b /386/pbslba /dev/sdC0/plan9
Or maybe you already have pbslba and you need pbs
disk/format -b /386/pbs /dev/sdC0/plan9
(it will just install a boot sector, not format).
And something more: is it possible to use history
and command completion with rc?
Not really. I like this command (which Tom Killian
introduced me to) a lot though:
g% cat /usr/rsc/bin/rc/"
#!/bin/rc
{
if(test -r /mnt/acme/acme/body)
cat /mnt/acme/acme/body
if not
cat /dev/text
} | grep '^[^ ]*%[ ]*'$1 |
{echo; cat} | pr -t -n | sort -u +1 | sort -n |
sed 's/^ *[0-9]+ //' | grep .
# the silly {echo; cat} gets around pr printing "empty file" when
# presented with no input.
g%
It prints all commands in the current
window that begin with the given string.
For example, it prints the two lines marked with >>>
in the following.
g% cat /usr/rsc/bin/rc/"
...
g% cat /adm/users
...
g% " cat
>>> g% cat /usr/rsc/bin/rc/"
>>> g% cat /adm/users
g%
Russ
next reply other threads:[~2000-07-13 20:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-13 20:43 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-14 7:40 okamoto
2000-07-14 8:07 ` Lucio De Re
2000-07-14 1:31 okamoto
2000-07-14 3:47 ` Lucio De Re
2000-07-13 18:34 pip
2000-07-13 16:18 Russ Cox
2000-07-13 15:34 Anthony Sorace
2000-07-14 9:17 ` Douglas A. Gwyn
2000-07-16 16:00 ` Lucio De Re
2000-07-13 14:11 jmk
2000-07-13 14:51 ` Lucio De Re
2000-07-14 19:02 ` Louis N. Beleos
2000-07-13 13:25 Anthony Sorace
2000-07-13 9:59 Michael Giegerich
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=200007132043.QAA11368@smtp3.fas.harvard.edu \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
--cc=migieger@vsnl.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).