[Ovirt-devel] [PATCH node] Creates a standalone mode entry point script.

Daniel P. Berrange berrange at redhat.com
Thu Nov 6 10:39:01 UTC 2008

On Wed, Nov 05, 2008 at 04:55:54PM -0500, Darryl Pierce wrote:
> Hash: SHA1
> Bryan Kearney wrote:
> > Darryl Pierce wrote:
> >> Hash: SHA1
> >>
> >> Bryan Kearney wrote:
> >>> I get this error when trying to run this:
> >>>
> >>> http://bkearney.fedorapeople.org/dbus_error.png
> >>
> >> Hnmmm, is that due to hal not being started?
> >>
> >> We should have standalone mode script run after hal's started.
> > 
> > So, haldaemon starts at 26, and network starts at 10. Can you probe the
> > nics w/o hal-device?
> Sure, we could use Awk to scrape through the output from /sbin/ifconfig.

No, this is wrong. Hardware enumeration is what HAL is for, you should
not try to re-invent this, because you will do a worse job than HAL.

You have a core boot strapping issue here. The first time boot you can
just let it automatically go all the way through init process without
networking, and then run your configuration script at S99. This lets
you use HAL (and later libvirt) to enumeration devices. When this script
is complete, either just ifup the interfaces you configure, or restart
the network service script, or just do a reboot. For all subseequent
boots the config will be there already, so there's no ordering issue.

|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

More information about the ovirt-devel mailing list