Since David's busy, I'm working on it now. Just some build issues to
be worked out since warnings were made fatal recently.
From: Matthew Jacob <[EMAIL PROTECTED]>
Subject: Re: chgrp broken on alpha systems
Date: Thu, 5 Jul 2001 14:17:51 -0700 (PDT)
> David claimed he would upgrade beast at some point- but he's pretty
> 1. If I had the authority to do so, I'd drive over to Concord and do it.
> I can do that next week some time.
> 2. If I had > 144KBit DSL, I'd pay the extra power bills and leave up a
> PC164 at Feral all the time for people to do this.
> 3. If I had the ability to sweet talk the NASA/Ames folks, I'd leave a
> machine there up all the time.
> If beast can't be upgraded soon, and #1 can't happen, I will make #2
> happen. I have two PC164s- and one could just be left up all the time.
> On Thu, 5 Jul 2001, Kris Kennaway wrote:
> > On Thu, Jul 05, 2001 at 11:00:09AM +0200, Dag-Erling Smorgrav wrote:
> > > Matthew Jacob <[EMAIL PROTECTED]> writes:
> > > > it's just the same old same old refrain of "beast is broken" or
> > > > "oh well", etc. etc. etc.... but yer right, insulting does no
> > > > good.
> > > >
> > > > I beg too much hard cider at dinner. It makes the veins in the forehead
> > > > swell and makes one impatient.
> > >
> > > I have no problem with that :) And beast isn't broken, it's just that
> > > its bsd.*.mk files are too old to test WARNS patches.
> > Actually, you can work around this if you set enough environment
> > variables, but it certainly is annoying to do.
> > Kris
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message