From: Jim Crilly <jim@why.dont.jablowme.net>
To: Marc Koschewski <marc@osknowledge.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [QUESTION] Your way doing kernel/module development
Date: Sat, 11 Feb 2006 16:33:59 -0500 [thread overview]
Message-ID: <20060211213359.GD3088@mail> (raw)
In-Reply-To: <20060211154206.GD5721@stiffy.osknowledge.org>
On 02/11/06 04:42:06PM +0100, Marc Koschewski wrote:
> I'd like to get some short but, however, fully descriptive statements about how
> you do your module development. I mean, what your way of doing coding,
> insmod-ing, rmmod-ing, ... And what about code, that cannot be <M>, just [*] or
> must-be-built-in.
>
> Hm, actually there's nothing more to say. Except that I'm tired of rebooting. ;)
> I tried kexec() but somehow I dont have all IDE devices sometimes on 'kexec -e'.
> So this just not a solution for me... :)
>
> Marc
Depending on what part of the kernel you're working on you could look
at using a VM to test in, as long as you don't need direct access to
a specific piece of hardware in your machine you should be able to use
qemu, UML, VMWare, etc to boot your new kernel.
Jim.
prev parent reply other threads:[~2006-02-11 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 15:42 [QUESTION] Your way doing kernel/module development Marc Koschewski
2006-02-11 21:33 ` Jim Crilly [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=20060211213359.GD3088@mail \
--to=jim@why.dont.jablowme.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@osknowledge.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