linux-kernel - Re: printk behavioral regression

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: <CAPXgP13y_xOUzHdStsDWescPtJYn0nvMhsQ7c2XS3HBuE=jwow@mail.gmail.com>
Date:	Tue, 19 Jun 2012 15:53:53 +0200
From:	Kay Sievers <kay@...y.org>
To:	Jan Beulich <JBeulich@...e.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: printk behavioral regression

On Tue, Jun 19, 2012 at 3:30 PM, Jan Beulich <JBeulich@...e.com> wrote:
> running 3.5-rc3 on a SLE11 SP1 system, early boot messages (apart
> from the very first one) end up in /var/log/messages rather than
> /var/log/boot.msg. I didn't dig deep enough yet to figure out what
> is causing this, and would hope that you (having contributed most
> of the changes between 3.4 and 3.5-rc3) might have an idea.

Hmm, no idea really, and why this should change.

/var/log/boot.msg is a SUSE speciality, that, as far as I know, just
dumps 'dmesg' after bootup, it has not much to do with the normal
syslog/klog logging in /var/log/messages, where all your messages should always
end up, and what seems to work for you.

Kay
--
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/