From: Larry McVoy <lm@bitmover.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel.bkbits.net and BK->CVS gateway
Date: Sat, 10 May 2003 12:55:45 -0700 [thread overview]
Message-ID: <20030510195545.GA26447@work.bitmover.com> (raw)
In-Reply-To: <20030510192253.GA24276@delft.aura.cs.cmu.edu>
On Sat, May 10, 2003 at 03:23:03PM -0400, Jan Harkes wrote:
> On Sat, May 10, 2003 at 09:22:07AM -0700, Larry McVoy wrote:
> > In other words, I think you're safe. Famous last words, we'll now discover
> > that our friends in .cz have written the world's first BK virus and it
> > corrupts the CVS tree. Or something. Regardless, we've taken steps to
> > make sure the CVS data is safe and restorable.
>
> Could you please stop making random accusations? Pavel probably has
Could you please stop whining about something that was clearly a joke?
Jeeze, get a sense of humor already.
> better things to do than to write a 'BK virus'. And about that comment
> 'taking steps to make sure CVS data is safe'...
>
> On Sat, May 10, 2003 at 07:04:55AM -0700, Larry McVoy wrote:
> > Dave, I put RH 7.3 on there but didn't install any security fixes, you get
> > to do that fun job if you care.
>
> Hmm, let's see https://rhn.redhat.com/errata/rh73-errata-security.html
Well aren't we the do goody little sys admin. For your information, those
patches were applied before I opened up the box, turned on accounts, or
turned on CVS.
[root@kernel root]# up2date -u
...
None of the packages you requested were found, or they are already updated.
> I sure hope Dave cared, because I wouldn't even consider plugging an
> unpatched anything into the network in the first place. Let alone
> announce this fact to a widely distributed mailing list.
So are you volunteering to manage that machine? Or just complaining?
It *never* fails to amaze me. I spend my friday night in a colo, spend
saturday morning finishing the job, and some arm chair quarterback
has to come along and rudely tell me that I'm not doing it right?!?
Would it be any surprise if the next time there is a problem we just
let it slide for a few weeks before it gets fixed?
"it's about being nice to people especially the ones that help you."
What he said.
next prev parent reply other threads:[~2003-05-10 19:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 14:04 kernel.bkbits.net and BK->CVS gateway Larry McVoy
2003-05-10 15:34 ` Ben Collins
2003-05-10 16:06 ` Larry McVoy
2003-05-10 15:43 ` Ben Collins
2003-05-10 16:22 ` Larry McVoy
2003-05-10 19:23 ` Jan Harkes
2003-05-10 19:55 ` Larry McVoy [this message]
2003-05-10 20:21 ` Roman Zippel
2003-05-10 20:42 ` David S. Miller
2003-05-10 20:59 ` Roman Zippel
2003-05-10 20:01 ` David S. Miller
2003-05-10 21:15 ` Roman Zippel
2003-05-10 20:44 ` Larry McVoy
2003-05-10 21:28 ` Roman Zippel
2003-05-10 21:43 ` Ben Collins
2003-05-11 15:45 ` Make kernel.bkbits.net public via web? [was Re: kernel.bkbits.net and BK->CVS gateway] Nicholas Wourms
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=20030510195545.GA26447@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linux-kernel@vger.kernel.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