From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] boot via aan from fileserver?
Date: Fri, 30 Jan 2004 00:27:03 +0100 [thread overview]
Message-ID: <200401292327.i0TNR3V07615@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Mon, 26 Jan 2004 09:19:57 +0100." <7936203a0948a36b8954bb9f3f73d4d1@plan9.escet.urjc.es>
nemo replied to my question about using aan to boot from fileserver:
> In the mean time you can perhaps reexport your
> worm fs form a cpu server, and use aan on that.
> But I'd say you better switch to fossil. You could
> have used aan directly then.
I'm now trying the reexport approach.
The simplest approach seemed to use import to get /root from
the cpu server, and let import use aan.
However, import -p uses /bin/aan, whereas in the boot trick
I will have /boot/aan. As work around I added a -P aanprog flag
to import, and hacked the boot code to have a new bootmethod 'tcpaan'
that run's this import to get /root from the cpu server,
in a way similar to fossil is started.
I at least succeeded to boot, and indeed aan is 'in' the connection,
as far as I can see.
I'll just let it run for some days and see what happens.\
Just curious: what network outage would I 'need' to benefit
from aan improved reliability?
(So far, I got the root fs via tcp over cable modem to cpu
which run trampoline to get to worm fs via il.)
Out of curiousity:
would there have been a simpler way than the on I described above?
And just one remark: once I had been browsing the boot code
enough to be a bit comfortable with its structure,
adding the new boot method turned out to be surprisingly simple
(the fact that all pieces I needed similar code already appeared
here and there (tcp, fossil boot) of course helped immensely)
Axel.
next prev parent reply other threads:[~2004-01-29 23:27 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 [this message]
2004-01-30 7:39 ` Fco.J.Ballesteros
2004-01-31 11:03 ` Axel Belinfante
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=200401292327.i0TNR3V07615@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).