Skip to contentSkip to conversation

Deprecating .gz format on kernel.org

DISCUSSION H. Peter Anvin 38 participants 57 messages Mar 19, 2003 – Mar 26, 2003 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

Hello everyone,

At some point it probably would make sense to start deprecating .gz format files from kernel.org.

I am envisioning this as a three-phase changeover:

a) Get all mirrors to carry .bz2 format. This would affect the following sites:

DUTH:format=gz
GARBO:format=gz
HCMC:format=gz
IGLU:format=gz
LINUXAID:format=gz
LLARIAN-NET:format=gz
MINET-FR:format=gz
NC-ORC:format=gz
PCSS:format=gz
PROGRAMVAREVERKSTEDET:format=gz
PUB-FTP-UNIVERSITY-OF-OLDENBURG:format=gz
RN-RNO:format=gz
TASK:format=gz
TELEPAC:format=gz
TENGU-EASYNET-FR:format=gz
UNC-METALAB:format=gz
WEBLAB:format=gz

b) Once that is done, change the robots to no longer require .gz files; .bz2 files uploaded would be signed but no .gz file would be generated.

-> If we get a complete loss of data here, all .gz files would be lost.

c) At some point, deprecate .gz uploads entirely and remove all the old .gz files. After that point .gz files uploaded would be treated just like .Z, .zip or any other "unmanaged" compression format.

Now, the questions that come up are:

i) Does this sound reasonable to everyone? In particular, is there any loss in losing the "original" compressed files?

ii) Assuming a yes on the previous question, what time frame would it make sense for this changeover to happen over?

-hpa

#1 lore raw
Quoted 38 lines · H. Peter Anvin

Hello everyone,

At some point it probably would make sense to start deprecating .gz format files from kernel.org.

I am envisioning this as a three-phase changeover:

a) Get all mirrors to carry .bz2 format. This would affect the following sites:

DUTH:format=gz
GARBO:format=gz
HCMC:format=gz
IGLU:format=gz
LINUXAID:format=gz
LLARIAN-NET:format=gz
MINET-FR:format=gz
NC-ORC:format=gz
PCSS:format=gz
PROGRAMVAREVERKSTEDET:format=gz
PUB-FTP-UNIVERSITY-OF-OLDENBURG:format=gz
RN-RNO:format=gz
TASK:format=gz
TELEPAC:format=gz
TENGU-EASYNET-FR:format=gz
UNC-METALAB:format=gz
WEBLAB:format=gz

b) Once that is done, change the robots to no longer require .gz files; .bz2 files uploaded would be signed but no .gz file would be generated.

-> If we get a complete loss of data here, all .gz files would be lost.

c) At some point, deprecate .gz uploads entirely and remove all the old .gz files. After that point .gz files uploaded would be treated just like .Z, .zip or any other "unmanaged" compression format.

Quoted 4 lines

Now, the questions that come up are:

i) Does this sound reasonable to everyone? In particular, is there any loss in losing the "original" compressed files?

I don't think phase three is really needed...

It sounds reasonable, but if it's mainly due to space consuption, I think it would be nice to code a bzip2-to-gz cgi server so that there is no loss on functionality. This would need CPU power, so perhaps rate-limiting the sending side of the CGI would manage to keep the CPU low on use.

Quoted 2 lines

ii) Assuming a yes on the previous question, what time frame would it make sense for this changeover to happen over?

Don't know.

Greets anyways, Antonio.

#2 lore raw
In reply to H. Peter Anvin
Quoted 2 lines

At some point it probably would make sense to start deprecating .gz format files from kernel.org.

Yay!

Quoted 4 lines

Now, the questions that come up are:

i) Does this sound reasonable to everyone? In particular, is there any loss in losing the "original" compressed files?

Can't see why ... the duplication seems rather silly.

Quoted 2 lines

ii) Assuming a yes on the previous question, what time frame would it make sense for this changeover to happen over?

As soon as you can get the mirrors to change over?

M.

#3 lore raw
In reply to H. Peter Anvin

Hello Peter , IMO it ain't going away '.' . My systems will not carry .bz2's , that is a Fyi . Not that it matters for systems over which you have opinion &/or control . Thanks for listening .
JimL

Quoted 6 lines · H. Peter Anvin

Hello everyone,
At some point it probably would make sense to start deprecating .gz format files from kernel.org.
I am envisioning this as a three-phase changeover:
a) Get all mirrors to carry .bz2 format. This would affect the following sites:

Signature · 5 lines
       +------------------------------------------------------------------+
       | James   W.   Laferriere | System    Techniques | Give me VMS     |
       | Network        Engineer |     P.O. Box 854     |  Give me Linux  |
       | [email protected] | Coudersport PA 16915 |   only  on  AXP |
       +------------------------------------------------------------------+
#4 lore raw
In reply to H. Peter Anvin
Quoted 2 lines · H. Peter Anvin

i) Does this sound reasonable to everyone? In particular, is there any loss in losing the "original" compressed files?

No, there is at least one reason for the "original" .gz files. Here are the logical steps:

a) any Linux distribution contains their own "linux" package with the source base being "vanilla" Linux .tar.gz file

b) switching such to .tar.bz2 will make building the package longer because of longer extract times

c) re-running tar to generate a .tar.gz from .tar.bz2 and store the .tar.gz instead will make customers suspicious --- i.e. they will have to ask "is this _really_ a plain Linux tree or do I need to run diff(1) to verify, just in case?"

See the reasoning? However, I agree that this reason is very weak. But you were interested in any reasons, including weak ones, I assume :)

Regards
Tigran

Quoted 12 lines

ii) Assuming a yes on the previous question, what time frame would it make sense for this changeover to happen over?

-hpa

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#21 lore raw
In reply to H. Peter Anvin
Quoted 4 lines · H. Peter Anvin

Hello everyone,

At some point it probably would make sense to start deprecating .gz format files from kernel.org.

It is a convinient feature that I can download the kernel now and then when at work (no linux) - and it makes it a bit simpler to use an archiver that has native support for the format used. Winzip, being the only allowed archiver at work, does not have native bz2 support.

I have a .bz2 commandline version on the windoze machine so I will cope, but mainly to let you know that deprecating .gz you will make it difficult for a minority to read the kernel src.

Sam

#5 lore raw
In reply to Tigran Aivazian
Quoted 9 lines · Tigran Aivazian
Quoted 2 lines · H. Peter Anvin

i) Does this sound reasonable to everyone? In particular, is there any loss in losing the "original" compressed files?

No, there is at least one reason for the "original" .gz files. Here are the logical steps:

a) any Linux distribution contains their own "linux" package with the source base being "vanilla" Linux .tar.gz file

I can't speak for the others, but Red Hat Linux uses the .bz2 files in kernel rpms

#6 lore raw

Em Wed, Mar 19, 2003 at 10:42:07PM +0100, Arjan van de Ven escreveu:

