Difference between revisions of "Creating a Live CD"

From LFScript
(Created page with "This page guides you through the steps required to create a Live CD of your system. The ability to create a Live CD is one of the core reasons of being of LFScript. == Compil...")
 
 
(13 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
This page guides you through the steps required to create a Live CD of your system. The ability to create a Live CD is one of the core reasons of being of LFScript.
+
[[Category:Documentation]]
 +
This page guides you through the steps required to create a Live CD of your
 +
system. The ability to create a Live CD is one of the core features of
 +
LFScript.
 +
 
 +
'''All commands presented here should be executed from the LFScript directory'''
  
 
== Compile your system ==
 
== Compile your system ==
−
Although it is not required, it is highly recommended that you compile your system into packages beforehand. For example:
+
Although it is not required, it is highly recommended that you compile your
 +
system into packages beforehand. For example:
 +
 
 
<pre>./lfscript -Bux fsos</pre>
 
<pre>./lfscript -Bux fsos</pre>
−
This command builds all packages (except those that are only for the 32-bit version) of fsOS.
+
 
 +
This command builds all packages (except those that are only for the 32-bit
 +
version) of fsOS.
  
 
== Create a system image ==
 
== Create a system image ==
−
<pre>dd if=/dev/zero of=sources/rootfs-$(uname -m).img bs=1G count=10 seek=100</pre>
+
<pre>dd if=/dev/zero of=sources/rootfs-$(uname -m).img bs=1G seek=10 count=0</pre>
−
This command should instantly create a 10GB sparse file. The file will not actually take up 10GB of your precious free disk space. It's actual size will initially be zero. Once it has a file system, has been mounted and starts to contain actual files it will automatically grow and use real disk space as needed (up to 10GB). This means that the actual size of the file will never be greater than the minimum size needed to contain your system.
+
 
 +
This command should instantly create a 10GB sparse file. The file will not
 +
actually take up 10GB of your precious free disk space. It's actual size will
 +
initially be zero. Once it has a file system, has been mounted and starts to
 +
contain actual files it will automatically grow and use real disk space as
 +
needed (up to 10GB). This means that the actual size of the file will never be
 +
greater than the minimum size needed to contain your system.
 +
 
 +
'''''Some filesystems do not support sparse files. On those systems, the above command will create a true 10GB file. For example, if you are using Ubuntu and you have your home folder encrypted (ecryptfs), you can not have sparse files anywhere in your home tree.'''''
  
−
The file will be created in the <code>sources</code> directory, because the <code>buildiso</code> script will need to be able to find the image.
+
The file will be created in the <code>sources</code> directory, because the
 +
<code>buildiso</code> script will need to be able to find the image.
  
−
The <code>$(uname -m)</code> part will automatically resolve to your host system CPU architecture (<code>i686</code>, <code>x86_64</code>, or something else), giving the image a name like <code>rootfs-i686.img</code>. Using <code>$(uname -m)</code> in these commands makes them suitable for copy-pasting on any machine.
+
The <code>$(uname -m)</code> part will automatically resolve to your host
 +
system CPU architecture (<code>i686</code>, <code>x86_64</code>, or something
 +
else), giving the image a name like <code>rootfs-i686.img</code>. Using
 +
<code>$(uname -m)</code> in these commands makes them suitable for copy-pasting
 +
on any machine.
  
 
== Create a file system on the image ==
 
== Create a file system on the image ==
 
This command should work on any machine with a recent kernel:
 
This command should work on any machine with a recent kernel:
 +
 
<pre>mkfs.ext4 -F sources/rootfs-$(uname -m).img</pre>
 
<pre>mkfs.ext4 -F sources/rootfs-$(uname -m).img</pre>
  
−
However, if you want to optimize for size at this stage (this does NOT affect the size of the final ISO image) and have <code>btrfs</code> available you could issue this one in stead:
+
However, if you want to optimize for size at this stage (this does NOT affect
 +
the size of the final ISO image) and have <code>btrfs</code> available you
 +
could issue this one in stead:
 +
 
 
<pre>mkfs.btrfs sources/rootfs-$(uname -m).img</pre>
 
<pre>mkfs.btrfs sources/rootfs-$(uname -m).img</pre>
  
−
A compressed <code>btrfs</code> system image will take up about 500MB of space if you just install a basic LFS system on it, compared to 1.3GB for an uncompressed <code>ext4</code> image.
+
A compressed <code>btrfs</code> system image will take up about 500MB of space
 +
if you just install a basic LFS system on it, compared to 1.3GB for an
 +
uncompressed <code>ext4</code> image.
  
−
Any file system for Linux should work just fine, and it does not even matter if the OS you will install in it has support for the file system you have selected. Later on, the image will be converted to <code>SquashFS</code> anyway.
+
Any file system for Linux should work just fine, and it does not even matter if
 +
the OS you will install in it has support for the file system you have
 +
selected. Later on, the image will be converted to <code>SquashFS</code>
 +
anyway.
  
 
== Create temporary installation directories ==
 
== Create temporary installation directories ==
−
<pre>mkdir -v rootfs</pre>
+
<pre>mkdir -v install_root</pre>
 +
 
 +
And if you would like to keep the overhead of <code>sources</code> and
 +
<code>tools</code> directories out of the image (only affects the system image
 +
size, not the ISO size):
  
−
And if you would like to keep the overhead of <code>sources</code> and <code>tools</code> directories out of the image (only affects the system image size, not the ISO size):
+
<pre>mkdir -v install_overhead</pre>
−
<pre>mkdir -v rootfs_overhead</pre>
 
  
 
== Mount the system image ==
 
== Mount the system image ==
 
If you installed an <code>ext4</code> fle system on the system image:
 
If you installed an <code>ext4</code> fle system on the system image:
−
<pre>mount -o loop sources/rootfs-$(uname -m).img rootfs</pre>
+
 
 +
<pre>mount -o loop sources/rootfs-$(uname -m).img install_root</pre>
  
 
Or if you used <code>btrfs</code>:
 
Or if you used <code>btrfs</code>:
−
<pre>mount -o loop,compress sources/rootfs-$(uname -m).img rootfs</pre>
+
 
 +
<pre>mount -o loop,compress sources/rootfs-$(uname -m).img install_root</pre>
  
 
== Install your system to the image ==
 
== Install your system to the image ==
−
<pre>./lfscript { base system and extra package options } -i rootfs -I rootfs_overhead</pre>
+
This installation command takes the form of <code>./lfscript [your_system_options] -i install_root -I install_overhead</code>. If you did not create the overhead directory, leave out <code>-I install_overhead</code>.
 +
 
 +
For example:
 +
 
 +
<pre>./lfscript -Bux fsos -i install_root -I install_overhead</pre>
  
−
If you did not create the overhead directory, leave out <code>-I rootfs_overhead</code>.
+
== Security ==
 +
It is a bad idea to keep SSH keys on your Live CD, so remove them:
 +
<pre>rm -rvf install_root/etc/ssh/ssh_host_*_key</pre>
  
−
For example:
+
If you have installed OpenSSH (and the OpenSSH bootscript), these keys need to be regenerated using a custom boot script. If you are not installing <code>fsos</code>, take a look at the page '[[FsOS_without_X11]]' for an example of the boot script.
−
<pre>./lfscript -Bux fsos -i rootfs -I rootfs_overhead</pre>
 
  
 
== Unmount the system image ==
 
== Unmount the system image ==
−
<pre>umount rootfs</pre>
+
<pre>umount install_root</pre>
  
 
== Build the ISO image ==
 
== Build the ISO image ==
 
<pre>./lfscript -Bux buildiso</pre>
 
<pre>./lfscript -Bux buildiso</pre>
  
−
The script that builds the ISO image could just as well be designed for use outside of LFScript (and in fact, with LFScript 3 it was). However, by executing <code>buildiso</code> through LFScript the ISO is created by your own system, which removes the need to have the utilities required to run <code>buildiso</code> (like <code>SquashFS</code> and <code>cdrtools</code> for example) installed on your host system. This reduces the risk of build failures considerably.
+
The script that builds the ISO image could just as well be designed for use
 +
outside of LFScript (and in fact, with LFScript 3 it was). However, by
 +
executing [[BuildISO]] through LFScript the ISO is created by your own
 +
system, which removes the need to have the utilities required to run
 +
[[BuildISO]] (like <code>SquashFS</code> and <code>cdrtools</code> for
 +
example) installed on your host system. This reduces the risk of build failures
 +
considerably.
 +
 
 +
Once completed, your Live CD ISO image will be saved to your
 +
<code>packages</code> directory.
 +
 
 +
== Cleanup ==
 +
This command removes both the temporary installation directories, and the
 +
original system image which you probably don't need anymore:
  
−
Once completed, your Live CD ISO image will be saved to your <code>packages</code> directory.
+
<pre>rm -rv&#102; install_root install_overhead sources/rootfs-$(uname -m).img</pre>

Latest revision as of 22:22, 15 April 2017

This page guides you through the steps required to create a Live CD of your system. The ability to create a Live CD is one of the core features of LFScript.

All commands presented here should be executed from the LFScript directory

Compile your system

Although it is not required, it is highly recommended that you compile your system into packages beforehand. For example: 

./lfscript -Bux fsos

This command builds all packages (except those that are only for the 32-bit version) of fsOS.

Create a system image

dd if=/dev/zero of=sources/rootfs-$(uname -m).img bs=1G seek=10 count=0

This command should instantly create a 10GB sparse file. The file will not actually take up 10GB of your precious free disk space. It's actual size will initially be zero. Once it has a file system, has been mounted and starts to contain actual files it will automatically grow and use real disk space as needed (up to 10GB). This means that the actual size of the file will never be greater than the minimum size needed to contain your system.

Some filesystems do not support sparse files. On those systems, the above command will create a true 10GB file. For example, if you are using Ubuntu and you have your home folder encrypted (ecryptfs), you can not have sparse files anywhere in your home tree.

The file will be created in the sources directory, because the buildiso script will need to be able to find the image.

The $(uname -m) part will automatically resolve to your host system CPU architecture (i686, x86_64, or something else), giving the image a name like rootfs-i686.img. Using $(uname -m) in these commands makes them suitable for copy-pasting on any machine.

Create a file system on the image

This command should work on any machine with a recent kernel: 

mkfs.ext4 -F sources/rootfs-$(uname -m).img

However, if you want to optimize for size at this stage (this does NOT affect the size of the final ISO image) and have btrfs available you could issue this one in stead: 

mkfs.btrfs sources/rootfs-$(uname -m).img

A compressed btrfs system image will take up about 500MB of space if you just install a basic LFS system on it, compared to 1.3GB for an uncompressed ext4 image.

Any file system for Linux should work just fine, and it does not even matter if the OS you will install in it has support for the file system you have selected. Later on, the image will be converted to SquashFS anyway.

Create temporary installation directories

mkdir -v install_root

And if you would like to keep the overhead of sources and tools directories out of the image (only affects the system image size, not the ISO size): 

mkdir -v install_overhead

Mount the system image

If you installed an ext4 fle system on the system image: 

mount -o loop sources/rootfs-$(uname -m).img install_root

Or if you used btrfs: 

mount -o loop,compress sources/rootfs-$(uname -m).img install_root

Install your system to the image

This installation command takes the form of ./lfscript [your_system_options] -i install_root -I install_overhead. If you did not create the overhead directory, leave out -I install_overhead.

For example: 

./lfscript -Bux fsos -i install_root -I install_overhead

Security

It is a bad idea to keep SSH keys on your Live CD, so remove them: 

rm -rvf install_root/etc/ssh/ssh_host_*_key

If you have installed OpenSSH (and the OpenSSH bootscript), these keys need to be regenerated using a custom boot script. If you are not installing fsos, take a look at the page 'FsOS_without_X11' for an example of the boot script.

Unmount the system image

umount install_root

Build the ISO image

./lfscript -Bux buildiso

The script that builds the ISO image could just as well be designed for use outside of LFScript (and in fact, with LFScript 3 it was). However, by executing BuildISO through LFScript the ISO is created by your own system, which removes the need to have the utilities required to run BuildISO (like SquashFS and cdrtools for example) installed on your host system. This reduces the risk of build failures considerably.

Once completed, your Live CD ISO image will be saved to your packages directory.

Cleanup

This command removes both the temporary installation directories, and the original system image which you probably don't need anymore: 

rm -rvf install_root install_overhead sources/rootfs-$(uname -m).img
Retrieved from "https://www.lfscript.org/w/index.php?title=Creating_a_Live_CD&oldid=1220"