rawhide install attempts fail - missing /usr/bin/hal-lock

[Gregory Woodbury]

Trying to install from the nightly compose desktop spin:
1) direct booting fails as gdm goes into a paroxysm of fail/restart and just
flashes the screen.
2) booting into mode 3 and doing a startx brings up a useable desktop
3) /usr/bin/liveinst fails with an error report of missing /usr/bin/hal-lock

giving up for the night.

[Adam Williamson]

On Wed, 2011-01-19 at 04:03 -0500, Gregory Woodbury wrote:
> Trying to install from the nightly compose desktop spin:
> direct booting fails as gdm goes into a paroxysm of fail/restart
>
> and just flashes the screen.

https://bugzilla.redhat.com/show_bug.cgi?id=670361
> /usr/bin/liveinst fails with an error report of
>
> missing /usr/bin/hal-lock

Oooh, bad anaconda, depending on hal. No cookie for you. Fileabug!

[James Laska]

On Wed, 2011-01-19 at 10:34 +0000, Adam Williamson wrote:
> > /usr/bin/liveinst fails with an error report of
> >
> > missing /usr/bin/hal-lock
>
> Oooh, bad anaconda, depending on hal. No cookie for you. Fileabug!

https://bugzilla.redhat.com/show_bug.cgi?id=670312

Thanks,
James

[Chris Lumens]

> > /usr/bin/liveinst fails with an error report of
> >
> > missing /usr/bin/hal-lock
>
> Oooh, bad anaconda, depending on hal. No cookie for you. Fileabug!

What would be even more useful would be suggesting what we should be
doing to replace the usage of /usr/bin/hal-lock.

- Chris

[Matthias Clasen]

On Wed, 2011-01-19 at 10:02 -0500, Chris Lumens wrote:
> > > /usr/bin/liveinst fails with an error report of
> > >
> > > missing /usr/bin/hal-lock
> >
> > Oooh, bad anaconda, depending on hal. No cookie for you. Fileabug!
>
> What would be even more useful would be suggesting what we should be
> doing to replace the usage of /usr/bin/hal-lock.

The replacement for hal-lock is udisks --inhibit. See udisks(1).

[Christoph Frieben]

2011/1/19 Gregory Woodbury:
> /usr/bin/liveinst fails with an error report of missing /usr/bin/hal-lock

Run 'yum install /usr/bin/hal-lock'. You will be prompted to install
the corresponding package, and liveinst then allows to install the
system successfully. ~C

[Gregory Woodbury]

On Wed, Jan 19, 2011 at 6:17 AM, Christoph Frieben <
[e-mail]> wrote:
> 2011/1/19 Gregory Woodbury:
> > /usr/bin/liveinst fails with an error report of missing
>
> /usr/bin/hal-lock
>
> Run 'yum install /usr/bin/hal-lock'. You will be prompted to install
> the corresponding package, and liveinst then allows to install the
> system successfully. ~C

That does indeed let the system install successfully.

1) Firstboot does not get run properly after reeboot
2) gdm still goes into paralasis of fail/restart so one can't log in
graphically
3) login on a text console works and using mode3 and startx brings up a
useable desktop

4) NFS is not part of the default system (personal nitpick)
5) vim is not on the default system (personal preference)

[Gregory Woodbury]

On Wed, Jan 19, 2011 at 10:26 AM, Gregory Woodbury wrote:
> On Wed, Jan 19, 2011 at 6:17 AM, Christoph Frieben <
> [e-mail]> wrote:
> > 2011/1/19 Gregory Woodbury:
> > > /usr/bin/liveinst fails with an error report of missing
> >
> > /usr/bin/hal-lock
> >
> > Run 'yum install /usr/bin/hal-lock'. You will be prompted to install
> > the corresponding package, and liveinst then allows to install the
> > system successfully. ~C
>
> That does indeed let the system install successfully.
> Firstboot does not get run properly after reeboot
> gdm still goes into paralasis of fail/restart so one can't log in
>
> graphically
> 3) login on a text console works and using mode3 and startx brings up a
> useable desktop

Additionally, plymouthd throws an error durring bootup: cannot log bootup,
address already in use.