Date: Thu, 16 May 2002 15:31:50 +0800 From: Adrian Chadd <adrian@FreeBSD.org> To: Robert Watson <rwatson@FreeBSD.org> Cc: Terry Lambert <tlambert2@mindspring.com>, Julian Elischer <julian@elischer.org>, arch@FreeBSD.org Subject: Re: Future of IFS Message-ID: <20020516153123.A17588@roaming.cacheboy.net> In-Reply-To: <Pine.NEB.3.96L.1020515094457.80385D-100000@fledge.watson.org>; from rwatson@FreeBSD.org on Wed, May 15, 2002 at 09:53:54AM -0400 References: <3CE1FCFE.A2602D49@mindspring.com> <Pine.NEB.3.96L.1020515094457.80385D-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 15, 2002, Robert Watson wrote: > As I said, there are really two options following the UFS2 commit: > disconnect it from the build if the maintainer hasn't updated it yet, or > remove it until the maintainer replaces it. If Adrian is willing to do > the work, that's great; if he's not, we'll need to find a maintainer. But > even if he is the maintainer, my impression from a conversation with him > is that he plans to reimplement it *anyway*, making removal of the current > IFS non-harmful during the "UFS2 is added but before IFS is replaced" > window. In the event he does plan to "start from" the current code, it > will all still be there in the Attic where it can be easily recovered > (some files never die...). Another choice would be for the maintainer to > do what is being done from ext2fs: divorce it from the UFS implementation > entirely, so that it does get mixed up in the UFS/FFS changes. Kill it. I'll revisit it after the filesystem changes have settled down. (Hi all :-) adrian -- Adrian Chadd "Programming is like sex: <adrian@freebsd.org> One mistake and you have to support for a lifetime." -- rec.humor.funny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020516153123.A17588>