Long delay, but...
>
>>>> I had a kernel panic last week and since it's been sorted out x
>>>> has no longer been autostarting. I log in at the prompt and
>>>> "sudo gdm" brings everything back to normal so I thought that
>>>> creating /etc/rc2.d/S99gdm would solve it, which it doesn't -
>>>> obviously don't really understand the function of that
>>>> directory. Any suggestions what to try next?
>>>>
>>>> Owain Clarke
>>>>
>>> The files in those directories are symlinks to /etc/init.d files
>>> (in case that's not what you did). You can use one of various
>>> apps such as sysv-rc-conf to handle the links via a gui or use
>>>
>>> sudo ln -s /etc/init.d/gdm /etc/rc2.d/S99gdm
>>>
>>> to do it manually. If you already did that then it might be worth
>>> looking in /etc/init.d/gdm to see if there's a variable acting as
>>> an on/off switch.
>>>
>>> ATB, Peter
>>>
>> I checked the link and it's ok. My /etc/init.d/gdm looks like:
>>
>> http://users.cooptel.net/simbobo/uploads/gdm
>>
>>
>>> Also check your runlevel, which you can find in /etc/inittab,
>>> looking something like this:
>>>
>>> # The default runlevel.
>>> id:2:initdefault:
>>>
>> Yes, that's correct. Runlevel displays
>> N 2
>> I don't know what the N refers to...
>>
>> Any more ideas?
>>
>> Owain Clarke
>>
>
> You could try tracing through the script:
>
> bash -x /etc/rc2.d/S99gdm start
>
> and see what happens. It may be that gdm isn't set as the default
> display manager for example.
>
> Peter
>
I get the impression it was something to do with splashy, which was
installed but not in use. I've purged that now, but how do I capture
the output of the script if I need to paste it? If I do
bash -x /etc/rc2.d/S99gdm start > lugpost
then the file 'lugpost' just contains
Starting GNOME Display Manager: gdm
Owain
