From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] boot via aan from fileserver?
Date: Fri, 30 Jan 2004 08:39:38 +0100 [thread overview]
Message-ID: <e637bb6a83a8b01af53ed4bf2410caf8@plan9.escet.urjc.es> (raw)
In-Reply-To: <200401292327.i0TNR3V07615@zamenhof.cs.utwente.nl>
> 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.
next prev parent reply other threads:[~2004-01-30 7:39 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 [this message]
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=e637bb6a83a8b01af53ed4bf2410caf8@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).