From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Mi57Z-0006oV-Uq for garchives@archives.gentoo.org; Mon, 31 Aug 2009 11:32:26 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 06EB6E07C9; Mon, 31 Aug 2009 16:41:18 +0000 (UTC) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by pigeon.gentoo.org (Postfix) with ESMTP id A24BFE07C9 for ; Mon, 31 Aug 2009 16:41:17 +0000 (UTC) Received: from rohan.altum.de (p5DC81808.dip0.t-ipconnect.de [93.200.24.8]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0MKv5w-1Mi9wS36JO-0003n9; Mon, 31 Aug 2009 18:41:16 +0200 Received: from localhost (localhost [127.0.0.1]) by rohan.altum.de (Postfix) with ESMTP id 65A95C96386 for ; Mon, 31 Aug 2009 18:41:16 +0200 (CEST) Received: from gondolin.localnet (gondolin [192.168.1.4]) (Authenticated sender: heini) by rohan.altum.de (Postfix) with ESMTP id DB2E0C95F36 for ; Mon, 31 Aug 2009 18:41:14 +0200 (CEST) From: Dirk Heinrichs Organization: Privat To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] How to set udev rule? Date: Mon, 31 Aug 2009 18:41:13 +0200 User-Agent: KMail/1.12.0 (Linux/2.6.30.5; KDE/4.3.0; i686; ; ) References: <98e072813338e844438b47ec9e95c0fd.squirrel@jesgue.homelinux.org> <200908302326.53203.wonko@wonkology.org> In-Reply-To: <200908302326.53203.wonko@wonkology.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2184349.uc2C9LUQ8Q"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200908311841.13365.dirk.heinrichs@online.de> X-Provags-ID: V01U2FsdGVkX1+FJdPtVCIOaDhr/fEGXFKIa0UhFsuP0Oix5xY 3vmhQrTCDGYPhsrIlHtnu5yFv3Ss78kQHK5z7Kwi7nBYV2/FeM Wlpt3sx+VhEd/Kta/I60A== X-Archives-Salt: b105bff3-a51b-475e-b1d6-2d0b29f42384 X-Archives-Hash: d9ec82fdeb20190d7ba859b67f50e158 --nextPart2184349.uc2C9LUQ8Q Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Am Sonntag 30 August 2009 23:26:52 schrieb Alex Schuster: > Jes=FAs Guerrero writes: > > On Sun, August 30, 2009 21:38, Dirk Heinrichs wrote: > > > Am Sonntag 30 August 2009 19:29:39 schrieb Alex Schuster: > > >> I have to change the bus from usb to scsi, then it works. But what > > >> about unmounting? Is is possible to have it unmounted after I pull t= he > > >> memory stick? > > > > > > How do want to umount something that's not there anymore? You have to > > > umount _before_ you pull it. > > > > You can force the umount using -l (no, it's not documented in the man > > page). You can use this to umount a volume *after* it has been physical= ly > > removed. > > The -l is not necessary here, a simple umount is enough. > > > And some people use this crap on udev rules to remove the > > volume when they unplug the pendrive. > > Yes, this very rule would be nice to have :) No, it would not. It can (and most likely will) lead to data loss. > I do so, it makes me feel better, but I wonder whether it is _really_ > necessary. Yes, it is. You never know when your data is written to physical storage=20 unless you explicitely synced or umounted it while the device was still=20 connected. > I see Windows users do this all the time, without any problem > yet. Of course, the wait a little after writing to it, but a few seconds > after the blinking stops seem to be enough. Usually it is, but you never know. Windows users don't have that broad choi= ce=20 of filesystems. They have NTFS and that's it, so they may know they're save= =2E=20 Linux filesystems may handle this differently, depending on which one you'v= e=20 chosen. > And people are lazy, I know my > Linux users _will_ just plug the stick. Using the KDE4 automounter, the > device will be unmounted automatically in this case, You mount filesystems, not devices. If you plug the device which holds the= =20 filesystem you've mounted, the fs can't be umounted anymore. There's nothin= g=20 KDE automounter (aka HAL/DBUS) can do about it. > but I am looking for a > solution without KDE4, and as few user interaction as possible. The udev > mouting rule is nice, but it leaves a lot of mounts when plugging in and > out repeatedly. Use the kernel automounter (autofs). It also umounts automatically (after a= =20 configurable time). Bye... Dirk --nextPart2184349.uc2C9LUQ8Q Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) iD8DBQBKm/0p8NVtnsLkZ7sRAttIAKCxWxVIyseUBGM3GPy65p8uookh3QCfYrxF U1LGEdJN2ePHq47th0HaWkI= =4N5W -----END PGP SIGNATURE----- --nextPart2184349.uc2C9LUQ8Q--