Quoted 7 lines · Tigran Aivazian
Quoted 3 lines · H. Peter Anvin

a) any Linux distribution contains their own "linux" package with the source base being "vanilla" Linux .tar.gz file

I can't speak for the others, but Red Hat Linux uses the .bz2 files in kernel rpms

Conectiva too.

- Arnaldo

#7 lore raw

Hi,

Quoted 5 lines · Arnaldo Carvalho de Melo

Em Wed, Mar 19, 2003 at 10:42:07PM +0100, Arjan van de Ven escreveu:

Quoted 2 lines

I can't speak for the others, but Red Hat Linux uses the .bz2 files in kernel rpms

Conectiva too.

... and so does SuSE.

Regards,

Signature · 3 lines
Kurt Garloff  <[email protected]>                          Eindhoven, NL
GPG key: See mail header, key servers                 SuSE Labs (Head)
SuSE Linux AG, Nuernberg, DE                            SCSI, Security
#27 lore raw
In reply to H. Peter Anvin
Quoted 5 lines · H. Peter Anvin

Hello everyone,

At some point it probably would make sense to start deprecating .gz format files from kernel.org.

OK, there seems to be enough resistance to this to put it off for a year or two. Since that means I don't have to do any work, that plan has inherent appeal to me.

In other words, the current setup will remain for now. HOWEVER, I would like to recommend that mirror sites start carrying .bz2 files if they want to carry only one format.

-hpa

#8 lore raw
In reply to Kurt Garloff
Quoted 11 lines · Kurt Garloff

Hi,

Quoted 5 lines · Arnaldo Carvalho de Melo

Em Wed, Mar 19, 2003 at 10:42:07PM +0100, Arjan van de Ven escreveu:

Quoted 1 line

I can't speak for the others, but Red Hat Linux uses the .bz2 files

in kernel rpms

Conectiva too.

... and so does SuSE.

And Source Mage (http://www.sourcemage.org). :)

-Sandalle

Signature · 7 lines
PGP Key 0x5C8D199A5A317214
http://search.keyserver.net:11371/pks/lookup?op=get&search=0x5A317214

Eric Sandall                     |  Source Mage GNU/Linux Developer
[email protected]                  |  http://www.sourcemage.org/
http://eric.sandall.us/          |  SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/  #196285  |  http://www.shock.wsu.edu/
#29 lore raw
In reply to a message not in the archive
Quoted 4 lines · Matt Critcher

now, since Nov, here are these same results --

Quoted 9 lines
.bz --  26815  == 52.6%
.gz --  24206  == 47.4%

again, i can only assume that these ratios are the fairly close throughout the ftp.us mirrors.

maybe we can watch these ratios for the next year or so and see how it changes....

Sounds like a plan. I have posted the recommendation that if you carry only one format, please carry .bz2.

-hpa

#32 lore raw
In reply to H. Peter Anvin

From: "H. Peter Anvin" <[email protected]>
Date: Wed, 19 Mar 2003 12:19:42 -0800

Now, the questions that come up are:

i) Does this sound reasonable to everyone? In particular, is there any loss in losing the "original" compressed files?

ii) Assuming a yes on the previous question, what time frame would it make sense for this changeover to happen over?

I'm fine with this, and my personal feeling on time is the sooner the better.

It's pretty hard to find a Linux system without bzip2 these days.

#13 lore raw
In reply to Tigran Aivazian
Quoted 2 lines · H. Peter Anvin

i) Does this sound reasonable to everyone? In particular, is there any loss in losing the "original" compressed files?

Personally I fetch the .bz2 tar files for a few base kernel versions, but I fetch the .gz patch files.

This is so that I can "zgrep" through the patch files looking for which version changed some feature or API.

bzgrep exists, but it is way too slow.

So if there were only .bz2 patch files, I would fetch them and convert them back into .gz files on my local mirror.

Which is ok of course, but then the signatures don't match any more.

Well, that's my really weak reason for liking .gz patches.

enjoy,
-- Jamie

#30 lore raw
In reply to H. Peter Anvin
Quoted 7 lines

OK, there seems to be enough resistance to this to put it off for a year or two. Since that means I don't have to do any work, that plan has inherent appeal to me.

In other words, the current setup will remain for now. HOWEVER, I would like to recommend that mirror sites start carrying .bz2 files if they want to carry only one format.

Can we at least switch the default upload format to bz2? I would think that's a reasonably simple change to the robot? For those of us uploading stuff over a slow modem link, the extra efficiency would be much appreciated.

M.

#31 lore raw
Quoted 9 lines · Martin J. Bligh
Quoted 7 lines

OK, there seems to be enough resistance to this to put it off for a year or two. Since that means I don't have to do any work, that plan has inherent appeal to me.

In other words, the current setup will remain for now. HOWEVER, I would like to recommend that mirror sites start carrying .bz2 files if they want to carry only one format.

Quoted 5 lines

Can we at least switch the default upload format to bz2? I would think that's a reasonably simple change to the robot? For those of us uploading stuff over a slow modem link, the extra efficiency would be much appreciated.

No, I don't want to muck with working scripts. I suggest setting up a script to upload to the /staging area and convert automatically. I have put a script called bz2togz in /usr/local/bin to help out.

-hpa

#10 lore raw
Quoted 5 lines · Thierry Vignaud
Quoted 3 lines · Eric Sandall
Quoted 3 lines
Quoted 3 lines
Quoted 2 lines

I can't speak for the others, but Red Hat Linux uses the .bz2 files in kernel rpms

Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
Quoted 1 line

Conectiva too.

... and so does SuSE.

And Source Mage (http://www.sourcemage.org). :)

mandrake too ...

Debian as well.

Signature · 1 line
ilmari
#33 lore raw
In reply to H. Peter Anvin
Quoted 2 lines

At some point it probably would make sense to start deprecating .gz format files from kernel.org.

Presumably the idea is to save bandwidth. In that case, it might be simpler to add:

<h1>.gz is depreciated and will be removed soon!</h1> Please start using .bz2 immediately. .gz downloads are rate limited to 5kbps.

to index.html :-).

Seriously, there are occasions when you're patching a kernel on a 486 or something, that it's quicker to use the .gz than the .bz2, even including the download time, (if you're on a fast connection). However, there are probably a lot of people downloading .gz, because they don't know what .bz2 is.

Likewise, http access to kernel.org is frequently slow, whereas ftp access can use 100% of my link, simply because many more people use http.

One other thing that occurs to me, the send your e-mail address as anonymous password requirement means I can't use wget to access the ftp site, (I think - the user:password@host syntax seems to confuse it, when it's anonymous:me@[email protected]).

John.

#36 lore raw
In reply to H. Peter Anvin

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 2 lines · H. Peter Anvin

At some point it probably would make sense to start deprecating .gz format files from kernel.org.

