I created a LiveCD with the cli version. i used remastersys dist. When I run the iso, however, it fails to umount the medium, fails with bluetooth, fails loading the snap daemon, and basically completely fails. I did not choose the Fail-Safe option, but rather the live option.

The refreshing of the initramfs is not working on a livesystem remastered with remastersys-gui 4.8/4.9 after install and has to be repaired.

Giving the error code of " missing Command" while initramfs-tools are installed.
Is this just on my machine or reproducable!?

Tested with:

• Remastersys 4.3 and 4.4
• Linux Mint 21.1 Cinnamon
• LightDM display manager (default manager in Cinnamon)

Login is not working in backup mode when using LightDM display manager. But does work with Gnome's gdm3 (not tested with KDE). I don't know why but, since version 4.4 fixed a similar issue with Dist mode there should be some relation.

Related to Issue #5 (closed).

ADDENDUM 1:

• gdm3 login works in backup mode, BUT home folder doesn't load.
• Need to test with DEBIAN 11.6, because Linux Mint IS NOT DEBIAN.

ADDENDUM 2:

• package 4.4-1 created in Linux Mint can not be installed on DEBIAN: unknown compression for element control.tar.zst.

ADDENDUM 3: package 4.4-2 created in Debian 11.6. It is now installable on Debian.

• Tested LightDM in backup mode: doesn't login.
• Tested gdm3 in backup mode: login works, BUT home folder doesn't load, impossible to open nautilus.
• Tested gdm3 in dist mode: everything works without issues.

If i use remastersys in backup-mode and install the new system from the livesystem-image, there will be given the username and password given from the livesystem, doesn't matters which name and pw i gave in the install process!

Btw: never tried the remastersys installer while we use the default ubiquity-gtk that all Debian based systems used to install their systems.

Is it possible to use the backup-mode and if i give a different/new username and pw during install process, it will be taken?

Easier: is this a problem of our customizations and skel inputs or is it normal in backup mode, that only the first given username in the remastered system is used?

What can i modify to get a new fresh install from remastered livesystem with a new username WITHOUT using distro mode??

Hi, first of all: thx for the latest update, autologin is now working on debian :))

But now I faced the next issue. The installer doesn't work, not with gui or terminal. With gui from start menu, nothing happens. When using sudo remastersys install only the help text appears

Checking if the /home/remastersys folder has already been created.

Copying /var and /etc to temporary area and deleting extra files.



Setting up Live CD options for mode backup.
update-initramfs: Generating /boot/initrd.img-5.4.0-165-generic
live-boot: core filesystems devices utils memdisk udev blockdev iscsi dns.

Copying your kernel and initrd to the Live CD.

Creating filesystem.squashfs. It will take a while, so be patient...

Parallel mksquashfs: Using 4 processors
Creating 4.0 filesystem on /home/remastersys/ISOTMP/live/filesystem.squashfs, block size 1048576.
[=================================================/                                                         ] 191627/413782  46%
real	12m44.480s
user	30m27.355s
sys	2m37.102s
cat: /etc/X11/default-display-manager: No such file or directory
The CD file system is missing. Either there was a problem creating the compressed file system, or you are trying to run the command "remastersys dist iso" before "remastersys dist cdfs".

The above log is generated by running the remastersys backup command, I made sure that I got the server without the GUI installed, but the log contains "cat: /etc/X11/default-display-manager: No such file or directory ", I'm not sure if it's my operation or the app itself.I'd appreciate it if you could confirm that for me.

I'm using PeppermintOS based on latest Devuan. After burning iso with remastersys 4.3 I can't login. Password is not accepted and auto login doesn't work.

EDIT: This only happens when using backup. Using 'distro' the user 'Peppermint Live User' is working without adding a PW.
But I need the backup function to get all my personal changes included in live cd

EDIT: I have learned, that the issue is the LightDM. With Gnome autologin is working for backup iso and also for dist iso

I try to build an image in backup-mode with more than 4GB! Everything was fine during mastering but after all there is no .ISO and an error in the log about too large files over 4GB and missing parameters!

Could you help, please!?

Remastersys 4.8.1, Linux Mint 21.1, Mate, 64bit

please seeerror message:

leos@LeOS-Linux:~/Downloads$ sudo dpkg -i remastersys_4.4-1_all.deb
[sudo] Password for leos:
dpkg-deb: error: archive "remastersys_4.4-1_all.deb" uses unknown compression for element "control.tar.zst", abort
dpkg: Error while processing archive remastersys_4.4-1_all.deb (--install):
"dpkg-deb --control" subprocess returned error value 2
Errors occurred while editing
remastersys_4.4-1_all.deb

