9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: <plan9@itic.ca>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] bitsy kernel
Date: Sun, 28 Apr 2002 12:06:44 -0500	[thread overview]
Message-ID: <FIEDLHOOAEHBJAPIKGJCGECNCBAA.plan9@itic.ca> (raw)

hum...

``some'' files are missing as refered to in armpaq.proto @ lines :
10,103,104,106,135,138,139,141

Actually /sys/src/9/bitsy/paqfiles is missing...

"Sape Mullender" <sape@plan9.bell-labs.com> a crit dans le message news:<760cca84bf458bdd5671c5e905c4bd81@plan9.bell-labs.com>...
> A word of warning to bitsy users.  In cpurc (/sys/src/9/bitsy/paqfiles/cpurc),
> add a -n flag to factotum to prevent it from looking for secstore and asking
> for a password at a time when there is not yet a keyboard to read the password from.
> 
> 	Sape
> 



             reply	other threads:[~2002-04-28 17:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-28 17:06 plan9 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-28 15:33 Sape Mullender

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=FIEDLHOOAEHBJAPIKGJCGECNCBAA.plan9@itic.ca \
    --to=plan9@itic.ca \
    --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).