aboot not working or something

[bdina at seresc.net]

Quoting Michal Jaegermann <michal at ellpspace.math.ualberta.ca>:
> 
> I cannot check that at this moment but it somehow hard to believe
> that 'fdisk' you got on  AC-0.9 CDs is unable to write disklabels.
> As a matter of fact 'b' is really a regular facility for a Linux
> fdisk even if it is not used that often on a given platform.  I just
> looked on x86 and x86_64 installations and surely enough it is
> there. 
>

I agree.  Somehow though something has changed.
 
> >  fdisk does always report it starts in BSD disklabel.
> 
> Maybe that is a reason that 'b' is then turned off?  In any case if
> you are printing partition tables then printouts for both types are
> quite distinct so it is hard to take one for another.  If you do have
> disklabel and you left unpartioned space at a disk start for aboot
> then you are set.  /etc/aboot.conf is only a convenience.  You can
> boot with '-fl i' and type whatever you desire at aboot prompt which
> will then show up. /etc/aboot.conf can be added later.
>

why would my fdisk start in BSD disklabel, there must be data somewhere on that
disk that is causing that.

That (fdisk starting in BSD disklabel) must be why 'b' is turned off.  

I have left unpartitioned space (after the manual partitioning), however it is
not as clean as I would like it to be, seeing as how I have the Free space, and
the Foreign space.  Something is screwed up and I feel that I will need a "real"
fresh start to correct everything.  I am going to try tomorrow and low level
format the disk, and start over.  I am just going to boot from the CD, and use
dd to remove all data.  Maybe that will get me back to normal.  I should be able
to follow the directions I posted to the list, if I can't then something is
wrong, and could cause other things down the line to also be wrong.

--Bryan

----------------------------------------------------------------------
This mail sent through Horde-Toaster (http://qmailtoaster.clikka.com/)