#30916 Request: add a short description field for os-configuration

Message #23 received at 30916@debbugs.gnu.org (full text, mbox, reply):

Received: (at 30916) by debbugs.gnu.org; 24 Mar 2018 17:00:34 +0000
From debbugs-submit-bounces@debbugs.gnu.org Sat Mar 24 13:00:34 2018
Received: from localhost ([127.0.0.1]:51656 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces@debbugs.gnu.org>)
	id 1ezmWv-0003uO-Ri
	for submit@debbugs.gnu.org; Sat, 24 Mar 2018 13:00:34 -0400
Received: from static.195.114.201.195.clients.your-server.de
 ([195.201.114.195]:53902 helo=conspiracy.of.n0.is)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <ng0@n0.is>) id 1ezmWt-0003uF-Qs
 for 30916@debbugs.gnu.org; Sat, 24 Mar 2018 13:00:32 -0400
Received: by conspiracy.of.n0.is (OpenSMTPD) with ESMTPSA id 2dacf479
 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); 
 Sat, 24 Mar 2018 17:00:29 +0000 (UTC)
Date: Sat, 24 Mar 2018 17:00:46 +0000
From: ng0 <ng0@n0.is>
To: Danny Milosavljevic <dannym@scratchpost.org>
Subject: Re: bug#30916: Request: add a short description field for
 os-configuration
Message-ID: <20180324170046.sl4hpkmblp5tzpzz@abyayala>
References: <d2032740-2182-6ded-a36c-14b6cdb5071b@uni-bremen.de>
 <20180323141537.64xtvlgalhlzlz3z@abyayala>
 <06f52ff5-4019-e449-1f56-a585c759abb1@uni-bremen.de>
 <20180324124556.7x36ap6mfeugc7pa@abyayala>
 <017b6770-3168-5d63-3dd5-e6c3b590f527@uni-bremen.de>
 <20180324175438.2ff4e55e@scratchpost.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="qays2pepb6zp63xw"
Content-Disposition: inline
In-Reply-To: <20180324175438.2ff4e55e@scratchpost.org>
X-Spam-Score: -0.0 (/)
X-Debbugs-Envelope-To: 30916
Cc: Martin Castillo <castilma@uni-bremen.de>, 30916@debbugs.gnu.org,
 ng0 <ng0@n0.is>
X-BeenThere: debbugs-submit@debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request@debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit@debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request@debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request@debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces@debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
X-Spam-Score: -0.0 (/)

[Message part 1 (text/plain, inline)]

Danny Milosavljevic transcribed 2.9K bytes:
> Hi Martin,
> 
> On Sat, 24 Mar 2018 14:56:03 +0100
> Martin Castillo <castilma@uni-bremen.de> wrote:
> 
> > ng0 wrote:
> > > So basically you want a field in the operating-system declaration where you
> > > can _manually_ set a description of a certain maximum length which will be
> > > added to the GRUB entry of the generated system generation?  
> > yes
> 
> I wonder whether this description can be generated instead - we have all
> the information we need - the packages, the users that are there etc.

But how much space do we have in the GRUB descriptions? I have computers with 800x600 or what
it was resolution for the screen, and while this would be a nice feature I wonder if there's
some implications in GRUB menu readability.
I'm not an expert in GRUB, I can boot without a menu, but GRUB is a small operating system
on its own :)

> Or a description could be generated only if a custom description is not specified.
> 
> In fact it's easy to add this and would be a nice intro project for a
> person interested in Guix development.  I can mentor.
> 
> The thing used to fill the Guix bootloader entries is <boot-parameters>.
> 
> There's a procedure "operating-system-boot-parameters" which is used
> to generate <boot-parameters> instances from an <operating-system>
> declaration.
> 
> (operating-system-bootcfg calls operating-system-boot-parameters)
> (perform-action calls operating-system-bootcfg)
> (perform-action is in the top-level guix script)
> 
> <boot-parameters> are serialized to disk into:
> 
> /var/guix/profiles/system-704-link$ cat parameters 
> (boot-parameters (version 0) (label "GNU with Linux-Libre 4.14.14 (beta)") (root-device "dayas:/") (kernel "/gnu/store/fnk2xhicbrjsvbq082p6x0ch6npkrg0z-linux-libre-4.14.14/bzImage") (kernel-arguments ("crashkernel=256M" "modprobe.blacklist=pcspkr,snd_pcsp" "quiet" "acpi_osi=Linux" "clocksource=acpi_pm" "allow-discards" "root_trim=yes")) (initrd "/gnu/store/nvhkdssz1m1p8xrggi78y8pd7jz4p3ng-raw-initrd/initrd") (bootloader-name grub) (store (device "dayas:/") (mount-point "/")))
> 
> But I wouldn't change the serialization format or what fields <boot-parameters> contain.
> 
> Just change operating-system-bootcfg to take a "description" parameter.
> And change operating-system-boot-parameters to take a "description" parameter and
> use it to calculate the label.
> 
> And change perform-action to calculate the value for to "description" parameter in this way:
> - Taking it from <operating-system> (or the command line?) 
> - Falling back to an automatic value (comparing it to the previous generation) otherwise.
> 
> That's it.



-- 
A88C8ADD129828D7EAC02E52E22F9BBFEE348588
https://n0.is

[signature.asc (application/pgp-signature, inline)]

Send a report that this bug log contains spam.