From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: Re[2]: [9fans] diskless boot of one terminal off kfs machine
Date: Wed, 5 Feb 2003 17:33:12 +0100 [thread overview]
Message-ID: <73665946363e2389a4b708ad082a7811@plan9.escet.urjc.es> (raw)
In-Reply-To: <a7981f92a6653b12c82dba61c89a5a37@plan9.bell-labs.com>
[-- Attachment #1: Type: text/plain, Size: 104 bytes --]
That might be the reason it works fine here, then.
I run just one fossil to service several partitions.
[-- Attachment #2: Type: message/rfc822, Size: 1860 bytes --]
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: Re[2]: [9fans] diskless boot of one terminal off kfs machine
Date: Wed, 5 Feb 2003 11:04:26 -0500
Message-ID: <a7981f92a6653b12c82dba61c89a5a37@plan9.bell-labs.com>
> What was strange was the slow speed of the mkfs | mkext.
forsyth pointed out to me that if you run mkfs | mkext with
the source and destination on the same physical disk, it's
likely to be quite slow because kfs and fossil will fight over
the disk, causing a lot of seeking. it should be much faster to run
mkfs >/file/on/other/disk
mkext </file/on/other/disk
in fact, /file/on/other/disk could be a spare raw disk partition,
since the archive has its own eof marker.
prev parent reply other threads:[~2003-02-05 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 10:18 steve.simon
2003-02-05 10:31 ` Fco.J.Ballesteros
2003-02-05 16:04 ` Russ Cox
2003-02-05 16:33 ` Fco.J.Ballesteros [this message]
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=73665946363e2389a4b708ad082a7811@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).