From: Gary Lawrence Murphy <garym@canada.com>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Cc: garym@teledyn.com
Subject: Kernel compiled from source won't read /parts/ of a CD?
Date: 01 Aug 2002 15:48:49 -0400 [thread overview]
Message-ID: <m24reetl5q.fsf@maya.dyndns.org> (raw)
This is one of the strangest situations I have ever seen: my
re-compiled Linux 2.4.18 kernel now /refuses/ to read /only/ the
"/Mandrake" directory branch of all three of the Mandrake distribution
CDs. It /has/ to be some kernel option, but I can't figure which one;
any advice or debugging hints at all are greatly appreciated.
I had to recompile a Mandrake 8.2 kernel to remove pcmcia support (so
I could use the sf release of it) Using the stock Mandrake 8.2 binary
kernel, the CDs can be read just fine, it is only the kernel that I
compiled from the linux-2.4.18-6mdk.src package that has this trouble.
There are no warning messages, only one line returned to the console
to say "ls /Mandrake: Invalid argument" and one line in syslog to say
"ISO 9660: RRIP_1991A" and that's the total diagnostic information I
have.
Using /usr/bin/isoinfo, I can list the CD contents just fine; all the
unix tools (ls, cd, cp ...) and rpm cannot read /Mandrake.
What could I have possibly omitted from the kernel config to cause
this? How could that one directory be singled out by a simple kernel
config problem? (or could it be a gcc 2.96 problem?)
--
Gary Lawrence Murphy <garym@teledyn.com> TeleDynamics Communications Inc
Business Innovations Through Open Source Systems: http://www.teledyn.com
"Computers are useless. They can only give you answers."(Pablo Picasso)
next reply other threads:[~2002-08-01 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 19:48 Gary Lawrence Murphy [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-01 19:40 Kernel compiled from source won't read /parts/ of a CD? Gary Lawrence Murphy
2002-08-01 19:58 ` Richard B. Johnson
2002-08-02 20:36 ` Gary Lawrence Murphy
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=m24reetl5q.fsf@maya.dyndns.org \
--to=garym@canada.com \
--cc=garym@teledyn.com \
--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.