wardmundy
Nerd Uno
- Joined
- Oct 12, 2007
- Messages
- 19,201
- Reaction score
- 5,221
Migrating from CentOS to Scientific Linux
Here's a simple way to convert your PIAF 2.0.6.5 (only!) server powered by CentOS 6.5 to Scientific Linux 6.5. Make yourself 2 scripts that look like this and run them. Takes about an hour. Also works for me using PIAF 2.0.6.4 server but you may have to do this. Haven't tested anything older than that.
WARNINGS: Proceed at your own risk! Test it on a virtual machine first! DO NOT MIGRATE IF YOUR SERVER IS BEING USED COMMERCIALLY.* THE SL LICENSE SAYS YOU CAN'T USE THEIR REPOS IN THIS CASE. ALSO SCHMOOZE MAY BLOCK YOU FROM USING THEIR COMMERCIAL MODULES. I DON'T KNOW WHAT THEIR POSITION IS ON THIS YET!
* Just to be clear. Our position as to GPL2 applicability goes like this. The yum package management system is GPL2 code (see/usr/share/doc/yum-3.2.29) and is an integral part of the collective work whether it's RHEL, CentOS, or Scientific Linux. It's the primary tool for installing, updating, and removing system components. The yum repository and yum.repos.d are integral components of the yum package manager. Under GPL2, there is no "commercial use exception." The only permissible exception is section 8's "geographical distribution limitation." Any component of the collective work that is not an "independent and separate work" cannot be licensed differently than the GPL2collective work as a whole: "You may not impose any further restrictions on the recipients' exercise of the rights granted herein." Since yum is part of the "operating system" and since the yum package management system without a yum repo would be like a day without sunshine, both are subject to the GPL2 license as installed. Stated another way, you can't produce a GPL2 operating system that includes components to keep the operating system current and secure, and then impose a non-commercial usage limitation that would keep the operating system from remaining current and secure when deployed commercially. In our opinion, Scientific Linux may be copied and distributed as a collective work subject to the conditions in sections 2 and 3 of GPL2. This is not legal advice and should not be relied upon to make any momentous or even trivial decision. Consult your own neighborhood attorney for that.
Here's a simple way to convert your PIAF 2.0.6.5 (only!) server powered by CentOS 6.5 to Scientific Linux 6.5. Make yourself 2 scripts that look like this and run them. Takes about an hour. Also works for me using PIAF 2.0.6.4 server but you may have to do this. Haven't tested anything older than that.
WARNINGS: Proceed at your own risk! Test it on a virtual machine first! DO NOT MIGRATE IF YOUR SERVER IS BEING USED COMMERCIALLY.* THE SL LICENSE SAYS YOU CAN'T USE THEIR REPOS IN THIS CASE. ALSO SCHMOOZE MAY BLOCK YOU FROM USING THEIR COMMERCIAL MODULES. I DON'T KNOW WHAT THEIR POSITION IS ON THIS YET!
Code:
rpm -ivh http://ftp.scientificlinux.org/linux/scientific/6x/i386/os/Packages/yum-conf-sl6x-1-2.noarch.rpm
processor=`uname -i`
centos=${processor:1:3}
if [ $centos != 386 ] ; then
rpm -ivh --force http://ftp.scientificlinux.org/linux/scientific/6x/x86_64/os/Packages/sl-release-6.5-1.x86_64.rpm
else
rpm -ivh --force http://ftp.scientificlinux.org/linux/scientific/6x/i386/os/Packages/sl-release-6.5-1.i686.rpm
fi
sed -i 's|centos-release|sl-release|' /etc/yum.conf
sed -i 's|exclude=centos|\#exclude=centos|' /etc/yum.conf
yum -y erase centos-release
yum -y clean all
yum -y distro-sync
yum -y reinstall `rpm -qa --qf "%{NAME} %{VENDOR}\n"|grep CentOS|awk '{print $1}'`
cd /boot/grub
mv splash.xpm.gz /root/splash.xpm.gz.centos
wget http://pbxinaflash.com/splash.xpm.gz
chmod 644 splash.xpm.gz
chattr -i /etc/pbx/.version
echo "3.0.6.5" > /etc/pbx/.version
chattr +i /etc/pbx/.version
reboot
Code:
cd /usr/src/asterisk
./configure
cd /usr/src/dahdi
make all
make install
service dahdi start
reboot
* Just to be clear. Our position as to GPL2 applicability goes like this. The yum package management system is GPL2 code (see/usr/share/doc/yum-3.2.29) and is an integral part of the collective work whether it's RHEL, CentOS, or Scientific Linux. It's the primary tool for installing, updating, and removing system components. The yum repository and yum.repos.d are integral components of the yum package manager. Under GPL2, there is no "commercial use exception." The only permissible exception is section 8's "geographical distribution limitation." Any component of the collective work that is not an "independent and separate work" cannot be licensed differently than the GPL2collective work as a whole: "You may not impose any further restrictions on the recipients' exercise of the rights granted herein." Since yum is part of the "operating system" and since the yum package management system without a yum repo would be like a day without sunshine, both are subject to the GPL2 license as installed. Stated another way, you can't produce a GPL2 operating system that includes components to keep the operating system current and secure, and then impose a non-commercial usage limitation that would keep the operating system from remaining current and secure when deployed commercially. In our opinion, Scientific Linux may be copied and distributed as a collective work subject to the conditions in sections 2 and 3 of GPL2. This is not legal advice and should not be relied upon to make any momentous or even trivial decision. Consult your own neighborhood attorney for that.