unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: znavko@tutanota.com
Cc: Help Guix <help-guix@gnu.org>
Subject: Re: Does not halt after Menu - Logout - Shut down and closing notebook	hood
Date: Mon, 15 Oct 2018 01:50:09 -0700	[thread overview]
Message-ID: <87y3aziofy.fsf@gmail.com> (raw)
In-Reply-To: <LOnSPaP--3-1@tutanota.com> (znavko's message of "Sun, 14 Oct 2018 18:43:04 +0200 (CEST)")

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

<znavko@tutanota.com> writes:

> [...]  And may be I will need
> any other configurations in other services that were not mentioned in
> Guix cgit.
> So how to get their exact names?

Some (perhaps most) services assume that you are somewhat familiar with
the software in question.  For example, the explanation of the
openssh-configuration in the Guix manual explains what the configuration
items do, but if you don't know what OpenSSH is, then it probably
doesn't help you very much.  When you encounter situations like this,
you might sometimes need to read more about the software in question
before you will understand how to use it in GuixSD.  This is generally
true for any GNU/Linux distribution.

> I started to learn guile at free time. But other Linux distributions
> had answers in the web how to configure.
> Using GuixSD I need to know exactly every package configurations and
> to now exactly how to translate it into Scheme.
> I there any specific manual how to do that?

In cases like this, your best bet is to do the following:

1) Check the GNU Guix manual.  You can read it online [1] or on your
computer via the command "info guix".

2) Check the GNU Guix source.  It sounds like you already know how to do
that.  Sometimes, the source code contains helpful information that has
not yet been added to the manual.

3) Search the help-guix@gnu.org email archives [2] for information.
Sometimes, the same question has been asked before.  It's also useful to
search the guix-devel@gnu.org email list [3], since a lot of discussion
happens there, also.

4) If you still don't understand something, ask for help at
help-guix@gnu.org.  You can also ask for help in our IRC chat room [4].

Nobody starts out knowing everything.  The Guix community is very
welcoming to newcomers, and I'm sure that if you take the time to ask
questions, you'll receive friendly, useful advice.  Good luck!

Footnotes: 
[1]  https://www.gnu.org/software/guix/manual/en/html_node/GNU-Distribution.html

[2]  https://lists.gnu.org/archive/html/help-guix/

[3]  https://lists.gnu.org/archive/html/guix-devel/

[4]  https://www.gnu.org/software/guix/contact/irc/

-- 
Chris

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

  reply	other threads:[~2018-10-15  8:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <LOlZSiB--3-1@tutanota.com-LOlZWEw--7-1>
2018-10-14 15:45 ` Does not halt after Menu - Logout - Shut down and closing notebook hood znavko
     [not found] ` <<LOlZSiB--3-1@tutanota.com-LOlZWEw--7-1>
     [not found]   ` <LOnFJsF--3-1@tutanota.com-LOnFNfQ----1>
2018-10-14 16:43     ` znavko
2018-10-15  8:50       ` Chris Marusich [this message]
2018-10-15 18:35         ` Marius Bakke
2018-10-16  4:24           ` znavko
2018-10-14  7:54 znavko
2018-10-14 12:10 ` 宋文武

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=87y3aziofy.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=znavko@tutanota.com \
    /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).