From: Cjfogg@aol.com
To: gnu-win32@cygnus.com
Subject: Re: Installation problems
Date: Sun, 27 Dec 1998 07:03:00 -0000 [thread overview]
Message-ID: <dfecf7d3.36864c30@aol.com> (raw)
In a message dated 27/12/98 04:03:08 GMT, you write:
<< Hi Cjfogg,
>>Hi,
>>
>>I am very new to programming and have gotten a little confused with Cygwin-
>>b20. I hate to ask a simple question, but I have downloaded
>>user-man.tar.bz2, stored it in Wordpad, and haven't the first clue how to
>>read it. I have tried to 'cd' to it but keep getting the reply;
>Did you download it with Netscape or MSIE ?
> I suppose, these get confused by the .bz2 ending of the file and try to
> store it as text file.
> Try to get it with some real ftp client or right click on wherever you
>saw the link and chose "download".
I downloaded it with aol and haven't had a lot of luck with using ftp. I am
refused a connection, and still can't manage to unpack user-man_tar.bz2.
Whatever I do, it is always stored in Wordpad.
>>
>>user-man.tar.bz2: Is a directory.
> Uhm, after having downloaded this file, copy it to for example /temp and
> unpack it with "bzip2 -d user-man.tar.bz2". You get a tar archive after
> having done this. Untar it with "tar -xvf user-man.tar".
>You then have a directory with all the man page files.
> So far for the easy part - now you need to download and install groff,
> ncurses, less and man ! You can get them from
> ftp://ftp.franken.de/pub/win32/develop/gnuwin32/cygwin32/porters/Hirmke_Micha
el/>B20
Argh! More to download? Sorry to sound ignorant (again) but what does groff,
ncurses, less and man do?
>>
>>What am I doing wrong? If I can't read the manual I don't have very high
>>hopes for my programming career!
>Don't give up - there is always a starting point and no one can know
> everything when starting with something new.
>>Thanks,
>>Catherine
Good luck !
Bye.
Michael.
--
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next reply other threads:[~1998-12-27 7:03 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-27 7:03 Cjfogg [this message]
1998-12-27 21:28 ` Chris McFarlane
-- strict thread matches above, loose matches on Subject: below --
2009-06-15 5:28 Neanderthelle Jones
2009-06-15 8:31 ` Larry Hall (Cygwin)
2009-06-15 8:47 ` Neanderthelle Jones
2005-04-15 3:02 George Sohos
2005-04-15 4:41 ` George Sohos
2005-04-15 5:09 ` Brian Dessent
2005-04-15 18:47 ` George Sohos
2004-06-08 16:56 Chris Carlson
2003-09-02 11:49 Hoyt Bailey
2003-09-02 14:23 ` Igor Pechtchanski
2003-09-02 1:13 Hoyt Bailey
2003-09-02 1:37 ` Larry Hall
2003-09-02 1:50 ` Igor Pechtchanski
2002-11-10 8:46 Todd Jones
2002-11-10 8:58 ` Christopher Faylor
2001-12-12 2:46 SHAJI K K
2001-12-12 7:23 ` Jason Tishler
2001-11-11 8:26 installation problems Robert Collins
2000-08-02 5:08 Installation problems Earnie Boyd
2000-08-02 7:07 ` DJ Delorie
2000-08-02 4:42 David A. Cobb
2000-08-02 7:05 ` DJ Delorie
2000-08-02 7:56 ` Norman Vine
1999-11-15 6:41 Earnie Boyd
1999-11-30 23:39 ` Earnie Boyd
1999-11-13 19:53 Ryan & Brigette Ramsey
1999-11-30 23:39 ` Ryan & Brigette Ramsey
1998-12-27 11:52 N8TM
[not found] <8256f9cf.36813b20.cygnus.gnu-win32@aol.com>
1998-12-23 20:10 ` DJ Delorie
1998-12-23 10:49 Cjfogg
1998-12-26 16:39 ` Michael Hirmke
1997-07-03 6:05 Xavier.Fornari
1997-01-31 5:54 Phaichayont
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=dfecf7d3.36864c30@aol.com \
--to=cjfogg@aol.com \
--cc=gnu-win32@cygnus.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).