Re: cvs commit: src UPDATING
On Mon, 28 May 2001, Warner Losh wrote: ... : -current is NOT safe, by any stretch of the imagination. Kris K. and I : have both posted numerous messages to -current about the problems we're : having let me know if you need copies. I'm not having problems :-). However, I see that around May 25 or 26 the freelist messages started... Have you tried to start aviplay ( coming from ports/graphics/avifile ) or using whine? Bye! Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src UPDATING
In message Pine.BSF.4.31.0105290848330.514-10@nihil Michael Reifenberger writes: : Have you tried to start aviplay ( coming from ports/graphics/avifile ) or using : whine? Nope. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src UPDATING
In message Pine.BSF.4.31.0105290848330.514-10@nihil Michael Reifenberger writes: : Have you tried to start aviplay ( coming from ports/graphics/avifile ) or using : whine? Nope. vmware does the job too, and I believe star-office. Warner -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src UPDATING
Brian Somers [EMAIL PROTECTED] wrote: In message Pine.BSF.4.31.0105290848330.514-10@nihil Michael Reifenberger writes: : Have you tried to start aviplay ( coming from ports/graphics/avifile ) or using : whine? Nope. vmware does the job too, and I believe star-office. I've noticed it, and after backing out locally the commits recently made to lock LDT access, things work (at least, as well as they used to). I didn't do this hastily; I spent hours looking at what could possibly be wrong with the new locking added, and couldn't find anything :( I know that sched_lock is being held too long, which means (I think) that either somehow the code is sleeping with it held or just not releasing it at all. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src UPDATING
Warner Losh wrote: imp 2001/05/28 21:26:44 PDT Modified files: .UPDATING Log: Looks like -current is safe again, and has been since Friday. -current is NOT safe, by any stretch of the imagination. Kris K. and I have both posted numerous messages to -current about the problems we're having let me know if you need copies. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src UPDATING
In message [EMAIL PROTECTED] Doug Barton writes: : Warner Losh wrote: : : imp 2001/05/28 21:26:44 PDT : :Modified files: : .UPDATING :Log: :Looks like -current is safe again, and has been since Friday. : : -current is NOT safe, by any stretch of the imagination. Kris K. and I : have both posted numerous messages to -current about the problems we're : having let me know if you need copies. I'm not having problems :-). However, I see that around May 25 or 26 the freelist messages started... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src UPDATING
On Mon, May 28, 2001 at 10:16:46PM -0700, Doug Barton wrote: .UPDATING Log: Looks like -current is safe again, and has been since Friday. Alpha is in evern worse shape than x86. The statement that -current is safe is 110% wrong. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
