[SOLVED] disabling slim

fabien · 2019-03-11 20:07:57

Hello,

I just installed DEVUAN and I am discovering sysVinit.

As root I tried service slim stop, it stop the DE right away but slim shoes up at the nest reboot.

How should I disabling slim, I don't need it.

Thank you.

Fabien

Last edited by fabien (2019-03-14 05:38:28)

ralph.ronnquist · 2019-03-11 20:57:23

I don't think the service script can disable a facility, and you'll need to use update-rc.d directly for that. The command line would be

# update-rc.d slim disable

Refer to

$ man update-rc.d

for details.

guuml.dev1 · 2019-03-11 21:31:06

The very traditional sysvinit was introduced some decades ago. In an ideal world It has nothing to do with systemd nor upstart! What's about man service? As of this writing I have read that man page the 1st time, and as far as I understand is saying service slim stop exactly the same as /etc/init.d/slim stop in sysvinit. But what is about the next reboot? As man init states there are several run levels in ls -1d /etc/rc*. You can easily adjust the symbolic links in /etc/rc?.d/ by adding or removing the links, but is this your question?

fabien wrote:

Hello,
....
How should I disabling slim, I don't need it.
Fabien

Are you sure you "don't need" to start the Xorg someway automagically? Did you ever tried startx from the console? What's about other "graphical login managers" like lightdm? What's about auto login as a given user?

@Fabien: As root of my own machine I can prevent starting slim with an command like

# rm /etc/rc?.d/S*slim

But there are consequences ...

ralph.ronnquist · 2019-03-11 22:06:47

Note that "disabling" slim with update-rc.d doesn't uninstall it, and it can well be started and stopped manually also after "disabling", which only means to remove it from the boot sequence.

Manual removal of the rc?.d links (that guuml.dev1 suggests) has almost the same effect, except that it doesn't remove slim from the "/etc/init.d/.depend.*" database, which also plays a role for sysvinit.

guuml.dev1 · 2019-03-11 23:30:34

ralph.ronnquist wrote:

.... has almost the same effect, except that it doesn't remove slim from the "/etc/init.d/.depend.*" database, which also plays a role for sysvinit.

Thanks a lot to the other side of the world especially to ralph.ronnquist! I have NEVER EVER heard about hidden files in /etc/init.d/ up to now! But they REALLY exist in less /etc/init.d/.depend.* as I see (in devuan/ascii at least).

WTF? As far as I can remember from the solaris 2.x manual: There are no "hidden" files. Every start/stop script is placed in /etc/init.d/ and afterwards the local sysadmin has to place the appropriate symlinks to /etc/rc?.d/ according to the naming convention.

Where does this "hidden database" come from? As far as I know there was no written manual at all-

ToxicExMachina · 2019-03-12 06:17:21

{Ctrl+Alt+F2}
{login as user}
su -c "service slim stop && apt-get purge slim"
cp .xinitrc .xinitrc.backup #if exist, just in case
nano ~/.xinitrc
startx

.xinitrc:

#!/bin/sh

/usr/bin/startxfce4 #or a command for starting another WM/DE

Congratulations. Slim was not just disabled but also removed from your system because you said "I don't need it". From now you can run graphical desktop only with startx command. If you want GUI login you have to install display manager (XDM, KDM, GDM, LightDM, Slim, ...). If you want to run another DE or WM you have to edit .xinitrc file or run it from your working WM/DE.

ralph.ronnquist · 2019-03-12 06:34:32

guuml.dev1 wrote:

Where does this "hidden database" come from? As far as I know there was no written manual at all-

Not very new, but it was new to me too until some few years ago... start with $ man insserv, I think.

dxrobertson · 2019-03-12 10:09:52

guuml.dev1 wrote:

Where does this "hidden database" come from? As far as I know there was no written manual at all-

As ralph.ronnquist mentions, the files are maintained by insserv.

The files are generated using the LSB header information in the init scripts themselves. Their purpose is to organize the boot order of the init scripts, based on the requirements of the scripts as defined in their LSB header. These hidden files are then in turn used to generate the numerically ordered sysmlinks in the runlevel directories rc#/d, or for openrc the deptree in /run/openrc.

I suppose they are hidden so not to create confusion in the init.d directory.

xinomilo · 2019-03-12 10:47:57

if you don't need slim at all, remove it.

# apt remove slim

[edit] oops, just read ToxicExMachina's post

Last edited by xinomilo (2019-03-12 10:48:55)

fabien · 2019-03-12 18:55:47

Thank you everybody for the accurate answers.

I am not sure if I don't need it finally, the panels are now long to show up and the wallpaper comes late...

May someone explain me why?

ToxicExMachina · 2019-03-13 06:13:40

fabien wrote:

I am not sure if I don't need it finally, the panels are now long to show up and the wallpaper comes late...
May someone explain me why?

Looks like it's videodriver issue. Could you write here your hardware config? Especially CPU and videocard/GPU.

