I second that. I've used Red Hat for many years, and the start up
messages have grown so much that it's hard to find useful information
amongst all the clutter. But I always turn off the graphical boot
anyway. On the other end, Solaris never tells you enough.

I absolutely love the OpenBSD dmesg. It's concise yet thorough.
There's no need to dig through /proc files (Linux) or run prtconf -v
(Solaris) for system configuration info.

The only use case for a silent boot that makes sense to me is an
embedded device, so as not to frighten the end users. But then you cut
out a lot of valuable information when something goes wrong. But maybe
there are other use cases I haven't thought of.

-- Michael

On Tue, Jul 6, 2010 at 1:11 AM, Vadim Zhukov <persg...@gmail.com> wrote:
> 2010/7/6 Ilya Ilembitov <ilembi...@gmail.com>:
>> But what if my system couldn't actually boot? For that
>> kind of occasion, I need my whole dmesg to be stored at any given
>> point, so I could access it. How do I do that?
>
> And where do you want dmesg to be saved if system did not mount any
> filesystems? And if mounted, there is /var/run/dmesg.boot.
>
> I do not see the problem with chatty dmesg. Moreover, after looking in
> Linux ones I found OpenBSD boot logs rather compact and elegant. What
> the problem with ignoring it? And what problem do you want to solve
> implementing graphical bootup?
>
> --
>  WBR,
>  Vadim Zhukov

Reply via email to