Posts: 3
robert-m64
Joined: 23 Jun 2017
#1
Hi, I am using antiX to setup a forensics platform for tree identification (to detect illegally traded wood). Previously, I used Puppy/Fatdog distros as base system (I am also the developer of MASSyPup(64),
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://peerj.com/articles/1401/"
linktext was:"https://peerj.com/articles/1401/"
====================================
,
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.bioprocess.org/massypup"
linktext was:"http://www.bioprocess.org/massypup"
====================================
)

Unfortunately, the live-usb-maker fails (because of the automounting of the USB after creating the 1st partition):

/dev/sdb1 is mounted; will not make a filesystem here!
Error: Could not make ext4 file system on /dev/sdb1. Perhaps try --force=makefs

Well, I tried the --force switches (not all of them work!), also the actual git version of the live-usb-maker and the GUI. Also a different USB stick.

Is there any (easy) way to create an ISO from the running system? This would be anyway the best solution, also for redistribution of the remastered system (data integrity of the exchanged system is an issue).

Thanks, Robert
Posts: 1,445
skidoo
Joined: 09 Feb 2012
#2
Unfortunately, the live-usb-maker fails (because of the automounting of the USB after creating the 1st partition).
Is there any (easy) way to create an ISO from the running system?).
Before launching live-usb-maker, ensure spaceFM isn't running.
(Because, unless you've tweaked the spacefm config, it (spaceFM+udevil) is probably automagically remounting the partition.)

It would be helpful if live-usb-maker checked `pidof spacefm` and warned/explained this,
but I guess we're expected to apply the"common sense" tenet of"before, proceeding, close all running programs".

The persist-save should probably perform a similar check/warning.
Firefox, in particular, if it's running when persist-save occurs... at next launch ff will likely complain"Your last session crashed!"


edit:

In case you didn't use the bootscreen F4 nomount option,
during a desktop session you can visit ControlCenter --} Disks --}"Configure Automounting"
to change the (auto)mounting behavior.