Hi

I like to disable Xorg at startup for default.
What must I change in the boot sequence?

peter

On Mar 29, 3:04 pm, Peter <u...@domain.invalid> wrote:
> Hi
>
> I like to disable Xorg at startup for default.
> What must I change in the boot sequence?

In the boot sequence? Nothing

However, in your /etc/inittab file, change the initdefault line from
run level 4 to run level 3. That is to say, change
id:4:initdefault:
to
id:3:initdefault:

On your next reboot/coldstart, you will start up in console mode
rather than in X mode

HTH
--
Lew

Lew Pitcher schreef:
> On Mar 29, 3:04 pm, Peter <u...@domain.invalid> wrote:
>> Hi
>>
>> I like to disable Xorg at startup for default.
>> What must I change in the boot sequence?
>
> In the boot sequence? Nothing
>
> However, in your /etc/inittab file, change the initdefault line from
> run level 4 to run level 3. That is to say, change
> id:4:initdefault:
> to
> id:3:initdefault:
>
> On your next reboot/coldstart, you will start up in console mode
> rather than in X mode
>
> HTH
> --
> Lew
>
>
>
Lew

I have id:2:initdefault: as default value
But I see the grafical login console

Peter <user@domain.invalid> writes:

>Hi

>I like to disable Xorg at startup for default.
>What must I change in the boot sequence?

Edit /etc/inittab. In the line starting with
id:5
make it start with
id:3
instead.

(Well, debian may have other numbering. Read what it says in /etc/inittab
about the various runlevels)



>peter

Peter wrote:
> Lew Pitcher schreef:
>
>> On Mar 29, 3:04 pm, Peter <u...@domain.invalid> wrote:
>>
>>> Hi
>>>
>>> I like to disable Xorg at startup for default.
>>> What must I change in the boot sequence?
>>
>>
>> In the boot sequence? Nothing
>>
>> However, in your /etc/inittab file, change the initdefault line from
>> run level 4 to run level 3. That is to say, change
>> id:4:initdefault:
>> to
>> id:3:initdefault:
>>
>> On your next reboot/coldstart, you will start up in console mode
>> rather than in X mode
>>
>> HTH
>> --
>> Lew
>>
>>
>>
> Lew
>
> I have id:2:initdefault: as default value
> But I see the grafical login console

Debian doesn't make any difference between by default between runlevels
2, 3, 4 and 5.

I have a debian etch running that uses gdm to start the graphical
login sessions. To prevent gdm from starting in runlevel 2 I would
rename the /etc/rc2.d/S21gdm symbolic link to /etc/rc2.d/K21gdm

If you are using another display manager (kdm, xdm) the name and
probably the number of your symbolic link will be different.


Regards,

Kees.

--
Kees Theunissen.

On 03/29/2007 02:04 PM, Peter wrote:
> Hi
>
> I like to disable Xorg at startup for default.
> What must I change in the boot sequence?
>
> peter

Read "man update-rc.d"; you want to remove /etc/rc2.d/S99gdm and
possibly replace it with /etc/rc2.d/K01gdm. Let the update-rc.d command
do this for you.

http://www.debian.org/doc/manuals/re...l#s-no-x-start

Peter <user@domain.invalid> wrote:
>
> I like to disable Xorg at startup for default.
> What must I change in the boot sequence?

Add the word "false" on a new line to the file
/etc/X11/default-display-manager .

--
Nik

On Thu, 29 Mar 2007 23:29:30 +0200,
Kees Theunissen <theuniss@rijnh.nl> wrote:

> I have a debian etch running that uses gdm to start the graphical
> login sessions. To prevent gdm from starting in runlevel 2 I would
> rename the /etc/rc2.d/S21gdm symbolic link to /etc/rc2.d/K21gdm

According to the documentation for update-rc.d, that K link should
actually be K79gdm, not K21gdm. (Assuming that I can count. )

Although I notice on my system, a large number of init scripts do in
fact use the same value for both S and K, while there are also several
that use the complimentary value. Doesn't seem to have caused any real
problems, though. *shrugs*


Fredderic

Fredderic wrote:
> On Thu, 29 Mar 2007 23:29:30 +0200,
> Kees Theunissen <theuniss@rijnh.nl> wrote:
>
>
>>I have a debian etch running that uses gdm to start the graphical
>>login sessions. To prevent gdm from starting in runlevel 2 I would
>>rename the /etc/rc2.d/S21gdm symbolic link to /etc/rc2.d/K21gdm
>
>
> According to the documentation for update-rc.d, that K link should
> actually be K79gdm, not K21gdm. (Assuming that I can count. )

Yeah, you're probably right. I was wondering if the number had to
be adjusted. I'm new to debian and still prefer Slackware that I'm
using for about 11 years.
I was already looking for a tool -or at least the correct way-
to disable services, else than a brute uninstall.
Peter's question was a good reason te start looking again.

I found in the update-rc.d(8) manpage:

A common system administration error is to delete the links
with the thought that this will "disable" the service, i.e.,
that this will prevent the service from being started. However,
if all links have been deleted then the next time the package is
upgraded, the package's postinst script will run update-rc.d
again and this will reinstall links at their factory default
locations. The correct way to disable services is to configure
the service as stopped in all runlevels in which it is started by
default. In the System V init system this means renaming the
service's symbolic links from S to K.

Here I stopped reading. There is no mention at all about adjusting
the number. And, as there are no /etc/rc2.d/K* symlinks at all
on my system, adjusting the number wouldn't make any difference
(for now).

>
> Although I notice on my system, a large number of init scripts do in
> fact use the same value for both S and K, while there are also several
> that use the complimentary value. Doesn't seem to have caused any real
> problems, though. *shrugs*
>

From the same manpage:

links will have sequence number 20, but this can be overridden by
supplying one NN or two SS and KK arguments; a single argument
overrides the sequence number for both start and stop links whereas
a pair of arguments overrides the sequence numbers for start and
stop links, respectively.

As a rule of thumb, the sequence number of the stop link should be
100 minus the sequence number of the start link; this causes services
to be stopped in the opposite order to that in which they are started.
Obviously, therefore, the default stop sequence number should be 80.
Defaulting to 20, as update-rc.d does, is an old bug that cannot be
fixed because of the risk of breaking things.

Looks like a known issue.
I hope, and assume, that the numbers are correct for those services
where the starting/stopping order is important.

>
> Fredderic


Regards,

Kees.

--
Kees Theunissen.