From: Mike Fedyk <mfedyk@matchmail.com>
To: Ian Stirling <root@mauve.demon.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Please tag tested releases of the 2.4.x kernel
Date: Fri, 30 Nov 2001 18:53:06 -0800 [thread overview]
Message-ID: <20011130185306.N504@mikef-linux.matchmail.com> (raw)
In-Reply-To: <20011130171017.L504@mikef-linux.matchmail.com> <200112010242.CAA12521@mauve.demon.co.uk>
In-Reply-To: <200112010242.CAA12521@mauve.demon.co.uk>
On Sat, Dec 01, 2001 at 02:42:02AM +0000, Ian Stirling wrote:
> >
> > On Sat, Dec 01, 2001 at 02:05:21AM +0100, willy tarreau wrote:
> > > I think that if even one tenth of the LKML
> > > subscribers rank their kernels at least once a week,
> > > we'll quickly see some stable and unusable kernels.
> > >
> >
> > I like this idea a lot.
> >
> > Who can get such a system up and running? Which web site?
>
> I've proposed in the past a more extensive version of this.
> make register
> or similar.
I think I remember reading about that on kernel traffic...
> Which you run, and it grabs a snapshot of system setup, optionally
> with comments, and sends it in to a registry.
> You can then do
> make comment
> and report issues.
> These would vary from "it crashes", to "my hard drive died/is dying"
> So we get information on systems, and some idea on which are reliable
> or not.
>
I think people would have trouble with the versions of their apps being
reported. Some people that is...
But, all something like this really needs is just to be blessed by someone
high in the kernel strata...
It doesn't actually *need* to be in the kernel though. A user space package
would work great. Run from a cron job, and report kernel version, and
optionally some other pertinent info.
Perodically, (monthly?) you would get an email asking you to fill out this
form and you'd get your registry with bug/status reports.
Even bigger, some sort of bug tracking system could be tied to this...
mf
> Last time some people disagreed with this obviously brilliant idea. :/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2001-12-01 2:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-01 1:05 Please tag tested releases of the 2.4.x kernel willy tarreau
2001-12-01 1:10 ` Mike Fedyk
2001-12-01 2:42 ` Ian Stirling
2001-12-01 2:53 ` Mike Fedyk [this message]
2001-12-01 11:31 ` Miquel van Smoorenburg
-- strict thread matches above, loose matches on Subject: below --
2001-12-02 23:38 Justin Wells
2001-11-30 22:04 Justin Wells
2001-11-30 23:15 ` Mike Fedyk
2001-12-01 0:28 ` Mike Fedyk
2001-12-01 9:41 ` Christoph Hellwig
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=20011130185306.N504@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@mauve.demon.co.uk \
/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