From: David Weinehall <tao@acc.umu.se>
To: cacook@freedom.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: write to dvd ram
Date: Tue, 22 May 2001 19:38:41 +0200 [thread overview]
Message-ID: <20010522193840.F12860@khan.acc.umu.se> (raw)
In-Reply-To: <20010522164700Z262628-933+213@vger.kernel.org>
In-Reply-To: <20010522164700Z262628-933+213@vger.kernel.org>; from cacook@freedom.net on Tue, May 22, 2001 at 10:38:49AM -0600
On Tue, May 22, 2001 at 10:38:49AM -0600, cacook@freedom.net wrote:
> OK, I've asked this question four weeks in a row and received no response
> whatsoever. Linux is supposed to be the OS where you can turn to the
> newsgroups/IRC and get able help.
>
> This is to those who couldn't lift a finger to help with this compile/driver
> problem:
Ignoring your obvious attitude problem for now (you haven't ever
considered the fact that (almost) all the people on this list develop
Linux voluntarily, in their spare-time?!), I suggest you try
at #kernelnewbies on irc if you want response. Or you could try to
download a newer version of the kernel. You know, the bug might've been
fixed since v2.4.2...
/David Weinehall
_ _
// David Weinehall <tao@acc.umu.se> /> Northern lights wander \\
// Project MCA Linux hacker // Dance across the winter sky //
\> http://www.acc.umu.se/~tao/ </ Full colour fire </
next prev parent reply other threads:[~2001-05-22 17:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 16:38 write to dvd ram cacook
2001-05-22 17:38 ` David Weinehall [this message]
2001-05-22 23:18 ` Rafael Herrera
2001-05-23 9:34 ` Helge Hafting
-- strict thread matches above, loose matches on Subject: below --
2001-05-22 16:38 quantum7
2001-05-15 16:32 cacook
[not found] <91FD33983070D21188A10008C728176C09421202@LDMS6003>
2001-05-08 14:53 ` cacook
2001-05-08 17:01 ` Ben Fennema
2001-05-08 17:50 ` Jens Axboe
2001-05-08 18:11 ` cacook
2001-05-08 18:59 ` Thiago Vinhas de Moraes
2001-05-08 19:10 ` Jens Axboe
2001-05-11 13:57 ` cacook
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=20010522193840.F12860@khan.acc.umu.se \
--to=tao@acc.umu.se \
--cc=cacook@freedom.net \
--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