summaryrefslogtreecommitdiffstats
path: root/COPYRIGHT
diff options
context:
space:
mode:
authorsobomax <sobomax@FreeBSD.org>2011-12-31 00:09:33 +0000
committersobomax <sobomax@FreeBSD.org>2011-12-31 00:09:33 +0000
commit3592175cf3af629b95ae03a65548de30a3662e3d (patch)
tree51f4117a2870ea35cfc767f78f1fa47a23c64293 /COPYRIGHT
parent6fc82bacd8ce4fd640b0bedb438ca948cb86b303 (diff)
downloadFreeBSD-src-3592175cf3af629b95ae03a65548de30a3662e3d.zip
FreeBSD-src-3592175cf3af629b95ae03a65548de30a3662e3d.tar.gz
Use in-label sectorsize to determine position of the label when
writing label into a file image. The most common use - putting disklabel into ISO file. Before this change the label would always go to the offset 512, while geom_part code expects it to be in the 1st sector (i.e. 2048 incase of ISO). BSD disklabels provide good and lightweight way to logically split livecds. It is non-intrusive as far as ISO9660 goes (both boot-wise and metadata-wise) and completely transparent to anything but BSD, so you can have BSD-specific area appended after regular ISO. And with a little bit of GEOM trickery you can do even more interesting stuff with it. For example we make "hybrid" bootable CDs using this method. We create bootable ISO with kernel and such and append UFS image compressed with UZIP and it works like a charm. We put label based on the offsef of the BSD part into the ISO. The kernel boots off normal ISO9660 part, tastes label attaches it, tastes UZIP, attaches it and finally mounts UFS using GEOM_LABEL. This provides much better way of eliminating waste than doing "crunched" build. MFC after: 1 month
Diffstat (limited to 'COPYRIGHT')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud