Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Latest update problems (ntsec and file permissions, I think)(tagged releases comment) Date: Mon, 21 Oct 2002 11:43:48 -0400 Message-ID: <7BFCE5F1EF28D64198522688F5449D5AD63A63@xchangeserver2.storigen.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Scott Prive" To: "William A. Hoffman" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g9LFi0o06899 > -----Original Message----- > From: William A. Hoffman [mailto:billlist@nycap.rr.com] > Sent: Monday, October 21, 2002 10:12 AM > To: cygwin@cygwin.com > Subject: Latest update problems (ntsec and file permissions, I think) > > Once I did that, things were better. Is this a problem that is going > to be fixes, or are people supposed to know that they have to run > mkpasswd -du after running setup? BTW, I also tried setting CYGWIN to > nontsec, but this had no effect on the problem. > > If a new user were to try cygwin right now, I think they > would be a bit > confused. > > -Bill Personally, I watch the list and am more careful now about upgrading a box I use in production. This can be intimidating to new users, especially when the "norm" is to expect a Setup program to present you with Release Notes. Cygwin reminds me of running the "testing" tree of Debian: something is updated every day, and by participating in this tree you assume a higher level of risk than "usual" Windows software. I think what is sorely needed is a "tagged release", or bundled packages. The way this could work is you are locked into a version set, and can add and remove packages without always getting the "latest" code. The benefit here would be a set of "known issues" for the release, and a proper set of Release Notes could be made for each release. I get the impression patches for "releases" and "show release notes" would be accepted (things I couldn't offer). -Scott -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/