Hello,
When I'm booting with udev-177 I get a cryptic message output to the
screen in amongst the bootscripts that reads: udevd[120]: No such file
or directory
Is anyone else seeing this? I suspect it may be due to kmod looking for
something that is not present in a monolithic kernel. When I run
Matt Burgess wrote:
> Yeah, both xz and zlib install their libraries to /lib, but oddly
> enough, kmod still found them after telling it that they were
> in /usr/lib. I guess the linker's searching in /lib by default?
Yes, it should search /lib by default.
(Wandering a bit off topic...)
dummy
On Tue, 2012-01-17 at 13:38 +, Andrew Benton wrote:
> Hello,
>
> When I'm booting with udev-177 I get a cryptic message output to the
> screen in amongst the bootscripts that reads: udevd[120]: No such file
> or directory
I got a similar message during testing, complaining about line 52. See
On Tue, 2012-01-17 at 21:41 +, Matt Burgess wrote:
> On Tue, 2012-01-17 at 13:38 +, Andrew Benton wrote:
> > When I run the
> > network interface commands I see this in amongst that output:
> > index_mm_open: No such file or directory
>
> I see that as well, but seeing as everything worked
