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 1Mhmt7-0003NN-OP for garchives@archives.gentoo.org; Sun, 30 Aug 2009 16:04:18 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 207A2E08BD; Sun, 30 Aug 2009 21:13:14 +0000 (UTC) Received: from mail-gx0-f207.google.com (mail-gx0-f207.google.com [209.85.217.207]) by pigeon.gentoo.org (Postfix) with ESMTP id F0D4FE08BD for ; Sun, 30 Aug 2009 21:13:13 +0000 (UTC) Received: by gxk3 with SMTP id 3so4812921gxk.14 for ; Sun, 30 Aug 2009 14:13:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=kXJoKowxbSrEpj23I/2NyzrYWdVBl8ZCMk/3DAtSTXE=; b=uurn7WMOSxrbEyJBdzzTTRi+pYJsZx4DEpvpAGJ0rl+vH7oi/gIRq3J00LMGs0ikbD 02xm6riRkRz0TvmZyB75Tj6PMQTL99d7GElTtTfLO214ZHuMz5f0S9N2LFQX5UbWUxck iPgi0k/gPdXaTpSalImRLuHirjURIgEessj3o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=ZhRNjMnHF1yXPgYGO3nGdPkpV4MlTRaJKl7SzzZgzH2+H3OSDxkOcZKl5L8/9T+V2H v8jA9vUJuIyA2M1PxSZNSYjNdsfFYULAop3XZ6HNRqI5sR5b5ImDkCo8qWriGiiZrU6a JLqcn4gRkM0gTy2DC7YieDwO5pediFn4jXFZY= Received: by 10.91.28.9 with SMTP id f9mr3335194agj.89.1251666793697; Sun, 30 Aug 2009 14:13:13 -0700 (PDT) Received: from ?192.168.1.1? (adsl-222-123-15.jan.bellsouth.net [68.222.123.15]) by mx.google.com with ESMTPS id 38sm669346agd.9.2009.08.30.14.13.12 (version=SSLv3 cipher=RC4-MD5); Sun, 30 Aug 2009 14:13:12 -0700 (PDT) Message-ID: <4A9AEB67.9060906@gmail.com> Date: Sun, 30 Aug 2009 16:13:11 -0500 From: Dale User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.22) Gecko/20090823 SeaMonkey/1.1.17 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] How to set udev rule? References: <20090827233339.72529ea6@osage.osagesoftware.com> <200908301929.39692.wonko@wonkology.org> <200908302138.14457.dirk.heinrichs@online.de> <98e072813338e844438b47ec9e95c0fd.squirrel@jesgue.homelinux.org> In-Reply-To: <98e072813338e844438b47ec9e95c0fd.squirrel@jesgue.homelinux.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 58f28ade-77c1-431f-96e5-c41dcad0c949 X-Archives-Hash: f29d78a5409370a91de0c3e693c08159 Jes=FAs Guerrero wrote: > On Sun, August 30, 2009 21:38, Dirk Heinrichs wrote: > =20 >> Am Sonntag 30 August 2009 19:29:39 schrieb Alex Schuster: >> >> >> =20 >>> 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 th= e >>> memory stick? >>> =20 >> How do want to umount something that's not there anymore? You have to >> umount _before_ you pull it. >> =20 > > 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. And some people use this crap on udev rules to remove the > volume when they unplug the pendrive. Then they wonder why the heck > the file is not where it should be. I guess they never heard of cached > writes. > > The correct thing to do is of course to umount it before, > and then unplug it or whatever. > > If you truly want to umount after, you should at least do a sync before > removing the device. In any case, if you don't follow the logical > order of the things don't complain if then you find that the files that > should be there are not there when you need them. > > If you truly love risk, just use umount -l, but you have to promise not > to cry if the fs breaks or your files are not writen when you sudenly > unplug the device. > > =20 Basically, if he is going to do this the way he is thinking of doing it, use cp NOT mv. o_O If he uses mv and then unpkugs it without unmounting or syncing, the file is gone for good. At least with cp you still have the original file. Just thinking this through a little here. Dale :-) :-)=20