From: Akshat Aranya <aaranya@cs.sunysb.edu>
To: Siddhartha Jain <sid@netmagicsolutions.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Replicating directories - Intercepting write/modify system calls
Date: Fri, 13 Feb 2004 10:11:32 -0500 [thread overview]
Message-ID: <402CE924.1040609@cs.sunysb.edu> (raw)
In-Reply-To: <AGEEIPMDCDHNNJHJCJEGCEEACAAA.sid@netmagicsolutions.com>
If you're doing kernel development, and fall in the 99.9% category of
people who crash and burn, it would be wise to use VMWare
(www.vmware.com). It saves a lot of trouble. It lets you mess around
with the kernel as much as you want. You can save snapshots of the
state of the virtual machine before you run the new code, and just
revert to the snapshot if you crash. However, the snapshot facility is
really useful only if you're writing kernel modules and not modifying
kernel proper.
-Akshat Aranya
Siddhartha Jain wrote:
> Apart from this, how do I keep my filesystems sane between kernel crashes? I
> mean once I start playing with the kernel (that too with stuff like
> sys_open, sys_write), there will be several crashes.
>
> There has to be a way other than re-installing the OS over and over again.
> Right?
>
> TIA,
>
> Siddhartha
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2004-02-13 15:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 12:39 Replicating directories - Intercepting write/modify system calls Siddhartha Jain
2004-02-12 17:21 ` Joseph D. Wagner
2004-02-13 5:00 ` Siddhartha Jain
2004-02-13 8:11 ` Joseph D. Wagner
2004-02-13 8:59 ` Siddhartha Jain
2004-02-14 13:08 ` Joseph D. Wagner
2004-02-13 14:34 ` Siddhartha Jain
2004-02-13 15:11 ` Akshat Aranya [this message]
2004-02-13 18:40 ` Herbert Poetzl
2004-02-15 8:06 ` Nir Tzachar
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=402CE924.1040609@cs.sunysb.edu \
--to=aaranya@cs.sunysb.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sid@netmagicsolutions.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.