Fernando de Oliveira wrote:
On 01-09-2014 17:33, Fernando de Oliveira wrote:
On 01-09-2014 16:50, Bruce Dubbs wrote:
[email protected] wrote:
--- trunk/bootscripts/Makefile Mon Sep 1 11:26:44 2014 (r14162)
+++ trunk/bootscripts/Makefile Mon Sep 1 12:34:36 2014
(r14163) @@ -277,9 +277,9 @@ ln -sf ../init.d/lxdm
${EXTDIR}/rc.d/rc0.d/K05lxdm ln -sf ../init.d/lxdm
${EXTDIR}/rc.d/rc1.d/K05lxdm ln -sf ../init.d/lxdm
${EXTDIR}/rc.d/rc2.d/K05lxdm - ln -sf ../init.d/lxdm
${EXTDIR}/rc.d/rc3.d/K05lxdm + ln -sf ../init.d/lxdm
${EXTDIR}/rc.d/rc3.d/S95lxdm ln -sf ../init.d/lxdm
${EXTDIR}/rc.d/rc4.d/K05lxdm - ln -sf ../init.d/lxdm
${EXTDIR}/rc.d/rc5.d/S95lxdm + ln -sf ../init.d/lxdm
${EXTDIR}/rc.d/rc5.d/K05lxdm ln -sf ../init.d/lxdm
${EXTDIR}/rc.d/rc6.d/K05lxdm
I think you had it right the first time. The standard definition
of run level 3 is without a gui.
When remembered to test rebooting, after the commit, didn't start.
Only if in runlevel 3. No idea why.
I don't know much about this, but I think I know where the problem
starts and present a first solution.
I have now:
$ head -n8 /etc/inittab
# Begin /etc/inittab
id:5:initdefault:
si::sysinit:/etc/rc.d/init.d/rc S
l0:0:wait:/etc/rc.d/init.d/rc 0
l1:S1:wait:/etc/rc.d/init.d/rc 1
Before, I had:
id:3:initdefault:
This suggested me that LXDM, which is taking the responsibility of
authenticating with PAM, was not allowed, because first, we had to login
at runlevel 3. It simply didn't even start (no mention anywhere in the
logs).
Now, it starts at runlevel 5.
As my knowledge is very limited, and I am facing two alternatives, each
modifying fundamental rules, what is the best solution?
1. Leave the bootscripts as I modified yesterday to start at runlevel 3.
2. Change in /etc/inittab to have id:5:initdefault.
Yes, have the user change initdefault, if desired. The 'init 5' command
also should work from the command line.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
