And it’ll be segregated from the base system and from other containers, like toolbox installs are?
Exactly. It's even possible to segregate it beyond what Toolbx has been able to do (at least since the last time I checked) in that you can define another folder/directory as your HOME directory within the distrobox.
I likely would have encountered this as I try to take the approach of research, then do.
Props to you mate 👏 ! That's the way 😉 .
This is the first time I’ve ever posted for Linux help/or guidance.
Thankfully the community is very helpful in general, so you're in good company :blush: !
Searching forums has historically lead me to an answer close enough to resolve my not-so unique issue.
Yeah lol, we've all been there 🤣 .
A lot of negatives seem to come up around Oracle and Canonical being involved with SUSE and Ubuntu
Fedora also has connections to Red Hat, so yeah 😅. I didn't even know Oracle had anything going with SUSE before the recent 'alliance' of sorts in reaction to what Red Hat has done recently. Was that what you meant or has SUSE being working with Oracle for a longer time?
Yeah lol 🤣 . Consider reporting back after testing your findings. Thanks in advance!
I'm a simple man; I like to use GNOME so any terminal that feels at home on GNOME suits me. Currently, I've been in a phase in which I primarily use GNOME Console because of how GNOME Terminal doesn't play nice with tiling managers. Though Black Box is definitely tempting me.
The official manual page for xorriso is probably the best place to start. Unfortunately it mostly glosses over how it's compatible with mkisofs and doesn't further delve too much into what mkisofs does and thus how to engage with the -b flag. Fortunately, that information can be found on the related manual page for xorrisofs.
Please feel free to notify me if I can be of further help :blush: !
Is the guy who called everyone thieves if they didn’t donate enough before downloading still part of Elementary?
Assuming you're referring to this article; I don't know. Was it even ever revealed who the author was? Honestly I don't even think that it matters, as publicating the blogpost means that the team -at least to some degree- endorsed the idea.
It has been my pleasure! I'm curious on what you'll end up doing. So please consider to report back if it isn't too much to ask :blush: !
Good questions!
I assume getting a persistent environment in a USB recovery stick is a bigger task?
I actually don't know if penguins-eggs allows persistent environments 🤔 . Though, other tools might be better fit for the job. Personally I'd recommend you to follow this guide for openSUSE Leap. A similarly good guide/documentation for Debian is absent, and openSUSE Leap is likewise a good fit due to it being supported over a longer time period as well. The steps outlined in the guide might be a bit more involved, but the team behind openSUSE have done a wonderful job to ensure accessibility.
I’m imagining that, with your method, I would need to repeat this process any time I wanted to update the image or load specific new kernel modules/drivers?
With the method outlined in my previous comment, you only have to repeat the process from scratch if you didn't save the Debian install some way or another. If you did keep the Debian install around, then you could just; open it up, apply some updates/changes or (un)install additional packages and make yet another live image out of it. Granted, the openSUSE Leap persistent Live USB that has been previously mentioned in this comment is easier to change later down the line regardless.
Btw, -to my knowledge- the persistent Live USB environment is also possible on other distros like Debian, Fedora, Ubuntu etc. So arguably it's best to first look at which distro satisfies your needs in regards to package availability. After which, in my opinion, LTS/Stable releases ought to be preferred over the others.
First of all: thank you! The necessary info is there and it's written splendid. I think it or a future iteration should definitely be considered as a sticky post in the long run.
A few nitpicks which you may or may not agree with:
In the section in which you talk about update frequency, you end the paragraph with something along the lines of "new and stable". While this is correct technically, you should define what you mean with 'stable' here. Because there exist two (somewhat related) definitions for 'stable':
"(Certain) resistance to breaking" - which is used in the context of "stable rolling release" when one refers to something like openSUSE Tumbleweed. This definition does not necessarily oppose new.
"Release model in which packages are frozen over a long(er) period of time and primarily only continue to receive security updates" - which is e.g. used in the name of the "Debian Stable" distro. This definition does oppose new.
In the section about desktop environments you mentioned something along the lines that Fedora defaults to GNOME. This applies only to their Workstation and Silverblue distros. For which both other "Spins" exist, which happens to be the recommended method of installing another desktop environment on Fedora; similar to how "Flavors" work for something like Ubuntu. While one can technically install it like how you've mentioned it, I wouldn't recommend it to a newer user.
Not sure if one would call this support, but technically Davinci Resolve can be installed as a flatpak.
Glad to be of help 💙 ! Feel free to inquire if you so desire 😉 .