more on my problem so in fact I created my sda2 partition with cfdisk and tagged it with 0xbf for solaris. (I was lucky to use the good one not 0x82) and then installed opensolaris 2009.06 on it
and now when i boot into linux, I noticed nautilus was reporting some strange 8Mb partition along side 2 16Gb partitions. and I finally understood it's what the kernel see from the solaris partition (the slices) in dmesg i got sda2: <solaris: [s0] sda13 [s2] sda14 [s8] sda15 > s0 is / the only partition used with zfs s2 is the whole disk/partition as VTOC standard and s8 is the boot partition the 8Mb unused and free. so I got my 3 partitions found in nautilus so the kernel got it right. and HAL use that to show it in nautilus. but as soon i run gparted, those partitions disapear in nautilus. i guess gparted use something like partprobe and force the kernel to see something wrong ! why (g)parted can't use what's seen by the kernel instead of doing its wrong magic thing here ? why can't it simply use the partition type in partition table ? at least as a hint ? the 0xbf partition type to try to read a solaris partition _______________________________________________ bug-parted mailing list bug-parted@gnu.org http://lists.gnu.org/mailman/listinfo/bug-parted
