ken wrote:

> Paul Bredbury wrote:
>
>> ken wrote:
>>> I tried adding hal,dbus, and ivman. They all emerged but hal wouldn't
>>> install via rc-update. (couldn't be found error)
>>
>> Look in /etc/init.d/ - it's hald rather than hal ("d" for "daemon",
>> probably). You can also run "rc-update show" to see the settings.
>>
>>> I setup kdm as per the instructions.
>>> I can only login as root. If I try to login using a user account
>>> kdm starup stalls at either the 'system' or 'perphials' stage,
>>> times out, and leaves me with a blank pale blue screen.
>>
>> This sounds very similar to
>>
>
http://groups-beta.google.com/group/...a29f4e6bb9ec05
>>
>> Try renaming your ~/.dmrc file.
> I found a fix. I killed kdm and setup my ~/.xinitrc
> to exec startkde since someone else said this allowed
> him to start kde as a user.
>
> Well it didn't help me except that when I
> <crtl><alt><bs>'ed to kill my
> stillborn kde session I got to see the error dump.
> It was complaining about not being able to open /dev/null
> Come to think of it, I got the same error when I log in
> via command line as a user from the 'born' shell. So I
> did a 'chmod a+rw /dev/null' and now it works.
> But why? Is the /dev/null device entry supposed to be
> world read/write?
> After making this change I can now start kde as a user.
> Comments?


More problems. After getting users to be able to log in
by fixing the /dev/null issue I see as a user I can't
open a Konsole (xterm) and get a bash prompt. I can
as root! What now?