[BusyBox] fdisk with entries not in disk order pb.
Erik Andersen
andersen at codepoet.org
Fri May 14 22:30:33 UTC 2004
On Fri May 14, 2004 at 12:46:24PM +0400, Vladimir N. Oleynik wrote:
> magicfox,
>
> >I used recently fdisk to remember which extra partition number to mount
> >on busybox. The mount is not a pb. but when entries are not in disk
> >order, the informations displayed seems to be wrong.
> >
> >Busybox fdisk:
> >-------------
> ># fdisk -l /dev/hda
> >Warning: ignoring extra data in partition table 5
> >Warning: ignoring extra data in partition table 5
> >Warning: ignoring extra data in partition table 6
> >Warning: invalid flag 0x1ac9 of partition table 5 will be corrected by
> >w(rite)
> >Warning: invalid flag 0x0026 of partition table 6 will be corrected by
> >w(rite)
> >
> >Disk /dev/hda: 40.0 GB, 40027029504 bytes
> >255 heads, 63 sectors/track, 4866 cylinders
> >Units = cylinders of 16065 * 512 = 8225280 bytes
> >
> > Device Boot Start End Blocks Id System
> >/dev/hda1 * 1 1992 16000708+ 83 Linux
> >/dev/hda2 1993 4866 23085405 5 Extended
> >/dev/hda5 ? 85074 164322 636558932 af Unknown
> >/dev/hda6 ? 105121 250671 1169129465 ff Unknown
>
> I haven`t problem with large disk with busybox-1.0pre7.
> Current busybox fdisk works invalid with large disk without
> support large files.
> I don`t like last Erik`s fdisk changes.
> Erik don`t say, why applied this changes again and again. :(
You mean ripping out all that lseek wrapper nonsense? I applied
that because the lseek wrapper junk was stupid. If you feel
fdisk needs to support large disks without busybox large file
support, I suppose I would be willing to unconditionally use
lseek64()...
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
More information about the busybox
mailing list