OpenVZ Virtuozzo Containers Wiki - User contributions [en]

Talk:Slackware template creation

2006-06-07T09:27:30Z

Scythe: Some formatting in my last reply

== klogd ==
I have added a note that klogd is needed sometimes. --[[User:Kir|Kir]] 15:43, 6 June 2006 (EDT)

== VE IP ==
Actually, since you do not run anything inside the temporary VE (777) which requires an IP address, you can omit the step of setting VE's OSTEMPLATE, an IP address and a hostname. This was done for Debian specifically because you have to run <tt>apt update</tt> and <tt>apt upgrade</tt> commands, which requires network to be working. So you can edit that out to simplify things. I have not done it yet because you might have other reasons to leave it. --[[User:Kir|Kir]] 15:43, 6 June 2006 (EDT)
: I have actually removed these settings from the text, since it looks like they are not needed, and you forgot to run <tt>vzctl set --ipdel</tt> so OS template cache ends up with the IP address which is wrong. So I followed the easy path and instead of adding the procedure of removing VE IP I just removed the adding of it! Also note that setting OSTEMPLATE is actually needed for <tt>vzctl set --ipadd</tt> to work. --[[User:Kir|Kir]] 16:15, 6 June 2006 (EDT)

== Typo + IPtables ==
I corrected a typo.
Also, I forgot to mention that IPtables needs modules from the running kernel in the VE to work, so
before cache creation or after VE creation the /lib/modules should be created with the needed iptables modules. --[[User:Scythe|Scythe]] 22:54, 6 June 2006 (CET)
: There is actually no need for iptables modules to be available inside VE for iptables to work, so you got it wrong. I have reverted your last change. No kernel modules are loaded inside VE at all -- so you do not need modutils as well. Also, can you please specify the summary then you are making a change? Otherwise it's not clear from the history page what have changed. It makes sense to select an option "Prompt me when entering a blank edit summary" in your preferences->editing. --[[User:Kir|Kir]] 05:05, 7 June 2006 (EDT)
:: You are right, I accidentally mixed the openvz.org "official" template cache's root filesystem with my host's own, so I mislooked the /lib/modules directory... I also corrected the typo again (a missing ")" in the "Moving a Sl. installation into a VE" part) which You have included again when reverting my erroneous notice about iptables modules. --[[User:Scythe|Scythe]] 11:26, 7 June 2006 (CET)

Talk:Slackware template creation

2006-06-07T09:26:46Z

Scythe: Reply to Kir

== klogd ==
I have added a note that klogd is needed sometimes. --[[User:Kir|Kir]] 15:43, 6 June 2006 (EDT)

== VE IP ==
Actually, since you do not run anything inside the temporary VE (777) which requires an IP address, you can omit the step of setting VE's OSTEMPLATE, an IP address and a hostname. This was done for Debian specifically because you have to run <tt>apt update</tt> and <tt>apt upgrade</tt> commands, which requires network to be working. So you can edit that out to simplify things. I have not done it yet because you might have other reasons to leave it. --[[User:Kir|Kir]] 15:43, 6 June 2006 (EDT)
: I have actually removed these settings from the text, since it looks like they are not needed, and you forgot to run <tt>vzctl set --ipdel</tt> so OS template cache ends up with the IP address which is wrong. So I followed the easy path and instead of adding the procedure of removing VE IP I just removed the adding of it! Also note that setting OSTEMPLATE is actually needed for <tt>vzctl set --ipadd</tt> to work. --[[User:Kir|Kir]] 16:15, 6 June 2006 (EDT)

== Typo + IPtables ==
I corrected a typo.
Also, I forgot to mention that IPtables needs modules from the running kernel in the VE to work, so
before cache creation or after VE creation the /lib/modules should be created with the needed iptables modules. --[[User:Scythe|Scythe]] 22:54, 6 June 2006 (CET)
: There is actually no need for iptables modules to be available inside VE for iptables to work, so you got it wrong. I have reverted your last change. No kernel modules are loaded inside VE at all -- so you do not need modutils as well. Also, can you please specify the summary then you are making a change? Otherwise it's not clear from the history page what have changed. It makes sense to select an option "Prompt me when entering a blank edit summary" in your preferences->editing. --[[User:Kir|Kir]] 05:05, 7 June 2006 (EDT)
:: You are right, I accidentally mixed the openvz.org "official" template cache's root filesystem with my host's own, so I mislooked the /lib/modules directory...
I also corrected the typo again (a missing ")" in the "Moving a Sl. installation into a VE" part) which You have included again when reverting my erroneous notice about iptables modules. --[[User:Scythe|Scythe]] 11:26, 7 June 2006 (CET)

