From owner-freebsd-stable Tue Dec 21 19: 2:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 024BF14CAB for ; Tue, 21 Dec 1999 19:02:10 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 120c2R-0004Ww-00; Tue, 21 Dec 1999 19:02:07 -0800 Date: Tue, 21 Dec 1999 19:02:02 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Ben WIlliams Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Re[2]: SOFTUPDATES In-Reply-To: <9880.991221@Home.Com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 21 Dec 1999, Ben WIlliams wrote: > How far back is "used to"? I have a 3.2-RELEASE box that I tried > booting into single-user mode both via `shutdown now` and 'boot -s' > and couldn't get it to enable soft updates on /. When I did > `shutdown now` it would complete the `tunefs -n enable rwd0s1a` but Probably because the r* superblocks are kept in memory, and don't modify the ondisk superblock. I think tunefs needs some more IQ in what devices it modifies. tunefs is fine to use with r* devices if you just want to see what the current settings are. I think tunefs should refuse to use the raw device for updating parameters, and always use the raw device to display parameters (so that -p works when the file system is mounted). Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message