Skip to content

Commit

Permalink
Merge pull request #3 from LumIT-Labs/develop
Browse files Browse the repository at this point in the history
A different incipit
  • Loading branch information
lumitlabs committed Oct 29, 2018
2 parents 25a4028 + 7884ca7 commit 2cbee79
Show file tree
Hide file tree
Showing 2 changed files with 18 additions and 17 deletions.
15 changes: 3 additions & 12 deletions README.md
Expand Up @@ -4,21 +4,12 @@ Next Generation Linux live distributions concepts

A live operating system allows booting from a removable medium, such a USB key, without the need of being installed to the hard drive.

Once written onto a USB key, a common live operating system is usually made up of one ISO9660 partition, containing the kernel, the initrd, the compressed filesystem.squashfs image and the second stage bootloader, usually *isolinux* (the boot sector code linking the second stage bootloader is contained within the MBR of the key). Modern lives also add a UEFI partition.
None of the existing live operating systems provide a kernel update feature: the kernel and the initrd are the only components that a live operating system cannot update, because they lay outside of the data persistence partition (if any) and usually the system partition is ISO9660-formatted. This will soon lead to an outdated operating system, particularly unsafe if used as a desktop-replacement or for security-critical activities.

If you need a live system which does data persistence, you will find another partition, usually an EXT4 one. This is pretty common as well.

There are a few live distibutions which support the UEFI Secure Boot (Debian lives do not), but no distribution is capable of updating the kernel maintaining a ISO9660 filesystem, which is the best option for a live.

The aim of the liveng project is to give the Community a set of best practices in order to transform a common Debian Linux live into a live(ng) operating system which does:
The aim of the liveng project is to give the Community a set of best practices in order to turn a common (Debian Stretch) Linux live into a live(ng) operating system which features:

* native encrypted persistence;
* kernel update (on a live ISO 9660 filesystem!);
* UEFI, with UEFI Secure Boot compatibility, with a real efi partition.

As the base of liveng we have chosen the Debian Stretch live distribution.

This Github repository hosts:

* source documentation files for Read the Docs, see https://liveng.readthedocs.io;
* a set of proof-of-concepts scripts.
This Github repository hosts all the source documentation files for Read the Docs, see https://liveng.readthedocs.io.
20 changes: 15 additions & 5 deletions docs/source/index.rst
Expand Up @@ -5,17 +5,27 @@ liveng

A live operating system allows booting from a removable medium, such a USB key, without the need of being installed to the hard drive.

Once written onto a USB key, a common live operating system is usually made up of one ISO9660 partition, containing the kernel, the initrd, the compressed filesystem.squashfs image and the second stage bootloader, usually *isolinux* (the boot sector code linking the second stage bootloader is contained within the MBR of the key). Modern lives also add a UEFI partition (some add a "fake" one).

Why liveng
^^^^^^^^^^

None of the existing live operating systems provide a **kernel update feature**: the kernel and the initrd are the only components that a live operating system cannot update, because they lay outside of the data persistence partition (if any) and usually the system partition is ISO9660-formatted. This will soon lead to an outdated operating system, particularly unsafe if used as a desktop-replacement or for security-critical activities.


More features
^^^^^^^^^^^^^

Once written onto a USB key, a common live operating system is usually made up of one ISO9660 partition, containing the kernel, the initrd, the compressed filesystem.squashfs image and the second stage bootloader, usually *isolinux* (the boot sector code linking the second stage bootloader is contained within the MBR of the key). Modern lives also add a UEFI partition (some add a "fake" one).

If you need a live system which does data persistence, you will find (or need to create) another partition, usually an EXT4 one. This is pretty common as well.

There are a few live distibutions which support the UEFI Secure Boot (Debian lives do not), but no distribution is capable of updating the kernel maintaining a ISO9660 filesystem, which is the best option for a live.
There are only a few live distibutions which support the UEFI Secure Boot (Debian lives do not), and, as stated before, no distribution is capable of updating the kernel maintaining a ISO9660 filesystem, which is the best option for a live.

The aim of the liveng project is to give the Community a set of best practices in order to transform a common Debian Linux live into a live(ng) operating system which does:
The full aim of the liveng project is to give the Community a set of best practices in order to turn a common Debian Linux live into a live(ng) operating system which features:

* native encrypted persistence;
* native **encrypted persistence**;
* kernel update (on a live ISO 9660 filesystem!);
* UEFI, with UEFI Secure Boot compatibility, with a real efi partition.
* UEFI, with **UEFI Secure Boot compatibility**, with a real efi partition.

As the base of liveng we have chosen the Debian Stretch live distribution.

Expand Down

0 comments on commit 2cbee79

Please sign in to comment.