From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.6.18-rc2 - syslog(0x8,,) seems broken
Date: Wed, 19 Jul 2006 16:32:02 +0200 [thread overview]
Message-ID: <1153319522.9722.6.camel@lycan.lan> (raw)
In-Reply-To: <Pine.LNX.4.64.0607151523180.5623@g5.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
On Sat, 2006-07-15 at 15:27 -0700, Linus Torvalds wrote:
> Ok, there it is, in all the usual places.
>
Currently using the latest git version, and it seems like 'dmesg -n
1' (ie 'syslog(0x8, 0, 0x1)') is broken. IE, kernel messages after
initscripts and 'dmesg -n1' is called goes to console (mostly when newer
udev does its coldplug thing).
If nobody have a hunch what it can be, I'll try to track it later on if
I get time. It still worked shortly with -git checkouts shortly before
2.6.18-rc1 was release. Unfortunately I did not have time to test newer
kernels until now.
Regards,
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-07-19 14:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-15 22:27 Linux v2.6.18-rc2 Linus Torvalds
2006-07-16 14:34 ` Linux v2.6.18-rc2 | UTS Release version does not match current version Michael Krufky
2006-07-16 20:36 ` Joel Becker
2006-07-16 21:12 ` Alistair John Strachan
2006-07-17 0:56 ` Joel Becker
2006-07-16 19:41 ` Linux v2.6.18-rc2 Olaf Hering
2006-07-16 20:40 ` Adrian Bunk
2006-07-16 22:45 ` David Woodhouse
2006-07-19 14:32 ` Martin Schlemmer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1153319522.9722.6.camel@lycan.lan \
--to=azarah@nosferatu.za.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.