[...]

I think it may be better to dump the .gz format for 2.5 and the forthcoming 2.6 series in favour of .bz2. Keep .gz for 2.[0-4] for those who need it (I certainly don't).

- --
Erik Hensema <[email protected]>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+eZINuNWfqpFSu/cRAkJfAJ9LNq+2krlpaU9PTNE0m0pVgMtgngCg+L8G FT6d5flYtelPMNCoEvoZQTY=
=MUhg
-----END PGP SIGNATURE-----

#12 lore raw
In reply to Kurt Garloff
Quoted 9 lines · Kurt Garloff
Quoted 5 lines · Arnaldo Carvalho de Melo

Em Wed, Mar 19, 2003 at 10:42:07PM +0100, Arjan van de Ven escreveu:

Quoted 2 lines

I can't speak for the others, but Red Hat Linux uses the .bz2 files in kernel rpms

Conectiva too.

... and so does SuSE.

... and so does MandrakeSoft (as it seems from their rpm).

Signature · 4 lines
Linux Solution Consultant         Tél: +33 476 143 278 - Fax: +33 476 146 105
HP/Intel Solution Center http://hpintelco.net Hewlett-Packard Grenoble/France
Des infos sur Linux?  http://www.HyPer-Linux.org      http://www.hp.com/linux
La musique ancienne?  http://www.musique-ancienne.org http://www.medieval.org
#34 lore raw
In reply to John Bradford

Among the latest 2.4-release kernels (2.4.19 and 2.4.20), it seems that bz2 saves ~6MB.

Downloads: 1.5MB DSL

time ncftpget ftp://ftp.kernel.org/pub/linux/kernel/v2.4/linux-2.4.20.tar.gz
real 3m24.004s
<snipped>

time ncftpget ftp://ftp.kernel.org/pub/linux/kernel/v2.4/linux-2.4.20.tar.bz2
real 2m51.481s
<snipped>

Uncompression: Dual AMD 1600+, 512MB ram, 30 GB seagate EIDE time gunzip linux-2.4.20.tar.gz

real    0m5.428s
user    0m2.285s
sys     0m1.096s

time bunzip2 linux-2.4.20.tar.bz2

real    0m28.892s
user    0m27.318s
sys     0m1.363s

Compression: Dual AMD 1600+, 512MB ram, 30 GB seagate EIDE time gzip linux-2.4.20.tar

real    0m18.771s
user    0m17.990s
sys     0m0.674s

time gzip -9 linux-2.4.20.tar

real    0m42.032s
user    0m40.725s
sys     0m0.791s

time bzip2 linux-2.4.20.tar

real    1m50.411s
user    1m49.197s
sys     0m0.555s

bz2 is about 18% of the size of the tarfile. gz is 22%. gzip -9 saved a whopping 310k compared to gzip.

Signature · 2 lines
-- John E. Jasen ([email protected])
-- User Error #2361: Please insert coffee and try again.
#35 lore raw
Quoted 41 lines · John Jasen

Among the latest 2.4-release kernels (2.4.19 and 2.4.20), it seems that bz2 saves ~6MB.

Downloads: 1.5MB DSL

time ncftpget ftp://ftp.kernel.org/pub/linux/kernel/v2.4/linux-2.4.20.tar.gz
real 3m24.004s
<snipped>

time ncftpget ftp://ftp.kernel.org/pub/linux/kernel/v2.4/linux-2.4.20.tar.bz2
real 2m51.481s
<snipped>

Uncompression: Dual AMD 1600+, 512MB ram, 30 GB seagate EIDE time gunzip linux-2.4.20.tar.gz

real    0m5.428s
user    0m2.285s
sys     0m1.096s

time bunzip2 linux-2.4.20.tar.bz2

real    0m28.892s
user    0m27.318s
sys     0m1.363s

Compression: Dual AMD 1600+, 512MB ram, 30 GB seagate EIDE time gzip linux-2.4.20.tar

real    0m18.771s
user    0m17.990s
sys     0m0.674s

time gzip -9 linux-2.4.20.tar

real    0m42.032s
user    0m40.725s
sys     0m0.791s

time bzip2 linux-2.4.20.tar

real    1m50.411s
user    1m49.197s
sys     0m0.555s
Quoted 7 lines

bz2 is about 18% of the size of the tarfile. gz is 22%. gzip -9 saved a whopping 310k compared to gzip.

--
-- John E. Jasen ([email protected])
-- User Error #2361: Please insert coffee and try again.

Simple question. Has anybody provided a modified tar that will properly extract tar -xzf ... without having to determine ahead of time if it's a bz2 or gzip file? If not, you will obsolete bz(2)illions of scripts that are in use for automatic functions world-wide.

If tar will filter through past, present, and future compression programs without human intervention, then you can get rid of anything you want. But, until this is done, you need to leave the "past" alone. There are many machines that get and install stuff from tapes and home-brew CDs. They may not even have 'bz' stuff. Right now you have to modify scripts to use tar -xjf after parsing the file-type to check its name and,

      |______ Dumb, doesn't make any sense.

some working systems don't even have bzip2 and are not connected to the Internet.

Last year, I was in Kuala Lumpur, Malaysia (a nice modern city). My company sent me a new CD to install a software update on a 3-year old system. The compression was in "@$^_@%" bz format. There was no such thing on that machine. I had to buy some "Distribution" and waste time finding out how to extract the bzip2 stuff from the CD/ROM. Not easy to do when the Distribution CD/ROM was designed to install a complete operating system.

So my advise is to let the past slowly die away. Do not convert any older distributions into something new. Leave them alone. Make sure that any new distribution has the tools to handle the old stuff and the next stuff. Then you can't go wrong.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips). Why is the government concerned about the lunatic fringe? Think about it.

#20 lore raw
In reply to Tigran Aivazian
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"tigran" == Tigran Aivazian <[email protected]> writes:

Quoted 2 lines · H. Peter Anvin
Quoted 2 lines

i) Does this sound reasonable to everyone? In particular, is there any loss in losing the "original" compressed files?

tigran> No, there is at least one reason for the "original" .gz files. Here are tigran> the logical steps:

tigran> a) any Linux distribution contains their own "linux" package with the tigran> source base being "vanilla" Linux .tar.gz file

Mandrake also use .bz2 since ages ago.

Later, Juan.

Signature · 2 lines
In theory, practice and theory are the same, but in practice they 
are different -- Larry McVoy
#11 lore raw
In reply to Dagfinn Ilmari Mannsåker
Quoted 9 lines · On Thu, 20 Mar 2003, Dagfinn Ilmari [iso-8859-1] Manns�ker wrote:
Quoted 7 lines · Thierry Vignaud
Quoted 5 lines · Eric Sandall
Quoted 5 lines
Quoted 4 lines
Quoted 2 lines

