linux-kernel - Re: Boot Consoles question...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090704102904.GB32257@elte.hu>
Date:	Sat, 4 Jul 2009 12:29:04 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Robin Getz <rgetz@...ckfin.uclinux.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Boot Consoles question...


* Robin Getz <rgetz@...ckfin.uclinux.org> wrote:

> Quick question...
> 
> In register_console()
> 
>         if (bcon && ((newcon->flags & (CON_CONSDEV | CON_BOOT)) == 
> CON_CONSDEV)) {
> 		[[snip]]
>                 newcon->flags &= ~CON_PRINTBUFFER;
>         }
> 
> So - when we are switching over from a boot console to a "real" 
> console - we don't back up the console, and print everything out.
> 
> This means that the boot console is on a different device than 
> that "real" console - you don't actually see the full boot message 
> (from log_start) on the "real" console.
> 
> Is this what is intended (that the boot message gets split into 2 
> - 1/3 going into the bootconsole - and the remaining to to the 
> real console?)
> 
> I can understand this when both (boot and real) are the same 
> device (serial) or vga, but where they are not - it is a little 
> confusing to the user - isn't it?

Could be changed i guess ... but is it really an issue? All messages 
should be in the syslog buffer (if it's large enough). One artifact 
could be manual scroll-back - it would perhaps be nice indeed to 
allow the scrollback to the top of the bootlog.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/