fabien · 2019-03-13 19:07:08

Here it is:

Intel(R) Core(TM) i5-7600 CPU @ 3.50GHz
VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070]
I am using the proprietary driver....

Thank you for helping me!

ToxicExMachina · 2019-03-13 19:47:55

Are you sure driver works properly?

glxinfo | grep vendor
glxinfo | grep direct

fabien · 2019-03-14 04:24:32

I can't tell you...

meca@i5:~$ glxinfo | grep vendor
server glx vendor string: NVIDIA Corporation
client glx vendor string: NVIDIA Corporation
OpenGL vendor string: NVIDIA Corporation
meca@i5:~$ glxinfo | grep direct
direct rendering: Yes
    GL_AMD_multi_draw_indirect, GL_AMD_seamless_cubemap_per_texture, 
    GL_ARB_direct_state_access, GL_ARB_draw_buffers, 
    GL_ARB_draw_indirect, GL_ARB_draw_instanced, GL_ARB_enhanced_layouts, 
    GL_ARB_indirect_parameters, GL_ARB_instanced_arrays, 
    GL_ARB_map_buffer_range, GL_ARB_multi_bind, GL_ARB_multi_draw_indirect, 
    GL_EXT_depth_bounds_test, GL_EXT_direct_state_access, 
    GL_NV_alpha_to_coverage_dither_control, GL_NV_bindless_multi_draw_indirect, 
    GL_NV_bindless_multi_draw_indirect_count, GL_NV_bindless_texture, 
    GL_AMD_multi_draw_indirect, GL_AMD_seamless_cubemap_per_texture, 
    GL_ARB_direct_state_access, GL_ARB_draw_buffers, 
    GL_ARB_draw_indirect, GL_ARB_draw_instanced, GL_ARB_enhanced_layouts, 
    GL_ARB_indirect_parameters, GL_ARB_instanced_arrays, 
    GL_ARB_map_buffer_range, GL_ARB_multi_bind, GL_ARB_multi_draw_indirect, 
    GL_EXT_depth_bounds_test, GL_EXT_direct_state_access, 
    GL_NV_alpha_to_coverage_dither_control, GL_NV_bindless_multi_draw_indirect, 
    GL_NV_bindless_multi_draw_indirect_count, GL_NV_bindless_texture, 
    GL_EXT_memory_object, GL_EXT_memory_object_fd, GL_EXT_multi_draw_indirect,

ToxicExMachina · 2019-03-14 04:48:34

It seems driver works properly.

Could you give detailed description of the problem? When and how panels, wallpapers and other GUI elements are showing up? How it happens during desktop work? How do you start desktop (slim, startx, or with something else)? Did you try nouveau driver?

fabien · 2019-03-14 05:36:59

Thank you ToxicExMachina, but I won't bothor you fixing this this.

Everything works fine when I use SLIM.

Post #2 answers the original question, I am just trying to understand noSystemd distros.

I will have more to ask on other subjects....

Merci!

Lysander · 2019-03-25 09:40:00

It would be good if this were given as an option during install. Personally I would prefer to drop to console rather than use a greeter.

ToxicExMachina · 2019-03-26 05:51:43

Lysander wrote:

It would be good if this were given as an option during install. Personally I would prefer to drop to console rather than use a greeter.

The option is already in installer: install minimal system. After that you can install X11 and WM or DE. If you would like to login into console i think you know how to configure what you really need.

The officially official Devuan Forum!

#1 2019-03-11 20:07:57

[SOLVED] disabling slim

#2 2019-03-11 20:57:23

Re: [SOLVED] disabling slim

#3 2019-03-11 21:31:06

Re: [SOLVED] disabling slim

#4 2019-03-11 22:06:47

Re: [SOLVED] disabling slim

#5 2019-03-11 23:30:34

Re: [SOLVED] disabling slim

#6 2019-03-12 06:17:21

Re: [SOLVED] disabling slim

#7 2019-03-12 06:34:32

Re: [SOLVED] disabling slim

#8 2019-03-12 10:09:52

Re: [SOLVED] disabling slim

#9 2019-03-12 10:47:57

Re: [SOLVED] disabling slim

#10 2019-03-12 18:55:47

Re: [SOLVED] disabling slim

#11 2019-03-13 06:13:40

Re: [SOLVED] disabling slim

#12 2019-03-13 19:07:08

Re: [SOLVED] disabling slim

#13 2019-03-13 19:47:55

Re: [SOLVED] disabling slim

#14 2019-03-14 04:24:32

Re: [SOLVED] disabling slim

#15 2019-03-14 04:48:34

Re: [SOLVED] disabling slim

#16 2019-03-14 05:36:59

Re: [SOLVED] disabling slim

#17 2019-03-25 09:40:00

Re: [SOLVED] disabling slim

#18 2019-03-26 05:51:43

Re: [SOLVED] disabling slim

Board footer