Koen Kooi wrote:
I decided to sit down and debug the udev problem on my c700.
Summary:
It's not a udev problem, it's pretty much a problem with zaurus
initscripts.
There are problems in udev init script as well, at least in oe.dev:
- typo in awk code, which checks, whether udev is
Stanislav Brabec wrote:
Koen Kooi wrote:
I decided to sit down and debug the udev problem on my c700.
Summary:
It's not a udev problem, it's pretty much a problem with zaurus
initscripts.
There are problems in udev init script as well, at least in oe.dev:
- typo in awk code, which
Koen Kooi wrote:
Stanislav Brabec wrote:
- /dev is fully populated only during first boot. Consequent boots
use /dev archive in /etc. This concept speeds up bopoting process, but
it may fail:
- After kernel change.
- When a removable device has its driver in kernel.
- If first
Hi,
I decided to sit down and debug the udev problem on my c700.
Summary:
It's not a udev problem, it's pretty much a problem with zaurus
initscripts.
Background:
Udev mount a tmpfs over /dev and starts adding nodes with the info
from /sys and creates a tarball when its done to make
Koen,
many thanks for having finally made your hands dirty...and solved the
nasty issue!
Andrea
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
It's not a udev problem, it's pretty much a problem with zaurus
initscripts.
While keeping udev_124, please implement the poky fix about persistent
rules [1] and perhaps the patch from mailing list [2] allowing to see
the pending jobs at timeout (in udev_125).
[1]
