From: philipp.muhoray@gmail.com (Philipp Muhoray)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Choosing the right environment
Date: Sat, 01 Nov 2014 15:41:36 +0100 [thread overview]
Message-ID: <5454F120.2050002@gmail.com> (raw)
In-Reply-To: <1414674761.76963.YahooMailNeo@web192804.mail.sg3.yahoo.com>
Hello there,
After reading LDD and LKD, I feel ready to start some actual kernel
hacking. Therefore I wanted to ask you what environment I should use in
the beginning. I have several options, but I'm not sure on which one to
set up my workspace:
- I could develop directly on and against my main machines
(desktop/laptop) ? This is probably not a good idea, since they are used
in ?production? and I don't want to mess things up there
- I could go with a virtual machine on one of my main machines ? But I'm
not quite sure whether the hardware-abstraction will give me troubles
when hacking on hardware drivers (which I want to start with)
- I could also use my Raspberry Pi ? I'm only afraid that the slightly
different environment (SD card instead of hard disk, ARM instead of x86,
limited I/O) could turn out to be a larger obstacle than I thought
- I have some pretty old stand alone desktops which I could use ? But
the hardware is so old (2004ish)
I think my preference is the Raspberry Pi, because I would work on
actual modern hardware without worrying about messing things up. Are
there some drawbacks I'm not considering? Or am I just overthinking
this? What did you use in the beginning?
Best regards,
Philipp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20141101/e0a402b9/attachment.html
next prev parent reply other threads:[~2014-11-01 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 13:12 sched_clock generic for all architectures Hemanth Kumar
2014-11-01 14:41 ` Philipp Muhoray [this message]
2014-11-18 15:03 ` Choosing the right environment Gusman Dharma Putra
2014-11-18 15:24 ` Saket Sinha
2014-11-18 15:36 ` Valdis.Kletnieks at vt.edu
2014-11-18 16:24 ` Philipp Muhoray
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=5454F120.2050002@gmail.com \
--to=philipp.muhoray@gmail.com \
--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).