DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=fTDYuaRZVxxFSWp14LVnbs7N3dNfgHZYWVIiSuAthcfOaaQ064Act
	jFaE5cZ3DhV5p8zs7wJfIl87fcA2erKBDLStm9G4S/DZ9r3zimitP8nd4YoJ9qqH
	9qCjFBUvXySbJvy0sixxOlggGi/sK8nfn+6K52TiihcECB75mTQ3ps=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Mon, 10 Nov 2014 22:31:13 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: TEST RELEASE: Cygwin 1.7.33-0.8
Message-ID: <20141110213113.GK2782@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20141107091107.GS28195@calimero.vinschen.de> <001e01cffd1f$fe393810$faaba830$@ieee.org> <20141110202954.GA13071@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="RVlUGXxwBj5SDcM9"
Content-Disposition: inline
In-Reply-To: <20141110202954.GA13071@calimero.vinschen.de>
User-Agent: Mutt/1.5.23 (2014-03-12)

--RVlUGXxwBj5SDcM9
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Nov 10 21:29, Corinna Vinschen wrote:
> On Nov 10 14:53, Pierre A. Humblet wrote:
> > > > I just realized that deleting the /etc/passwd file in existing doma=
in
> > > > systems may change usernames, which will break cron and other progr=
ams
> > > > that use files named after usernames. Also the (local) privileged
> > > > username will change.
> >=20
> > > Yes.  Is there a way to accommodate that?  Maybe a postinstall script
> > > checking for existing user cron files and renaming them if required?
> >=20
> > That's possible but it must be a postinstall than runs when an updated
> > Cygwin is installed (or deinstalled), not when cron is, except if we tr=
y to
> > synchronize both.
>=20
> A new cron when Cygwin 1.7.33 goes release might be a good idea.
> I have already new OpenSSH and, even more important, base-cygwin
> packages waiting in the backdrop.

I just realized that this is hard, if not impossible to automate.
Consider that an update to Cygwin 1.7.33 leaves /etc/passwd intact
and no /etc/nsswitch.conf file will be installed.  Thus, the default
setting of "passwd: files db" will be used.  Thus, the usernames
won't change.  They *might* change if the administrator of the
system decides to remove /etc/passwd or set "passwd: db" in
/etc/nsswitch.conf, but there's no way to anticipate this move in
a postinstall script.

The easiest thing to do would probbaly be to provide a conversion
script for manual usage.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--RVlUGXxwBj5SDcM9
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUYS6gAAoJEPU2Bp2uRE+gbe0P/2AC87yUsbtIjQkal+D/zlJh
FKmkXByQfhqnkEN7NptUq+NS8EPTPCq6hXsmJovVuUiCZpNFI77tM+IwSkDhyvV4
xzYwZ2Ozi3oM79yv80Bck8nxS4feGkjdX9xyPAeF4GFPp9D68+JsKkgc91Dt3HSu
/vTOdpYNqheve7vAbAKsV2xalogx0sdw/5onrg6Pnsk6+umEaEJ5WzntG+kLrIDh
24VazMueAn3hxDsdiNr1tdqUBbIYqUuKlfH+xXFp8KJHrJ2jMf6U/cksmIMVQF8I
dF859A19EDFCaWcJX2ubEcM7XUbw1M22lhBeXRr+RF9DjZZJHTV2mgdXKg7AInai
9JZBC1nWiZKmJlStHere8h8KR7TbIe24nSpD73hFu+tTWAnuJ7zHlNfjy11+rUva
duIIGNXLTQj6oVR9A6DX4djKkmsDhxess4BHX/y16mMBpahvRVDHOSbO+sukrZTB
GCp9hcDfKH4Fb46vmmXw3pU2ZWYRpfSdjRTgnwMChF9aKyjDAUOLbPX67l5NfZRT
NnpY84EQ162nQcmC4Y4YEqFA+Zfy6NzjaDkKnlTEgQPLpCpLniOP/Vu6ULAvN7gD
Vp6Lga2c5WGyj8EAOvkWwxvf0LPxmF7IZO1SeuSw1XwMT9Mvr4lt/x5R2X1FQUGb
RgA05D51yXQJmOzbaM8+
=t09L
-----END PGP SIGNATURE-----

--RVlUGXxwBj5SDcM9--