Re: Why is the STABLE branch not so stable anymore?

2001-06-12 Thread W Gerald Hicks

Mark Evenson wrote:
> 
> W Gerald Hicks <[EMAIL PROTECTED]> writes:
> 
> > Cripes people, the CVS repository is available for people to be able to
> > slide back and forth in time as necessary.  It only requires a tiny bit
> > of competence.  For fair effort on your part you also gain a fair amount
> > of liberty along with a system that has literally made computing history
> > in terms of stability.  On top of that, it's free.
> 
> Not true:  anonymous CVS access to the FreeBSD tree has not been available
> for at least a couple years now.  Or did I miss something?
> 

Yeah, CVSup's ability to maintain a local repository.  With this
methodology, instead of using CVSup to keep /usr/{ports,src} up to date
one keeps their local repo up to date and then uses cvs to checkout
directly from there.

Cheers,

Jerry Hicks
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: Next STABLE release going to be 4.4?

2001-05-01 Thread W Gerald Hicks

(makes note to request [EMAIL PROTECTED])

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: REMINDER: 4.2 code freeze starts tomorrow!

2000-11-01 Thread W Gerald Hicks

Sean O'Connell wrote:
> 
> all of my daily scripts were run twice as well.
> 

Aye, here too.

Jerry Hicks
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: debugging a crash

1999-09-23 Thread W Gerald Hicks

> My machine running 3.3-STABLE is randomly rebooting from time to
> time.   There is nothing in the system logs.  What should I do if I
> want to find the cause of these reboots?  Is the "Kernel Debugging"
> section in the handbook the right place to start? This machines is
> destined to become our main file server, so I have to take care of the
> problem.  Thanks for any advice!

Hmm... sounds like NMI, often caused by memory/motherboard hardware
problems.

By chance is this machine loaded down with a *lot* of memory?  If so,
try removing half of the memory and see if you're loading the memory
bus too heavily.

Good Luck,

Jerry Hicks
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message