Slackware template creation

2006-06-07T09:20:33Z

Scythe: Corrected typo: missing ")" in Movings Sl. installation into a VE part

This page is about making a template cache for OpenVZ [[VE]] from Slackware linux.
(This method was used for creating the minimal cache from Slackware 10.2)
The method is basically the same as described in article [[Debian template creation]].

== Getting a Slackware root filesystem ==

=== Downloading and installing Slackware ===

First you need to download Slackware linux from [http://www.slackware.org/getslack/ http://www.slackware.org/getslack/]. Then you have to [http://www.slackware.org/install/ install] it to some hardware you can spare while the cache creation process is going on. For [[VE]] creation it is recommended not to install any unnecessary software into the box you are making the cache from.
This means for a minimal Slackware 10.2 cache I have chosen only series A (<tt>Base Linux System</tt>) at the package series selection screen of Slackware Setup. Then '''expert''' prompting mode on the next screen. On the Series A package selection screen I chose the following packages:

* kernel-ide - This is requied to boot the OS to be able to get it's root filesystem
* aaa_base
* aaa_elflibs
* bash
* bin
* bzip2
* coreutils
* cxxlibs
* dcron
* devs
* e2fsprogs - This is not really needed for a VE, but let him install it
* elvis
* etc
* gawk
* glibc-solibs
* grep
* gzip
* kernel-modules - This is needed for the first boot only as kernel-ide
* less
* lilo - For first boot only too
* logrotate
* module-init-tools
* openssl-solibs
* pkgtools
* procps
* sed
* shadow
* sysklogd
* sysvinit
* tar
* udev
* util-linux

After selecting these packages just install the kernel and lilo, you are ready to run Slackware!

=== Configuring Slackware for acting as a VE ===

Now that you have a running minimal Slackware installation, You can begin to prepare it to be
a template for a [[VE]]. First you need some additional packages, 7 exactly:

{| class="wikitable"
|+ '''List of additional packages'''
! Package !! Directory of installation media to take the package from
|-
| groff-1.19.1-i486-3.tgz || slackware/ap
|-
| man-1.5p-i486-1.tgz || slackware/ap
|-
| quota-3.12-i486-1.tgz || slackware/ap
|-
| iptables-1.3.3-i486-1.tgz || slackware/n
|-
| openssh-4.2p1-i486-1.tgz || slackware/n
|-
| tcpip-0.17-i486-35.tgz || slackware/n
|-
| whois-4.6.16-i486-1.tgz || slackware/n
|}
You can install these packages issuing the following command:
<pre>
installpkg <packagename>
</pre>

After these steps, you are ready to move your Slackware installation into a [[VE]].

=== Moving a Slackware installation into a VE ===

I did it by compressing the whole filesystem into a tgz file and copying it to the host running OpenVZ.

Compressing it is easy:
<pre>
tar czf /slackware.tgz /
</pre>

But to copy it, you need to setup a network device on the slackware system (use <tt>ifconfig</tt> and <tt>ftp</tt>) or manually remove the hard drive containing the Slackware installation and copy the tgz file from there.

After you got the tgz file on the host, make a new directory into <tt>/vz/private</tt> with a new VEID, ''for example'' 777.
Uncompress the tgz file into this directory and remove the tgz.
<pre>
mv slackware.tgz /vz/private/777
cd /vz/private/777
gunzip -dc slackware.tgz |tar -xvf -
rm /vz/private/777/slackware.tgz
</pre>

== Preparing the new VE ==

=== Creating VE config ===

Now you need to create the configuration file for the [[VE]], 777.conf:

<pre>
vzctl set 777 --applyconfig vps.basic --save
</pre>

=== Getting the filesystem ready to run in a VE ===

Now you need to make some minor alterations under the /vz/private/777 directory.

==== Delete the directory /lost+found, clean /boot, /tmp, and /var/mail and make /proc ====
<pre>
rm -r /vz/private/777/lost+found
rm /vz/private/777/boot/*
rm /vz/private/777/tmp/*
rm /vz/private/777/var/mail/*
mkdir /vz/private/777/proc
</pre>

==== Delete the kernel modules from /lib/modules ====
<pre>
rm -r /vz/private/777/lib/modules
</pre>

==== Make a home directory for root, readable only by him ====
<pre>
mkdir /vz/private/777/root
chmod 0700 /vz/private/777/root
</pre>

==== Delete all keys from /etc/ssh ====
<pre>
rm /vz/private/777/etc/ssh/*key*
</pre>
This will ensure that a unique ssh key is generated for every single [[VE]] at the first boot.
Edit ssh_config and sshd_config here if you want.

==== Delete the file /etc/mtab and make it a symlink to /proc/mounts. ====
<pre>
rm /vz/private/777/etc/mtab
ln -s /vz/private/777/etc/mtab /proc/mounts
</pre>

==== Clean the /etc/fstab file ====
<pre>
echo -n > /vz/private/777/etc/fstab
</pre>

==== Edit /etc/inittab ====

Edit /vz/private/777/etc/inittab, put a hashmark (#) before the lines containing:
<pre>
c?:1235:respawn:/sbin/agetty 38400 tty? linux
</pre>
This will prevent linux gettys to spawn.

==== Edit /etc/shadow ====

Edit <tt>/vz/private/777/etc/shadow</tt>, change root's password in the first line to an exclamation mark (<tt>!</tt>):
<pre>
root:!:13305:0:::::
</pre>
This will disable the root login until the password changed with <tt>vzctl set VEID --userpasswd root:xxx</tt>.

==== Edit /etc/rc.d/rc.S ====

Edit <tt>/vz/private/777/etc/rc.d/rc.S</tt>, putting a hashmark (<tt>#</tt>) as the first character of the line containing:
<pre>
/bin/rm -f /etc/mtab*
</pre>
This should be line 162. This will forbid Slackware to delete our symlink at every reboot.

==== Edit /etc/rc.d/rc.syslog ====

Edit <tt>/vz/private/777/etc/rc.d/rc.syslog</tt> file, put a hashmark (<tt>#</tt>) before the lines containing
<pre>
sleep 1
echo "/usr/bin/klogd -c 3 -x"
/usr/bin/klogd -c 3 -x
killall klogd 2> /dev/null
</pre>
These should be lines 11, 12, 15 and 21. This will prevent <tt>klogd</tt> (which is usually not needed) from starting at boot time.

{{Note|if you are going to use iptables rules inside your Slackware VEs which will do logging (i.e. the ones with the <tt>LOG</tt> target), you should not disable <tt>klogd</tt>.}}

== Testing the new VE and making a cache file ==

=== Testing the new VE ===

To test the new [[VE]], simply start it:
<pre>
vzctl start 777
</pre>
If you did everything all right (and this article is correct) your new Slackware [[VE]] will boot.

If the VE booted, and you can enter/ssh to it, then stop it:
<pre>
vzctl stop 777
</pre>

=== Making a cache file ===

Now make a .tar.gz out of the [[VE]]:
<pre>
tar czf /vz/template/cache/slackware-10.2-i486-minimal.tar.gz /vz/private/777/
</pre>

== Testing the new cache file ==

To test the the new cache file, issue:
<pre>
vzctl create 555 --ostemplate slackware-10.2-i486-minimal --ipadd x.x.x.x --hostname testy
</pre>

If created successfully, try to start it:
<pre>
vzctl start 555
</pre>
If it started, and you can ssh in, congratulations, you've got a working slackware template!

[[Category: HOWTO]]
[[Category: Templates]]

Slackware template creation

2006-06-06T20:58:33Z

Scythe:

Talk:Slackware template creation

2006-06-06T20:54:52Z

Scythe:

Slackware template creation

2006-06-06T20:48:13Z

Scythe:

Slackware template creation

2006-06-06T19:16:06Z

Scythe:

This page is about making a template cache for OpenVZ [[VE]] from Slackware linux.
(This method was used for creating the minimal cache from Slackware 10.2)
The method is basically the same as described in article [[Debian template creation]].

== Getting a Slackware root filesystem ==

=== Downloading and installing Slackware ===

First you need to download Slackware linux from [http://www.slackware.org/getslack/ http://www.slackware.org/getslack/]. Then you have to [http://www.slackware.org/install/ install] it to some hardware you can spare while the cache creation process is going on. For [[VE]] creation it is recommended not to install any unnecessary software into the box you are making the cache from.
This means for a minimal Slackware 10.2 cache I have chosen only series A (<tt>Base Linux System</tt>) at the package series selection screen of Slackware Setup. Then '''expert''' prompting mode on the next screen. On the Series A package selection screen I chose the following packages:

* kernel-ide - This is requied to boot the OS to be able to get it's root filesystem
* aaa_base
* aaa_elflibs
* bash
* bin
* bzip2
* coreutils
* cxxlibs
* dcron
* devs
* e2fsprogs - This is not really needed for a VE, but let him install it
* elvis
* etc
* gawk
* glibc-solibs
* grep
* gzip
* kernel-modules - This is needed for the first boot only as kernel-ide
* less
* lilo - For first boot only too
* logrotate
* module-init-tools
* openssl-solibs
* pkgtools
* procps
* sed
* shadow
* sysklogd
* sysvinit
* tar
* udev
* util-linux

After selecting these packages just install the kernel and lilo, you are ready to run Slackware!

=== Configuring Slackware for acting as a VE ===

Now that you have a running minimal Slackware installation, You can begin to prepare it to be
a template for a [[VE]]. First you need some additional packages, 7 exactly:

* groff-1.19.1-i486-3.tgz from the slackware/ap directory of installation media
* man-1.5p-i486-1.tgz from the slackware/ap directory of installation media
* quota-3.12-i486-1.tgz from the slackware/ap directory of installation media
* iptables-1.3.3-i486-1.tgz from the slackware/n directory of installation media
* openssh-4.2p1-i486-1.tgz from the slackware/n directory of installation media
* tcpip-0.17-i486-35.tgz from the slackware/n directory of installation media
* whois-4.6.16-i486-1.tgz from the slackware/n directory of installation media

You can install these packages issuing the following command:
<pre>
# installpkg <packagename>
</pre>

After these steps, you are ready to move your Slackware installation into a [[VE]]

=== Moving a Slackware installation into a VE ===

I did it by compressing the whole filesystem into a tgz file and copying it to the host running OpenVZ.

Compressing it is easy:
<pre>
# tar czf /slackware.tgz /
</pre>

But to copy it, you need to setup a network device on the slackware system (use <tt>ifconfig</tt> and <tt>ftp</tt> or manually remove the hard drive containing the Slackware installation and copying the tgz file from there.

After you got the tgz file on the host, make a new directory into /vz/private with a new VPSID, for example 777.
Uncompress the tgz file into this directory and delete it.
<pre>
mv slackware.tgz /vz/private/777
cd /vz/private/777
gunzip -dc slackware.tgz |tar -xvf -
rm /vz/private/777/slackware.tgz
</pre>

== Preparing the new VE ==

=== Creating a new .conf file ===

Now you need to create the config file for the Slackware [[VE]], 777.conf.

<pre>
vzctl set 777 --applyconfig vps.basic --save
</pre>

You need to set it's OSTEMPLATE.
<pre>
echo "OSTEMPLATE=slackware-10.2-i486-minimal" >> /etc/sysconfig/vz-scripts/777.conf
</pre>

And an IP address and a Hostname
<pre>
vzctl set 777 --ipadd x.x.x.x --save
vzctl set 777 --hostname myslacky --save
</pre>

=== Getting the filesystem ready to run in a VE ===

Now you need to make some minor alterations under the /vz/private/777 directory.

==== Delete the directory /lost+found, clean /boot, /tmp, and /var/mail and make /proc ====
<pre>
rm -r /vz/private/777/lost+found
rm /vz/private/777/boot/*
rm /vz/private/777/tmp/*
rm /vz/private/777/var/mail/*
mkdir /vz/private/777/proc
</pre>

==== Delete the kernel modules from /lib/modules ====
<pre>
rm -r /vz/private/777/lib/modules
</pre>

==== Make a home directory for root, readable only by him ====
<pre>
mkdir /vz/private/777/root
chmod 0700 /vz/private/777/root
</pre>

==== Delete all keys from /etc/ssh ====
<pre>
rm /vz/private/777/etc/ssh/*key*
</pre>
This will ensure that a unique ssh key is generated for every single [[VE]] at the first boot.
Edit ssh_config and sshd_config here if you want.

==== Delete the file /etc/mtab and make it a symlink to /proc/mounts. ====
<pre>
rm /vz/private/777/etc/mtab
ln -s /vz/private/777/etc/mtab /proc/mouns
</pre>

==== Clean the /etc/fstab file ====
<pre>
echo -n > /vz/private/777/etc/fstab
</pre>

==== Edit /etc/inittab ====

Edit /vz/private/777/etc/inittab, put a hashmark (#) before the lines containing:
<pre>
c?:1235:respawn:/sbin/agetty 38400 tty? linux
</pre>
This will prevent linux gettys to spawn.

==== Edit /etc/shadow ====

Edit /vz/private/777/etc/shadow, change root's password in the first line to an exclamation mark (!):
<pre>
#root:!:13305:0:::::
</pre>
This will disable the root login until the password chaned with "vzctl set VPSID --userpasswd root:xxx"

==== Edit /etc/rc.d/rc.S ====

Edit /vz/private/777/etc/rc.d/rc.S, put a hashmark (#) before the line containing:
<pre>
/bin/rm -f /etc/mtab*
</pre>
This should be line 162. This will forbid Slackware to delete our symlink at every reboot.

==== Edit /etc/rc.d/rc.syslog ====

Edit /vz/private/777/etc/rc.d/rc.syslog, put a hashmark (#) before the lines containing
<pre>
sleep 1
echo "/usr/bin/klogd -c 3 -x"
/usr/bin/klogd -c 3 -x
killall klogd 2> /dev/null
</pre>
These should be lines 11, 12, 15 and 21. This will prevent klogd (which is not needed) from starting at boottime.

== Testing the new VE and making a cache file ==

=== Testing the new VE ===

To test the new [[VE]], simply start it:
<pre>
vzctl start 777
</pre>
If you did everythingall right (and I didn't make a mistake here) your new slackware will boot.

If the VE booted, and you can enter/ssh in it, then stop it.
<pre>
vzctl stop 777
</pre>

=== Making a cache file ===

Now make a .tar.gz out of the [[VE]]:
<pre>
tar czf /vz/template/cache/slackware-10.2-i486-minimal.tar.gz /vz/private/777/
</pre>

== Testing the new cache file ==

To test the the new cache file, issue:
<pre>
vzctl create 555 --ostemplate slackware-10.2-i486-minimal --ipadd x.x.x.x --hostname testy
</pre>

If created successfully, try to start it:
<pre>
vzctl start 555
</pre>
If it started, and you can ssh in, congratulations, you've got a working slackware template!

[[Category: HOWTO]]
[[Category: Templates]]

Slackware template creation

2006-06-06T19:14:57Z

Scythe:

This page is about making a template cache for OpenVZ [[VE]] from Slackware linux.
(This method was used for creating the minimal cache from Slackware 10.2)
The method is basically the same as described in article [[Debian template creation]].

== Getting a Slackware root filesystem ==

=== Downloading and installing Slackware ===

First you need to download Slackware linux from [http://www.slackware.org/getslack/ http://www.slackware.org/getslack/]. Then you have to [http://www.slackware.org/install/ install] it to some hardware you can spare while the cache creation process is going on. For [[VE]] creation it is recommended not to install any unnecessary software into the box you are making the cache from.
This means for a minimal Slackware 10.2 cache I have chosen only series A (<tt>Base Linux System</tt>) at the package series selection screen of Slackware Setup. Then '''expert''' prompting mode on the next screen. On the Series A package selection screen I chose the following packages:

* kernel-ide - This is requied to boot the OS to be able to get it's root filesystem
* aaa_base
* aaa_elflibs
* bash
* bin
* bzip2
* coreutils
* cxxlibs
* dcron
* devs
* e2fsprogs - This is not really needed for a VE, but let him install it
* elvis
* etc
* gawk
* glibc-solibs
* grep
* gzip
* kernel-modules - This is needed for the first boot only as kernel-ide
* less
* lilo - For first boot only too
* logrotate
* module-init-tools
* openssl-solibs
* pkgtools
* procps
* sed
* shadow
* sysklogd
* sysvinit
* tar
* udev
* util-linux

After selecting these packages just install the kernel and lilo, you are ready to run Slackware!

=== Configuring Slackware for acting as a VE ===

Now that you have a running minimal Slackware installation, You can begin to prepare it to be
a template for a [[VE]]. First you need some additional packages, 7 exactly:

* groff-1.19.1-i486-3.tgz from the slackware/ap directory of installation media
* man-1.5p-i486-1.tgz from the slackware/ap directory of installation media
* quota-3.12-i486-1.tgz from the slackware/ap directory of installation media
* iptables-1.3.3-i486-1.tgz from the slackware/n directory of installation media
* openssh-4.2p1-i486-1.tgz from the slackware/n directory of installation media
* tcpip-0.17-i486-35.tgz from the slackware/n directory of installation media
* whois-4.6.16-i486-1.tgz from the slackware/n directory of installation media

You can install these packages issuing the following command:
<pre>
# installpkg <packagename>
</pre>

After these steps, you are ready to move your Slackware installation into a [[VE]]

=== Moving a Slackware installation into a VE ===

I did it by compressing the whole filesystem into a tgz file and copying it to the host running OpenVZ.

Compressing it is easy:
<pre>
# tar czf /slackware.tgz /
</pre>

But to copy it, you need to setup a network device on the slackware system (use <tt>ifconfig</tt> and <tt>ftp</tt> or manually remove the hard drive containing the Slackware installation and copying the tgz file from there.

After you got the tgz file on the host, make a new directory into /vz/private with a new VPSID, for example 777.
Uncompress the tgz file into this directory and delete it.
<pre>
mv slackware.tgz /vz/private/777
cd /vz/private/777
gunzip -dc slackware.tgz |tar -xvf -
rm /vz/private/777/slackware.tgz
</pre>

== Preparing the new VE ==

=== Creating a new .conf file ===

Now you need to create the config file for the Slackware [[VE]], 777.conf.

<pre>
vzctl set 777 --applyconfig vps.basic --save
</pre>

You need to set it's OSTEMPLATE.
<pre>
echo "OSTEMPLATE=slackware-10.2-i486-minimal" >> /etc/sysconfig/vz-scripts/777.conf
</pre>

And an IP address and a Hostname
<pre>
vzctl set 777 --ipadd x.x.x.x --save
vzctl set 777 --hostname myslacky --save
</pre>

=== Getting the filesystem ready to run in a VE ===

Now you need to make some minor alterations under the /vz/private/777 directory.

==== Delete the directory /lost+found, clean /boot, /tmp, and /var/mail and make /proc ====
<pre>
rm -r /vz/private/777/lost+found
rm /vz/private/777/boot/*
rm /vz/private/777/tmp/*
rm /vz/private/777/var/mail/*
mkdir /vz/private/777/proc
</pre>

==== Delete the kernel modules from /lib/modules ====
<pre>
rm -r /vz/private/777/lib/modules
</pre>

==== Make a home directory for root, readable only by him ====
<pre>
mkdir /vz/private/777/root
chmod 0700 /vz/private/777/root
</pre>

==== Delete all keys from /etc/ssh ====
<pre>
rm /vz/private/777/etc/ssh/*key*
</pre>
This will ensure that a unique ssh key is generated for every single [[VE]] at the first boot.
Edit ssh_config and sshd_config here if you want.

==== Delete the file /etc/mtab and make it a symlink to /proc/mounts. ====
<pre>
rm /vz/private/777/etc/mtab
ln -s /vz/private/777/etc/mtab /proc/mouns
</pre>

==== Clean the /etc/fstab file ====
<pre>
echo -n > /vz/private/777/etc/fstab
</pre>

==== Edit /etc/inittab ====

Edit /vz/private/777/etc/inittab, put a hashmark (#) before the lines containing ====
<pre>
c?:1235:respawn:/sbin/agetty 38400 tty? linux
</pre>
This will prevent linux gettys to spawn.

==== Edit /etc/shadow ====

Edit /vz/private/777/etc/shadow, change root's password in the first line to an exclamation mark (!):
<pre>
#root:!:13305:0:::::
</pre>
This will disable the root login until the password chaned with "vzctl set VPSID --userpasswd root:xxx"

==== Edit /etc/rc.d/rc.S ====

Edit /vz/private/777/etc/rc.d/rc.S, put a hashmark (#) before the line containing:
<pre>
/bin/rm -f /etc/mtab*
</pre>
This should be line 162. This will forbid Slackware to delete our symlink at every reboot.

==== Edit /etc/rc.d/rc.syslog ====

Edit /vz/private/777/etc/rc.d/rc.syslog, put a hashmark (#) before the lines containing
<pre>
sleep 1
echo "/usr/bin/klogd -c 3 -x"
/usr/bin/klogd -c 3 -x
killall klogd 2> /dev/null
</pre>
These should be lines 11, 12, 15 and 21. This will prevent klogd (which is not needed) from starting at boottime.

== Testing the new VE and making a cache file ==

=== Testing the new VE ===

To test the new [[VE]], simply start it:
<pre>
vzctl start 777
</pre>
If you did everythingall right (and I didn't make a mistake here) your new slackware will boot.

If the VE booted, and you can enter/ssh in it, then stop it.
<pre>
vzctl stop 777
</pre>

=== Making a cache file ===

Now make a .tar.gz out of the [[VE]]:
<pre>
tar czf /vz/template/cache/slackware-10.2-i486-minimal.tar.gz /vz/private/777/
</pre>

== Testing the new cache file ==

To test the the new cache file, issue:
<pre>
vzctl create 555 --ostemplate slackware-10.2-i486-minimal --ipadd x.x.x.x --hostname testy
</pre>

If created successfully, try to start it:
<pre>
vzctl start 555
</pre>
If it started, and you can ssh in, congratulations, you've got a working slackware template!

[[Category: HOWTO]]
[[Category: Templates]]

Slackware template creation

2006-06-06T19:08:25Z

Scythe:

This page is about making a template cache for OpenVZ [[VE]] from Slackware linux.
(This method was used for creating the minimal cache from Slackware 10.2)
The method is basically the same as described in article [[Debian template creation]].

== Getting a Slackware root filesystem ==

=== Downloading and installing Slackware ===

First you need to download Slackware linux from [http://www.slackware.org/getslack/ http://www.slackware.org/getslack/]. Then you have to [http://www.slackware.org/install/ install] it to some hardware you can spare while the cache creation process is going on. For [[VE]] creation it is recommended not to install any unnecessary software into the box you are making the cache from.
This means for a minimal Slackware 10.2 cache I have chosen only series A (<tt>Base Linux System</tt>) at the package series selection screen of Slackware Setup. Then '''expert''' prompting mode on the next screen. On the Series A package selection screen I chose the following packages:

* kernel-ide - This is requied to boot the OS to be able to get it's root filesystem
* aaa_base
* aaa_elflibs
* bash
* bin
* bzip2
* coreutils
* cxxlibs
* dcron
* devs
* e2fsprogs - This is not really needed for a VE, but let him install it
* elvis
* etc
* gawk
* glibc-solibs
* grep
* gzip
* kernel-modules - This is needed for the first boot only as kernel-ide
* less
* lilo - For first boot only too
* logrotate
* module-init-tools
* openssl-solibs
* pkgtools
* procps
* sed
* shadow
* sysklogd
* sysvinit
* tar
* udev
* util-linux

After selecting these packages just install the kernel and lilo, you are ready to run Slackware!

=== Configuring Slackware for acting as a VE ===

Now that you have a running minimal Slackware installation, You can begin to prepare it to be
a template for a [[VE]]. First you need some additional packages, 7 exactly:

* groff-1.19.1-i486-3.tgz from the slackware/ap directory of installation media
* man-1.5p-i486-1.tgz from the slackware/ap directory of installation media
* quota-3.12-i486-1.tgz from the slackware/ap directory of installation media
* iptables-1.3.3-i486-1.tgz from the slackware/n directory of installation media
* openssh-4.2p1-i486-1.tgz from the slackware/n directory of installation media
* tcpip-0.17-i486-35.tgz from the slackware/n directory of installation media
* whois-4.6.16-i486-1.tgz from the slackware/n directory of installation media

You can install these packages issuing the following command:
<pre>
# installpkg <packagename>
</pre>

After these steps, you are ready to move your Slackware installation into a [[VE]]

=== Moving a Slackware installation into a VE ===

I did it by compressing the whole filesystem into a tgz file and copying it to the host running OpenVZ.

Compressing it is easy:
<pre>
# tar czf /slackware.tgz /
</pre>

But to copy it, you need to setup a network device on the slackware system (use <tt>ifconfig</tt> and <tt>ftp</tt> or manually remove the hard drive containing the Slackware installation and copying the tgz file from there.

After you got the tgz file on the host, make a new directory into /vz/private with a new VPSID, for example 777.
Uncompress the tgz file into this directory and delete it.
<pre>
mv slackware.tgz /vz/private/777
cd /vz/private/777
gunzip -dc slackware.tgz |tar -xvf -
rm /vz/private/777/slackware.tgz
</pre>

== Preparing the new VE ==

=== Creating a new .conf file ===

Now you need to create the config file for the Slackware [[VE]], 777.conf.

<pre>
vzctl set 777 --applyconfig vps.basic --save
</pre>

You need to set it's OSTEMPLATE.
<pre>
echo "OSTEMPLATE=slackware-10.2-i486-minimal" >> /etc/sysconfig/vz-scripts/777.conf
</pre>

And an IP address and a Hostname
<pre>
vzctl set 777 --ipadd x.x.x.x --save
vzctl set 777 --hostname myslacky --save
</pre>

=== Getting the filesystem ready to run in a VE ===

Now you need to make some minor alterations under the /vz/private/777 directory.

==== Delete the directory /lost+found, clean /boot, /tmp, and /var/mail and make /proc ====
<pre>
rm -r /vz/private/777/lost+found
rm /vz/private/777/boot/*
rm /vz/private/777/tmp/*
rm /vz/private/777/var/mail/*
mkdir /vz/private/777/proc
</pre>

==== Delete the kernel modules from /lib/modules ====
<pre>
rm -r /vz/private/777/lib/modules
</pre>

==== Make a home directory for root, readable only by him ====
<pre>
mkdir /vz/private/777/root
chmod 0700 /vz/private/777/root
</pre>

==== Delete all keys from /vz/private/777/etc/ssh ====
<pre>
rm /vz/private/777/etc/ssh/*key*
</pre>
This will ensure that a unique ssh key is generated for every single [[VE]] at the first boot.
Edit ssh_config and sshd_config here if you want.

==== Delete the file /etc/mtab and make it a symlink to /proc/mounts. ====
<pre>
rm /vz/private/777/etc/mtab
ln -s /vz/private/777/etc/mtab /proc/mouns
</pre>

==== Clean the /etc/fstab file ====
<pre>
echo -n > /vz/private/777/etc/fstab
</pre>

==== Edit /vz/private/777/etc/inittab ====

Edit /vz/private/777/etc/inittab, put a hashmark (#) before the lines containing ====
<pre>
c?:1235:respawn:/sbin/agetty 38400 tty? linux
</pre>
This will prevent linux gettys to spawn.

==== Edit /vz/private/777/etc/shadow====

Edit /vz/private/777/etc/shadow, change root's password in the first line to an exclamation mark (!):
<pre>
#root:!:13305:0:::::
</pre>
This will disable the root login until the password chaned with "vzctl set VPSID --userpasswd root:xxx"

==== Edit /vz/private/777/etc/rc.d/rc.S ====

Edit /vz/private/777/etc/rc.d/rc.S, put a hashmark (#) before the line containing:
<pre>
/bin/rm -f /etc/mtab*
</pre>
This should be line 162. This will forbid Slackware to delete our symlink at every reboot.

==== Edit /vz/private/777/etc/rc.d/rc.syslog ====

Edit /vz/private/777/etc/rc.d/rc.syslog, put a hashmark (#) before the lines containing
<pre>
sleep 1
echo "/usr/bin/klogd -c 3 -x"
/usr/bin/klogd -c 3 -x
killall klogd 2> /dev/null
</pre>
These should be lines 11, 12, 15 and 21. This will prevent klogd (which is not needed) from starting at boottime.

== Testing the new VE and making a cache file ==

=== Testing the new VE ===

To test the new [[VE]], simply start it:
<pre>
vzctl start 777
</pre>
If you did everythingall right (and I didn't make a mistake here) your new slackware will boot.

If the VE booted, and you can enter/ssh in it, then stop it.
<pre>
vzctl stop 777
</pre>

=== Making a cache file ===

Now make a .tar.gz out of the [[VE]]:
<pre>
tar czf /vz/template/cache/slackware-10.2-i486-minimal.tar.gz /vz/private/777/
</pre>

== Testing the new cache file ==

To test the the new cache file, issue:
<pre>
vzctl create 555 --ostemplate slackware-10.2-i486-minimal --ipadd x.x.x.x --hostname testy
</pre>

If created successfully, try to start it:
<pre>
vzctl start 555
</pre>
If it started, and you can ssh in, congratulations, you've got a working slackware template!

[[Category: HOWTO]]
[[Category: Templates]]