Date: Wed, 13 Jul 2016 07:22:58 -0700 From: Maxim Sobolev <sobomax@freebsd.org> To: Glen Barber <gjb@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: FreeBSD-11.0-BETA1-amd64-disc1.iso is too big for my 700MB CD-r Message-ID: <CAH7qZfu98q9kNRU1RF0bpzM7Xsx8Rp5fE-AuA7kum%2BQm=4gNDw@mail.gmail.com> In-Reply-To: <20160713135213.GH1520@FreeBSD.org> References: <op.ykgfddt2kndu52@eveline> <CAG6CVpW3rGEoqTcQodY%2BWVPVsTdxUd6OsB%2BzAq1k7Y-vUrdaSg@mail.gmail.com> <CAOtMX2gAwr_OPgy=FNYjc_wDKafV0DmXPMBxnGOdacctmdtgmw@mail.gmail.com> <20160711214144.GA7465@FreeBSD.org> <20160711214604.GG20831@zxy.spb.ru> <4a7eeee3c2737e9abcb6ba2557630d87@ultimatedns.net> <16f749e5-ca72-de79-651f-d50f9c42309e@freebsd.org> <7d0bd071cfbc78fcb9956e47f186e90b@ultimatedns.net> <CAH7qZfv7wrCK7xORCyP4x4wP0T_9BuhJiyoZ%2B0O-cwKfR7A=Qw@mail.gmail.com> <20160713135213.GH1520@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Glen, UFSFILE here is the path to the UFS file system input image that can
be created either via attaching file (vnode) with mdconfig, doing newfs
mdX, mount mdX etc or by using mkimg tool. The UZPFILE is resulting CLOOP
image, temporary file. ISOFILE is the output file (ISO). Let me know if you
have some more specific questions, I'll be glad to help.
-Max
On Wed, Jul 13, 2016 at 6:52 AM, Glen Barber <gjb@freebsd.org> wrote:
> On Mon, Jul 11, 2016 at 05:23:32PM -0700, Maxim Sobolev wrote:
> > P.S. Just in case if somebody wants to integrate this method into FreeBSD
> > liveCD build, we do a bit of trick there by making normal ISO9660 file
> > system with compressed kernel and relevant boot pieces and then also
> > sticking in BSD label on the same disk image. It turns out ISO9660 and
> BSD
> > disklabel structures do not overlap, so it works nicely since 2005 or
> > so. Then we append UFS image compressed with mkuzip at the end of it.
> > Resulting image can be used just as any ISO would. We also cook up UFS
> with
> > unique label and then use GEOM_LABEL to easily find relevant file system
> on
> > boot regardless of the physical device name.
> >
> > mkuzip -dL -S -s 65536 -o ${UZPFILE} ${UFSFILE}
> > mkisofs -b boot/${CDBOOT} -no-emul-boot -r -o ${ISOFILE} ${CDIR}
> > eval $(stat -s ${UZPFILE})
> > UZPSIZE=$((st_size + 2048 - (st_size % 2048)))
> > truncate -s ${UZPSIZE} ${UZPFILE}
> > eval $(stat -s ${ISOFILE})
> > ISOSIZE=${st_size}
> > echo "bytes/sector: 2048" >
> > ${TDIR}/label.txt
> > echo "sectors/unit: $(((UZPSIZE + ISOSIZE) / 2048))" >>
> > ${TDIR}/label.txt
> > echo "a: $((UZPSIZE / 2048)) $((ISOSIZE / 2048)) unused" >>
> > ${TDIR}/label.txt
> > echo "c: $(((UZPSIZE + ISOSIZE) / 2048)) 0 unused" >>
> > ${TDIR}/label.txt
> > truncate -s $((ISOSIZE + UZPSIZE)) ${ISOFILE}
> > disklabel -A -R -f ${ISOFILE} ${TDIR}/label.txt
> > truncate -s ${ISOSIZE} ${ISOFILE}
> > cat ${UZPFILE} >> ${ISOFILE}
> >
>
> I'm very interested in implementing this, provided it solves the
> disc1.iso size issue. Could you provide a bit explanation on what the
> variables above represent? At the moment, I'm having trouble parsing
> the file paths and input/output paths.
>
> Glen
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAH7qZfu98q9kNRU1RF0bpzM7Xsx8Rp5fE-AuA7kum%2BQm=4gNDw>