[Mageia-dev] Minimum install of cauldron don't start console

Tue Mar 6 14:51:26 CET 2012

'Twas brillig, and Pascal Terjan at 06/03/12 13:34 did gyre and gimble:
+> On Tue, Mar 6, 2012 at 13:23, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+>> 'Twas brillig, and Olivier Thauvin at 06/03/12 12:38 did gyre and gimble:
+>>> * Colin Guthrie (mageia at colin.guthr.ie) wrote:
+>>>> 'Twas brillig, and Olivier Thauvin at 06/03/12 09:24 did gyre and gimble:
+>>>>> Hi there,
+>>>>>
+>>>>> I just try to install a cauldron to setup a test IPv6 firewall/router.
+>>>>> To setup server I do a minimum install:
+>>>>> - /boot on its own partition
+>>>>> - /var /tmp and swap on lvm
+>>>>> - select no packages categories but yes install doc
+>>>>> - no post configuration, so no X11 (hey it's a server)
+>>>>>
+>>>>> At boot the system started but stop to "starting display manager" (??)
+>>>>> and I were unable to reach any text terminal.
+>>>>
+>>>> No text terminal at all? Not on tty2 or 3?
+>>>
+>>> Indeed, alt + F2 show the login prompt. But before I pressed alt + F2 ps
+>>> was not showing any "*getty" program, a bit confusing, especially since
+>>> there is nothing on first console.
+>>>
+>>>>
+>>>> If you try and start dm (prefdm.service) then you will NOT get a tty1
+>>>> getty (prefdm.service conflicts with getty at tty1.service), but all other
+>>>> tty's should be fine (handled by autovt at .service)
+>>>
+>>> Maybe, but I never asked to have prefdm and in fact I don't want X
+>>> terminal.
+>>
+>> They why are you booting to a graphical target?
+> 
+>>From what I read, because that's what was done during installation
+> 
+> prefdm shouldn't be there on installs without X
+
+Well both the service (part of systemd-units) and the script (part of
+initscripts) will certainly exist.
+
+And prefdm.service is a hard requirement of graphical.target (due to
+/lib/systemd/system/graphical.target.wants/display-manager.service
+symlink) [display-manager.service is in turn a symlink to prefdm.service
+- longer term it'll probably become the official name instead of prefdm]
+
+
+The thing is that the default.target symlink should change between
+multi-user.target and graphical.target (or runlevel3.target and
+runlevel5.target which are compatibility symlinks for the newer, more
+descriptive names).
+
+This symlink structure is equiv to the line in inittab:
+id:5:initdefault:
+where 5 or 3 are the typical values.
+
+> When you install a new machine (without X) and boot it, you expect to
+> be given a login prompt
+
+I would agree. In that case the code should ensure that
+multi-user.target or runlevel3.target is used.
+
+We need to check what the inittab file says too. The drakx code that
+deals with runlevels should keep the default.target symlink and inittab
+file in sync. If a fresh install like this includes an initab with 5,
+then that's a problem.
+
+Or perhaps we just need to create a default.target in the %post of
+systemd-units if it doesn't exist and default it to whatever inittab
+says? I'm pretty sure the installer code should take care of creating
+this symlink tho'.... will try and double check with a clean install in
+a VM.
+
+Col
+
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+