From: Herbert Rosmanith <kernel@wildsau.enemy.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pktcdvd major contradicts <linux/Documentation/devices.txt>
Date: Sun, 21 May 2006 00:18:18 +0200 (MET DST) [thread overview]
Message-ID: <200605202218.k4KMIIUX007492@wildsau.enemy.org> (raw)
In-Reply-To: <20060520213506.GC7930@mipter.zuzino.mipt.ru>
> Fixed is in -git since Mon May 15 09:44:40 2006 -0700.
aha. I'm only working with 2.6.16.16.
anyway. As I just started with the pkt-writing module, I noticed
another strange behaviour (at least, it seems strange to me, but YMMV),
and I wonder if this is has already been fixed in some -git or -mm
prepatch or snapshot or subsubsub-release-canditate ...
<linux/Documentation/cdrom/packet-writing.txt> says:
- Setup your writer
# pktsetup dev_name /dev/hdc
Therefore, I do "pktsetup node0 /dev/hdc", which gives:
# pktsetup node0 /dev/hdc
ctl open: Not a directory
strace shows that pktsetup is trying to open /dev/pktcdvd/control,
which it cannot, since /dev/pktcdvd is a char device obviously
created upon "modprobe pktcdvd". The char device has major 10 minor
63, which seems to be missing in devices.txt.
Once I remove the char-device, pktsetup will work and create
/dev/pktcdvd/control and /dev/pktcdvd/node0. Now I try to figure
out how the rest of "packet-writing.txt" works ...
kind regards,
h.rosmanith
prev parent reply other threads:[~2006-05-20 22:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-20 21:17 Herbert Rosmanith
2006-05-20 21:35 ` Alexey Dobriyan
2006-05-20 22:18 ` Herbert Rosmanith [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=200605202218.k4KMIIUX007492@wildsau.enemy.org \
--to=kernel@wildsau.enemy.org \
--cc=adobriyan@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome