I don't know what this module is doing different then the instructions on the Wiki. Is it written to fix a bug? or is it written to to make things more convenient?
The VirtualBox service, for instance, is started when KDE boots and when the VirtualBox guest additions are in environment.kdePackages . The only useful application I can think of right now is that a seperate NixOS module could make configuring the VirtualBox guest additions a little easier, e.g. a option that says services.virtualBoxGuestAdditions = true; and automatically sets the desired properties of a machine. Could David clarify his intentions a bit? -----Original Message----- From: [email protected] on behalf of Marc Weber Sent: Mon 5/10/2010 11:44 AM To: nix-dev Subject: Re: [Nix-dev] virtualbox VBoxService/modules Excerpts from David Brown's message of Sun May 09 22:13:54 +0200 2010: > I'd like to update the Wiki to describe how to auto-start the > virtualbox guest addon modules and daemon, but wanted to get any > feedback before editing it. The updates I've made are below. These > are just the things I've added for this support. > > Should this support be instead added to the virtualbox module so it > can just be enabled? Which virtualbox module are you talking about? Your code looks like beeing a NixOS module without options. However I could'nt find an existing module. Can you point me to the source? I'd add an enable option and add it to NixOS. box is used by many people here. Marc Weber _______________________________________________ nix-dev mailing list [email protected] https://mail.cs.uu.nl/mailman/listinfo/nix-dev
_______________________________________________ nix-dev mailing list [email protected] https://mail.cs.uu.nl/mailman/listinfo/nix-dev
