From: Pavel Machek <pavel@suse.cz>
To: David Woodhouse <dwmw2@infradead.org>
Cc: adam.keys@HOTARD.engr.smu.edu, linux-kernel@vger.kernel.org
Subject: journaling and devel [was Re: Development Setups]
Date: Sat, 6 Oct 2001 00:27:41 +0000 [thread overview]
Message-ID: <20011006002741.A35@toy.ucw.cz> (raw)
In-Reply-To: <20011005041759.OPDP14306.femail26.sdc1.sfba.home.com@there> <19213.1002268923@redhat.com>
In-Reply-To: <19213.1002268923@redhat.com>; from dwmw2@infradead.org on Fri, Oct 05, 2001 at 09:02:03AM +0100
Hi!
> > I was thinking of starting with a modern machine for developing/
> > compiling on, and then older machine(s) for testing. This way I
> > would not risk losing data if I oops or somesuch.
>
> With journalling filesystems you needn't worry _too_ much about losing
> data; depending of course on what you're hacking on. Having two separate
> boxen for development and testing is mostly valuable because you can keep
> working when you break it - it doesn't take your entire desktop environment
> down with it.
I disagree.. With journal filesystem, when something is silently corrupting
your disk, you'll never know. With ext2, you sometimes sync & reset to make
sure your disks are still healthy. I would not recommend journaling on
experimental boxes.
Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
next prev parent reply other threads:[~2001-10-13 20:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-05 4:20 Development Setups Adam Keys
2001-10-05 4:36 ` Michael Rothwell
2001-10-05 8:02 ` David Woodhouse
2001-10-06 0:27 ` Pavel Machek [this message]
2001-10-13 20:30 ` journaling and devel [was Re: Development Setups] Steve Lord
2001-10-05 9:50 ` Development Setups Riley Williams
2001-10-05 11:22 ` Alan Cox
2001-10-05 14:53 ` Jeff Dike
2001-10-05 17:15 ` Andrew Ebling
2001-10-06 11:38 ` Adrian Cox
2001-10-13 20:38 ` Tim Moore
2001-10-15 9:09 journaling and devel [was Re: Development Setups] Andreas Dilger
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=20011006002741.A35@toy.ucw.cz \
--to=pavel@suse.cz \
--cc=adam.keys@HOTARD.engr.smu.edu \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®