Re: FreeBSD 4.x Sysinstall upgrade problems?
- From: Tim Judd <tjudd01@xxxxxxxxxxx>
- Date: Tue, 17 Jul 2007 11:58:10 -0600
Nathan wrote:
Well... thanks, I think.
I'll check there.
Lowell Gilbert wrote:comp.unix.bsd.freebsd is not widely propagated, so you won't
necessarily get much help here (in comp.unix.bsd.freebsd).
See http://www.freebsd.org/support.html for better ideas...
[followups redirected accordingly]
Nathan <thorin@xxxxxxx> writes:
I have the pleasure of managing a few FreeBSD mail servers which were
setup and sort of left go for a long time.
One runs FreeBSD 4.1, the other FreeBSD 4.5.
I've read that FreeBSD can be updated using the Sysinstall utility.
I'm considering doing so, but before i even TRY it, i'd like to do
some research, as both servers handle a great deal of mail for our
clients.
Both are running qmail, and apache for webmail.
I'm not really a FreeBSD guy, i've used other BSD's in the past, and i
can manage a FreeBSD server as well as i can any other *nix server, my
background lie's in RedHat Linux.
So i'm looking for input, what can i expect to go wrong using
sysinstall to update the system? I'm told that i should be able to
update to a later release of FreeBSD altogher using sysinstall. Is
this true? If so, what sort of procedure is it?
It's certainly true, but you will need to use the sysinstall that
comes with the system you are upgrading *to*, not the one already on
the system you are upgrading *from*. That said, if these machines have really been lying around untouched
for five or six years running Internet applications, you may be a
lot safer restarting from scratch anyway.
Good luck.
I came into this thread late, apologies for any statements that are duplicated etc.
Why not dump either/both systems to another machine (even a workstation) and restore the image with enough disk space (which might be the problem), and perform suggested updates on the workstation.
This gets you a life scenario that might happen to the machines during the real binary update. However, running a binary update may change the APIs the current programs are using, so the system will work, the ports won't until they're reinstalled.
I don't see how there's any safe way of updating (up to) 7 years (4.1 released Jul/27/2000) of technology and software. Something will break and cause a major snafu. I think you're better off dump(8)ing the current system. Installing a newer OS (6.2 is really a sweet system, it was very well done, and I can't wait for 7.0 which has "started" it's release process) from scratch, and bringing the system back operational.
Just yesterday (in a home environment), I got postfix, amavisd-new (spam and virus filter), courier-imap, and courier-sqwebmail installed. It's a slick system, and runs very well. I would be happy to provide a short howto (just the steps, no descriptions) for anybody interested. And for those who want to know why I chose sqwebmail over any other webmail system, is that sqwebmail doesn't relay the requests though a client, but accesses the maildir directly (faster). It's also part of courier, so the imap and sqwebmail are going to have the same options and benefits (compatability). You could also run the courier esmtp system, but postfix is well recommended everywhere I look.
HTH, please feel free to post more questions if and when you'd like help.
.
- References:
- Re: FreeBSD 4.x Sysinstall upgrade problems?
- From: Nathan
- Re: FreeBSD 4.x Sysinstall upgrade problems?
- Prev by Date: Re: FreeBSD 4.x Sysinstall upgrade problems?
- Next by Date: Re: FreeBSD 4.x Sysinstall upgrade problems?
- Previous by thread: Re: FreeBSD 4.x Sysinstall upgrade problems?
- Next by thread: Alternate superblock updating ?
- Index(es):
Relevant Pages
|
|
