From: fmarshall AT acm DOT org (Fred Marshall) Subject: WIN NT File Structure 24 Nov 1998 03:08:11 -0800 Message-ID: <006a01be16f8$327c25d0$cac8c8c8.cygnus.gnu-win32@mindspring> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0062_01BE16B5.1C7A47A0" To: "Cygnus32" This is a multi-part message in MIME format. ------=_NextPart_000_0062_01BE16B5.1C7A47A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable In working to install various GNU and CYGNUS tools, I find that the = assumed file structure is sometimes hard to comprehend - because I'm not = a big UNIX user I guess. Any suggestions how to create a file structure that will work well for = GNU and CYGNUS tools? "Work well" means: 1) Be usable without a lot of trouble when it's all installed. 2) Be easy to comprehend installation instructions during installation. Seems this would be very helpful to a lot of people and might reduce the = number of questions asked during installation. ------=_NextPart_000_0062_01BE16B5.1C7A47A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

In working to = install various=20 GNU and CYGNUS tools, I find that the assumed file structure is = sometimes hard=20 to comprehend - because I'm not a big UNIX user I guess.

Any suggestions = how to create=20 a file structure that will work well for GNU and CYGNUS = tools?

"Work = well"=20 means:

1) Be = usable without a=20 lot of trouble when it's all installed.

2) Be = easy to=20 comprehend installation instructions during installation.

Seems this = would be very=20 helpful to a lot of people and might reduce the number of questions = asked during=20 installation.

------=_NextPart_000_0062_01BE16B5.1C7A47A0-- - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".