From mboxrd@z Thu Jan 1 00:00:00 1970 From: Akshat Aranya Subject: Re: Replicating directories - Intercepting write/modify system calls Date: Fri, 13 Feb 2004 10:11:32 -0500 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <402CE924.1040609@cs.sunysb.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org Return-path: Received: from mail.ic.sunysb.edu ([129.49.1.4]:44014 "EHLO mail.ic.sunysb.edu") by vger.kernel.org with ESMTP id S267034AbUBMPN6 (ORCPT ); Fri, 13 Feb 2004 10:13:58 -0500 To: Siddhartha Jain In-Reply-To: List-Id: linux-fsdevel.vger.kernel.org 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 > >