From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?QmrDtnJuIEjDtmZsaW5n?= Subject: Re: Installation-Protocol for GuixSD x86_64 v0.15-preview Date: Wed, 4 Jul 2018 19:56:33 +0200 Message-ID: <20180704195633.6b38a4e1@alma-ubu> References: <20180703101553.702b0b00@alma-ubu> <8736x0fvbr.fsf@lapdog.tobias.gr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/FIgoZwojOU31=1d4QLJjghS"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34558) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fam1F-0004kl-6G for guix-devel@gnu.org; Wed, 04 Jul 2018 13:56:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fam1C-0003C7-3O for guix-devel@gnu.org; Wed, 04 Jul 2018 13:56:45 -0400 Received: from m4s11.vlinux.de ([83.151.27.109]:46590 helo=bjoernhoefling.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fam1B-0003BW-OS for guix-devel@gnu.org; Wed, 04 Jul 2018 13:56:42 -0400 In-Reply-To: <8736x0fvbr.fsf@lapdog.tobias.gr> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Tobias Geerinckx-Rice Cc: guix-devel --Sig_/FIgoZwojOU31=1d4QLJjghS Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Tobias, On Tue, 03 Jul 2018 12:49:12 +0200 Tobias Geerinckx-Rice wrote: > Hullo Bjrn, >=20 > Bj=C3=B6rn H=C3=B6fling wrote: > > Hi people, > > > > as Ludo "requested", today I freshly installed GuixSD in a QEMU > > environment (x86_64 on both host and virtual env) to check the > > installation process of the upcoming release. =20 >=20 > Wow. Thanks! >=20 > You've motivated me to try it on a headless server (if that=20 > works). Are you doing that with QEMU? I would be interested in improving my Q-foo and know how to create a headless, SSH-only QEMU-server. =20 > > qemu-system-x86_64 -m 1024 -smp 1 \ > > -net user -net nic,model=3Dvirtio -boot menu=3Don \ > > -drive file=3Dguixsd-install-0.14.0.system.iso \ > > -drive file=3Dguixsd.img > > > > I prefered writing the disk like this: > > > > -drive readonly,media=3Dcdrom,\ > > file=3D/gnu/store/70p7140n5igrqsfl989cxfzx6q3czc9a-image.iso > > > > In that way, I can use the RO store entry and QEMU will not=20 > > complain > > about not being able to write to. =20 >=20 > My QEMU-FU is, to say the least, rusty. >=20 > Do I parse this correctly as two separate (but related)=20 > suggestions: adding =E2=80=98readonly,media=3Dcdrom=E2=80=99 to silence t= he=20 > complaint and =E2=80=98file=3D/gnu/store/...=E2=80=99 to use an image fro= m the=20 > store? >=20 > > Should we update the manual? =20 >=20 > ...if so: +1 to the first suggestion. Yes, that is what I mean. Maybe the "readonly" is superfluous with "media=3Dcdrom", I have to read/try that. I can write a docs-patch by the end of the week. =20 > The second one seems to depend on your situation. The manual=20 > assumes you've downloaded the image (probably not using =E2=80=98guix=20 > download=E2=80=99) instead of building it from scratch, but we could=20 > document both. Especially since the latter can be written as one=20 > easy command: >=20 > qemu-system-x86_64 [...] -drive readonly,media=3Dcdrom,file=3D$(guix=20 > ...) Yes, we should take that as a separate thing. AFAIK the combination might be a bit dangerous: Building the installation media is not (yet?) reproducible, so the $(guix ...) command will produce every time a new image, not just a reference on the existing store item as would be the case for reproducibly-stable package builds. [...] > > I tried instead wget or curl. But both are not there. Do we have > > "HTTP client" tools in the installer package to test the network=20 > > this > > way? Or is this too heavy in size for the installer? Do we have > > anything else to give the user at it's hand besides ping? =20 >=20 > =E2=80=98guix download=E2=80=99. (Hey, if we include a static example and= its hash=20 > in the manual you'll even know when your being MITM'd by an=20 > incompetent!) Of cause. Cool! =20 [..] > > 6) Editors: When it comes about editing the standard config,=20 > > there are > > three editors mentioned: zile, nano, nvi. The first ones are=20 > > fired up as > > named, for "nvi" the command is "vi". This is not obvious for=20 > > everyone. =20 >=20 > Thorough testing :-) Good catch! Do you have time to submit a=20 > patch? Yes. This week. =20 [..] > > 12) ls | less > > > > ls has a colored output. Nice. > > ls | less has ugly escape sequences. Only ls --color=3Dno | less=20 > > works. =20 >=20 > I'd be surprised if =E2=80=98ls | less -R=E2=80=99 didn't (and that would= be a=20 > bug). >=20 > Otherwise, this is standard behaviour for both =E2=80=98ls=E2=80=99 and = =E2=80=98less=E2=80=99. If=20 > other distributions wrap it in magick, it would be interesting to=20 > know how, and where, and if it's clean enough for us to copy. I saw your discussions on IRC and look forward for a patch :-) Bj=C3=B6rn --Sig_/FIgoZwojOU31=1d4QLJjghS Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAls9ClIACgkQvyhstlk+X/2SAwCeJXZ7gBWRC9l7/RySAYYgO22n gOUAoLKsETET/8x9KAV4nNHcwQ0AvtGQ =S8s3 -----END PGP SIGNATURE----- --Sig_/FIgoZwojOU31=1d4QLJjghS--