mdconfig, bsdlabel, disktab

[Samuel Martín Moro]

A few checks later: it seems that my problem isn't related to bsdlabel.

I scpied images generated (dd+bsdlabel) on 7.2 to the 8.1 host, and vice
versa.
It seems that when I mdconfig -a -f $file the 7.2 img on the 8.1 host,
/dev/md${x}c doesn't appear.
But when I add the 8.1 image on the 7.2 host, /dev/md${x}c is correctly
added.

What is happening?!


Samuel Martín Moro
{EPITECH.} tek4
CamTrace S.A.S
  (+033) 1 41 38 37 60
  1 Allée de la Venelle
  92150 Suresnes
  FRANCE

"Nobody wants to say how this works.
  Maybe nobody knows ..."
                      Xorg.conf(5)


On Wed, Aug 4, 2010 at 12:01 PM, Samuel Martín Moro <faust64 at gmail.com>wrote:

>
> Hello,
>
>
> I'm having troubles, porting our release generation scripts from 7.2 to
> 8.1.
>
> We start creating the image file:
>     dd bs=18k count=4096 </dev/zero >cdroot.img 2>/dev/null
> We add our image to mdevices:
>     mdconfig -a -t vnode -f ./cdroot.img
> Then, bsdlabel:
>     bsdlabel -w -B -b cdroot/boot/boot /dev/mdX minimum4
>     (
>     with minimum4 is a "custom" entry in disktab, as:
>         minimum4:ty=mfs:se#512:nt#1:rm#300:\
>                 :ns#11520:nc#1:\
>                 :pa#11520:oa#0:ba#4096:fa#512:\
>                 :pc#11520:oc#0:bc#4096:fc#512:
>     )
> And I get this warning:
>     bsdlabel: partition c doesn't cover the whole unit!
>     bsdlabel: An incorrect partition c may cause problems for standard
> system utilities
>
> While generating on 5.4, 6.2 or 7.2, after bsdlabel, I have devices
> /dev/mdXa and /dev/mdXc, as expected.
> But while trying on 8.1, I just have /dev/mdXa...
>
> I'm not used to bsdlabel and disktab stuffs, so it may sound stupid, but:
> - Is there a way to create a correct disktab layout, to use with a disk
> image like our script does?
> - Or, is there a way to adapt our dd to get an image file matching the size
> required by our disktab layout?
> - If so, how to compute that size (somethign like $pa * $se + $pc * $se?
> adding $fa + $fc?)
> - tldr; / otherwise, is there a way to actually get back our /dev/mdXc
> after bsdlabel?
>
>
> Thanks!
>
>
>
> Samuel Martín Moro
> {EPITECH.} tek4
> CamTrace S.A.S
>   (+033) 1 41 38 37 60
>   1 Allée de la Venelle
>   92150 Suresnes
>   FRANCE
>
> "Nobody wants to say how this works.
>   Maybe nobody knows ..."
>                       Xorg.conf(5)
>