From: Jan Blunck <jblunck@gmail.com>
To: omb@bluewin.ch
Cc: linux-kernel@vger.kernel.org
Subject: Re: how to be (SAFE) a kernel developer ?
Date: Wed, 20 Jul 2005 01:02:57 +0200 [thread overview]
Message-ID: <4de7f8a605071916022f019cd0@mail.gmail.com> (raw)
In-Reply-To: <42DD7644.5040304@khandalf.com>
On 7/19/05, Brian O'Mahoney <omb@khandalf.com> wrote:
>
> 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 ;-)
>
Or try qemu/bochs for your laptop, Xen for your desktop and z/VM for
your mainframe ;)
Jan
next prev parent reply other threads:[~2005-07-19 23:03 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 ` how to be (SAFE) " Brian O'Mahoney
2005-07-19 23:02 ` Jan Blunck [this message]
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=4de7f8a605071916022f019cd0@mail.gmail.com \
--to=jblunck@gmail.com \
--cc=j.blunck@tu-harburg.de \
--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