mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Klink <colonel@clouddancer.com>
To: WebMonster@idsa.ch
Cc: linux-kernel@vger.kernel.org
Subject: Re: .config question
Date: Thu,  3 Jun 2004 11:19:56 -0700 (PDT)	[thread overview]
Message-ID: <20040603181956.A4B3A229E08@phoenix.clouddancer.com> (raw)
In-Reply-To: <s0bf4d74.020@idfw.idsa.ch> (WebMonster@idsa.ch)


   Date:	Thu, 03 Jun 2004 16:10:09 +0200
   From: "Francois Pernet" <WebMonster@idsa.ch>

   Hi,
   Sorry to not be part of the mailing list and ask question. Please,
   could you post any answer (CC) to this question, if relevant ? Many
   TIA.

Probably show up on the list, otherwise likely to be a silent fix RSN.
I was surprised that it hadn't been posted, spent time making sure
that I could repeat it....but it could still be something in my setup.


   I've got a kernel already installed in my machine (SuSe Pro 9). I would
   like to modify something and recompile the kernel. Since it has been
   installed from rpm, there is no .config in /usr/src/linux. Is there any
   way to create this file from the image and modules, so i do not need to
   verify all my config prior to change something ?

There is an option in 2.6 to determine the .config that built the
kernel somehow.  I've just noticed it while reading 'make xconfig',
but never use it (I don't lose track of my .config files, been doing
that tooo long).  Try reading the source for how this is supposed to
work.  You might look around a bit, such as in /boot, as many distros
include the config someplace.


      parent reply	other threads:[~2004-06-03 18:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03 14:10 Francois Pernet
2004-06-03 14:37 ` Wolfgang Fritz
2004-06-03 14:42 ` Fabian Fenaut
2004-06-03 15:13 ` Daniel Andersen
2004-06-03 18:19 ` Klink [this message]

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=20040603181956.A4B3A229E08@phoenix.clouddancer.com \
    --to=colonel@clouddancer.com \
    --cc=WebMonster@idsa.ch \
    --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

all inboxes | Powered by JetHome®