On Mon, May 16, 2011 at 2:46 PM, Lennart Poettering
wrote:
> > It takes about 5-6s for udev to run input_id on the keyboard + touchpad,
> and
> > thus for them to be available to X.
>
> How come this takes so long?
>
> Does this actually delay X? Nromally X should be fine without kbd/mouse
> and t
On Mon, 16.05.11 14:43, Scott James Remnant ([email protected]) wrote:
> On Mon, May 16, 2011 at 2:23 PM, Lennart Poettering
> wrote:
>
> > Our entire userspace bootup takes <1s here on an older X300. I think
> > nobody expects that the mouse reacts any quicker than that.
> >
> Your "older X300"
On Mon, May 16, 2011 at 2:23 PM, Lennart Poettering
wrote:
> Our entire userspace bootup takes <1s here on an older X300. I think
> nobody expects that the mouse reacts any quicker than that.
>
> Your "older X300" is probably rather more powerful than a single-core Atom
CPU.
> But as mentioned e
On Thu, 12.05.11 09:09, Scott James Remnant ([email protected]) 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
> > Blue
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 8:45 PM, Kay Sievers wrote:
> On Tue, May 10, 2011 at 00:27, Gustavo Sverzut Barbieri
> wrote:
>
> > you can blacklist it if there is no userspace tools to handle it. That
> would
> > require some packaging changes to cope, but it is doable.
> > If it's desirable to load i
On Tue, May 10, 2011 at 00:27, Gustavo Sverzut Barbieri
wrote:
> you can blacklist it if there is no userspace tools to handle it. That would
> require some packaging changes to cope, but it is doable.
> If it's desirable to load it if there is some user space using it, one you'd
> need to add so
On Mon, 09.05.11 19:27, Gustavo Sverzut Barbieri ([email protected])
wrote:
> > So I was curious how these problems would be solved in the systemd world?
> > Reading through the documentation I came up with the following:
> >
> > The Kernel Driver is still going to get loaded regardless, be
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
> socket/D-Bus Activation right? So the presence of the device creates
On Mon, May 9, 2011 at 5:13 PM, Scott James Remnant wrote:
> Thanks for your answers so far, I haven't had a chance to fully read and
> digest them yet, but will do so before replying on those threads (if I even
> need to, it's likely your responses are complete in of themselves).
>
> My third que
Thanks for your answers so far, I haven't had a chance to fully read and
digest them yet, but will do so before replying on those threads (if I even
need to, it's likely your responses are complete in of themselves).
My third question is about communicating need; for this I'd like to outline
a use
13 matches
Mail list logo
