public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: Bernd Petrovitsch <bernd@firmix.at>,
	Oliver Neukum <oliver@neukum.org>,
	Robert Hancock <hancockr@shaw.ca>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
Date: Mon, 09 Jan 2006 23:30:18 -0500	[thread overview]
Message-ID: <1136867419.2007.56.camel@mindpipe> (raw)
In-Reply-To: <200601100145.00044.s0348365@sms.ed.ac.uk>

On Tue, 2006-01-10 at 01:44 +0000, Alistair John Strachan wrote:
> Sounds like a broken configuration to me. Of course the usual array of
> hardware specs, configuration, filesystem, free RAM, etc. all play
> into this, but no KDE application, including the originally cited
> Kate, takes longer than 1s to start on this machine (1.6GHz P-M, 2MB
> L2, 400MHz FSB, 1GB PC2700).
> 
> Hell kfm is probably a hell of a lot more bloated than Nautilus and
> it's pretty fast to start first time (1-2s), and cached it's pretty
> much instantaneous (I'd say less than 400ms). Fast enough, no?
> 

I don't think it's a broken configuration, just a slow machine (600MHz
VIA C3).  Windows XP screams compared to Linux on this thing.

Lee


  reply	other threads:[~2006-01-10  4:30 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5t06S-7nB-15@gated-at.bofh.it>
     [not found] ` <5t34G-3Zu-21@gated-at.bofh.it>
     [not found]   ` <5t5pU-7tD-37@gated-at.bofh.it>
     [not found]     ` <5t5JU-7Sn-11@gated-at.bofh.it>
2006-01-09 14:18       ` Why the DOS has many ntfs read and write driver,but the linux can't for a long time Robert Hancock
2006-01-09 14:28         ` Oliver Neukum
2006-01-09 15:15           ` Lee Revell
2006-01-09 16:02             ` Oliver Neukum
2006-01-09 16:04               ` Lee Revell
2006-01-09 16:14                 ` Oliver Neukum
2006-01-09 16:19                   ` Lee Revell
2006-01-09 16:29                     ` Bernd Petrovitsch
2006-01-09 16:41                       ` Lee Revell
2006-01-09 16:53                         ` Oliver Neukum
2006-01-09 16:56                           ` Lee Revell
2006-01-09 17:14                           ` Olivier Galibert
2006-01-09 17:28                             ` Lee Revell
2006-01-09 19:35                               ` Anton Altaparmakov
2006-01-10 10:32                             ` File type by extension is evil (was Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time) Bernhard R. Link
2006-01-10 20:28                               ` Lee Revell
2006-01-09 17:14                           ` Why the DOS has many ntfs read and write driver,but the linux can't for a long time Bernd Petrovitsch
2006-01-09 17:31                           ` Alan Cox
2006-01-09 16:45                             ` Jeff V. Merkey
2006-01-09 17:33                             ` Lee Revell
2006-01-09 18:11                               ` Marcin Dalecki
2006-01-09 17:45                             ` Oliver Neukum
2006-01-09 16:59                         ` Bernd Petrovitsch
2006-01-10  1:44                         ` Alistair John Strachan
2006-01-10  4:30                           ` Lee Revell [this message]
2006-01-10 10:13                             ` Jakob Oestergaard
2006-01-10 10:34                               ` Jesper Juhl
2006-01-10 23:48 Lukas Hejtmanek
2006-01-10 23:57 ` Lee Revell
2006-01-11  0:02   ` Lukas Hejtmanek
  -- strict thread matches above, loose matches on Subject: below --
2006-01-09  7:54 Boxer Gnome
2006-01-09  8:06 ` Erik Andersen
2006-01-09  8:21   ` Boxer Gnome
2006-01-09  8:53     ` Jim Crilly
2006-01-09  9:07   ` Yaroslav Rastrigin
2006-01-09 10:22     ` Alistair John Strachan
2006-01-09 11:03       ` Yaroslav Rastrigin
2006-01-09 12:45         ` CaT
2006-01-09 13:34           ` Yaroslav Rastrigin
2006-01-10 13:29             ` Helge Hafting
2006-01-10 16:29               ` Randy.Dunlap
2006-01-11  2:29             ` David Nicol
2006-01-11  2:56               ` Lee Revell
2006-01-12 18:53                 ` David Nicol
2006-01-12 21:05                   ` Lee Revell
2006-01-09 13:36         ` Kasper Sandberg
2006-01-09 13:56           ` Yaroslav Rastrigin
2006-01-09 16:07             ` Alan Cox
2006-01-09 16:15               ` Lee Revell
2006-01-09 16:34                 ` Alan Cox
2006-01-09 16:34                 ` Olivier Galibert
2006-01-09 19:24               ` Diego Calleja
2006-01-09 19:33                 ` Lee Revell
2006-01-09 13:54         ` Lee Revell
2006-01-09 14:32         ` Bernd Petrovitsch
2006-01-09 15:22         ` Denis Vlasenko
2006-01-09 19:07         ` Diego Calleja
2006-01-09 22:49         ` Dave Airlie
2006-01-10 12:00         ` Pavel Machek
2006-01-09 13:56     ` Lee Revell
2006-01-10  7:13     ` Andrew Morton
2006-01-10  7:33       ` Denis Vlasenko
2006-01-10  8:33         ` D. Hazelton
2006-01-10 10:49           ` Diego Calleja
2006-01-10 13:26           ` Denis Vlasenko
2006-01-11  4:57             ` D. Hazelton
2006-01-10  9:32         ` Yaroslav Rastrigin
2006-01-10  9:20       ` Yaroslav Rastrigin
2006-01-10 10:50         ` Diego Calleja
2006-01-09 16:32 ` Bernd Petrovitsch

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=1136867419.2007.56.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=bernd@firmix.at \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=s0348365@sms.ed.ac.uk \
    /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