linux-kernel - Idea: new parameter: save_boot_messages_to_a_file

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>] [day] [month] [year] [list]

Date:	Wed, 13 Aug 2014 10:37:16 +0800
From:	積丹尼 Dan Jacobson <jidanni@...anni.org>
To:	linux-kernel@...r.kernel.org
Subject: Idea: new parameter: save_boot_messages_to_a_file_on=/dev/sdb1

Problem: boot messages fly off the screen before the kernel panic is reached.
Possible to write boot messages to a file on a USB stick?

Gentlemen, we all know what a hassle it can be to get all those error
messages that fly off your screen upon failed boots. One needs extra
equipment etc.

Well how about a new parameter that one could add there via typing "e"
in grub,

 linux /boot/vmlinuz... root=... ro single panic=333 save_boot_messages_to_a_file_on=/dev/sdb1

Whereas normally the system would be just attempted to be booted, upon
seeing the "save_boot_messages_to_a_file_on=" parameter, the kernel's
first job would be to start writing copies of messages that it sends to
the screen to some file (default BOOTMES.TXT) on /dev/sdb1 , then
proceed to do the booting, making sure after writing its final stack
trace to the screen to then close that file and sync it to the disk
before giving up and starting the panic wait.
--
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/