Slackware template creation - Revision history

84.252.55.232: /* Edit /etc/rc.d/rc.syslog */

2011-05-28T08:54:13Z

‎Edit /etc/rc.d/rc.syslog

84.252.55.232: /* Edit /etc/rc.d/rc.S */

2011-05-28T08:44:17Z

‎Edit /etc/rc.d/rc.S

Kir: /* Moving a Slackware installation into a container */ use --numeric-owner option for tar

2009-10-19T10:45:07Z

‎Moving a Slackware installation into a container: use --numeric-owner option for tar

Botinki Kira: Robot: Automated text replacement (-VE +container)

2008-03-11T11:35:58Z

Robot: Automated text replacement (-VE +container)

Botinki Kira: Robot: Automated text replacement (-VEs +containers)

2008-03-11T09:49:17Z

Robot: Automated text replacement (-VEs +containers)

Botinki Kira: Robot: Automated text replacement (-VEID +CTID)

2008-03-11T09:44:06Z

Robot: Automated text replacement (-VEID +CTID)

Kir: Reverted edit of 1158264444, changed back to last version by Kir

2006-09-14T20:14:46Z

Reverted edit of 1158264444, changed back to last version by Kir

Kir: Reverted edit of 1158177983, changed back to last version by Erickinolik

2006-09-13T21:45:44Z

Reverted edit of 1158177983, changed back to last version by Erickinolik

Erickinolik: had the ln options backwards

2006-06-21T04:43:38Z

had the ln options backwards

Erickinolik: /* Moving a Slackware installation into a VE */

2006-06-21T04:41:50Z

‎Moving a Slackware installation into a VE

@@ Line 181: / Line 181: @@
 </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 containers which will do logging (i.e. the ones with the <tt>LOG</tt> target), you should not disable <tt>klogd</tt>.}}

@@ Line 169: / Line 169: @@
 /bin/rm -f /etc/mtab*
 </pre>
-This should be line 162. This will forbid Slackware to delete our symlink at every reboot.
+This should be line 162 (239 - slackware 13.1). This will forbid Slackware to delete our symlink at every reboot.
 ==== Edit /etc/rc.d/rc.syslog ====

@@ Line 81: / Line 81: @@
 Compressing it is easy:
 <pre>
-tar czf /slackware.tgz --exclude /slackware.tgz /
+tar --numeric-owner -czf /slackware.tgz --exclude /slackware.tgz /
 </pre>

@@ Line 1: / Line 1: @@
-This page is about making a template cache for OpenVZ [[VE]] from Slackware linux.
+This page is about making a template cache for OpenVZ [[container]] 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]].
@@ Line 7: / Line 7: @@
 === 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.
+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 [[container]] 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:
@@ Line 20: / Line 20: @@
 * dcron
 * devs
-* e2fsprogs <i>- This is not really needed for a VE, but let him install it</i>
+* e2fsprogs <i>- This is not really needed for a container, but let him install it</i>
 * elvis
 * etc
@@ Line 45: / Line 45: @@
 After selecting these packages just install the kernel and lilo, you are ready to run Slackware!
-=== Configuring Slackware for acting as a VE ===
+=== Configuring Slackware for acting as a container ===
 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:
+a template for a [[container]]. First you need some additional packages, 7 exactly:
 {| class="wikitable"
@@ Line 73: / Line 73: @@
 </pre>
-After these steps, you are ready to move your Slackware installation into a [[VE]].
+After these steps, you are ready to move your Slackware installation into a [[container]].
-=== Moving a Slackware installation into a VE ===
+=== Moving a Slackware installation into a container ===
 I did it by compressing the whole filesystem into a tgz file and copying it to the host running OpenVZ.
@@ Line 95: / Line 95: @@
 </pre>
-== Preparing the new VE ==
+== Preparing the new container ==
-=== Creating VE config ===
+=== Creating container config ===
-Now you need to create the configuration file for the [[VE]], 777.conf:
+Now you need to create the configuration file for the [[container]], 777.conf:
 <pre>
@@ Line 105: / Line 105: @@
 </pre>
-=== Getting the filesystem ready to run in a VE ===
+=== Getting the filesystem ready to run in a container ===
 Now you need to make some minor alterations under the /vz/private/777 directory.
@@ Line 133: / Line 133: @@
 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.
+This will ensure that a unique ssh key is generated for every single [[container]] at the first boot.
 Edit ssh_config and sshd_config here if you want.
@@ Line 184: / Line 184: @@
 {{Note|if you are going to use iptables rules inside your Slackware containers 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 container and making a cache file ==
-=== Testing the new VE ===
+=== Testing the new container ===
-To test the new [[VE]], simply start it:
+To test the new [[container]], 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 you did everything all right (and this article is correct) your new Slackware [[container]] will boot.
-If the VE booted, and you can enter/ssh to it, then stop it:
+If the container booted, and you can enter/ssh to it, then stop it:
 <pre>
 vzctl stop 777
@@ Line 201: / Line 201: @@
 === Making a cache file ===
-Now make a .tar.gz out of the [[VE]]:
+Now make a .tar.gz out of the [[container]]:
 <pre>
 tar czf /vz/template/cache/slackware-10.2-i486-minimal.tar.gz /vz/private/777/

@@ Line 182: / Line 182: @@
 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>.}}
+{{Note|if you are going to use iptables rules inside your Slackware containers 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 ==

@@ Line 86: / Line 86: @@
 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.
+After you got the tgz file on the host, make a new directory into <tt>/vz/private</tt> with a new CTID, ''for example'' 777.
 Uncompress the tgz file into this directory and remove the tgz.
 <pre>
@@ Line 161: / Line 161: @@
 root:!:13305:0:::::
 </pre>
-This will disable the root login until the password changed with <tt>vzctl set VEID --userpasswd root:xxx</tt>.
+This will disable the root login until the password changed with <tt>vzctl set CTID --userpasswd root:xxx</tt>.
 ==== Edit /etc/rc.d/rc.S ====

← Older revision	Revision as of 20:14, 14 September 2006
(No difference)

← Older revision	Revision as of 21:45, 13 September 2006
(No difference)

@@ Line 139: / Line 139: @@
 <pre>
 rm /vz/private/777/etc/mtab
-ln -s /vz/private/777/etc/mtab /proc/mounts
+ln -s /proc/mounts /vz/private/777/etc/mtab
 </pre>