From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cifs guinea pig wanted
Date: Thu, 1 Jul 2004 12:23:29 +0100 [thread overview]
Message-ID: <2504fb0feb9a5aaa2750f3801f06adb7@quintile.net> (raw)
In-Reply-To: <000601c45eff$45140d70$d1fa7d50@SOMA>
I have no choice as our Novell servers are about
to be replaced with Windows servers.
Its a matter of need rather than informed choice.
You known when you are really starting to understand CIFS,
when you get to the point where you cannot beleive that the
designers where that incompetent, and start to wonder if
it was deliberatly obfuscated.
-Steve
next prev parent reply other threads:[~2004-07-01 11:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 17:12 Steve Simon
2004-06-30 18:11 ` Fco. J. Ballesteros
2004-07-01 0:00 ` Adrian Tritschler
2004-07-01 0:06 ` boyd, rounin
2004-07-01 2:02 ` Kenji Okamoto
2004-07-01 2:12 ` Jack Johnson
2004-07-01 11:23 ` Steve Simon [this message]
2004-07-01 5:20 ` lucio
2004-07-01 8:49 ` vdharani
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=2504fb0feb9a5aaa2750f3801f06adb7@quintile.net \
--to=steve@quintile.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).