From: Hubert Figuiere <Hubert.Figuiere@solsoft.fr>
To: Patrik Jonsson <patrik@ucolick.org>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: New XF68_FBDev - how to download?
Date: Mon, 7 Dec 1998 12:09:05 +0100 [thread overview]
Message-ID: <19981207120905.B2395@dirkpitt.solsoft.fr> (raw)
In-Reply-To: <Pine.SUN.3.95.981205180529.7735A-100000@helios.ucolick.org>; from Patrik Jonsson on Sat, Dec 05, 1998 at 06:07:49PM -0800
According to Patrik Jonsson <patrik@ucolick.org>:
>
> On Fri, 4 Dec 1998, Geert Uytterhoeven wrote:
>
> > New version at:
> >
> > http://www.cs.kuleuven.ac.be/~geert/bin/XF68_FBDev-accel-ppc-19981204-2.gz
>
> Hi all,
> how in the world do you get this file? When I try to save it in netscape,
> it strips the .gz suffix, but doesn't seem to unzip the file. I can't
> execute OR run gunzip on the thing I get...
> I hate downloading binaries with netscape! Does anyone have any advice
> here?
Try with lynx:
lynx \
http://www.cs.kuleuven.ac.be/~geert/bin/XF68_FBDev-accel-ppc-19981204-2.gz \
-dump >XF68_FBDev-accel-ppc-19981204-2.gz
Hub
--
"Your mouse has moved. Please reboot to continue."
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1998-12-07 11:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.03.9812041606410.26444-100000@mercator.cs.kuleuven.ac.be>
1998-12-06 2:07 ` New XF68_FBDev - how to download? Patrik Jonsson
1998-12-07 11:09 ` Hubert Figuiere [this message]
1998-12-07 14:50 ` Jens Ch. Restemeier
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=19981207120905.B2395@dirkpitt.solsoft.fr \
--to=hubert.figuiere@solsoft.fr \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=patrik@ucolick.org \
/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).