From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: [9fans] bitsy questions
Date: Mon, 13 May 2002 18:52:14 +0200 [thread overview]
Message-ID: <83bffd42261981d6c3e650cfad827289@plan9.escet.urjc.es> (raw)
I started to play w/ the bitsy, in part to adapt the sdata thing,
which seems that no longer works in the 4th edition. So my first
question is, anyone already doing this?
The second question is that I'm getting what I think are
ramfs crashes. They are quite reproducible, if I open in acme
/ or /bin I usually get a series of "Bseek: unknown state" messages
and then the fs no longer works. Anyone saw the same thing?
thanks
PS: I saw the console putchar disabled, enabled it, and it seems to work
fine. Ditto for suspend (which resets the thing by default). Bug or
feature?
next reply other threads:[~2002-05-13 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 16:52 Fco.J.Ballesteros [this message]
2004-03-09 16:06 [9fans] Bitsy questions (was: Plan 9 questions and quarrel) jmk
2004-03-12 19:13 ` [9fans] Bitsy questions Axel Belinfante
2004-03-15 9:38 ` Fco.J.Ballesteros
2004-03-15 9:46 ` Geoff Collyer
2004-03-16 13:21 ` Derek Fawcus
2004-03-16 13:26 ` lucio
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=83bffd42261981d6c3e650cfad827289@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--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).