---
loader2/init.c | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/loader2/init.c b/loader2/init.c
index d654d4c..e1ab65c 100644
--- a/loader2/init.c
+++ b/loader2/init.c
@@ -535,6 +535,11 @@ int main(int argc, char **argv) {
if (mount("/dev", "/dev", "tmpfs", 0, NULL))
fatal_error(1);
createDevices();
+ printf("starting udev...");
+ if (fork() == 0) {
+ execl("/sbin/udevd", "/sbin/udevd","--daemon",NULL);
+ exit(1);
+ }
}
printf("done
");

--
1.5.3.4

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

We should probably set udev's loglevel dependent on the loglevel that
you boot with. And to then have that output at least to where we can
get to it

Jeremy

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

Jeremy Katz (katzj@redhat.com) said:
> We should probably set udev's loglevel dependent on the loglevel that
> you boot with. And to then have that output at least to where we can
> get to it

That's either modifying the config file, or including more binaries
in stage1. Not sure either of those is what we want.

Bill

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

On Thu, 2007-12-06 at 12:01 -0500, Bill Nottingham wrote:
> Jeremy Katz (katzj@redhat.com) said:
> > We should probably set udev's loglevel dependent on the loglevel that
> > you boot with. And to then have that output at least to where we can
> > get to it
>
> That's either modifying the config file, or including more binaries
> in stage1. Not sure either of those is what we want.

You can pass the log_priority on the command line --
udevd log_priority=debug

And we could capture the output with --verbose and just making stdout
point at a file (and/or tty5)

Jeremy

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

Jeremy Katz (katzj@redhat.com) said:
> On Thu, 2007-12-06 at 12:01 -0500, Bill Nottingham wrote:
> > Jeremy Katz (katzj@redhat.com) said:
> > > We should probably set udev's loglevel dependent on the loglevel that
> > > you boot with. And to then have that output at least to where we can
> > > get to it
> >
> > That's either modifying the config file, or including more binaries
> > in stage1. Not sure either of those is what we want.
>
> You can pass the log_priority on the command line --
> udevd log_priority=debug
>
> And we could capture the output with --verbose and just making stdout
> point at a file (and/or tty5)

Well, if you want to pass the loglevel you booted with, that requires
starting udev from the loader (or parsing the command line in both places.)

Seems more clean to launch it from init.

Bill

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

Bill Nottingham (notting@redhat.com) said:
> Well, if you want to pass the loglevel you booted with, that requires
> starting udev from the loader (or parsing the command line in both places.)
>
> Seems more clean to launch it from init.

Additionally, unless you really *want* 50 lines of output on a single
usb device event, nothing other than 'err' (the default) is useful.

Bill

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

On Thu, 2007-12-06 at 17:03 -0500, Bill Nottingham wrote:
> Bill Nottingham (notting@redhat.com) said:
> > Well, if you want to pass the loglevel you booted with, that requires
> > starting udev from the loader (or parsing the command line in both places.)
> >
> > Seems more clean to launch it from init.

Oh, hrm. We could wait to start it from the loader... the number of
devices needed before it would be reasonable to start it from the loader
(rather than init) is really just the console bits.

...

> Additionally, unless you really *want* 50 lines of output on a single
> usb device event, nothing other than 'err' (the default) is useful.

But given this, ugh. I guess that if something doesn't work, it just
gets to be time to rebuild an initramfs with a custom udev that has
useful logging :-/

Jeremy

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list