I can't speak for the others, but Red Hat Linux uses the .bz2 files in kernel rpms

Conectiva too.

Quoted 8 lines
Quoted 5 lines
Quoted 3 lines
Quoted 1 line

... and so does SuSE.

And Source Mage (http://www.sourcemage.org). :)

mandrake too ...

Debian as well.

And Gentoo :-)

#37 lore raw
In reply to H. Peter Anvin

On Wed, 2003-03-19 12:19:42 -0800, H. Peter Anvin <[email protected]> wrote in message <[email protected]>:

Quoted 4 lines

Hello everyone,

At some point it probably would make sense to start deprecating .gz format files from kernel.org.

However, please keep in mind that it's a *PITA* if you're working on a machine with not > 500MHz and > 128MB RAM:

jbglaw@schnarchnase:/tmp$ ls -l linux-2.5.65.tar.*
-rw-r--r--    1 jbglaw   jbglaw   31889910 Mar 20 11:37
linux-2.5.65.tar.bz2
-rw-r--r--    1 jbglaw   jbglaw   39711645 Mar 20 11:44
linux-2.5.65.tar.gz
jbglaw@schnarchnase:/tmp$ time tar xjf linux-2.5.65.tar.bz2
real    194m21.665s
user    172m55.026s
sys     14m19.018s
jbglaw@schnarchnase:/tmp$ mv linux-2.5.65 linux-2.5.65xx
jbglaw@schnarchnase:/tmp$ time tar xzf linux-2.5.65.tar.gz
real    39m39.294s
user    22m32.306s
sys     13m56.524s
jbglaw@schnarchnase:/tmp$ free
             total       used       free     shared    buffers     cached
Mem:         10100       9792        308          0        952       5232
-/+ buffers/cache:       3608       6492
Swap:       292816       1484     291332
jbglaw@schnarchnase:/tmp$ cat /proc/cpuinfo 
processor       : 0
vendor_id       : UMC UMC UMC 
cpu family      : 4
model           : 2
model name      : ff/02
stepping        : 3
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : no
fpu_exception   : no
cpuid level     : 1
wp              : yes
flags           :
bogomips        : 15.10
jbglaw@schnarchnase:/tmp$ uname -a
Linux schnarchnase 2.5.65 #1 Thu Mar 20 07:39:11 CET 2003 i486 unknown unknown GNU/Linux

MfG, JBG

Signature · 4 lines
   Jan-Benedict Glaw       [email protected]    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));
#38 lore raw
Quoted 3 lines · Jan-Benedict Glaw
jbglaw@schnarchnase:/tmp$ cat /proc/cpuinfo

bogomips : 15.10

out of curiosity, how long does the machine take to compile a kernel?

Do you use a stopwatch or a calendar?

Mike

#14 lore raw
In reply to Jamie Lokier

Jamie Lokier said:
<snip>

Quoted 1 line

Which is ok of course, but then the signatures don't match any more.

<snip>

Quoted 1 line

-- Jamie

Why not get the signature from the .tar file, that way the compression method doesn't matter? This is how Source Mage does it's checking, we create and md5sum (and soon GPG) signature based on the uncompressed .tar file. This way, you can use any compression you want, even changing around the compression to your favourite one, and the signatures will always match. :)

-Sandalle

Signature · 7 lines
PGP Key 0x5C8D199A5A317214
http://search.keyserver.net:11371/pks/lookup?op=get&search=0x5A317214

Eric Sandall                     |  Source Mage GNU/Linux Developer
[email protected]                  |  http://www.sourcemage.org/
http://eric.sandall.us/          |  SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/  #196285  |  http://www.shock.wsu.edu/
#50 lore raw
In reply to Jan-Benedict Glaw

On Thu, 20 Mar 2003 17:32:07 +0100 Jan-Benedict Glaw <[email protected]> wrote:

| However, please keep in mind that it's a *PITA* if you're working on a
| machine with not > 500MHz and > 128MB RAM:
| 
| jbglaw@schnarchnase:/tmp$ ls -l linux-2.5.65.tar.*
| -rw-r--r--    1 jbglaw   jbglaw   31889910 Mar 20 11:37
| linux-2.5.65.tar.bz2
| -rw-r--r--    1 jbglaw   jbglaw   39711645 Mar 20 11:44
| linux-2.5.65.tar.gz
| jbglaw@schnarchnase:/tmp$ time tar xjf linux-2.5.65.tar.bz2
| 
| real    194m21.665s
| user    172m55.026s
| sys     14m19.018s
| jbglaw@schnarchnase:/tmp$ mv linux-2.5.65 linux-2.5.65xx
| jbglaw@schnarchnase:/tmp$ time tar xzf linux-2.5.65.tar.gz
| 
| real    39m39.294s
| user    22m32.306s
| sys     13m56.524s
| jbglaw@schnarchnase:/tmp$ free
|              total       used       free     shared    buffers     cached
| Mem:         10100       9792        308          0        952       5232
...
| jbglaw@schnarchnase:/tmp$ cat /proc/cpuinfo 
...
| bogomips        : 15.10
| 
| jbglaw@schnarchnase:/tmp$ uname -a
| Linux schnarchnase 2.5.65 #1 Thu Mar 20 07:39:11 CET 2003 i486 unknown unknown GNU/Linux

What kind of processor/system is that?

I also see quite a difference in untarring gz vs. bz2.

On a Pentium classic with genuine f00f bug, 180 Mhz, 80 MB of RAM, running Linux 2.5.64, I get:

[rddunlap@eeyore linsrc]$ time tar xzf linux-2.5.65.tar.gz 41.98user 38.15system 1:45.94elapsed 75%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (314major+97minor)pagefaults 0swaps [rddunlap@eeyore linsrc]$ mv linux-2.5.65 linux-2565

[rddunlap@eeyore linsrc]$ time tar xjf linux-2.5.65.tar.bz2 243.99user 39.62system 5:29.39elapsed 86%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (324major+971minor)pagefaults 0swaps

--
~Randy

#15 lore raw
In reply to Eric Sandall
Quoted 4 lines · Eric Sandall

Jamie Lokier said:
<snip>

Quoted 1 line

Which is ok of course, but then the signatures don't match any more.

<snip>

Quoted 8 lines
Quoted 1 line

-- Jamie

Why not get the signature from the .tar file, that way the compression method doesn't matter? This is how Source Mage does it's checking, we create and md5sum (and soon GPG) signature based on the uncompressed .tar file. This way, you can use any compression you want, even changing around the compression to your favourite one, and the signatures will always match. :)

(a) I use .gz for the patches not the tar files. But your point still applies.

(b) On something as large as a .tar, decompressing a bz2 file to check the signature is really quite slow, compared with checking the signature of the compressed file.

-- Jamie

#52 lore raw
In reply to Jan-Benedict Glaw
Quoted 11 lines

[[email protected]]

