From: Douglas Gilbert <dougg@torque.net>
To: linux-kernel@vger.kernel.org
Cc: Friedrich Lindenberg <frlind@gmx.net>
Subject: Re: AW: ATAPI CDRW which doesn't work -> devfs problems
Date: Sun, 04 Feb 2001 15:19:01 -0500 [thread overview]
Message-ID: <3A7DB935.4170BEBC@torque.net> (raw)
Friedrich Lindenberg wrote:
> I was trying to burn cds under linux-2.4.1 with
> devFS enabled. But x-cd-roast (and also cdrecord)
> do not find any scsi drives. I guess they have been
> renamed or something like that, I cannot find them
> in /dev, nor anywhere in /dev/scsi ...
xcdroast expects to find a whole swag of sg device
filenames (/dev/sg[0-16], /dev/sg[a-q]) and scsi
cdrom names (/dev/sr[0-15]) when it starts. The
xcdroast tarball comes with a MAKEDEVICES.sh script to
create them. If they are not all there it seems to
get upset.
This is not very devfs friendly since its policy
is only to show /dev entries for devices that you
actually have connected and that a driver is
controlling.
So the hack solution is to edit out of MAKEDEVICES.sh
those file names that you actually have then execute
it. IMO this is not a devfs problem, xcdroast needs an
improved device scanning algorithm.
BTW the /dev/sga,b,c style of sg device names are
deprecated in favour of the numeric style.
Doug Gilbert
-
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/
next reply other threads:[~2001-02-04 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-04 20:19 Douglas Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-04 10:16 ATAPI CDRW which doesn't work Joachim 'roh' Steiger
2001-02-04 10:35 ` AW: ATAPI CDRW which doesn't work -> devfs problems Friedrich Lindenberg
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=3A7DB935.4170BEBC@torque.net \
--to=dougg@torque.net \
--cc=frlind@gmx.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