From: "Bryan O'Sullivan" <bos@serpentine.com>
To: nbecker@fred.net
Cc: linux-kernel@vger.kernel.org, Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: Whither autofs4?
Date: 30 Jan 2001 13:58:56 -0800 [thread overview]
Message-ID: <87r91kln1b.fsf@pelerin.serpentine.com> (raw)
In-Reply-To: <x88zog8ddtg.fsf@adglinux1.hns.com>
In-Reply-To: nbecker@fred.net's message of "30 Jan 2001 14:45:15 -0500"
n> What is the status of autofs4? There is no mention in
n> 2.4.0/Doc/Changes. There doesn't seem to be any activity in the
n> ftp.kernel.org/.../autofs area. Is autofs4 alive?
Yes, it is. Jeremy has been responding to bug reports and issuing new
userspace prereleases every so often. As far as I know, autofs4 has
been in fairly wide use for a while, and could reasonably be
considered stable (I've been using it since he started working on it,
with few problems).
<b
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-30 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 19:45 Whither autofs4? nbecker
2001-01-30 21:58 ` Bryan O'Sullivan [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=87r91kln1b.fsf@pelerin.serpentine.com \
--to=bos@serpentine.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbecker@fred.net \
/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