From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tim Cross Newsgroups: gmane.emacs.devel Subject: Re: Proposed patch: allow user to disable lockfile creation Date: Fri, 29 Jul 2011 10:12:11 +1000 Message-ID: References: <87ei1bqi8p.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1311898351 31048 80.91.229.12 (29 Jul 2011 00:12:31 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 29 Jul 2011 00:12:31 +0000 (UTC) Cc: johnw@newartisans.com, Lennart Borgman , emacs-devel@gnu.org, schwab@linux-m68k.org, dave@boostpro.com, stephen@xemacs.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 29 02:12:18 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Qmagc-0004q7-LD for ged-emacs-devel@m.gmane.org; Fri, 29 Jul 2011 02:12:18 +0200 Original-Received: from localhost ([::1]:58260 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qmagc-0004h6-1j for ged-emacs-devel@m.gmane.org; Thu, 28 Jul 2011 20:12:18 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:34371) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QmagZ-0004h1-IU for emacs-devel@gnu.org; Thu, 28 Jul 2011 20:12:16 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QmagY-0003As-GZ for emacs-devel@gnu.org; Thu, 28 Jul 2011 20:12:15 -0400 Original-Received: from mail-iy0-f169.google.com ([209.85.210.169]:51757) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QmagX-00039q-2t; Thu, 28 Jul 2011 20:12:13 -0400 Original-Received: by iyb14 with SMTP id 14so4299308iyb.0 for ; Thu, 28 Jul 2011 17:12:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=2wxzGKPm8XPz6cjJ5n/m5NXbHPoB7+wenJ/p/4WJguU=; b=XMWLMclunWj8g0znNb02DmIRyw/pRNqYpxe3QhgaajylJaZeNzAlOR9KOpIyGbpu/6 E066f88VknctHexvjQ0BA5Wf25y5j5hWOnevr4VcAhKoH6AIfALq8NfuLaJJuj5YC26N y0+Q3h+LmhZT6zR8NL6Egv2K/Wr8JRWdDbU1w= Original-Received: by 10.231.197.16 with SMTP id ei16mr434162ibb.111.1311898331512; Thu, 28 Jul 2011 17:12:11 -0700 (PDT) Original-Received: by 10.231.35.74 with HTTP; Thu, 28 Jul 2011 17:12:11 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.210.169 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:142474 Archived-At: On Fri, Jul 29, 2011 at 9:00 AM, Richard Stallman wrote: > =A0 =A0Is not the default today to have single users machines? And in oth= er > =A0 =A0cases have accounts setups so that clashes will not occur. > > Most machines today are single users, but I don't follow the second > part. =A0What do you mean by "account setups"? > > Normally, in a multi-user machine, people cooperate and there are some > files that various people might edit. > > -- > Dr Richard Stallman > President, Free Software Foundation > 51 Franklin St > Boston MA 02110 > USA > www.fsf.org =A0www.gnu.org > Skype: No way! That's nonfree (freedom-denying) software. > =A0Use free telephony http://directory.fsf.org/category/tel/ > > Another common use case is single systems with multiple serial users i.e. there is only ever one person actively using the system, but it is used by multiple people. In the 'old days' you would have to log out to allow another person to log in (via the same keyboard/monitor etc). However, many systems now have a 'switch user' context, which allows the desktop to switch to another user without the previous use logging out. Potentially, this could have locking implications. Yes, as far as I know, most of the remote file systems do have an entry in the output of df, at least under GNU Linux. Another common remote filesystem is sshfs, which uses the fuse utilities with ssh and can be dynamically created by the user. While most remote filesystems can are listed in df, not all of them have entries in fstab and the list is or can be somewhat dynamic i.e. change during a user's session. It seems that the issue isn't really about conflict detection per se, but rather how emacs implements it via symlinks. If the OS level file locking has matured enough, it would certainly be something worth looking at as I imagine it will allow emacs to perform such protection 'privately' and not put things in the filesystem which can impact on other programs. Personally, I've not found this an issue as the symlinks that emacs uses are easy to recognize and most of the scripts I use are ones I've written and told to ignore such links/directories. Tim