Date: Thu, 16 May 2002 22:05:59 -0400 (EDT) From: Robert Watson <rwatson@FreeBSD.org> To: Adrian Chadd <adrian@FreeBSD.org> Cc: Terry Lambert <tlambert2@mindspring.com>, Julian Elischer <julian@elischer.org>, arch@FreeBSD.org Subject: Re: Future of IFS Message-ID: <Pine.NEB.3.96L.1020516220436.33209B-100000@fledge.watson.org> In-Reply-To: <20020516153123.A17588@roaming.cacheboy.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 16 May 2002, Adrian Chadd wrote: > 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 :-) Hey there Adrian! Well, that was an easy answer. :-) Feel free to start doing the whole commit thing again sometime, too :-) Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services 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?Pine.NEB.3.96L.1020516220436.33209B-100000>