misc/38582: sysinstall sets newfs flag after changing
mount point
Craig Carey
snowfall at gmx.co.uk
Tue Aug 12 07:10:23 PDT 2003
The following reply was made to PR misc/38582; it has been noted by GNATS.
From: Craig Carey <snowfall at gmx.co.uk>
To: freebsd-gnats-submit at FreeBSD.org
Cc: nludban at columbus.rr.com, ob at www.partner.de
Subject: Re: misc/38582: sysinstall sets newfs flag after changing
mount point
Date: Wed, 13 Aug 2003 02:05:27 +1200
I note that these two problem reports appear to be reporting the same
problem:
misc/38582:
"sysinstall sets newfs flag after changing mount point" [26 May 2002]
http://www.freebsd.org/cgi/query-pr.cgi?pr=misc/38582
bin/31837: "sysinstall change mountpoint" [7 Nov 2001]
"... then ... change the mount point in the disk labeling, the newfs
flag switch from no format to newfs !.
http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/31837
PS. Sysinstall has 2 bugs that could result in loss of over xxxxGB per
user:
http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/47384 [22 Jan 2003]
"Machine has two disks, ad0 (existing 5.0 system) and da0 (scratch
disk). Selecting da0 as the target for 'partition' and then
following that by the sequence 'label/distribution/commit'
results in a wiped ad0."
http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/29375
"the disk editor used by /stand/sysinstall gets confused by
slices that are not labelled in order and writes the
partition table incorrectly."
-- C Carey
More information about the freebsd-qa
mailing list