From: Francesco Poli <frx@firenze.linux.it>
To: cpufreq@www.linux.org.uk
Subject: Re: Help with Installation
Date: Tue, 6 Apr 2004 23:01:34 +0200 [thread overview]
Message-ID: <20040406230134.01c2e4b3.frx@firenze.linux.it> (raw)
In-Reply-To: <20040405220654.D17303@flint.arm.linux.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1521 bytes --]
On Mon, 5 Apr 2004 22:06:54 +0100 Russell King wrote:
> > 2) modifies it using latest cpufreq from
> > http://ftp.linux.org.uk/pub/linux/cpufreq/
>
> This would be a manual step.
Why? Did I misunderstand something?
Wouldn't some shell commands like
tar xzvfp cpufreq-...tar.gz
cd cpufreq
./patchin.sh /path/to/kernel/sources
suffice?
I am quoting Bruno Ducrot's instructions... but maybe I don't catch
something important...
>
> > Such a script should be run daily (via cron) on ftp.linux.org.uk
>
> You're making the very big assumption that ftp.linux.org.uk _has_
> the space to do this. [...]
>
> So, _we_ _do_ _not_ _currently_ _have_ _the_ _resources_ _to_ _host_
> _such_ _a_ _service_. As I've said _three_ times in this thread so
> far.
I'm sorry: I didn't realize you were /so/ short of space... :-(
I thought you meant you couldn't generate and store one daily patch for
/every/ 2.4.x kernel version (that is 25 daily patches + a zillion of
patches against /all/ the pre-releases).
I now realize that you don't even have enough resources for one daily
patch against /one/ kernel version.
>
> The fact is that right now there is only 10MB free for the anonymous
> FTP archive.
That's really a pity... :-(
--
| GnuPG Key ID = DD6DFCF4 | You're compiling a program
Francesco | Key fingerprint = | and, all of a sudden, boom!
Poli | C979 F34B 27CE 5CD8 DC12 | -- from APT HOWTO,
| 31B5 78F4 279B DD6D FCF4 | version 1.8.0
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq
next prev parent reply other threads:[~2004-04-06 21:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-03 13:42 Help with Installation Ozeki San
2004-04-03 14:50 ` Bruno Ducrot
2004-04-03 15:16 ` Francesco Poli
2004-04-03 16:22 ` Russell King
2004-04-04 17:57 ` Francesco Poli
2004-04-04 21:11 ` Dominik Brodowski
2004-04-05 20:20 ` Francesco Poli
2004-04-05 21:06 ` Russell King
2004-04-06 21:01 ` Francesco Poli [this message]
2004-04-07 7:11 ` Russell King
2004-04-07 20:26 ` Francesco Poli
2004-04-05 21:11 ` Dominik Brodowski
2004-04-06 8:25 ` Bruno Ducrot
2004-04-06 8:47 ` Bruno Ducrot
2004-04-06 21:50 ` Francesco Poli
2004-04-07 16:18 ` Bruno Ducrot
2004-04-06 21:48 ` Francesco Poli
2004-04-06 22:00 ` Dominik Brodowski
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=20040406230134.01c2e4b3.frx@firenze.linux.it \
--to=frx@firenze.linux.it \
--cc=cpufreq@www.linux.org.uk \
/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