From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plan 9 ports to unix (including libdraw)
Date: Mon, 20 Oct 2003 10:50:18 +0200 [thread overview]
Message-ID: <3279e1cac4e41327cb86a2b28ec29bdd@plan9.escet.urjc.es> (raw)
In-Reply-To: <df0294ec5aceae44f5797c4640e175a0@granite.cias.osakafu-u.ac.jp>
[-- Attachment #1: Type: text/plain, Size: 398 bytes --]
Doesnt have to be a difference if you don't want to have it. For us, our fileserver
is also a regular cpuserver used just for the web, mail, and the like. But you could
certainly use it to export your fossil to the network and nothing else; and it would
behave like the old worm. In fact, we are not even exporting venti, since it
runs only on a loopback interface to service fossil requests.
[-- Attachment #2: Type: message/rfc822, Size: 2080 bytes --]
From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plan 9 ports to unix (including libdraw)
Date: Mon, 20 Oct 2003 17:45:17 +0900
Message-ID: <df0294ec5aceae44f5797c4640e175a0@granite.cias.osakafu-u.ac.jp>
> i'd have thought the auth could happily coexist, though:
So, you think that we don't worry about to have AUTH + Fosssil + Venti
on a machine. I'm not a speciallist of computer security. I'd like to know
what is the difference between old file server and new fossil + etc, the
former was a standalone machine, and the latter can be a network machine.
Kenji
next prev parent reply other threads:[~2003-10-20 8:50 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 16:30 David Presotto
2003-10-20 2:01 ` okamoto
2003-10-20 6:33 ` Nigel Roles
2003-10-20 8:29 ` Charles Forsyth
2003-10-20 8:45 ` Fco.J.Ballesteros
2003-10-20 8:45 ` okamoto
2003-10-20 8:50 ` Fco.J.Ballesteros [this message]
2003-10-20 17:21 ` ron minnich
2003-10-20 19:30 ` Charles Forsyth
2003-10-20 19:40 ` ron minnich
2003-10-20 20:07 ` mirtchov
2003-10-20 20:14 ` ron minnich
2003-10-20 21:08 ` David Presotto
2003-10-20 21:08 ` Enache Adrian
2003-10-20 21:17 ` mirtchov
2003-10-20 21:23 ` Scott Schwartz
2003-10-20 21:39 ` Skip Tavakkolian
2003-10-20 23:12 ` Geoff Collyer
2003-10-21 1:16 ` okamoto
2003-10-21 2:48 ` okamoto
2003-10-21 3:23 ` Russ Cox
2003-10-21 3:33 ` okamoto
2003-10-21 3:56 ` Russ Cox
2003-10-21 4:01 ` ron minnich
2003-10-21 12:05 ` David Presotto
2003-10-21 6:28 ` Nigel Roles
2003-10-21 7:37 ` Richard Miller
2003-10-22 2:01 ` Adrian Tritschler
2003-10-21 9:39 ` a
2003-10-21 14:01 ` paurea
2003-10-21 16:05 ` C H Forsyth
2003-10-21 17:11 ` Fco.J.Ballesteros
2003-10-21 11:20 ` Charles Forsyth
-- strict thread matches above, loose matches on Subject: below --
2003-10-17 18:21 Caerwyn B Jones
2003-10-17 20:35 ` Derek Fawcus
2003-10-17 15:48 matt
2003-10-17 16:02 ` Nigel Roles
2003-10-17 16:14 ` matt
2003-10-17 15:13 Richard C Bilson
2003-10-17 13:03 Caerwyn B Jones
2003-10-13 18:31 Russ Cox
2003-10-13 21:34 ` Caerwyn Jones
2003-10-14 0:53 ` arisawa
2003-10-14 18:09 ` andrey mirtchovski
2003-10-14 18:10 ` andrey mirtchovski
2003-10-17 2:53 ` Richard C Bilson
2003-10-17 3:02 ` William Josephson
2003-10-17 9:42 ` a
2003-10-17 14:30 ` Joel Salomon
2003-10-17 14:38 ` Joel Salomon
2003-10-17 23:57 ` Bruce Ellis
2003-10-17 17:25 ` Roman Shaposhnick
2003-10-17 18:00 ` matt
2003-10-17 18:06 ` Roman Shaposhnick
2003-10-17 21:16 ` matt
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=3279e1cac4e41327cb86a2b28ec29bdd@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).