From: Robert Collins <robert.collins@itdomain.com.au>
To: Mark Bradshaw <bradshaw@staff.crosswalk.com>
Cc: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: RE: press for cygwin
Date: Fri, 31 Aug 2001 17:09:00 -0000 [thread overview]
Message-ID: <999303016.27290.11.camel@lifelesswks> (raw)
In-Reply-To: <911C684A29ACD311921800508B7293BA010A8C81@cnmail>
On 31 Aug 2001 10:35:45 -0400, Mark Bradshaw wrote:
> Hmm... Should I paint a bulls eye on my chest here. Eh. Why not.
Hmmm... do you gamble ? ;}
> 3) Yes I know it's an unsupported install, but I think the point was missed
> here. Many windows admins won't install the full cygwin installation, and
> most won't have a clue what to do with bash, etc. The point here isn't to
> exclude people from a great tool, but to help make an intermediate step more
> palatable. I know many will disagree with this, with sentiments along the
> lines of "They should just learn how to work with it." I disagree. I think
> it's worth it to get telnet replaced, in whatever fashion that happens.
> Bashless or not.
I'm only addressing this point, because I believe that the already
posted responses from Chuck and Larry didn't quite emphasis enough. You
are in the position of writing a HOW-TO for installers of sshd for
cygwin... chucks url reference (which had a typo:
http://tech.erdelynet.com/cygwin-sshd.asp is the correct address) covers
a somewhat larger install than you needed.
This page http://tech.erdelynet.com/cygwin-sshdmin.asp covers using the
cygwin setup.exe to install the core files - you could easily remove
ash,bash, fileutils, gawk, grep, sh-utils and txtutils from the list.
This would give you a *standard install* that happened to have only the
core utilities. The precious cygwin mount points and symlinks needed for
correct operation - say when these budding NT Admins learn about grep or
awk and try to install it - when any larger packages are added in. Also
note that setup.exe from cygwin.com extracts the .tar.gz files - no
experience with tar is needed.
As a parallel - hopefully I won't rub salt into the wounds :] - the
winzip approach is roughly equivalent to taking a MS Office install CD,
extracting winword.exe and a few select .dll's by hand, and then
manually adding a couple of registry keys. Sure - once someone documents
how to do it, anyone can follow, but *none* of the followers can ever
install the full office without a traumatic repair period.
If you are in a position to create errata for that article, I encourage
you to do so... you will be saving your target audience from a lot of
grief - down the track.
Rob
--
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/
next prev parent reply other threads:[~2001-08-31 17:09 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-31 7:36 Mark Bradshaw
2001-08-31 8:07 ` Charles Wilson
2001-08-31 10:29 ` Larry Hall (RFK Partners, Inc)
2001-08-31 17:09 ` Robert Collins [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-06 1:55 jmarshall
2001-09-05 5:04 jmarshall
2001-09-05 8:52 ` Christopher Faylor
2001-09-03 8:56 Bernard Dautrevaux
2001-09-03 6:52 Bernard Dautrevaux
2001-09-03 7:56 ` Charles Wilson
2001-09-03 8:14 ` Christopher Faylor
2001-09-03 8:45 ` Michael Schaap
2001-09-03 9:03 ` Christopher Faylor
2001-09-03 9:30 ` Andrew Markebo
2001-09-03 9:36 ` Christopher Faylor
2001-09-03 15:23 ` Robert Collins
2001-09-03 18:23 ` Christopher Faylor
2001-09-03 19:17 ` Charles Wilson
2001-09-03 19:35 ` Robert Collins
2001-09-04 9:52 ` Warren Young
2001-09-04 12:52 ` Christopher Faylor
2001-09-05 18:04 ` Warren Young
2001-09-07 12:27 ` Warren Young
2001-09-07 12:35 ` Christopher Faylor
2001-09-07 14:22 ` Warren Young
2001-09-07 14:43 ` Christopher Faylor
2001-08-31 0:34 Press for Cygwin Peter Ring
2001-08-30 14:34 press for cygwin Peter Buckley
2001-08-30 14:57 ` Christopher Faylor
2001-08-30 14:31 Press for Cygwin yap_noel
2001-08-30 15:38 ` Eric M. Monsler
2001-08-30 14:10 Robinow, David
2001-08-30 14:24 ` Charles Wilson
2001-08-30 13:47 Robinow, David
2001-08-30 12:57 Larry Hall (RFK Partners, Inc)
2001-08-30 13:07 ` Christopher Faylor
2001-08-30 13:12 ` Larry Hall (RFK Partners, Inc)
2001-08-30 13:25 ` Christopher Faylor
2001-08-30 13:37 ` Jonathon Merz
2001-08-30 14:04 ` Charles Wilson
2001-08-30 13:29 ` Rick Rankin
2001-08-30 13:33 ` Gerrit P. Haase
2001-08-30 13:42 ` Michael Schaap
2001-08-30 13:50 ` Christopher Faylor
2001-08-30 14:01 ` Michael Schaap
2001-08-30 14:06 ` Christopher Faylor
2001-09-02 20:24 ` John Marshall
2001-08-30 13:56 ` Gerrit P. Haase
2001-08-30 14:03 ` Michael F. March
2001-08-30 14:12 ` Michael Schaap
2001-08-30 14:06 ` Charles Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=999303016.27290.11.camel@lifelesswks \
--to=robert.collins@itdomain.com.au \
--cc=bradshaw@staff.crosswalk.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).