From: Mike Dresser <mdresser_l@windsormachine.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6 not cat proof
Date: Wed, 26 Nov 2003 15:41:05 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.56.0311261533310.489@router.windsormachine.com> (raw)
In-Reply-To: <20031126201052.GA16106@outpost.ds9a.nl>
On Wed, 26 Nov 2003, bert hubert wrote:
> This bug has been seen here over eight years ago and it is back.. linux
> 2.6.0-test4 is still not cat proof :-)
There has been a fix for this issue in the kernel source for quite awhile.
>From as far back as the configuration utility in 2.4.22:
CONFIG_WATCHDOG:
If you say Y here (and to one of the following options) and create a
character special file /dev/watchdog with major number 10 and minor
number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
It should be under Character devices somewhere.
Hope this helps,
Mike
next prev parent reply other threads:[~2003-11-26 20:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 20:10 2.6 not cat proof bert hubert
2003-11-26 20:16 ` Nigel Cunningham
2003-11-26 20:38 ` William Lee Irwin III
2003-11-27 7:30 ` Gábor Lénárt
2003-11-27 8:54 ` Måns Rullgård
2003-11-27 11:57 ` Paul Jackson
2003-11-27 16:41 ` Måns Rullgård
2003-11-27 17:37 ` Gene Heskett
2003-11-27 18:21 ` Nigel Cunningham
2003-11-28 10:43 ` Harald Arnesen
2003-11-30 20:09 ` Bernd Petrovitsch
2003-11-30 21:37 ` Henrik Persson
2003-12-01 1:46 ` Stuart Longland
2003-11-26 20:41 ` Mike Dresser [this message]
2003-11-26 20:48 ` Edesio Costa e Silva
2003-11-26 23:46 ` Mike Fedyk
2003-11-27 0:50 ` Måns Rullgård
2003-11-27 1:06 ` Mike Fedyk
2003-11-27 8:52 ` Stuart Longland
2003-11-26 20:42 ` Måns Rullgård
2003-11-28 4:19 ` Tim Connors
2003-11-29 13:36 ` Bill Davidsen
2003-11-29 14:23 ` Gene Heskett
2003-11-29 16:36 ` Markus Hästbacka
2003-11-30 14:29 ` Bill Davidsen
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=Pine.LNX.4.56.0311261533310.489@router.windsormachine.com \
--to=mdresser_l@windsormachine.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).