Question re: snapshottool

[gurtid]

I'm wanting to take a snapshot of my installed 'proof' to install on another computer. I have separate / and /home partitions.

Is it possible to do this from a single .iso image created using the snapshot tool?

The instructions in the cookbook only give details on how to 'snapshot' a single partition.

How does one make a snapshot and specify more than one partiton? (i guess i just edit the configs a bit . . . ?)

Can I make a full snapshot (i.e. / and /home) from within my running 'proof' system?

P.S. Apologies in advance - i normally should/would just trial and error this , but I'm being lazy.

[machinebacon]

Well, then I'm lazy to answer ;)

I haven't tried it yet but I strongly suppose it just works. Do this:

- sudo bbqsnapshot
- in a new terminal, enter: sudo ncdu /home/work/
- wait until the snapshot tool pauses
- in the other terminal, navigate through the folders. What you see there is the structure of what is going to be installed. Your "real /home" is now in the folder "/home/work/myfs/home/"

If you are unhappy with it, simply Ctrl-C the other terminal and remove the cruft in /home/work via a filemanager (as root) and report back.

[gurtid]

:D i knew i should have just stfu and experimented . . . ;)

[gurtid]

You are right mb - it did just work. Of course there's no need to specify more than / . . . don't know wot i was thinking. :D

Anyways - have created on iso of my 'proof'. I'm running systemd on this one. The iso falls to boot complaining about systemd stuff but anyways . . . something to play around with over the next few days @ work :X .

[machinebacon]

Easy fix:

Boot the stick, in the boot menu press [Tab], remove init=/bin/systemd , then hit [Enter]
Install as usually, then edit /etc/default/grub and check that there is no init=/bin/systemd anywhere

[gurtid]

oh - tu. Was pressing 'e' which didn't work :D

[gurtid]

she squeals about

sysv

with the

systemd

stuff removed.

will

arse

around with creating moer isos . . .

[machinebacon]

then keep the systemd in, so revert. when you boot up again, with systemd, run

systemd-analyze blame

and post the output here. If the boot hangs, wait up to 5 minutes - might happen.

[gurtid]

OK - so starting again . . . :)

. . . fresh install of Proof. Made a few changes - theme , wallpaper and that's about it i think. Snapshoted and dded to stick.

Will not boot - complains about lack of systemd (proof never came with systemd) and kernel panic. Can only hard reboot.

Has anyone snapshoted a proof system and put it on stick successfully?

[machinebacon]

The solution is simple:

1) in GRUB enter the kernel boot line (press 'e') and remove the init=/bin/systemd , then hit F10 or Ctrl-x

2a) if you want systemd, install the packages: systemd libpam-systemd live-config-systemd
2b) edit as root: /etc/default/grub and make sure you have the entry GRUB_CMDLINE_LINUX_DEFAULT="quiet init=/bin/systemd" in line 9
2c) save and exit, then run update-grub

3) if you want to stay with sysvinit, edit as root: /etc/default/grub and remove any traces of init=/bin/systemd (line 9) and save/exit. Then run update-grub again.

Edit: If you want I can create a systemd-Proof and upload it ths weekend. Though it's really just a matter of installing/removing those 3 packages and changing the default GRUB line

[gurtid]

It worked MB. :) thank you.

Coupla questions tho' . . . why did it add systemd to the kernel boot line anyway since proof doesn't come with systemd?

Why did my snapshot from the other day not work (i had installed systemd on that system)?

Thank you for the offer but systemd proof is not required. It's easy to add as you suggested.

[machinebacon]

I originally uploaded the spin to test Liquorix and make sure that systemd doesn't interfer with the live boot. So, systemd was disabled and sysvinit chosen as default. If a snapshot is being made by the user, he/she should decide upon which init system he/she wants to use and change the things accordingly. The live boot however stays sysV, because it uses a different package (live-config-systemd vs live-config-sysvinit). The /etc/default/grub is set to systemd because it was meant to be the standard for the BBQ. Of course I should/could have removed the entry there, and then leave it to the user if he wants to use systemd or sysvinit. So, my fault, apologies :D

[gurtid]

All good MB. I have no problems with it as it is, now that i understand the reason. Thanks for your patience :)

[machinebacon]

Anytime, I'm happy if people try, use and create snapshots, that's what it is for, and it was indeed unclear for Proof.