From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36117) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dN4Xj-0000sR-Nh for guix-patches@gnu.org; Mon, 19 Jun 2017 17:49:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dN4Xe-0000zP-Nc for guix-patches@gnu.org; Mon, 19 Jun 2017 17:49:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:53982) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dN4Xe-0000zL-Jm for guix-patches@gnu.org; Mon, 19 Jun 2017 17:49:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dN4Xe-0005Ho-Cf for guix-patches@gnu.org; Mon, 19 Jun 2017 17:49:02 -0400 Subject: [bug#27401] [PATCH] doc: Suggest a QEMU image size large enough for the system examples. Resent-Message-ID: Date: Mon, 19 Jun 2017 17:48:20 -0400 From: Leo Famulari Message-ID: <20170619214820.GA2317@jasmine.lan> References: <4fedabaa491c5a46b8d437748f9071a4aa1d966d.1497676494.git.leo@famulari.name> <87vanrc16w.fsf@gnu.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="yrj/dFKFPuw6o+aM" Content-Disposition: inline In-Reply-To: <87vanrc16w.fsf@gnu.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Jan Nieuwenhuizen Cc: 27401@debbugs.gnu.org --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 19, 2017 at 07:55:03PM +0200, Jan Nieuwenhuizen wrote: > Leo Famulari writes: >=20 > > * doc/guix.texi (Installing GuixSD in a Virtual Machine): Increase sugg= ested > > image size from 5 GB to 50 GB. >=20 > LGTM, however -- What about something like this patch too? I seems that > the VMs we create (although they are of the ballooning cow2 kind), are > 2GiB -- i.e., almost unusable for Real Stuff (TM)? I chose 2GiB for those images because it's pretty easy to grow a partition and ext4 filesystem from a running system. On the other hand, I couldn't find an easy way to shrink them. We can't predict the size of the virtual block device storage provided by a VPS hoster, so I chose this small size with these expectations: 1) 2GiB will never be too big 2) users will resize after booting I didn't come up with a better solution for the problem of not knowing the storage size in advance. What do you think? --yrj/dFKFPuw6o+aM Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAllIRqEACgkQJkb6MLrK fwiA+RAA43qKJJJvOBYvIaWfwzCq7Sl98mJn6yW4Uk11Xeeksn2S5yu/+PcUAEJW 8+Cq6chCG0iifWgQGNEwZoaCu9QAPRfkvr+gtHmZiQUutbz/Xj932+AD3lV8EN/j 28TIgYY1inC39dOBjUVsXoMPWtilA3VE3/LZCTVLyk2HDWfEIi6CPEs8dJQxwZ0z vaN8NpdnNEA+tJxNuIYsXQ5KKkD3Axm+L8oD7FVOKY0oWtFsNsCNH85aN0APNFKP otKeUjKKn2uPdl3rK3wJug9BLfPNEH84g+hOMoB3EGS0SUCIJjkjNiUQfBT1gaUR ERH+CYb+HNpum1r2B4uqW9yRxC9AfbkW/BK16AOthXKpw5TZoN4KQ56Ajciz+/5L YIA9Cq2vX3xXAgyFJQrmBze0LLGRvnR7+5ZH8NDGHGUTqH7cc6VU8kIu5JcwDbIE TAM89OX3Qkic/VtovZTFdWgXT4i8rAPcqbcjdPI9VYyskis13xGmuXupwpZgxo+g NZSNROhT5TkOzqAX1DrtRzeoOAyz6QPw7S7VYxvPH1i5TLajd+YeaykcufE2E+o/ VAdIFOeUXpjIMGjonudPwTgMn31Ie4w76ua68UH6fSyoqxgJ0DQlGAwiW5s6ipnT htw6Xogp04PfNnBL0b3UepHMaUo4/HPOKAG82xLJqp544eSDg8s= =9CYO -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM--