Installing DragonFly

[Colin Adams]

If I add an extra initial line:

4 partitions:

Then I no longer get the error message.
But it does say sector size 0, and just typing:

disklabel ad0s1

shows the same information as before.

2009/4/20 Colin Adams <colinpauladams at googlemail.com>:
> I also tried saving the output from disklabel ad0s1 and just using the
> last part of that.
> But I get the same error messages. It looks like a bug in disklabel to me.
>
> 2009/4/20 Colin Adams <colinpauladams at googlemail.com>:
>> Thanks.
>>
>> I am having problems with the disklabel.
>>
>> I get:
>>
>> line 2: partition name out of range a-`: a
>>
>> and similar for lines 3 - 5
>>
>> I tried reading the disklabel man page, but could not find anything
>> that said where I was going wrong.
>>
>> P.S. I have a UK keyboard - this is not recognised. I work round it by
>> typing SHIFT-3 (£) to produce a #, but I wonder
>> if this might be relevant (though I can't think why it should be).
>>
>> 2009/4/19 Michael Neumann <mneumann at ntecs.de>:
>>> Am Sonntag, 19. April 2009 14:30:56 schrieben Sie:
>>>> But I don't want to install on Hammer. I only have 160GB disk, and
>>>> Matt has said you shouldn't consider Hammer on less than 500GB, if I
>>>> remember rightly.
>>>
>>> You don't have to. The instructions are similar for UFS. Replace
>>> newfs_hammer with newfs for example and ignore all Hammer related stuff.
>>>
>>> Take a look at /usr/share/examples/rconfig/auto.sh .
>>> It should be available on the installer CD. It's an example how to
>>> install DragonFly without the installer using UFS. Of course you need to
>>> change "fdisk -IB $disk" into "fdisk -IB -C $disk" in this file.
>>>
>>> If you have any further questions, please ask.
>>>
>>> Regards,
>>>
>>>  Michael
>>>
>>>
>>>>
>>>> 2009/4/19 Michael Neumann <mneumann at ntecs.de>:
>>>> > On Sat, 18 Apr 2009 09:00:21 +0100
>>>> >
>>>> > Colin Adams <colinpauladams at googlemail.com> wrote:
>>>> >> 2009/4/18 Jordan Gordeev <jgordeev at dir.bg>:
>>>> >> > Colin Adams wrote:
>>>> >> >> I don't know if it is the same problem (it certainly sounds
>>>> >> >> similar).
>>>> >> >>
>>>> >> >> This is not a laptop though. Nor is it an old machine (less
>>>> >> >> than 3 years old).
>>>> >> >>
>>>> >> >> Anyway, I have booted DragonFly from the live CD and logged in
>>>> >> >> as root.
>>>> >> >>
>>>> >> >> But what device name do I use (I only have one disk)?
>>>> >> >> Everything I guessed at, it says "device not configured".
>>>> >> >>
>>>> >> >> 2009/4/17 Michael Neumann <mneumann at ntecs.de>:
>>>> >> >
>>>> >> > Try ad0 or sd0.
>>>> >> > You should look at dmesg(8) output and see what devices the
>>>> >> > kernel has recognised (and what names they got).
>>>> >>
>>>> >> I had already tried ad0.
>>>> >>
>>>> >> dmesg revealed that the disk hadn't been seen at all. Perhaps I
>>>> >> plugged it in too late. Re-booting and re-plugging really early
>>>> >> did the trick (it was ad0, which was where the live DVD installed
>>>> >> DragonFly yesterday).
>>>> >>
>>>> >> so fdisk -C ad0 says (slightly abbreviated):
>>>> >>
>>>> >> cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl)
>>>> >>
>>>> >> Media sector size is 512 bytes.
>>>> >> Warning: BIOS sector numbering starts with sector 1
>>>> >> Information form DOS bootblock is:
>>>> >> The data for partition 1 is:
>>>> >> ssysid 165,(DragonFly/FreeBSD/NetBSD/386BSD)
>>>> >>         start 63, size 312581745 (152627 Meg), flag 80 (active)
>>>> >>              beg: cyl 0/ head 1/ sector 1;
>>>> >>              end: cyl 1023/ head 255/ sector 63
>>>> >> partitions 2 3 and 4 <UNUSED>
>>>> >>
>>>> >> So where do I go from here?
>>>> >
>>>> > Basically, follow those instructions below, replacing ad4 with ad0,
>>>> > and "fdisk -B -I ad4" with "fdisk -B -I -C ad0". You simply have to
>>>> > by-pass the installer, because it doesn't use the "-C" option in
>>>> > fdisk, which is essential!
>>>> >
>>>> > http://www.ntecs.de/blog/articles/2008/07/30/dragonfly-on-hammer/
>>>> >
>>>> > The instructions above are a bit outdated, but they should still
>>>> > work. You can stop the instructions after "reboot".
>>>> >
>>>> > Regards,
>>>> >
>>>> >  Michael
>>>
>>> --
>>> Rubyist for over a decade
>>>
>>
>