Another change I think we need to consider for eggs is to make the initrd, grub etc stuff generate itself separate to the user data set with : sudo eggs dad
Reason is I don't want to pause my automated build script to set a new Name every single time, but I use eggs dad to make the initrd etc set correctly.
I think we need
sudo eggs dad - keep same for backwards compatibility
'sudo eggs dad --kernel` - using this switch will do the equivalent to the -n does for other commands/tools. It will use the default or pre set user files and generate the correct working boot settings for the other file (if you don't want 2 files you could simply update the existing eggs.yaml keeping the user data in tact, I just thought 2 files may be better for the purpose).
eggs.yaml: (As it currently is)
compression: xz
force_installer: true
initrd_img: /boot/initrd.img-5.15.0-91-generic
machine_id: 15fdb9313a8141b9aa1c50ce20c37e83
make_efi: true
make_isohybrid: true
make_md5sum: false
pmount_fixed: false
root_passwd: live
snapshot_basename: Linux
snapshot_dir: /home/eggs/
snapshot_excludes: /etc/penguins-eggs.d/exclude.list
snapshot_mnt: /home/eggs/.mnt/
snapshot_prefix: LastOS
ssh_pass: false
timezone: Europe/Rome
user_opt: live
user_opt_passwd: live
version: 10.0.8
vmlinuz: /boot/vmlinuz-5.15.0-91-generic
As the user only gets asked a few choices, they get stored and then all the automatic stuff
(New method I propose below, and maybe use 2 files to separate if easier/possible, so I can overlay my user data without having to run the manual options each time).
eggs_user.yaml
compression: xz
force_installer: true
make_efi: true
make_isohybrid: true
make_md5sum: false
pmount_fixed: false
root_passwd: live
snapshot_basename: Linux
snapshot_dir: /home/eggs/
snapshot_excludes: /etc/penguins-eggs.d/exclude.list
snapshot_mnt: /home/eggs/.mnt/
snapshot_prefix: LastOS
ssh_pass: false
timezone: Europe/Rome
user_opt: live
user_opt_passwd: live: live
snapshot_basename: Linux
snapshot_prefix: LastOS
user_opt: live
user_opt_passwd: live
(This stuff below generates itself, so why is it in the user data that I want to provide a constant name and password for?)
eggs_kernel.yaml:
initrd_img: /boot/initrd.img-5.15.0-91-generic
machine_id: 15fdb9313a8141b9aa1c50ce20c37e83
version: 10.0.8
vmlinuz: /boot/vmlinuz-5.15.0-91-generic
pieroproietti
commented
1 month ago
Another change I think we need to consider for eggs is to make the initrd, grub etc stuff generate itself separate to the user data set with :
sudo eggs dadReason is I don't want to pause my automated build script to set a new Name every single time, but I use eggs dad to make the initrd etc set correctly.
I think we need
sudo eggs dad- keep same for backwards compatibility'sudo eggs dad --kernel` - using this switch will do the equivalent to the -n does for other commands/tools. It will use the default or pre set user files and generate the correct working boot settings for the other file (if you don't want 2 files you could simply update the existing eggs.yaml keeping the user data in tact, I just thought 2 files may be better for the purpose). eggs.yaml: (As it currently is)