All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Peter Osterlund <petero2@telia.com>
Cc: Phillip Susi <psusi@cfl.rr.com>, Damian Pietras <daper@daper.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Problems with eject and pktcdvd
Date: Sun, 15 Jan 2006 22:55:22 +0000	[thread overview]
Message-ID: <87wth19k4l.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <m3ek39z09f.fsf@telia.com> (Peter Osterlund's message of "15 Jan 2006 20:48:38 -0000")

On 15 Jan 2006, Peter Osterlund murmured:
> If you do
> 
> 	pktsetup 0 /dev/hdc
> 	mount /dev/hdc /mnt/tmp
> 	umount /mnt/tmp

> the door will be left in a locked state.

This is indeed what I see.

> 	pktsetup 0 /dev/hdc
> 	mount /dev/pktcdvd/0 /mnt/tmp
> 	umount /mnt/tmp
> 
> the door will be properly unlocked.

... and this.

... and my assumption that I couldn't mount non-packetwritten CDs via
the /dev/pktcdvd/0 device is entirely erroneous. So it all works after
all, as long as I never use the non-packetwritten device.

Oh *good*. Thank you for this: this was my last real thing that worked
better in 2.4 than in 2.6 :)))

> The problem is that the cdrom driver locks the door the first time the
> device is opened in blocking mode, but doesn't unlock it again until
> the open count goes down to zero. The pktcdvd driver tries to work
> around that, but it can't do it in the first example because the
> mount/umount commands do not involve the pktcdvd driver at all.

Yeah, well, it's obvious once you've explained it ;)

-- 
`Logic and human nature don't seem to mix very well,
 unfortunately.' --- Velvet Wood

      parent reply	other threads:[~2006-01-15 22:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-15 12:35 Problems with eject and pktcdvd Damian Pietras
2006-01-15 17:53 ` Phillip Susi
2006-01-15 18:50   ` Damian Pietras
2006-01-15 19:17     ` Phillip Susi
2006-01-15 20:47       ` Peter Osterlund
2006-01-15 21:04         ` Damian Pietras
2006-01-15 21:18           ` Jan Engelhardt
2006-01-15 21:34             ` Peter Osterlund
2006-02-05 19:13           ` Peter Osterlund
2006-02-05 21:07             ` Damian Pietras
2006-02-05 22:44               ` Peter Osterlund
2006-02-06 20:15                 ` Damian Pietras
2006-02-11 11:21                   ` Peter Osterlund
2006-02-12 10:34                     ` Damian Pietras
2006-01-15 22:23         ` Phillip Susi
2006-01-15 22:55         ` Nix [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=87wth19k4l.fsf@amaterasu.srvr.nix \
    --to=nix@esperi.org.uk \
    --cc=daper@daper.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petero2@telia.com \
    --cc=psusi@cfl.rr.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 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.