From: j.neuschaefer@gmx.net (Jonathan Neuschäfer)
To: kernelnewbies@lists.kernelnewbies.org
Subject: what's best way for playing with kernel configurations and source code
Date: Mon, 27 May 2013 16:21:57 +0200 [thread overview]
Message-ID: <20130527142157.GA3197@debian.debian> (raw)
In-Reply-To: <CAMSEaH55+--5sa_8OzbPwvz4UdvE41ee+5cHSa+Uu6JruofiDQ@mail.gmail.com>
On Mon, May 27, 2013 at 12:01:20AM +0530, Sankar P wrote:
> On Sun, May 26, 2013 at 9:13 PM, Alshamlan, Mohammad <malsh002@fiu.edu> wrote:
> > Hi everybody,
> >
> > How you can reconfigure and also modify your source code without affected
> > your system? Please, if you want to suggest a virtual machine is the best
> > option, then could you tell me why? Thanks in advance.
> >
>
> Usually while kernel development, you do not overwrite your existing
> distro-provided kernel, but install your built kernel as a new option.
> This helps you in not losing access to your machine in case the kernel
> changes you have made are serious.
If they're serious enough you might still break your file system and
lose your data, so it's in any case good to have a backup. ;-)
--
Thanks,
Jonathan Neusch?fer
prev parent reply other threads:[~2013-05-27 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-26 15:43 what's best way for playing with kernel configurations and source code Alshamlan, Mohammad
2013-05-26 18:31 ` Sankar P
2013-05-27 14:21 ` Jonathan Neuschäfer [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=20130527142157.GA3197@debian.debian \
--to=j.neuschaefer@gmx.net \
--cc=kernelnewbies@lists.kernelnewbies.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).