Hi,
Ludovic Courtès wrote:
> Michael Raskin <7c6f4...@mail.ru> writes:
>
>> Arie Middelkoop wrote:
We have to use the directy sleep hack, because it there is time window
between starting the dbus daemon process and when it is really active.
>>> You could create a busy loop with "dbus-
Hello,
Eelco Dolstra
writes:
> Marc Weber wrote:
>
>> +If you neither create /etc/cron.deny nor /etc/cron.allow only
>> root
>> +will be allowed to have its own crontab file.
>
> It's /var/cron/cron.{deny|allow}, actually.
>
> Also, perhaps we should just create /var/cro
Michael Raskin <7c6f4...@mail.ru> writes:
> Arie Middelkoop wrote:
>>> We have to use the directy sleep hack, because it there is time window
>>> between starting the dbus daemon process and when it is really active.
>>
>> You could create a busy loop with "dbus-send" and keep on retrying until
>
Hi,
Marc Weber wrote:
> +If you neither create /etc/cron.deny nor /etc/cron.allow only
> root
> +will be allowed to have its own crontab file.
It's /var/cron/cron.{deny|allow}, actually.
Also, perhaps we should just create /var/cron/cron.deny in the Upstart job's
start
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Arie Middelkoop wrote:
>> We have to use the directy sleep hack, because it there is time window
>> between starting the dbus daemon process and when it is really active.
>
> You could create a busy loop with "dbus-send" and keep on retrying until
>
> We have to use the directy sleep hack, because it there is time window
> between starting the dbus daemon process and when it is really active.
You could create a busy loop with "dbus-send" and keep on retrying until
it succeeds...
___
nix-dev mailing
I'm still experimenting with it, but I agree that we have to make it active by
default.
We have to use the directy sleep hack, because it there is time window between
starting the dbus daemon process and when it is really active.
-Original Message-
From: Ludovic Courtès [mailto:l...@gnu.
Hi Tony,
On Fri, Apr 3, 2009 at 10:31, Tony White wrote:
> So, I decided to try to copy the ipw2200 firmware expression in
> nixpkgs to build a new package :
>
> I've got /etc/nixos/nixpkgs/pkgs/os-specific/linux/firmware/ipw2100
>
> Then I've added :
>
> ipw2100fw = import ../os-specific/linux/
Hi nix people,
I've join the list because I'm very interested in nix, Nixos and it's
concepts, Hoping that someone will be able to answer a few questions I
have, So I can make more sense of how I understand nix and Nixos.
I've read through the documentation a few times for both the nix
package sys
Hello!
Sander van der Burg writes:
> +consolekit = {
> +
> + enable = mkOption {
> +default = false;
I think this kind of thing should be enabled by default if/when it works
well.
> +job = ''
> + description "Console Kit Service"
> +
> + start on dbus
> +
10 matches
Mail list logo
