[Nix-dev] RE: [Nix-commits] SVN commit: nix - 14913 - sandervanderburg - in nixos/trunk: system upstart-jobs

Sander van der Burg - EWI S.vanderBurg at tudelft.nl
Tue Apr 7 22:35:47 CEST 2009


Yes, the kdm.nix script is basically a copy of xserver.nix, with modifications to make KDM working. I'm still experimenting with it and I will try derive a better/modular configuration of it afterwards.

Configuring a fully featured xserver is rather complex. There are some display managers available such as slim, kdm (included with KDE), gdm (included with GNOME), wdm and so on.
Each of these display managers can start a desktop session which could be the desktop that is included with the login manager (in this case KDE with KDM), but also other desktop sessions, e.g. kdm can also start GNOME for instance, or xmonad.

Therefore I think we have to specify desktops, display managers and desktops sessions as seperate modules in NixOS. In the configuration.nix we have to define what display manager we have to use and what available desktops sessions we want. By using these properties we can derive configurations for each display manager.


-----Oorspronkelijk bericht-----
Van: Nicolas Pierron [mailto:nicolas.b.pierron at gmail.com]
Verzonden: di 7-4-2009 21:01
Aan: nix-dev at cs.uu.nl; Sander van der Burg - EWI
Onderwerp: Re: [Nix-commits] SVN commit: nix - 14913 - sandervanderburg - in nixos/trunk: system upstart-jobs
 
Hi Sander,

If I understand your commit well, you have duplicated most of the
content of xserver.nix to copy it inside kdm.nix.  I guessing that the
reason you made this copy & paste is that the upstart-job describe in
xserver.nix is a job which is starting Slim.

If you have a look at the fix-style branch, you may see that the
xserver.nix file no longer exists.  This file is divided into many
subset which allow you to keep things separated between displayManager
/ windowManager / desktopManager.

I have to admit that I don't know how to merge your commit inside the
fix-style branch because there is too much differences and I haven't
look at KDM yet.  On the other hand you may find pretty-straight
forward to add KDM in the fix-style branch.

As the fix-style branch is pending to be merged, I think your
comparison could be a useful feedback for all of us.  Either this
would be a failure for some reasons (that I am expecting you to find)
or this would be a success in which case your experience will be
valuable for sceptical person.

Sincerly,

On Tue, Apr 7, 2009 at 17:34, Sander van der Burg
<S.vanderBurg at tudelft.nl> wrote:
> Added very experimental KDM support
>
> Changes:
>
> Modified: nixos/trunk/system/options.nix
> ===================================================================
> --- nixos/trunk/system/options.nix      2009-04-07 15:12:12 UTC (rev 14912)
> +++ nixos/trunk/system/options.nix      2009-04-07 15:33:59 UTC (rev 14913)
> @@ -1191,6 +1191,15 @@
>       };
>     };
>
> +    kdm = {
> +
> +      enable = mkOption {
> +        default = false;
> +        description = "
> +          Whether to enable the KDE display manager.
> +        ";
> +      };
> +    };
>
>     xserver = {
>
> Added: nixos/trunk/upstart-jobs/kdm.nix
> ===================================================================
> --- nixos/trunk/upstart-jobs/kdm.nix                            (rev 0)
> +++ nixos/trunk/upstart-jobs/kdm.nix    2009-04-07 15:33:59 UTC (rev 14913)
> @@ -0,0 +1,269 @@
> + # ...
> + # A huge part coming from xserver.nix
> + # ...



-- 
Nicolas Pierron
http://www.linkedin.com/in/nicolasbpierron
- If you are doing something twice then you should try to do it once.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20090407/df6ed1a8/attachment.html 


More information about the nix-dev mailing list