Date: Tue, 12 Jul 2016 10:48:35 -0700 From: Maxim Sobolev <sobomax@freebsd.org> To: Allan Jude <allanjude@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: <CAH7qZfvrMKzqgVYZgmdSZHXC3DjBARnMOgAJLJ_ujA%2BhEbv88g@mail.gmail.com> In-Reply-To: <7b82334d-92af-92c2-8b09-76d407750ad9@freebsd.org> References: <op.ykgfddt2kndu52@eveline> <CAG6CVpW3rGEoqTcQodY%2BWVPVsTdxUd6OsB%2BzAq1k7Y-vUrdaSg@mail.gmail.com> <CAOtMX2gAwr_OPgy=FNYjc_wDKafV0DmXPMBxnGOdacctmdtgmw@mail.gmail.com> <20160711214144.GA7465@FreeBSD.org> <1811960453.20160712012238@ofca.me> <5784EEA7.2030102@quip.cz> <892ABC57-2BC0-4A56-97AF-5AE28CDBE0DB@gmail.com> <7b82334d-92af-92c2-8b09-76d407750ad9@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Another option for the kvm installs and that we are using for many years
here is to pre-load root UZIP image into RAM. With some easy trimming you
can bring base system down to 30MB or so compressed. Yes, bit of delay to
load, but the kernel alone is around 10MB compressed, so it's not an order
of magnitude increase. Then it runs from the RAM completely, so you are
immune to any disconnects or stalls. If your kvm disconnects in the middle
of the session, you just re-connect and continue.
UZPNAME here is the root UFS compressed with mkuzip. You would just put it
into your ISO as file somewhere and use:
echo 'image_load=3D"YES"' >> ${CDIR}/boot/loader.conf
echo "image_name=3D\"/${UZPNAME}\"" >> ${CDIR}/boot/loader.conf
echo 'image_type=3D"md_image"' >> ${CDIR}/boot/loader.conf
Also we set mountftom (requires GEOM_LABEL):
echo vfs.root.mountfrom=3D\"ufs:ufs/${MD_LABEL}\" >>
${CDIR}/boot/loader.conf
-Maxim
On Tue, Jul 12, 2016 at 9:31 AM, Allan Jude <allanjude@freebsd.org> wrote:
> On 2016-07-12 11:15, Ngie Cooper (yaneurabeya) wrote:
> >
> >> On Jul 12, 2016, at 06:20, Miroslav Lachman <000.fbsd@quip.cz> wrote:
> >>
> >> Pawe=C5=82 Tyll wrote on 07/12/2016 01:22:
> >>
> >>> Those 3 things should shave off about 130MB of the 173MB needed to fi=
t
> >>> on 80-min CD-R. But... why this abstract number anyway? Why not 650M=
B
> >>> CD-R? Why not overburnable 800MB 90-min CD-R or even 870MB 99-mi=
n
> >>> CD-R? :)
> >>
> >> It is not only about the target media size. The size matters when you
> need to boot some recovery media from you desktop on remote server via KV=
M.
> >>
> >> And there is one thing I don't understand - why is the bootonly so
> large? I remember days when this fits to 50MB and now it is almost 235MB
> which renders it almost useless. For recoveries and remote installs I
> always use mfsbsd images (about 45MB).
> >
> > I wholeheartedly agree.
> >
> > It sucks having to transfer more than 50 MB over our work link across a
> few thousand miles with IPMI remote KVM redirection.
> >
> > Thanks,
> > -Ngie
> >
>
> With IPMI virtual media, you usually do not transfer the entire image,
> only read the blocks used by files that you load. Some IPMI clients
> provide stats, usually only about 40mb is read from the bootonly cd.
> More if you do things like invoke an editor to write a custom /etc/fstab
> etc.
>
> --
> Allan Jude
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAH7qZfvrMKzqgVYZgmdSZHXC3DjBARnMOgAJLJ_ujA%2BhEbv88g>