linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yaroslav Rastrigin <yarick@it-territory.ru>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Alistair John Strachan <s0348365@sms.ed.ac.uk>,
	andersen@codepoet.org, linux-kernel@vger.kernel.org
Subject: [OT?] Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
Date: Mon, 9 Jan 2006 17:51:27 +0300	[thread overview]
Message-ID: <200601091751.27405.yarick@it-territory.ru> (raw)
In-Reply-To: <1136814862.9957.5.camel@mindpipe>

Hi, Lee,
On 9 January 2006 16:54, you wrote:
> > 
> 
> Where are the bug reports?  You didn't expect these to just fix
> themselves did you?
Been there, done that. Bugreport about malfunctioning (due to ACPI) 3c556 in IBM ThinkPad T20 was looked at once in a few months without any progress, 
and I've finally lost track of it after changing hardware. In more than a year this problem wasn't solved, so I'm assuming bugreports aren't so effective.
2200BG ping and packet loss problem was reported in ipw2200-devel mailing list recently (by another user), and the only answer was 
"Switch to version 1.0.0" (which is tooo old and missing needed features and bugfixes, so recommentation was unacceptable). So I'm assuming addressing 
developers directly is not too effective either. 
Two other options I see are to debug/fix it by myself and try to stimulate others monetarily. First option isn't really affordable for me , 
so I'm trying to research second. 
-- 
Managing your Territory since the dawn of times ...

  reply	other threads:[~2006-01-09 14:51 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09  7:54 Why the DOS has many ntfs read and write driver,but the linux can't for a long time 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:51           ` Yaroslav Rastrigin [this message]
2006-01-09 15:15             ` [OT?] " Lee Revell
2006-01-09 15:36               ` Randy.Dunlap
2006-01-14  9:55                 ` Pavel Machek
2006-01-09 15:17             ` Pekka Enberg
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=200601091751.27405.yarick@it-territory.ru \
    --to=yarick@it-territory.ru \
    --cc=andersen@codepoet.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    --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;
as well as URLs for NNTP newsgroup(s).