Re: boot0 and fdisk / disklabel misbehaviour

2003-11-13 Thread Rudolf Cejka
Rudolf Cejka wrote (2003/11/11): > And almost at the same time, I'm looking at the last change to > boot0.s 1.26, if there is forgotten TBL1SZ update, or not :o))) Just for record: I have submitted patch solving problems with bad information about partitions as kern/59256 right now. -- Rudolf Ce

Re: boot0 and fdisk / disklabel misbehaviour

2003-11-11 Thread Rudolf Cejka
Dag-ErlingSm?rgrav wrote (2003/11/11): > - boot0 off-by-one error: >The OS table in boot0.s is as follows: > .byte os_misc-. # Unknown > ... > .byte os_bsd-. # NetBSD >Now, boot0 identifies my FreeBSD partitions as "BSD" inst

Re: boot0 and fdisk / disklabel misbehaviour

2003-11-11 Thread Bruce Evans
On Tue, 11 Nov 2003, Dag-Erling [iso-8859-1] Smørgrav wrote: > I've been busy installing various OSes on a spare disk in order to try > to reproduce some of fefe's benchmarks. In the process, I've noticed > a couple of bogons in boot0 and disklabel: > > - disklabel -B trashes the partition table

Re: boot0 and fdisk / disklabel misbehaviour

2003-11-11 Thread Dag-Erling Smørgrav
Alexander Leidinger <[EMAIL PROTECTED]> writes: > Do you have a second disk in the system? Are you able to switch to the > second disk with boot0? I have a current system where I'm not able to > switch to the second disk (master on secondary ata channel). Yes, I can switch back and forth between t

Re: boot0 and fdisk / disklabel misbehaviour

2003-11-11 Thread Alexander Leidinger
On Tue, 11 Nov 2003 09:36:14 +0100 [EMAIL PROTECTED] (Dag-Erling Smørgrav) wrote: > - boot0 off-by-one error: >Now, boot0 identifies my FreeBSD partitions as "BSD" instead of >"FreeBSD". It also identifies my Debian partition (type 0x83) as >"BSD" instead of "Linux" and my Debian sw

Re: boot0 and fdisk / disklabel misbehaviour

2003-11-11 Thread Dag-Erling Smørgrav
[EMAIL PROTECTED] (Dag-Erling Smørgrav) writes: >This probably happens because fdisk silently allows the user to >create a partition that overlaps the partition table. Arguably >pilot error, but very confusing at the time, and fdisk should warn >about it. ...and here's the patch.