public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug McNaught <doug@wireboard.com>
To: root@chaos.analogic.com
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Version 2.4.1 cannot be built.
Date: 31 Jan 2001 10:01:13 -0500	[thread overview]
Message-ID: <m3d7d3lq9y.fsf@belphigor.mcnaught.org> (raw)
In-Reply-To: <Pine.LNX.3.95.1010131093940.13598C-200000@chaos.analogic.com>
In-Reply-To: "Richard B. Johnson"'s message of "Wed, 31 Jan 2001 09:42:20 -0500 (EST)"

"Richard B. Johnson" <root@chaos.analogic.com> writes:

> See attached. "Just because you can see the candy doesn't mean
> they'll let you have any...."

[output of README when you connect:]

>  Please note that the directory structure on ftp.gnu.org was redisorganzied
>  fairly recently, such that there is a directory for each program.  One side
>  effect of this is that if you cd into the gnu directory, and do
>  > ls emacs*
>  you will get a list of all the files in the emacs directory, but it will not
>  be obvious from the ls output that you have to `cd emacs' before you can
>  download those files.

Now,

> ftp> cd gnu
> ftp> ls mak*
> 200 PORT command successful.
> 150 Opening ASCII mode data connection for file list.
> -rw-r--r--   1 ftp      ftp          1095 Jul 14  1997 makeinfo.README
> 
> make:
> -rw-r--r--   1 ftp      ftp         27010 Sep 23  1989 make-3.55-3.56.diff.gz
[...]
> -rw-r--r--   1 ftp      ftp       1030393 Jun 24  2000 make-3.79.1.tar.gz
> -rw-r--r--   1 ftp      ftp        959005 Apr 11  2000 make-3.79.tar.gz
> 226 Transfer complete.
> ftp> bin
> 200 Type set to I.
> ftp> get make-3.79.1.tar.gz
> local: make-3.79.1.tar.gz remote: make-3.79.1.tar.gz
> 200 PORT command successful.
> 550 make-3.79.1.tar.gz: No such file or directory

Duh.

Read the README next time; that's what it's there for.

-Doug
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-01-31 15:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-30 21:45 Version 2.4.1 cannot be built Richard B. Johnson
2001-01-30 22:13 ` Rik van Riel
2001-01-30 23:42   ` Reiserfs problem was: " Brett G. Person
2001-01-31  0:14     ` Chris Mason
2001-01-31 13:50   ` Richard B. Johnson
2001-01-30  3:15     ` Michael B. Trausch
2001-01-31 14:27       ` Richard B. Johnson
2001-01-31 13:55     ` Rik van Riel
2001-01-31 14:24       ` Richard B. Johnson
2001-01-31 14:35         ` Rik van Riel
2001-01-31 14:42           ` Richard B. Johnson
2001-01-31 14:48             ` David Woodhouse
2001-01-31 14:51               ` Rik van Riel
2001-01-31 14:48             ` Rik van Riel
2001-01-31 14:53             ` Mike Dresser
2001-01-31 15:01             ` Doug McNaught [this message]
2001-02-01 14:14             ` Matt Kemner
2001-01-31 15:03         ` James Sutherland
2001-02-02 22:22         ` Mo McKinlay
2001-01-30 22:36 ` Keith Owens
2001-01-30 22:57   ` Richard B. Johnson
2001-01-30 23:01     ` Xuan Baldauf
2001-01-30 23:04     ` Keith Owens
2001-01-30 23:09       ` Richard B. Johnson
2001-01-30 23:29         ` Keith Owens
2001-01-30 23:07     ` Richard B. Johnson
2001-01-31  6:14       ` Peter Samuelson
2001-01-31 18:37 ` mirabilos
  -- strict thread matches above, loose matches on Subject: below --
2001-01-31 14:49 anders.karlsson
     [not found] <20010131145059.D10769@dev.sportingbet.com>
2001-01-31 14:58 ` Richard B. Johnson

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=m3d7d3lq9y.fsf@belphigor.mcnaught.org \
    --to=doug@wireboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.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