Chroot Rescue & Installer


Q: Why CRI doesn't like systemd?
A: Because systemd is just big and overcomplicated replacement of well known and rock solid Linux utilities. It introduces some radical changes, tries to do too much (with various results), can easily take your system down or prevent it from booting etc. It is simply too unpredictable and too unstable to use on production systems and brings no real benefits for experienced sysadmins.

Q: Will CRI offer live rescue systems based on other Linux distributions?
A: It is very unlikely that other distributions will be supported.

Q: What systems can be installed using CRI?
A: TLD Linux, Debian, Devuan and Ubuntu Server LTS. Ubuntu can be installed only via direct network install. Other distributions can be installed using both, preconfigured chroots and direct network install.

Q: Software I need is not available in live rescue. Can I install it somehow?
A: Please configure and start network and then use poldek (TLD Linux package manager) to install desired packages. Keep in mind that rescue systems are working in RAM. If you'll fill rescue filesystem you'll also fill your RAM and rescue system will crash badly.

Q: How the hell can I install something using this poldek stuff?
A: Simply type poldek -i some-package

Q: Can I make bootable USB disk with CRI?
A: You just need to install GRUB2 on your USB disk and copy contents of CRI disk to it. To install GRUB2 run following command: grub-install --force --no-floppy --boot-directory=/mnt/usb/boot /dev/sdX where /mnt/usb is directory at which your USB disk is mounted and /dev/sdX is device name assigned to your USB disk.

Q: Can I personalize / modify CRI for my needs?
A: No. CRI developement environment is not and will not be publicly available.


If you have any bug reports, requests or questions feel free to mail me: hawk (at) tld-linux (dot) org