* De: Conrad Sabatier <[EMAIL PROTECTED]> [ 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 <[EMAIL PROTECTED]>
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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
