Hey Scott, On Sat, Feb 08, 2020 at 02:53:41AM +0000, scott092...@aol.com wrote: >>I'm wondering exactly what the effect of "with persistence" is, for example. > >Persistence is a very useful feature, whereby a certain amount of storage is >reserved >on the media that is used when a change is made from the .iso , so that when >it is again >booted, that change is still there.
Oh, sorry. I wasn't clear enough. I know what persistence *is*, I was more wondering exactly how mkusb modifies an image to *enable* persistence. If it's blindly modifying the filesystems included in an image, that could cause all kinds of problems. :-/ ... >>Could you try again without that and see if that makes a difference for you, >>please? >Yes... well... booting the live-usb without persistence solved the problem. > >I can only speculate, that Calamares (or something Calamares calls) refers to >/run/live/medium/live/filesystem.squashfs >two different ways in two (or more) different locations of the code. >Without persistence, the two ways point to the same place, and all is good. >With persistence, the two ways point to two different places, and it fails. I'm thinking that it's more likely that mkusb is doing something odd to the image, I'll be honest. I don't have time to dig into it right now (prepping the latest buster point release this weekend!), but AFAICS it's a tool written to work primarily with Ubuntu images? Ubuntu and Debian live images are really quite different beasts and it *may* be making invalid assumptions about how live images work. -- Steve McIntyre, Cambridge, UK. st...@einval.com "Further comment on how I feel about IBM will appear once I've worked out whether they're being malicious or incompetent. Capital letters are forecast." Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html
