unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: 宋文武 <iyzsong@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Few notes to 0.8
Date: Sat, 29 Nov 2014 21:45:24 +0100	[thread overview]
Message-ID: <87y4qtwxaz.fsf@gnu.org> (raw)
In-Reply-To: <87r3wm1aoq.fsf@gmail.com> ("宋文武"'s message of "Sat, 29 Nov 2014 11:57:25 +0000")

宋文武 <iyzsong@gmail.com> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Adam Pribyl <pribyl@lowlevel.cz> skribis:

[...]

>>> 2. during boot the system twice sets the console font, each time to a
>>> different one (this is not always reproducible). Minor.
>>
>> Hmm, you mean on the same tty?
> Yeah, I have issue too, solved by:
>
>   (initrd (lambda (fs . args)
>             (apply base-initrd fs
>                    #:extra-modules '("i915")
>                    args)))
>
> To get fbcon in initrd before udev-service and console-font-service.

Oh, OK.

> I think the 'Console' lines of `dmesg' tell the reason.

I have:

--8<---------------cut here---------------start------------->8---
$ dmesg |grep -E '(udevd.*starting|Conso)'
[    0.000000] Console: colour VGA+ 80x25
[    3.750956] udevd[190]: starting version 1.10
[    4.536397] Console: switching to colour dummy device 80x25
[    5.421016] Console: switching to colour frame buffer device 170x48
--8<---------------cut here---------------end--------------->8---

I don’t think we can solve it generically without adding udev and all
the graphics drivers to the initrd, can we?  Or perhaps we could just
include a few common graphics drivers by default?

> I just put it in my config.scm:
>
>   (define (console-layout-service layout)
>     (with-monad %store-monad
>      (return
>       (service
>        (document "Setup keyboard layout for console")
>        (provision '(console-layout))
>        (start #~(lambda _
>                   (system* (string-append #kbd "/bin/loadkeys") #$layout)))
>        (stop #~(const #t))
>        (respawn? #f)))))

Excellent.  I was thinking that we should have a keyboard layout setting
in the OS declaration, that would lead to a service like the one above
as well as the appropriate X settings.

> Any plan for user services?
> Get guix build a dmd.conf for user should be really cool.

Yeah, that could be nice.

I wonder how this should work.  Currently we’d have to start one dmd
instance per user; I’m not sure where/when this should be started.
Also, should the global OS declaration include user-specific service
lists?  WDYT?

Thanks for your feedback!

Ludo’.

  reply	other threads:[~2014-11-29 20:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-28 11:41 Few notes to 0.8 Adam Pribyl
2014-11-28 21:31 ` Ludovic Courtès
2014-11-29 11:57   ` 宋文武
2014-11-29 20:45     ` Ludovic Courtès [this message]
2014-11-30 11:05       ` 宋文武
2014-11-30 11:34         ` Services and access to the global configuration Ludovic Courtès
2014-11-29 21:06     ` Few notes to 0.8 Alex Kost

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=87y4qtwxaz.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=iyzsong@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).