All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: John M Collins <jmc@xisl.com>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
	Lars Marowsky-Bree <lmb@suse.de>,
	Helge Hafting <helge.hafting@aitel.hist.no>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Exploit in 2.6 kernels
Date: Sat, 16 Apr 2005 04:32:06 +0200	[thread overview]
Message-ID: <20050416023206.GH4831@stusta.de> (raw)
In-Reply-To: <1113400906.10763.20.camel@caveman.xisl.com>

On Wed, Apr 13, 2005 at 03:01:46PM +0100, John M Collins wrote:
>...
> Could I possibly make a suggestion for "make xconfig" in the kernel tree
> (and make other-kinds-of-config I suppose)?
> 
> I currently routinely copy the ".config" out of the previous kernel tree
> before I start to save working through questions about sound cards I
> never heard of and so forth.
> 
> Could it perhaps optionally initialise most of the settings to fit the
> current machine and/or grab the last lot of settings
> from /proc/config.gz?


  zcat /proc/config.gz > .config


cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-04-16  2:32 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12  9:34 Exploit in 2.6 kernels John M Collins
2005-04-12 12:24 ` Baruch Even
2005-04-12 15:00   ` John M Collins
2005-04-12 21:08     ` Chris Wright
2005-04-12 21:32       ` John M Collins
2005-04-13  5:28         ` Valdis.Kletnieks
2005-04-13  9:47         ` Helge Hafting
2005-04-13 12:59           ` Lennart Sorensen
2005-04-13 13:06             ` Lars Marowsky-Bree
2005-04-13 13:23               ` Lennart Sorensen
2005-04-13 14:01                 ` John M Collins
2005-04-16  2:32                   ` Adrian Bunk [this message]
2005-04-13 15:22                 ` Chris Friesen
2005-04-14 14:01                   ` Helge Hafting
2005-04-20 18:17                     ` nVidia stuff again Doug Ledford
2005-04-20 23:12                       ` Dave Airlie
2005-04-21 11:23                         ` Helge Hafting
2005-04-21 12:15                         ` Doug Ledford
2005-04-21 12:54                           ` Dave Airlie
2005-04-21 13:35                           ` Lennart Sorensen
2005-04-21 14:43                             ` Manu Abraham
2005-04-21 21:17                               ` J.A. Magallon
2005-04-22 14:44                                 ` Arjan van de Ven
2005-04-15 15:00                 ` Exploit in 2.6 kernels Alan Cox
2005-04-15 16:06                   ` Dave Airlie
2005-04-15 16:19                     ` Duncan Sands
2005-04-14 12:46             ` Helge Hafting
2005-05-05 22:00               ` Olaf Titz
2005-04-13 13:02         ` Lennart Sorensen
2005-04-13 14:26           ` Eric Rannaud
2005-04-13 14:41             ` Lennart Sorensen
2005-04-14 20:02               ` Greg Folkert
2005-04-14 22:27                 ` John M Collins
2005-05-09 18:37     ` Alessandro Salvatori

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=20050416023206.GH4831@stusta.de \
    --to=bunk@stusta.de \
    --cc=helge.hafting@aitel.hist.no \
    --cc=jmc@xisl.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lmb@suse.de \
    --cc=lsorense@csclub.uwaterloo.ca \
    /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.