All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suresh Ramasubramanian <mallet@efn.org>
To: linux-india-help@lists.linux-india.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [LIH] Re: PROBLEMS: computer crash due to overfilling ramfs; iso9660 CD not read correctly
Date: Wed, 10 Jan 2001 10:53:52 +0530	[thread overview]
Message-ID: <20010110105352.A24711@oyeindia.com> (raw)
In-Reply-To: <200101100501.VAA23068@pl1.hushmail.com> <3A5BF073.2F075978@psynet.net>
In-Reply-To: <3A5BF073.2F075978@psynet.net>; from devrootp@psynet.net on Wed, Jan 10, 2001 at 10:47:39AM +0530

Archan Paul rearranged electrons thusly:

> I faced the same problem when I patched 2.4.0test7 with reiserFS
> support. On my further correspondence with Alan Cox, he wrote that he is
> unwilling to listen about any "bug report for 2.4kernel", arising after
> patching kernel with some foreign code...
> Any comments? 
 
Simple comment: you misplaced the "quotes".  If you use third party patches
(and reiserfs, though fairly mainstream, _is_ a third party patch), you have to
ask the patch maintainer.  ReiserFS is not (as far as I know) part of the linux
kernel yet.

	--suresh

-- 
Suresh Ramasubramanian  <-->  mallet <at> efn <dot> org
EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2001-01-10  5:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-10  4:57 PROBLEMS: computer crash due to overfilling ramfs; iso9660 CD not read correctly noodlez
2001-01-10  5:17 ` Archan Paul
2001-01-10  5:23   ` Suresh Ramasubramanian [this message]

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=20010110105352.A24711@oyeindia.com \
    --to=mallet@efn.org \
    --cc=linux-india-help@lists.linux-india.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.