Here we are again..

What is the reason that all efi-files are missing in livesystem?

Did with remastersys 4.9, isolinux on a NON UEFI pure BIOS-based system.

Should i remaster on an UEFI based Computer to get both working in livesystem: UEFI and BIOS-based installs

OR

Should i use GRUB as option to rebuild to get UEFI working??

So there is nothing wrong with the liveimage, just that is to install in CSM/BIOS-mode and NOT supporting EFI...:()

Hello
Help me please.

I am trying to create a LIVE image, so that then it would be installed on a computer. However, I have a problem with the preserved user settings. Maybe I'm doing something wrong?

If without user settings, then LIVE works and you can install the system on the disk from this LIVE.

I work for Debian 12, maybe this is the reason?

I was working on patching remastersys to allow to boot EFI systems, I think this would fix the fact only MBR boot is possible last I checked, but I'm not sure if you fixed it already or are planning on doing so.

Resolv.conf is missing in remastered system after install. DNS/Internetconnection is broken through this.

I am using Linux Mint 21.1 MATE, remastersys 4.9, dist-mode

Internetconnection was working before remastering and resolv.conf there..

When doing an iso restore, I noticed that it was not booting correctly through UEFI (including when I actually tested it), but I solved the problem manually, which may help you a bit

1. Create UFI partition : fdisk /dev/sdb (n 1 enter +512M t [EFI System] w)
2. sudo apt-get install dosfstools
3. format it: sudo mkfs.fat -F32 /dev/sdb1
4. mount: sudo mount /dev/sdb1 /boot/efi
5. sudo grub-install /dev/sdb --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB
6. echo "/dev/sdb1 /boot/efi vfat defaults 0 1" | sudo tee -a /etc/fstab

PS: /dev/sdb is boot system disk

There may be times when this boot is not shown in the bios, you can try add the boot option

DELL BIOS Examples

I noticed that not all files copied in /etc/remastersys - version4.9!

E.g. grub.cfg and others.

Triggers remastersys to give error messages and ends in a broken liveimage!?

Is this just on my machine or on others too?

Thanks for your work!

Before using this repo, is it necessary to do the steps informed in the original Remastersys website? For example, for a Debian system:

There are some pre-requisites for the debian version that aren't there for the Ubuntu version.

You should install squashfs-modules for your kernel and either aufs-modules or unionfs-modules before you install remastersys. On initial testing from a net-inst lenny cd I had not installed these prior and something very bad happened to my install - it was unable to boot and the livecd created was also unusable. I feel it had something to do with building the initramfs. As another safeguard, its recommended to reboot your system after the modules are installed just to ensure it boots properly. If all that goes well, you are fully prepared to install and run remastersys for debian.

If your kernel doesn't have the squashfs-modules and either the aufs-modules or unionfs-modules, you MUST use a different kernel. No ifs ands or buts about it.

I also find confusing in how to run/install this, as the README.me does not mention it. The running commands on the original Remastersys were (at least in debian):

"remastersys backup" as root to make a full system backup, or "remastersys dist" again as root, to make a distributable copy to share with friends.

Should remastersys be run under usr/bin in remastersys/usr/bin? Or rather be installed WITH this repo (and how)?

I figured I'd try this on MX Linux as it seems to provide more options for customization than MX Snapshot.

However, when creating the distribution, all it seems to do is completely fill up space on my SSD. I was down to 0GB of space. Had to clear and try again. I did that, and it was just doing the same thing.

This doesn't seem to work so well.

when I just wait for it to load by itself it does not go through an installation process. it just automatically installs like bam. no setup screen just like as if you had it for years and you are signing in again. Weird, because the maintaner said this is not supposed to happen.

label with bug

Discussed in #19

Now, I got it to work. However, I do not know the password. On the VM I made it on, the password is xyz (not actual password but a placeholder) but xyz is not the password of the system. This is driving me nuts. I really want to see it working! Yes, it boots and this is the log: droptext.cc/w9tps

Trying to run the iso on my Mac using UTM (a VM system), because my other laptop does not have enough storage.

hi, I've found options for packaging images larger than 4g, perhaps we could use the cdrtools toolkit as a dependency, which provides an enhanced version of mkisofs, (supporting ISO9660 v 2) that would seamlessly replace the old mkisofs

PS:
https://downloads.sourceforge.net/cdrtools/

I have a patch that I worked on to remove the 4 GB limit so you can build a pendrive bootable version. It's a lot more useful to revive the "Backup" option.

If you're interested I could submit a PR