public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@gnu.org>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux <util-linux@vger.kernel.org>,
	David Zeuthen <davidz@redhat.com>,
	Michal Luscon <mluscon@redhat.com>
Subject: Re: eject merged into util-linux
Date: Thu, 05 Apr 2012 17:00:07 +0200	[thread overview]
Message-ID: <1333638007.2628.1.camel@offbook> (raw)
In-Reply-To: <20120405143032.GC20515@x2.net.home>

On Thu, 2012-04-05 at 16:30 +0200, Karel Zak wrote:
> The original eject project (at sourceforge.net) is inactive for more
>  than 4 year. Unfortunately, the command is still used in mainstream
>  Linux distributions (for example udisks depends on the eject
>  functionality). 

Great news! This was one of my favorite tools when I first began using
Linux, nice to have it in u-l now.

> Changes:
> 
>   * complete refactoring (the original code was real mess...)
> 
>   * merged patches from Fedora (auto-eject, manual-eject, close-tray
>     list-speed and removable/hotpluggable-check patches)
> 
>   * removed support for incomplete paths (for example "eject foo" was
>     interpreted as "eject /media/foo" or "eject /mnt/foo". The
>     incomplete paths are supported for devices only (e.g. "eject sda").
> 
>     FOR MOUNTPOINT YOU HAVE TO SPECIFY COMPLETE PATH!
> 
>   * enabled by default (and added --disable-eject)
> 
>   * if a partition is specified, whole-disk device is used for eject
>     ioctl(s), for example "eject /dev/sda1" is the same as "eject /dev/sda"
> 
> 
>  Thanks to Michal Luscon for help.
> 
>     Karel
> 

      reply	other threads:[~2012-04-05 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05 14:30 eject merged into util-linux Karel Zak
2012-04-05 15:00 ` Davidlohr Bueso [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=1333638007.2628.1.camel@offbook \
    --to=dave@gnu.org \
    --cc=davidz@redhat.com \
    --cc=kzak@redhat.com \
    --cc=mluscon@redhat.com \
    --cc=util-linux@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