Date: Sun, 24 Oct 2004 16:25:19 -0700 From: "Loren M. Lang" <lorenl@alzatex.com> To: Vlad Tudorache <vladtudorache@home.ro> Cc: freebsd-questions@freebsd.org Subject: Re: KDE, kernel or other problem? Message-ID: <20041024232519.GB6513@alzatex.com> In-Reply-To: <417C0E25.6050001@home.ro> References: <417C0E25.6050001@home.ro>
next in thread | previous in thread | raw e-mail | index | archive | help
--rJwd6BRFiFCcLxzm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 24, 2004 at 11:18:45PM +0300, Vlad Tudorache wrote: > I was testing this on Linux (2.4.26 or 2.6.x) and FreeBSD 4.10 and 5.21.= =20 > My CD-RW refuses to eject media from KDE (NOT form GNOME) when I'm using= =20 > the "devices" created on desktop and sometimes even at "eject" command=20 > from console. Or, EVEN IF the CD is ejected, there's an error like=20 > "eject /dev/sr0 failed!" (replace sr0 with coresponding devices for the= =20 > OSes I mentioned). I repeat, NOT under GNOME. This happens on all the=20 > systems I mentioned, with/without atapicam or ide-scsi, respectively=20 > (I'm sorry for beeing so brief but I've been using UNIXes for ~3 years=20 > and I didn't have any problem). IThe problem appears with generic and=20 > self-compiled kernels. > Help! > Thank you. This a very annoying KDE problem, I get around it by just using ye old xterm for accessing all removable media. The problem is a device can't be unmounted when it's in use. It can be in use because a file or program is open on the media, or even if a program is sitting in that directory like the konqueror file manager. Usually closing the file manager window will fix that, but sometimes I have to use lsof to find which process is sitting in the cdrom directory and kill it. Most cdrom's are also locked by unix when there mounted so it can be a big problem. Mandrake gets around this problem by using a kernel mod called supermount which prevents devices from being locked even though they are mounted. On linux there is also an option to force a drive to be unlocked, but it really shouldn't be used except by things like knoppix just as the system halts. If anyone has a fix for this I might go back to using KDE again, instead of fvwm2+xterm which has always worked pretty well. >=20 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg" >=20 >=20 > !DSPAM:417c111f182511642842525! >=20 --=20 I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C =20 --rJwd6BRFiFCcLxzm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBfDnf+vN6RuSjKAwRAjskAJ42XP5mCxHDkpsQva3BFak6FUysQwCeP/21 IhBhV2u2n3V54885PCtGRXA= =50kJ -----END PGP SIGNATURE----- --rJwd6BRFiFCcLxzm--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041024232519.GB6513>