From: jw schultz <jw@pegasys.ws>
To: linux-kernel@vger.kernel.org
Subject: Re: syslog full of kernel BUGS, frequent intermittent instability
Date: Sat, 1 Mar 2003 18:36:50 -0800 [thread overview]
Message-ID: <20030302023649.GA30797@pegasys.ws> (raw)
In-Reply-To: <20030301150350.GA27794@lug-owl.de>
On Sat, Mar 01, 2003 at 04:03:50PM +0100, Jan-Benedict Glaw wrote:
> On Sat, 2003-03-01 14:55:58 +0000, John Bradford <john@grabjohn.com>
> wrote in message <200303011455.h21EtwhU000402@81-2-122-30.bradfords.org.uk>:
> > > It's the mandrake default AFAIK. I don't know what all that stuff is,
> > > so I don't mess with it. My installation does "feel" bloated (very
> > > unscientific opinion): it "feels" much less responsive in the GUI
> >
> > /dev/hda2 / ext3 defaults 1 1
> >
> > which you can change to
> >
> > /dev/hda2 / ext3 defaults, noatime 1 1
> you loose -----^
>
> > This is a bit off-topic, but in my experience is about the best way to
> > increase performance on old, (and not so old), hardware, apart from
> > compiling a custom kernel. Without noatime, every time you read a
> > file, the current date and time is written to the disk. With noatime,
> > it's only recorded for a write. Almost no programs use the access
> > time data.
>
> Except some email clients...
And as you and i already hashed out on the rsync list mutt is
perfectly happy and fully functional with noatime,nodiratime
because it updates the atime manually which still works.
As the headers indicate i'm using mutt, It spots new mail
in other mboxes just fine with noatime turned on. I get the
"Inc:" count, c<tab> works, and folder lists indicate
correctly which folders have been updated since last visit.
Perhaps you are thinking of another MUA or an oooold version
of mutt?
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw@pegasys.ws
Remember Cernan and Schmitt
next prev parent reply other threads:[~2003-03-02 2:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 9:12 wyleus
2003-02-26 9:44 ` John Bradford
2003-02-26 11:48 ` Denis Vlasenko
2003-02-27 13:23 ` wyleus
2003-02-28 6:41 ` Denis Vlasenko
2003-02-28 13:47 ` Robert Redelmeier
2003-02-28 14:13 ` John Bradford
2003-03-01 13:21 ` wyleus
2003-03-01 14:55 ` John Bradford
2003-03-01 15:03 ` Jan-Benedict Glaw
2003-03-02 2:36 ` jw schultz [this message]
2003-03-01 15:33 ` redelm
2003-03-01 20:55 ` wyleus
2003-03-02 11:14 ` wyleus
2003-03-03 15:10 ` Denis Vlasenko
[not found] <200302262224.h1QMOem0000411@81-2-122-30.bradfords.org.uk>
2003-02-27 0:24 ` wyleus
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=20030302023649.GA30797@pegasys.ws \
--to=jw@pegasys.ws \
--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®