Date: Fri, 3 May 2019 10:57:20 -0600 From: Alan Somers <asomers@freebsd.org> To: David Boyd <David.Boyd49@twc.com> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: New vm-image size is much smaller than previos Message-ID: <CAOtMX2h288pFqZybBQ8hB%2B4GEuSHZagmB1kqpM%2BpOQ86r%2B8hEQ@mail.gmail.com> In-Reply-To: <28d9446e246bcdb58f1fe48fce9900e054a5d4d3.camel@twc.com> References: <28d9446e246bcdb58f1fe48fce9900e054a5d4d3.camel@twc.com>
next in thread | previous in thread | raw e-mail | index | archive | help
See r346959. Before first boot, you should expand the image up to whatever size you want. growfs(8) will automatically expand the file system. -Alan On Fri, May 3, 2019 at 10:32 AM David Boyd <David.Boyd49@twc.com> wrote: > > The vm-image for 13.0-CURRENT > > FreeBSD-13.0-CURRENT-amd64-20190503-r347033.vmdk > > is only 4.0 GB in size. Previous images were about 31.0 GB. > > This smaller image doesn't leave much room to add packages and other > customizations. > > Thanks. > > David Boyd. > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2h288pFqZybBQ8hB%2B4GEuSHZagmB1kqpM%2BpOQ86r%2B8hEQ>