From: Cort Dougan <cort@fsmlabs.com>
To: Frank Smith <smith@appliedmicro.ns.ca>
Cc: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: ftp.ppc.kernel.org
Date: Tue, 25 Jan 2000 14:40:22 -0700 [thread overview]
Message-ID: <20000125144022.E25824@hq.fsmlabs.com> (raw)
In-Reply-To: <00Jan25.074648ast.7304@dragon.appliedmicro.ns.ca>; from Frank Smith on Tue, Jan 25, 2000 at 07:46:47AM -0400
We're going to be moving it because of the problems. We'll have a better
feed with fewer hops to get elsewhere.
} Hi,
}
} Has anyone else been having problems connecting to
} ftp.ppc.kernel.org? Anyone know what's going on?
}
} I recall there being some small ramdisk images in the
} embedded directory. Would someone be so kind as to
} e-mail me one? I'm just looking for something small
} to hack around with.
}
} Thanks,
} Frank Smith.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-01-25 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-25 11:46 ftp.ppc.kernel.org Frank Smith
2000-01-25 21:40 ` Cort Dougan [this message]
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=20000125144022.E25824@hq.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=smith@appliedmicro.ns.ca \
/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 NNTP newsgroup(s).