Re: Upgrade recommendations
On 2002-10-16 15:12, Jonathan Arnold [EMAIL PROTECTED] wrote: FreeBSD the hardest thing to beat into peoples heads has been don't use -current on critical machines. Thanks for insisting on that too! I don't have, by any means, a critical machine - it's just a play web site and mailing list - but I do like to have them up, so perhaps I'll stay away for now. 5.0 is now very near to being released, and the team of people who are working on making it a stable enough system that is worthy of being cut in stone as 5.0-RELEASE will certainly be very grateful for extra testing. But you should only run -current if you have the time to follow the latest changes closely, since there are still a few bumpy points. Bearing that in mind, I have run -current at my workstation at home ever since I remember me switching to 3-current and it's not very difficult to keep it stable if you are cautious when upgrading to avoid the occasional periods of serious problems. Giorgos. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Upgrade recommendations
I'm currently running 4.5, and want to upgrade my machine and was wondering what you might have for recommendations. It has dual 333mhz Pentium II cpus, an S3 video card, 256mb RAM and a 20gb hard drive - not cutting edge hardware by any means! All it does is serve my small web sites via Apache and run some low volume mailing lists via Mailman. It isn't kept too busy, but it shouldn't be down for long periods nonetheless. I'm thinking of 3 possible paths: 1] A binary upgrade using the latest 4.x (4.7?) 2] A binary upgrade to 5.0 3] A reformat and complete upgrade to 5.0 - I already have the web site mailing list dbs backed up. As scary as it sounds, I'm leaning towards #3. It seems it shouldn't be too hard to move the Mailman database stuff to a new machine, so my main concern is how stable 5.0 is at this point. I'm willing (heck, even want) to play with some bleeding edge technology, but I do need it to be running with extensive handholding. Is 5.0 at that stage? -- Jonathan Arnold (mailto:[EMAIL PROTECTED]) The Incredible Brightness of Seeing, a Home Theater weblog http://jdarnold.tzo.com/HomeTheater To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Upgrade recommendations
I would recommend a cvsup, build world, build kernel, etc. upgrade to 4.7-RELEASE personnally. Doing the upgrade this way will keep downtime to a minumum ( perhaps 10 minutes downtime ). - Mike I'm currently running 4.5, and want to upgrade my machine and was wondering what you might have for recommendations. It has dual 333mhz Pentium II cpus, an S3 video card, 256mb RAM and a 20gb hard drive - not cutting edge hardware by any means! All it does is serve my small web sites via Apache and run some low volume mailing lists via Mailman. It isn't kept too busy, but it shouldn't be down for long periods nonetheless. I'm thinking of 3 possible paths: 1] A binary upgrade using the latest 4.x (4.7?) 2] A binary upgrade to 5.0 3] A reformat and complete upgrade to 5.0 - I already have the web site mailing list dbs backed up. As scary as it sounds, I'm leaning towards #3. It seems it shouldn't be too hard to move the Mailman database stuff to a new machine, so my main concern is how stable 5.0 is at this point. I'm willing (heck, even want) to play with some bleeding edge technology, but I do need it to be running with extensive handholding. Is 5.0 at that stage? -- Jonathan Arnold (mailto:[EMAIL PROTECTED]) The Incredible Brightness of Seeing, a Home Theater weblog http://jdarnold.tzo.com/HomeTheater To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Upgrade recommendations
At 10:24 AM 10.16.2002 -0700, Mike Hogsett wrote: I would recommend a cvsup, build world, build kernel, etc. upgrade to 4.7-RELEASE personnally. Doing the upgrade this way will keep downtime to a minumum ( perhaps 10 minutes downtime ). - Mike I'm currently running 4.5, and want to upgrade my machine and was wondering what you might have for recommendations. It has dual 333mhz Pentium II cpus, an S3 video card, 256mb RAM and a 20gb hard drive - not cutting edge hardware by any means! All it does is serve my small web sites via Apache and run some low volume mailing lists via Mailman. It isn't kept too busy, but it shouldn't be down for long periods nonetheless. I'm thinking of 3 possible paths: 1] A binary upgrade using the latest 4.x (4.7?) 2] A binary upgrade to 5.0 3] A reformat and complete upgrade to 5.0 - I already have the web site mailing list dbs backed up. As scary as it sounds, I'm leaning towards #3. It seems it shouldn't be too hard to move the Mailman database stuff to a new machine, so my main concern is how stable 5.0 is at this point. I'm willing (heck, even want) to play with some bleeding edge technology, but I do need it to be running with extensive handholding. Is 5.0 at that stage? -- Jonathan Arnold (mailto:[EMAIL PROTECTED]) The Incredible Brightness of Seeing, a Home Theater weblog http://jdarnold.tzo.com/HomeTheater I am also running 4.5 and have not moved up because I don't want to deal with the Sendmail 8.12.x changes yet that will affect my mail server and majordomo. So, there will be some configuring *pains* to deal with and need to be ready for and it may hamper and extend the downtime well beyond the 10 minutes if you don't first test on another machine IMHO Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Upgrade recommendations
On Wed, Oct 16, 2002 at 01:14:12PM -0400, Jonathan Arnold wrote: I'm currently running 4.5, and want to upgrade my machine and was wondering what you might have for recommendations. [...] 3] A reformat and complete upgrade to 5.0 - I already have the web site mailing list dbs backed up. As scary as it sounds, I'm leaning towards #3. That does sound scary. By all means go right ahead if it doesn't matter that the server stays up. In the past 7 years that I have been using FreeBSD the hardest thing to beat into peoples heads has been don't use -current on critical machines. Am concerned that your system is still 4.5, which suggests you don't have to spend much time keeping it running (good) but don't spend much time keeping up (bad). There have been serious issues with ssh, apache, and probably other things since 4.5. You may be vulnerable. Make buildworld, make installworld, mergemaster, and make kernel can be performed on a running system. Then with any luck you are only a reboot away from being updated. That's what I do. -- David Kelly N4HHE, [EMAIL PROTECTED] = The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Upgrade recommendations
At 01:15 PM 10.16.2002 -0500, David Kelly wrote: On Wed, Oct 16, 2002 at 01:14:12PM -0400, Jonathan Arnold wrote: I'm currently running 4.5, and want to upgrade my machine and was wondering what you might have for recommendations. [...] 3] A reformat and complete upgrade to 5.0 - I already have the web site mailing list dbs backed up. As scary as it sounds, I'm leaning towards #3. That does sound scary. By all means go right ahead if it doesn't matter that the server stays up. In the past 7 years that I have been using FreeBSD the hardest thing to beat into peoples heads has been don't use -current on critical machines. Am concerned that your system is still 4.5, which suggests you don't have to spend much time keeping it running (good) but don't spend much time keeping up (bad). There have been serious issues with ssh, apache, and probably other things since 4.5. You may be vulnerable. Make buildworld, make installworld, mergemaster, and make kernel can be performed on a running system. Then with any luck you are only a reboot away from being updated. That's what I do. -- David Kelly N4HHE, [EMAIL PROTECTED] = There have been serious issues with ssh, apache, and probably other things since 4.5. You may be vulnerable. This is not an issue with the base system. the ssh has been patched and Apache is not part of the base system and can be updated separately from ports or packages. I'm running on e of the latest versions not vulnerable. Also, am running 4.5-RELEASE p-20 which is right up to date with security patches. I don't track STABLE. but do track all security patches and update as and when they come out so, one doesn't have to upgrade above 4.5 to have the security. Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Upgrade recommendations
FreeBSD the hardest thing to beat into peoples heads has been don't use -current on critical machines. Thanks for insisting on that too! I don't have, by any means, a critical machine - it's just a play web site and mailing list - but I do like to have them up, so perhaps I'll stay away for now. time keeping up (bad). There have been serious issues with ssh, apache, and probably other things since 4.5. You may be vulnerable. All valid concerns. But I don't use ssh (have it turned off) and I have kept Apache patched. I do run some updates, just haven't jumped whole hog into the water. Make buildworld, make installworld, mergemaster, and make kernel can be performed on a running system. Then with any luck you are only a reboot away from being updated. That's what I do. You know, I will probably do that, to the recent 4.7, now that I think about it a little more. -- Jonathan Arnold (mailto:[EMAIL PROTECTED]) The Incredible Brightness of Seeing, a Home Theater weblog http://jdarnold.tzo.com/HomeTheater To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
