On Tuesday 06 January 2009 02:02:16 Francisco Ares wrote:
> This is a snippet of the end of the boot screen:
>
> * Setting framebuffer console images ... [ ok ]
> * Starting gpm ... [ ok ]
> * Setting up kdm ...
Am Dienstag, 6. Januar 2009 03:52:54 schrieb Francisco Ares:
> Tried to use net.eth2 in boot group: it works,
There's no need to do so, they belong into default.
> but I still have the init
> scripts frozen as X starts, up until I hit Ctrl-Alt-F1 and watch them go
> on.
What is the next service
Am Dienstag, 6. Januar 2009 03:55:30 schrieb Nick Cunningham:
> If thats xdm then ive no idea why its starting so early,
Because it's perfectly fine to do so. On my system, there are about 10
services which are started _after_ xdm (kdm).
Bye...
Dirk
signature.asc
Description: This is
On Tue, Jan 6, 2009 at 12:55 AM, Nick Cunningham wrote:
>
>> ...
>>
>
> Ok, that net.* error may mean you have some config in the wrong place (or a
> really old config file). Network configs for all interfaces should go in
> /etc/conf.d/net and then to ensure they get started you create a symlink
>
>
> rc_parallel="NO" (I have tried once, but gave up) and it is really X, I use
> "verbose" framebuffer images
>
> Gonna check that openrc, though.
>
> But, while re-emerging sysvinit:
>
> "
> * WARNING: You have older net.* files in /etc/init.d/
> * They need to be converted to symlinks to net
On Tue, Jan 6, 2009 at 12:02 AM, Francisco Ares wrote:
>
> On Mon, Jan 5, 2009 at 11:21 PM, Nick Cunningham wrote:
>
>>
>> Sorry to answer a question with another one, but how do I know to which
>>> group the services should be added?
>>>
>>> That really might be the solution of my problem. And,
On Mon, Jan 5, 2009 at 11:21 PM, Nick Cunningham wrote:
>
> Sorry to answer a question with another one, but how do I know to which
>> group the services should be added?
>>
>> That really might be the solution of my problem. And, yes, it is really X
>> .
>>
>> This is the output from rc-uptate -s
> Sorry to answer a question with another one, but how do I know to which
> group the services should be added?
>
> That really might be the solution of my problem. And, yes, it is really X .
>
> This is the output from rc-uptate -s :
>acpid | default
>alsasound |
On Mon, Jan 5, 2009 at 10:22 PM, Nick Cunningham
wrote:
>
>
> 2009/1/6 Francisco Ares
>>
>> Hi, guys
>>
>> I've been seeing this for several months now, and I couldn't fix it. It
is easy to workaround, so I didn't want to bother the list before.
>>
>> But when it's enough, it's enough.
>>
>> Whi
2009/1/6 Francisco Ares
> Hi, guys
>
> I've been seeing this for several months now, and I couldn't fix it. It is
> easy to workaround, so I didn't want to bother the list before.
>
> But when it's enough, it's enough.
>
> While booting, I can see the init scripts progress up to the time xdm (kd
Hi, guys
I've been seeing this for several months now, and I couldn't fix it. It is
easy to workaround, so I didn't want to bother the list before.
But when it's enough, it's enough.
While booting, I can see the init scripts progress up to the time xdm (kdm)
starts. Then I lo gin and start to
11 matches
Mail list logo