On Thu, May 12, 2011 at 6:59 PM, Gustavo Sverzut Barbieri <
[email protected]> wrote:
>
> Well, maybe you didn't get the activation part or you're trolling :-)
>
> Neither...
> As I said in my mail about the bluetooth part, the problem with kernel
> modules is that "you don't know what's in
On Thu, May 12, 2011 at 1:09 PM, Scott James Remnant wrote:
> On Mon, May 9, 2011 at 4:32 PM, Lennart Poettering > wrote:
>
>> On Mon, 09.05.11 13:13, Scott James Remnant ([email protected]) wrote:
>>
>> > The System Daemon seems to be where systemd is much more clever; a
>> Bluetooth
>> > devic
On Mon, May 9, 2011 at 4:32 PM, Lennart Poettering
wrote:
> On Mon, 09.05.11 13:13, Scott James Remnant ([email protected]) wrote:
>
> > The System Daemon seems to be where systemd is much more clever; a
> Bluetooth
> > device unit would "want" the System Daemon, but that could be joined with
> >
On Mon, May 9, 2011 at 12:43 PM, Lennart Poettering
wrote:
> > This means there are a large number of devices already known to the
> kernel
> > at the point that systemd starts, especially if you build the drivers
> into
> > the kernel for those devices. It's possible to get going straight away
>
On Tue, May 10, 2011 at 9:39 AM, Lennart Poettering
wrote:
> Note that you need to delay execution of user code after the base system
> is set up anyway, in order to ensure that the right perms are set on the
> volatile and other directories. That means having a single transaction
> for both user