On Wed, 2003-03-19 12:19:42 -0800, H. Peter Anvin <[email protected]> wrote in message <[email protected]>:

Quoted 4 lines

Hello everyone,

At some point it probably would make sense to start deprecating .gz format files from kernel.org.

However, please keep in mind that it's a *PITA* if you're working on a machine with not > 500MHz and > 128MB RAM:

Well, you see, hpa probably made a mistake in his original proposal.

Likely he meant to say he intended to deprecate bz2 and was about to introduce lzo instead. ;)

Signature · 1 line
Tomas Szepe <[email protected]>
#39 lore raw
In reply to Mike Dresser
Quoted 6 lines · Mike Dresser
Quoted 1 line · Jan-Benedict Glaw
jbglaw@schnarchnase:/tmp$ cat /proc/cpuinfo
Quoted 6 lines
Quoted 1 line

bogomips : 15.10

out of curiosity, how long does the machine take to compile a kernel?

Do you use a stopwatch or a calendar?

Well, going back to his original email,

jbglaw@schnarchnase:/tmp$ uname -a
Linux schnarchnase 2.5.65 #1 Thu Mar 20 07:39:11 CET 2003 i486 unknown unknown GNU/Linux

And looking on kernel.org,
Mar 17 22:29 linux-2.5.65.tar.gz

It takes him less than a week anyway*... ;) (Timezone conversions left as an exercise to the reader.)

So, who can beat his 15.10 bogomips? Anyone run <1 bogomips?

*grin*

Eli

