X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 19 Oct 2007 10:01:15 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] Updated: bash-3.2.25-17 Message-ID: <20071019080115.GF20400@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Oct 18 13:29, Igor Peshansky wrote: > On Wed, 17 Oct 2007, Eric Blake wrote: > > > [snip] > > Based on user response, I may be convinced to fold in the rest of Igor's > > create_devices.sh [see > > http://cygwin.com/cygwin-ug-net/using-specialnames.html] into the bash > > postinstall, as it admittedly looks a bit weird when 'ls /dev' shows > > /dev/stdin but not /dev/null (rest assured, all the devices still exist, > > even if a listing of /dev does not show them). > > FYI, mknod works just fine on Cygwin, and I've been using a /ddev > directory populated with mknod for a while now (not in scripts, of course) > with no problems. > > I have a preliminary version of a modified script that uses mknod to > populate a directory with devices. Should we use that instead (and put > this in a postinstall script for the "cygwin" package)? Why not create a stand-alone package in the base category which consists of just the postinstall script? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/