https://bugzilla.novell.com/show_bug.cgi?id=728921 https://bugzilla.novell.com/show_bug.cgi?id=728921#c David Majda changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728921 https://bugzilla.novell.com/show_bug.cgi?id=728921#c2 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |werner@suse.com AssignedTo|werner@suse.com |fcrozat@suse.com --- Comment #2 from Dr. Werner Fink 2011-11-08 15:38:57 UTC ---

maintainer systemd bugowner of Base:System/systemd -- fcrozat@suse.com

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728921 https://bugzilla.novell.com/show_bug.cgi?id=728921#c4 --- Comment #4 from Dr. Werner Fink 2011-11-08 15:59:16 UTC --- (In reply to comment #3) Is there a way to delay the agetty on tty1 upto the point where the boot process is (mostly) finished for e.g. using syslog+console as output? Or the other way to use syslog+tty10 as output before starting agetty on tty1? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728921 https://bugzilla.novell.com/show_bug.cgi?id=728921#c6 --- Comment #6 from Dr. Werner Fink 2011-11-08 16:35:44 UTC --- There seems to be a bug in /lib/systemd/system/bootsplash-quit.service ... [Unit] Description=Terminate bootsplash After=xdm.service rc-local.service bootsplash-startup.service Before=getty@tty1.service DefaultDependencies=no Names=plymout-quit-wait.service ^ --------------+ s/t-/th-/ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728921 https://bugzilla.novell.com/show_bug.cgi?id=728921#c8 --- Comment #8 from David Majda 2011-11-09 09:29:41 UTC --- I don't know whether the typo fix was supposed to fix the problem but I tried again in Studio with the fixed file put as an overlay file into the appliance. The result is still the same. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728921 https://bugzilla.novell.com/show_bug.cgi?id=728921#c10 James Mason changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jmason@suse.com --- Comment #10 from James Mason 2011-11-09 20:13:27 UTC --- Although we've already made this assumption, its worth documenting that this does not happen with sysvinit; only systemd. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728921 https://bugzilla.novell.com/show_bug.cgi?id=728921#c12 Tim Hardeck changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fcrozat@suse.com, | |thardeck@suse.com AssignedTo|fcrozat@suse.com |thardeck@suse.com --- Comment #12 from Tim Hardeck 2012-08-21 13:36:13 UTC --- It looks like the issue doesn't appear with a regular openSUSE server installation because they are using the kernel parameter "quiet" which Kiwi Jeos doesn't. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728921 https://bugzilla.novell.com/show_bug.cgi?id=728921#c14 --- Comment #14 from David Majda 2012-08-21 15:03:05 UTC --- (In reply to comment #13)

Marcus, could you add the kernel parameter "quiet" to Jeos?

Just to make everything clear: This is not a KIWI JeOS-specific thing, it affects all text-mode 12.1 and 12.2 appliances in Studio. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728921 https://bugzilla.novell.com/show_bug.cgi?id=728921#c16 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ms@suse.com |jatan@suse.com --- Comment #16 from Marcus Schaefer 2012-08-21 15:23:09 UTC --- you can't be serious on that, I should suppress all kernel messages just because one has to hit a key in order to see the getty login prompt ? sorry guys it must be possible for a linux service daemon to show the user a good result after all required/intermediate services are ready. I'm not willing to add quiet as a default boot option. If studio wants to do that use the kernelcmdline attribute in your <type> setup I strongly recommend to prevent it though what the heck is going on here ? are we really moving into the Windows direction were it's not possible even not by option to see what the core system does at boot time ? I don't want to be forced to watch an animation while the system boots up as for the kiwi way and because I know that nearly all people doesn't like what I wrote I say it again, you can add this parameter in your own appliance setup because kiwi supports that but I'm not going to make quiet part of the default boot option set Assigning back to studio thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728921 https://bugzilla.novell.com/show_bug.cgi?id=728921#c18 David Majda changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jatan@suse.com |thardeck@suse.com --- Comment #18 from David Majda 2012-08-22 07:38:50 UTC --- Requiring users to press a key to see a login prompt is a major usability issue when using Studio's testdrive. Imagine a new user who builds a JeOS image. He boots it in test drive and at some point the screen becomes static. He presses some keys but nothing happens because the focus is not on the flash player (this is another issue we should probably try solve if possible). Because he doesn't know anything about the focus, he concludes this whole Studio thing is broken and leaves. If the user saw the login prompt there is much bigger chance that he would discover that the problem is just in the focus being wrong, because the screen wouldn't look broken. But this is not just about testdrive. From user's POV, the fact that he has to press a key to reveal the login prompt is just stupid. It is an unnecessary step. As a user I would immediately think about lack of attention to detail and usability by openSUSE/KIWI/Studio developers and I would start to wonder whether other parts of the system are the same. ----- My rule when supporting new openSUSE's in Studio always was to mimic the regular distro experience as much as possible. If the regular distro uses the "quiet" param, so should we. The boot experience should be as similar as we can make it. This guideline is very important for Studio. Now I wanted to fix this in KIWI because this apparently isn't a Studio's problem. But if Marcus is unwilling to do this change in KIWI, we should fix it on our side. Tim, does using the "quiet" param make the JeOS/Server template boot sequence look closer to the regular openSUSE boot sequence (in text mode)? If so and if this also solves the login prompt problem, please make Studio pass the "quiet" param to KIWI. If not, we'll have to look for the solution elsewhere. ----- As a sidenote, I think that after the boot the user should see exactly two things: 1. The OS welcome screen 2. The login prompt Everything else is just a garbage that gives an impression of unfriendliness and makes the user fell less in control of his system (because he sees something he does not understand). Even I as a user don't care the slightest bit what happens inside the computer during the boot -- because I don't want to debug it, I want to *use* it. But my opinon is mostly irrelevant here -- as I wrote above, we should mimic what the regular distro does. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728921 https://bugzilla.novell.com/show_bug.cgi?id=728921#c20 Tim Hardeck changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #20 from Tim Hardeck 2012-08-27 15:33:07 UTC --- This should be fixed now for openSUSE 12.1 and 12.2 in Studio. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.