Currently I am using SystemRescueCD on USB flash drive as a live distribution. This has certain limitations like, if I want to install additional packages I have do a work around. If I want to have the latest kernel then also I need to jump through loops.

So has anyone installed SystemRescueCD on their drive permanently? It maybe a removable external drive, that also would be fine. Are you able to update the packages and install new ones too? What about Kernel releases. How do you manage that?

Any help, suggestion and comments would be welcome.

systemrescuecd is used to rescue, nothing more. There is no need to update anything on it, if it works.
Otherwise here is the official documentation: https://www.system-rescue.org/manual...e_on_the_disk/

I agree that SystemRescue is a toolkit and not a regular distribution. If you write it to a USB drive using rufus or the systemrescue usb writer you can create a writeable filesystem and therefore install programs using pacman. The SystemRescue website as posted above has information on how to install it to a hard drive and how to make custom versions. I don't necessarily need or want to constantly keep it updated due to the fact that changes could break it and not what you want when you need to rescue a broken system.

Consider installing SystemRescueCD on your removable disk using Rufus or dd for Linux. After installation, use `system-install` and `pacman` for package updates and kernel upgrades. Ensure persistence for saved changes. It's a solid setup for managing updates and installing new packages efficiently. I had a tight deadline and needed help with my research paper, so I decided to try https://domypaper.com/ The writer delivered a high-quality paper that was well-researched and well-written. The customer support was very responsive and helpful, throughout the process. I'm very satisfied with the service and would recommend it to anyone in need of academic assistance.

I have taken live images and used them as full installs.

I started by reading a Knoppix article where Klaus said how he'd do it. Basically a bootable image has been built originally from a real install. The trick is to get it back to that state. Some live use a compresses file that contains a filesystem within it. The compression method and version has to be known to reverse it. Usually not hard.

Oh? Which one helped you?? Anything in particular??