Re: Few notes to 0.8

[宋文武]

Ludovic Courtès <address@hidden> writes:

> 宋文武 <address@hidden> skribis:
>
>> Ludovic Courtès <address@hidden> writes:
>>
>>> Adam Pribyl <address@hidden> 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.
Currently, operating-system is not declarative, with the setting:
  (operating-system
    (keymap "dvorak"))
IIUC, the xorg-server service can't see it unless passed explicitly.

In NixOS, declarative configuration is implemented by 'modules':
  https://nixos.org/wiki/NixOS:Modules
  
Every module can define some options, access and contrib to the config,
the configuration.nix is just a normal module provided by user.

Yeah, how all the modules eval toghether is still a mystery for me.
>
>> 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.
How about run:
   $ guix system --user reconfigure config.scm (or guix user-profile?)
   
With config.scm:
   (user-profile
     (locale "en_US.utf8")
     (services (list (emacs-daemon-service)))
     (packages (list emacs)))
     
Get ~/.guix-profile (a better name?):
   boot locale profile

The `boot' is just like system's boot, run the activate script, start
dmd, even populate user's home with files build by guix.

After login, I can just run `boot' manually, or automatic by adding
it to ~/.bash_profile, ~/.xsession (can be populated by guix too).

> Also, should the global OS declaration include user-specific service
> lists?  WDYT?
The global OS could provide the default settings for user profile.

  (operating-system
    (user-profile))

And access as a singleton as %os, then user can reuse or override with:
  (user-profile
    (services (list (operating-system-services %os))))

But the declarative way is more better!
>
> Thanks for your feedback!
>
> Ludo’.