From: jordan.breeding@attbi.com
To: linux-kernel@vger.kernel.org
Cc: torvalds@transmeta.com
Subject: [PATCH] fix /dev/cdroms on 2.5.38-bk current
Date: Wed, 25 Sep 2002 06:02:04 +0000 [thread overview]
Message-ID: <20020925060206.FGZU16629.rwcrmhc51.attbi.com@rwcrwbc58> (raw)
[-- Attachment #1: Type: text/plain, Size: 197 bytes --]
Hello,
Currently 2.5.38-bk ends up creating all devfs based
cdrom entries in /dev/cdroms/cdroms, this should actually
only be /dev/cdroms. This patch fixes it for me at least.
Jordan Breeding
[-- Attachment #2: patch-cdrom-fix-2.5.38-1 --]
[-- Type: application/octet-stream, Size: 429 bytes --]
--- linux-2.5.38/fs/partitions/check.c 2002-09-23 21:55:43.000000000 -0500
+++ linux-2.5.38-bk/fs/partitions/check.c 2002-09-24 22:53:00.000000000 -0500
@@ -348,7 +348,7 @@
cdroms = devfs_mk_dir (NULL, "cdroms", NULL);
dev->number = devfs_alloc_unique_number(&cdrom_numspace);
- sprintf(vname, "cdroms/cdrom%d", dev->number);
+ sprintf(vname, "cdrom%d", dev->number);
if (dev->de) {
int pos;
devfs_handle_t slave;
reply other threads:[~2002-09-25 5:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020925060206.FGZU16629.rwcrmhc51.attbi.com@rwcrwbc58 \
--to=jordan.breeding@attbi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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).