1,574
edits
Changes
From SME Server
Jump to navigationJump to searchISO Install for Testing
As a general rule just about any hardware will suffice as a Standalone test machines or as a host for a virtual environment.
As a general rule just about any hardware will suffice as a Standalone test machines or as a host for a virtual environment.
== Install ISO for Testing or Bug Verification==
Its simple for those who do this regularly, it can be a bloody mine pit for someone who doesn't 🙂 very easy to kill a test system and no way to get out but wipe and start again, please don't be put off, if nothing else it sure educates you on the blackmagic in koozali/sme
1. Install current iso that is available from the Koozali webssite - [[SME Server:Download|Downloads]]
2. Once installed, use SSH, SSH access must be enabled with the /server-manager, set remote access to allow, from the cli run a # yum update (DO NOT enable any repos) there can be many mb of updates depending on age of iso, on occasion ie very very rarely smeserver-yum may also need updating first, it may be in smeupdates-testing or updates, so a heads up a quick look under the hood can save a world of grief, [http://mirror.canada.pialasse.com/releases/testing/10/ Koozali Repository] eg
# yum update smeserver-yum --enablerepo=smeupdates-testing
3. Make sure to reboot/reconfig
# signal-event post-upgrade; signal-event reboot
4. Best practice is to select a Bug that need verifying, See [[Dashboard|the Dashboard]] in the wiki, update the package with the uopdated rpm listed in the Bug
# yum update e-smith-base --enablerepo=smeupdatestesting (ONLY this)
5. Now for the fly in the ointment - sometimes, rarely, there will be a package in /smetest that fixes a borked update in smeupdates-testing, that situation can arise with any update, these will appear in smeupdates-testing eventually, it is alwways a good idea to check in /smetest for a later version of a package.
6. If you issue the following
# yum update --enablerepo=smeupdates-testing
you will update ALL the packages that have been updated or added and need testing, every new/modified rpm - a danger Will Robinson moment if there ever was one - this not recommended but can be useful to carry out overall testing of the system or Contrib updates/import testing and verification BUT beware you could also kill your test box VM 🙂
Have fun..always learning
== VM Setups ==
== VM Setups ==
