Bug#435645: Bug seen with 2.1.5-4

2008-02-11 Thread Vincent Fourmond
Hello, On Feb 11, 2008 2:10 AM, Klaus Ethgen <[EMAIL PROTECTED]> wrote: >spawnv(): executing /bin/mount '/bin/mount' '-t' 'iso9660' '-o' > 'nosuid,nodev,user,async,atime,noexec,uid=10230,gid=101' '/dev/hdc' > '/media/cdrom' > With eject switched to always using pumount also for drives moun

Bug#435645: Bug seen with 2.1.5-4

2008-02-10 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Vincent, Am So den 10. Feb 2008 um 11:06 schrieb Vincent Fourmond: > Thanks. I think I might understand the problem here. Just to make > sure, could you please provide the output of: > > pmount -d /dev/cdrom resolved /dev/cdrom to device /de

Bug#435645: Bug seen with 2.1.5-4

2008-02-10 Thread Vincent Fourmond
retitle 435645 pumount does not play nicely with symlinks in /etc/fstab thanks Hello, Klaus Ethgen wrote: > Well, my cdrom is no scsi. So: >~> pumount -d /cdrom >checking whether /cdrom is a mounted directory >resolved mount point /cdrom to device /dev/hdc >resolved /dev/hdc t

Bug#435645: Bug seen with 2.1.5-4

2008-02-09 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I now have the pmount 0.9.17-1 and the bug is still not fixed. Sorry for the late answer as I was very busy. Am Sa den 18. Aug 2007 um 1:42 schrieb Vincent Fourmond: > could you please post the result of > > pumount -d /dev/scd0 Well, my cd

Bug#435645: Bug seen with 2.1.5-4

2007-08-17 Thread Vincent Fourmond
Hello ! Klaus Ethgen wrote: >>> % eject -v >>> eject: using default device `cdrom' >>> eject: device name is `cdrom' >>> eject: expanded name is `/dev/cdrom' >>> eject: `/dev/cdrom' is a link to `/dev/scd0' >>> eject: `/dev/scd0' is mounted at `/cdrom' >>> eject: unmounting device `/dev/scd0' f

Bug#435645: Bug seen with 2.1.5-4

2007-08-17 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Am Di den 14. Aug 2007 um 13:51 schrieb Frank Lichtenheld: > > % eject -v > > eject: using default device `cdrom' > > eject: device name is `cdrom' > > eject: expanded name is `/dev/cdrom' > > eject: `/dev/cdrom' is a link to `/dev/scd0' > > eject

Bug#435645: Bug seen with 2.1.5-4

2007-08-14 Thread Nicholas Breen
On Tue, Aug 14, 2007 at 01:51:07PM +0200, Frank Lichtenheld wrote: > This is definetly no eject error message. It comes from pumount. > You will either need to list /cdrom in /etc/fstab (since pumount > should fall back to umount then, if it doesn't, please reassign this bug > there) or you need to

Bug#435645: Bug seen with 2.1.5-4

2007-08-14 Thread Frank Lichtenheld
On Sun, Aug 05, 2007 at 09:56:20PM -0700, Nicholas Breen wrote: > I also see this behavior on my system with eject 2.1.5-4. > > % eject -v > eject: using default device `cdrom' > eject: device name is `cdrom' > eject: expanded name is `/dev/cdrom' > eject: `/dev/cdrom' is a link to `/dev/scd0' > e

Bug#435645: Bug seen with 2.1.5-4

2007-08-05 Thread Nicholas Breen
found 435645 2.1.5-4 thanks I also see this behavior on my system with eject 2.1.5-4. % eject -v eject: using default device `cdrom' eject: device name is `cdrom' eject: expanded name is `/dev/cdrom' eject: `/dev/cdrom' is a link to `/dev/scd0' eject: `/dev/scd0' is mounted at `/cdrom' eject: un