From: Daniel Egger <degger@fhm.edu>
To: Eric Sandall <eric@sandall.us>
Cc: linux-kernel@vger.kernel.org
Subject: Re: srfs - a new file system.
Date: Fri, 24 Oct 2003 01:15:00 +0200 [thread overview]
Message-ID: <1066943094.1686.36.camel@sonja> (raw)
In-Reply-To: <1066934851.3f982243bc9a8@horde.sandall.us>
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
Am Don, den 23.10.2003 schrieb Eric Sandall um 20:47:
> Agreed, more DFS' are always good. As for Coda, it has compiled fine for me for
> the last year (with some bison patches), but I have not actually tried it yet.
> NFS may be slow, but at least it works and I haven't lost any files due to
> using it.
The slowless of NFS is not an issue for me (actually I'm getting quite
good performance over a switched 100Mbit network). However it doesn't
replicate which is annoying when being much on the road but normally
also using lots of computers in the lab.
--
Servus,
Daniel
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-23 23:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.44.0310070757400.4688-100000@sundance.cse.ucsc.edu>
2003-10-20 9:12 ` srfs - a new file system Nir Tzachar
2003-10-20 21:00 ` Eric Sandall
2003-10-21 12:07 ` Nir Tzachar
2003-10-21 14:29 ` Brian Beattie
2003-10-23 13:58 ` Pavel Machek
2003-10-24 9:28 ` Nir Tzachar
2003-10-23 17:46 ` Daniel Egger
2003-10-23 18:47 ` Eric Sandall
2003-10-23 23:15 ` Daniel Egger [this message]
2003-10-24 15:45 ` srfs - a new file system.--OT Gadgeteer
2003-10-24 9:26 ` srfs - a new file system Nir Tzachar
2003-10-22 4:57 ` Erik Andersen
2003-10-22 10:16 ` Nir Tzachar
2003-10-22 10:21 ` Nir Tzachar
2003-10-22 16:05 ` Valdis.Kletnieks
2003-10-22 19:38 ` Erik Andersen
2003-10-23 5:20 ` Miles Bader
2003-10-23 5:37 ` Valdis.Kletnieks
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=1066943094.1686.36.camel@sonja \
--to=degger@fhm.edu \
--cc=eric@sandall.us \
--cc=linux-kernel@vger.kernel.org \
/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