🚀 go-pugleaf

fmeissch@eduserv2.rug.ac.be (Frank Meisschaert) writes:

> I'm running FreeBSD together with linux on my computer. The disk is divided
> as follows: a small part with lilo and the kernel, then FreeBSD and then
> linux. Now I decided to install slackware in stead of RedHat. The bootdisk
> contains a kernel which recognizes the bsd disk partitions, fdisk doesn't
> know about them. However fdisk tells the install program where the linux
> partitions are, in my case hda5 - hda9, which for the kernel are hda11 -
> hda15. So first I overwrited some of the bsd partitions (I accepted
> hda5-hda9). Luckily one of the bsd partitions ran full, so no more damage
> could be done. I then reinstalled slackware but before I ran setup I deleted
> the hda5-9 entries in /dev (on the ramdisk image) and remade them with minor
> number 11-15. Installation was a succes (after I changed the entries in
> fstab, of course).

I've not heard of fdisk not seeing partitions, but once I found cfdisk
assigned partition numbers to partitions in a more desirable order than
fdisk did.  Seems strange that they wouldn't be the same for all SW.


Gary's Encyclopedia ( http://www.aa.net/~swear/pedia/ ) has this:

      <A HREF="http://www.eklektix.com/lwn/980514/a/fdisk.html">
        Article comparing Disk Druid, fdisk, cfdisk, sfdisk </A>
        (by maintainer; says fdisk has problems)

which doesn't sound good either.  Sounds like it's time for some
brave soul to dig into it and drive forward an effort to fix this
situation, or at least describe it well.