Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <004701c0207f$43c91180$f7c723cb@lifelesswks> From: "Robert Collins" To: , "Chris Abbey" References: <4 DOT 3 DOT 2 DOT 7 DOT 0 DOT 20000917003310 DOT 00bdce30 AT pop> <4 DOT 3 DOT 2 DOT 7 DOT 0 DOT 20000917015958 DOT 00bda100 AT pop DOT bresnanlink DOT net> Subject: Re: mount points and inetd Date: Sun, 17 Sep 2000 19:14:10 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 X-OriginalArrivalTime: 17 Sep 2000 08:12:43.0369 (UTC) FILETIME=[0DF85D90:01C0207F] ----- Original Message ----- From: "Chris Abbey" To: Sent: Sunday, September 17, 2000 7:03 PM Subject: Re: mount points and inetd > At 18:00 9/17/00 +1100, Robert Collins wrote: > >Two thoughts: > > > >are your mounts system or user mounts? > > all user as I showed, but I think the three created by default > *should* be system; at least / should be.... I've just moved them > over to system mounts and am rebooting now... > > ok, that fixes the three important ones, but that exposes me to > the userid behavior... I guess I'll just make *all* my mounts > system mounts (in which case I'll question the usefulness of > having user mode mounts at all.) Inetd *needs a mount table* - just as with Unix systems. In fact cygwin is more flexible that some Unices. I suggest that your core (/, /usr/bin, /usr/lib, /etc) mounts be system and then the rest can be user or system at your choice. DJ - perhaps setup should default to 'install for all' ? (If it doesn't already) > >two: inetd may be trying to start before the networking services have > >started: ie before tcp is available. > > hmmm... good idea, although I should have pointed out that the > failure was clearly mount point related as the logs showed that > it couldn't find /etc/inetd.conf > > actually... shouldn't inetd --install-as-service do this > automatically? I've created the reg key myself for this, > just to prevent future wierdness though. ;) If anyone wants > directions on how to do this let me know. > > > -- > Want to unsubscribe from this list? > Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com > > -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com