From: Russell King <rmk@arm.linux.org.uk>
To: Mark Shewmaker <mark@primefactor.com>
Cc: Brian Dushaw <dushaw@munk.apl.washington.edu>,
linux-kernel@vger.kernel.org
Subject: Re: Linux kernel - and regular sync'ing?
Date: Tue, 13 Mar 2001 19:43:08 +0000 [thread overview]
Message-ID: <20010313194308.A2536@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20010308223319.A25679@flint.arm.linux.org.uk> <Pine.LNX.4.30.0103081439400.18253-100000@munk.apl.washington.edu> <20010312142702.A28863@primefactor.com>
In-Reply-To: <20010312142702.A28863@primefactor.com>; from mark@primefactor.com on Mon, Mar 12, 2001 at 02:27:02PM -0500
On Mon, Mar 12, 2001 at 02:27:02PM -0500, Mark Shewmaker wrote:
> It's probably very much worth it for you to keep your /etc/fstab as you've
> edited it, but I did want to warn you that the noatime option can
> still unexpectedly break programs that make quite reasonable assumptions.
Easy workaround - place your /home and /var trees on separate filesystems
and mount /home normally. Make /var "nodiratime" so accessing directories
doesn't update their atime. Make / "noatime".
This is basically what I've been running here for the past couple of years
and it seems fine for me. Your milage may vary though (depending on what
software you run).
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-03-13 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-08 4:21 Linux kernel - and regular sync'ing? Brian Dushaw
2001-03-08 12:09 ` Alan Cox
2001-03-08 22:33 ` Russell King
2001-03-08 22:50 ` Brian Dushaw
2001-03-12 19:27 ` Mark Shewmaker
2001-03-13 19:43 ` Russell King [this message]
2001-03-09 11:46 ` Pavel Machek
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=20010313194308.A2536@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=dushaw@munk.apl.washington.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@primefactor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox