https://wiki.koozali.org/api.php?action=feedcontributions&user=Gregswallow&feedformat=atomSME Server - User contributions [en]2024-03-29T16:01:04ZUser contributionsMediaWiki 1.35.5https://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18840SME Server:9.0Alpha2013-02-19T18:20:56Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 14 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
There have as of now been 2 versions of the SME9Alpha1 ISO - check the date, this is current as for the Feb 14 2013 version.<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
{{note box| keep in mind you need to activate the PAE option of your virtualisation environment for playing with SME Server 9}}<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
<br />
If possible use something like zsync which will transfer just the chages to the ISO and not the whole file itself :<br />
<br />
:*You can get it for Debian/Ubuntu with <br />
sudo apt-get install zsync<br />
<br />
:*On CentOS/ RH you can get an RPM here http://pkgs.repoforge.org/zsync/<br />
<br />
You can then do the following : <br />
<br />
{{tip box|zsync http://mirror.contribs.org/releases/testing/9/iso/x86_64/smeserver-9.0alpha1-x86_64.iso.zsync<br />
<br />
zsync http://mirror.contribs.org/releases/testing/9/iso/i386/smeserver-9.0alpha1-i386.iso.zsync}}<br />
<br />
If the ISO changes, just run these commands again and it will propogate the changes, not the whole file.<br />
<br />
* Start the machine and choose the ISO image to boot from and install SME Server following the instructions.<br />
<br />
== After first reboot ==<br />
* Login as root and enable networking:<br />
- This is a temporary measure, and should work if you have the a DHCP server giving your external adapter (usually eth1) an IP address<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. After the post-upgrade/reboot the proper yum configuration is enabled.<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum upgrade to the latest the e-smith and smeserver packages<br />
- All the e-smith and smeserver packages needed are installed by the CD now, and bug [[bugzilla:7350]] is fixed with e-smith-base-5.4.0-10 so now the command is just:<br />
<pre style="white-space:normal;"><br />
yum --disablerepo=base,updates,extras upgrade --nogpg<br />
</pre><br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* When system boots up it will ask you if you want to restore from backup (say no) and enter a root password, etc, and will reboot.<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', choose the desired configuration and then it ask you to reboot again.<br />
* Re-enable ssh access (the lazy not-so-secure way, but I am assuming for this testing/dev scenario that your external IP is really a local address behind a router)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Enable easier access to the server manager if you prefer (modify as needed for your network)<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
db configuration setprop httpd-admin PermitPlainTextAccess yes <br />
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' <br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
Should be able to access https://yourserverip/server-manager/ now in a browser but seems that you have to log in here first - https://yourserverip/server-common/cgi-bin/login - Is that right? I think I'm missing something...Someone fix this part of the instructions please :-) - Oh, it could be [[bugzilla:7254]] causing part of that problem...<br />
* Save a snapshot in virtualbox so you can revert to this point if needed.<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
- the repo smeupdates-testing is not enabled by default. At this point in the development process you will probably want those rpms. This will check what is available: <br />
<pre><br />
yum --enablerepo=smeupdates-testing upgrade --nogpg<br />
</pre><br />
<br />
== Some ideas for things to look for:==<br />
<br />
{{note box| <br />
In this Alpha ISO there are going to be a lot of strange things that might appear '''before''' doing a configure and reboot. Most of these things won't be of interest to us. Once we fix the configure and reboot part of the first-boot then we can really start looking at the issues that occur during install and first boot.<br />
<br />
If you notice any issues/bugs that occur '''after the initial config and reboot''' please continue to raise them.}}<br />
<br />
<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18839SME Server:9.0Alpha2013-02-19T18:16:55Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 14 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
There have as of now been 2 versions of the SME9Alpha1 ISO - check the date, this is current as for the Feb 14 2013 version.<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
{{note box| keep in mind you need to activate the PAE option of your virtualisation environment for playing with SME Server 9}}<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
<br />
If possible use something like zsync which will transfer just the chages to the ISO and not the whole file itself :<br />
<br />
:*You can get it for Debian/Ubuntu with <br />
sudo apt-get install zsync<br />
<br />
:*On CentOS/ RH you can get an RPM here http://pkgs.repoforge.org/zsync/<br />
<br />
You can then do the following : <br />
<br />
{{tip box|zsync http://mirror.contribs.org/releases/testing/9/iso/x86_64/smeserver-9.0alpha1-x86_64.iso.zsync<br />
<br />
zsync http://mirror.contribs.org/releases/testing/9/iso/i386/smeserver-9.0alpha1-i386.iso.zsync}}<br />
<br />
If the ISO changes, just run these commands again and it will propogate the changes, not the whole file.<br />
<br />
* Start the machine and choose the ISO image to boot from and install SME Server following the instructions.<br />
<br />
== After first reboot ==<br />
* Login as root and enable networking:<br />
- This is a temporary measure, and should work if you have the a DHCP server giving your external adapter (usually eth1) an IP address<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. After the post-upgrade/reboot the proper yum configuration is enabled.<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum upgrade to the latest the e-smith and smeserver packages<br />
- All the e-smith and smeserver packages needed are installed by the CD now, and bug [[bugzilla:7350]] is fixed with e-smith-base-5.4.0-10 so now the command is just:<br />
<pre style="white-space:normal;"><br />
yum --disablerepo=base,updates,extras upgrade --nogpg<br />
</pre><br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* When system boots up it will ask you if you want to restore from backup (say no) and enter a root password, etc, and will reboot.<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', choose the desired configuration and then it ask you to reboot again.<br />
* Re-enable ssh access (the lazy not-so-secure way, but I am assuming for this testing/dev scenario that your external IP is really a local address behind a router)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Enable easier access to the server manager (modify as needed for your network)<br />
- I could not access the server manager from the console<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
db configuration setprop httpd-admin PermitPlainTextAccess yes <br />
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' <br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
Should be able to access https://yourserverip/server-manager/ now in a browser but seems that you have to log in here first - https://yourserverip/server-common/cgi-bin/login - Is that right? I think I'm missing something...Someone fix this part of the instructions please :-) - Oh, it could be [[bugzilla:7254]] causing part of that problem...<br />
* Save a snapshot in virtualbox so you can revert to this point if needed.<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
- the repo smeupdates-testing is not enabled by default. At this point in the development process you will probably want those rpms. This will check what is available: <br />
<pre><br />
yum --enablerepo=smeupdates-testing upgrade --nogpg<br />
</pre><br />
<br />
== Some ideas for things to look for:==<br />
<br />
{{note box| <br />
In this Alpha ISO there are going to be a lot of strange things that might appear '''before''' doing a configure and reboot. Most of these things won't be of interest to us. Once we fix the configure and reboot part of the first-boot then we can really start looking at the issues that occur during install and first boot.<br />
<br />
If you notice any issues/bugs that occur '''after the initial config and reboot''' please continue to raise them.}}<br />
<br />
<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18838SME Server:9.0Alpha2013-02-19T18:14:41Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 14 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
There have as of now been 2 versions of the SME9Alpha1 ISO - check the date, this is current as for the Feb 14 2013 version.<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
{{note box| keep in mind you need to activate the PAE option of your virtualisation environment for playing with SME Server 9}}<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
<br />
If possible use something like zsync which will transfer just the chages to the ISO and not the whole file itself :<br />
<br />
:*You can get it for Debian/Ubuntu with <br />
sudo apt-get install zsync<br />
<br />
:*On CentOS/ RH you can get an RPM here http://pkgs.repoforge.org/zsync/<br />
<br />
You can then do the following : <br />
<br />
{{tip box|zsync http://mirror.contribs.org/releases/testing/9/iso/x86_64/smeserver-9.0alpha1-x86_64.iso.zsync<br />
<br />
zsync http://mirror.contribs.org/releases/testing/9/iso/i386/smeserver-9.0alpha1-i386.iso.zsync}}<br />
<br />
If the ISO changes, just run these commands again and it will propogate the changes, not the whole file.<br />
<br />
* Start the machine and choose the ISO image to boot from and install SME Server following the instructions.<br />
<br />
== After first reboot ==<br />
* Login as root and enable networking:<br />
- This is a temporary measure, and should work if you have the a DHCP server giving your external adapter (usually eth1) an IP address<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- enabling ssh now is not really needed, there isn't a long command to copy and paste anymore, so skip this if you like...This is also temporary, the hosts.allow file is templated and will be overwritten soon<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. After the post-upgrade/reboot the proper yum configuration is enabled.<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum upgrade to the latest the e-smith and smeserver packages<br />
- All the e-smith and smeserver packages needed are installed by the CD now, and bug [[bugzilla:7350]] is fixed with e-smith-base-5.4.0-10 so now the command is just:<br />
<pre style="white-space:normal;"><br />
yum --disablerepo=base,updates,extras upgrade --nogpg<br />
</pre><br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* When system boots up it will ask you if you want to restore from backup (say no) and enter a root password, etc, and will reboot.<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', choose the desired configuration and then it ask you to reboot again.<br />
* Re-enable ssh access (the lazy not-so-secure way, but I am assuming for this testing/dev scenario that your external IP is really a local address behind a router)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Enable easier access to the server manager (modify as needed for your network)<br />
- I could not access the server manager from the console<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
db configuration setprop httpd-admin PermitPlainTextAccess yes <br />
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' <br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
Should be able to access https://yourserverip/server-manager/ now in a browser but seems that you have to log in here first - https://yourserverip/server-common/cgi-bin/login - Is that right? I think I'm missing something...Someone fix this part of the instructions please :-) - Oh, it could be [[bugzilla:7254]] causing part of that problem...<br />
* Save a snapshot in virtualbox so you can revert to this point if needed.<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
- the repo smeupdates-testing is not enabled by default. At this point in the development process you will probably want those rpms. This will check what is available: <br />
<pre><br />
yum --enablerepo=smeupdates-testing upgrade --nogpg<br />
</pre><br />
<br />
== Some ideas for things to look for:==<br />
<br />
{{note box| <br />
In this Alpha ISO there are going to be a lot of strange things that might appear '''before''' doing a configure and reboot. Most of these things won't be of interest to us. Once we fix the configure and reboot part of the first-boot then we can really start looking at the issues that occur during install and first boot.<br />
<br />
If you notice any issues/bugs that occur '''after the initial config and reboot''' please continue to raise them.}}<br />
<br />
<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18837SME Server:9.0Alpha2013-02-19T18:11:49Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 14 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
There have as of now been 2 versions of the SME9Alpha1 ISO - check the date, this is current as for the Feb 14 2013 version.<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
{{note box| keep in mind you need to activate the PAE option of your virtualisation environment for playing with SME Server 9}}<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
<br />
If possible use something like zsync which will transfer just the chages to the ISO and not the whole file itself :<br />
<br />
:*You can get it for Debian/Ubuntu with <br />
sudo apt-get install zsync<br />
<br />
:*On CentOS/ RH you can get an RPM here http://pkgs.repoforge.org/zsync/<br />
<br />
You can then do the following : <br />
<br />
{{tip box|zsync http://mirror.contribs.org/releases/testing/9/iso/x86_64/smeserver-9.0alpha1-x86_64.iso.zsync<br />
<br />
zsync http://mirror.contribs.org/releases/testing/9/iso/i386/smeserver-9.0alpha1-i386.iso.zsync}}<br />
<br />
If the ISO changes, just run these commands again and it will propogate the changes, not the whole file.<br />
<br />
* Start the machine and choose the ISO image to boot from and install SME Server following the instructions.<br />
<br />
== After first reboot ==<br />
* Login as root and enable networking:<br />
- This is a temporary measure, and should work if you have the a DHCP server giving your external adapter (usually eth1) an IP address<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- enabling ssh now is not really needed, there isn't a long command to copy and paste anymore, so skip this if you like...This is also temporary, the hosts.allow file is templated and will be overwritten soon<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. After the post-upgrade/reboot the proper yum configuration is enabled.<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum upgrade to the latest the e-smith and smeserver packages<br />
- All the e-smith and smeserver packages needed are installed by the CD now, and bug [[bugzilla:7350]] is fixed with e-smith-base-5.4.0-10 so now the command is just:<br />
<pre style="white-space:normal;"><br />
yum --disablerepo=base,updates,extras upgrade --nogpg<br />
</pre><br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
- NOTE: press the 'ESC' key to close the CentOS graphical splash screen with the blue/white bar at the bottom of the screen before it is all white - see [[bugzilla:7354]]<br />
* When system boots up it will ask you if you want to restore from backup (say no) and enter a root password, etc, and will reboot.<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', choose the desired configuration and then it ask you to reboot again.<br />
* Re-enable ssh access (the lazy not-so-secure way, but I am assuming for this testing/dev scenario that your external IP is really a local address behind a router)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Enable easier access to the server manager (modify as needed for your network)<br />
- I could not access the server manager from the console<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
db configuration setprop httpd-admin PermitPlainTextAccess yes <br />
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' <br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
Should be able to access https://yourserverip/server-manager/ now in a browser but seems that you have to log in here first - https://yourserverip/server-common/cgi-bin/login - Is that right? I think I'm missing something...Someone fix this part of the instructions please :-) - Oh, it could be [[bugzilla:7254]] causing part of that problem...<br />
* Save a snapshot in virtualbox so you can revert to this point if needed.<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
- the repo smeupdates-testing is not enabled by default. At this point in the development process you will probably want those rpms. This will check what is available: <br />
<pre><br />
yum --enablerepo=smeupdates-testing upgrade --nogpg<br />
</pre><br />
<br />
== Some ideas for things to look for:==<br />
<br />
{{note box| <br />
In this Alpha ISO there are going to be a lot of strange things that might appear '''before''' doing a configure and reboot. Most of these things won't be of interest to us. Once we fix the configure and reboot part of the first-boot then we can really start looking at the issues that occur during install and first boot.<br />
<br />
If you notice any issues/bugs that occur '''after the initial config and reboot''' please continue to raise them.}}<br />
<br />
<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18836SME Server:9.0Alpha2013-02-19T18:10:35Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 14 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
There have as of now been 2 versions of the SME9Alpha1 ISO - check the date, this is current as for the Feb 14 2013 version.<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
{{note box| keep in mind you need to activate the PAE option of your virtualisation environment for playing with SME Server 9}}<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
<br />
If possible use something like zsync which will transfer just the chages to the ISO and not the whole file itself :<br />
<br />
:*You can get it for Debian/Ubuntu with <br />
sudo apt-get install zsync<br />
<br />
:*On CentOS/ RH you can get an RPM here http://pkgs.repoforge.org/zsync/<br />
<br />
You can then do the following : <br />
<br />
{{tip box|zsync http://mirror.contribs.org/releases/testing/9/iso/x86_64/smeserver-9.0alpha1-x86_64.iso.zsync<br />
<br />
zsync http://mirror.contribs.org/releases/testing/9/iso/i386/smeserver-9.0alpha1-i386.iso.zsync}}<br />
<br />
If the ISO changes, just run these commands again and it will propogate the changes, not the whole file.<br />
<br />
* Start the machine and choose the ISO image to boot from and install SME Server following the instructions.<br />
<br />
== After first reboot ==<br />
* Login as root and enable networking:<br />
- This is a temporary measure, and should work if you have the a DHCP server giving your external adapter (usually eth1) an IP address<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- enabling ssh now is not really needed, there isn't a long command to copy and paste anymore, so skip this if you like...This is also temporary, the hosts.allow file is templated and will be overwritten soon<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. After the post-upgrade/reboot the proper yum configuration is enabled.<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum upgrade to the latest the e-smith and smeserver packages<br />
- All the e-smith and smeserver packages needed are installed by the CD now, and bug [[bugzilla:7350]] is fixed with e-smith-base-5.4.0-10 so now the command is just:<br />
<pre style="white-space:normal;"><br />
yum --disablerepo=base,updates,extras upgrade --nogpg<br />
</pre><br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
- NOTE: press the 'ESC' key to close the CentOS graphical splash screen with the blue/white bar at the bottom of the screen before it is all white - see [[bugzilla:7354]]<br />
* When system boots up it will ask you if you want to restore from backup (say no) and enter a root password, etc, and will reboot.<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', choose the desired configuration and then it ask you to reboot again.<br />
* Re-enable ssh access (the lazy not-so-secure way, but I am assuming for this testing/dev scenario that your external IP is really a local address behind a router)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Enable easier access to the server manager (modify as needed for your network)<br />
- I could not access the server manager from the console<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
db configuration setprop httpd-admin PermitPlainTextAccess yes <br />
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' <br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
Should be able to access https://yourserverip/server-manager/ now in a browser but seems that you have to log in here first - https://yourserverip/server-common/cgi-bin/login - Is that right? I think I'm missing something...Someone fix this part of the instructions please :-) - Oh, it could be [[bugzilla:7254]] causing part of that problem...<br />
* Save a snapshot in virtualbox so you can revert to this point if needed.<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
- the repo smeupdates-testing is not enabled by default. At this point in the development process you will probably want those rpms. This will check what is available: <br />
<pre><br />
yum --enablerepo=smeupdates-testing upgrade<br />
</pre><br />
<br />
== Some ideas for things to look for:==<br />
<br />
{{note box| <br />
In this Alpha ISO there are going to be a lot of strange things that might appear '''before''' doing a configure and reboot. Most of these things won't be of interest to us. Once we fix the configure and reboot part of the first-boot then we can really start looking at the issues that occur during install and first boot.<br />
<br />
If you notice any issues/bugs that occur '''after the initial config and reboot''' please continue to raise them.}}<br />
<br />
<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18834SME Server:9.0Alpha2013-02-19T17:55:54Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 14 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
There have as of now been 2 versions of the SME9Alpha1 ISO - check the date, this is current as for the Feb 14 2013 version.<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
{{note box| keep in mind you need to activate the PAE option of your virtualisation environment for playing with SME Server 9}}<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
<br />
If possible use something like zsync which will transfer just the chages to the ISO and not the whole file itself :<br />
<br />
:*You can get it for Debian/Ubuntu with <br />
sudo apt-get install zsync<br />
<br />
:*On CentOS/ RH you can get an RPM here http://pkgs.repoforge.org/zsync/<br />
<br />
You can then do the following : <br />
<br />
{{tip box|zsync http://mirror.contribs.org/releases/testing/9/iso/x86_64/smeserver-9.0alpha1-x86_64.iso.zsync<br />
<br />
zsync http://mirror.contribs.org/releases/testing/9/iso/i386/smeserver-9.0alpha1-i386.iso.zsync}}<br />
<br />
If the ISO changes, just run these commands again and it will propogate the changes, not the whole file.<br />
<br />
* Start the machine and choose the ISO image to boot from and install SME Server following the instructions.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- This is a temporary measure, and should work if you have the a DHCP server giving your external adapter (usually eth1) an IP address<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- enabling ssh now is not really needed, there isn't a long command to copy and paste anymore, so skip this if you like...This is also temporary, the hosts.allow file is templated and will be overwritten soon<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. After the post-upgrade/reboot the proper yum configuration is enabled.<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum upgrade to the latest the e-smith and smeserver packages<br />
- All the e-smith and smeserver packages needed are installed by the CD now, and bug [[bugzilla:7350]] is fixed with e-smith-base-5.4.0-10 so now the command is just:<br />
<pre style="white-space:normal;"><br />
yum --disablerepo=base,updates,extras upgrade --nogpg<br />
</pre><br />
* Save another snapshot<br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
- NOTE: press the 'ESC' key to close the CentOS graphical splash screen with the blue/white bar at the bottom of the screen before it is all white - see [[bugzilla:7354]]<br />
* When system boots up it will ask you if you want to restore from backup (say no) and enter a root password, etc, and will reboot.<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', choose the desired configuration and then it ask you to reboot again.<br />
* Re-enable ssh access (the lazy not-so-secure way, but I am assuming for this testing/dev scenario that your external IP is really a local address behind a router)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Enable easier access to the server manager (modify as needed for your network)<br />
- I could not access the server manager from the console<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
db configuration setprop httpd-admin PermitPlainTextAccess yes <br />
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' <br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
Should be able to access https://yourserverip/server-manager/ now in a browser but seems that you have to log in here first - https://yourserverip/server-common/cgi-bin/login - Is that right? I think I'm missing something...Someone fix this part of the instructions please :-) - Oh, it could be [[bugzilla:7254]] causing part of that problem...<br />
* Save another snapshot<br />
* to-do - check smeupdates-testing is enabled, and if not, enable it and do another yum upgrade<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
<br />
{{note box| <br />
In this Alpha ISO there are going to be a lot of strange things that might appear '''before''' doing a configure and reboot. Most of these things won't be of interest to us. Once we fix the configure and reboot part of the first-boot then we can really start looking at the issues that occur during install and first boot.<br />
<br />
If you notice any issues/bugs that occur '''after the initial config and reboot''' please continue to raise them.}}<br />
<br />
<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18833SME Server:9.0Alpha2013-02-19T17:25:58Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 14 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
There have as of now been 2 versions of the SME9Alpha1 ISO - check the date, this is current as for the Feb 14 2013 version.<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
{{note box| keep in mind you need to activate the PAE option of your virtualisation environment for playing with SME Server 9}}<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
<br />
If possible use something like zsync which will transfer just the chages to the ISO and not the whole file itself :<br />
<br />
:*You can get it for Debian/Ubuntu with <br />
sudo apt-get install zsync<br />
<br />
:*On CentOS/ RH you can get an RPM here http://pkgs.repoforge.org/zsync/<br />
<br />
You can then do the following : <br />
<br />
{{tip box|zsync http://mirror.contribs.org/releases/testing/9/iso/x86_64/smeserver-9.0alpha1-x86_64.iso.zsync<br />
<br />
zsync http://mirror.contribs.org/releases/testing/9/iso/i386/smeserver-9.0alpha1-i386.iso.zsync}}<br />
<br />
If the ISO changes, just run these commands again and it will propogate the changes, not the whole file.<br />
<br />
* Start the machine and choose the ISO image to boot from and install SME Server following the instructions.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- This is a temporary measure, and should work if you have the a DHCP server giving your external adapter (usually eth1) an IP address<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- For easier copy/paste of the next few commands...This is also temporary, the hosts.allow file is templated and will be overwritten soon<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. After the post-upgrade/reboot the proper yum configuration is enabled.<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install the e-smith and smeserver packages<br />
- Bug [[bugzilla:7350]] is fixed with e-smith-base-5.4.0-10 so now the command is just:<br />
<pre style="white-space:normal;"><br />
yum install smeserve\* e-smit\* --nogpg<br />
</pre><br />
(todo: fix the repo file and instructions to not have to add --nogpg)<br />
<br />
* Yum upgrade to see if there are other updates available<br />
- currently this does nothing, no other rpms are updated<br />
<pre><br />
yum upgrade<br />
</pre><br />
* Save another snapshot<br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
- NOTE: press the 'ESC' key to close the CentOS graphical splash screen with the blue/white bar at the bottom of the screen before it is all white - see [[bugzilla:7354]]<br />
* When system boots up it will ask you if you want to restore from backup (say no) and enter a root password, etc, and will reboot.<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', choose the desired configuration and then it ask you to reboot again.<br />
* Re-enable ssh access (the lazy not-so-secure way, but I am assuming for this testing/dev scenario that your external IP is really a local address behind a router)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Enable easier access to the server manager (modify as needed for your network)<br />
- I could not access the server manager from the console<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
db configuration setprop httpd-admin PermitPlainTextAccess yes <br />
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' <br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
Should be able to access https://yourserverip/server-manager/ now in a browser but seems that you have to log in here first - https://yourserverip/server-common/cgi-bin/login - Is that right? I think I'm missing something...Someone fix this part of the instructions please :-) - Oh, it could be [[bugzilla:7254]] causing part of that problem...<br />
* Save another snapshot<br />
* to-do - check smeupdates-testing is enabled, and if not, enable it and do another yum upgrade<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
<br />
{{note box| <br />
In this Alpha ISO there are going to be a lot of strange things that might appear '''before''' doing a configure and reboot. Most of these things won't be of interest to us. Once we fix the configure and reboot part of the first-boot then we can really start looking at the issues that occur during install and first boot.<br />
<br />
If you notice any issues/bugs that occur '''after the initial config and reboot''' please continue to raise them.}}<br />
<br />
<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18832SME Server:9.0Alpha2013-02-19T17:18:56Z<p>Gregswallow: change yum command now that bug 7350 is fixed</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 14 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
There have as of now been 2 versions of the SME9Alpha1 ISO - check the date, this is current as for the Feb 14 2013 version.<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
{{note box| keep in mind you need to activate the PAE option of your virtualisation environment for playing with SME Server 9}}<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
<br />
If possible use something like zsync which will transfer just the chages to the ISO and not the whole file itself :<br />
<br />
:*You can get it for Debian/Ubuntu with <br />
sudo apt-get install zsync<br />
<br />
:*On CentOS/ RH you can get an RPM here http://pkgs.repoforge.org/zsync/<br />
<br />
You can then do the following : <br />
<br />
{{tip box|zsync http://mirror.contribs.org/releases/testing/9/iso/x86_64/smeserver-9.0alpha1-x86_64.iso.zsync<br />
<br />
zsync http://mirror.contribs.org/releases/testing/9/iso/i386/smeserver-9.0alpha1-i386.iso.zsync}}<br />
<br />
If the ISO changes, just run these commands again and it will propogate the changes, not the whole file.<br />
<br />
* Start the machine and choose the ISO image to boot from and install SME Server following the instructions.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- This is a temporary measure, and should work if you have the a DHCP server giving your external adapter (usually eth1) an IP address<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- For easier copy/paste of the next few commands...This is also temporary, the hosts.allow file is templated and will be overwritten soon<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6<br />
- This is a temporary measure. After the post-upgrade/reboot the proper yum configuration is enabled.<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install the e-smith and smeserver packages<br />
- Bug [[bugzilla:7350]] is fixed with e-smith-base-5.4.0-10 so now the command is just:<br />
<pre style="white-space:normal;"><br />
yum install smeserve\* e-smit\* --nogpg<br />
</pre><br />
(todo: fix the repo file and instructions to not have to add --nogpg)<br />
<br />
* Yum upgrade to see if there are other updates available<br />
- currently this does nothing, no other rpms are updated<br />
<pre><br />
yum upgrade<br />
</pre><br />
* Save another snapshot<br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
- NOTE: press the 'ESC' key to close the CentOS graphical splash screen with the blue/white bar at the bottom of the screen before it is all white - see [[bugzilla:7354]]<br />
* When system boots up it will ask you if you want to restore from backup (say no) and enter a root password, etc, and will reboot.<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', choose the desired configuration and then it ask you to reboot again.<br />
* Re-enable ssh access (the lazy not-so-secure way, but I am assuming for this testing/dev scenario that your external IP is really a local address behind a router)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Enable easier access to the server manager (modify as needed for your network)<br />
- I could not access the server manager from the console<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
db configuration setprop httpd-admin PermitPlainTextAccess yes <br />
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' <br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
Should be able to access https://yourserverip/server-manager/ now in a browser but seems that you have to log in here first - https://yourserverip/server-common/cgi-bin/login - Is that right? I think I'm missing something...Someone fix this part of the instructions please :-) - Oh, it could be [[bugzilla:7254]] causing part of that problem...<br />
* Save another snapshot<br />
* to-do - check smeupdates-testing is enabled, and if not, enable it and do another yum upgrade<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
<br />
{{note box| <br />
In this Alpha ISO there are going to be a lot of strange things that might appear '''before''' doing a configure and reboot. Most of these things won't be of interest to us. Once we fix the configure and reboot part of the first-boot then we can really start looking at the issues that occur during install and first boot.<br />
<br />
If you notice any issues/bugs that occur '''after the initial config and reboot''' please continue to raise them.}}<br />
<br />
<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18626SME Server:9.0Alpha2013-02-15T18:13:32Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 14 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
There have as of now been 2 versions of the SME9Alpha1 ISO - check the date, this is current as for the Feb 14 2013 version.<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from and install SME Server following the instructions.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- This is a temporary measure, and should work if you have the a DHCP server giving your external adapter (usually eth1) an IP address<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- For easier copy/paste of the next few commands...This is also temporary, the hosts.allow file is templated and will be overwritten soon<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6<br />
- This is a temporary measure. After the post-upgrade/reboot the proper yum configuration is enabled.<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this has been reported in [[bugzilla:7350]]. The extra rpms listed below were in SME8 and may or may not be part of SME9, but they are all in the smeos repo<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap --nogpg<br />
</pre><br />
(todo: fix the repo file and instructions to not have to add --nogpg)<br />
* Yum upgrade to see if there are other updates available<br />
- currently this does nothing, no other rpms are updated<br />
<pre><br />
yum upgrade<br />
</pre><br />
* Save another snapshot<br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
- NOTE: press the 'ESC' key to close the CentOS graphical splash screen with the blue/white bar at the bottom of the screen before it is all white - see [[bugzilla:7354]]<br />
* When system boots up it will ask you if you want to restore from backup (say no) and enter a root password, etc, and will reboot.<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', choose the desired configuration and then it ask you to reboot again.<br />
* Re-enable ssh access (the lazy not-so-secure way, but I am assuming for this testing/dev scenario that your external IP is really a local address behind a router)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Enable easier access to the server manager (modify as needed for your network)<br />
- I could not access the server manager from the console<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
db configuration setprop httpd-admin PermitPlainTextAccess yes <br />
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' <br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
Should be able to access https://yourserverip/server-manager/ now in a browser but seems that you have to log in here first - https://yourserverip/server-common/cgi-bin/login - Is that right? I think I'm missing something...Someone fix this part of the instructions please :-) - Oh, it could be [[bugzilla:7254]] causing part of that problem...<br />
* Save another snapshot<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18606SME Server:9.0Alpha2013-02-15T09:37:57Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 14 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
There have as of now been 2 versions of the SME9Alpha1 ISO - check the date, this is current as for the Feb 14 2013 version.<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from and install SME Server following the instructions.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- This is a temporary measure, and should work if you have the a DHCP server giving your external adapter (usually eth1) an IP address<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- For easier copy/paste of the next few commands...This is also temporary, the hosts.allow file is templated and will be overwritten soon<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6<br />
- This is a temporary measure. After the post-upgrade/reboot the proper yum configuration is enabled.<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this has been reported in [[bugzilla:7350]]. The extra rpms listed below were in SME8 and may or may not be part of SME9, but they are all in the smeos repo<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap --nogpg<br />
</pre><br />
(todo: fix the repo file and instructions to not have to add --nogpg)<br />
* Yum upgrade to see if there are other updates available<br />
- currently this does nothing, no other rpms are updated<br />
<pre><br />
yum upgrade<br />
</pre><br />
* Save another snapshot<br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
- NOTE: press the 'ESC' key to close the CentOS graphical splash screen with the blue/white bar at the bottom of the screen before it is all white - see [[bugzilla:7354]]<br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', and should ask you to reboot to apply changes, if it does not, manually do post-upgrade/reboot. - Does it? I forgot to make a note of it...<br />
* Re-enable ssh access (the lazy not-so-secure way, but I am assuming for this testing/dev scenario that your external IP is really a local address behind a router)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Enable easier access to the server manager (modify as needed for your network)<br />
- I could not access the server manager from the console<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
db configuration setprop httpd-admin PermitPlainTextAccess yes <br />
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' <br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
Should be able to access https://yourserverip/server-manager/ now in a browser but seems that you have to log in here first - https://yourserverip/server-common/cgi-bin/login - Is that right? I think I'm missing something...Someone fix this part of the instructions please :-) - Oh, it could be [[bugzilla:7254]] causing part of that problem...<br />
* Save another snapshot<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18605SME Server:9.0Alpha2013-02-15T06:46:21Z<p>Gregswallow: /* Installing SME9 Alpha */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 14 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
There have as of now been 2 versions of the SME9Alpha1 ISO - check the date, this is current as for the Feb 14 2013 version.<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from and install SME Server following the instructions.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- This is a temporary measure, and should work if you have the a DHCP server giving your external adapter (usually eth1) an IP address<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- For easier copy/paste of the next few commands...This is also temporary, the hosts.allow file is templated and will be overwritten soon<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6<br />
- This is a temporary measure. After the post-upgrade/reboot the proper yum configuration is enabled.<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this has been reported in [[bugzilla:7350]]. The extra rpms listed below were in SME8 and may or may not be part of SME9, but they are all in the smeos repo<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap --nogpg<br />
</pre><br />
(todo: fix the repo file and instructions to not have to add --nogpg)<br />
* Yum upgrade to see if there are other updates available<br />
- currently this does nothing, no other rpms are updated<br />
<pre><br />
yum upgrade<br />
</pre><br />
* Save another snapshot<br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
- NOTE: press the 'ESC' key to close the CentOS graphical splash screen with the blue/white bar at the bottom of the screen before it is all white - see [[bugzilla:7354]]<br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', and should ask you to reboot to apply changes, if it does not, manually do post-upgrade/reboot. - Does it? I forgot to make a note of it...<br />
* Re-enable ssh access (the lazy not-so-secure way, but I am assuming for this testing/dev scenario that your external IP is really a local address behind a router)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Enable easier access to the server manager (modify as needed for your network)<br />
- I could not access the server manager from the console<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
db configuration setprop httpd-admin PermitPlainTextAccess yes <br />
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' <br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
Should be able to access https://yourserverip/server-manager/ now in a browser but seems that you have to log in here first - https://yourserverip/server-common/cgi-bin/login - Is that right? I think I'm missing something...Someone fix this part of the instructions please :-)<br />
* Save another snapshot<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_on_CentOS_6&diff=18604SME on CentOS 62013-02-15T06:45:13Z<p>Gregswallow: redirect to Alpha ISO instructions</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
These instructions are now out of date. Please see [[SME9Alpha | SME9Alpha]] instead.<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18603SME Server:9.0Alpha2013-02-15T06:41:11Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 14 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
There have as of now been 2 versions of the SME9Alpha1 ISO - check the date, this is current as for the Feb 14 2013 version.<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- This is a temporary measure, and should work if you have the a DHCP server giving your external adapter (usually eth1) an IP address<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- For easier copy/paste of the next few commands...This is also temporary, the hosts.allow file is templated and will be overwritten soon<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6<br />
- This is a temporary measure. After the post-upgrade/reboot the proper yum configuration is enabled.<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this has been reported in [[bugzilla:7350]]. The extra rpms listed below were in SME8 and may or may not be part of SME9, but they are all in the smeos repo<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap --nogpg<br />
</pre><br />
(todo: fix the repo file and instructions to not have to add --nogpg)<br />
* Yum upgrade to see if there are other updates available<br />
- currently this does nothing, no other rpms are updated<br />
<pre><br />
yum upgrade<br />
</pre><br />
* Save another snapshot<br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
- NOTE: press the 'ESC' key to close the CentOS graphical splash screen with the blue/white bar at the bottom of the screen before it is all white - see [[bugzilla:7354]]<br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', and should ask you to reboot to apply changes, if it does not, manually do post-upgrade/reboot. - Does it? I forgot to make a note of it...<br />
* Re-enable ssh access (the lazy not-so-secure way, but I am assuming for this testing/dev scenario that your external IP is really a local address behind a router)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Enable easier access to the server manager (modify as needed for your network)<br />
- I could not access the server manager from the console<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
db configuration setprop httpd-admin PermitPlainTextAccess yes <br />
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' <br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
Should be able to access https://yourserverip/server-manager/ now in a browser but seems that you have to log in here first - https://yourserverip/server-common/cgi-bin/login - Is that right? I think I'm missing something...Someone fix this part of the instructions please :-)<br />
* Save another snapshot<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18602SME Server:9.0Alpha2013-02-15T06:28:58Z<p>Gregswallow: /* SME 9 Alpha (Feb 13 2013 version) ISO Testing */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 14 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
There have as of now been 2 versions of the SME9Alpha1 ISO - check the date, this is current as for the Feb 14 2013 version.<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6<br />
- This is a temporary measure. After the post-upgrade/reboot the proper yum configuration is enabled.<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this has been reported in [[bugzilla:7350]]<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap --nogpg<br />
</pre><br />
(todo: fix the repo file and instructions to not have to add --nogpg)<br />
* Yum upgrade to see if there are other updates available<br />
<pre><br />
yum upgrade<br />
</pre><br />
* Save another snapshot<br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', will reboot to apply changes, if it does not reboot, manually do post-upgrade/reboot.<br />
* Re-enable ssh access (the lazy not-so-secure way)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Enable easier access to the server manager (modify as needed for your network)<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
db configuration setprop httpd-admin PermitPlainTextAccess yes <br />
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' <br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
Should be able to access https://yourserverip/server-manager/ now in a browser but seems that you have to log in here first - https://yourserverip/server-common/cgi-bin/login - Is that right? Someone fix this part of the instructions please....<br />
* Save another snapshot<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18601SME Server:9.0Alpha2013-02-15T06:23:45Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 13 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6<br />
- This is a temporary measure. After the post-upgrade/reboot the proper yum configuration is enabled.<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this has been reported in [[bugzilla:7350]]<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap --nogpg<br />
</pre><br />
(todo: fix the repo file and instructions to not have to add --nogpg)<br />
* Yum upgrade to see if there are other updates available<br />
<pre><br />
yum upgrade<br />
</pre><br />
* Save another snapshot<br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', will reboot to apply changes, if it does not reboot, manually do post-upgrade/reboot.<br />
* Re-enable ssh access (the lazy not-so-secure way)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Enable easier access to the server manager (modify as needed for your network)<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
db configuration setprop httpd-admin PermitPlainTextAccess yes <br />
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' <br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
Should be able to access https://yourserverip/server-manager/ now in a browser but seems that you have to log in here first - https://yourserverip/server-common/cgi-bin/login - Is that right? Someone fix this part of the instructions please....<br />
* Save another snapshot<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18600SME Server:9.0Alpha2013-02-15T06:08:24Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 13 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6<br />
- This is a temporary measure. After the post-upgrade/reboot the proper yum configuration is enabled.<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this has been reported in [[bugzilla:7350]]<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap --nogpg<br />
</pre><br />
(todo: fix the repo file and instructions to not have to add --nogpg)<br />
* Yum upgrade to see if there are other updates available<br />
<pre><br />
yum upgrade<br />
</pre><br />
* Save another snapshot<br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', will reboot to apply changes, if it does not reboot, manually do post-upgrade/reboot.<br />
* Re-enable ssh access (the lazy not-so-secure way)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Enable easier access to the server manager (modify as needed for your network)<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
db configuration setprop httpd-admin PermitPlainTextAccess yes <br />
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' <br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
Should be able to access https://yourserverip/server-manager/ now in a browser<br />
* Save another snapshot<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18599SME Server:9.0Alpha2013-02-15T05:57:45Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 13 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6<br />
- This is a temporary measure. After the post-upgrade/reboot the proper yum configuration is enabled.<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this has been reported in [[bugzilla:7350]]<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap --nogpg<br />
</pre><br />
(todo: fix the repo file and instructions to not have to add --nogpg)<br />
* Yum upgrade to see if there are other updates available<br />
<pre><br />
yum upgrade<br />
</pre><br />
* Save another snapshot<br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', will reboot to apply changes<br />
* Re-enable ssh access (the lazy not-so-secure way)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Enable easier access to the server manager (modify as needed for your network)<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
db configuration setprop httpd-admin PermitPlainTextAccess yes <br />
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' <br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
Should be able to access https://yourserverip/server-manager/ now in a browser<br />
* Save another snapshot<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18598SME Server:9.0Alpha2013-02-15T05:55:20Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 13 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this has been reported in [[bugzilla:7350]]<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap --nogpg<br />
</pre><br />
(todo: fix the repo file and instructions to not have to add --nogpg)<br />
* Yum upgrade to see if there are other updates available<br />
<pre><br />
yum upgrade<br />
</pre><br />
* Save another snapshot<br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', will reboot to apply changes<br />
* Re-enable ssh access (the lazy not-so-secure way)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Enable easier access to the server manager (modify as needed for your network)<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
db configuration setprop httpd-admin PermitPlainTextAccess yes <br />
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' <br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
Should be able to access https://yourserverip/server-manager/ now in a browser<br />
* Save another snapshot<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18597SME Server:9.0Alpha2013-02-14T23:21:25Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 13 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap --nogpg<br />
</pre><br />
(todo: fix the repo file and instructions to not have to add --nogpg)<br />
* Yum upgrade to see if there are other updates available<br />
<pre><br />
yum upgrade<br />
</pre><br />
* Save another snapshot<br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', will reboot to apply changes<br />
* Re-enable ssh access (the lazy not-so-secure way)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Enable easier access to the server manager (modify as needed for your network)<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
db configuration setprop httpd-admin PermitPlainTextAccess yes <br />
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' <br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
Should be able to access https://yourserverip/server-manager/ now in a browser<br />
* Save another snapshot<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18596SME Server:9.0Alpha2013-02-14T23:08:20Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 13 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap --nogpg<br />
</pre><br />
(todo: fix the repo file and instructions to not have to add --nogpg)<br />
* Yum upgrade to see if there are other updates available<br />
<pre><br />
yum upgrade<br />
</pre><br />
* Save another snapshot<br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', will reboot to apply changes<br />
* Re-enable ssh access (the lazy not-so-secure way)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Enable easier access to the server manager (modify as needed for your network)<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
db configuration setprop httpd-admin PermitPlainTextAccess yes <br />
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' <br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
Should be able to access https://yourserverip/server-manager/ now in a browser<br />
* Save another snapshot<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18595SME Server:9.0Alpha2013-02-14T22:07:07Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 13 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap --nogpg<br />
</pre><br />
(todo: fix the repo file and instructions to not have to add --nogpg)<br />
* Yum upgrade to see if there are other updates available<br />
<pre><br />
yum upgrade<br />
</pre><br />
* Save another snapshot<br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', will reboot to apply changes<br />
* Re-enable ssh access (the lazy not-so-secure way)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Enable easier access to the server manager (modify as needed for your network)<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
db configuration setprop httpd-admin PermitPlainTextAccess yes <br />
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' <br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
Should be able to access http://yourserverip/server-manager/ now in a browser<br />
* Save another snapshot<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18594SME Server:9.0Alpha2013-02-14T21:54:15Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 13 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap --nogpg<br />
</pre><br />
(todo: fix the repo file and instructions to not have to add --nogpg)<br />
* Yum upgrade to see if there are other updates available<br />
<pre><br />
yum upgrade<br />
</pre><br />
* Save another snapshot<br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', will reboot to apply changes<br />
* Re-enable ssh access (the lazy not-so-secure way)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* How to enable open access to server manager??? - this doesn't do it...<br />
<pre><br />
db configuration setprop httpd-admin access public<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Save another snapshot<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18593SME Server:9.0Alpha2013-02-14T21:44:06Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 13 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap --nogpg<br />
</pre><br />
(todo: fix the repo file and instructions to not have to add --nogpg)<br />
* Yum upgrade to see if there are other updates available<br />
<pre><br />
yum upgrade<br />
</pre><br />
* Save another snapshot<br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', will reboot to apply changes<br />
* Re-enable ssh access (the lazy not-so-secure way)<br />
<pre><br />
db configuration setprop sshd status enabled<br />
db configuration setprop sshd PermitRootLogin yes<br />
db configuration setprop sshd acccess public<br />
db configuration setprop sshd PasswordAuthentication yes<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
</pre><br />
* Save another snapshot<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18592SME Server:9.0Alpha2013-02-14T21:18:08Z<p>Gregswallow: /* SME 9 Alpha ISO Testing */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha (Feb 13 2013 version) ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap --nogpg<br />
</pre><br />
(todo: fix the repo file and instructions to not have to add --nogpg)<br />
* Yum upgrade to see if there are other updates available<br />
<pre><br />
yum upgrade<br />
</pre><br />
* Save another snapshot<br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', will reboot to apply changes<br />
* Save another snapshot<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18591SME Server:9.0Alpha2013-02-14T21:10:47Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap --nogpg<br />
</pre><br />
(todo: fix the repo file and instructions to not have to add --nogpg)<br />
* Yum upgrade to see if there are other updates available<br />
<pre><br />
yum upgrade<br />
</pre><br />
* Save another snapshot<br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', will reboot to apply changes<br />
* Save another snapshot<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18589SME Server:9.0Alpha2013-02-14T20:47:00Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap<br />
</pre><br />
* Yum upgrade to see if there are other updates available<br />
<pre><br />
yum upgrade<br />
</pre><br />
* Save another snapshot<br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server', will reboot to apply changes<br />
* Save another snapshot<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18588SME Server:9.0Alpha2013-02-14T20:40:17Z<p>Gregswallow: </p>
<hr />
<div>Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap<br />
</pre><br />
* Yum upgrade to see if there are other updates available<br />
<pre><br />
yum upgrade<br />
</pre><br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server'<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18587SME Server:9.0Alpha2013-02-14T20:39:43Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this has been reported in [[bugzilla:???]]<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap<br />
</pre><br />
* Yum upgrade to see if there are other updates available<br />
<pre><br />
yum upgrade<br />
</pre><br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server'<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18586SME Server:9.0Alpha2013-02-14T20:34:48Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Some packages in smeos8,smeupdates8 are excluded as the versions are higher than in el6<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap<br />
</pre><br />
* Yum upgrade to see if there are other updates available<br />
<pre><br />
yum upgrade<br />
</pre><br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server'<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18585SME Server:9.0Alpha2013-02-14T20:22:23Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Some packages in smeos8,smeupdates8 are excluded as the versions are higher than in el6<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=____<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre style="white-space:normal;"><br />
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap<br />
</pre><br />
* Yum upgrade to see if there are other updates available<br />
<pre><br />
yum upgrade<br />
</pre><br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server'<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18584SME Server:9.0Alpha2013-02-14T20:01:33Z<p>Gregswallow: /* Bugs */</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
* Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]<br />
* SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. <br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=____<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre style="white-space:normal;"><br />
yum install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap<br />
</pre><br />
* Yum upgrade to see if there are other updates available<br />
<pre><br />
yum upgrade<br />
</pre><br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server'<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18583SME Server:9.0Alpha2013-02-14T19:58:56Z<p>Gregswallow: /* After first reboot */</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
Check the recent activity in the SME9 category:<br />
[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948]<br />
SME9 Bugs by type / status: <br />
http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. <br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=____<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre style="white-space:normal;"><br />
yum install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap<br />
</pre><br />
* Yum upgrade to see if there are other updates available<br />
<pre><br />
yum upgrade<br />
</pre><br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server'<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&diff=18582SME Server:9.0Alpha2013-02-14T19:57:44Z<p>Gregswallow: Created page with "{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}} Back to [[SME_Se..."</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9 Alpha ISO Testing ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
=== User Feedback ===<br />
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
=== Bugs ===<br />
Check the recent activity in the SME9 category:<br />
[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948]<br />
SME9 Bugs by type / status: <br />
http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap]<br />
<br />
== Installing SME9 Alpha ==<br />
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.<br />
* Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it.<br />
* Start the machine and choose the ISO image to boot from.<br />
<br />
== After first reboot ==<br />
* Save a snapshot<br />
* Login as root and enable networking:<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
ifup eth0<br />
ifup eth1<br />
</pre><br />
* enable ssh for access from Putty or other SSH client<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
echo "ALL:ALL" >> /etc/hosts.allow<br />
service sshd reload<br />
</pre><br />
* Configure SME9 repositories<br />
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. <br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=____<br />
</pre><br />
* Yum install some packages not installed by the CD<br />
- The necessity of doing this manually has been reported in [[bugzilla:???]]<br />
<pre><br />
yum install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap<br />
</pre><br />
* Yum upgrade to see if there are other updates available<br />
<pre><br />
yum upgrade<br />
</pre><br />
* post-upgrade / reboot<br />
<pre><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</pre><br />
* Save another snapshot<br />
* Configure the server<br />
- log in as root and run 'console' and select 'configure this server'<br />
* Look for things to fix & Report bugs/problems<br />
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
== Some ideas for things to look for:==<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* Look in the various log files for clues to problems<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_on_CentOS_6&diff=18545SME on CentOS 62013-02-13T09:58:20Z<p>Gregswallow: /* Move everything from rc7.d to rc4.d */</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9, based on CentOS 6 ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
<br />
=== Prerequisites ===<br />
* VIrtual machine (Vmware, Parallels or Virtualbox)<br />
* Centos Minimal 64-bit architecture. 32-bit may follow later<br />
* [[Setting_up_RPM_Building_for_SME_Server|Setting up a RPM Building environment]]<br />
<br />
=== User Feedback ===<br />
Unstructured user feedback can be noted here: [[SME9DEV_user_feedback|SME9DEV user feedback]]. Issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
<br />
=== Bugs ===<br />
[http://bugs.contribs.org/bugs/buglist.cgi?product=SME%20Server%209.X&component=Cleanup&resolution=--- Bug Tracker] <br />
[http://wiki.contribs.org/SME9BuildQueue#SME_9_Error_list_and_affected_packages SME 9 error list]<br />
<br />
=== Considerations ===<br />
* Primary and only goal for now is the transition of SME Server based on CentOS 5.8 to SME Server based on CentOS6.3<br />
* SysVinit is no longer the default with the release of RHEL6, beyond RHEL6 systemd will be used<br />
* perl has a new location of the filesystem. New: /usr/share/perl5/vendor_perl instead Old: /usr/lib/perl5/site_perl/<br />
* perl version 5.8.8 is the new default version on RHEL6. This requires a review of all the perl module rpms which are specific for perl 5.8.5<br />
<br />
== Installing CentOS 6 minimal ==<br />
First a few notes on CentOS 6 minimal, which is a bare bones install with very little on board. You can download a copy from one of the CentOS mirrors [http://www.centos.org/modules/tinycontent/index.php?id=30 here]<br />
<br />
* As per above note, only use Virtual Machine for testing purposes. A good free VM package can be obtained [https://www.virtualbox.org/wiki/Downloads here]<br />
* You might want to note down as much as possible so you yourself and others can reproduce the actions<br />
* Don't use yum with the '-y' flag (install/upgrade without further user interaction) when using the yum install/upgrade commands. (beware copy/paste yum commands)<br />
* you might want to note down all packages listed by yum to be installed/upgraded AND their dependencies<br />
* Make regular snapshots of your Virtual Machine and describe them specifically. At least when you've reached an important milestone for yourself<br />
<br />
<br />
==== Installing the ISO ====<br />
* Just install a minimal el6 installation (I just installed a few utilities like htop, screen, rsync, vim, openssh-clients mc etc…). You can use either the DVD, the minimal CD install, a net install with PXE, it's up to you<br />
* wellsi: I have used CentOS-6.3-x86_64-minimal.iso<br />
<br />
<br />
==== Enable networking ====<br />
Each boot you have to start the network etc etc. I decided it was better with the minimal install and touch as little as possible - if I could then get SME packages installed I could then use that to configure networking later.<br />
<br />
To start the networking <br />
<syntaxhighlight lang="Bash"><br />
./etc/sysconfig/network-scripts/ifup-eth eth0<br />
</syntaxhighlight><br />
<br />
or <br />
<syntaxhighlight lang="Bash"><br />
dhclient eth0<br />
</syntaxhighlight><br />
<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="Collapse" data-expandtext="More on networking"><br />
or if you want to assign a specific IP address (e.g. 192.168.1.2).<br />
<syntaxhighlight lang="Bash"><br />
ifconfig eth0 192.168.1.2<br />
echo "nameserver 192.168.1.254" >> /etc/resolv.conf<br />
route add default gw 192.168.1.254 eth0<br />
</syntaxhighlight> <br />
<br />
To make your changes permanent you will need to edit the configuration file to make it active on boot. There is only the vi text editor, you can also install nano. <br />
<syntaxhighlight lang="Bash"><br />
yum install nano<br />
nano /etc/sysconfig/network-scripts/ifcfg-eth0<br />
</syntaxhighlight><br />
and set ONBOOT=”YES”<br />
</div><br />
<br />
==== Enable SSH ====<br />
SSH is present but is disabled at this stage. To enable ssh issue:<br />
<syntaxhighlight lang="Bash"><br />
service sshd start<br />
</syntaxhighlight><br />
<br />
<br />
==== Disable / Remove SELinux ====<br />
It will be easier to see what's going on (and turn off selinux at kernel level, just to be sure)<br />
<syntaxhighlight lang="Bash"><br />
sed -i -e 's/rhgb quiet/selinux=0/g' /boot/grub/grub.conf<br />
<br />
sed -i -e 's/SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config<br />
<br />
yum remove selinux-policy-targeted<br />
<br />
setenforce 0<br />
</syntaxhighlight><br />
<br />
== Configure basic requirements ==<br />
==== Configure SME9 repositories ====<br />
<br />
See the following bugs tracking issues with repositories:<br />
* [[bugzilla:7294|Bug #7294: rpms that still need to be rebuilt or sourced for the SME9 repositories]]<br />
* [[bugzilla:7298|Bug #7298: Import perl-Unix-ConfigFile from rpmforge]]<br />
* [[bugzilla:7292|Bug #7292: more rpms in the SME8 repositories that have a lower version in our SME9 repositories]]<br />
* [[bugzilla:7305|Bug #7305: smeserver-yum doesn't provide the /etc/yum.smerepos.d dir]]<br />
<br />
<syntaxhighlight lang="Bash"><br />
yum install wget<br />
</syntaxhighlight><br />
<syntaxhighlight lang="Bash"><br />
mkdir /tmp/repo.bak<br />
mv /etc/yum.repos.d/*.repo /tmp/repo.bak/<br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3652<br />
</syntaxhighlight><br />
<br />
==== Import needed GPG Keys ====<br />
<syntaxhighlight lang="Bash"><br />
rpm --import http://sme-mirror.firewall-services.com/releases/8/smeos/x86_64/RPM-GPG-KEY-SMEServer<br />
rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt<br />
rpm --import https://fedoraproject.org/static/217521F6.txt<br />
rpm --import http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br />
rpm --import http://www.salstar.sk/pub/yum/keys/RPM-GPG-KEY-Fedora-Pre-Extras<br />
</syntaxhighlight><br />
<br />
==== Clean yum cache ====<br />
<syntaxhighlight lang="Bash"><br />
yum --enablerepo=* clean all<br />
</syntaxhighlight><br />
<br />
==== Install e-smith and smeserver packages & update all packages====<br />
Now, you should be ready to install all the e-smith and smeserver packages (and their dependencies), plus the rest of the rpms that aren't required by a smeserver- or e-smith- rpm, but were installed on SME8 [[bugzilla:7311]]. This should pull about 500 packages to install, and 14 to update, and then you can do 'yum upgrade' to upgrade the remaining CentOS packages. Some other notes on this in [[bugzilla:7240]]<br />
<br />
<pre style="white-space:normal;"> <br />
yum --disablerepo=* --enablerepo=smeupdates9,smeupdates-testing9,smeos8,smeupdates8 install e-smith\* smeserver\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap<br />
</pre><br />
<br />
<pre><br />
yum upgrade<br />
</pre><br />
<br />
See the following bugs:<br />
*[[bugzilla:7233|Bug #7233: e-smith-ldap should require openldap-servers]]<br />
*[[bugzilla:7252|Bug #7252: e-smith-radiusd should require freeradius-ldap]]<br />
*[[bugzilla:7234|Bug #7234: e-smith-apache should require mod_ssl]]<br />
*[[bugzilla:7297|Bug #7297: e-smith-hosts should require dhcp]]<br />
<br />
==== Move some perl modules ====<br />
We need to copy some perl modules to a new directory, because @INC has changed in EL6: [[bugzilla:7223]]<br />
<syntaxhighlight lang="Bash"><br />
cp -a /usr/lib/perl5/site_perl/esmith/* /usr/share/perl5/vendor_perl/esmith<br />
</syntaxhighlight><br />
<br />
==== Run post-upgrade ====<br />
We can now try to post-upgrade<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</syntaxhighlight><br />
<br />
== Look for things to fix & Report bugs/problems ==<br />
<br />
To configure the server further, log in as root at then type 'console' and select 'configure this server'. <br />
<br />
If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
* [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap SME 9 Bug Report Matrix]<br />
* Open a new bug report - http://bugs.contribs.org/enter_bug.cgi<br />
<br />
Some ideas for things to look for:<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* what el5 packages are still installed that need working on? To check do<br />
<pre><br />
rpm -qa |grep el5<br />
</pre><br />
*<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_on_CentOS_6&diff=18528SME on CentOS 62013-02-12T22:48:34Z<p>Gregswallow: /* Install e-smith and smeserver packages & update all packages */</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9, based on CentOS 6 ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
<br />
=== Prerequisites ===<br />
* VIrtual machine (Vmware, Parallels or Virtualbox)<br />
* Centos Minimal 64-bit architecture. 32-bit may follow later<br />
* [[Setting_up_RPM_Building_for_SME_Server|Setting up a RPM Building environment]]<br />
<br />
=== User Feedback ===<br />
Unstructured user feedback can be noted here: [[SME9DEV_user_feedback|SME9DEV user feedback]]. Issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
<br />
=== Bugs ===<br />
[http://bugs.contribs.org/bugs/buglist.cgi?product=SME%20Server%209.X&component=Cleanup&resolution=--- Bug Tracker] <br />
[http://wiki.contribs.org/SME9BuildQueue#SME_9_Error_list_and_affected_packages SME 9 error list]<br />
<br />
=== Considerations ===<br />
* Primary and only goal for now is the transition of SME Server based on CentOS 5.8 to SME Server based on CentOS6.3<br />
* SysVinit is no longer the default with the release of RHEL6, beyond RHEL6 systemd will be used<br />
* perl has a new location of the filesystem. New: /usr/share/perl5/vendor_perl instead Old: /usr/lib/perl5/site_perl/<br />
* perl version 5.8.8 is the new default version on RHEL6. This requires a review of all the perl module rpms which are specific for perl 5.8.5<br />
<br />
== Installing CentOS 6 minimal ==<br />
First a few notes on CentOS 6 minimal, which is a bare bones install with very little on board. You can download a copy from one of the CentOS mirrors [http://www.centos.org/modules/tinycontent/index.php?id=30 here]<br />
<br />
* As per above note, only use Virtual Machine for testing purposes. A good free VM package can be obtained [https://www.virtualbox.org/wiki/Downloads here]<br />
* You might want to note down as much as possible so you yourself and others can reproduce the actions<br />
* Don't use yum with the '-y' flag (install/upgrade without further user interaction) when using the yum install/upgrade commands. (beware copy/paste yum commands)<br />
* you might want to note down all packages listed by yum to be installed/upgraded AND their dependencies<br />
* Make regular snapshots of your Virtual Machine and describe them specifically. At least when you've reached an important milestone for yourself<br />
<br />
<br />
==== Installing the ISO ====<br />
* Just install a minimal el6 installation (I just installed a few utilities like htop, screen, rsync, vim, openssh-clients mc etc…). You can use either the DVD, the minimal CD install, a net install with PXE, it's up to you<br />
* wellsi: I have used CentOS-6.3-x86_64-minimal.iso<br />
<br />
<br />
==== Enable networking ====<br />
Each boot you have to start the network etc etc. I decided it was better with the minimal install and touch as little as possible - if I could then get SME packages installed I could then use that to configure networking later.<br />
<br />
To start the networking <br />
<syntaxhighlight lang="Bash"><br />
./etc/sysconfig/network-scripts/ifup-eth eth0<br />
</syntaxhighlight><br />
<br />
or <br />
<syntaxhighlight lang="Bash"><br />
dhclient eth0<br />
</syntaxhighlight><br />
<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="Collapse" data-expandtext="More on networking"><br />
or if you want to assign a specific IP address (e.g. 192.168.1.2).<br />
<syntaxhighlight lang="Bash"><br />
ifconfig eth0 192.168.1.2<br />
echo "nameserver 192.168.1.254" >> /etc/resolv.conf<br />
route add default gw 192.168.1.254 eth0<br />
</syntaxhighlight> <br />
<br />
To make your changes permanent you will need to edit the configuration file to make it active on boot. There is only the vi text editor, you can also install nano. <br />
<syntaxhighlight lang="Bash"><br />
yum install nano<br />
nano /etc/sysconfig/network-scripts/ifcfg-eth0<br />
</syntaxhighlight><br />
and set ONBOOT=”YES”<br />
</div><br />
<br />
==== Enable SSH ====<br />
SSH is present but is disabled at this stage. To enable ssh issue:<br />
<syntaxhighlight lang="Bash"><br />
service sshd start<br />
</syntaxhighlight><br />
<br />
<br />
==== Disable / Remove SELinux ====<br />
It will be easier to see what's going on (and turn off selinux at kernel level, just to be sure)<br />
<syntaxhighlight lang="Bash"><br />
sed -i -e 's/rhgb quiet/selinux=0/g' /boot/grub/grub.conf<br />
<br />
sed -i -e 's/SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config<br />
<br />
yum remove selinux-policy-targeted<br />
<br />
setenforce 0<br />
</syntaxhighlight><br />
<br />
== Configure basic requirements ==<br />
==== Configure SME9 repositories ====<br />
<br />
See the following bugs tracking issues with repositories:<br />
* [[bugzilla:7294|Bug #7294: rpms that still need to be rebuilt or sourced for the SME9 repositories]]<br />
* [[bugzilla:7298|Bug #7298: Import perl-Unix-ConfigFile from rpmforge]]<br />
* [[bugzilla:7292|Bug #7292: more rpms in the SME8 repositories that have a lower version in our SME9 repositories]]<br />
* [[bugzilla:7305|Bug #7305: smeserver-yum doesn't provide the /etc/yum.smerepos.d dir]]<br />
<br />
<syntaxhighlight lang="Bash"><br />
yum install wget<br />
</syntaxhighlight><br />
<syntaxhighlight lang="Bash"><br />
mkdir /tmp/repo.bak<br />
mv /etc/yum.repos.d/*.repo /tmp/repo.bak/<br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3652<br />
</syntaxhighlight><br />
<br />
==== Import needed GPG Keys ====<br />
<syntaxhighlight lang="Bash"><br />
rpm --import http://sme-mirror.firewall-services.com/releases/8/smeos/x86_64/RPM-GPG-KEY-SMEServer<br />
rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt<br />
rpm --import https://fedoraproject.org/static/217521F6.txt<br />
rpm --import http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br />
rpm --import http://www.salstar.sk/pub/yum/keys/RPM-GPG-KEY-Fedora-Pre-Extras<br />
</syntaxhighlight><br />
<br />
==== Clean yum cache ====<br />
<syntaxhighlight lang="Bash"><br />
yum --enablerepo=* clean all<br />
</syntaxhighlight><br />
<br />
==== Install e-smith and smeserver packages & update all packages====<br />
Now, you should be ready to install all the e-smith and smeserver packages (and their dependencies), plus the rest of the rpms that aren't required by a smeserver- or e-smith- rpm, but were installed on SME8 [[bugzilla:7311]]. This should pull about 500 packages to install, and 14 to update, and then you can do 'yum upgrade' to upgrade the remaining CentOS packages. Some other notes on this in [[bugzilla:7240]]<br />
<br />
<pre style="white-space:normal;"> <br />
yum --disablerepo=* --enablerepo=smeupdates9,smeupdates-testing9,smeos8,smeupdates8 install e-smith\* smeserver\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap<br />
</pre><br />
<br />
<pre><br />
yum upgrade<br />
</pre><br />
<br />
See the following bugs:<br />
*[[bugzilla:7233|Bug #7233: e-smith-ldap should require openldap-servers]]<br />
*[[bugzilla:7252|Bug #7252: e-smith-radiusd should require freeradius-ldap]]<br />
*[[bugzilla:7234|Bug #7234: e-smith-apache should require mod_ssl]]<br />
*[[bugzilla:7297|Bug #7297: e-smith-hosts should require dhcp]]<br />
<br />
==== Move everything from rc7.d to rc4.d ====<br />
More info in [[bugzilla:7217]]<br />
All the links in rc4.d should then point to e-smith-service<br />
<syntaxhighlight lang="Bash"><br />
rm -f /etc/rc4.d/*<br />
cp -a /etc/rc7.d/* /etc/rc4.d/<br />
</syntaxhighlight><br />
<br />
==== Move some perl modules ====<br />
We need to copy some perl modules to a new directory, because @INC has changed in EL6: [[bugzilla:7223]]<br />
<syntaxhighlight lang="Bash"><br />
cp -a /usr/lib/perl5/site_perl/esmith/* /usr/share/perl5/vendor_perl/esmith<br />
</syntaxhighlight><br />
<br />
==== Run post-upgrade ====<br />
We can now try to post-upgrade<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</syntaxhighlight><br />
<br />
== Look for things to fix & Report bugs/problems ==<br />
<br />
To configure the server further, log in as root at then type 'console' and select 'configure this server'. <br />
<br />
If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
* [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap SME 9 Bug Report Matrix]<br />
* Open a new bug report - http://bugs.contribs.org/enter_bug.cgi<br />
<br />
Some ideas for things to look for:<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* what el5 packages are still installed that need working on? To check do<br />
<pre><br />
rpm -qa |grep el5<br />
</pre><br />
*<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_on_CentOS_6&diff=18527SME on CentOS 62013-02-12T22:43:39Z<p>Gregswallow: /* Install e-smith and smeserver packages & update all packages */</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9, based on CentOS 6 ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
<br />
=== Prerequisites ===<br />
* VIrtual machine (Vmware, Parallels or Virtualbox)<br />
* Centos Minimal 64-bit architecture. 32-bit may follow later<br />
* [[Setting_up_RPM_Building_for_SME_Server|Setting up a RPM Building environment]]<br />
<br />
=== User Feedback ===<br />
Unstructured user feedback can be noted here: [[SME9DEV_user_feedback|SME9DEV user feedback]]. Issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
<br />
=== Bugs ===<br />
[http://bugs.contribs.org/bugs/buglist.cgi?product=SME%20Server%209.X&component=Cleanup&resolution=--- Bug Tracker] <br />
[http://wiki.contribs.org/SME9BuildQueue#SME_9_Error_list_and_affected_packages SME 9 error list]<br />
<br />
=== Considerations ===<br />
* Primary and only goal for now is the transition of SME Server based on CentOS 5.8 to SME Server based on CentOS6.3<br />
* SysVinit is no longer the default with the release of RHEL6, beyond RHEL6 systemd will be used<br />
* perl has a new location of the filesystem. New: /usr/share/perl5/vendor_perl instead Old: /usr/lib/perl5/site_perl/<br />
* perl version 5.8.8 is the new default version on RHEL6. This requires a review of all the perl module rpms which are specific for perl 5.8.5<br />
<br />
== Installing CentOS 6 minimal ==<br />
First a few notes on CentOS 6 minimal, which is a bare bones install with very little on board. You can download a copy from one of the CentOS mirrors [http://www.centos.org/modules/tinycontent/index.php?id=30 here]<br />
<br />
* As per above note, only use Virtual Machine for testing purposes. A good free VM package can be obtained [https://www.virtualbox.org/wiki/Downloads here]<br />
* You might want to note down as much as possible so you yourself and others can reproduce the actions<br />
* Don't use yum with the '-y' flag (install/upgrade without further user interaction) when using the yum install/upgrade commands. (beware copy/paste yum commands)<br />
* you might want to note down all packages listed by yum to be installed/upgraded AND their dependencies<br />
* Make regular snapshots of your Virtual Machine and describe them specifically. At least when you've reached an important milestone for yourself<br />
<br />
<br />
==== Installing the ISO ====<br />
* Just install a minimal el6 installation (I just installed a few utilities like htop, screen, rsync, vim, openssh-clients mc etc…). You can use either the DVD, the minimal CD install, a net install with PXE, it's up to you<br />
* wellsi: I have used CentOS-6.3-x86_64-minimal.iso<br />
<br />
<br />
==== Enable networking ====<br />
Each boot you have to start the network etc etc. I decided it was better with the minimal install and touch as little as possible - if I could then get SME packages installed I could then use that to configure networking later.<br />
<br />
To start the networking <br />
<syntaxhighlight lang="Bash"><br />
./etc/sysconfig/network-scripts/ifup-eth eth0<br />
</syntaxhighlight><br />
<br />
or <br />
<syntaxhighlight lang="Bash"><br />
dhclient eth0<br />
</syntaxhighlight><br />
<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="Collapse" data-expandtext="More on networking"><br />
or if you want to assign a specific IP address (e.g. 192.168.1.2).<br />
<syntaxhighlight lang="Bash"><br />
ifconfig eth0 192.168.1.2<br />
echo "nameserver 192.168.1.254" >> /etc/resolv.conf<br />
route add default gw 192.168.1.254 eth0<br />
</syntaxhighlight> <br />
<br />
To make your changes permanent you will need to edit the configuration file to make it active on boot. There is only the vi text editor, you can also install nano. <br />
<syntaxhighlight lang="Bash"><br />
yum install nano<br />
nano /etc/sysconfig/network-scripts/ifcfg-eth0<br />
</syntaxhighlight><br />
and set ONBOOT=”YES”<br />
</div><br />
<br />
==== Enable SSH ====<br />
SSH is present but is disabled at this stage. To enable ssh issue:<br />
<syntaxhighlight lang="Bash"><br />
service sshd start<br />
</syntaxhighlight><br />
<br />
<br />
==== Disable / Remove SELinux ====<br />
It will be easier to see what's going on (and turn off selinux at kernel level, just to be sure)<br />
<syntaxhighlight lang="Bash"><br />
sed -i -e 's/rhgb quiet/selinux=0/g' /boot/grub/grub.conf<br />
<br />
sed -i -e 's/SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config<br />
<br />
yum remove selinux-policy-targeted<br />
<br />
setenforce 0<br />
</syntaxhighlight><br />
<br />
== Configure basic requirements ==<br />
==== Configure SME9 repositories ====<br />
<br />
See the following bugs tracking issues with repositories:<br />
* [[bugzilla:7294|Bug #7294: rpms that still need to be rebuilt or sourced for the SME9 repositories]]<br />
* [[bugzilla:7298|Bug #7298: Import perl-Unix-ConfigFile from rpmforge]]<br />
* [[bugzilla:7292|Bug #7292: more rpms in the SME8 repositories that have a lower version in our SME9 repositories]]<br />
* [[bugzilla:7305|Bug #7305: smeserver-yum doesn't provide the /etc/yum.smerepos.d dir]]<br />
<br />
<syntaxhighlight lang="Bash"><br />
yum install wget<br />
</syntaxhighlight><br />
<syntaxhighlight lang="Bash"><br />
mkdir /tmp/repo.bak<br />
mv /etc/yum.repos.d/*.repo /tmp/repo.bak/<br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3652<br />
</syntaxhighlight><br />
<br />
==== Import needed GPG Keys ====<br />
<syntaxhighlight lang="Bash"><br />
rpm --import http://sme-mirror.firewall-services.com/releases/8/smeos/x86_64/RPM-GPG-KEY-SMEServer<br />
rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt<br />
rpm --import https://fedoraproject.org/static/217521F6.txt<br />
rpm --import http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br />
rpm --import http://www.salstar.sk/pub/yum/keys/RPM-GPG-KEY-Fedora-Pre-Extras<br />
</syntaxhighlight><br />
<br />
==== Clean yum cache ====<br />
<syntaxhighlight lang="Bash"><br />
yum --enablerepo=* clean all<br />
</syntaxhighlight><br />
<br />
==== Install e-smith and smeserver packages & update all packages====<br />
Now, you should be ready to install all the e-smith and smeserver packages (and their dependencies), plus the rest of the rpms that aren't required by a smeserver- or e-smith- rpm, but were installed on SME8 [[bugzilla:7311]]. This should pull about 500 packages to install, and 14 to update, and then you can do 'yum upgrade' to upgrade the remaining CentOS packages. Some other notes on this in [[bugzilla:7240]]<br />
<br />
<pre style="white-space:normal;"> <br />
yum --disablerepo=* --enablerepo=smeupdates9,smeupdates-testing9,smeos8,smeupdates8 install e-smith\* smeserver\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef<br />
</pre><br />
<br />
<pre><br />
yum upgrade<br />
</pre><br />
<br />
See the following bugs:<br />
*[[bugzilla:7233|Bug #7233: e-smith-ldap should require openldap-servers]]<br />
*[[bugzilla:7252|Bug #7252: e-smith-radiusd should require freeradius-ldap]]<br />
*[[bugzilla:7234|Bug #7234: e-smith-apache should require mod_ssl]]<br />
*[[bugzilla:7297|Bug #7297: e-smith-hosts should require dhcp]]<br />
<br />
==== Move everything from rc7.d to rc4.d ====<br />
More info in [[bugzilla:7217]]<br />
All the links in rc4.d should then point to e-smith-service<br />
<syntaxhighlight lang="Bash"><br />
rm -f /etc/rc4.d/*<br />
cp -a /etc/rc7.d/* /etc/rc4.d/<br />
</syntaxhighlight><br />
<br />
==== Move some perl modules ====<br />
We need to copy some perl modules to a new directory, because @INC has changed in EL6: [[bugzilla:7223]]<br />
<syntaxhighlight lang="Bash"><br />
cp -a /usr/lib/perl5/site_perl/esmith/* /usr/share/perl5/vendor_perl/esmith<br />
</syntaxhighlight><br />
<br />
==== Run post-upgrade ====<br />
We can now try to post-upgrade<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</syntaxhighlight><br />
<br />
== Look for things to fix & Report bugs/problems ==<br />
<br />
To configure the server further, log in as root at then type 'console' and select 'configure this server'. <br />
<br />
If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
* [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap SME 9 Bug Report Matrix]<br />
* Open a new bug report - http://bugs.contribs.org/enter_bug.cgi<br />
<br />
Some ideas for things to look for:<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* what el5 packages are still installed that need working on? To check do<br />
<pre><br />
rpm -qa |grep el5<br />
</pre><br />
*<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_on_CentOS_6&diff=18505SME on CentOS 62013-02-12T20:21:06Z<p>Gregswallow: /* Install e-smith and smeserver packages & update all packages */</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9, based on CentOS 6 ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
<br />
=== Prerequisites ===<br />
* VIrtual machine (Vmware, Parallels or Virtualbox)<br />
* Centos Minimal 64-bit architecture. 32-bit may follow later<br />
* [[Setting_up_RPM_Building_for_SME_Server|Setting up a RPM Building environment]]<br />
<br />
=== User Feedback ===<br />
Unstructured user feedback can be noted here: [[SME9DEV_user_feedback|SME9DEV user feedback]]. Issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
<br />
=== Bugs ===<br />
[http://bugs.contribs.org/bugs/buglist.cgi?product=SME%20Server%209.X&component=Cleanup&resolution=--- Bug Tracker] <br />
[http://wiki.contribs.org/SME9BuildQueue#SME_9_Error_list_and_affected_packages SME 9 error list]<br />
<br />
=== Considerations ===<br />
* Primary and only goal for now is the transition of SME Server based on CentOS 5.8 to SME Server based on CentOS6.3<br />
* SysVinit is no longer the default with the release of RHEL6, beyond RHEL6 systemd will be used<br />
* perl has a new location of the filesystem. New: /usr/share/perl5/vendor_perl instead Old: /usr/lib/perl5/site_perl/<br />
* perl version 5.8.8 is the new default version on RHEL6. This requires a review of all the perl module rpms which are specific for perl 5.8.5<br />
<br />
== Installing CentOS 6 minimal ==<br />
First a few notes on CentOS 6 minimal, which is a bare bones install with very little on board. You can download a copy from one of the CentOS mirrors [http://www.centos.org/modules/tinycontent/index.php?id=30 here]<br />
<br />
* As per above note, only use Virtual Machine for testing purposes. A good free VM package can be obtained [https://www.virtualbox.org/wiki/Downloads here]<br />
* You might want to note down as much as possible so you yourself and others can reproduce the actions<br />
* Don't use yum with the '-y' flag (install/upgrade without further user interaction) when using the yum install/upgrade commands. (beware copy/paste yum commands)<br />
* you might want to note down all packages listed by yum to be installed/upgraded AND their dependencies<br />
* Make regular snapshots of your Virtual Machine and describe them specifically. At least when you've reached an important milestone for yourself<br />
<br />
<br />
==== Installing the ISO ====<br />
* Just install a minimal el6 installation (I just installed a few utilities like htop, screen, rsync, vim, openssh-clients mc etc…). You can use either the DVD, the minimal CD install, a net install with PXE, it's up to you<br />
* wellsi: I have used CentOS-6.3-x86_64-minimal.iso<br />
<br />
<br />
==== Enable networking ====<br />
Each boot you have to start the network etc etc. I decided it was better with the minimal install and touch as little as possible - if I could then get SME packages installed I could then use that to configure networking later.<br />
<br />
To start the networking <br />
<syntaxhighlight lang="Bash"><br />
./etc/sysconfig/network-scripts/ifup-eth eth0<br />
</syntaxhighlight><br />
<br />
or <br />
<syntaxhighlight lang="Bash"><br />
dhclient eth0<br />
</syntaxhighlight><br />
<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="Collapse" data-expandtext="More on networking"><br />
or if you want to assign a specific IP address (e.g. 192.168.1.2).<br />
<syntaxhighlight lang="Bash"><br />
ifconfig eth0 192.168.1.2<br />
echo "nameserver 192.168.1.254" >> /etc/resolv.conf<br />
route add default gw 192.168.1.254 eth0<br />
</syntaxhighlight> <br />
<br />
To make your changes permanent you will need to edit the configuration file to make it active on boot. There is only the vi text editor, you can also install nano. <br />
<syntaxhighlight lang="Bash"><br />
yum install nano<br />
nano /etc/sysconfig/network-scripts/ifcfg-eth0<br />
</syntaxhighlight><br />
and set ONBOOT=”YES”<br />
</div><br />
<br />
==== Enable SSH ====<br />
SSH is present but is disabled at this stage. To enable ssh issue:<br />
<syntaxhighlight lang="Bash"><br />
service sshd start<br />
</syntaxhighlight><br />
<br />
<br />
==== Disable / Remove SELinux ====<br />
It will be easier to see what's going on (and turn off selinux at kernel level, just to be sure)<br />
<syntaxhighlight lang="Bash"><br />
sed -i -e 's/rhgb quiet/selinux=0/g' /boot/grub/grub.conf<br />
<br />
sed -i -e 's/SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config<br />
<br />
yum remove selinux-policy-targeted<br />
<br />
setenforce 0<br />
</syntaxhighlight><br />
<br />
== Configure basic requirements ==<br />
==== Configure SME9 repositories ====<br />
<br />
See the following bugs tracking issues with repositories:<br />
* [[bugzilla:7294|Bug #7294: rpms that still need to be rebuilt or sourced for the SME9 repositories]]<br />
* [[bugzilla:7298|Bug #7298: Import perl-Unix-ConfigFile from rpmforge]]<br />
* [[bugzilla:7292|Bug #7292: more rpms in the SME8 repositories that have a lower version in our SME9 repositories]]<br />
* [[bugzilla:7305|Bug #7305: smeserver-yum doesn't provide the /etc/yum.smerepos.d dir]]<br />
<br />
<syntaxhighlight lang="Bash"><br />
yum install wget<br />
</syntaxhighlight><br />
<syntaxhighlight lang="Bash"><br />
mkdir /tmp/repo.bak<br />
mv /etc/yum.repos.d/*.repo /tmp/repo.bak/<br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3652<br />
</syntaxhighlight><br />
<br />
==== Import needed GPG Keys ====<br />
<syntaxhighlight lang="Bash"><br />
rpm --import http://sme-mirror.firewall-services.com/releases/8/smeos/x86_64/RPM-GPG-KEY-SMEServer<br />
rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt<br />
rpm --import https://fedoraproject.org/static/217521F6.txt<br />
rpm --import http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br />
rpm --import http://www.salstar.sk/pub/yum/keys/RPM-GPG-KEY-Fedora-Pre-Extras<br />
</syntaxhighlight><br />
<br />
==== Clean yum cache ====<br />
<syntaxhighlight lang="Bash"><br />
yum --enablerepo=* clean all<br />
</syntaxhighlight><br />
<br />
==== Install e-smith and smeserver packages & update all packages====<br />
Now, you should be ready to install all the e-smith and smeserver packages (and their dependencies), plus the rest of the rpms that aren't required by a smeserver- or e-smith- rpm, but were installed on SME8 [[bugzilla:7311]]. This should pull about 501 packages to install, and 14 to update, and then you can do 'yum upgrade' to upgrade the remaining CentOS packages. Some other notes on this in [[bugzilla:7240]]<br />
<br />
<pre style="white-space:normal;"> <br />
yum --disablerepo=* --enablerepo=smeupdates9,smeupdates-testing9,smeos8,smeupdates8 install e-smith\* smeserver\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef<br />
</pre><br />
<br />
<pre><br />
yum upgrade<br />
</pre><br />
<br />
See the following bugs:<br />
*[[bugzilla:7233|Bug #7233: e-smith-ldap should require openldap-servers]]<br />
*[[bugzilla:7252|Bug #7252: e-smith-radiusd should require freeradius-ldap]]<br />
*[[bugzilla:7234|Bug #7234: e-smith-apache should require mod_ssl]]<br />
*[[bugzilla:7297|Bug #7297: e-smith-hosts should require dhcp]]<br />
<br />
==== Move everything from rc7.d to rc4.d ====<br />
More info in [[bugzilla:7217]]<br />
All the links in rc4.d should then point to e-smith-service<br />
<syntaxhighlight lang="Bash"><br />
rm -f /etc/rc4.d/*<br />
cp -a /etc/rc7.d/* /etc/rc4.d/<br />
</syntaxhighlight><br />
<br />
==== Move some perl modules ====<br />
We need to copy some perl modules to a new directory, because @INC has changed in EL6: [[bugzilla:7223]]<br />
<syntaxhighlight lang="Bash"><br />
cp -a /usr/lib/perl5/site_perl/esmith/* /usr/share/perl5/vendor_perl/esmith<br />
</syntaxhighlight><br />
<br />
==== Run post-upgrade ====<br />
We can now try to post-upgrade<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</syntaxhighlight><br />
<br />
== Look for things to fix & Report bugs/problems ==<br />
<br />
To configure the server further, log in as root at then type 'console' and select 'configure this server'. <br />
<br />
If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
* [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap SME 9 Bug Report Matrix]<br />
* Open a new bug report - http://bugs.contribs.org/enter_bug.cgi<br />
<br />
Some ideas for things to look for:<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* what el5 packages are still installed that need working on? To check do<br />
<pre><br />
rpm -qa |grep el5<br />
</pre><br />
*<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_on_CentOS_6&diff=18358SME on CentOS 62013-02-09T08:59:38Z<p>Gregswallow: /* Install e-smith and smeserver packages & update all packages */</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9, based on CentOS 6 ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
<br />
=== Prerequisites ===<br />
* VIrtual machine (Vmware, Parallels or Virtualbox)<br />
* Centos Minimal 64-bit architecture. 32-bit may follow later<br />
* [[Setting_up_RPM_Building_for_SME_Server|Setting up a RPM Building environment]]<br />
<br />
=== User Feedback ===<br />
Unstructured user feedback can be noted here: [[SME9DEV_user_feedback|SME9DEV user feedback]]. Issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
<br />
=== Bugs ===<br />
[http://bugs.contribs.org/bugs/buglist.cgi?product=SME%20Server%209.X&component=Cleanup&resolution=--- Bug Tracker] <br />
[http://wiki.contribs.org/SME9BuildQueue#SME_9_Error_list_and_affected_packages SME 9 error list]<br />
<br />
=== Considerations ===<br />
* Primary and only goal for now is the transition of SME Server based on CentOS 5.8 to SME Server based on CentOS6.3<br />
* SysVinit is no longer the default with the release of RHEL6, beyond RHEL6 systemd will be used<br />
* perl has a new location of the filesystem. New: /usr/share/perl5/vendor_perl instead Old: /usr/lib/perl5/site_perl/<br />
* perl version 5.8.8 is the new default version on RHEL6. This requires a review of all the perl module rpms which are specific for perl 5.8.5<br />
<br />
== Installing CentOS 6 minimal ==<br />
First a few notes on CentOS 6 minimal, which is a bare bones install with very little on board. You can download a copy from one of the CentOS mirrors [http://www.centos.org/modules/tinycontent/index.php?id=30 here]<br />
<br />
* As per above note, only use Virtual Machine for testing purposes. A good free VM package can be obtained [https://www.virtualbox.org/wiki/Downloads here]<br />
* You might want to note down as much as possible so you yourself and others can reproduce the actions<br />
* Don't use yum with the '-y' flag (install/upgrade without further user interaction) when using the yum install/upgrade commands. (beware copy/paste yum commands)<br />
* you might want to note down all packages listed by yum to be installed/upgraded AND their dependencies<br />
* Make regular snapshots of your Virtual Machine and describe them specifically. At least when you've reached an important milestone for yourself<br />
<br />
<br />
==== Installing the ISO ====<br />
* Just install a minimal el6 installation (I just installed a few utilities like htop, screen, rsync, vim, openssh-clients mc etc…). You can use either the DVD, the minimal CD install, a net install with PXE, it's up to you<br />
* wellsi: I have used CentOS-6.3-x86_64-minimal.iso<br />
<br />
<br />
==== Enable networking ====<br />
Each boot you have to start the network etc etc. I decided it was better with the minimal install and touch as little as possible - if I could then get SME packages installed I could then use that to configure networking later.<br />
<br />
To start the networking <br />
<syntaxhighlight lang="Bash"><br />
./etc/sysconfig/network-scripts/ifup-eth eth0<br />
</syntaxhighlight><br />
<br />
or <br />
<syntaxhighlight lang="Bash"><br />
dhclient eth0<br />
</syntaxhighlight><br />
<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="Collapse" data-expandtext="More on networking"><br />
or if you want to assign a specific IP address (e.g. 192.168.1.2).<br />
<syntaxhighlight lang="Bash"><br />
ifconfig eth0 192.168.1.2<br />
echo "nameserver 192.168.1.254" >> /etc/resolv.conf<br />
route add default gw 192.168.1.254 eth0<br />
</syntaxhighlight> <br />
<br />
To make your changes permanent you will need to edit the configuration file to make it active on boot. There is only the vi text editor, you can also install nano. <br />
<syntaxhighlight lang="Bash"><br />
yum install nano<br />
nano /etc/sysconfig/network-scripts/ifcfg-eth0<br />
</syntaxhighlight><br />
and set ONBOOT=”YES”<br />
</div><br />
<br />
==== Enable SSH ====<br />
SSH is present but is disabled at this stage. To enable ssh issue:<br />
<syntaxhighlight lang="Bash"><br />
service sshd start<br />
</syntaxhighlight><br />
<br />
<br />
==== Disable / Remove SELinux ====<br />
It will be easier to see what's going on (and turn off selinux at kernel level, just to be sure)<br />
<syntaxhighlight lang="Bash"><br />
sed -i -e 's/rhgb quiet/selinux=0/g' /boot/grub/grub.conf<br />
<br />
sed -i -e 's/SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config<br />
<br />
yum remove selinux-policy-targeted<br />
<br />
setenforce 0<br />
</syntaxhighlight><br />
<br />
== Configure basic requirements ==<br />
==== Configure SME9 repositories ====<br />
<br />
See the following bugs tracking issues with repositories:<br />
* [[bugzilla:7294|Bug #7294: rpms that still need to be rebuilt or sourced for the SME9 repositories]]<br />
* [[bugzilla:7298|Bug #7298: Import perl-Unix-ConfigFile from rpmforge]]<br />
* [[bugzilla:7292|Bug #7292: more rpms in the SME8 repositories that have a lower version in our SME9 repositories]]<br />
* [[bugzilla:7305|Bug #7305: smeserver-yum doesn't provide the /etc/yum.smerepos.d dir]]<br />
<br />
<syntaxhighlight lang="Bash"><br />
yum install wget<br />
</syntaxhighlight><br />
<syntaxhighlight lang="Bash"><br />
mkdir /tmp/repo.bak<br />
mv /etc/yum.repos.d/*.repo /tmp/repo.bak/<br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3652<br />
</syntaxhighlight><br />
<br />
==== Import needed GPG Keys ====<br />
<syntaxhighlight lang="Bash"><br />
rpm --import http://sme-mirror.firewall-services.com/releases/8/smeos/x86_64/RPM-GPG-KEY-SMEServer<br />
rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt<br />
rpm --import https://fedoraproject.org/static/217521F6.txt<br />
rpm --import http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br />
rpm --import http://www.salstar.sk/pub/yum/keys/RPM-GPG-KEY-Fedora-Pre-Extras<br />
</syntaxhighlight><br />
<br />
==== Clean yum cache ====<br />
<syntaxhighlight lang="Bash"><br />
yum --enablerepo=* clean all<br />
</syntaxhighlight><br />
<br />
==== Install e-smith and smeserver packages & update all packages====<br />
Now, you should be ready to install all the e-smith and smeserver packages (and their dependencies), plus the rest of the rpms that aren't required by a smeserver- or e-smith- rpm, but were installed on SME8 [[bugzilla:7311]]. This should pull about 501 packages to install, and 14 to update, and then you can do 'yum upgrade' to upgrade the remaining CentOS packages. Some other notes on this in [[bugzilla:7240]]<br />
<br />
Currently a problem preventing this from working - feb 9 2013 - [[bugzilla:7331]]<br />
<pre style="white-space:normal;"> <br />
yum --disablerepo=* --enablerepo=smeupdates9,smeupdates-testing9,smeos8,smeupdates8 install e-smith\* smeserver\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync<br />
</pre><br />
<pre><br />
yum upgrade<br />
</pre><br />
<br />
See the following bugs:<br />
*[[bugzilla:7233|Bug #7233: e-smith-ldap should require openldap-servers]]<br />
*[[bugzilla:7252|Bug #7252: e-smith-radiusd should require freeradius-ldap]]<br />
*[[bugzilla:7234|Bug #7234: e-smith-apache should require mod_ssl]]<br />
*[[bugzilla:7297|Bug #7297: e-smith-hosts should require dhcp]]<br />
<br />
==== Move everything from rc7.d to rc4.d ====<br />
More info in [[bugzilla:7217]]<br />
All the links in rc4.d should then point to e-smith-service<br />
<syntaxhighlight lang="Bash"><br />
rm -f /etc/rc4.d/*<br />
cp -a /etc/rc7.d/* /etc/rc4.d/<br />
</syntaxhighlight><br />
<br />
==== Move some perl modules ====<br />
We need to copy some perl modules to a new directory, because @INC has changed in EL6: [[bugzilla:7223]]<br />
<syntaxhighlight lang="Bash"><br />
cp -a /usr/lib/perl5/site_perl/esmith/* /usr/share/perl5/vendor_perl/esmith<br />
</syntaxhighlight><br />
<br />
==== Create a service entry for rsyslog ====<br />
We need to create a new service entry in the DB, because the standard syslog package is now rsyslog:<br />
* See [[bugzilla:7221|Bug #7221: Change from syslog to rsyslog]] and [[bugzilla:7322|Bug #7322: Change from syslog to rsyslog - Add link]] This step can be removed when e-smith-base-5.4.0-8 is available.<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/db configuration set rsyslog service status enabled<br />
cp -a /etc/rc7.d/S05syslog /etc/rc4.d/S05rsyslog<br />
</syntaxhighlight><br />
<br />
==== Run post-upgrade ====<br />
We can now try to post-upgrade<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</syntaxhighlight><br />
<br />
== Look for things to fix & Report bugs/problems ==<br />
If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
* SME 9 Bug Report Matrix - http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap<br />
* Open a new bug report - http://bugs.contribs.org/enter_bug.cgi<br />
<br />
Some ideas for things to look for:<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* what el5 packages are still installed that need working on? To check do<br />
<pre><br />
rpm -qa |grep el5<br />
</pre><br />
*<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_on_CentOS_6&diff=18357SME on CentOS 62013-02-09T07:19:50Z<p>Gregswallow: /* Move everything from rc7.d to rc4.d */</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9, based on CentOS 6 ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
<br />
=== Prerequisites ===<br />
* VIrtual machine (Vmware, Parallels or Virtualbox)<br />
* Centos Minimal 64-bit architecture. 32-bit may follow later<br />
* [[Setting_up_RPM_Building_for_SME_Server|Setting up a RPM Building environment]]<br />
<br />
=== User Feedback ===<br />
Unstructured user feedback can be noted here: [[SME9DEV_user_feedback|SME9DEV user feedback]]. Issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
<br />
=== Bugs ===<br />
[http://bugs.contribs.org/bugs/buglist.cgi?product=SME%20Server%209.X&component=Cleanup&resolution=--- Bug Tracker] <br />
[http://wiki.contribs.org/SME9BuildQueue#SME_9_Error_list_and_affected_packages SME 9 error list]<br />
<br />
=== Considerations ===<br />
* Primary and only goal for now is the transition of SME Server based on CentOS 5.8 to SME Server based on CentOS6.3<br />
* SysVinit is no longer the default with the release of RHEL6, beyond RHEL6 systemd will be used<br />
* perl has a new location of the filesystem. New: /usr/share/perl5/vendor_perl instead Old: /usr/lib/perl5/site_perl/<br />
* perl version 5.8.8 is the new default version on RHEL6. This requires a review of all the perl module rpms which are specific for perl 5.8.5<br />
<br />
== Installing CentOS 6 minimal ==<br />
First a few notes on CentOS 6 minimal, which is a bare bones install with very little on board. You can download a copy from one of the CentOS mirrors [http://www.centos.org/modules/tinycontent/index.php?id=30 here]<br />
<br />
* As per above note, only use Virtual Machine for testing purposes. A good free VM package can be obtained [https://www.virtualbox.org/wiki/Downloads here]<br />
* You might want to note down as much as possible so you yourself and others can reproduce the actions<br />
* Don't use yum with the '-y' flag (install/upgrade without further user interaction) when using the yum install/upgrade commands. (beware copy/paste yum commands)<br />
* you might want to note down all packages listed by yum to be installed/upgraded AND their dependencies<br />
* Make regular snapshots of your Virtual Machine and describe them specifically. At least when you've reached an important milestone for yourself<br />
<br />
<br />
==== Installing the ISO ====<br />
* Just install a minimal el6 installation (I just installed a few utilities like htop, screen, rsync, vim, openssh-clients mc etc…). You can use either the DVD, the minimal CD install, a net install with PXE, it's up to you<br />
* wellsi: I have used CentOS-6.3-x86_64-minimal.iso<br />
<br />
<br />
==== Enable networking ====<br />
Each boot you have to start the network etc etc. I decided it was better with the minimal install and touch as little as possible - if I could then get SME packages installed I could then use that to configure networking later.<br />
<br />
To start the networking <br />
<syntaxhighlight lang="Bash"><br />
./etc/sysconfig/network-scripts/ifup-eth eth0<br />
</syntaxhighlight><br />
<br />
or <br />
<syntaxhighlight lang="Bash"><br />
dhclient eth0<br />
</syntaxhighlight><br />
<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="Collapse" data-expandtext="More on networking"><br />
or if you want to assign a specific IP address (e.g. 192.168.1.2).<br />
<syntaxhighlight lang="Bash"><br />
ifconfig eth0 192.168.1.2<br />
echo "nameserver 192.168.1.254" >> /etc/resolv.conf<br />
route add default gw 192.168.1.254 eth0<br />
</syntaxhighlight> <br />
<br />
To make your changes permanent you will need to edit the configuration file to make it active on boot. There is only the vi text editor, you can also install nano. <br />
<syntaxhighlight lang="Bash"><br />
yum install nano<br />
nano /etc/sysconfig/network-scripts/ifcfg-eth0<br />
</syntaxhighlight><br />
and set ONBOOT=”YES”<br />
</div><br />
<br />
==== Enable SSH ====<br />
SSH is present but is disabled at this stage. To enable ssh issue:<br />
<syntaxhighlight lang="Bash"><br />
service sshd start<br />
</syntaxhighlight><br />
<br />
<br />
==== Disable / Remove SELinux ====<br />
It will be easier to see what's going on (and turn off selinux at kernel level, just to be sure)<br />
<syntaxhighlight lang="Bash"><br />
sed -i -e 's/rhgb quiet/selinux=0/g' /boot/grub/grub.conf<br />
<br />
sed -i -e 's/SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config<br />
<br />
yum remove selinux-policy-targeted<br />
<br />
setenforce 0<br />
</syntaxhighlight><br />
<br />
== Configure basic requirements ==<br />
==== Configure SME9 repositories ====<br />
<br />
See the following bugs tracking issues with repositories:<br />
* [[bugzilla:7294|Bug #7294: rpms that still need to be rebuilt or sourced for the SME9 repositories]]<br />
* [[bugzilla:7298|Bug #7298: Import perl-Unix-ConfigFile from rpmforge]]<br />
* [[bugzilla:7292|Bug #7292: more rpms in the SME8 repositories that have a lower version in our SME9 repositories]]<br />
* [[bugzilla:7305|Bug #7305: smeserver-yum doesn't provide the /etc/yum.smerepos.d dir]]<br />
<br />
<syntaxhighlight lang="Bash"><br />
yum install wget<br />
</syntaxhighlight><br />
<syntaxhighlight lang="Bash"><br />
mkdir /tmp/repo.bak<br />
mv /etc/yum.repos.d/*.repo /tmp/repo.bak/<br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3652<br />
</syntaxhighlight><br />
<br />
==== Import needed GPG Keys ====<br />
<syntaxhighlight lang="Bash"><br />
rpm --import http://sme-mirror.firewall-services.com/releases/8/smeos/x86_64/RPM-GPG-KEY-SMEServer<br />
rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt<br />
rpm --import https://fedoraproject.org/static/217521F6.txt<br />
rpm --import http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br />
rpm --import http://www.salstar.sk/pub/yum/keys/RPM-GPG-KEY-Fedora-Pre-Extras<br />
</syntaxhighlight><br />
<br />
==== Clean yum cache ====<br />
<syntaxhighlight lang="Bash"><br />
yum --enablerepo=* clean all<br />
</syntaxhighlight><br />
<br />
==== Install e-smith and smeserver packages & update all packages====<br />
Now, you should be ready to install all the e-smith and smeserver packages (and their dependencies), plus the rest of the rpms that aren't required by a smeserver- or e-smith- rpm, but were installed on SME8 [[bugzilla:7311]]. This should pull about 501 packages to install, and 14 to update, and then you can do 'yum upgrade' to upgrade the remaining CentOS packages. Some other notes on this in [[bugzilla:7240]]<br />
<pre style="white-space:normal;"> <br />
yum --disablerepo=* --enablerepo=smeupdates9,smeupdates-testing9,smeos8,smeupdates8 install e-smith\* smeserver\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync<br />
</pre><br />
<pre><br />
yum upgrade<br />
</pre><br />
<br />
See the following bugs:<br />
*[[bugzilla:7233|Bug #7233: e-smith-ldap should require openldap-servers]]<br />
*[[bugzilla:7252|Bug #7252: e-smith-radiusd should require freeradius-ldap]]<br />
*[[bugzilla:7234|Bug #7234: e-smith-apache should require mod_ssl]]<br />
*[[bugzilla:7297|Bug #7297: e-smith-hosts should require dhcp]]<br />
<br />
==== Move everything from rc7.d to rc4.d ====<br />
More info in [[bugzilla:7217]]<br />
All the links in rc4.d should then point to e-smith-service<br />
<syntaxhighlight lang="Bash"><br />
rm -f /etc/rc4.d/*<br />
cp -a /etc/rc7.d/* /etc/rc4.d/<br />
</syntaxhighlight><br />
<br />
==== Move some perl modules ====<br />
We need to copy some perl modules to a new directory, because @INC has changed in EL6: [[bugzilla:7223]]<br />
<syntaxhighlight lang="Bash"><br />
cp -a /usr/lib/perl5/site_perl/esmith/* /usr/share/perl5/vendor_perl/esmith<br />
</syntaxhighlight><br />
<br />
==== Create a service entry for rsyslog ====<br />
We need to create a new service entry in the DB, because the standard syslog package is now rsyslog:<br />
* See [[bugzilla:7221|Bug #7221: Change from syslog to rsyslog]] and [[bugzilla:7322|Bug #7322: Change from syslog to rsyslog - Add link]] This step can be removed when e-smith-base-5.4.0-8 is available.<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/db configuration set rsyslog service status enabled<br />
cp -a /etc/rc7.d/S05syslog /etc/rc4.d/S05rsyslog<br />
</syntaxhighlight><br />
<br />
==== Run post-upgrade ====<br />
We can now try to post-upgrade<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</syntaxhighlight><br />
<br />
== Look for things to fix & Report bugs/problems ==<br />
If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
* SME 9 Bug Report Matrix - http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap<br />
* Open a new bug report - http://bugs.contribs.org/enter_bug.cgi<br />
<br />
Some ideas for things to look for:<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* what el5 packages are still installed that need working on? To check do<br />
<pre><br />
rpm -qa |grep el5<br />
</pre><br />
*<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_on_CentOS_6&diff=18356SME on CentOS 62013-02-09T07:03:04Z<p>Gregswallow: /* Configure SME9 repositories */</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9, based on CentOS 6 ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
<br />
=== Prerequisites ===<br />
* VIrtual machine (Vmware, Parallels or Virtualbox)<br />
* Centos Minimal 64-bit architecture. 32-bit may follow later<br />
* [[Setting_up_RPM_Building_for_SME_Server|Setting up a RPM Building environment]]<br />
<br />
=== User Feedback ===<br />
Unstructured user feedback can be noted here: [[SME9DEV_user_feedback|SME9DEV user feedback]]. Issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
<br />
=== Bugs ===<br />
[http://bugs.contribs.org/bugs/buglist.cgi?product=SME%20Server%209.X&component=Cleanup&resolution=--- Bug Tracker] <br />
[http://wiki.contribs.org/SME9BuildQueue#SME_9_Error_list_and_affected_packages SME 9 error list]<br />
<br />
=== Considerations ===<br />
* Primary and only goal for now is the transition of SME Server based on CentOS 5.8 to SME Server based on CentOS6.3<br />
* SysVinit is no longer the default with the release of RHEL6, beyond RHEL6 systemd will be used<br />
* perl has a new location of the filesystem. New: /usr/share/perl5/vendor_perl instead Old: /usr/lib/perl5/site_perl/<br />
* perl version 5.8.8 is the new default version on RHEL6. This requires a review of all the perl module rpms which are specific for perl 5.8.5<br />
<br />
== Installing CentOS 6 minimal ==<br />
First a few notes on CentOS 6 minimal, which is a bare bones install with very little on board. You can download a copy from one of the CentOS mirrors [http://www.centos.org/modules/tinycontent/index.php?id=30 here]<br />
<br />
* As per above note, only use Virtual Machine for testing purposes. A good free VM package can be obtained [https://www.virtualbox.org/wiki/Downloads here]<br />
* You might want to note down as much as possible so you yourself and others can reproduce the actions<br />
* Don't use yum with the '-y' flag (install/upgrade without further user interaction) when using the yum install/upgrade commands. (beware copy/paste yum commands)<br />
* you might want to note down all packages listed by yum to be installed/upgraded AND their dependencies<br />
* Make regular snapshots of your Virtual Machine and describe them specifically. At least when you've reached an important milestone for yourself<br />
<br />
<br />
==== Installing the ISO ====<br />
* Just install a minimal el6 installation (I just installed a few utilities like htop, screen, rsync, vim, openssh-clients mc etc…). You can use either the DVD, the minimal CD install, a net install with PXE, it's up to you<br />
* wellsi: I have used CentOS-6.3-x86_64-minimal.iso<br />
<br />
<br />
==== Enable networking ====<br />
Each boot you have to start the network etc etc. I decided it was better with the minimal install and touch as little as possible - if I could then get SME packages installed I could then use that to configure networking later.<br />
<br />
To start the networking <br />
<syntaxhighlight lang="Bash"><br />
./etc/sysconfig/network-scripts/ifup-eth eth0<br />
</syntaxhighlight><br />
<br />
or <br />
<syntaxhighlight lang="Bash"><br />
dhclient eth0<br />
</syntaxhighlight><br />
<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="Collapse" data-expandtext="More on networking"><br />
or if you want to assign a specific IP address (e.g. 192.168.1.2).<br />
<syntaxhighlight lang="Bash"><br />
ifconfig eth0 192.168.1.2<br />
echo "nameserver 192.168.1.254" >> /etc/resolv.conf<br />
route add default gw 192.168.1.254 eth0<br />
</syntaxhighlight> <br />
<br />
To make your changes permanent you will need to edit the configuration file to make it active on boot. There is only the vi text editor, you can also install nano. <br />
<syntaxhighlight lang="Bash"><br />
yum install nano<br />
nano /etc/sysconfig/network-scripts/ifcfg-eth0<br />
</syntaxhighlight><br />
and set ONBOOT=”YES”<br />
</div><br />
<br />
==== Enable SSH ====<br />
SSH is present but is disabled at this stage. To enable ssh issue:<br />
<syntaxhighlight lang="Bash"><br />
service sshd start<br />
</syntaxhighlight><br />
<br />
<br />
==== Disable / Remove SELinux ====<br />
It will be easier to see what's going on (and turn off selinux at kernel level, just to be sure)<br />
<syntaxhighlight lang="Bash"><br />
sed -i -e 's/rhgb quiet/selinux=0/g' /boot/grub/grub.conf<br />
<br />
sed -i -e 's/SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config<br />
<br />
yum remove selinux-policy-targeted<br />
<br />
setenforce 0<br />
</syntaxhighlight><br />
<br />
== Configure basic requirements ==<br />
==== Configure SME9 repositories ====<br />
<br />
See the following bugs tracking issues with repositories:<br />
* [[bugzilla:7294|Bug #7294: rpms that still need to be rebuilt or sourced for the SME9 repositories]]<br />
* [[bugzilla:7298|Bug #7298: Import perl-Unix-ConfigFile from rpmforge]]<br />
* [[bugzilla:7292|Bug #7292: more rpms in the SME8 repositories that have a lower version in our SME9 repositories]]<br />
* [[bugzilla:7305|Bug #7305: smeserver-yum doesn't provide the /etc/yum.smerepos.d dir]]<br />
<br />
<syntaxhighlight lang="Bash"><br />
yum install wget<br />
</syntaxhighlight><br />
<syntaxhighlight lang="Bash"><br />
mkdir /tmp/repo.bak<br />
mv /etc/yum.repos.d/*.repo /tmp/repo.bak/<br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3652<br />
</syntaxhighlight><br />
<br />
==== Import needed GPG Keys ====<br />
<syntaxhighlight lang="Bash"><br />
rpm --import http://sme-mirror.firewall-services.com/releases/8/smeos/x86_64/RPM-GPG-KEY-SMEServer<br />
rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt<br />
rpm --import https://fedoraproject.org/static/217521F6.txt<br />
rpm --import http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br />
rpm --import http://www.salstar.sk/pub/yum/keys/RPM-GPG-KEY-Fedora-Pre-Extras<br />
</syntaxhighlight><br />
<br />
==== Clean yum cache ====<br />
<syntaxhighlight lang="Bash"><br />
yum --enablerepo=* clean all<br />
</syntaxhighlight><br />
<br />
==== Install e-smith and smeserver packages & update all packages====<br />
Now, you should be ready to install all the e-smith and smeserver packages (and their dependencies), plus the rest of the rpms that aren't required by a smeserver- or e-smith- rpm, but were installed on SME8 [[bugzilla:7311]]. This should pull about 501 packages to install, and 14 to update, and then you can do 'yum upgrade' to upgrade the remaining CentOS packages. Some other notes on this in [[bugzilla:7240]]<br />
<pre style="white-space:normal;"> <br />
yum --disablerepo=* --enablerepo=smeupdates9,smeupdates-testing9,smeos8,smeupdates8 install e-smith\* smeserver\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync<br />
</pre><br />
<pre><br />
yum upgrade<br />
</pre><br />
<br />
See the following bugs:<br />
*[[bugzilla:7233|Bug #7233: e-smith-ldap should require openldap-servers]]<br />
*[[bugzilla:7252|Bug #7252: e-smith-radiusd should require freeradius-ldap]]<br />
*[[bugzilla:7234|Bug #7234: e-smith-apache should require mod_ssl]]<br />
*[[bugzilla:7297|Bug #7297: e-smith-hosts should require dhcp]]<br />
<br />
==== Move everything from rc7.d to rc4.d ====<br />
All the links in rc4.d should then point to e-smith-service<br />
<syntaxhighlight lang="Bash"><br />
rm -f /etc/rc4.d/*<br />
cp -a /etc/rc7.d/* /etc/rc4.d/<br />
</syntaxhighlight><br />
<br />
==== Move some perl modules ====<br />
We need to copy some perl modules to a new directory, because @INC has changed in EL6: [[bugzilla:7223]]<br />
<syntaxhighlight lang="Bash"><br />
cp -a /usr/lib/perl5/site_perl/esmith/* /usr/share/perl5/vendor_perl/esmith<br />
</syntaxhighlight><br />
<br />
==== Create a service entry for rsyslog ====<br />
We need to create a new service entry in the DB, because the standard syslog package is now rsyslog:<br />
* See [[bugzilla:7221|Bug #7221: Change from syslog to rsyslog]] and [[bugzilla:7322|Bug #7322: Change from syslog to rsyslog - Add link]] This step can be removed when e-smith-base-5.4.0-8 is available.<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/db configuration set rsyslog service status enabled<br />
cp -a /etc/rc7.d/S05syslog /etc/rc4.d/S05rsyslog<br />
</syntaxhighlight><br />
<br />
==== Run post-upgrade ====<br />
We can now try to post-upgrade<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</syntaxhighlight><br />
<br />
== Look for things to fix & Report bugs/problems ==<br />
If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
* SME 9 Bug Report Matrix - http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap<br />
* Open a new bug report - http://bugs.contribs.org/enter_bug.cgi<br />
<br />
Some ideas for things to look for:<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* what el5 packages are still installed that need working on? To check do<br />
<pre><br />
rpm -qa |grep el5<br />
</pre><br />
*<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_on_CentOS_6&diff=18355SME on CentOS 62013-02-09T06:56:00Z<p>Gregswallow: /* Look for things to fix & Report bugs/problems */</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9, based on CentOS 6 ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
<br />
=== Prerequisites ===<br />
* VIrtual machine (Vmware, Parallels or Virtualbox)<br />
* Centos Minimal 64-bit architecture. 32-bit may follow later<br />
* [[Setting_up_RPM_Building_for_SME_Server|Setting up a RPM Building environment]]<br />
<br />
=== User Feedback ===<br />
Unstructured user feedback can be noted here: [[SME9DEV_user_feedback|SME9DEV user feedback]]. Issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
<br />
=== Bugs ===<br />
[http://bugs.contribs.org/bugs/buglist.cgi?product=SME%20Server%209.X&component=Cleanup&resolution=--- Bug Tracker] <br />
[http://wiki.contribs.org/SME9BuildQueue#SME_9_Error_list_and_affected_packages SME 9 error list]<br />
<br />
=== Considerations ===<br />
* Primary and only goal for now is the transition of SME Server based on CentOS 5.8 to SME Server based on CentOS6.3<br />
* SysVinit is no longer the default with the release of RHEL6, beyond RHEL6 systemd will be used<br />
* perl has a new location of the filesystem. New: /usr/share/perl5/vendor_perl instead Old: /usr/lib/perl5/site_perl/<br />
* perl version 5.8.8 is the new default version on RHEL6. This requires a review of all the perl module rpms which are specific for perl 5.8.5<br />
<br />
== Installing CentOS 6 minimal ==<br />
First a few notes on CentOS 6 minimal, which is a bare bones install with very little on board. You can download a copy from one of the CentOS mirrors [http://www.centos.org/modules/tinycontent/index.php?id=30 here]<br />
<br />
* As per above note, only use Virtual Machine for testing purposes. A good free VM package can be obtained [https://www.virtualbox.org/wiki/Downloads here]<br />
* You might want to note down as much as possible so you yourself and others can reproduce the actions<br />
* Don't use yum with the '-y' flag (install/upgrade without further user interaction) when using the yum install/upgrade commands. (beware copy/paste yum commands)<br />
* you might want to note down all packages listed by yum to be installed/upgraded AND their dependencies<br />
* Make regular snapshots of your Virtual Machine and describe them specifically. At least when you've reached an important milestone for yourself<br />
<br />
<br />
==== Installing the ISO ====<br />
* Just install a minimal el6 installation (I just installed a few utilities like htop, screen, rsync, vim, openssh-clients mc etc…). You can use either the DVD, the minimal CD install, a net install with PXE, it's up to you<br />
* wellsi: I have used CentOS-6.3-x86_64-minimal.iso<br />
<br />
<br />
==== Enable networking ====<br />
Each boot you have to start the network etc etc. I decided it was better with the minimal install and touch as little as possible - if I could then get SME packages installed I could then use that to configure networking later.<br />
<br />
To start the networking <br />
<syntaxhighlight lang="Bash"><br />
./etc/sysconfig/network-scripts/ifup-eth eth0<br />
</syntaxhighlight><br />
<br />
or <br />
<syntaxhighlight lang="Bash"><br />
dhclient eth0<br />
</syntaxhighlight><br />
<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="Collapse" data-expandtext="More on networking"><br />
or if you want to assign a specific IP address (e.g. 192.168.1.2).<br />
<syntaxhighlight lang="Bash"><br />
ifconfig eth0 192.168.1.2<br />
echo "nameserver 192.168.1.254" >> /etc/resolv.conf<br />
route add default gw 192.168.1.254 eth0<br />
</syntaxhighlight> <br />
<br />
To make your changes permanent you will need to edit the configuration file to make it active on boot. There is only the vi text editor, you can also install nano. <br />
<syntaxhighlight lang="Bash"><br />
yum install nano<br />
nano /etc/sysconfig/network-scripts/ifcfg-eth0<br />
</syntaxhighlight><br />
and set ONBOOT=”YES”<br />
</div><br />
<br />
==== Enable SSH ====<br />
SSH is present but is disabled at this stage. To enable ssh issue:<br />
<syntaxhighlight lang="Bash"><br />
service sshd start<br />
</syntaxhighlight><br />
<br />
<br />
==== Disable / Remove SELinux ====<br />
It will be easier to see what's going on (and turn off selinux at kernel level, just to be sure)<br />
<syntaxhighlight lang="Bash"><br />
sed -i -e 's/rhgb quiet/selinux=0/g' /boot/grub/grub.conf<br />
<br />
sed -i -e 's/SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config<br />
<br />
yum remove selinux-policy-targeted<br />
<br />
setenforce 0<br />
</syntaxhighlight><br />
<br />
== Configure basic requirements ==<br />
==== Configure SME9 repositories ====<br />
<br />
See the following bugs tracking issues with repositories:<br />
* [[bugzilla:7294|Bug #7294: rpms that still need to be rebuilt or sourced for the SME9 repositories]]<br />
* [[bugzilla:7298|Bug #7298: Import perl-Unix-ConfigFile from rpmforge]]<br />
* [[bugzilla:7292|Bug #7292: more rpms in the SME8 repositories that have a lower version in our SME9 repositories]]<br />
* [[bugzilla:7305|Bug #7305: smeserver-yum doesn't provide the /etc/yum.smerepos.d dir]]<br />
<br />
<syntaxhighlight lang="Bash"><br />
yum install wget<br />
</syntaxhighlight><br />
<syntaxhighlight lang="Bash"><br />
mkdir /tmp/repo.bak<br />
mv /etc/yum.repos.d/*.repo /tmp/repo.bak/<br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3650<br />
</syntaxhighlight><br />
<br />
==== Import needed GPG Keys ====<br />
<syntaxhighlight lang="Bash"><br />
rpm --import http://sme-mirror.firewall-services.com/releases/8/smeos/x86_64/RPM-GPG-KEY-SMEServer<br />
rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt<br />
rpm --import https://fedoraproject.org/static/217521F6.txt<br />
rpm --import http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br />
rpm --import http://www.salstar.sk/pub/yum/keys/RPM-GPG-KEY-Fedora-Pre-Extras<br />
</syntaxhighlight><br />
<br />
==== Clean yum cache ====<br />
<syntaxhighlight lang="Bash"><br />
yum --enablerepo=* clean all<br />
</syntaxhighlight><br />
<br />
==== Install e-smith and smeserver packages & update all packages====<br />
Now, you should be ready to install all the e-smith and smeserver packages (and their dependencies), plus the rest of the rpms that aren't required by a smeserver- or e-smith- rpm, but were installed on SME8 [[bugzilla:7311]]. This should pull about 501 packages to install, and 14 to update, and then you can do 'yum upgrade' to upgrade the remaining CentOS packages. Some other notes on this in [[bugzilla:7240]]<br />
<pre style="white-space:normal;"> <br />
yum --disablerepo=* --enablerepo=smeupdates9,smeupdates-testing9,smeos8,smeupdates8 install e-smith\* smeserver\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync<br />
</pre><br />
<pre><br />
yum upgrade<br />
</pre><br />
<br />
See the following bugs:<br />
*[[bugzilla:7233|Bug #7233: e-smith-ldap should require openldap-servers]]<br />
*[[bugzilla:7252|Bug #7252: e-smith-radiusd should require freeradius-ldap]]<br />
*[[bugzilla:7234|Bug #7234: e-smith-apache should require mod_ssl]]<br />
*[[bugzilla:7297|Bug #7297: e-smith-hosts should require dhcp]]<br />
<br />
==== Move everything from rc7.d to rc4.d ====<br />
All the links in rc4.d should then point to e-smith-service<br />
<syntaxhighlight lang="Bash"><br />
rm -f /etc/rc4.d/*<br />
cp -a /etc/rc7.d/* /etc/rc4.d/<br />
</syntaxhighlight><br />
<br />
==== Move some perl modules ====<br />
We need to copy some perl modules to a new directory, because @INC has changed in EL6: [[bugzilla:7223]]<br />
<syntaxhighlight lang="Bash"><br />
cp -a /usr/lib/perl5/site_perl/esmith/* /usr/share/perl5/vendor_perl/esmith<br />
</syntaxhighlight><br />
<br />
==== Create a service entry for rsyslog ====<br />
We need to create a new service entry in the DB, because the standard syslog package is now rsyslog:<br />
* See [[bugzilla:7221|Bug #7221: Change from syslog to rsyslog]] and [[bugzilla:7322|Bug #7322: Change from syslog to rsyslog - Add link]] This step can be removed when e-smith-base-5.4.0-8 is available.<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/db configuration set rsyslog service status enabled<br />
cp -a /etc/rc7.d/S05syslog /etc/rc4.d/S05rsyslog<br />
</syntaxhighlight><br />
<br />
==== Run post-upgrade ====<br />
We can now try to post-upgrade<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</syntaxhighlight><br />
<br />
== Look for things to fix & Report bugs/problems ==<br />
If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
* SME 9 Bug Report Matrix - http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap<br />
* Open a new bug report - http://bugs.contribs.org/enter_bug.cgi<br />
<br />
Some ideas for things to look for:<br />
* Services not starting<br />
* Config files (templates) that need changes, especially if the major version of the package has changed<br />
* what el5 packages are still installed that need working on? To check do<br />
<pre><br />
rpm -qa |grep el5<br />
</pre><br />
*<br />
*<br />
*<br />
* add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_on_CentOS_6&diff=18354SME on CentOS 62013-02-09T06:54:56Z<p>Gregswallow: /* Install e-smith and smeserver packages */</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9, based on CentOS 6 ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
<br />
=== Prerequisites ===<br />
* VIrtual machine (Vmware, Parallels or Virtualbox)<br />
* Centos Minimal 64-bit architecture. 32-bit may follow later<br />
* [[Setting_up_RPM_Building_for_SME_Server|Setting up a RPM Building environment]]<br />
<br />
=== User Feedback ===<br />
Unstructured user feedback can be noted here: [[SME9DEV_user_feedback|SME9DEV user feedback]]. Issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
<br />
=== Bugs ===<br />
[http://bugs.contribs.org/bugs/buglist.cgi?product=SME%20Server%209.X&component=Cleanup&resolution=--- Bug Tracker] <br />
[http://wiki.contribs.org/SME9BuildQueue#SME_9_Error_list_and_affected_packages SME 9 error list]<br />
<br />
=== Considerations ===<br />
* Primary and only goal for now is the transition of SME Server based on CentOS 5.8 to SME Server based on CentOS6.3<br />
* SysVinit is no longer the default with the release of RHEL6, beyond RHEL6 systemd will be used<br />
* perl has a new location of the filesystem. New: /usr/share/perl5/vendor_perl instead Old: /usr/lib/perl5/site_perl/<br />
* perl version 5.8.8 is the new default version on RHEL6. This requires a review of all the perl module rpms which are specific for perl 5.8.5<br />
<br />
== Installing CentOS 6 minimal ==<br />
First a few notes on CentOS 6 minimal, which is a bare bones install with very little on board. You can download a copy from one of the CentOS mirrors [http://www.centos.org/modules/tinycontent/index.php?id=30 here]<br />
<br />
* As per above note, only use Virtual Machine for testing purposes. A good free VM package can be obtained [https://www.virtualbox.org/wiki/Downloads here]<br />
* You might want to note down as much as possible so you yourself and others can reproduce the actions<br />
* Don't use yum with the '-y' flag (install/upgrade without further user interaction) when using the yum install/upgrade commands. (beware copy/paste yum commands)<br />
* you might want to note down all packages listed by yum to be installed/upgraded AND their dependencies<br />
* Make regular snapshots of your Virtual Machine and describe them specifically. At least when you've reached an important milestone for yourself<br />
<br />
<br />
==== Installing the ISO ====<br />
* Just install a minimal el6 installation (I just installed a few utilities like htop, screen, rsync, vim, openssh-clients mc etc…). You can use either the DVD, the minimal CD install, a net install with PXE, it's up to you<br />
* wellsi: I have used CentOS-6.3-x86_64-minimal.iso<br />
<br />
<br />
==== Enable networking ====<br />
Each boot you have to start the network etc etc. I decided it was better with the minimal install and touch as little as possible - if I could then get SME packages installed I could then use that to configure networking later.<br />
<br />
To start the networking <br />
<syntaxhighlight lang="Bash"><br />
./etc/sysconfig/network-scripts/ifup-eth eth0<br />
</syntaxhighlight><br />
<br />
or <br />
<syntaxhighlight lang="Bash"><br />
dhclient eth0<br />
</syntaxhighlight><br />
<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="Collapse" data-expandtext="More on networking"><br />
or if you want to assign a specific IP address (e.g. 192.168.1.2).<br />
<syntaxhighlight lang="Bash"><br />
ifconfig eth0 192.168.1.2<br />
echo "nameserver 192.168.1.254" >> /etc/resolv.conf<br />
route add default gw 192.168.1.254 eth0<br />
</syntaxhighlight> <br />
<br />
To make your changes permanent you will need to edit the configuration file to make it active on boot. There is only the vi text editor, you can also install nano. <br />
<syntaxhighlight lang="Bash"><br />
yum install nano<br />
nano /etc/sysconfig/network-scripts/ifcfg-eth0<br />
</syntaxhighlight><br />
and set ONBOOT=”YES”<br />
</div><br />
<br />
==== Enable SSH ====<br />
SSH is present but is disabled at this stage. To enable ssh issue:<br />
<syntaxhighlight lang="Bash"><br />
service sshd start<br />
</syntaxhighlight><br />
<br />
<br />
==== Disable / Remove SELinux ====<br />
It will be easier to see what's going on (and turn off selinux at kernel level, just to be sure)<br />
<syntaxhighlight lang="Bash"><br />
sed -i -e 's/rhgb quiet/selinux=0/g' /boot/grub/grub.conf<br />
<br />
sed -i -e 's/SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config<br />
<br />
yum remove selinux-policy-targeted<br />
<br />
setenforce 0<br />
</syntaxhighlight><br />
<br />
== Configure basic requirements ==<br />
==== Configure SME9 repositories ====<br />
<br />
See the following bugs tracking issues with repositories:<br />
* [[bugzilla:7294|Bug #7294: rpms that still need to be rebuilt or sourced for the SME9 repositories]]<br />
* [[bugzilla:7298|Bug #7298: Import perl-Unix-ConfigFile from rpmforge]]<br />
* [[bugzilla:7292|Bug #7292: more rpms in the SME8 repositories that have a lower version in our SME9 repositories]]<br />
* [[bugzilla:7305|Bug #7305: smeserver-yum doesn't provide the /etc/yum.smerepos.d dir]]<br />
<br />
<syntaxhighlight lang="Bash"><br />
yum install wget<br />
</syntaxhighlight><br />
<syntaxhighlight lang="Bash"><br />
mkdir /tmp/repo.bak<br />
mv /etc/yum.repos.d/*.repo /tmp/repo.bak/<br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3650<br />
</syntaxhighlight><br />
<br />
==== Import needed GPG Keys ====<br />
<syntaxhighlight lang="Bash"><br />
rpm --import http://sme-mirror.firewall-services.com/releases/8/smeos/x86_64/RPM-GPG-KEY-SMEServer<br />
rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt<br />
rpm --import https://fedoraproject.org/static/217521F6.txt<br />
rpm --import http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br />
rpm --import http://www.salstar.sk/pub/yum/keys/RPM-GPG-KEY-Fedora-Pre-Extras<br />
</syntaxhighlight><br />
<br />
==== Clean yum cache ====<br />
<syntaxhighlight lang="Bash"><br />
yum --enablerepo=* clean all<br />
</syntaxhighlight><br />
<br />
==== Install e-smith and smeserver packages & update all packages====<br />
Now, you should be ready to install all the e-smith and smeserver packages (and their dependencies), plus the rest of the rpms that aren't required by a smeserver- or e-smith- rpm, but were installed on SME8 [[bugzilla:7311]]. This should pull about 501 packages to install, and 14 to update, and then you can do 'yum upgrade' to upgrade the remaining CentOS packages. Some other notes on this in [[bugzilla:7240]]<br />
<pre style="white-space:normal;"> <br />
yum --disablerepo=* --enablerepo=smeupdates9,smeupdates-testing9,smeos8,smeupdates8 install e-smith\* smeserver\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync<br />
</pre><br />
<pre><br />
yum upgrade<br />
</pre><br />
<br />
See the following bugs:<br />
*[[bugzilla:7233|Bug #7233: e-smith-ldap should require openldap-servers]]<br />
*[[bugzilla:7252|Bug #7252: e-smith-radiusd should require freeradius-ldap]]<br />
*[[bugzilla:7234|Bug #7234: e-smith-apache should require mod_ssl]]<br />
*[[bugzilla:7297|Bug #7297: e-smith-hosts should require dhcp]]<br />
<br />
==== Move everything from rc7.d to rc4.d ====<br />
All the links in rc4.d should then point to e-smith-service<br />
<syntaxhighlight lang="Bash"><br />
rm -f /etc/rc4.d/*<br />
cp -a /etc/rc7.d/* /etc/rc4.d/<br />
</syntaxhighlight><br />
<br />
==== Move some perl modules ====<br />
We need to copy some perl modules to a new directory, because @INC has changed in EL6: [[bugzilla:7223]]<br />
<syntaxhighlight lang="Bash"><br />
cp -a /usr/lib/perl5/site_perl/esmith/* /usr/share/perl5/vendor_perl/esmith<br />
</syntaxhighlight><br />
<br />
==== Create a service entry for rsyslog ====<br />
We need to create a new service entry in the DB, because the standard syslog package is now rsyslog:<br />
* See [[bugzilla:7221|Bug #7221: Change from syslog to rsyslog]] and [[bugzilla:7322|Bug #7322: Change from syslog to rsyslog - Add link]] This step can be removed when e-smith-base-5.4.0-8 is available.<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/db configuration set rsyslog service status enabled<br />
cp -a /etc/rc7.d/S05syslog /etc/rc4.d/S05rsyslog<br />
</syntaxhighlight><br />
<br />
==== Run post-upgrade ====<br />
We can now try to post-upgrade<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</syntaxhighlight><br />
<br />
== Look for things to fix & Report bugs/problems ==<br />
If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
* SME 9 Bug Report Matrix - http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap<br />
* Open a new bug report - http://bugs.contribs.org/enter_bug.cgi<br />
<br />
Some ideas for things to look for:<br />
- Services not starting<br />
- Config files (templates) that need changes, especially if the major version of the package has changed<br />
- what el5 packages are still installed that need working on? To check do<br />
<pre><br />
rpm -qa |grep el5<br />
</pre><br />
-<br />
-<br />
-<br />
- add more generic ideas here....specific issues to the bugtracker please<br />
<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_on_CentOS_6&diff=18353SME on CentOS 62013-02-09T06:54:15Z<p>Gregswallow: </p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9, based on CentOS 6 ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
<br />
=== Prerequisites ===<br />
* VIrtual machine (Vmware, Parallels or Virtualbox)<br />
* Centos Minimal 64-bit architecture. 32-bit may follow later<br />
* [[Setting_up_RPM_Building_for_SME_Server|Setting up a RPM Building environment]]<br />
<br />
=== User Feedback ===<br />
Unstructured user feedback can be noted here: [[SME9DEV_user_feedback|SME9DEV user feedback]]. Issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
<br />
=== Bugs ===<br />
[http://bugs.contribs.org/bugs/buglist.cgi?product=SME%20Server%209.X&component=Cleanup&resolution=--- Bug Tracker] <br />
[http://wiki.contribs.org/SME9BuildQueue#SME_9_Error_list_and_affected_packages SME 9 error list]<br />
<br />
=== Considerations ===<br />
* Primary and only goal for now is the transition of SME Server based on CentOS 5.8 to SME Server based on CentOS6.3<br />
* SysVinit is no longer the default with the release of RHEL6, beyond RHEL6 systemd will be used<br />
* perl has a new location of the filesystem. New: /usr/share/perl5/vendor_perl instead Old: /usr/lib/perl5/site_perl/<br />
* perl version 5.8.8 is the new default version on RHEL6. This requires a review of all the perl module rpms which are specific for perl 5.8.5<br />
<br />
== Installing CentOS 6 minimal ==<br />
First a few notes on CentOS 6 minimal, which is a bare bones install with very little on board. You can download a copy from one of the CentOS mirrors [http://www.centos.org/modules/tinycontent/index.php?id=30 here]<br />
<br />
* As per above note, only use Virtual Machine for testing purposes. A good free VM package can be obtained [https://www.virtualbox.org/wiki/Downloads here]<br />
* You might want to note down as much as possible so you yourself and others can reproduce the actions<br />
* Don't use yum with the '-y' flag (install/upgrade without further user interaction) when using the yum install/upgrade commands. (beware copy/paste yum commands)<br />
* you might want to note down all packages listed by yum to be installed/upgraded AND their dependencies<br />
* Make regular snapshots of your Virtual Machine and describe them specifically. At least when you've reached an important milestone for yourself<br />
<br />
<br />
==== Installing the ISO ====<br />
* Just install a minimal el6 installation (I just installed a few utilities like htop, screen, rsync, vim, openssh-clients mc etc…). You can use either the DVD, the minimal CD install, a net install with PXE, it's up to you<br />
* wellsi: I have used CentOS-6.3-x86_64-minimal.iso<br />
<br />
<br />
==== Enable networking ====<br />
Each boot you have to start the network etc etc. I decided it was better with the minimal install and touch as little as possible - if I could then get SME packages installed I could then use that to configure networking later.<br />
<br />
To start the networking <br />
<syntaxhighlight lang="Bash"><br />
./etc/sysconfig/network-scripts/ifup-eth eth0<br />
</syntaxhighlight><br />
<br />
or <br />
<syntaxhighlight lang="Bash"><br />
dhclient eth0<br />
</syntaxhighlight><br />
<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="Collapse" data-expandtext="More on networking"><br />
or if you want to assign a specific IP address (e.g. 192.168.1.2).<br />
<syntaxhighlight lang="Bash"><br />
ifconfig eth0 192.168.1.2<br />
echo "nameserver 192.168.1.254" >> /etc/resolv.conf<br />
route add default gw 192.168.1.254 eth0<br />
</syntaxhighlight> <br />
<br />
To make your changes permanent you will need to edit the configuration file to make it active on boot. There is only the vi text editor, you can also install nano. <br />
<syntaxhighlight lang="Bash"><br />
yum install nano<br />
nano /etc/sysconfig/network-scripts/ifcfg-eth0<br />
</syntaxhighlight><br />
and set ONBOOT=”YES”<br />
</div><br />
<br />
==== Enable SSH ====<br />
SSH is present but is disabled at this stage. To enable ssh issue:<br />
<syntaxhighlight lang="Bash"><br />
service sshd start<br />
</syntaxhighlight><br />
<br />
<br />
==== Disable / Remove SELinux ====<br />
It will be easier to see what's going on (and turn off selinux at kernel level, just to be sure)<br />
<syntaxhighlight lang="Bash"><br />
sed -i -e 's/rhgb quiet/selinux=0/g' /boot/grub/grub.conf<br />
<br />
sed -i -e 's/SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config<br />
<br />
yum remove selinux-policy-targeted<br />
<br />
setenforce 0<br />
</syntaxhighlight><br />
<br />
== Configure basic requirements ==<br />
==== Configure SME9 repositories ====<br />
<br />
See the following bugs tracking issues with repositories:<br />
* [[bugzilla:7294|Bug #7294: rpms that still need to be rebuilt or sourced for the SME9 repositories]]<br />
* [[bugzilla:7298|Bug #7298: Import perl-Unix-ConfigFile from rpmforge]]<br />
* [[bugzilla:7292|Bug #7292: more rpms in the SME8 repositories that have a lower version in our SME9 repositories]]<br />
* [[bugzilla:7305|Bug #7305: smeserver-yum doesn't provide the /etc/yum.smerepos.d dir]]<br />
<br />
<syntaxhighlight lang="Bash"><br />
yum install wget<br />
</syntaxhighlight><br />
<syntaxhighlight lang="Bash"><br />
mkdir /tmp/repo.bak<br />
mv /etc/yum.repos.d/*.repo /tmp/repo.bak/<br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3650<br />
</syntaxhighlight><br />
<br />
==== Import needed GPG Keys ====<br />
<syntaxhighlight lang="Bash"><br />
rpm --import http://sme-mirror.firewall-services.com/releases/8/smeos/x86_64/RPM-GPG-KEY-SMEServer<br />
rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt<br />
rpm --import https://fedoraproject.org/static/217521F6.txt<br />
rpm --import http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br />
rpm --import http://www.salstar.sk/pub/yum/keys/RPM-GPG-KEY-Fedora-Pre-Extras<br />
</syntaxhighlight><br />
<br />
==== Clean yum cache ====<br />
<syntaxhighlight lang="Bash"><br />
yum --enablerepo=* clean all<br />
</syntaxhighlight><br />
<br />
==== Install e-smith and smeserver packages ====<br />
Now, you should be ready to install all the e-smith and smeserver packages (and their dependencies), plus the rest of the rpms that aren't required by a smeserver- or e-smith- rpm, but were installed on SME8 [[bugzilla:7311]]. This should pull about 501 packages to install, and 14 to update, and then you can do 'yum upgrade' to upgrade the remaining CentOS packages. Some other notes on this in [[bugzilla:7240]]<br />
<pre style="white-space:normal;"> <br />
yum --disablerepo=* --enablerepo=smeupdates9,smeupdates-testing9,smeos8,smeupdates8 install e-smith\* smeserver\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync<br />
</pre><br />
<pre><br />
yum upgrade<br />
</pre><br />
<br />
See the following bugs:<br />
*[[bugzilla:7233|Bug #7233: e-smith-ldap should require openldap-servers]]<br />
*[[bugzilla:7252|Bug #7252: e-smith-radiusd should require freeradius-ldap]]<br />
*[[bugzilla:7234|Bug #7234: e-smith-apache should require mod_ssl]]<br />
*[[bugzilla:7297|Bug #7297: e-smith-hosts should require dhcp]]<br />
<br />
==== Move everything from rc7.d to rc4.d ====<br />
All the links in rc4.d should then point to e-smith-service<br />
<syntaxhighlight lang="Bash"><br />
rm -f /etc/rc4.d/*<br />
cp -a /etc/rc7.d/* /etc/rc4.d/<br />
</syntaxhighlight><br />
<br />
==== Move some perl modules ====<br />
We need to copy some perl modules to a new directory, because @INC has changed in EL6: [[bugzilla:7223]]<br />
<syntaxhighlight lang="Bash"><br />
cp -a /usr/lib/perl5/site_perl/esmith/* /usr/share/perl5/vendor_perl/esmith<br />
</syntaxhighlight><br />
<br />
==== Create a service entry for rsyslog ====<br />
We need to create a new service entry in the DB, because the standard syslog package is now rsyslog:<br />
* See [[bugzilla:7221|Bug #7221: Change from syslog to rsyslog]] and [[bugzilla:7322|Bug #7322: Change from syslog to rsyslog - Add link]] This step can be removed when e-smith-base-5.4.0-8 is available.<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/db configuration set rsyslog service status enabled<br />
cp -a /etc/rc7.d/S05syslog /etc/rc4.d/S05rsyslog<br />
</syntaxhighlight><br />
<br />
==== Run post-upgrade ====<br />
We can now try to post-upgrade<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</syntaxhighlight><br />
<br />
== Look for things to fix & Report bugs/problems ==<br />
If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
* SME 9 Bug Report Matrix - http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap<br />
* Open a new bug report - http://bugs.contribs.org/enter_bug.cgi<br />
<br />
Some ideas for things to look for:<br />
- Services not starting<br />
- Config files (templates) that need changes, especially if the major version of the package has changed<br />
- what el5 packages are still installed that need working on? To check do<br />
<pre><br />
rpm -qa |grep el5<br />
</pre><br />
-<br />
-<br />
-<br />
- add more generic ideas here....specific issues to the bugtracker please<br />
<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_on_CentOS_6&diff=18352SME on CentOS 62013-02-09T06:48:17Z<p>Gregswallow: we have el6 versions of all the upstream sourced perl module packages in the repos now</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9, based on CentOS 6 ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
<br />
=== Prerequisites ===<br />
* VIrtual machine (Vmware, Parallels or Virtualbox)<br />
* Centos Minimal 64-bit architecture. 32-bit may follow later<br />
* [[Setting_up_RPM_Building_for_SME_Server|Setting up a RPM Building environment]]<br />
<br />
=== User Feedback ===<br />
Unstructured user feedback can be noted here: [[SME9DEV_user_feedback|SME9DEV user feedback]]. Issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
<br />
=== Bugs ===<br />
[http://bugs.contribs.org/bugs/buglist.cgi?product=SME%20Server%209.X&component=Cleanup&resolution=--- Bug Tracker] <br />
[http://wiki.contribs.org/SME9BuildQueue#SME_9_Error_list_and_affected_packages SME 9 error list]<br />
<br />
=== Considerations ===<br />
* Primary and only goal for now is the transition of SME Server based on CentOS 5.8 to SME Server based on CentOS6.3<br />
* SysVinit is no longer the default with the release of RHEL6, beyond RHEL6 systemd will be used<br />
* perl has a new location of the filesystem. New: /usr/share/perl5/vendor_perl instead Old: /usr/lib/perl5/site_perl/<br />
* perl version 5.8.8 is the new default version on RHEL6. This requires a review of all the perl module rpms which are specific for perl 5.8.5<br />
<br />
== Installing CentOS 6 minimal ==<br />
First a few notes on CentOS 6 minimal, which is a bare bones install with very little on board. You can download a copy from one of the CentOS mirrors [http://www.centos.org/modules/tinycontent/index.php?id=30 here]<br />
<br />
* As per above note, only use Virtual Machine for testing purposes. A good free VM package can be obtained [https://www.virtualbox.org/wiki/Downloads here]<br />
* You might want to note down as much as possible so you yourself and others can reproduce the actions<br />
* Don't use yum with the '-y' flag (install/upgrade without further user interaction) when using the yum install/upgrade commands. (beware copy/paste yum commands)<br />
* you might want to note down all packages listed by yum to be installed/upgraded AND their dependencies<br />
* Make regular snapshots of your Virtual Machine and describe them specifically. At least when you've reached an important milestone for yourself<br />
<br />
<br />
==== Installing the ISO ====<br />
* Just install a minimal el6 installation (I just installed a few utilities like htop, screen, rsync, vim, openssh-clients mc etc…). You can use either the DVD, the minimal CD install, a net install with PXE, it's up to you<br />
* wellsi: I have used CentOS-6.3-x86_64-minimal.iso<br />
<br />
<br />
==== Enable networking ====<br />
Each boot you have to start the network etc etc. I decided it was better with the minimal install and touch as little as possible - if I could then get SME packages installed I could then use that to configure networking later.<br />
<br />
To start the networking <br />
<syntaxhighlight lang="Bash"><br />
./etc/sysconfig/network-scripts/ifup-eth eth0<br />
</syntaxhighlight><br />
<br />
or <br />
<syntaxhighlight lang="Bash"><br />
dhclient eth0<br />
</syntaxhighlight><br />
<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="Collapse" data-expandtext="More on networking"><br />
or if you want to assign a specific IP address (e.g. 192.168.1.2).<br />
<syntaxhighlight lang="Bash"><br />
ifconfig eth0 192.168.1.2<br />
echo "nameserver 192.168.1.254" >> /etc/resolv.conf<br />
route add default gw 192.168.1.254 eth0<br />
</syntaxhighlight> <br />
<br />
To make your changes permanent you will need to edit the configuration file to make it active on boot. There is only the vi text editor, you can also install nano. <br />
<syntaxhighlight lang="Bash"><br />
yum install nano<br />
nano /etc/sysconfig/network-scripts/ifcfg-eth0<br />
</syntaxhighlight><br />
and set ONBOOT=”YES”<br />
</div><br />
<br />
==== Enable SSH ====<br />
SSH is present but is disabled at this stage. To enable ssh issue:<br />
<syntaxhighlight lang="Bash"><br />
service sshd start<br />
</syntaxhighlight><br />
<br />
<br />
==== Disable / Remove SELinux ====<br />
It will be easier to see what's going on (and turn off selinux at kernel level, just to be sure)<br />
<syntaxhighlight lang="Bash"><br />
sed -i -e 's/rhgb quiet/selinux=0/g' /boot/grub/grub.conf<br />
<br />
sed -i -e 's/SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config<br />
<br />
yum remove selinux-policy-targeted<br />
<br />
setenforce 0<br />
</syntaxhighlight><br />
<br />
== Configure basic requirements ==<br />
==== Configure SME9 repositories ====<br />
<br />
See the following bugs tracking issues with repositories:<br />
* [[bugzilla:7294|Bug #7294: rpms that still need to be rebuilt or sourced for the SME9 repositories]]<br />
* [[bugzilla:7298|Bug #7298: Import perl-Unix-ConfigFile from rpmforge]]<br />
* [[bugzilla:7292|Bug #7292: more rpms in the SME8 repositories that have a lower version in our SME9 repositories]]<br />
* [[bugzilla:7305|Bug #7305: smeserver-yum doesn't provide the /etc/yum.smerepos.d dir]]<br />
<br />
<syntaxhighlight lang="Bash"><br />
yum install wget<br />
</syntaxhighlight><br />
<syntaxhighlight lang="Bash"><br />
mkdir /tmp/repo.bak<br />
mv /etc/yum.repos.d/*.repo /tmp/repo.bak/<br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3650<br />
</syntaxhighlight><br />
<br />
==== Import needed GPG Keys ====<br />
<syntaxhighlight lang="Bash"><br />
rpm --import http://sme-mirror.firewall-services.com/releases/8/smeos/x86_64/RPM-GPG-KEY-SMEServer<br />
rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt<br />
rpm --import https://fedoraproject.org/static/217521F6.txt<br />
rpm --import http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br />
rpm --import http://www.salstar.sk/pub/yum/keys/RPM-GPG-KEY-Fedora-Pre-Extras<br />
</syntaxhighlight><br />
<br />
==== Clean yum cache ====<br />
<syntaxhighlight lang="Bash"><br />
yum --enablerepo=* clean all<br />
</syntaxhighlight><br />
<br />
<br />
==== Install e-smith and smeserver packages ====<br />
Now, you should be ready to install all the e-smith and smeserver packages (and their dependencies), plus the rest of the rpms that aren't required by a smeserver- or e-smith- rpm, but were installed on SME8 [[bugzilla:7311]]. This should pull about 501 packages to install, and 14 to update, and then you can do 'yum upgrade' to upgrade the remaining CentOS packages. Some other notes on this in [[bugzilla:7240]]<br />
<pre style="white-space:normal;"> <br />
yum --disablerepo=* --enablerepo=smeupdates9,smeupdates-testing9,smeos8,smeupdates8 install e-smith\* smeserver\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync<br />
</pre><br />
<pre><br />
yum upgrade<br />
</pre><br />
<br />
See the following bugs:<br />
*[[bugzilla:7233|Bug #7233: e-smith-ldap should require openldap-servers]]<br />
*[[bugzilla:7252|Bug #7252: e-smith-radiusd should require freeradius-ldap]]<br />
*[[bugzilla:7234|Bug #7234: e-smith-apache should require mod_ssl]]<br />
*[[bugzilla:7297|Bug #7297: e-smith-hosts should require dhcp]]<br />
<br />
==== Move everything from rc7.d to rc4.d ====<br />
All the links in rc4.d should then point to e-smith-service<br />
<syntaxhighlight lang="Bash"><br />
rm -f /etc/rc4.d/*<br />
cp -a /etc/rc7.d/* /etc/rc4.d/<br />
</syntaxhighlight><br />
<br />
==== Move some perl modules ====<br />
We need to copy some perl modules to a new directory, because @INC has changed in EL6: [[bugzilla:7223]]<br />
<syntaxhighlight lang="Bash"><br />
cp -a /usr/lib/perl5/site_perl/esmith/* /usr/share/perl5/vendor_perl/esmith<br />
</syntaxhighlight><br />
<br />
==== Create a service entry for rsyslog ====<br />
We need to create a new service entry in the DB, because the standard syslog package is now rsyslog:<br />
* See [[bugzilla:7221|Bug #7221: Change from syslog to rsyslog]] and [[bugzilla:7322|Bug #7322: Change from syslog to rsyslog - Add link]] This step can be removed when e-smith-base-5.4.0-8 is available.<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/db configuration set rsyslog service status enabled<br />
cp -a /etc/rc7.d/S05syslog /etc/rc4.d/S05rsyslog<br />
</syntaxhighlight><br />
<br />
==== Run post-upgrade ====<br />
We can now try to post-upgrade<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</syntaxhighlight><br />
<br />
==== Look for things to fix & Report bugs/problems ====<br />
If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
* SME 9 Bug Report Matrix - http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap<br />
* Open a new bug report - http://bugs.contribs.org/enter_bug.cgi<br />
<br />
Some ideas for things to look for:<br />
- Services not starting<br />
- Config files (templates) that need changes, especially if the major version of the package has changed<br />
- add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== SME Server specific/required packages ==<br />
To get a list of all specific SME Server packages you can run:<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa | grep 'smeserver\|e-smith'| sed -e 's/-[0-9].*//' | sort > smeserver-packages.txt<br />
</syntaxhighlight><br />
<br />
<br />
== FormMagick ==<br />
Next will be an attack on FormMagick - there is no package in the default install so need to figure that out. In may indeed be horrible, but we can live with it for now.<br />
<br />
Hopefully with perl and FormMagick installed, most of the SME stuff *should* basically install.<br />
<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
<br />
==== Kickstart file ====<br />
* A starting point can be found on the [[SME9_Kickstart| SME9 Kickstart]] page.<br />
<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_on_CentOS_6&diff=18351SME on CentOS 62013-02-09T06:46:05Z<p>Gregswallow: i dont think we should list specific problems here, thats what the bug tracker is for</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9, based on CentOS 6 ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
<br />
=== Prerequisites ===<br />
* VIrtual machine (Vmware, Parallels or Virtualbox)<br />
* Centos Minimal 64-bit architecture. 32-bit may follow later<br />
* [[Setting_up_RPM_Building_for_SME_Server|Setting up a RPM Building environment]]<br />
<br />
=== User Feedback ===<br />
Unstructured user feedback can be noted here: [[SME9DEV_user_feedback|SME9DEV user feedback]]. Issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
<br />
=== Bugs ===<br />
[http://bugs.contribs.org/bugs/buglist.cgi?product=SME%20Server%209.X&component=Cleanup&resolution=--- Bug Tracker] <br />
[http://wiki.contribs.org/SME9BuildQueue#SME_9_Error_list_and_affected_packages SME 9 error list]<br />
<br />
=== Considerations ===<br />
* Primary and only goal for now is the transition of SME Server based on CentOS 5.8 to SME Server based on CentOS6.3<br />
* SysVinit is no longer the default with the release of RHEL6, beyond RHEL6 systemd will be used<br />
* perl has a new location of the filesystem. New: /usr/share/perl5/vendor_perl instead Old: /usr/lib/perl5/site_perl/<br />
* perl version 5.8.8 is the new default version on RHEL6. This requires a review of all the perl module rpms which are specific for perl 5.8.5<br />
<br />
== Installing CentOS 6 minimal ==<br />
First a few notes on CentOS 6 minimal, which is a bare bones install with very little on board. You can download a copy from one of the CentOS mirrors [http://www.centos.org/modules/tinycontent/index.php?id=30 here]<br />
<br />
* As per above note, only use Virtual Machine for testing purposes. A good free VM package can be obtained [https://www.virtualbox.org/wiki/Downloads here]<br />
* You might want to note down as much as possible so you yourself and others can reproduce the actions<br />
* Don't use yum with the '-y' flag (install/upgrade without further user interaction) when using the yum install/upgrade commands. (beware copy/paste yum commands)<br />
* you might want to note down all packages listed by yum to be installed/upgraded AND their dependencies<br />
* Make regular snapshots of your Virtual Machine and describe them specifically. At least when you've reached an important milestone for yourself<br />
<br />
<br />
==== Installing the ISO ====<br />
* Just install a minimal el6 installation (I just installed a few utilities like htop, screen, rsync, vim, openssh-clients mc etc…). You can use either the DVD, the minimal CD install, a net install with PXE, it's up to you<br />
* wellsi: I have used CentOS-6.3-x86_64-minimal.iso<br />
<br />
<br />
==== Enable networking ====<br />
Each boot you have to start the network etc etc. I decided it was better with the minimal install and touch as little as possible - if I could then get SME packages installed I could then use that to configure networking later.<br />
<br />
To start the networking <br />
<syntaxhighlight lang="Bash"><br />
./etc/sysconfig/network-scripts/ifup-eth eth0<br />
</syntaxhighlight><br />
<br />
or <br />
<syntaxhighlight lang="Bash"><br />
dhclient eth0<br />
</syntaxhighlight><br />
<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="Collapse" data-expandtext="More on networking"><br />
or if you want to assign a specific IP address (e.g. 192.168.1.2).<br />
<syntaxhighlight lang="Bash"><br />
ifconfig eth0 192.168.1.2<br />
echo "nameserver 192.168.1.254" >> /etc/resolv.conf<br />
route add default gw 192.168.1.254 eth0<br />
</syntaxhighlight> <br />
<br />
To make your changes permanent you will need to edit the configuration file to make it active on boot. There is only the vi text editor, you can also install nano. <br />
<syntaxhighlight lang="Bash"><br />
yum install nano<br />
nano /etc/sysconfig/network-scripts/ifcfg-eth0<br />
</syntaxhighlight><br />
and set ONBOOT=”YES”<br />
</div><br />
<br />
==== Enable SSH ====<br />
SSH is present but is disabled at this stage. To enable ssh issue:<br />
<syntaxhighlight lang="Bash"><br />
service sshd start<br />
</syntaxhighlight><br />
<br />
<br />
==== Disable / Remove SELinux ====<br />
It will be easier to see what's going on (and turn off selinux at kernel level, just to be sure)<br />
<syntaxhighlight lang="Bash"><br />
sed -i -e 's/rhgb quiet/selinux=0/g' /boot/grub/grub.conf<br />
<br />
sed -i -e 's/SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config<br />
<br />
yum remove selinux-policy-targeted<br />
<br />
setenforce 0<br />
</syntaxhighlight><br />
<br />
== Configure basic requirements ==<br />
==== Configure SME9 repositories ====<br />
<br />
See the following bugs tracking issues with repositories:<br />
* [[bugzilla:7294|Bug #7294: rpms that still need to be rebuilt or sourced for the SME9 repositories]]<br />
* [[bugzilla:7298|Bug #7298: Import perl-Unix-ConfigFile from rpmforge]]<br />
* [[bugzilla:7292|Bug #7292: more rpms in the SME8 repositories that have a lower version in our SME9 repositories]]<br />
* [[bugzilla:7305|Bug #7305: smeserver-yum doesn't provide the /etc/yum.smerepos.d dir]]<br />
<br />
<syntaxhighlight lang="Bash"><br />
yum install wget<br />
</syntaxhighlight><br />
<syntaxhighlight lang="Bash"><br />
mkdir /tmp/repo.bak<br />
mv /etc/yum.repos.d/*.repo /tmp/repo.bak/<br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3650<br />
</syntaxhighlight><br />
<br />
==== Import needed GPG Keys ====<br />
<syntaxhighlight lang="Bash"><br />
rpm --import http://sme-mirror.firewall-services.com/releases/8/smeos/x86_64/RPM-GPG-KEY-SMEServer<br />
rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt<br />
rpm --import https://fedoraproject.org/static/217521F6.txt<br />
rpm --import http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br />
rpm --import http://www.salstar.sk/pub/yum/keys/RPM-GPG-KEY-Fedora-Pre-Extras<br />
</syntaxhighlight><br />
<br />
==== Clean yum cache ====<br />
<syntaxhighlight lang="Bash"><br />
yum --enablerepo=* clean all<br />
</syntaxhighlight><br />
<br />
<br />
==== Install e-smith and smeserver packages ====<br />
Now, you should be ready to install all the e-smith and smeserver packages (and their dependencies), plus the rest of the rpms that aren't required by a smeserver- or e-smith- rpm, but were installed on SME8 [[bugzilla:7311]]. This should pull about 501 packages to install, and 14 to update, and then you can do 'yum upgrade' to upgrade the remaining CentOS packages. Some other notes on this in [[bugzilla:7240]]<br />
<pre style="white-space:normal;"> <br />
yum --disablerepo=* --enablerepo=smeupdates9,smeupdates-testing9,smeos8,smeupdates8 install e-smith\* smeserver\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync<br />
</pre><br />
<pre><br />
yum upgrade<br />
</pre><br />
<br />
See the following bugs:<br />
*[[bugzilla:7233|Bug #7233: e-smith-ldap should require openldap-servers]]<br />
*[[bugzilla:7252|Bug #7252: e-smith-radiusd should require freeradius-ldap]]<br />
*[[bugzilla:7234|Bug #7234: e-smith-apache should require mod_ssl]]<br />
*[[bugzilla:7297|Bug #7297: e-smith-hosts should require dhcp]]<br />
<br />
==== Move everything from rc7.d to rc4.d ====<br />
All the links in rc4.d should then point to e-smith-service<br />
<syntaxhighlight lang="Bash"><br />
rm -f /etc/rc4.d/*<br />
cp -a /etc/rc7.d/* /etc/rc4.d/<br />
</syntaxhighlight><br />
<br />
==== Move some perl modules ====<br />
We need to copy some perl modules to a new directory, because @INC has changed in EL6: [[bugzilla:7223]]<br />
<syntaxhighlight lang="Bash"><br />
cp -a /usr/lib/perl5/site_perl/esmith/* /usr/share/perl5/vendor_perl/esmith<br />
</syntaxhighlight><br />
<br />
==== Create a service entry for rsyslog ====<br />
We need to create a new service entry in the DB, because the standard syslog package is now rsyslog:<br />
* See [[bugzilla:7221|Bug #7221: Change from syslog to rsyslog]] and [[bugzilla:7322|Bug #7322: Change from syslog to rsyslog - Add link]] This step can be removed when e-smith-base-5.4.0-8 is available.<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/db configuration set rsyslog service status enabled<br />
cp -a /etc/rc7.d/S05syslog /etc/rc4.d/S05rsyslog<br />
</syntaxhighlight><br />
<br />
==== Run post-upgrade ====<br />
We can now try to post-upgrade<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</syntaxhighlight><br />
<br />
==== Look for things to fix & Report bugs/problems ====<br />
If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.<br />
<br />
* SME 9 Bug Report Matrix - http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap<br />
* Open a new bug report - http://bugs.contribs.org/enter_bug.cgi<br />
<br />
Some ideas for things to look for:<br />
- Services not starting<br />
- Config files (templates) that need changes, especially if the major version of the package has changed<br />
- add more generic ideas here....specific issues to the bugtracker please<br />
<br />
== SME Server specific/required packages ==<br />
To get a list of all specific SME Server packages you can run:<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa | grep 'smeserver\|e-smith'| sed -e 's/-[0-9].*//' | sort > smeserver-packages.txt<br />
</syntaxhighlight><br />
<br />
<br />
== SME Server specific/required perl packages ==<br />
To get a list of the file names ''containing'' the string 'perl' on a running SME8 server.<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa | grep perl | sed -e 's/-[0-9].*//' | sort<br />
</syntaxhighlight><br />
<br />
or, as per suggestion on the lists (All files ''starting'' with the string 'perl')<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa --qf '%{NAME}\n' name=perl\* | sort<br />
</syntaxhighlight><br />
<br />
To export the list to a plain text file you could do:<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa | grep perl | sed -e 's/-[0-9].*//' | sort > perl-list.txt<br />
</syntaxhighlight><br />
<br />
<br />
perl-Digest-SHA Y<br />
perl Y<br />
perl-Archive-Tar Y<br />
perl-Authen-PAM ******<br />
perl-Authen-SASL Y<br />
perl-BSD-Resource ******<br />
perl-CGI-FormMagick ******<br />
perl-CGI-Persistent ******<br />
perl-Class-ParamParser ******<br />
perl-Clone Y<br />
perl-Compress-Raw-Bzip2 Y<br />
perl-Compress-Raw-Zlib Y<br />
perl-Compress-Zlib Y<br />
perl-Convert-ASN1 Y<br />
perl-Convert-BinHex Y<br />
perl-Convert-TNEF ******<br />
perl-Crypt-Cracklib ******<br />
perl-Crypt-OpenSSL-Bignum Y<br />
perl-Crypt-OpenSSL-Random Y<br />
perl-Crypt-OpenSSL-RSA Y<br />
perl-DateManip Y<br />
perl-DBD-MySQL Y<br />
perl-DBI Y<br />
perl-Digest-HMAC Y<br />
perl-Digest-SHA1 Y<br />
perl-Email-Date-Format Y<br />
perl-Encode-Detect Y<br />
perl-Error Y<br />
perl-File-MMagic ******<br />
perl-Geography-Countries ******<br />
perl-HTML-Parser Y<br />
perl-HTML-Tabulate ******<br />
perl-HTML-Tagset Y<br />
perl-I18N-AcceptLanguage ******<br />
perl-IO-Compress-Base Y<br />
perl-IO-Compress-Bzip2 Y<br />
perl-IO-Compress-Zlib Y<br />
perl-IO-Socket-INET6 Y<br />
perl-IO-Socket-SSL Y<br />
perl-IO-stringy Y<br />
perl-IO-Zlib Y<br />
perl-IP-Country ******<br />
perl-LDAP Y<br />
perl-libwww-perl Y<br />
perl-Locale-gettext ******<br />
perl-Mail-DKIM Y<br />
perl-Mail-RFC822-Address ******<br />
perl-Mail-SPF ******<br />
perl-MailTools Y<br />
perl-MIME-Lite Y<br />
perl-MIME-tools Y<br />
perl-Net-DNS Y<br />
perl-Net-Ident ******<br />
perl-Net-IP Y<br />
perl-Net-IPv4Addr ******<br />
perl-Net-SMTP-SSL Y<br />
perl-Net-SSLeay Y<br />
perl-NetAddr-IP Y<br />
perl-Object-Persistence ******<br />
perl-Package-Constants Y<br />
perl-Quota ******<br />
perl-Razor-Agent ******<br />
perl-RPM2 ******<br />
perl-Socket6 Y<br />
perl-suidperl Y<br />
perl-Test-Inline ******<br />
perl-Text-Iconv Y<br />
perl-Text-Template ******<br />
perl-Time-TAI64 ******<br />
perl-TimeDate Y<br />
perl-Unix-ConfigFile ******<br />
perl-URI Y<br />
perl-version Y<br />
perl-WWW-Automate ******<br />
perl-XML-NamespaceSupport Y<br />
perl-XML-Parser Y<br />
perl-XML-SAX Y<br />
<br />
<br />
I am now going to try and lob in the existing/missing el5 versions to see what happens. My guess is we will need to rebuild the required modules.<br />
<br />
<br />
== FormMagick ==<br />
Next will be an attack on FormMagick - there is no package in the default install so need to figure that out. In may indeed be horrible, but we can live with it for now.<br />
<br />
Hopefully with perl and FormMagick installed, most of the SME stuff *should* basically install.<br />
<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
<br />
==== Kickstart file ====<br />
* A starting point can be found on the [[SME9_Kickstart| SME9 Kickstart]] page.<br />
<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_on_CentOS_6&diff=18350SME on CentOS 62013-02-09T06:27:24Z<p>Gregswallow: </p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9, based on CentOS 6 ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
<br />
=== Prerequisites ===<br />
* VIrtual machine (Vmware, Parallels or Virtualbox)<br />
* Centos Minimal 64-bit architecture. 32-bit may follow later<br />
* [[Setting_up_RPM_Building_for_SME_Server|Setting up a RPM Building environment]]<br />
<br />
=== User Feedback ===<br />
Unstructured user feedback can be noted here: [[SME9DEV_user_feedback|SME9DEV user feedback]]. Issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
<br />
=== Bugs ===<br />
[http://bugs.contribs.org/bugs/buglist.cgi?product=SME%20Server%209.X&component=Cleanup&resolution=--- Bug Tracker] <br />
[http://wiki.contribs.org/SME9BuildQueue#SME_9_Error_list_and_affected_packages SME 9 error list]<br />
<br />
=== Considerations ===<br />
* Primary and only goal for now is the transition of SME Server based on CentOS 5.8 to SME Server based on CentOS6.3<br />
* SysVinit is no longer the default with the release of RHEL6, beyond RHEL6 systemd will be used<br />
* perl has a new location of the filesystem. New: /usr/share/perl5/vendor_perl instead Old: /usr/lib/perl5/site_perl/<br />
* perl version 5.8.8 is the new default version on RHEL6. This requires a review of all the perl module rpms which are specific for perl 5.8.5<br />
<br />
== Installing CentOS 6 minimal ==<br />
First a few notes on CentOS 6 minimal, which is a bare bones install with very little on board. You can download a copy from one of the CentOS mirrors [http://www.centos.org/modules/tinycontent/index.php?id=30 here]<br />
<br />
* As per above note, only use Virtual Machine for testing purposes. A good free VM package can be obtained [https://www.virtualbox.org/wiki/Downloads here]<br />
* You might want to note down as much as possible so you yourself and others can reproduce the actions<br />
* Don't use yum with the '-y' flag (install/upgrade without further user interaction) when using the yum install/upgrade commands. (beware copy/paste yum commands)<br />
* you might want to note down all packages listed by yum to be installed/upgraded AND their dependencies<br />
* Make regular snapshots of your Virtual Machine and describe them specifically. At least when you've reached an important milestone for yourself<br />
<br />
<br />
==== Installing the ISO ====<br />
* Just install a minimal el6 installation (I just installed a few utilities like htop, screen, rsync, vim, openssh-clients mc etc…). You can use either the DVD, the minimal CD install, a net install with PXE, it's up to you<br />
* wellsi: I have used CentOS-6.3-x86_64-minimal.iso<br />
<br />
<br />
==== Enable networking ====<br />
Each boot you have to start the network etc etc. I decided it was better with the minimal install and touch as little as possible - if I could then get SME packages installed I could then use that to configure networking later.<br />
<br />
To start the networking <br />
<syntaxhighlight lang="Bash"><br />
./etc/sysconfig/network-scripts/ifup-eth eth0<br />
</syntaxhighlight><br />
<br />
or <br />
<syntaxhighlight lang="Bash"><br />
dhclient eth0<br />
</syntaxhighlight><br />
<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="Collapse" data-expandtext="More on networking"><br />
or if you want to assign a specific IP address (e.g. 192.168.1.2).<br />
<syntaxhighlight lang="Bash"><br />
ifconfig eth0 192.168.1.2<br />
echo "nameserver 192.168.1.254" >> /etc/resolv.conf<br />
route add default gw 192.168.1.254 eth0<br />
</syntaxhighlight> <br />
<br />
To make your changes permanent you will need to edit the configuration file to make it active on boot. There is only the vi text editor, you can also install nano. <br />
<syntaxhighlight lang="Bash"><br />
yum install nano<br />
nano /etc/sysconfig/network-scripts/ifcfg-eth0<br />
</syntaxhighlight><br />
and set ONBOOT=”YES”<br />
</div><br />
<br />
==== Enable SSH ====<br />
SSH is present but is disabled at this stage. To enable ssh issue:<br />
<syntaxhighlight lang="Bash"><br />
service sshd start<br />
</syntaxhighlight><br />
<br />
<br />
==== Disable / Remove SELinux ====<br />
It will be easier to see what's going on (and turn off selinux at kernel level, just to be sure)<br />
<syntaxhighlight lang="Bash"><br />
sed -i -e 's/rhgb quiet/selinux=0/g' /boot/grub/grub.conf<br />
<br />
sed -i -e 's/SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config<br />
<br />
yum remove selinux-policy-targeted<br />
<br />
setenforce 0<br />
</syntaxhighlight><br />
<br />
== Configure basic requirements ==<br />
==== Configure SME9 repositories ====<br />
<br />
See the following bugs tracking issues with repositories:<br />
* [[bugzilla:7294|Bug #7294: rpms that still need to be rebuilt or sourced for the SME9 repositories]]<br />
* [[bugzilla:7298|Bug #7298: Import perl-Unix-ConfigFile from rpmforge]]<br />
* [[bugzilla:7292|Bug #7292: more rpms in the SME8 repositories that have a lower version in our SME9 repositories]]<br />
* [[bugzilla:7305|Bug #7305: smeserver-yum doesn't provide the /etc/yum.smerepos.d dir]]<br />
<br />
<syntaxhighlight lang="Bash"><br />
yum install wget<br />
</syntaxhighlight><br />
<syntaxhighlight lang="Bash"><br />
mkdir /tmp/repo.bak<br />
mv /etc/yum.repos.d/*.repo /tmp/repo.bak/<br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3650<br />
</syntaxhighlight><br />
<br />
==== Import needed GPG Keys ====<br />
<syntaxhighlight lang="Bash"><br />
rpm --import http://sme-mirror.firewall-services.com/releases/8/smeos/x86_64/RPM-GPG-KEY-SMEServer<br />
rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt<br />
rpm --import https://fedoraproject.org/static/217521F6.txt<br />
rpm --import http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br />
rpm --import http://www.salstar.sk/pub/yum/keys/RPM-GPG-KEY-Fedora-Pre-Extras<br />
</syntaxhighlight><br />
<br />
==== Clean yum cache ====<br />
<syntaxhighlight lang="Bash"><br />
yum --enablerepo=* clean all<br />
</syntaxhighlight><br />
<br />
<br />
==== Install e-smith and smeserver packages ====<br />
Now, you should be ready to install all the e-smith and smeserver packages (and their dependencies), plus the rest of the rpms that aren't required by a smeserver- or e-smith- rpm, but were installed on SME8 [[bugzilla:7311]]. This should pull about 501 packages to install, and 14 to update, and then you can do 'yum upgrade' to upgrade the remaining CentOS packages. Some other notes on this in [[bugzilla:7240]]<br />
<pre style="white-space:normal;"> <br />
yum --disablerepo=* --enablerepo=smeupdates9,smeupdates-testing9,smeos8,smeupdates8 install e-smith\* smeserver\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync<br />
</pre><br />
<pre><br />
yum upgrade<br />
</pre><br />
<br />
See the following bugs:<br />
*[[bugzilla:7233|Bug #7233: e-smith-ldap should require openldap-servers]]<br />
*[[bugzilla:7252|Bug #7252: e-smith-radiusd should require freeradius-ldap]]<br />
*[[bugzilla:7234|Bug #7234: e-smith-apache should require mod_ssl]]<br />
*[[bugzilla:7297|Bug #7297: e-smith-hosts should require dhcp]]<br />
<br />
==== Move everything from rc7.d to rc4.d ====<br />
All the links in rc4.d should then point to e-smith-service<br />
<syntaxhighlight lang="Bash"><br />
rm -f /etc/rc4.d/*<br />
cp -a /etc/rc7.d/* /etc/rc4.d/<br />
</syntaxhighlight><br />
<br />
==== Move some perl modules ====<br />
We need to copy some perl modules to a new directory, because @INC has changed in EL6: [[bugzilla:7223]]<br />
<syntaxhighlight lang="Bash"><br />
cp -a /usr/lib/perl5/site_perl/esmith/* /usr/share/perl5/vendor_perl/esmith<br />
</syntaxhighlight><br />
<br />
==== Create a service entry for rsyslog ====<br />
We need to create a new service entry in the DB, because the standard syslog package is now rsyslog:<br />
* See [[bugzilla:7221|Bug #7221: Change from syslog to rsyslog]] and [[bugzilla:7322|Bug #7322: Change from syslog to rsyslog - Add link]] This step can be removed when e-smith-base-5.4.0-8 is available.<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/db configuration set rsyslog service status enabled<br />
cp -a /etc/rc7.d/S05syslog /etc/rc4.d/S05rsyslog<br />
</syntaxhighlight><br />
<br />
==== Run post-upgrade ====<br />
We can now try to post-upgrade<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</syntaxhighlight><br />
<br />
==== The system boots but completly broken :-) ====<br />
Ok, so the system should now boot, but is really not usable, after a quick look, at least the following doesn't work as expected:<br />
<br />
* The console on the first boot don't really work. It asks for the admin password <strike>(and BTW the password appears in cleartext)</strike> but it's all<br />
* <strike>No network interfaces are detected by the console menu (because kudzu is not installed, only available in SME repo, and require an older python which conflicts with the the one * from EL6)</strike><br />
* slapd won't start<br />
* httpd won't start<br />
* squid won't start<br />
* manually running expand-template has no effect (and no error message is printed). But signal-event seems to work (files get expanded and services restarted)<br />
* as the network interface are not configured, all the services which requires the internel IP (or the external one) in their config (at least sshd squid and dnscache) won't start<br />
* <strike>qpsmtpd won't start (can't locate Qpsmtpd/TcpServer.pm in @INC)</strike><br />
* There's probably a lot more which is not working<br />
<br />
<br />
* wellsi: Is there an easy way to get SSH access to it at this point?<br />
<br />
== SME Server specific/required packages ==<br />
To get a list of all specific SME Server packages you can run:<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa | grep 'smeserver\|e-smith'| sed -e 's/-[0-9].*//' | sort > smeserver-packages.txt<br />
</syntaxhighlight><br />
<br />
<br />
== SME Server specific/required perl packages ==<br />
To get a list of the file names ''containing'' the string 'perl' on a running SME8 server.<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa | grep perl | sed -e 's/-[0-9].*//' | sort<br />
</syntaxhighlight><br />
<br />
or, as per suggestion on the lists (All files ''starting'' with the string 'perl')<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa --qf '%{NAME}\n' name=perl\* | sort<br />
</syntaxhighlight><br />
<br />
To export the list to a plain text file you could do:<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa | grep perl | sed -e 's/-[0-9].*//' | sort > perl-list.txt<br />
</syntaxhighlight><br />
<br />
<br />
perl-Digest-SHA Y<br />
perl Y<br />
perl-Archive-Tar Y<br />
perl-Authen-PAM ******<br />
perl-Authen-SASL Y<br />
perl-BSD-Resource ******<br />
perl-CGI-FormMagick ******<br />
perl-CGI-Persistent ******<br />
perl-Class-ParamParser ******<br />
perl-Clone Y<br />
perl-Compress-Raw-Bzip2 Y<br />
perl-Compress-Raw-Zlib Y<br />
perl-Compress-Zlib Y<br />
perl-Convert-ASN1 Y<br />
perl-Convert-BinHex Y<br />
perl-Convert-TNEF ******<br />
perl-Crypt-Cracklib ******<br />
perl-Crypt-OpenSSL-Bignum Y<br />
perl-Crypt-OpenSSL-Random Y<br />
perl-Crypt-OpenSSL-RSA Y<br />
perl-DateManip Y<br />
perl-DBD-MySQL Y<br />
perl-DBI Y<br />
perl-Digest-HMAC Y<br />
perl-Digest-SHA1 Y<br />
perl-Email-Date-Format Y<br />
perl-Encode-Detect Y<br />
perl-Error Y<br />
perl-File-MMagic ******<br />
perl-Geography-Countries ******<br />
perl-HTML-Parser Y<br />
perl-HTML-Tabulate ******<br />
perl-HTML-Tagset Y<br />
perl-I18N-AcceptLanguage ******<br />
perl-IO-Compress-Base Y<br />
perl-IO-Compress-Bzip2 Y<br />
perl-IO-Compress-Zlib Y<br />
perl-IO-Socket-INET6 Y<br />
perl-IO-Socket-SSL Y<br />
perl-IO-stringy Y<br />
perl-IO-Zlib Y<br />
perl-IP-Country ******<br />
perl-LDAP Y<br />
perl-libwww-perl Y<br />
perl-Locale-gettext ******<br />
perl-Mail-DKIM Y<br />
perl-Mail-RFC822-Address ******<br />
perl-Mail-SPF ******<br />
perl-MailTools Y<br />
perl-MIME-Lite Y<br />
perl-MIME-tools Y<br />
perl-Net-DNS Y<br />
perl-Net-Ident ******<br />
perl-Net-IP Y<br />
perl-Net-IPv4Addr ******<br />
perl-Net-SMTP-SSL Y<br />
perl-Net-SSLeay Y<br />
perl-NetAddr-IP Y<br />
perl-Object-Persistence ******<br />
perl-Package-Constants Y<br />
perl-Quota ******<br />
perl-Razor-Agent ******<br />
perl-RPM2 ******<br />
perl-Socket6 Y<br />
perl-suidperl Y<br />
perl-Test-Inline ******<br />
perl-Text-Iconv Y<br />
perl-Text-Template ******<br />
perl-Time-TAI64 ******<br />
perl-TimeDate Y<br />
perl-Unix-ConfigFile ******<br />
perl-URI Y<br />
perl-version Y<br />
perl-WWW-Automate ******<br />
perl-XML-NamespaceSupport Y<br />
perl-XML-Parser Y<br />
perl-XML-SAX Y<br />
<br />
<br />
I am now going to try and lob in the existing/missing el5 versions to see what happens. My guess is we will need to rebuild the required modules.<br />
<br />
<br />
== FormMagick ==<br />
Next will be an attack on FormMagick - there is no package in the default install so need to figure that out. In may indeed be horrible, but we can live with it for now.<br />
<br />
Hopefully with perl and FormMagick installed, most of the SME stuff *should* basically install.<br />
<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
<br />
==== Kickstart file ====<br />
* A starting point can be found on the [[SME9_Kickstart| SME9 Kickstart]] page.<br />
<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_on_CentOS_6&diff=18349SME on CentOS 62013-02-08T22:19:38Z<p>Gregswallow: /* Install e-smith and smeserver packages */</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9, based on CentOS 6 ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
<br />
=== Prerequisites ===<br />
* VIrtual machine (Vmware, Parallels or Virtualbox)<br />
* Centos Minimal 64-bit architecture. 32-bit may follow later<br />
* [[Setting_up_RPM_Building_for_SME_Server|Setting up a RPM Building environment]]<br />
<br />
=== User Feedback ===<br />
Unstructured user feedback can be noted here: [[SME9DEV_user_feedback|SME9DEV user feedback]]. Issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
<br />
=== Bugs ===<br />
[http://bugs.contribs.org/bugs/buglist.cgi?product=SME%20Server%209.X&component=Cleanup&resolution=--- Bug Tracker] <br />
[http://wiki.contribs.org/SME9BuildQueue#SME_9_Error_list_and_affected_packages SME 9 error list]<br />
<br />
=== Considerations ===<br />
* Primary and only goal for now is the transition of SME Server based on CentOS 5.8 to SME Server based on CentOS6.3<br />
* SysVinit is no longer the default with the release of RHEL6, beyond RHEL6 systemd will be used<br />
* perl has a new location of the filesystem. New: /usr/share/perl5/vendor_perl instead Old: /usr/lib/perl5/site_perl/<br />
* perl version 5.8.8 is the new default version on RHEL6. This requires a review of all the perl module rpms which are specific for perl 5.8.5<br />
<br />
== Installing CentOS 6 minimal ==<br />
First a few notes on CentOS 6 minimal, which is a bare bones install with very little on board. You can download a copy from one of the CentOS mirrors [http://www.centos.org/modules/tinycontent/index.php?id=30 here]<br />
<br />
* As per above note, only use Virtual Machine for testing purposes. A good free VM package can be obtained [https://www.virtualbox.org/wiki/Downloads here]<br />
* You might want to note down as much as possible so you yourself and others can reproduce the actions<br />
* Don't use yum with the '-y' flag (install/upgrade without further user interaction) when using the yum install/upgrade commands. (beware copy/paste yum commands)<br />
* you might want to note down all packages listed by yum to be installed/upgraded AND their dependencies<br />
* Make regular snapshots of your Virtual Machine and describe them specifically. At least when you've reached an important milestone for yourself<br />
<br />
<br />
==== Installing the ISO ====<br />
* Just install a minimal el6 installation (I just installed a few utilities like htop, screen, rsync, vim, openssh-clients mc etc…). You can use either the DVD, the minimal CD install, a net install with PXE, it's up to you<br />
* wellsi: I have used CentOS-6.3-x86_64-minimal.iso<br />
<br />
<br />
==== Enable networking ====<br />
Each boot you have to start the network etc etc. I decided it was better with the minimal install and touch as little as possible - if I could then get SME packages installed I could then use that to configure networking later.<br />
<br />
To start the networking <br />
<syntaxhighlight lang="Bash"><br />
./etc/sysconfig/network-scripts/ifup-eth eth0<br />
</syntaxhighlight><br />
<br />
or <br />
<syntaxhighlight lang="Bash"><br />
dhclient eth0<br />
</syntaxhighlight><br />
<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="Collapse" data-expandtext="More on networking"><br />
or if you want to assign a specific IP address (e.g. 192.168.1.2).<br />
<syntaxhighlight lang="Bash"><br />
ifconfig eth0 192.168.1.2<br />
echo "nameserver 192.168.1.254" >> /etc/resolv.conf<br />
route add default gw 192.168.1.254 eth0<br />
</syntaxhighlight> <br />
<br />
To make your changes permanent you will need to edit the configuration file to make it active on boot. There is only the vi text editor, you can also install nano. <br />
<syntaxhighlight lang="Bash"><br />
yum install nano<br />
nano /etc/sysconfig/network-scripts/ifcfg-eth0<br />
</syntaxhighlight><br />
and set ONBOOT=”YES”<br />
</div><br />
<br />
==== Enable SSH ====<br />
SSH is present but is disabled at this stage. To enable ssh issue:<br />
<syntaxhighlight lang="Bash"><br />
service sshd start<br />
</syntaxhighlight><br />
<br />
<br />
==== Disable SELinux ====<br />
It will be easier to see what's going on (and turn off selinux at kernel level, just to be sure)<br />
<syntaxhighlight lang="Bash"><br />
sed -i -e 's/rhgb quiet/selinux=0/g' /boot/grub/grub.conf<br />
sed -i -e 's/SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config<br />
</syntaxhighlight><br />
<br />
<br />
==== Remove selinux-policy-targeted ====<br />
They conflict with some e-smith/smeserver packages<br />
<syntaxhighlight lang="Bash"><br />
yum remove selinux-policy-targeted<br />
</syntaxhighlight><br />
<br />
==reboot==<br />
I think a reboot is in order here, to boot with selinux disabled. That is what i did anyways....Greg<br />
* Wouldn't <syntaxhighlight lang="Bash">setenforce 0</syntaxhighlight> do the job instead of a reboot?<br />
<br />
== Configure basic requirements ==<br />
==== Configure SME9 repositories ====<br />
<br />
See the following bugs tracking issues with repositories:<br />
* [[bugzilla:7294|Bug #7294: rpms that still need to be rebuilt or sourced for the SME9 repositories]]<br />
* [[bugzilla:7298|Bug #7298: Import perl-Unix-ConfigFile from rpmforge]]<br />
* [[bugzilla:7292|Bug #7292: more rpms in the SME8 repositories that have a lower version in our SME9 repositories]]<br />
* [[bugzilla:7305|Bug #7305: smeserver-yum doesn't provide the /etc/yum.smerepos.d dir]]<br />
<br />
<syntaxhighlight lang="Bash"><br />
yum install wget<br />
</syntaxhighlight><br />
<syntaxhighlight lang="Bash"><br />
mkdir /tmp/repo.bak<br />
mv /etc/yum.repos.d/*.repo /tmp/repo.bak/<br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3650<br />
</syntaxhighlight><br />
<br />
==== Import needed GPG Keys ====<br />
<syntaxhighlight lang="Bash"><br />
rpm --import http://sme-mirror.firewall-services.com/releases/8/smeos/x86_64/RPM-GPG-KEY-SMEServer<br />
rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt<br />
rpm --import https://fedoraproject.org/static/217521F6.txt<br />
rpm --import http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br />
rpm --import http://www.salstar.sk/pub/yum/keys/RPM-GPG-KEY-Fedora-Pre-Extras<br />
</syntaxhighlight><br />
<br />
==== Clean yum cache ====<br />
<syntaxhighlight lang="Bash"><br />
yum --enablerepo=* clean all<br />
</syntaxhighlight><br />
<br />
<br />
==== Install e-smith and smeserver packages ====<br />
Now, you should be ready to install all the e-smith and smeserver packages (and their dependencies), plus the rest of the rpms that aren't required by a smeserver- or e-smith- rpm, but were installed on SME8 [[bugzilla:7311]]. This should pull about 501 packages to install, and 14 to update, and then you can do 'yum upgrade' to upgrade the remaining CentOS packages. Some other notes on this in [[bugzilla:7240]]<br />
<pre style="white-space:normal;"> <br />
yum --disablerepo=* --enablerepo=smeupdates9,smeupdates-testing9,smeos8,smeupdates8 install e-smith\* smeserver\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync<br />
</pre><br />
<pre><br />
yum upgrade<br />
</pre><br />
<br />
See the following bugs:<br />
*[[bugzilla:7233|Bug #7233: e-smith-ldap should require openldap-servers]]<br />
*[[bugzilla:7252|Bug #7252: e-smith-radiusd should require freeradius-ldap]]<br />
*[[bugzilla:7234|Bug #7234: e-smith-apache should require mod_ssl]]<br />
*[[bugzilla:7297|Bug #7297: e-smith-hosts should require dhcp]]<br />
<br />
==== Move everything from rc7.d to rc4.d ====<br />
All the links in rc4.d should then point to e-smith-service<br />
<syntaxhighlight lang="Bash"><br />
rm -f /etc/rc4.d/*<br />
cp -a /etc/rc7.d/* /etc/rc4.d/<br />
</syntaxhighlight><br />
<br />
==== Move some perl modules ====<br />
We need to copy some perl modules to a new directory, because @INC has changed in EL6: [[bugzilla:7223]]<br />
<syntaxhighlight lang="Bash"><br />
cp -a /usr/lib/perl5/site_perl/esmith/* /usr/share/perl5/vendor_perl/esmith<br />
</syntaxhighlight><br />
<br />
==== Create a service entry for rsyslog ====<br />
We need to create a new service entry in the DB, because the standard syslog package is now rsyslog:<br />
* See [[bugzilla:7221|Bug #7221: Change from syslog to rsyslog]] and [[bugzilla:7322|Bug #7322: Change from syslog to rsyslog - Add link]] This step can be removed when e-smith-base-5.4.0-8 is available.<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/db configuration set rsyslog service status enabled<br />
cp -a /etc/rc7.d/S05syslog /etc/rc4.d/S05rsyslog<br />
</syntaxhighlight><br />
<br />
==== Run post-upgrade ====<br />
We can now try to post-upgrade<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</syntaxhighlight><br />
<br />
==== The system boots but completly broken :-) ====<br />
Ok, so the system should now boot, but is really not usable, after a quick look, at least the following doesn't work as expected:<br />
<br />
* The console on the first boot don't really work. It asks for the admin password <strike>(and BTW the password appears in cleartext)</strike> but it's all<br />
* <strike>No network interfaces are detected by the console menu (because kudzu is not installed, only available in SME repo, and require an older python which conflicts with the the one * from EL6)</strike><br />
* slapd won't start<br />
* httpd won't start<br />
* squid won't start<br />
* manually running expand-template has no effect (and no error message is printed). But signal-event seems to work (files get expanded and services restarted)<br />
* as the network interface are not configured, all the services which requires the internel IP (or the external one) in their config (at least sshd squid and dnscache) won't start<br />
* <strike>qpsmtpd won't start (can't locate Qpsmtpd/TcpServer.pm in @INC)</strike><br />
* There's probably a lot more which is not working<br />
<br />
<br />
* wellsi: Is there an easy way to get SSH access to it at this point?<br />
<br />
== SME Server specific/required packages ==<br />
To get a list of all specific SME Server packages you can run:<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa | grep 'smeserver\|e-smith'| sed -e 's/-[0-9].*//' | sort > smeserver-packages.txt<br />
</syntaxhighlight><br />
<br />
<br />
== SME Server specific/required perl packages ==<br />
To get a list of the file names ''containing'' the string 'perl' on a running SME8 server.<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa | grep perl | sed -e 's/-[0-9].*//' | sort<br />
</syntaxhighlight><br />
<br />
or, as per suggestion on the lists (All files ''starting'' with the string 'perl')<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa --qf '%{NAME}\n' name=perl\* | sort<br />
</syntaxhighlight><br />
<br />
To export the list to a plain text file you could do:<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa | grep perl | sed -e 's/-[0-9].*//' | sort > perl-list.txt<br />
</syntaxhighlight><br />
<br />
<br />
perl-Digest-SHA Y<br />
perl Y<br />
perl-Archive-Tar Y<br />
perl-Authen-PAM ******<br />
perl-Authen-SASL Y<br />
perl-BSD-Resource ******<br />
perl-CGI-FormMagick ******<br />
perl-CGI-Persistent ******<br />
perl-Class-ParamParser ******<br />
perl-Clone Y<br />
perl-Compress-Raw-Bzip2 Y<br />
perl-Compress-Raw-Zlib Y<br />
perl-Compress-Zlib Y<br />
perl-Convert-ASN1 Y<br />
perl-Convert-BinHex Y<br />
perl-Convert-TNEF ******<br />
perl-Crypt-Cracklib ******<br />
perl-Crypt-OpenSSL-Bignum Y<br />
perl-Crypt-OpenSSL-Random Y<br />
perl-Crypt-OpenSSL-RSA Y<br />
perl-DateManip Y<br />
perl-DBD-MySQL Y<br />
perl-DBI Y<br />
perl-Digest-HMAC Y<br />
perl-Digest-SHA1 Y<br />
perl-Email-Date-Format Y<br />
perl-Encode-Detect Y<br />
perl-Error Y<br />
perl-File-MMagic ******<br />
perl-Geography-Countries ******<br />
perl-HTML-Parser Y<br />
perl-HTML-Tabulate ******<br />
perl-HTML-Tagset Y<br />
perl-I18N-AcceptLanguage ******<br />
perl-IO-Compress-Base Y<br />
perl-IO-Compress-Bzip2 Y<br />
perl-IO-Compress-Zlib Y<br />
perl-IO-Socket-INET6 Y<br />
perl-IO-Socket-SSL Y<br />
perl-IO-stringy Y<br />
perl-IO-Zlib Y<br />
perl-IP-Country ******<br />
perl-LDAP Y<br />
perl-libwww-perl Y<br />
perl-Locale-gettext ******<br />
perl-Mail-DKIM Y<br />
perl-Mail-RFC822-Address ******<br />
perl-Mail-SPF ******<br />
perl-MailTools Y<br />
perl-MIME-Lite Y<br />
perl-MIME-tools Y<br />
perl-Net-DNS Y<br />
perl-Net-Ident ******<br />
perl-Net-IP Y<br />
perl-Net-IPv4Addr ******<br />
perl-Net-SMTP-SSL Y<br />
perl-Net-SSLeay Y<br />
perl-NetAddr-IP Y<br />
perl-Object-Persistence ******<br />
perl-Package-Constants Y<br />
perl-Quota ******<br />
perl-Razor-Agent ******<br />
perl-RPM2 ******<br />
perl-Socket6 Y<br />
perl-suidperl Y<br />
perl-Test-Inline ******<br />
perl-Text-Iconv Y<br />
perl-Text-Template ******<br />
perl-Time-TAI64 ******<br />
perl-TimeDate Y<br />
perl-Unix-ConfigFile ******<br />
perl-URI Y<br />
perl-version Y<br />
perl-WWW-Automate ******<br />
perl-XML-NamespaceSupport Y<br />
perl-XML-Parser Y<br />
perl-XML-SAX Y<br />
<br />
<br />
I am now going to try and lob in the existing/missing el5 versions to see what happens. My guess is we will need to rebuild the required modules.<br />
<br />
<br />
== FormMagick ==<br />
Next will be an attack on FormMagick - there is no package in the default install so need to figure that out. In may indeed be horrible, but we can live with it for now.<br />
<br />
Hopefully with perl and FormMagick installed, most of the SME stuff *should* basically install.<br />
<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
<br />
==== Kickstart file ====<br />
* A starting point can be found on the [[SME9_Kickstart| SME9 Kickstart]] page.<br />
<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_on_CentOS_6&diff=18348SME on CentOS 62013-02-08T22:19:09Z<p>Gregswallow: /* Install e-smith and smeserver packages */</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9, based on CentOS 6 ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
<br />
=== Prerequisites ===<br />
* VIrtual machine (Vmware, Parallels or Virtualbox)<br />
* Centos Minimal 64-bit architecture. 32-bit may follow later<br />
* [[Setting_up_RPM_Building_for_SME_Server|Setting up a RPM Building environment]]<br />
<br />
=== User Feedback ===<br />
Unstructured user feedback can be noted here: [[SME9DEV_user_feedback|SME9DEV user feedback]]. Issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
<br />
=== Bugs ===<br />
[http://bugs.contribs.org/bugs/buglist.cgi?product=SME%20Server%209.X&component=Cleanup&resolution=--- Bug Tracker] <br />
[http://wiki.contribs.org/SME9BuildQueue#SME_9_Error_list_and_affected_packages SME 9 error list]<br />
<br />
=== Considerations ===<br />
* Primary and only goal for now is the transition of SME Server based on CentOS 5.8 to SME Server based on CentOS6.3<br />
* SysVinit is no longer the default with the release of RHEL6, beyond RHEL6 systemd will be used<br />
* perl has a new location of the filesystem. New: /usr/share/perl5/vendor_perl instead Old: /usr/lib/perl5/site_perl/<br />
* perl version 5.8.8 is the new default version on RHEL6. This requires a review of all the perl module rpms which are specific for perl 5.8.5<br />
<br />
== Installing CentOS 6 minimal ==<br />
First a few notes on CentOS 6 minimal, which is a bare bones install with very little on board. You can download a copy from one of the CentOS mirrors [http://www.centos.org/modules/tinycontent/index.php?id=30 here]<br />
<br />
* As per above note, only use Virtual Machine for testing purposes. A good free VM package can be obtained [https://www.virtualbox.org/wiki/Downloads here]<br />
* You might want to note down as much as possible so you yourself and others can reproduce the actions<br />
* Don't use yum with the '-y' flag (install/upgrade without further user interaction) when using the yum install/upgrade commands. (beware copy/paste yum commands)<br />
* you might want to note down all packages listed by yum to be installed/upgraded AND their dependencies<br />
* Make regular snapshots of your Virtual Machine and describe them specifically. At least when you've reached an important milestone for yourself<br />
<br />
<br />
==== Installing the ISO ====<br />
* Just install a minimal el6 installation (I just installed a few utilities like htop, screen, rsync, vim, openssh-clients mc etc…). You can use either the DVD, the minimal CD install, a net install with PXE, it's up to you<br />
* wellsi: I have used CentOS-6.3-x86_64-minimal.iso<br />
<br />
<br />
==== Enable networking ====<br />
Each boot you have to start the network etc etc. I decided it was better with the minimal install and touch as little as possible - if I could then get SME packages installed I could then use that to configure networking later.<br />
<br />
To start the networking <br />
<syntaxhighlight lang="Bash"><br />
./etc/sysconfig/network-scripts/ifup-eth eth0<br />
</syntaxhighlight><br />
<br />
or <br />
<syntaxhighlight lang="Bash"><br />
dhclient eth0<br />
</syntaxhighlight><br />
<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="Collapse" data-expandtext="More on networking"><br />
or if you want to assign a specific IP address (e.g. 192.168.1.2).<br />
<syntaxhighlight lang="Bash"><br />
ifconfig eth0 192.168.1.2<br />
echo "nameserver 192.168.1.254" >> /etc/resolv.conf<br />
route add default gw 192.168.1.254 eth0<br />
</syntaxhighlight> <br />
<br />
To make your changes permanent you will need to edit the configuration file to make it active on boot. There is only the vi text editor, you can also install nano. <br />
<syntaxhighlight lang="Bash"><br />
yum install nano<br />
nano /etc/sysconfig/network-scripts/ifcfg-eth0<br />
</syntaxhighlight><br />
and set ONBOOT=”YES”<br />
</div><br />
<br />
==== Enable SSH ====<br />
SSH is present but is disabled at this stage. To enable ssh issue:<br />
<syntaxhighlight lang="Bash"><br />
service sshd start<br />
</syntaxhighlight><br />
<br />
<br />
==== Disable SELinux ====<br />
It will be easier to see what's going on (and turn off selinux at kernel level, just to be sure)<br />
<syntaxhighlight lang="Bash"><br />
sed -i -e 's/rhgb quiet/selinux=0/g' /boot/grub/grub.conf<br />
sed -i -e 's/SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config<br />
</syntaxhighlight><br />
<br />
<br />
==== Remove selinux-policy-targeted ====<br />
They conflict with some e-smith/smeserver packages<br />
<syntaxhighlight lang="Bash"><br />
yum remove selinux-policy-targeted<br />
</syntaxhighlight><br />
<br />
==reboot==<br />
I think a reboot is in order here, to boot with selinux disabled. That is what i did anyways....Greg<br />
* Wouldn't <syntaxhighlight lang="Bash">setenforce 0</syntaxhighlight> do the job instead of a reboot?<br />
<br />
== Configure basic requirements ==<br />
==== Configure SME9 repositories ====<br />
<br />
See the following bugs tracking issues with repositories:<br />
* [[bugzilla:7294|Bug #7294: rpms that still need to be rebuilt or sourced for the SME9 repositories]]<br />
* [[bugzilla:7298|Bug #7298: Import perl-Unix-ConfigFile from rpmforge]]<br />
* [[bugzilla:7292|Bug #7292: more rpms in the SME8 repositories that have a lower version in our SME9 repositories]]<br />
* [[bugzilla:7305|Bug #7305: smeserver-yum doesn't provide the /etc/yum.smerepos.d dir]]<br />
<br />
<syntaxhighlight lang="Bash"><br />
yum install wget<br />
</syntaxhighlight><br />
<syntaxhighlight lang="Bash"><br />
mkdir /tmp/repo.bak<br />
mv /etc/yum.repos.d/*.repo /tmp/repo.bak/<br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3650<br />
</syntaxhighlight><br />
<br />
==== Import needed GPG Keys ====<br />
<syntaxhighlight lang="Bash"><br />
rpm --import http://sme-mirror.firewall-services.com/releases/8/smeos/x86_64/RPM-GPG-KEY-SMEServer<br />
rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt<br />
rpm --import https://fedoraproject.org/static/217521F6.txt<br />
rpm --import http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br />
rpm --import http://www.salstar.sk/pub/yum/keys/RPM-GPG-KEY-Fedora-Pre-Extras<br />
</syntaxhighlight><br />
<br />
==== Clean yum cache ====<br />
<syntaxhighlight lang="Bash"><br />
yum --enablerepo=* clean all<br />
</syntaxhighlight><br />
<br />
<br />
==== Install e-smith and smeserver packages ====<br />
Now, you should be ready to install all the e-smith and smeserver packages (and their dependencies), plus the rest of the rpms that aren't required by a smeserver- or e-smith- rpm, but were installed on SME8 [[bugzilla:7311]]. This should pull about 501 packages to install, and 14 to update, and then you can do 'yum upgrade' to upgrade the remaining CentOS packages. Some other notes on this in [[bugzilla:7240]]<br />
<pre style="white-space:normal;"> <br />
yum --disablerepo=* --enablerepo=smeupdates9,smeupdates-testing9,smeos8,smeupdates8 install e-smith\* smeserver\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync<br />
<br />
yum upgrade<br />
</pre><br />
<br />
See the following bugs:<br />
*[[bugzilla:7233|Bug #7233: e-smith-ldap should require openldap-servers]]<br />
*[[bugzilla:7252|Bug #7252: e-smith-radiusd should require freeradius-ldap]]<br />
*[[bugzilla:7234|Bug #7234: e-smith-apache should require mod_ssl]]<br />
*[[bugzilla:7297|Bug #7297: e-smith-hosts should require dhcp]]<br />
<br />
==== Move everything from rc7.d to rc4.d ====<br />
All the links in rc4.d should then point to e-smith-service<br />
<syntaxhighlight lang="Bash"><br />
rm -f /etc/rc4.d/*<br />
cp -a /etc/rc7.d/* /etc/rc4.d/<br />
</syntaxhighlight><br />
<br />
==== Move some perl modules ====<br />
We need to copy some perl modules to a new directory, because @INC has changed in EL6: [[bugzilla:7223]]<br />
<syntaxhighlight lang="Bash"><br />
cp -a /usr/lib/perl5/site_perl/esmith/* /usr/share/perl5/vendor_perl/esmith<br />
</syntaxhighlight><br />
<br />
==== Create a service entry for rsyslog ====<br />
We need to create a new service entry in the DB, because the standard syslog package is now rsyslog:<br />
* See [[bugzilla:7221|Bug #7221: Change from syslog to rsyslog]] and [[bugzilla:7322|Bug #7322: Change from syslog to rsyslog - Add link]] This step can be removed when e-smith-base-5.4.0-8 is available.<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/db configuration set rsyslog service status enabled<br />
cp -a /etc/rc7.d/S05syslog /etc/rc4.d/S05rsyslog<br />
</syntaxhighlight><br />
<br />
==== Run post-upgrade ====<br />
We can now try to post-upgrade<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</syntaxhighlight><br />
<br />
==== The system boots but completly broken :-) ====<br />
Ok, so the system should now boot, but is really not usable, after a quick look, at least the following doesn't work as expected:<br />
<br />
* The console on the first boot don't really work. It asks for the admin password <strike>(and BTW the password appears in cleartext)</strike> but it's all<br />
* <strike>No network interfaces are detected by the console menu (because kudzu is not installed, only available in SME repo, and require an older python which conflicts with the the one * from EL6)</strike><br />
* slapd won't start<br />
* httpd won't start<br />
* squid won't start<br />
* manually running expand-template has no effect (and no error message is printed). But signal-event seems to work (files get expanded and services restarted)<br />
* as the network interface are not configured, all the services which requires the internel IP (or the external one) in their config (at least sshd squid and dnscache) won't start<br />
* <strike>qpsmtpd won't start (can't locate Qpsmtpd/TcpServer.pm in @INC)</strike><br />
* There's probably a lot more which is not working<br />
<br />
<br />
* wellsi: Is there an easy way to get SSH access to it at this point?<br />
<br />
== SME Server specific/required packages ==<br />
To get a list of all specific SME Server packages you can run:<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa | grep 'smeserver\|e-smith'| sed -e 's/-[0-9].*//' | sort > smeserver-packages.txt<br />
</syntaxhighlight><br />
<br />
<br />
== SME Server specific/required perl packages ==<br />
To get a list of the file names ''containing'' the string 'perl' on a running SME8 server.<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa | grep perl | sed -e 's/-[0-9].*//' | sort<br />
</syntaxhighlight><br />
<br />
or, as per suggestion on the lists (All files ''starting'' with the string 'perl')<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa --qf '%{NAME}\n' name=perl\* | sort<br />
</syntaxhighlight><br />
<br />
To export the list to a plain text file you could do:<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa | grep perl | sed -e 's/-[0-9].*//' | sort > perl-list.txt<br />
</syntaxhighlight><br />
<br />
<br />
perl-Digest-SHA Y<br />
perl Y<br />
perl-Archive-Tar Y<br />
perl-Authen-PAM ******<br />
perl-Authen-SASL Y<br />
perl-BSD-Resource ******<br />
perl-CGI-FormMagick ******<br />
perl-CGI-Persistent ******<br />
perl-Class-ParamParser ******<br />
perl-Clone Y<br />
perl-Compress-Raw-Bzip2 Y<br />
perl-Compress-Raw-Zlib Y<br />
perl-Compress-Zlib Y<br />
perl-Convert-ASN1 Y<br />
perl-Convert-BinHex Y<br />
perl-Convert-TNEF ******<br />
perl-Crypt-Cracklib ******<br />
perl-Crypt-OpenSSL-Bignum Y<br />
perl-Crypt-OpenSSL-Random Y<br />
perl-Crypt-OpenSSL-RSA Y<br />
perl-DateManip Y<br />
perl-DBD-MySQL Y<br />
perl-DBI Y<br />
perl-Digest-HMAC Y<br />
perl-Digest-SHA1 Y<br />
perl-Email-Date-Format Y<br />
perl-Encode-Detect Y<br />
perl-Error Y<br />
perl-File-MMagic ******<br />
perl-Geography-Countries ******<br />
perl-HTML-Parser Y<br />
perl-HTML-Tabulate ******<br />
perl-HTML-Tagset Y<br />
perl-I18N-AcceptLanguage ******<br />
perl-IO-Compress-Base Y<br />
perl-IO-Compress-Bzip2 Y<br />
perl-IO-Compress-Zlib Y<br />
perl-IO-Socket-INET6 Y<br />
perl-IO-Socket-SSL Y<br />
perl-IO-stringy Y<br />
perl-IO-Zlib Y<br />
perl-IP-Country ******<br />
perl-LDAP Y<br />
perl-libwww-perl Y<br />
perl-Locale-gettext ******<br />
perl-Mail-DKIM Y<br />
perl-Mail-RFC822-Address ******<br />
perl-Mail-SPF ******<br />
perl-MailTools Y<br />
perl-MIME-Lite Y<br />
perl-MIME-tools Y<br />
perl-Net-DNS Y<br />
perl-Net-Ident ******<br />
perl-Net-IP Y<br />
perl-Net-IPv4Addr ******<br />
perl-Net-SMTP-SSL Y<br />
perl-Net-SSLeay Y<br />
perl-NetAddr-IP Y<br />
perl-Object-Persistence ******<br />
perl-Package-Constants Y<br />
perl-Quota ******<br />
perl-Razor-Agent ******<br />
perl-RPM2 ******<br />
perl-Socket6 Y<br />
perl-suidperl Y<br />
perl-Test-Inline ******<br />
perl-Text-Iconv Y<br />
perl-Text-Template ******<br />
perl-Time-TAI64 ******<br />
perl-TimeDate Y<br />
perl-Unix-ConfigFile ******<br />
perl-URI Y<br />
perl-version Y<br />
perl-WWW-Automate ******<br />
perl-XML-NamespaceSupport Y<br />
perl-XML-Parser Y<br />
perl-XML-SAX Y<br />
<br />
<br />
I am now going to try and lob in the existing/missing el5 versions to see what happens. My guess is we will need to rebuild the required modules.<br />
<br />
<br />
== FormMagick ==<br />
Next will be an attack on FormMagick - there is no package in the default install so need to figure that out. In may indeed be horrible, but we can live with it for now.<br />
<br />
Hopefully with perl and FormMagick installed, most of the SME stuff *should* basically install.<br />
<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
<br />
==== Kickstart file ====<br />
* A starting point can be found on the [[SME9_Kickstart| SME9 Kickstart]] page.<br />
<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_on_CentOS_6&diff=18340SME on CentOS 62013-02-08T20:41:03Z<p>Gregswallow: /* Move some perl modules */</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9, based on CentOS 6 ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
<br />
=== Prerequisites ===<br />
* VIrtual machine (Vmware, Parallels or Virtualbox)<br />
* Centos Minimal 64-bit architecture. 32-bit may follow later<br />
* [[Setting_up_RPM_Building_for_SME_Server|Setting up a RPM Building environment]]<br />
<br />
=== User Feedback ===<br />
Unstructured user feedback can be noted here: [[SME9DEV_user_feedback|SME9DEV user feedback]]. Issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
<br />
=== Bugs ===<br />
[http://bugs.contribs.org/bugs/buglist.cgi?product=SME%20Server%209.X&component=Cleanup&resolution=--- Bug Tracker] <br />
[http://wiki.contribs.org/SME9BuildQueue#SME_9_Error_list_and_affected_packages SME 9 error list]<br />
<br />
=== Considerations ===<br />
* Primary and only goal for now is the transition of SME Server based on CentOS 5.8 to SME Server based on CentOS6.3<br />
* SysVinit is no longer the default with the release of RHEL6, beyond RHEL6 systemd will be used<br />
* perl has a new location of the filesystem. New: /usr/share/perl5/vendor_perl instead Old: /usr/lib/perl5/site_perl/<br />
* perl version 5.8.8 is the new default version on RHEL6. This requires a review of all the perl module rpms which are specific for perl 5.8.5<br />
<br />
== Installing CentOS 6 minimal ==<br />
First a few notes on CentOS 6 minimal, which is a bare bones install with very little on board. You can download a copy from one of the CentOS mirrors [http://www.centos.org/modules/tinycontent/index.php?id=30 here]<br />
<br />
* As per above note, only use Virtual Machine for testing purposes. A good free VM package can be obtained [https://www.virtualbox.org/wiki/Downloads here]<br />
* You might want to note down as much as possible so you yourself and others can reproduce the actions<br />
* Don't use yum with the '-y' flag (install/upgrade without further user interaction) when using the yum install/upgrade commands. (beware copy/paste yum commands)<br />
* you might want to note down all packages listed by yum to be installed/upgraded AND their dependencies<br />
* Make regular snapshots of your Virtual Machine and describe them specifically. At least when you've reached an important milestone for yourself<br />
<br />
<br />
==== Installing the ISO ====<br />
* Just install a minimal el6 installation (I just installed a few utilities like htop, screen, rsync, vim, openssh-clients mc etc…). You can use either the DVD, the minimal CD install, a net install with PXE, it's up to you<br />
* wellsi: I have used CentOS-6.3-x86_64-minimal.iso<br />
<br />
<br />
==== Enable networking ====<br />
Each boot you have to start the network etc etc. I decided it was better with the minimal install and touch as little as possible - if I could then get SME packages installed I could then use that to configure networking later.<br />
<br />
To start the networking <br />
<syntaxhighlight lang="Bash"><br />
./etc/sysconfig/network-scripts/ifup-eth eth0<br />
</syntaxhighlight><br />
<br />
or <br />
<syntaxhighlight lang="Bash"><br />
dhclient eth0<br />
</syntaxhighlight><br />
<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="Collapse" data-expandtext="More on networking"><br />
or if you want to assign a specific IP address (e.g. 192.168.1.2).<br />
<syntaxhighlight lang="Bash"><br />
ifconfig eth0 192.168.1.2<br />
echo "nameserver 192.168.1.254" >> /etc/resolv.conf<br />
route add default gw 192.168.1.254 eth0<br />
</syntaxhighlight> <br />
<br />
To make your changes permanent you will need to edit the configuration file to make it active on boot. There is only the vi text editor, you can also install nano. <br />
<syntaxhighlight lang="Bash"><br />
yum install nano<br />
nano /etc/sysconfig/network-scripts/ifcfg-eth0<br />
</syntaxhighlight><br />
and set ONBOOT=”YES”<br />
</div><br />
<br />
==== Enable SSH ====<br />
SSH is present but is disabled at this stage. To enable ssh issue:<br />
<syntaxhighlight lang="Bash"><br />
service sshd start<br />
</syntaxhighlight><br />
<br />
<br />
==== Disable SELinux ====<br />
It will be easier to see what's going on (and turn off selinux at kernel level, just to be sure)<br />
<syntaxhighlight lang="Bash"><br />
sed -i -e 's/rhgb quiet/selinux=0/g' /boot/grub/grub.conf<br />
sed -i -e 's/SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config<br />
</syntaxhighlight><br />
<br />
<br />
==== Remove selinux-policy-targeted ====<br />
They conflict with some e-smith/smeserver packages<br />
<syntaxhighlight lang="Bash"><br />
yum remove selinux-policy-targeted<br />
</syntaxhighlight><br />
<br />
==reboot==<br />
I think a reboot is in order here, to boot with selinux disabled. That is what i did anyways....Greg<br />
<br />
== Configure basic requirements ==<br />
==== Configure SME9 repositories ====<br />
<br />
See the following bugs tracking issues with repositories:<br />
* [[bugzilla:7294|Bug #7294: rpms that still need to be rebuilt or sourced for the SME9 repositories]]<br />
* [[bugzilla:7298|Bug #7298: Import perl-Unix-ConfigFile from rpmforge]]<br />
* [[bugzilla:7292|Bug #7292: more rpms in the SME8 repositories that have a lower version in our SME9 repositories]]<br />
* [[bugzilla:7305|Bug #7305: smeserver-yum doesn't provide the /etc/yum.smerepos.d dir]]<br />
<br />
<syntaxhighlight lang="Bash"><br />
yum install wget<br />
</syntaxhighlight><br />
<syntaxhighlight lang="Bash"><br />
mkdir /tmp/repo.bak<br />
mv /etc/yum.repos.d/*.repo /tmp/repo.bak/<br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3650<br />
</syntaxhighlight><br />
<br />
==== Import needed GPG Keys ====<br />
<syntaxhighlight lang="Bash"><br />
rpm --import http://sme-mirror.firewall-services.com/releases/8/smeos/x86_64/RPM-GPG-KEY-SMEServer<br />
rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt<br />
rpm --import https://fedoraproject.org/static/217521F6.txt<br />
rpm --import http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br />
rpm --import http://www.salstar.sk/pub/yum/keys/RPM-GPG-KEY-Fedora-Pre-Extras<br />
</syntaxhighlight><br />
<br />
==== Clean yum cache ====<br />
<syntaxhighlight lang="Bash"><br />
yum --enablerepo=* clean all<br />
</syntaxhighlight><br />
<br />
<br />
==== Install e-smith and smeserver packages ====<br />
Now, you should be ready to install all the e-smith and smeserver packages (and their dependencies), plus the rest of the rpms that aren't required by a smeserver- or e-smith- rpm, but were installed on SME8 [[bugzilla:7311]]. This should pull about 501 packages to install, and 14 to update<br />
<pre style="white-space:normal;"> <br />
yum --disablerepo=* --enablerepo=smeupdates9,smeupdates-testing9,smeos8,smeupdates8 install e-smith\* smeserver\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync<br />
</pre><br />
<br />
See the following bugs:<br />
*[[bugzilla:7233|Bug #7233: e-smith-ldap should require openldap-servers]]<br />
*[[bugzilla:7252|Bug #7252: e-smith-radiusd should require freeradius-ldap]]<br />
*[[bugzilla:7234|Bug #7234: e-smith-apache should require mod_ssl]]<br />
*[[bugzilla:7297|Bug #7297: e-smith-hosts should require dhcp]]<br />
<br />
==== Move everything from rc7.d to rc4.d ====<br />
All the links in rc4.d should then point to e-smith-service<br />
<syntaxhighlight lang="Bash"><br />
rm -f /etc/rc4.d/*<br />
cp -a /etc/rc7.d/* /etc/rc4.d/<br />
</syntaxhighlight><br />
<br />
==== Move some perl modules ====<br />
We need to copy some perl modules to a new directory, because @INC has changed in EL6: [[bugzilla:7223]]<br />
<syntaxhighlight lang="Bash"><br />
cp -a /usr/lib/perl5/site_perl/esmith/* /usr/share/perl5/vendor_perl/esmith<br />
</syntaxhighlight><br />
<br />
==== Create a service entry for rsyslog ====<br />
We need to create a new service entry in the DB, because the standard syslog package is now rsyslog:<br />
* See [[bugzilla:7221|Bug #7221: Change from syslog to rsyslog]] and [[bugzilla:7322|Bug #7322: Change from syslog to rsyslog - Add link]] This step can be removed when e-smith-base-5.4.0-8 is available.<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/db configuration set rsyslog service status enabled<br />
cp -a /etc/rc7.d/S05syslog /etc/rc4.d/S05rsyslog<br />
</syntaxhighlight><br />
<br />
==== Run post-upgrade ====<br />
We can now try to post-upgrade<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</syntaxhighlight><br />
<br />
==== The system boots but completly broken :-) ====<br />
Ok, so the system should now boot, but is really not usable, after a quick look, at least the following doesn't work as expected:<br />
<br />
* The console on the first boot don't really work. It asks for the admin password <strike>(and BTW the password appears in cleartext)</strike> but it's all<br />
* <strike>No network interfaces are detected by the console menu (because kudzu is not installed, only available in SME repo, and require an older python which conflicts with the the one * from EL6)</strike><br />
* slapd won't start<br />
* httpd won't start<br />
* squid won't start<br />
* manually running expand-template has no effect (and no error message is printed). But signal-event seems to work (files get expanded and services restarted)<br />
* as the network interface are not configured, all the services which requires the internel IP (or the external one) in their config (at least sshd squid and dnscache) won't start<br />
* <strike>qpsmtpd won't start (can't locate Qpsmtpd/TcpServer.pm in @INC)</strike><br />
* There's probably a lot more which is not working<br />
<br />
<br />
* wellsi: Is there an easy way to get SSH access to it at this point?<br />
<br />
== SME Server specific/required packages ==<br />
To get a list of all specific SME Server packages you can run:<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa | grep 'smeserver\|e-smith'| sed -e 's/-[0-9].*//' | sort > smeserver-packages.txt<br />
</syntaxhighlight><br />
<br />
<br />
== SME Server specific/required perl packages ==<br />
To get a list of the file names ''containing'' the string 'perl' on a running SME8 server.<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa | grep perl | sed -e 's/-[0-9].*//' | sort<br />
</syntaxhighlight><br />
<br />
or, as per suggestion on the lists (All files ''starting'' with the string 'perl')<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa --qf '%{NAME}\n' name=perl\* | sort<br />
</syntaxhighlight><br />
<br />
To export the list to a plain text file you could do:<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa | grep perl | sed -e 's/-[0-9].*//' | sort > perl-list.txt<br />
</syntaxhighlight><br />
<br />
<br />
perl-Digest-SHA Y<br />
perl Y<br />
perl-Archive-Tar Y<br />
perl-Authen-PAM ******<br />
perl-Authen-SASL Y<br />
perl-BSD-Resource ******<br />
perl-CGI-FormMagick ******<br />
perl-CGI-Persistent ******<br />
perl-Class-ParamParser ******<br />
perl-Clone Y<br />
perl-Compress-Raw-Bzip2 Y<br />
perl-Compress-Raw-Zlib Y<br />
perl-Compress-Zlib Y<br />
perl-Convert-ASN1 Y<br />
perl-Convert-BinHex Y<br />
perl-Convert-TNEF ******<br />
perl-Crypt-Cracklib ******<br />
perl-Crypt-OpenSSL-Bignum Y<br />
perl-Crypt-OpenSSL-Random Y<br />
perl-Crypt-OpenSSL-RSA Y<br />
perl-DateManip Y<br />
perl-DBD-MySQL Y<br />
perl-DBI Y<br />
perl-Digest-HMAC Y<br />
perl-Digest-SHA1 Y<br />
perl-Email-Date-Format Y<br />
perl-Encode-Detect Y<br />
perl-Error Y<br />
perl-File-MMagic ******<br />
perl-Geography-Countries ******<br />
perl-HTML-Parser Y<br />
perl-HTML-Tabulate ******<br />
perl-HTML-Tagset Y<br />
perl-I18N-AcceptLanguage ******<br />
perl-IO-Compress-Base Y<br />
perl-IO-Compress-Bzip2 Y<br />
perl-IO-Compress-Zlib Y<br />
perl-IO-Socket-INET6 Y<br />
perl-IO-Socket-SSL Y<br />
perl-IO-stringy Y<br />
perl-IO-Zlib Y<br />
perl-IP-Country ******<br />
perl-LDAP Y<br />
perl-libwww-perl Y<br />
perl-Locale-gettext ******<br />
perl-Mail-DKIM Y<br />
perl-Mail-RFC822-Address ******<br />
perl-Mail-SPF ******<br />
perl-MailTools Y<br />
perl-MIME-Lite Y<br />
perl-MIME-tools Y<br />
perl-Net-DNS Y<br />
perl-Net-Ident ******<br />
perl-Net-IP Y<br />
perl-Net-IPv4Addr ******<br />
perl-Net-SMTP-SSL Y<br />
perl-Net-SSLeay Y<br />
perl-NetAddr-IP Y<br />
perl-Object-Persistence ******<br />
perl-Package-Constants Y<br />
perl-Quota ******<br />
perl-Razor-Agent ******<br />
perl-RPM2 ******<br />
perl-Socket6 Y<br />
perl-suidperl Y<br />
perl-Test-Inline ******<br />
perl-Text-Iconv Y<br />
perl-Text-Template ******<br />
perl-Time-TAI64 ******<br />
perl-TimeDate Y<br />
perl-Unix-ConfigFile ******<br />
perl-URI Y<br />
perl-version Y<br />
perl-WWW-Automate ******<br />
perl-XML-NamespaceSupport Y<br />
perl-XML-Parser Y<br />
perl-XML-SAX Y<br />
<br />
<br />
I am now going to try and lob in the existing/missing el5 versions to see what happens. My guess is we will need to rebuild the required modules.<br />
<br />
<br />
== FormMagick ==<br />
Next will be an attack on FormMagick - there is no package in the default install so need to figure that out. In may indeed be horrible, but we can live with it for now.<br />
<br />
Hopefully with perl and FormMagick installed, most of the SME stuff *should* basically install.<br />
<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
<br />
==== Kickstart file ====<br />
* A starting point can be found on the [[SME9_Kickstart| SME9 Kickstart]] page.<br />
<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallowhttps://wiki.koozali.org/index.php?title=SME_on_CentOS_6&diff=18339SME on CentOS 62013-02-08T20:38:59Z<p>Gregswallow: /* Install e-smith and smeserver packages */</p>
<hr />
<div>{{Tip box|Please only use a virtual machine to test this.Try to follow what others have done and repeat it. Make any notes yourself and post your findings.}}<br />
<br />
Back to [[SME_Server_9.0_Development|SME Server 9.0 Development]]<br />
<br />
__TOC__<br />
== SME 9, based on CentOS 6 ==<br />
An overview of related SME9 development pages can be found [[:Category:SME9-Development|here]].<br />
<br />
<br />
=== Prerequisites ===<br />
* VIrtual machine (Vmware, Parallels or Virtualbox)<br />
* Centos Minimal 64-bit architecture. 32-bit may follow later<br />
* [[Setting_up_RPM_Building_for_SME_Server|Setting up a RPM Building environment]]<br />
<br />
=== User Feedback ===<br />
Unstructured user feedback can be noted here: [[SME9DEV_user_feedback|SME9DEV user feedback]]. Issues that require developers attention should be logged in our Bug Tracker. (See below)<br />
<br />
<br />
=== Bugs ===<br />
[http://bugs.contribs.org/bugs/buglist.cgi?product=SME%20Server%209.X&component=Cleanup&resolution=--- Bug Tracker] <br />
[http://wiki.contribs.org/SME9BuildQueue#SME_9_Error_list_and_affected_packages SME 9 error list]<br />
<br />
=== Considerations ===<br />
* Primary and only goal for now is the transition of SME Server based on CentOS 5.8 to SME Server based on CentOS6.3<br />
* SysVinit is no longer the default with the release of RHEL6, beyond RHEL6 systemd will be used<br />
* perl has a new location of the filesystem. New: /usr/share/perl5/vendor_perl instead Old: /usr/lib/perl5/site_perl/<br />
* perl version 5.8.8 is the new default version on RHEL6. This requires a review of all the perl module rpms which are specific for perl 5.8.5<br />
<br />
== Installing CentOS 6 minimal ==<br />
First a few notes on CentOS 6 minimal, which is a bare bones install with very little on board. You can download a copy from one of the CentOS mirrors [http://www.centos.org/modules/tinycontent/index.php?id=30 here]<br />
<br />
* As per above note, only use Virtual Machine for testing purposes. A good free VM package can be obtained [https://www.virtualbox.org/wiki/Downloads here]<br />
* You might want to note down as much as possible so you yourself and others can reproduce the actions<br />
* Don't use yum with the '-y' flag (install/upgrade without further user interaction) when using the yum install/upgrade commands. (beware copy/paste yum commands)<br />
* you might want to note down all packages listed by yum to be installed/upgraded AND their dependencies<br />
* Make regular snapshots of your Virtual Machine and describe them specifically. At least when you've reached an important milestone for yourself<br />
<br />
<br />
==== Installing the ISO ====<br />
* Just install a minimal el6 installation (I just installed a few utilities like htop, screen, rsync, vim, openssh-clients mc etc…). You can use either the DVD, the minimal CD install, a net install with PXE, it's up to you<br />
* wellsi: I have used CentOS-6.3-x86_64-minimal.iso<br />
<br />
<br />
==== Enable networking ====<br />
Each boot you have to start the network etc etc. I decided it was better with the minimal install and touch as little as possible - if I could then get SME packages installed I could then use that to configure networking later.<br />
<br />
To start the networking <br />
<syntaxhighlight lang="Bash"><br />
./etc/sysconfig/network-scripts/ifup-eth eth0<br />
</syntaxhighlight><br />
<br />
or <br />
<syntaxhighlight lang="Bash"><br />
dhclient eth0<br />
</syntaxhighlight><br />
<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="Collapse" data-expandtext="More on networking"><br />
or if you want to assign a specific IP address (e.g. 192.168.1.2).<br />
<syntaxhighlight lang="Bash"><br />
ifconfig eth0 192.168.1.2<br />
echo "nameserver 192.168.1.254" >> /etc/resolv.conf<br />
route add default gw 192.168.1.254 eth0<br />
</syntaxhighlight> <br />
<br />
To make your changes permanent you will need to edit the configuration file to make it active on boot. There is only the vi text editor, you can also install nano. <br />
<syntaxhighlight lang="Bash"><br />
yum install nano<br />
nano /etc/sysconfig/network-scripts/ifcfg-eth0<br />
</syntaxhighlight><br />
and set ONBOOT=”YES”<br />
</div><br />
<br />
==== Enable SSH ====<br />
SSH is present but is disabled at this stage. To enable ssh issue:<br />
<syntaxhighlight lang="Bash"><br />
service sshd start<br />
</syntaxhighlight><br />
<br />
<br />
==== Disable SELinux ====<br />
It will be easier to see what's going on (and turn off selinux at kernel level, just to be sure)<br />
<syntaxhighlight lang="Bash"><br />
sed -i -e 's/rhgb quiet/selinux=0/g' /boot/grub/grub.conf<br />
sed -i -e 's/SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config<br />
</syntaxhighlight><br />
<br />
<br />
==== Remove selinux-policy-targeted ====<br />
They conflict with some e-smith/smeserver packages<br />
<syntaxhighlight lang="Bash"><br />
yum remove selinux-policy-targeted<br />
</syntaxhighlight><br />
<br />
==reboot==<br />
I think a reboot is in order here, to boot with selinux disabled. That is what i did anyways....Greg<br />
<br />
== Configure basic requirements ==<br />
==== Configure SME9 repositories ====<br />
<br />
See the following bugs tracking issues with repositories:<br />
* [[bugzilla:7294|Bug #7294: rpms that still need to be rebuilt or sourced for the SME9 repositories]]<br />
* [[bugzilla:7298|Bug #7298: Import perl-Unix-ConfigFile from rpmforge]]<br />
* [[bugzilla:7292|Bug #7292: more rpms in the SME8 repositories that have a lower version in our SME9 repositories]]<br />
* [[bugzilla:7305|Bug #7305: smeserver-yum doesn't provide the /etc/yum.smerepos.d dir]]<br />
<br />
<syntaxhighlight lang="Bash"><br />
yum install wget<br />
</syntaxhighlight><br />
<syntaxhighlight lang="Bash"><br />
mkdir /tmp/repo.bak<br />
mv /etc/yum.repos.d/*.repo /tmp/repo.bak/<br />
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3650<br />
</syntaxhighlight><br />
<br />
==== Import needed GPG Keys ====<br />
<syntaxhighlight lang="Bash"><br />
rpm --import http://sme-mirror.firewall-services.com/releases/8/smeos/x86_64/RPM-GPG-KEY-SMEServer<br />
rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt<br />
rpm --import https://fedoraproject.org/static/217521F6.txt<br />
rpm --import http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br />
rpm --import http://www.salstar.sk/pub/yum/keys/RPM-GPG-KEY-Fedora-Pre-Extras<br />
</syntaxhighlight><br />
<br />
==== Clean yum cache ====<br />
<syntaxhighlight lang="Bash"><br />
yum --enablerepo=* clean all<br />
</syntaxhighlight><br />
<br />
<br />
==== Install e-smith and smeserver packages ====<br />
Now, you should be ready to install all the e-smith and smeserver packages (and their dependencies), plus the rest of the rpms that aren't required by a smeserver- or e-smith- rpm, but were installed on SME8 [[bugzilla:7311]]. This should pull about 501 packages to install, and 14 to update<br />
<pre style="white-space:normal;"> <br />
yum --disablerepo=* --enablerepo=smeupdates9,smeupdates-testing9,smeos8,smeupdates8 install e-smith\* smeserver\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync<br />
</pre><br />
<br />
See the following bugs:<br />
*[[bugzilla:7233|Bug #7233: e-smith-ldap should require openldap-servers]]<br />
*[[bugzilla:7252|Bug #7252: e-smith-radiusd should require freeradius-ldap]]<br />
*[[bugzilla:7234|Bug #7234: e-smith-apache should require mod_ssl]]<br />
*[[bugzilla:7297|Bug #7297: e-smith-hosts should require dhcp]]<br />
<br />
==== Move everything from rc7.d to rc4.d ====<br />
All the links in rc4.d should then point to e-smith-service<br />
<syntaxhighlight lang="Bash"><br />
rm -f /etc/rc4.d/*<br />
cp -a /etc/rc7.d/* /etc/rc4.d/<br />
</syntaxhighlight><br />
<br />
==== Move some perl modules ====<br />
We need to copy some perl modules to a new directory, because @INC has changed in EL6:<br />
<syntaxhighlight lang="Bash"><br />
cp -a /usr/lib/perl5/site_perl/esmith/* /usr/share/perl5/vendor_perl/esmith<br />
</syntaxhighlight><br />
<br />
==== Create a service entry for rsyslog ====<br />
We need to create a new service entry in the DB, because the standard syslog package is now rsyslog:<br />
* See [[bugzilla:7221|Bug #7221: Change from syslog to rsyslog]] and [[bugzilla:7322|Bug #7322: Change from syslog to rsyslog - Add link]] This step can be removed when e-smith-base-5.4.0-8 is available.<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/db configuration set rsyslog service status enabled<br />
cp -a /etc/rc7.d/S05syslog /etc/rc4.d/S05rsyslog<br />
</syntaxhighlight><br />
<br />
==== Run post-upgrade ====<br />
We can now try to post-upgrade<br />
<syntaxhighlight lang="Bash"><br />
/sbin/e-smith/signal-event post-upgrade<br />
/sbin/e-smith/signal-event reboot<br />
</syntaxhighlight><br />
<br />
==== The system boots but completly broken :-) ====<br />
Ok, so the system should now boot, but is really not usable, after a quick look, at least the following doesn't work as expected:<br />
<br />
* The console on the first boot don't really work. It asks for the admin password <strike>(and BTW the password appears in cleartext)</strike> but it's all<br />
* <strike>No network interfaces are detected by the console menu (because kudzu is not installed, only available in SME repo, and require an older python which conflicts with the the one * from EL6)</strike><br />
* slapd won't start<br />
* httpd won't start<br />
* squid won't start<br />
* manually running expand-template has no effect (and no error message is printed). But signal-event seems to work (files get expanded and services restarted)<br />
* as the network interface are not configured, all the services which requires the internel IP (or the external one) in their config (at least sshd squid and dnscache) won't start<br />
* <strike>qpsmtpd won't start (can't locate Qpsmtpd/TcpServer.pm in @INC)</strike><br />
* There's probably a lot more which is not working<br />
<br />
<br />
* wellsi: Is there an easy way to get SSH access to it at this point?<br />
<br />
== SME Server specific/required packages ==<br />
To get a list of all specific SME Server packages you can run:<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa | grep 'smeserver\|e-smith'| sed -e 's/-[0-9].*//' | sort > smeserver-packages.txt<br />
</syntaxhighlight><br />
<br />
<br />
== SME Server specific/required perl packages ==<br />
To get a list of the file names ''containing'' the string 'perl' on a running SME8 server.<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa | grep perl | sed -e 's/-[0-9].*//' | sort<br />
</syntaxhighlight><br />
<br />
or, as per suggestion on the lists (All files ''starting'' with the string 'perl')<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa --qf '%{NAME}\n' name=perl\* | sort<br />
</syntaxhighlight><br />
<br />
To export the list to a plain text file you could do:<br />
<syntaxhighlight lang="Bash"><br />
rpm -qa | grep perl | sed -e 's/-[0-9].*//' | sort > perl-list.txt<br />
</syntaxhighlight><br />
<br />
<br />
perl-Digest-SHA Y<br />
perl Y<br />
perl-Archive-Tar Y<br />
perl-Authen-PAM ******<br />
perl-Authen-SASL Y<br />
perl-BSD-Resource ******<br />
perl-CGI-FormMagick ******<br />
perl-CGI-Persistent ******<br />
perl-Class-ParamParser ******<br />
perl-Clone Y<br />
perl-Compress-Raw-Bzip2 Y<br />
perl-Compress-Raw-Zlib Y<br />
perl-Compress-Zlib Y<br />
perl-Convert-ASN1 Y<br />
perl-Convert-BinHex Y<br />
perl-Convert-TNEF ******<br />
perl-Crypt-Cracklib ******<br />
perl-Crypt-OpenSSL-Bignum Y<br />
perl-Crypt-OpenSSL-Random Y<br />
perl-Crypt-OpenSSL-RSA Y<br />
perl-DateManip Y<br />
perl-DBD-MySQL Y<br />
perl-DBI Y<br />
perl-Digest-HMAC Y<br />
perl-Digest-SHA1 Y<br />
perl-Email-Date-Format Y<br />
perl-Encode-Detect Y<br />
perl-Error Y<br />
perl-File-MMagic ******<br />
perl-Geography-Countries ******<br />
perl-HTML-Parser Y<br />
perl-HTML-Tabulate ******<br />
perl-HTML-Tagset Y<br />
perl-I18N-AcceptLanguage ******<br />
perl-IO-Compress-Base Y<br />
perl-IO-Compress-Bzip2 Y<br />
perl-IO-Compress-Zlib Y<br />
perl-IO-Socket-INET6 Y<br />
perl-IO-Socket-SSL Y<br />
perl-IO-stringy Y<br />
perl-IO-Zlib Y<br />
perl-IP-Country ******<br />
perl-LDAP Y<br />
perl-libwww-perl Y<br />
perl-Locale-gettext ******<br />
perl-Mail-DKIM Y<br />
perl-Mail-RFC822-Address ******<br />
perl-Mail-SPF ******<br />
perl-MailTools Y<br />
perl-MIME-Lite Y<br />
perl-MIME-tools Y<br />
perl-Net-DNS Y<br />
perl-Net-Ident ******<br />
perl-Net-IP Y<br />
perl-Net-IPv4Addr ******<br />
perl-Net-SMTP-SSL Y<br />
perl-Net-SSLeay Y<br />
perl-NetAddr-IP Y<br />
perl-Object-Persistence ******<br />
perl-Package-Constants Y<br />
perl-Quota ******<br />
perl-Razor-Agent ******<br />
perl-RPM2 ******<br />
perl-Socket6 Y<br />
perl-suidperl Y<br />
perl-Test-Inline ******<br />
perl-Text-Iconv Y<br />
perl-Text-Template ******<br />
perl-Time-TAI64 ******<br />
perl-TimeDate Y<br />
perl-Unix-ConfigFile ******<br />
perl-URI Y<br />
perl-version Y<br />
perl-WWW-Automate ******<br />
perl-XML-NamespaceSupport Y<br />
perl-XML-Parser Y<br />
perl-XML-SAX Y<br />
<br />
<br />
I am now going to try and lob in the existing/missing el5 versions to see what happens. My guess is we will need to rebuild the required modules.<br />
<br />
<br />
== FormMagick ==<br />
Next will be an attack on FormMagick - there is no package in the default install so need to figure that out. In may indeed be horrible, but we can live with it for now.<br />
<br />
Hopefully with perl and FormMagick installed, most of the SME stuff *should* basically install.<br />
<br />
<br />
== Discussion, help and share ==<br />
* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"<br />
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)<br />
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.<br />
<br />
<br />
== Resources and references ==<br />
<br />
<br />
==== Kickstart file ====<br />
* A starting point can be found on the [[SME9_Kickstart| SME9 Kickstart]] page.<br />
<br />
<br />
==== Setting up a RPM Building environment under CentOS ====<br />
* [[Simple_Package_Modification|Simplest way to develop patches to submit]]<br />
* [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]<br />
* [[Package_Modification|Simple Package Modification]]<br />
* [http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment On the CentOS wiki]<br />
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project]<br />
<br />
<br />
<br />
<br />
<br />
<noinclude>[[Category:Howto]][[Category:SME9-Development]]</div>Gregswallow