Hi Daniel,
Thanks for getting in touch.
On Thu, Jan 13, 2011 at 5:29 PM, Daniel Poelzleithner poe...@poelzi.org wrote:
What is currently unknown on the other hand is the current active X
window in use. This could be done by connecting tho X and reacting to
events there, but I think a cleaner
Ludwig Nussel wrote:
mount --bind /var/run /mnt
mount /var
mount -M /mnt /var/run
This doesn't work. It means there is a period during boot where
/var/run suddenly vanishes (when mount the separate /var).
You have to do:
mount DEV_OF_VAR /mnt
mount --bind /var/run /mnt/run
mount -M /mnt
There is, of course, one use for settle; I like to have a monitor
running during boot that creates /var/log/udev - settle is as good a
command as any to kill monitor when it's done.
On Thu, Mar 31, 2011 at 11:35 AM, Kay Sievers kay.siev...@vrfy.org wrote:
Hey,
the underlying problem described
Another question I wasn't able to find an answer to in the documentation
I've read so far.
The use of device units seems to very much rely on udevd running on the
system, and not only that, udev rules having been parsed for the device and
a systemd tag set in the udevdb. udev obviously starts
On Tue, May 10, 2011 at 7:41 AM, Gustavo Sverzut Barbieri
barbi...@profusion.mobi wrote:
I'm not following all the user-session discussion, but AFAIU this
management will be done by the same code, but not same process (it's not
PID1). PAM (or another entity that has a role in the
On Mon, May 9, 2011 at 12:43 PM, Lennart Poettering
lenn...@poettering.netwrote:
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
On Mon, May 16, 2011 at 2:23 PM, Lennart Poettering
lenn...@poettering.netwrote:
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
On Mon, May 16, 2011 at 2:46 PM, Lennart Poettering
lenn...@poettering.netwrote:
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
