mdconfig, bsdlabel, disktab

Samuel Martín Moro faust64 at
Wed Aug 4 10:01:56 UTC 2010


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:
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


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

"Nobody wants to say how this works.
  Maybe nobody knows ..."

More information about the freebsd-questions mailing list