Re: ypserv.new (feeback requested)

[Deven Kampenhout]

David E. Cross wrote:

 I notice that a lot of people downloaded the ypserv update.  I also know that
 many people have had the same troubles I reported with the 'old' ypserv.
 Have any of you who have had troubles tested this version?  Did it work?
 For those who are running it, have you noticed any problems?
 
 --
 David Cross   | email: [EMAIL PROTECTED] 
 Lab Director  | Rm: 308 Lally Hall
 Rensselaer Polytechnic Institute, | Ph: 518.276.2860
 Department of Computer Science| Fax: 518.276.4033
 I speak only for myself.  | WinNT:Linux::Linux:FreeBSD
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-stable in the body of the message

When was this update published? I cvsuped to 4.4-prerelease on a system 
last friday, and was having problems getting nis to work correctly. I 
could get information fine, but when trying to log in with a linux 
machine (nis server is running FreeBSD 4.4-prerelease), the password 
keeps failing. Seems like the linux box can't correctly read the nis 
passwords.

Is this part of the known problem, or am I doing something wrong?

- Deven
[EMAIL PROTECTED]


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

Re: nVidia Cards /w FreeBSD (3D Acceleration)

[Deven Kampenhout]

Deven Kampenhout wrote:

 Kal Torak wrote:
 
 I am waiting for nVidia to confirm if there is any work
 currently happening on a FreeBSD driver...
 
 But when I talked to loki (www.lokigames.com) about drivers
 for FreeBSD, they sure didnt know anything about it... So we
 may as well get started on the group letter!
 
 Who said they could provide fast web access? And anyone interested
 in making the page? We just need a simple page saying what where
 trying to do and some sort of submition type thing setup... I could
 do a simple perl script to handel that if no one has any better ideas!
 
 
 I can provide web server space. I can't say I have all the time in 
 the  world to create a web page, but I can give whoever wants to head 
 that up  access to my system. 

Ok. The site is up, along with a main page that I was able to spend 
about 1 minute in creating. If we have any web developers who wish to 
enhance the site, feel free to mail me to help get the page started. If 
not, then I will get to it eventually, but I warn that it will not be in 
the near future as I'm extremely busy at the moment.

The site is at http://nvidia.netexplorer.org/

- Deven Kampenhout
[EMAIL PROTECTED]


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

Re: Further question Re: cvsupped to RELENG_4 but got 4.3-RC

[Deven Kampenhout]

I agree with you completely, Bob. The idea of keeping one "master 
server" to push out updates to many is extremely useful when you are 
maintaining a large number of similar systems. It is much less 
work-intensive to maintain several hundred systems if they are running 
on exactly the same configuration, kernel, etc. The only caveat is that 
you must be extremely careful with any changes you make to the master, 
and make certain that any changes that you make to your master system 
are pushed out to all of the "leaf" systems. If not, then you get some 
updates here and there on various systems and you may as well be running 
different software on all of the machines. CVS is definately the way to 
go, as it helps you to be disciplined about distribution. Just make sure 
that the master server that is cvsuping is thoroughly tested before you 
push things out, or you're heading for trouble very quickly :)

Robert wrote:

 There may be some value in the multiple servers case, of running one as a
 cvs server, and updating all the others off that one. Then all your servers
 are reflections of the one that is cvsupping the - remote-cvs-server
 
 just a thought.
 
 Bob
 
 
 
 On Wed, 4 Apr 2001, Brian D. Woodruff wrote:
 
 At 10:35 PM 4/4/01 -0400, you wrote:
 
 On Wed, Apr 04, 2001 at 09:32:39PM -0500, Brian D. Woodruff wrote:
 
 Here are my questions:
 
 1.) is there a way to specify 4.2-STABLE, which is what I
 
 have been using?
 
 can anyone tell me how to get the STABLE version I want?
 
 I would rather be consistent across my servers than have some be one
 release past the others.
 
 If you're using CVS to get RELENG_4 at different points in time, even if
 they're all 4.2-STABLE, your servers will NOT be consistent anyway.  The
 -STABLE branch is a stream, in constant development.  If you update your
 sources via CVS to build one server, then the next day update sources
 again to build another server, the two servers will be different.  This is
 the essence of -STABLE, even though it seems to contradict the meaning of
 the word "stable". :-)
 
 If you require absolute consistency across servers, you need to either
 update all servers from the very same source, or specify an exact CVS tag
 to get the same sources for all servers.
 
 And if it doesn't bother you that your servers are on different points of
 4.2-STABLE, then 4.3-RC is just another point a little farther down the
 development stream.  I'd actually consider the -RC to be safer bet than
 the average -STABLE.
 
 Ken
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-stable" in the body of the message
 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-stable" in the body of the message




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