Date: Tue, 13 Aug 2002 08:41:57 -0400 (EDT) From: Robert Watson <rwatson@FreeBSD.org> To: Poul-Henning Kamp <phk@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/ufs/ffs ffs_vfsops.c ffs_vnops.c Message-ID: <Pine.NEB.3.96L.1020813083945.80589C-100000@fledge.watson.org> In-Reply-To: <200208131033.g7DAXvcY054080@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 13 Aug 2002, Poul-Henning Kamp wrote: > phk 2002/08/13 03:33:57 PDT > > Modified files: > sys/ufs/ffs ffs_vfsops.c ffs_vnops.c > Log: > Unravel the UFS_EXTATTR incest between FFS and UFS: UFS_EXTATTR is an > UFS only thing, and FFS should in principle not know if it is enabled > or not. > > This commit cleans ffs_vnops.c for such knowledge, but not ffs_vfsops.c Yeah, what was missing when I originally dropped this in was mount and unmount events from FFS to UFS allowing file systems based on UFS to notify UFS when mount and unmount occurred. This would allow UFS to perform UFS-specific initialization, such as extattr initialization, if it was need. This would also pull the UFS aspects of mount and unmount into UFS rather than have them happen in FFS. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" 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.1020813083945.80589C-100000>