tsiou
Verified User
migrate directadmin into freebsds ports (exim etc)
The file with the instructions is moved here...
**** EDITED ******************************************************
Hi, unfortunately i dont have time to put it all together, but i'm posting some notes attached for how i did my migration to ports.
There may be some mistakes (some of the notes added after some months of the real test), so try it and post any problems to check it out.
Don't try if possible in a production server, i hope that someone who has the time to test it will post back a 100% working directions.
It's running on freebsd 6.3 and (6.2) 32bit but i thing that it can be used for 7.0
Be sure to replace some [email protected] with your domain name..
Paix i hope that you can edit it and test it for 7.0 64bit ..
Before changing anything take a backup!
********************************************************************
Hi,
i have just managed to make my directadmin independent from its custom build services.
Unfortunately i cant write an extensive how to as many hours and attempts needed to make it work.
I can say though that it can be done. I have disabled all of DA's services and use freebsd's default services.. now i can freely portupgrade and follow security updates for apache, exim etc and follow freebsd's update tree.
The idea came from DA's how to upgrade mysql for freebsd.
As a rule, the standard procedure was :
1. install the service (cd /usr/ports/www/apache20) and when possible complile it with flags that DA uses.
2. cd to /usr/local/etc/apache, delete the folder and make a link to DA's config (/etc/httpd/conf)
3. delete DA's service files (/usr/local/bin/httpd) so the system use /usr/local/sbin/httpd)
4. set some flags to /etc/rc.conf to match DA's prefs and enable the service
5. sometimes have some links from DA's services to freebsd services like ln /usr/local/sbin/httpd /usr/local/bin/httpd
6. delete DA's startup files and let the system use its own.
7. start the service and see the logs for what you have forgotten
Dont try to move all of the services by one, for example change spamassasin, wait for some days to see that the system goes ok, change exim and wait some days, then proftp etc..
proftpd is the simpler service along with mysql
then you can try spamassassin (this needs the links from the old executables as exim uses them by absolute path) etc...
In the end if something doesnt work you can pkg_delete it and use DA's custom build script to reinstall it and go from scratch.
I'm willing to help anyone who try's some of the above, i will watch this thread (cant every day due to military obligations for some months)..
************************************************************************************************
The file with the instructions is moved here...
**** EDITED ******************************************************
Hi, unfortunately i dont have time to put it all together, but i'm posting some notes attached for how i did my migration to ports.
There may be some mistakes (some of the notes added after some months of the real test), so try it and post any problems to check it out.
Don't try if possible in a production server, i hope that someone who has the time to test it will post back a 100% working directions.
It's running on freebsd 6.3 and (6.2) 32bit but i thing that it can be used for 7.0
Be sure to replace some [email protected] with your domain name..
Paix i hope that you can edit it and test it for 7.0 64bit ..
Before changing anything take a backup!
********************************************************************
Hi,
i have just managed to make my directadmin independent from its custom build services.
Unfortunately i cant write an extensive how to as many hours and attempts needed to make it work.
I can say though that it can be done. I have disabled all of DA's services and use freebsd's default services.. now i can freely portupgrade and follow security updates for apache, exim etc and follow freebsd's update tree.
The idea came from DA's how to upgrade mysql for freebsd.
As a rule, the standard procedure was :
1. install the service (cd /usr/ports/www/apache20) and when possible complile it with flags that DA uses.
2. cd to /usr/local/etc/apache, delete the folder and make a link to DA's config (/etc/httpd/conf)
3. delete DA's service files (/usr/local/bin/httpd) so the system use /usr/local/sbin/httpd)
4. set some flags to /etc/rc.conf to match DA's prefs and enable the service
5. sometimes have some links from DA's services to freebsd services like ln /usr/local/sbin/httpd /usr/local/bin/httpd
6. delete DA's startup files and let the system use its own.
7. start the service and see the logs for what you have forgotten
Dont try to move all of the services by one, for example change spamassasin, wait for some days to see that the system goes ok, change exim and wait some days, then proftp etc..
proftpd is the simpler service along with mysql
then you can try spamassassin (this needs the links from the old executables as exim uses them by absolute path) etc...
In the end if something doesnt work you can pkg_delete it and use DA's custom build script to reinstall it and go from scratch.
I'm willing to help anyone who try's some of the above, i will watch this thread (cant every day due to military obligations for some months)..
************************************************************************************************
Attachments
Last edited: