From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17136 invoked by alias); 3 Apr 2008 16:27:07 -0000 Received: (qmail 17116 invoked by uid 22791); 3 Apr 2008 16:27:07 -0000 X-Spam-Check-By: sourceware.org Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Thu, 03 Apr 2008 16:26:49 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id D2CDE6D430A; Thu, 3 Apr 2008 18:26:46 +0200 (CEST) Date: Thu, 03 Apr 2008 16:27:00 -0000 From: Corinna Vinschen To: cygwin-apps@cygwin.com, cygwin-developers@cygwin.com Subject: Re: [HEADSUP] Let's start a Cygwin 1.7 release area Message-ID: <20080403162646.GA27896@calimero.vinschen.de> Mail-Followup-To: cygwin-apps@cygwin.com, cygwin-developers@cygwin.com References: <20080402123551.GB4468@calimero.vinschen.de> <20080402174556.GI4468@calimero.vinschen.de> <47F40F16.8080303@cwilson.fastmail.fm> <20080403094220.GA21673@calimero.vinschen.de> <20080403135620.GA9219@ednor.casa.cgf.cx> <20080403141958.GM4468@calimero.vinschen.de> <20080403161154.GC9594@ednor.casa.cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080403161154.GC9594@ednor.casa.cgf.cx> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2008-04/txt/msg00046.txt.bz2 On Apr 3 12:11, Christopher Faylor wrote: > On Thu, Apr 03, 2008 at 04:19:58PM +0200, Corinna Vinschen wrote: > >Do you think that / should be free as today: > > > > C:\arbitrary\useless\new\path / ntfs binary 0 0 > > > >or do you think an automatic approach as the above > > > > root / ntfs binary 0 0 > > > >is the way to go? As for cygdrives, isn't the > > > > cygdrive /mnt auto binary 0 0 > > > >already along the lines of an automount?!? > > "auto" in /etc/fstab doesn't mean "automount". It means that it is > meant to be "auto"matically mounted at "boot time". That's fine for /, /bin, /usr/bin. > It isn't fine for z: where z: is a usb device. Uh, that's something I didn't look for. I just used the word "auto" because it sounded nice at this point. Actually the third field is ignored. The important part is the "cygdrive" in the first field, which is along the lines of, say, "proc" or "sysfs" in Linux. We don't have a reason (so far) to care for the FS type field in fstab. > >> >Another problem is that the 1.7 mount(1) still creates the mount entries > >> >in the registry. This should be removed, if we stick to the file based > >> >approach. mount would only create temporary mount points which are > >> >only valid in this single session, until the last Cygwin process in this > >> >session exits. A bit like a reboot on Linux :) > >> > >> On XP it should be possible to make it so that the mounts last until > >> reboot. If we can do that I think it would be ideal. > > > >How? The mount points are bound to the existance of the shared > >memory they reside in. This shared mem disappears when the last > >Cygwin process in a session exits. > > I have to research what I'm thinking of but I think it's possible. I don't > know if it is possible for a non-privileged user though. If you mean to create permanent shared objects, that's not possible for an admin user either without tweaking the security policy. This policy is by default only active for kernel mode code. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat