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 Subject: Re: setup problem: only ash comes as /bin/sh From: Robert Collins To: "S.L." Cc: Elfyn McBratney , cygwin@cygwin.com In-Reply-To: <10484.1054819633@www3.gmx.net> References: <00de01c32b24$f9b806b0$710d86d9@ellixia> <10484.1054819633@www3.gmx.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-yBrlpaXsHwkNONh7ITgj" Organization: Message-Id: <1054820078.1328.2.camel@localhost> Mime-Version: 1.0 Date: 05 Jun 2003 23:34:38 +1000 --=-yBrlpaXsHwkNONh7ITgj Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2003-06-05 at 23:27, S.L. wrote: > >From a user point of view, I would create a 'Shells' subcategory for 'Ba= se'. > And an intermediate step for setup to manage the /bin/sh issue (when the > user chooses more than one shell).=20 Nope. ash is part of base. It's a required component for the cygwin net distribution. Installing multiple shells is completely supported, but skipping ash is not. Rob --=20 GPG key available at: . --=-yBrlpaXsHwkNONh7ITgj Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQA+30btI5+kQ8LJcoIRAudMAKCUuLkXGg0qeJPiyyg3lv4vCi01lwCfYSxb 5n81d+wxgvRVGH6ww+TSggg= =vSok -----END PGP SIGNATURE----- --=-yBrlpaXsHwkNONh7ITgj--