From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org
Cc: Clemens Schwaighofer <cs@tequila.co.jp>,
Jeff Garzik <jgarzik@pobox.com>,
"Markus T." <markus@trippelsdorf.net>
Subject: Re: Linux 2.6.9-rc3
Date: Fri, 1 Oct 2004 00:01:44 -0400 [thread overview]
Message-ID: <200410010001.44762.gene.heskett@verizon.net> (raw)
In-Reply-To: <415CD05F.4040305@tequila.co.jp>
On Thursday 30 September 2004 23:34, Clemens Schwaighofer wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>On 10/01/2004 12:30 PM, Gene Heskett wrote:
>|> Beats me, Clemens. But at the time, I got curious and the
>|> problem was 100% repeatable using the bz2 src code files I had.
>|> The third time I went after the srcs and patches to build that
>|> kernel, I got the .gz versions of both, and they worked first
>|> time. Then I went back to the .bz2's and was seeing the same
>|> problem as the first 2 downloads gave me. I mv'd that src file &
>|> patch, went after the .bz2's again (for the 3rd time), and that
>|> time it worked flawlessly. Both the 2nd and 3rd dl's files had
>|> the exact same md5sum too. Go figure.
>
>have you unpacked the source and made a diff? is the source the same
>then? perhaps its something with CPU/RAM ? Ever thought of that. If
> only you have it, then what kind of libraries are you using,
> perhaps it some problem only on your box. Can you repeat that on
> other boxes, etc.
>
>|> bz2 problem? DamnedifIknow. snilmerg maybe? But it goes away
>|> if I stick to the .gz's.
>
>It would be interesting to investigate this further. Because if bz2
> is not save to transport data, then you can't use it anymore.
>
I think my biggest concern was the fact that it didn't give any kind
of an error message at the time. That box is now my firewall, and
has the latest up2dates installed until rh eol'd the 7.3 support.
Running an old kernel 2.4.21-rc1-ck6 I built, it commonly gets quite
boring uptimes. I have a BIG ups, so its only prolonged outages that
reset me.
Well, I was gonna brag, but 14 days isn't bragging materiel. I
rebooted it after seeing something I didn't like in the logs, a port
scan for port 33377 or some such number, from an IP thats is a
verizon nameserver. How they got thru the router is beyond me. The
last time that happened, it hacked a 2 week old Seimans router into a
light weight paper weight. The linksys I have in there now seems to
have survived, but is getting flakey, and Jim, the IT guy at the tv
station tells me he had to get 3 of them in a week recently for his
home system because they kept falling over. When in the hell are
they gonna put in the quality before the name goes on the box again?
That knocking sound? That will be me pounding my head on the wall if
this one pukes.
>- --
>[ Clemens Schwaighofer -----=====:::::~ ]
>[ TBWA\ && TEQUILA\ Japan IT Group ]
>[ 6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ]
>[ Tel: +81-(0)3-3545-7703 Fax: +81-(0)3-3545-7343 ]
>[ http://www.tequila.co.jp http://www.tbwajapan.co.jp ]
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.2.4 (GNU/Linux)
>Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
>iD8DBQFBXNBfjBz/yQjBxz8RAkLBAKCTFd4niu/StV85xloSuHmOowcOUgCdGTyI
>18/zlWp2oyfNz/jSJ7Zpjig=
>=iG6j
>-----END PGP SIGNATURE-----
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
next prev parent reply other threads:[~2004-10-01 4:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 3:37 Linus Torvalds
2004-09-30 4:53 ` Markus T.
2004-09-30 4:59 ` Tom Duffy
2004-09-30 5:02 ` Gene Heskett
2004-09-30 6:29 ` Clemens Schwaighofer
2004-09-30 7:30 ` James Bruce
2004-09-30 7:33 ` Clemens Schwaighofer
2004-09-30 15:53 ` Ingo Saitz
2004-09-30 20:27 ` Gene Heskett
2004-09-30 21:55 ` Jeff Garzik
2004-10-01 0:42 ` Clemens Schwaighofer
2004-10-01 3:30 ` Gene Heskett
2004-10-01 3:34 ` Clemens Schwaighofer
2004-10-01 4:01 ` Gene Heskett [this message]
2004-10-01 4:05 ` Clemens Schwaighofer
2004-10-01 4:06 ` Gene Heskett
2004-10-01 3:17 ` Gene Heskett
2004-10-01 5:44 ` Christian Hesse
2004-09-30 18:58 ` Bill Davidsen
2004-09-30 20:32 ` Gene Heskett
2004-09-30 5:03 ` Tom Duffy
2004-09-30 5:14 ` Marcel Holtmann
2004-09-30 5:33 ` Tom Duffy
2004-09-30 5:20 ` Gene Heskett
2004-09-30 5:24 ` Marcel Holtmann
2004-09-30 20:41 ` Gene Heskett
2004-09-30 14:13 ` Linux 2.6.9-rc3 (compile stats) John Cherry
2004-09-30 19:03 ` Linux 2.6.9-rc3 Bill Davidsen
2004-10-01 13:49 ` [PATCH] tty fall-out (was: Re: Linux 2.6.9-rc3) Geert Uytterhoeven
2004-09-30 15:38 Linux 2.6.9-rc3 Tim Krieglstein
[not found] <2K07b-1Ez-3@gated-at.bofh.it>
[not found] ` <2Kh8e-5H2-23@gated-at.bofh.it>
[not found] ` <2KjMz-6E6-17@gated-at.bofh.it>
[not found] ` <2Kmr3-9n-1@gated-at.bofh.it>
2004-10-01 12:36 ` Pascal Schmidt
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=200410010001.44762.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--cc=cs@tequila.co.jp \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.net \
/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
all inboxes | Powered by JetHome®