From owner-freebsd-current Mon Mar 9 22:54:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26969 for freebsd-current-outgoing; Mon, 9 Mar 1998 22:54:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from luoqi.watermarkgroup.com (luoqi.watermarkgroup.com [207.202.73.170]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26946 for ; Mon, 9 Mar 1998 22:54:25 -0800 (PST) (envelope-from src@luoqi.watermarkgroup.com) Received: (from src@localhost) by luoqi.watermarkgroup.com (8.8.8/8.8.8) id BAA00289 for current@freebsd.org; Tue, 10 Mar 1998 01:54:20 -0500 (EST) (envelope-from src) Date: Tue, 10 Mar 1998 01:54:20 -0500 (EST) From: Source Code Message-Id: <199803100654.BAA00289@luoqi.watermarkgroup.com> To: current@FreeBSD.ORG Subject: Enabling softupdates for root filesystem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With the lastest softupdates code cvsupped, there's no way to enable softupdates for the root partition, no matter what I tried (single user, fixit floppy, boot off another disk). It turned out that when upgrading the root mount from r/o to r/w, no attempt was made to enable the softupdate code. The following patch would do the trick, Index: ffs_vfsops.c =================================================================== RCS file: /fun/cvs/src/sys/ufs/ffs/ffs_vfsops.c,v retrieving revision 1.76 diff -u -r1.76 ffs_vfsops.c --- ffs_vfsops.c 1998/03/08 09:59:06 1.76 +++ ffs_vfsops.c 1998/03/10 06:38:39 @@ -241,6 +241,12 @@ VOP_UNLOCK(devvp, 0, p); } + if ((fs->fs_flags & FS_DOSOFTDEP) && + (error = softdep_mount(ump->um_devvp, mp, + fs, p->p_ucred)) != 0) { + return (error); + } + fs->fs_ronly = 0; } if (fs->fs_ronly == 0) { ----------- -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message