From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] boot via aan from fileserver?
Date: Sat, 31 Jan 2004 12:03:14 +0100 [thread overview]
Message-ID: <200401311103.i0VB3F518364@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Fri, 30 Jan 2004 08:39:38 +0100." <e637bb6a83a8b01af53ed4bf2410caf8@plan9.escet.urjc.es>
> > Out of curiousity:
> > would there have been a simpler way than the on I described above?
>
> I think I once did something similar but did not have to modify boot code.
> Sadly, I don't remember exactly what I did. Probably I did not used aan
> in the cpu server and thus didn't have to change things. It was when
> we had (well, we still have) a flaky network and had to import the venerable
> fs(8) into a cpu server to reexport it through tcp instead of il.
hmm. interesting.
In the mean time, after being away for a day, I find at home that
my connection has been down long enough such that a machine
booted 'normally' from the work fs gives the 'i/o on hungup channel'
whereas the 'tcpaan' booted one does not complain but simply
hangs and waits -- seems what I'm doing does not (yet?) give
me what I'm looking for...
The aan log on the cpu server only shows a last 'waiting for
connection message.
The result of ^t^tp on the client scrolls too fast to be able
to read the start, and ends up partially garbled on another
machine via serial cable
(fix this by playing with meessages to eia0 ctl?
or change baud rate in plan9.ini console entry?)
Got similar result after rebooting the machine and
(once up and having run for a while) unplugging its network cable
for a while and then plugging it back in.
Somehow it looks like the client doesn't notice the connection
is broken and something has to be done?
Too late to experiment more now. I'll try to find some time later
to play a bit with debugging on the client aan enabled.
(and a running snoopy)
Axel.
next prev parent reply other threads:[~2004-01-31 11:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 13:49 Axel Belinfante
2004-01-25 13:57 ` David Presotto
2004-01-26 8:19 ` Fco.J.Ballesteros
2004-01-29 23:27 ` Axel Belinfante
2004-01-30 7:39 ` Fco.J.Ballesteros
2004-01-31 11:03 ` Axel Belinfante [this message]
2004-01-31 16:44 ` Axel Belinfante
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=200401311103.i0VB3F518364@zamenhof.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--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).