From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kfs file size limit?
Date: Tue, 22 Apr 2003 23:15:13 -0700 [thread overview]
Message-ID: <9be0a310e443acc6cc6187237ad290a2@collyer.net> (raw)
In-Reply-To: <415dafad78692570bfdbf128c8896dc7@granite.cias.osakafu-u.ac.jp>
On second thought, if the kfs is also the laptop's root file system,
boot the laptop using another file server as root (the way normal
diskless terminals boot), then ream the kfs as I suggested in my
previous message, then reload the kfs.
next prev parent reply other threads:[~2003-04-23 6:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 3:29 okamoto
2003-04-23 4:44 ` Geoff Collyer
2003-04-23 5:28 ` okamoto
2003-04-23 6:11 ` Geoff Collyer
2003-04-23 6:15 ` Geoff Collyer [this message]
2003-04-23 9:24 ` okamoto
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=9be0a310e443acc6cc6187237ad290a2@collyer.net \
--to=geoff@collyer.net \
--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).