From: Kai.Grossjohann@CS.Uni-Dortmund.DE
Subject: Re: ftp news server?
Date: 19 Mar 1999 18:41:22 +0100 [thread overview]
Message-ID: <vaf7lsdgywt.fsf@ramses.cs.uni-dortmund.de> (raw)
In-Reply-To: Shaun Lipscombe's message of "19 Mar 1999 17:28:21 +0000"
Shaun Lipscombe <shaun.lipscombe@gasops.co.uk> writes:
> As gnus can use ange-ftp to read a directory of files as if it were a
> news server, I was wondering if it were possible to set up an ftp
> server, and have lots of emacsen connected to it around the company,
> so that our internal ftp server can be used as an internal bulletin
> board without the hassle of setting up INN.
Well, nndoc groups are read-only, as a nneething groups.
But maybe something useful happens if you create an nnmh group and
change its directory to an ange-ftp directory.
Please take note that Gnus expects to be the *only* program writing
its directories and files. nnmh is the backend with the fewest
problems in this regard. But you're asking for trouble if you let two
Gnusae or Gnus and an external program write to the same directory/file.
kai
--
I like _\bb_\bo_\bt_\bh kinds of music.
parent reply other threads:[~1999-03-19 17:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <wkemmlpex6.fsf@mail.gasops.co.uk>]
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=vaf7lsdgywt.fsf@ramses.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).