On Thu, Nov 20, 2008 at 8:31 AM, Freddie Cash <[EMAIL PROTECTED]> wrote:
> On November 20, 2008 02:42 am Nate Eldredge wrote:
>> On Thu, 20 Nov 2008, Jeremy Chadwick wrote:
>> > On Wed, Nov 19, 2008 at 11:48:36PM -0800, Nate Eldredge wrote:
>> >> On Wed, 19 Nov 2008, Jeremy Chadwick wrote:
>> >>> O
On November 20, 2008 02:42 am Nate Eldredge wrote:
> On Thu, 20 Nov 2008, Jeremy Chadwick wrote:
> > On Wed, Nov 19, 2008 at 11:48:36PM -0800, Nate Eldredge wrote:
> >> On Wed, 19 Nov 2008, Jeremy Chadwick wrote:
> >>> On Thu, Nov 20, 2008 at 05:39:36PM +1100, Peter Jeremy wrote:
> I hope that
On Nov 20, 2008, at 4:03 AM, Jeremy Chadwick wrote:
This has two problems, but I'm probably missing something:
1) See my original post, re: users of our systems use "dmesg" to find
out what the status of the system is. By "status" I don't mean "from
the point the kernel finished to now", I li
On Thu, 20 Nov 2008, Jeremy Chadwick wrote:
On Wed, Nov 19, 2008 at 11:48:36PM -0800, Nate Eldredge wrote:
On Wed, 19 Nov 2008, Jeremy Chadwick wrote:
On Thu, Nov 20, 2008 at 05:39:36PM +1100, Peter Jeremy wrote:
I hope that never gets committed - it will make debugging kernel
problems muc
On Thu, Nov 20, 2008 at 10:53:07AM +0100, Dag-Erling Smørgrav wrote:
> Jeremy Chadwick <[EMAIL PROTECTED]> writes:
> > Peter Jeremy <[EMAIL PROTECTED]> writes:
> > > This is deliberate. If the system panics, stuff that was in the
> > > message buffer (and might not be on disk) can be read when the
On Wed, Nov 19, 2008 at 11:48:36PM -0800, Nate Eldredge wrote:
> On Wed, 19 Nov 2008, Jeremy Chadwick wrote:
>
>> On Thu, Nov 20, 2008 at 05:39:36PM +1100, Peter Jeremy wrote:
>
>>> I hope that never gets committed - it will make debugging kernel
>>> problems much harder. There is already a kern.m
Jeremy Chadwick <[EMAIL PROTECTED]> writes:
> Peter Jeremy <[EMAIL PROTECTED]> writes:
> > This is deliberate. If the system panics, stuff that was in the
> > message buffer (and might not be on disk) can be read when the
> > system reboots. If there is no crashdump, this might be the only
> > re
On Wed, 19 Nov 2008, Jeremy Chadwick wrote:
On Thu, Nov 20, 2008 at 05:39:36PM +1100, Peter Jeremy wrote:
I hope that never gets committed - it will make debugging kernel
problems much harder. There is already a kern.msgbuf_clear sysctl and
maybe people who are concerned about msgbuf leakage
On Thu, Nov 20, 2008 at 05:39:36PM +1100, Peter Jeremy wrote:
> On 2008-Nov-19 02:47:31 -0800, Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> >There's a known "issue" with the kernel message buffer though: it's not
> >NULL'd out upon reboot.
>
> This is deliberate. If the system panics, stuff that
On 2008-Nov-19 02:47:31 -0800, Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
>There's a known "issue" with the kernel message buffer though: it's not
>NULL'd out upon reboot.
This is deliberate. If the system panics, stuff that was in the
message buffer (and might not be on disk) can be read when th
On Tue, Nov 18, 2008 at 7:34 PM, Ed Schouten <[EMAIL PROTECTED]> wrote:
> Hello Carlos, others,
>
> * Ed Schouten <[EMAIL PROTECTED]> wrote:
>> About the /dev/console issues: Robert Watson and I discussed this some
>> time ago on IRC and what I did in HEAD (not RELENG_7) was that I changed
>> TIOCC
On Wed, Nov 19, 2008 at 02:02:42AM -0800, Garrett Cooper wrote:
> On Tue, Nov 18, 2008 at 1:49 PM, David Wolfskill <[EMAIL PROTECTED]> wrote:
> > On Tue, Nov 18, 2008 at 10:34:10PM +0100, Ed Schouten wrote:
> >> ...
> >> One solution would be to let xconsole just display /var/log/messages.
> >
> >
On Tue, Nov 18, 2008 at 1:49 PM, David Wolfskill <[EMAIL PROTECTED]> wrote:
> On Tue, Nov 18, 2008 at 10:34:10PM +0100, Ed Schouten wrote:
>> ...
>> One solution would be to let xconsole just display /var/log/messages.
>
> Errr... it may be rather a pathological case, but you might want to
> check
On Tue, Nov 18, 2008 at 10:34:10PM +0100, Ed Schouten wrote:
> ...
> One solution would be to let xconsole just display /var/log/messages.
Errr... it may be rather a pathological case, but you might want to
check the content of /etc/syslog.conf on the local machine before
getting too carried away
Hello Carlos, others,
* Ed Schouten <[EMAIL PROTECTED]> wrote:
> About the /dev/console issues: Robert Watson and I discussed this some
> time ago on IRC and what I did in HEAD (not RELENG_7) was that I changed
> TIOCCONS not to take a look at the permissions of /dev/console, but we
> changed it t
Ed, good day.
Tue, Oct 28, 2008 at 09:11:54AM +0100, Ed Schouten wrote:
> It's nice to hear that the patch didn't break anything on your system. I
> hope to receive more reviews, but I think I'll just commit it this
> weekend (with small modifications).
Just a quick "me too" message: patchset fro
Hello Carlos,
* Carlos A. M. dos Santos <[EMAIL PROTECTED]> wrote:
> The patched source builds and installs flawlessy. However I observed
> something that seems to be a regression. If I run either xconsole or
> xterm -C I only see kernel messages, even though my X startup (via
> XDM) changes the o
On Sun, Oct 26, 2008 at 1:27 PM, Ed Schouten <[EMAIL PROTECTED]> wrote:
> Hello everyone,
>
> Most of you probably already know that I've been very busy improving our
> kernel's TTY implementation. I've committed the new MPSAFE TTY layer
> back in August. So far most of the things seem to work prop
Hello everyone,
Most of you probably already know that I've been very busy improving our
kernel's TTY implementation. I've committed the new MPSAFE TTY layer
back in August. So far most of the things seem to work properly as far
as I can see. There are always some small bugs, but I'm confident we'
19 matches
Mail list logo
