From owner-freebsd-current Sun Jun 18 23:54:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 27A8D37BC0C for ; Sun, 18 Jun 2000 23:54:50 -0700 (PDT) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id CAA01304; Mon, 19 Jun 2000 02:53:45 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Mon, 19 Jun 2000 02:53:45 -0400 (EDT) From: "Brandon D. Valentine" To: Bob Bishop Cc: Greg Lehey , FreeBSD current users Subject: Re: -e option to umount? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jun 2000, Bob Bishop wrote: >What's special about mounted devices? I'd prefer to see an eject command >which attempts to unmount the device if it's mounted. What'd be really spiffy is if when I hit the eject button on my CDROM drive that whatever scsi signal that event generates, was intercepted by the kernel and, provided the filesystem met the normal criteria for being umount'd(i.e. nothing accessing it), it would be umount'd and then ejected. I know nothing about what happens when I hit the eject button on a CDROM drive. Anyone care to speculate on if that's a reasonable thing to implement? Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message