Fwd: Re: [opensuse] openSUSE 12.1 boot progress indicator
I think you still missed the reply-all button it but I'll forward it. And I think a progress bar that didn't actually show the progress of anything would look stupid not "pro end". You can't have a progress bar because there is no progress to measure. What you could have is a busy indicator. A spinner or other cyclic animation. Every time a systemd action happened, the animation moves a frame. Something that repeats, cycles, or oscillates, not goes from start to finish, because _there is no finish_. The processes that get started up do not get started up in any predefined order, nor is there a predefined list of things that should be running and actions that should be taken to consider yourself done booting up. There is no such thing as a target condition that represents boot completion and so asking for a progress bar that shows progress towards boot completion is like asking for pet fish claw trimmers. I understand all your previous pet dogs and cats had claws that needed trimming, but pet fish just don't work that way. -- bkw -------- Original Message -------- Subject: Re: [opensuse] openSUSE 12.1 boot progress indicator Date: Thu, 16 Feb 2012 10:29:41 -0300 From: Hernan_ <hernanthiers@gmail.com> To: Brian K. White <brian@aljex.com> Sorry I miss the ANSWER TO ALL button 2012/2/16 Hernan_ <hernanthiers@gmail.com>:
What does people think about geekos eyes as the load indicator? I think it's "funny" but in the end a progress bar may look more pro end.
2012/2/16 Brian K. White <brian@aljex.com>:
Under systemd there can be no such thing as a progress indicator because there is no such thing as "100% completed" or any other % completed. Because that is one of the fundamental differences in the way systemd works vs how sysvinit works. Systemd does not process a list of scripts in an orderly fashion and there is no first and no last action. Systemd reads all it's various service descriptor config files and all of them start doing their individual things essentially at the same time. Some do have to wait for others, but there is no inherent order laid down ahead of time like sysv init scripts. Also, many services start and stop dynamically in response to various run-time conditions. There isn't a "done" state, because it's basically always watching to start and stop things if they are needed the entire time the machine is running, even one second before you shut it off after a year, not just starting them all up once at the beginning. Since there is no "done" state, there is no such thing as "75% of the way to done" either.
There might be _something_ that could be monitored in systemd that could give you _some_ sort of progress, but I don't know what it would be or how it would work. basically, at least right now, it's just a meaningless concept.
-- bkw
On 2/16/2012 5:49 AM, Istvan Gabor wrote:
2012. február 15. 21:37 napon Steven Hess<flamebait@gmail.com> írta:
On Wed, Feb 15, 2012 at 6:50 AM, Peter Suetterlin <P.Suetterlin@royac.iac.es> wrote:
Istvan Gabor wrote:
Hello:
The subject tells: How can get a boot progress indicator in oS 12.1? A similar one to any of that of previous suse versions.
I'd be happy to get *any* info on the progress. Even screen output in text mode is stopped after fsck - the first time I thought the system has crashed.
-- Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit Institute for Solar Physics Tel.: +34 922 405 590 (Spain) P.Suetterlin@royac.iac.es +46 8 5537 8507 (Sweden) Peter.Suetterlin@astro.su.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
My /boot/grub/menu.lst stanza looks like this and I get a verbose boot in 12.1:
title Desktop -- openSUSE 12.1 - 3.1.9-1.4 (desktop) root (hd0,5) kernel /boot/vmlinuz-3.1.9-1.4-desktop root=/dev/disk/by-id/ata-ST3500630AS_9QG141S6-part6 resume=/dev/disk/by-id/ata-ST3500630AS_9QG141S6-part5 splash=verbose verbose showopts vga=0x31a initrd /boot/initrd-3.1.9-1.4-desktop
Hope this helps.
This is different thing. I meant that the splash screen in every previous suse version showed a progress bar which indicated that the progress of the boot process. For some reason the developers removed this progress bar and only the splash image is shown. You can press escape and go to verbose mode any time but then you can not get back to the splash screen.
What Peter mentioned about fsck was again a different issue. From 11.x version the progress of fsck is not shown at boot. In 9.x and 10.x versions the fsck showed its progress during boot.
This was discussed here: http://lists.opensuse.org/opensuse/2010-02/msg01277.html but no solution was given, only hints, and I could not solve it.
I would like to know how I could enable fsck progress bar for both root and non-root filesystems during bootup.
Peter, if you are interested in this one, please start a specific new thread devoted to this question.
Istvan
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- Hernán Thiers Garcia Ingeniero Informático Santiago, Chile.
-- Hernán Thiers Garcia Ingeniero Informático Santiago, Chile. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Feb 16, 2012 at 10:31 AM, Brian K. White <brian@aljex.com> wrote:
I think you still missed the reply-all button it but I'll forward it.
And I think a progress bar that didn't actually show the progress of anything would look stupid not "pro end".
You can't have a progress bar because there is no progress to measure.
What you could have is a busy indicator.
Isn't that what the Gecko eyes provide now in a 12.1 boot. ie. They move from looking left to right every couple seconds. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
That's right it's a busy indicator and is good but seems that it's not easy to see. I mean there's people who haven't yet found it. 2012/2/16 Greg Freemyer <greg.freemyer@gmail.com>:
On Thu, Feb 16, 2012 at 10:31 AM, Brian K. White <brian@aljex.com> wrote:
I think you still missed the reply-all button it but I'll forward it.
And I think a progress bar that didn't actually show the progress of anything would look stupid not "pro end".
You can't have a progress bar because there is no progress to measure.
What you could have is a busy indicator.
Isn't that what the Gecko eyes provide now in a 12.1 boot. ie. They move from looking left to right every couple seconds.
Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- Hernán Thiers Garcia Ingeniero Informático Santiago, Chile. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/02/16 12:48 (GMT-0300) Hernan_ composed:
Greg Freemyer composed:
Brian K. White wrote:
You can't have a progress bar because there is no progress to measure.
What you could have is a busy indicator.
Isn't that what the Gecko eyes provide now in a 12.1 boot. ie. They move from looking left to right every couple seconds.
That's right it's a busy indicator and is good but seems that it's not easy to see. I mean there's people who haven't yet found it.
This is why I always get rid of GUI boot. It seems most people responsible for packaging such things have no knowledge of the meaning or need for accessibility, choosing to theme less than full screen and with low contrast colors. To some people a puter is a necessary tool, not a toy, and things need to just work without getting in the way of goals. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 16 Feb 2012 11:29:32 -0500, Felix Miata <mrmazda@earthlink.net> wrote:
To some people a puter is a necessary tool, not a toy, and things need to just work without getting in the way of goals.
And then there are the folks who regard any text message while booting an error. For those the hiding is perfect. For the others it's very easy to add 'splash=verbose' to the kernel command line, best when booting for installation as the the command is copied over to grubs boot menu. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Brian K. White
-
Felix Miata
-
Greg Freemyer
-
Hernan_
-
Philipp Thomas