From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: [V2 PATCH 1/1] services: Add agetty service. Date: Fri, 17 Feb 2017 17:59:47 -0500 Message-ID: <20170217225947.GA16812@jasmine> References: <8b9a83141665a7a86aa3d3c9ba6363c1ba2e93cd.1487117562.git.leo@famulari.name> <20170215002417.GA19546@jasmine> <20170216070650.GA21674@jasmine> <86poig3bsv.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39958) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cerVJ-0001yi-VB for guix-devel@gnu.org; Fri, 17 Feb 2017 17:59:54 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cerVG-0006Bw-Qa for guix-devel@gnu.org; Fri, 17 Feb 2017 17:59:54 -0500 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:33967) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cerVG-0006Bb-Gl for guix-devel@gnu.org; Fri, 17 Feb 2017 17:59:50 -0500 Content-Disposition: inline In-Reply-To: <86poig3bsv.fsf@gmail.com> 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: myglc2 Cc: guix-devel@gnu.org On Fri, Feb 17, 2017 at 01:35:44PM -0500, myglc2 wrote: > Hi Leo, > > I think that what you have is great. With this in my system config ... > > (agetty-service (agetty-configuration > (tty "ttyS1") > (baud-rate "115200"))) > > ... it works painlessly on a headless GuixSD server over IPMI. I think > you can put a brief example in the doc, refer the user to the code and > the agetty man page for more info, and declare victory. Awesome! Veering off-topic, I wonder what created that device node /dev/ttyS1? I have 32 of them, but (gnu build linux-boot) appears to only create the first one: https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/build/linux-boot.scm#n160 > But let me digress a bit on this topic. What if, in situations like > this, Guix provided an easy way to export the "native config" generated > by Guix? > > Then we could tell the user ... > > 1) If you want to know exactly what we are doing, export the native > config and read the native doc. > > 2) If you want features we don't support, export the native config, read > the doc, modify it, and feed it into the "native config hatch." > > With this approach, we could implement and document only "key features" > with a clear conscience. When we haven't implemented a feature the user > needs they will be no worse off that they were before. In fact, they > will usually be ahead, because Guix has taken care of the general > requirements and provided a sound starting point for a native config. An interesting idea! I guess the implementation would vary based on services that use a configuration file (like nginx) and those that are configured on the command-line (like agetty). But I'm still finding my way around services, in general, so I'm not sure.