From: Christopher Faylor <cgf@alum.bu.edu>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: overseers@gcc.gnu.org
Subject: Re: /var/ftp and ~ftp broken!
Date: Sun, 02 May 2004 15:51:00 -0000 [thread overview]
Message-ID: <20040502152116.GC18669@coe.bosbc.com> (raw)
In-Reply-To: <Pine.BSF.4.58.0405021404360.64607@acrux.dbai.tuwien.ac.at>
On Sun, May 02, 2004 at 03:08:12PM +0200, Gerald Pfeifer wrote:
>Who broke both /var/ftp and ~ftp, and why?
>
>I noticed that the public ftp data area now seems to reside in
> /sourceware/ftp/anonftp/pub
>and both /var/ftp and ~ftp are broken.
This has been the home of ftp since the machines inception, AFAIK.
The link was something that I added when the new sourceware was
brought online.
I don't know how the symlink evaporated. I did try an installation of
proftpd to see what would happen but the RPM intallation failed. It
sure didn't look like it got far enough to do any of this type of
damage but I guess that's the probable reason for this.
Anyway, I put the link back.
cgf
prev parent reply other threads:[~2004-05-02 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-02 15:21 Gerald Pfeifer
2004-05-02 15:51 ` Christopher Faylor [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=20040502152116.GC18669@coe.bosbc.com \
--to=cgf@alum.bu.edu \
--cc=gerald@pfeifer.com \
--cc=overseers@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).