Re: fdisk implementation [read this before deciding what to do]

[Bill Hacker <wbh@xxxxxxxxxxxxx>]

61842.GA93290@quark.hightek.org> <20090217175440.16920046@aNX>
In-Reply-To: <20090217175440.16920046@aNX>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 26
Message-ID: <499b08dd$0$880$415eb37d@crater_reader.dragonflybsd.org>
NNTP-Posting-Host: 61.10.57.144
X-Trace: 1234897118 crater_reader.dragonflybsd.org 880 61.10.57.144
Xref: crater_reader.dragonflybsd.org dragonfly.users:11979

Jost Tobias Springenberg wrote:
> Is there any chance of this moving forward ?
> As mentioned in my previous  post I really need this feature :). If you
> need any help or the like I would be more than happy to help and get
> this project on track again!
> Otherwise I might go back to were I started off and finish a new fdisk
> with less features myself.
> 
> Greetings,
> 	Tobi
> 

I need it also - even my laptop has all four *BSD on one HDD. One of the 
towers has those four, plus Solaris, Slackware, Minix, Syllable...

However ... I don't code 'C', and ASM is probably not in your plans...

But I sure can *test* on a wide range of MB, controllers, media, and 
'foreign' OS disk layouts.

The 'feature' I need most is an fdisk (and a disklabel) that at least do 
not harm what they cannot understand.

;-)

Bill