From owner-freebsd-current Mon Jan 27 18:24:42 2003 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id B87E737B401; Mon, 27 Jan 2003 18:24:40 -0800 (PST) Date: Mon, 27 Jan 2003 18:24:40 -0800 From: Juli Mallett To: Conrad Sabatier Cc: current@FreeBSD.ORG Subject: Re: tunefs using libufs. Message-ID: <20030127182440.A16715@FreeBSD.org> References: <20030117211040.B20672@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from conrads@cox.net on Mon, Jan 27, 2003 at 08:19:07PM -0600 Organisation: The FreeBSD Project X-Alternate-Addresses: , , , , X-Towel: Yes X-LiveJournal: flata, jmallett X-Negacore: Yes Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * De: Conrad Sabatier [ Data: 2003-01-27 ] [ Subjecte: Re: tunefs using libufs. ] > I'm getting some odd behavior with tunefs (5.0-CURRENT cvsupped and built > Sunday, Jan 26). If a filesystem, rather than an actual device, is specified, > it spits out a weird error message regarding my linproc mount: > > # tunefs -p /tmp > tunefs: linproc: could not find special device > > My /etc/fstab: > > # Device Mountpoint FStype Options Dump Pass# > /dev/ad0s1b none swap sw 0 0 > /dev/ad0s1a / ufs rw 1 1 > /dev/ad0s1f /tmp ufs rw 2 2 > /dev/ad0s1g /usr ufs rw 2 2 > /dev/ad0s1e /var ufs rw 2 2 > /dev/acd0c /cdrom cd9660 ro,noauto 0 0 > /dev/acd1c /cdrom1 cd9660 ro,noauto 0 0 > proc /proc procfs rw 0 0 > /dev/ad1s1e /mm ufs rw 2 2 > linproc /compat/linux/proc linprocfs rw 0 0 > > Is anyone else seeing this? Could it just be the result of the gcc > optimizations I'm using (an admittedly heavy set of flags)? Or might it be > related to the recent changes the OP mentioned? Now that libufs will hunt for the disk, tunefs shouldn't, that's all. Doing it both shouldn't have caused a problem, I don't think, but it does for me, too. This is caused by more-recent changes to libufs. I'll commit a fix shortly, once I verify the behaviour is correct. -- Juli Mallett AIM: BSDFlata -- IRC: juli on EFnet OpenDarwin, Mono, FreeBSD Developer ircd-hybrid Developer, EFnet addict FreeBSD on MIPS-Anything on FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message