From: "Brian O'Mahoney" <omb@khandalf.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org
Subject: how to be (SAFE) a kernel developer ?
Date: Tue, 19 Jul 2005 23:53:08 +0200 [thread overview]
Message-ID: <42DD7644.5040304@khandalf.com> (raw)
In-Reply-To: <9a87484905071818116f7cb0de@mail.gmail.com>
Jesper Juhl wrote: ...
much useful advice, almost all of which I agree with _BUT_
please do NOT debug kernel mods on your 'main-box', where your
filesystems live. unless you like to live dangerously and make
perfect backups you don't mind spending lots of hours restoring,
unless you want to specialise in file systems, but maybe do
want to work on device drivers use a ---
sacrifical system, and, for example NFS mount everything, on
it from your main box, otherwise use a cheap local disk just
for your fs stuff
then when you blow it there is no FS damage and you don't need
to wait for FSCK, or Journal Replay, when your fs works you
can live more dangerously ;-)
You will also need a main system, and serial X-over cable,
if you want to use some of the increasing number of tools,
kdb, kgdb, kprobes .... that assume a 2 box setup
Finally, Linus personally dislikes debuggers, ... 'read the source
Luke' so patches to the mm or mainstream should be grounded an
source code analysis, not it works or xxx has 0x1234 in it.
--
mit freundlichen Grüßen, Brian.
next prev parent reply other threads:[~2005-07-19 21:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 14:35 how to be a kernel developer ? regatta
2005-07-18 14:43 ` Alejandro Bonilla
2005-07-18 16:22 ` Andrew Ruder
2005-07-19 1:11 ` Jesper Juhl
2005-07-19 1:24 ` Jesper Juhl
2005-07-19 21:53 ` Brian O'Mahoney [this message]
2005-07-19 23:02 ` how to be (SAFE) " Jan Blunck
2005-07-20 0:25 ` Jesper Juhl
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=42DD7644.5040304@khandalf.com \
--to=omb@khandalf.com \
--cc=linux-kernel@vger.kernel.org \
--cc=omb@bluewin.ch \
/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