public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Christoph Hellwig <hch@infradead.org>,
	Samphan Raruenrom <samphan@nectec.or.th>,
	Jens Axboe <axboe@image.dk>,
	linux-kernel@vger.kernel.org, Linux TLE Team <rdi1@opentle.org>,
	Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: [PATCH] Add MOUNT_STATUS ioctl to cdrom device
Date: Tue, 26 Aug 2003 11:58:30 +0200	[thread overview]
Message-ID: <20030826095830.GA20693@suse.de> (raw)
In-Reply-To: <20030826105613.A23356@infradead.org>

On Tue, Aug 26 2003, Christoph Hellwig wrote:
> On Tue, Aug 26, 2003 at 04:09:54PM +0700, Samphan Raruenrom wrote:
> > The only visible feature of this new magicdev is that now
> > GNOME users can eject there CDs (the discs' icon will
> > disappear). The eject button now act as 'umount' command.
> > 
> > One new requirement from this new magicdev is the question
> > "will umount failed?". I have no preference on any way to
> > implement it. Should there be the right way to do it, I'll
> > do so. I can think of many way to implement it (including
> > adding a new lazy-lock mode to cdrom device) but since
> > I have no kernel hacking experience, I need everyone
> > advices. Novice users need this 'eject' button after all.
> 
> This doesn't make sense at all.  Just try the unmount and
> tell the user if it failed - you can't say whether it will
> fail before trying.

Exactly. You poll media events from the drive, and upon an eject request
you try and umount it. If it suceeds, you eject the tray. It's pretty
simple, really.

This mount status patch is seriously broken and misguided.

-- 
Jens Axboe


  reply	other threads:[~2003-08-26  9:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-25 18:22 [PATCH] Add MOUNT_STATUS ioctl to cdrom device Samphan Raruenrom
2003-08-25 18:50 ` Christoph Hellwig
2003-08-26  6:50   ` Samphan Raruenrom
2003-08-26  7:32     ` Christoph Hellwig
2003-08-26  9:09       ` Samphan Raruenrom
2003-08-26  9:56         ` Christoph Hellwig
2003-08-26  9:58           ` Jens Axboe [this message]
2003-08-26 11:30             ` [Rdi1] " Samphan Raruenrom
2003-08-26 11:36               ` Jens Axboe
2003-08-26 12:44                 ` Samphan Raruenrom
2003-08-26 14:16                   ` Jens Axboe
2003-08-26 13:58               ` Christoph Hellwig
2003-08-26 15:32                 ` Samphan Raruenrom
2003-08-26 15:45                   ` Jens Axboe
2003-08-25 20:03 ` viro

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=20030826095830.GA20693@suse.de \
    --to=axboe@suse.de \
    --cc=axboe@image.dk \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=rdi1@opentle.org \
    --cc=samphan@nectec.or.th \
    /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