Bug 100058 - Arch testing request for sys-block/unieject
|
Bug#:
100058
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: enhancement
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: flameeyes@gentoo.org
|
Reported By: flameeyes@gentoo.org
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: Arch testing request for sys-block/unieject
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2005-07-23 12:42 0000
|
I've added my unieject-2 to portage, a drop-in replacement for sys-apps/eject
using dev-libs/libcdio.
I can just try it on AMD64/Linux and x86/FreeBSD it's just marked ~amd64; if
arches can test and mark it (or report failures) that can be an alterantive to
eject command.
Thanks in advance,
Diego
Marked ~x86.
Problems found:
-n returns nothing
umounting does not work, even with -f
eject provides a volname binary, unieject does not.
(In reply to comment #2)
> -n returns nothing
This would report problems with unmounting/looking of devices. It's best
suited with -v.
> umounting does not work, even with -f
To use unmount features you must use eject by root, I still have to figure out
how to use libcap to make use of capabilities.
> eject provides a volname binary, unieject does not.
I know, and I'm planning something like this: as volname isn't exactly
something an eject program would provide in general (neither bsd's eject has
it), I'll write a volname replacement with libcdio and add that to libcdio
bundle (directly upstream).
Last time I looked (to add virtual/eject), software depending on eject wasn't
using volname at all.
Re-adding sparc and ppc64 back, sorry for the trouble guys.
unieject-3 uses dev-libs/confuse for configuration file handling, which is not
marked for those arches.