From: Stephen Parker <stephen.parker@pitechnology.com>
To: "'9fans@cse.psu.edu'" <9fans@cse.psu.edu>
Subject: RE: [9fans] boot halts after "version..."
Date: Fri, 3 May 2002 17:04:03 +0100 [thread overview]
Message-ID: <A12EAD94F69FD211ABB800805F650CC402CEE62F@eagle.pigroup.co.uk> (raw)
the system is at home and i'm not. but i tried typing a variety
of things at it and nothing had any effect until del. it could
be coincidence. it did respond to ^T^Tp but i didn't note the
results down. kfs and factotum were running.
i'll do further experiments.
stephen
--
Stephen Parker. Pi Technology. +44 (0)1223 203438.
> -----Original Message-----
> From: Russ Cox [mailto:rsc@plan9.bell-labs.com]
> Sent: 03 May 2002 16:42
> To: 9fans@cse.psu.edu
> Subject: Re: [9fans] boot halts after "version..."
>
>
> > after fiddling with plan9.ini my pc (boot and kfs off local drive)
> > now pauses after kfs... version...
> >
> > if i press del it continues to time... but otherwise hangs for
> > at least several minutes.
>
> what if you type "criswell" instead?
>
> i don't see why del should do anything -- del is only special
> to rio. as far as the kernel is concerned, del is just another
> keystroke at the point you're at.
>
> it could be that we've screwed up scheduling and typing
> generates interrupts which keep the system going, but i don't
> really think that's true. can you type ^t ^t p without
> making it continue? if so, it'd be nice to know what the
> kfs lines look like.
>
> russ
>
next reply other threads:[~2002-05-03 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 16:04 Stephen Parker [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-15 9:38 Stephen Parker
2002-05-10 4:26 rsc
2002-05-03 16:22 forsyth
2002-05-03 15:41 Russ Cox
2002-05-03 10:23 Stephen Parker
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=A12EAD94F69FD211ABB800805F650CC402CEE62F@eagle.pigroup.co.uk \
--to=stephen.parker@pitechnology.com \
--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).