Michael Biebl wrote:
Richard Kettlewell wrote:
Michael Biebl writes:
Armin Berres wrote:
Heyya!
I just tried to install hal in a chroot and got exactly the same error.
Calling addgroup by hand solved the problem for me. Maybe you should
add
the group before calling adduser just to be sure?
I copied some stuff from my real system to the chroot, which could be a
reason, but calling addgroup shouldn't hurt, so...
Hi Richard,
did you do something similar like this:
copy /etc/passwd (but not /etc/group) from another system? Did you have
an older version of hal installed before or was it a clean install?
The system was initialized by xen-create-image. (I'm sorry I didn't
mention this before!)
My vm host is turned off right now but I can check its configuration
in detail if necessary.
Yes, that would help. Could you check (or send me) the contents of
/etc/passwd and /etc/group for the haldaemon entry.
What does
getent passwd | grep haldaemon
getent group | grep haldaemon
say.
I currently have:
[EMAIL PROTECTED]:~$ getent passwd | grep haldaemon
haldaemon:x:108:105:Hardware abstraction layer,,,:/var/run/hal:/bin/false
[EMAIL PROTECTED]:~$ getent group | grep haldaemon
haldaemon:x:105:
..and hal configured OK some time ago.
I see that you still have the same adduser command the postinst; and
experimenting with adduser indicates that the command would still fail
if the user existed but the group did not. I think I must have created
the group manually at some point.
I think incorrect passwd/group setup when the VM was created must be the
ultimate source of the problem.
ttfn/rjk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
