In message [EMAIL PROTECTED], Warner Losh writes:
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: It seems that our new boot blocks doesn't like the taste of disks
: prepared according to the meagre information we have in the handbook.
How does this script differ from 'disklabel -w wd0
What fails? Can you be more specific? How recent are your boot1/boot2
blocks? I would be inclined to dd at least 8k over the front of the
disk myself, but I don't think that's relevant in your case.
Disk error #1 while trying to load boot/loader. I think the bios
in this case trust
On Tue, 3 Aug 1999, Bruce Evans wrote:
My semantics may be wrong on these two: what I'm talking about is
what is in handbook chapter 8 "Using command line utilities " gives
you a disk which doesn't boot.
Ok; of those two examples, the first should give you a truly dedicated
disk.
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: My real beef here is not with the boot failure but with the fact that our
: command line tools stink when I bring in a new blank disk...
Yes. Several times I've hit this problem, but have never been PO'd
enough to fix it...
Warner
To
It seems that our new boot blocks doesn't like the taste of disks
prepared according to the meagre information we have in the handbook.
The following script seems to DTRT for me, and should really be
either integrated into a "fdisk -A" flag or maybe as a stand alone
script. Either way: manpage
On Sun, Aug 01, 1999 at 04:19:52PM +0200, Poul-Henning Kamp wrote:
The following script seems to DTRT for me, and should really be
either integrated into a "fdisk -A" flag or maybe as a stand alone
script. Either way: manpage handbook needs updated too.
What, specifically, is wrong with
In message [EMAIL PROTECTED], Nik Clayton writes:
On Sun, Aug 01, 1999 at 04:19:52PM +0200, Poul-Henning Kamp wrote:
The following script seems to DTRT for me, and should really be
either integrated into a "fdisk -A" flag or maybe as a stand alone
script. Either way: manpage handbook needs
In message [EMAIL PROTECTED], Bruce Evans writes:
All of the above only work for the easy case where the whole disk is
being labelled. In general, the disk size must be reduced to the slice
size before applying a label to a slice.
And that is the problem, it seems that "dangerously dedicated"
In message [EMAIL PROTECTED], Mike Smith writes:
In message [EMAIL PROTECTED], Bruce Evans writes:
All of the above only work for the easy case where the whole disk is
being labelled. In general, the disk size must be reduced to the slice
size before applying a label to a slice.
And
In message [EMAIL PROTECTED], Mike Smith writes:
In message [EMAIL PROTECTED], Bruce Evans writes:
All of the above only work for the easy case where the whole disk is
being labelled. In general, the disk size must be reduced to the slice
size before applying a label to a slice.
In message [EMAIL PROTECTED], Mike Smith writes:
My semantics may be wrong on these two: what I'm talking about is
what is in handbook chapter 8 "Using command line utilities " gives
you a disk which doesn't boot.
Ok; of those two examples, the first should give you a truly dedicated
disk.
11 matches
Mail list logo