public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ryan Anderson <ryan@michonline.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Some thoughts about stable kernel development
Date: Tue, 11 Nov 2003 02:47:15 -0500	[thread overview]
Message-ID: <20031111074715.GH22850@michonline.com> (raw)
In-Reply-To: <200311100850.hAA8oiIX000283@81-2-122-30.bradfords.org.uk>

On Mon, Nov 10, 2003 at 08:50:44AM +0000, John Bradford wrote:
> On the other hand, many users out there are _obviously_ under the
> illusion that 2.6.0-test has no known security issues, and that is
> false.  If their machine is internet-connected and compromised, it can
> cause annoyance to third parties.  Given that, I think a file in the
> root of the kernel tree, saying something like, "Don't use me on an
> internet connected machine unless you know what you're doing" would be
> worth considering.

Something vaguely like this might help the issue (with the obvious file
created having the appropriate note in it)

Untested, and I'm sure there are style problems, but the idea should be
obvious:

--- Makefile	2003-10-26 19:04:21.000000000 -0500
+++ Makefile.ryan	2003-11-11 02:45:01.000000000 -0500
@@ -81,7 +81,7 @@
 
 # That's our default target when none is given on the command line
 .PHONY: all
-all:
+all: check-beta
   
 ifneq ($(KBUILD_OUTPUT),)
 # Invoke a second make in the output directory, passing relevant variables
@@ -1027,3 +1027,12 @@
 endif	# skip-makefile
 
 FORCE:
+
+.PHONY: check-beta
+
+check-beta:
+	if [ -f README.Security && ! -f README.Security.IknowwhatImdoing ] ; then \
+		cat README.Security ; \
+		read ; \
+	fi
+


-- 

Ryan Anderson
  sometimes Pug Majere

  reply	other threads:[~2003-11-11  7:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-09 18:41 Some thoughts about stable kernel development Krzysztof Halasa
2003-11-09 19:05 ` Valdis.Kletnieks
2003-11-12 15:05   ` Krzysztof Halasa
2003-11-09 19:06 ` Stefan Smietanowski
2003-11-12 15:07   ` Krzysztof Halasa
2003-11-12 16:04     ` Stefan Smietanowski
2003-11-12 16:51       ` Krzysztof Halasa
2003-11-13  7:33         ` Stefan Smietanowski
2003-11-13 19:55           ` Krzysztof Halasa
2003-11-09 19:26 ` Andrew Morton
2003-11-09 20:34   ` Alan Cox
2003-11-09 20:41   ` Maciej Zenczykowski
2003-11-09 19:29 ` Willy Tarreau
2003-11-12 15:01   ` Krzysztof Halasa
2003-11-09 19:50 ` John Bradford
2003-11-09 23:49   ` Valdis.Kletnieks
2003-11-10  8:53     ` John Bradford
2003-11-09 23:54   ` Rob Landley
2003-11-10  8:50     ` John Bradford
2003-11-11  7:47       ` Ryan Anderson [this message]
2003-11-11  8:19       ` Valdis.Kletnieks
2003-11-11  8:53         ` John Bradford
2003-11-10 10:58 ` Marcelo Tosatti
2003-11-12 14:48   ` Krzysztof Halasa
2003-11-10 13:35 ` jlnance
2003-11-12 14:43   ` Krzysztof Halasa
2003-11-10 16:54 ` Adrian Bunk
2003-11-12 14:40   ` Krzysztof Halasa
  -- strict thread matches above, loose matches on Subject: below --
2003-11-09 21:53 Matt

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=20031111074715.GH22850@michonline.com \
    --to=ryan@michonline.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