Date: Mon, 9 Apr 2001 21:18:12 -0700 From: Danny Howard <dannyman@tellme.com> To: Greg Lehey <grog@lemis.com> Cc: FreeBSD Questions <questions@FreeBSD.org>, freebsd-stable@freebsd.org Subject: Re: fdisk & disklabel dont work! Message-ID: <20010409211812.P59290@tellme.com> In-Reply-To: <20010410113808.K64481@wantadilla.lemis.com>; from grog@lemis.com on Tue, Apr 10, 2001 at 11:38:08AM %2B0930 References: <20010409185759.N59290@tellme.com> <20010410113808.K64481@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Okay.
Well, FWIW, fdisk -I does *not* work successfully for me, under any
circumstances I've tried so far.
I have found a work-around, though:
TERM=cons25 # If serial console, set this to vt100
export TERM
/stand/sysinstall nonInteractive=YES partition=all bootManager=standard \
disk=${disk} diskPartitionEditor diskPartitionWrite
Woohah!
Interestingly enough, I see the same complaints about there not being a
disklabel, but my subsequent disklabel commands work. To whit:
disk=${disk}s1
disklabel -r -w $disk auto
disksize=`disklabel $disk | awk -F : '$1 == "sectors/unit" {print $2}'`
[...]
disklabel $disk | grep -v ' c:' > /tmp/mylabel
disklabel -R -B $disk /tmp/mylabel
And then some MAKEDEV, newfs, distributions, packages, config files, etc.
Okay, so I'll need to test this some more, but this is a pleasant
break-through for the evening. One which I hope will hold. :)
This is way screwed up, imho. I might investigate some day as to why
sysinstall can do what fdisk -I can not, but I have some machines that are
overdue for installs. :)
-danny
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010409211812.P59290>