* Yes, I know he could be doing patches and incremental builds. --------------------. "If it ain't broke now,
Eli Carter \ it will be soon." -- crypto-gram
eli.carter(a)inet.com `-------------------------------------------------

#53 lore raw
In reply to Tomas Szepe
Quoted 4 lines · Tomas Szepe

Well, you see, hpa probably made a mistake in his original proposal.

Likely he meant to say he intended to deprecate bz2 and was about to introduce lzo instead. ;)

LZO rocks!

It's got my vote :)

--
Dana Lacoste
Ottawa, Canada

#16 lore raw
In reply to Jamie Lokier
Quoted 14 lines · Jamie Lokier
Quoted 4 lines · Eric Sandall

Jamie Lokier said:
<snip>

Quoted 1 line

Which is ok of course, but then the signatures don't match any more.

<snip>

Quoted 8 lines
Quoted 1 line

-- Jamie

Why not get the signature from the .tar file, that way the compression method doesn't matter? This is how Source Mage does it's checking, we create and md5sum (and soon GPG) signature based on the uncompressed .tar file. This way, you can use any compression you want, even changing around the compression to your favourite one, and the signatures will always match. :)

Quoted 8 lines

(a) I use .gz for the patches not the tar files. But your point still applies.

(b) On something as large as a .tar, decompressing a bz2 file to check the signature is really quite slow, compared with checking the
signature of the compressed file.

-- Jamie

True...for large files it'd be nice to know if you have the correct tarball _before_ spending all that CPU time decompressing it. It's a trade off, mostly, CPU time for more generic useage. I know this isn't the Right Way(TM), but since fast computers are becoming fairly cheap, I say the signature on the .tar file is a good way to go. However, Linux also runs sufficiently well on slow machines, and this would just make them slower. Shall we just follow the path of least resistence and keep it as is?

-Sandalle

Signature · 7 lines
PGP Key 0x5C8D199A5A317214
http://search.keyserver.net:11371/pks/lookup?op=get&search=0x5A317214

Eric Sandall                     |  Source Mage GNU/Linux Developer
[email protected]                  |  http://www.sourcemage.org/
http://eric.sandall.us/          |  SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/  #196285  |  http://www.shock.wsu.edu/
#40 lore raw
In reply to Eli Carter
Quoted 1 line · Eli Carter

So, who can beat his 15.10 bogomips?

my firewall:

[tduffy@crackho ~]$ more /proc/cpuinfo
processor : 0
vendor_id : unknown
cpu family : 4
model : 0
model name : 486
stepping : unknown
fdiv_bug : no
hlt_bug : no
sep_bug : no
f00f_bug : no
coma_bug : no
fpu : no
fpu_exception : no
cpuid level : -1
wp : yes
flags :
bogomips : 12.44

Signature · 1 line
YOO-ESS-AYE! YOO-ESS-AYE!
#45 lore raw
In reply to Eli Carter

On Thu, 2003-03-20 11:51:41 -0600, Eli Carter <[email protected]> wrote in message <[email protected]>:

Quoted 20 lines
Quoted 6 lines · Mike Dresser
Quoted 1 line · Jan-Benedict Glaw
jbglaw@schnarchnase:/tmp$ cat /proc/cpuinfo
Quoted 6 lines
Quoted 1 line

bogomips : 15.10

out of curiosity, how long does the machine take to compile a kernel?

Do you use a stopwatch or a calendar?

Well, going back to his original email,

jbglaw@schnarchnase:/tmp$ uname -a
Linux schnarchnase 2.5.65 #1 Thu Mar 20 07:39:11 CET 2003 i486 unknown 
unknown GNU/Linux
Quoted 5 lines

And looking on kernel.org,
Mar 17 22:29 linux-2.5.65.tar.gz

It takes him less than a week anyway*... ;) (Timezone conversions left as an exercise to the reader.)

Um, no. I compiled it on my Athlon (2x1.4GHz) and that's more like 5min... Letting the box compile a full 2.5.x (with mostly anything useable choosen as a module), I think that would be at about 10..20 day. So it's more like looking at a calendar than looking at a stopwatch:=

Quoted 1 line

So, who can beat his 15.10 bogomips? Anyone run <1 bogomips?

No problem - start linux from within bochs:)

Signature · 4 lines
   Jan-Benedict Glaw       [email protected]    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));
#51 lore raw
In reply to Randy.Dunlap

On Thu, 2003-03-20 09:23:34 -0800, Randy.Dunlap <[email protected]> wrote in message <[email protected]>:

Quoted 32 lines · On Thu, 20 Mar 2003 17:32:07 +0100 Jan-Benedict Glaw <[email protected]> wrote:
| However, please keep in mind that it's a *PITA* if you're working on a
| machine with not > 500MHz and > 128MB RAM:
| 
| jbglaw@schnarchnase:/tmp$ ls -l linux-2.5.65.tar.*
| -rw-r--r--    1 jbglaw   jbglaw   31889910 Mar 20 11:37
| linux-2.5.65.tar.bz2
| -rw-r--r--    1 jbglaw   jbglaw   39711645 Mar 20 11:44
| linux-2.5.65.tar.gz
| jbglaw@schnarchnase:/tmp$ time tar xjf linux-2.5.65.tar.bz2
| 
| real    194m21.665s
| user    172m55.026s
| sys     14m19.018s
| jbglaw@schnarchnase:/tmp$ mv linux-2.5.65 linux-2.5.65xx
| jbglaw@schnarchnase:/tmp$ time tar xzf linux-2.5.65.tar.gz
| 
| real    39m39.294s
| user    22m32.306s
| sys     13m56.524s
| jbglaw@schnarchnase:/tmp$ free
|              total       used       free     shared    buffers     cached
| Mem:         10100       9792        308          0        952       5232
...
| jbglaw@schnarchnase:/tmp$ cat /proc/cpuinfo 
...
| bogomips        : 15.10
| 
| jbglaw@schnarchnase:/tmp$ uname -a
| Linux schnarchnase 2.5.65 #1 Thu Mar 20 07:39:11 CET 2003 i486 unknown unknown GNU/Linux
Quoted 1 line

What kind of processor/system is that?

It's a UMC chip - a i486 clone without FPU. (I thought that this chip was an i386 clone but uname tells me different so I believe it.)

However, I've got two early i386 (original Intel brand) laying around and I'm definitely like installing Linux on them, just to see it running:-)

MfG, JBG

Signature · 4 lines
   Jan-Benedict Glaw       [email protected]    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));
#54 lore raw
In reply to Dana Lacoste
Quoted 11 lines

[[email protected]]

Quoted 4 lines · Tomas Szepe

Well, you see, hpa probably made a mistake in his original proposal.

Likely he meant to say he intended to deprecate bz2 and was about to introduce lzo instead. ;)

LZO rocks!

It's got my vote :)

Yeah, lzo{,p} makes my good old sparc32s feel like gigahertz monsters. :)

Signature · 1 line
Tomas Szepe <[email protected]>
#55 lore raw
In reply to H. Peter Anvin
Quoted 4 lines · H. Peter Anvin

Hello everyone,

At some point it probably would make sense to start deprecating .gz format files from kernel.org.

When I started mirroring kernel.org, I was under the assumption that most of the world was still using .gz for the most part, and we are under a space constraint that prevents us from having both formats (this will change once we get the new server for OSS mirrors up and running). However, Matt's stats are pretty interesting. So even though we probably won't be depricating .gz right now, I've switched over my mirror from .gz to .bz2. Peter, mark me (RN-RNO) down as converted.

Now, if only GNU tar would read .gz OR .bz2 format when specifying -z (my fingers automatically type "tar zxvf", and it will take a long time to change that. What is bz2? j? That's too hard to remember.)

Signature · 6 lines
Ryan Finnie
Senior System Administrator
Redundant Networks
[email protected]
775-850-4222 x2222
775-771-4472 (Cell)
#56 lore raw
Quoted 8 lines · Ryan Finnie

When I started mirroring kernel.org, I was under the assumption that
most of the world was still using .gz for the most part, and we are
under a space constraint that prevents us from having both formats (this
will change once we get the new server for OSS mirrors up and running). However, Matt's stats are pretty interesting. So even though we probably won't be depricating .gz right now, I've switched over my
mirror from .gz to .bz2. Peter, mark me (RN-RNO) down as converted.

Quoted 4 lines

Now, if only GNU tar would read .gz OR .bz2 format when specifying -z (my fingers automatically type "tar zxvf", and it will take a long time to change that. What is bz2? j? That's too hard to remember.)

Yes, for decode it should be able to spawn the right program by looking at the magic number. For encode, well, of course it needs to know. But yes, it's "j".

-hpa

#17 lore raw
In reply to Jamie Lokier
Quoted 9 lines · Jamie Lokier
Quoted 7 lines · Eric Sandall

Why not get the signature from the .tar file, that way the compression method doesn't matter? This is how Source Mage does it's checking, we create and md5sum (and soon GPG) signature based on the uncompressed .tar file. This way, you can use any compression you want, even changing around the compression to your favourite one, and the signatures will always match. :)

Quoted 3 lines

(b) On something as large as a .tar, decompressing a bz2 file to check the signature is really quite slow, compared with checking the signature of the compressed file.

That shouldn't matter, most of the times. If you want to build the code, you have to [bg]unzip anyway, so there is no extra cost. And I have a hard time to think of a real-world application where you don't want to unpack but need to verify the signature.

Jörn

Signature · 4 lines
If System.PrivateProfileString("",
"HKEY_CURRENT_USER\Software\Microsoft\Office\9.0\Word\Security", "Level") <>
"" Then  CommandBars("Macro").Controls("Security...").Enabled = False
-- from the Melissa-source
#22 lore raw
In reply to Sam Ravnborg
Quoted 5 lines · Sam Ravnborg

It is a convinient feature that I can download the kernel now and then when at work (no linux) - and it makes it a bit simpler to use an archiver that has native support for the format used. Winzip, being the only allowed archiver at work, does not have native bz2 support.

----
I asked WinZip for plugin support so users could add
arbitrary compressions formats (I specifically mentioned 'bz2').
I even offered to do it myself if they wanted to give me NDA access
to the code.... and was told that they have thought about
extensibility but had no plans to support it in the forseeable
future. Consider it a benefit of a closed source product.
They control your file format, they control your business and personal decisions...nice.

Anyone up for writing a Free version of Winzip to replace
the "cooperative" Winzip authors' version (was was up for making minor mod's, but not starting from scratch).

-linda

#23 lore raw

[Removing the mirrors list from this since I have to manually approve everything...]+

Quoted 9 lines · LA Walsh

I asked WinZip for plugin support so users could add
arbitrary compressions formats (I specifically mentioned 'bz2').
I even offered to do it myself if they wanted to give me NDA access
to the code.... and was told that they have thought about
extensibility but had no plans to support it in the forseeable
future. Consider it a benefit of a closed source product.
They control your file format, they control your business and personal decisions...nice.

Quoted 4 lines

Anyone up for writing a Free version of Winzip to replace
the "cooperative" Winzip authors' version (was was up for making minor mod's, but not starting from scratch).

WinME and WinXP has something called compressed folder support... they treat .zip files as containers right in the desktop UI.

Perhaps *that* has some kind of plugin architecture?

-hpa

#24 lore raw
In reply to LA Walsh
Quoted 10 lines · LA Walsh

----
I asked WinZip for plugin support so users could add
arbitrary compressions formats (I specifically mentioned 'bz2'). I even offered to do it myself if they wanted to give me NDA access to the code.... and was told that they have thought about extensibility but had no plans to support it in the forseeable future. Consider it a benefit of a closed source product. They control your file format, they control your business and personal decisions...nice.

Quoted 5 lines

Anyone up for writing a Free version of Winzip to replace
the "cooperative" Winzip authors' version (was was up for making minor mod's, but not starting from scratch).

-linda

FYI, WinRAR (http://www.rarsoft.com) supports BZ2 files. ;)

-Sandalle

Signature · 7 lines
PGP Key 0x5C8D199A5A317214
http://search.keyserver.net:11371/pks/lookup?op=get&search=0x5A317214

Eric Sandall                     |  Source Mage GNU/Linux Developer
[email protected]                  |  http://www.sourcemage.org/
http://eric.sandall.us/          |  SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/  #196285  |  http://www.shock.wsu.edu/
#25 lore raw
Quoted 16 lines

-----Original Message-----
From: [email protected] [mailto:[email protected]]On Behalf Of Eric Sandall
Sent: Thursday, March 20, 2003 6:10 PM
To: [email protected]
Subject: RE: Deprecating .gz format on kernel.org

Quoted 4 lines · LA Walsh

----
I asked WinZip for plugin support so users could add
arbitrary compressions formats (I specifically mentioned 'bz2'). I even offered to do it myself if they wanted to give me

NDA access to

Quoted 4 lines

the code.... and was told that they have thought about extensibility but had no plans to support it in the forseeable future. Consider it a benefit of a closed source product. They control your file format, they control your business

Quoted 8 lines

and personal

Quoted 5 lines

decisions...nice.
Anyone up for writing a Free version of Winzip to replace
the "cooperative" Winzip authors' version (was was up for making minor mod's, but not starting from scratch).
-linda

FYI, WinRAR (http://www.rarsoft.com) supports BZ2 files. ;) -Sandalle

But, WinRAR doesn't handle symlinks.

--

/"\ / For information and quotes, email us at

 \ /  ASCII RIBBON CAMPAIGN / [email protected]
  X   AGAINST HTML MAIL    / http://www.lrsehosting.com/
 / \  AND POSTINGS        / [email protected]

-------------------------------------------------------------------------

#26 lore raw

[email protected] said:
<snip>

Quoted 1 line

But, WinRAR doesn't handle symlinks.

True...hence an argument how OpenSource software is better. ;) Not that I need to argue that here, and not all OS is better than closed, but it is easier to get what you want.

Perhaps someone with the knowledge (certainly not I) could write a GPL'd unarchiver (with GUI, since Windows folks like those) that can handle .gz, .bz2, .zip, .lzo, etc. files?

-Sandalle

Signature · 7 lines
PGP Key 0x5C8D199A5A317214
http://search.keyserver.net:11371/pks/lookup?op=get&search=0x5A317214

Eric Sandall                     |  Source Mage GNU/Linux Developer
[email protected]                  |  http://www.sourcemage.org/
http://eric.sandall.us/          |  SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/  #196285  |  http://www.shock.wsu.edu/
#57 lore raw
In reply to H. Peter Anvin

Hi HPA :)

H. Peter Anvin dixit:

Quoted 2 lines

At some point it probably would make sense to start deprecating .gz format files from kernel.org.

Just one point: while with kernel sources the space saving is
notable using .bz2 instead of .gz, in my experience with different files, formats, etc... the saving is negligible and the speed just sucks, gzip beats bzip2 for me in general.

Anyway I think bzip2 is standard nowadays.

Quoted 2 lines

i) Does this sound reasonable to everyone? In particular, is there any loss in losing the "original" compressed files?

IMHO, just the decompression speed. I've made no tests, but if
the kernel sources behave like other archives I have, .gz is faster. OTOH, you save a few megs for downloading, and this is *very* important too.

Raúl Núñez de Arenas Coronado

Signature · 2 lines
Linux Registered User 88736
http://www.pleyades.net & http://www.pleyades.net/~raulnac
#46 lore raw
In reply to Eli Carter
Quoted 1 line · Eli Carter

So, who can beat his 15.10 bogomips? Anyone run <1 bogomips?

The normal systems I develop for have 4-6 bogomips (NEC V850E/MA1 @50MHz).

For debugging I often run linux on gdb's simulator, which probably has somewhere under 1 bogomips (the number reported is not correct because I have to lie to the kernel about the clock interrupt rate, as it can't handle the real value). It's still quite usable interactively though (actually 2.5.x feels noticably better than 2.4.x in this situation)...

-Miles

Signature · 1 line
97% of everything is grunge
#47 lore raw
Quoted 1 line · Miles Bader

The normal systems I develop for have 4-6 bogomips (NEC V850E/MA1 @50MHz).

BTW, this system has no cache, and I think about 3 wait-states on normal memory access.

-Miles

Signature · 2 lines
"Whatever you do will be insignificant, but it is very important that
 you do it."  Mahatma Ghandi
#48 lore raw
In reply to Miles Bader

I can get down to somewhere around 2... (Mips R5k w/ no l2 cache... painfull) why? I appear to have missed the start of this thread
Nick

Quoted 20 lines · Miles Bader
Quoted 1 line · Eli Carter

So, who can beat his 15.10 bogomips? Anyone run <1 bogomips?

The normal systems I develop for have 4-6 bogomips (NEC V850E/MA1 @50MHz).

For debugging I often run linux on gdb's simulator, which probably has somewhere under 1 bogomips (the number reported is not correct because I have to lie to the kernel about the clock interrupt rate, as it can't handle the real value). It's still quite usable interactively though (actually 2.5.x feels noticably better than 2.4.x in this situation)...

-Miles

Signature · 6 lines
97% of everything is grunge
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
#49 lore raw
In reply to Eli Carter

On Thu, 2003-03-20 11:51:41 -0600, Eli Carter <[email protected]> wrote in message <[email protected]>:

Quoted 9 lines
Quoted 6 lines · Mike Dresser
Quoted 4 lines · Jan-Benedict Glaw
jbglaw@schnarchnase:/tmp$ cat /proc/cpuinfo

bogomips : 15.10

So, who can beat his 15.10 bogomips? Anyone run <1 bogomips?

I've tested an Intel i386SX, 16MHz these days. It reached 1.19 Bogomips IIRC using 2.4.x.

As you may see, I'm currently collecting very different hardware (very old ia32 based systems as well as anything != ia32 capable of running Linux). My goal is to build an (automated) compile & boot farm of machines to detect major breakages _early_. In the past few years, we had quite some ups (and some really hard downs...) which I want to see:

- Remember SCSI-eh changes? Some drivers still need to be ported (or am I wrong here?)
- module-init-tools took quite some time...
- sparc32 unfortunately is not yet really running 2.5.x. 2.4.x doesn't do SMP for me (Level 15 Interrupt). However, here I do know when this was introduced and I'll have a look. Somewhen...
- ...

Things are easier to sort out as long as the breakages are _new_. If they're there for a year and nobody cares about fixing them, non-ia32 architectures might again be near being dropped (sun4?).

With some luck, I'll get some room (incl. power and IP connectivity) near Halle/Westf. (Germany). If this fails, I'd be _really_ interested in other offers here... "CRT - Compile and Run a Test"

MfG, JBG

Signature · 4 lines
   Jan-Benedict Glaw       [email protected]    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));
#18 lore raw
In reply to Jörn Engel
Quoted 4 lines · On Thu, 20 Mar 2003, [iso-8859-1] Jörn Engel wrote:

That shouldn't matter, most of the times. If you want to build the code, you have to [bg]unzip anyway, so there is no extra cost. And I have a hard time to think of a real-world application where you don't want to unpack but need to verify the signature.

My real world includes downloading a bunch of files and burning a CD to move them to a test environment which is completely private and has no external connections of any kind. I don't do all files that way, of course, but that is the way at least half of the 2.5 kernels I've used were moved to a machine which was non-production.

Signature · 3 lines
bill davidsen <[email protected]>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
#41 lore raw
In reply to Thomas Duffy
Quoted 15 lines · Thomas Duffy
Quoted 1 line · Eli Carter

So, who can beat his 15.10 bogomips?

my firewall:

[tduffy@crackho ~]$ more /proc/cpuinfo
processor : 0
vendor_id : unknown
cpu family : 4
model : 0
model name : 486
stepping : unknown
fdiv_bug : no
hlt_bug : no
sep_bug : no

Quoted 11 lines

f00f_bug : no
coma_bug : no
fpu : no
fpu_exception : no
cpuid level : -1
wp : yes
flags :
bogomips : 12.44

Signature · 1 line
YOO-ESS-AYE! YOO-ESS-AYE!

At one point I ran Linux on a 386SX-16 with 12MB. That machine ran 1.2.13 (IIRC) until Dec 31 1999, when I was afraid it was not Y2k hardened. I still see spam to glacial.tmr.com today. The name was NOT because it was so cool ;-)

I may still have that board, but I'm not about to put it back in service to measure speed. Your firewall is the slowest "real machine" I've seen, emulation and embedded machines are not really general purpose.

Signature · 3 lines
bill davidsen <[email protected]>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
#42 lore raw

On Tue, 2003-03-25 11:04:51 -0500, Bill Davidsen <[email protected]> wrote in message <[email protected]>:

Quoted 7 lines · Thomas Duffy
Quoted 5 lines · Eli Carter
Quoted 1 line

So, who can beat his 15.10 bogomips?

my firewall:

Quoted 7 lines

At one point I ran Linux on a 386SX-16 with 12MB. That machine ran 1.2.13 (IIRC) until Dec 31 1999, when I was afraid it was not Y2k hardened. I still see spam to glacial.tmr.com today. The name was NOT because it was so cool ;-)

I may still have that board, but I'm not about to put it back in service to measure speed. Your firewall is the slowest "real machine" I've seen,

I do have such a system, too (but only 4..8MB RAM) and I'm going to install it this evening (or tomorrow). I've just got back a 40GB HDD from IBM^WHitachi:) That box should have just about 1.2 BogoMips...

MfG, JBG

Signature · 4 lines
   Jan-Benedict Glaw       [email protected]    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));
#43 lore raw
In reply to Bill Davidsen
Quoted 5 lines · * Bill Davidsen ([email protected]) wrote:
Quoted 3 lines · Thomas Duffy
Quoted 1 line · Eli Carter

So, who can beat his 15.10 bogomips?

[...]

Quoted 10 lines
Quoted 1 line

bogomips : 12.44

At one point I ran Linux on a 386SX-16 with 12MB. That machine ran 1.2.13 (IIRC) until Dec 31 1999, when I was afraid it was not Y2k hardened. I still see spam to glacial.tmr.com today. The name was NOT because it was so cool ;-)

I may still have that board, but I'm not about to put it back in service to measure speed. Your firewall is the slowest "real machine" I've seen, emulation and embedded machines are not really general purpose.

If we're really curious...

sfrost@ns2:/home/sfrost> cat /proc/cpuinfo
processor : 0
vendor_id : unknown
cpu family : 4
model : 0
model name : 486
stepping : unknown
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : no
cpuid level : -1
wp : yes
flags :
bogomips : 9.42

This is my secondary name server. This was also after an upgrade from a 386 because bind9 is a bloody pig. :) To be honest I've thought about putting the 386 back in service as something else because unlike my web server and primary name server there's no chance a CPU fan on it is going to die causing a CPU to fry and the system to crash. At one point the 386 had a 630 day uptime, running 2.2.16.

Stephen

#44 lore raw

Re: Deprecating .gz format on kernel.org aka BogoMips

Hi All,

Your little BogoMips "contest" made me curious..:-) I've build a ELKS Kernel for my old 8088 PC. After some trouble with booting and root disks I can tell you the result now:

In "Turbo";-) mode I got 0.64 BogoMips (~8Mhz)
In "Normal" mode I got 0.37 BogoMips (~4Mhz)

Have you ever seen such a fast machine? :-))

greets

Marc

Quoted 47 lines · On Tue, 25 Mar 2003 11:34:02 -0500 Stephen Frost <[email protected]> wrote:
Quoted 5 lines · * Bill Davidsen ([email protected]) wrote:
Quoted 3 lines · Thomas Duffy
Quoted 1 line · Eli Carter

So, who can beat his 15.10 bogomips?

[...]

Quoted 10 lines
Quoted 1 line

bogomips : 12.44

At one point I ran Linux on a 386SX-16 with 12MB. That machine ran 1.2.13 (IIRC) until Dec 31 1999, when I was afraid it was not Y2k hardened. I still see spam to glacial.tmr.com today. The name was NOT because it was so cool ;-)

I may still have that board, but I'm not about to put it back in service to measure speed. Your firewall is the slowest "real machine" I've seen, emulation and embedded machines are not really general purpose.

If we're really curious...

sfrost@ns2:/home/sfrost> cat /proc/cpuinfo
processor : 0
vendor_id : unknown
cpu family : 4
model : 0
model name : 486
stepping : unknown
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : no
cpuid level : -1
wp : yes
flags :
bogomips : 9.42

This is my secondary name server. This was also after an upgrade from a 386 because bind9 is a bloody pig. :) To be honest I've thought about putting the 386 back in service as something else because unlike my web server and primary name server there's no chance a CPU fan on it is going to die causing a CPU to fry and the system to crash. At one point the 386 had a 630 day uptime, running 2.2.16.

Stephen

#19 lore raw
In reply to Bill Davidsen
Quoted 10 lines · Bill Davidsen
Quoted 2 lines · On Thu, 20 Mar 2003, [iso-8859-1] J?rn Engel wrote:

And I have a hard time to think of a real-world application where you don't want to unpack but need to verify the signature.

My real world includes downloading a bunch of files and burning a CD to move them to a test environment which is completely private and has no external connections of any kind. I don't do all files that way, of course, but that is the way at least half of the 2.5 kernels I've used were moved to a machine which was non-production.

Real world always wins over imagination. I'll shut up now. :)

Jörn

Signature · 2 lines
When in doubt, use brute force.
-- Ken Thompson