Re: The World and MIT krb5

2003-12-03 Thread Tillman Hodgson
On Wed, Dec 03, 2003 at 11:52:27AM -0800, Galen Sampson wrote: Hello all, snip [Note: I'm not sure that this should be in current@ rather than [EMAIL PROTECTED] 1) Are the worlds daemons written to link against kerberos (as apposed to the heimdal replacements replacing their traditional

[Tillman: Upgraded to latest -current today, boot hangs on ata3: resetting devices]

2003-11-04 Thread Tillman Hodgson
It occurs to me that this is likely related to the new interrupt code. that tends to imply that the fix is wait a few days and re-cvsup, but I thought folks here would be interested in seeing Sparc64 feedback. -T -- [It] contains vegetable stabilizer which sounds ominous. How unstable are

Re: [Tillman: Upgraded to latest -current today, boot hangs on ata3: resetting devices]

2003-11-04 Thread Tillman Hodgson
On Tue, Nov 04, 2003 at 02:20:19PM -0500, John Baldwin wrote: On 04-Nov-2003 Tillman Hodgson wrote: It occurs to me that this is likely related to the new interrupt code. that tends to imply that the fix is wait a few days and re-cvsup, but I thought folks here would be interested

Re: cvsup sites are all at capacity?

2003-09-16 Thread Tillman Hodgson
On Tue, Sep 16, 2003 at 05:11:02PM -0500, Dan Nelson wrote: In the last episode (Sep 16), Andrew Lankford said: I've tried various cvsup sites (normally cvsup2 or cvsup16 ) and each site returns this message: Rejected by server: Access limit exceeded; try again later I've gotten

Re: Buildworld fails in 5.1

2003-07-18 Thread Tillman
On Wed, Jul 16, 2003 at 02:24:18PM +, Bosko Milekic wrote: Same here, remove the -j N. Right now there seem to be some dependencies which you fail against with a parallel build. And it works here as well. Building with -j highlights a problem I'm seeing on a sparc64 though ... the stock

Re: Buildworld fails in 5.1

2003-07-16 Thread Tillman
On Wed, Jul 16, 2003 at 01:47:38PM -0400, Matt Loschert wrote: My buildworlds have been failing ever since the gcc 3.3 upgrade. I got the message that you got on one of the failures. However, my last three builds have consistently failed at the following point: Mine has as well, though I