From owner-freebsd-questions@FreeBSD.ORG Thu Feb 3 12:56:44 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E609316A4CE for ; Thu, 3 Feb 2005 12:56:44 +0000 (GMT) Received: from server1.ultratrends.com (S01060004e20310fa.rd.shawcable.net [70.65.87.221]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDEB243D54 for ; Thu, 3 Feb 2005 12:56:43 +0000 (GMT) (envelope-from technical@ultratrends.com) Received: from server1.ultratrends.com (localhost [127.0.0.1]) j13CufoS065667; Thu, 3 Feb 2005 05:56:41 -0700 (MST) (envelope-from trodat@server1.ultratrends.com) Received: from localhost (trodat@localhost)j13CufFf065664; Thu, 3 Feb 2005 05:56:41 -0700 (MST) (envelope-from trodat@server1.ultratrends.com) Date: Thu, 3 Feb 2005 05:56:41 -0700 (MST) From: Technical Director To: gfoster9055@comcast.net In-Reply-To: <020320051228.11461.420219080001A78B00002CC52200735834CACACFC79D0A9B9C010009@comcast.net> Message-ID: <20050203054641.O65648@server1.ultratrends.com> References: <020320051228.11461.420219080001A78B00002CC52200735834CACACFC79D0A9B9C010009@comcast.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Milter: Spamilter (Reciever: server1.ultratrends.com; Sender-ip: 127.0.0.1; Sender-helo: server1.ultratrends.com;) cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 3.2 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2005 12:56:45 -0000 Greg, Wow, talk about handcuffing. One thing I am interested in is if they apply this policy to Microsoft/Sun/Oracle/{$Enterprise} software. Most institutions I know seem to feel that since they've paid the big bucks for this software they better stay up with the latest to be safe. If this is the case for your situation you might want to encourage that this to is required for such things as this server and what it is doing. Enterprise or not they should see the business model for this. Rob. PS If you *have* to stay at 3.2 you might want to consider shifting away (IMHO) from packages/ports and start to work with the individual packages themselves. Keeping in mind that if this is a production server you should probably get a pre-production box with 3.2 on it and do your 'playing' around there. FreeBSD is in the most part a good system to install software on from the original source tar.gz. eg: - MySQL will install but you will have to place a fair amount of time getting a proper foundation in place prior to actually attempting it. (NOTE: Threads, compiler, make, etc.) - PHP should be less of a hassle unless your ./configure line looks like a short story. On Thu, 3 Feb 2005 gfoster9055@comcast.net wrote: > At this momment I am not allowed to up date from FreeBSD 3.2 to another > version, this machine sits at a school and there policies are slow, so I > have to use what is there for the most part, what I need to do is add > some packages like mysql, update php etc..... I was wondering if anyone > knew if FreeBSD 3.2 uses the same package manager has 5.3? Does anyone > know where I might be able to find docs for 3.2? Since this is a > production server I can't just play and try things like I want to. Any > info would be greatly appreciated. > > Thanks > Greg > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >