unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: Miles Fidelman <mfidelman@meetinghouse.net>, help-guix@gnu.org
Subject: Re: question re. packaging, build, init and shepherd
Date: Fri, 10 May 2019 09:12:26 +0200	[thread overview]
Message-ID: <87mujuhjfp.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <544e9b99-f1a1-8eec-b2d3-fbe8318ee93b@meetinghouse.net>

[-- Attachment #1: Type: text/plain, Size: 1905 bytes --]

Hello Miles,

Miles Fidelman <mfidelman@meetinghouse.net> writes:

> On 5/9/19 1:03 PM, Christopher Baines wrote:

[...]

>> So, whereas I think things like systemd are aware of sysvinit scripts in
>> the usual place,

no: rc script are **wrapped** to service units by systemd-sysv-generator
at boot or systemd service reload

https://unix.stackexchange.com/a/233581 is a good summary
also https://www.turnkeylinux.org/blog/debugging-systemd-sysv-init-compat

that's not the solution, a full rewrite of rc script is often needed

>> the shepherd is completely unaware.
>
> So... that kind of leaves out automatically setting up servers. I mean, 
> most server software still comes with init files, maybe with systemd or 
> other init files, but generally make install sets things up so that 
> servers start & run.

I'm an absolute beginner here, but AFAIU...

each Guix service comes with a service definition written in guix
language, as documented
https://www.gnu.org/software/guix/manual/en/html_node/Defining-Services.html

e.g. OpenSSH definition is:
https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/services/ssh.scm#n263

guix services definition and activation is "another story" compared to
what happens in other init systems

...and yes, we (including me) have to study Guile and Guix to be able to
define guix services... and that's a lot of fun :-)

> So how does GUIX support this?

AFAIK Guix does not support wrapping rc scripts

> And, for that matter, how does GUIX handle any kind of post-install 
> configuration?  E.g., the kind of things that debconf might be used
> for.

declaratively, via
https://www.gnu.org/software/guix/manual/en/html_node/System-Configuration.html

that's much more than
apt+debconf+devops(ansible,puppet,cfengine,younameit)

[...]

HTH! Gio'

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2019-05-10  7:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09 16:07 question re. packaging, build, init and shepherd Miles Fidelman
2019-05-09 17:03 ` Christopher Baines
2019-05-09 21:22   ` Miles Fidelman
2019-05-10  7:12     ` Giovanni Biscuolo [this message]
2019-05-10  7:28     ` Christopher Baines

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mujuhjfp.fsf@roquette.mug.biscuolo.net \
    --to=g@xelera.eu \
    --cc=help-guix@gnu.org \
    --cc=mfidelman@meetinghouse.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).