All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Starr <spstarr@sh0n.net>
To: Dan Chen <crimsun@email.unc.edu>
Cc: Linux <linux-kernel@vger.kernel.org>
Subject: Re: [PROBLEM]: 2.4.18-rc1 - Unable to mount CD-ROM/RW
Date: 21 Feb 2002 15:29:51 -0500	[thread overview]
Message-ID: <1014323419.8811.34.camel@unaropia> (raw)
In-Reply-To: <20020221195724.GA11435@opeth.ath.cx>
In-Reply-To: <LI5YSPXWYTY04431V32LFIF97042TP.3c7534b4@jss> <1014316330.8812.27.camel@unaropia>  <20020221195724.GA11435@opeth.ath.cx>

Interesting, I will find out when i push out -shawn7 tonght (Quota
problems will remain still).

Shawn.

On Thu, 2002-02-21 at 14:57, Dan Chen wrote:
> On Thu, Feb 21, 2002 at 01:31:42PM -0500, Shawn Starr wrote:
> > It's an LFS distribution i built. The problem is 2.4.17 didn't have this
> > problem. Something introduced into 2.4.18-pre/rc.
> 
> Hmm, when I spoke with you this morning on #kn I forgot to mention I'm
> using rc2-ac1, which as someone else mentioned, doesn't exhibit the
> symptoms you describe. Were the sg changes/updates ever applied to 2.4
> mainline? I know they went into Alan's tree in .12 or .13 ...
> 
> -- 
> Dan Chen                 crimsun@email.unc.edu
> GPG key:   www.unc.edu/~crimsun/pubkey.gpg.asc



  reply	other threads:[~2002-02-21 20:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <LI5YSPXWYTY04431V32LFIF97042TP.3c7534b4@jss>
2002-02-21 18:31 ` [PROBLEM]: 2.4.18-rc1 - Unable to mount CD-ROM/RW Shawn Starr
2002-02-21 19:57   ` Dan Chen
2002-02-21 20:29     ` Shawn Starr [this message]
2002-02-21 19:19 Brenneke, Matthew Jeffrey (UMR-Student)
  -- strict thread matches above, loose matches on Subject: below --
2002-02-21 17:40 Shawn Starr
2002-02-21 19:09 ` Matt Reppert

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=1014323419.8811.34.camel@unaropia \
    --to=spstarr@sh0n.net \
    --cc=crimsun@email.unc.edu \
    --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.