Consequently, does OpenSUSE support dynamically resizing the live system drive in order to transfer the SWAP partition to it? It seems like it would be a complex process, but I don’t know of any reason why it would be fundamentally impossible. If I should use a live image for this, that’s not problematic.
@rokejulianlockhart just create the swap partition on the device and size you want, add it to the mix, turn off swap, delete the old swap partition and turn swap on again. It’s dynamic, likewise with a swapfile or the likes of zram.
Define “drive” and “primary”. The straightforward interpretation - hard disk drive (HDD) or solid state drive (SSD). How are you going to resize hardware when booted?
If you mean filesystem or partition - it depends on which filesystem exactly and on partition layout. And it has nothing to do with “OpenSUSE” (which is “openSUSE” by the way) because it is the same in any other distribution.
@rokejulianlockhart then you the installer person, set it where you want it to be, by creating and setting it as swap… guided is best guess, use existing partitions or none and then create as required.
I’m not competent enough for that. I can use a commandline for script kiddy tasks, but I’m no software dev yet - I’m a GUI guy unless I know I’m doing.
@rokejulianlockhart Maybe it would, on my installs I usually just pre-partition what I want and tell it to use existing partitions and move on from that, especially if dual boot.
Maybe Tumbleweed is not for you then if not wanting to extend your command line skills?
I think it is, because it’s not like this makes sense - a drive shouldn’t ever be touched unless the user explicitly allows it. I’ve no issue with using the commandline, I just don’t want to be forced to do everything via it because the GUIs are broken, else I’d use Arch.
@rokejulianlockhart It is correct, it will select an existing partition (nvmen1p3) that is already created as swap, it won’t try and create another (perhaps if encryption is used?).
Go change the type of that already existing swap partition(s) to type 8300 temporarily and will create on on the selected drive.
As explained in your bug report, guided tries it’s best, use the expert partitioner for multiple disks/partitions.
The installer offers GUI-based “Expert Partitioner”. I use it since several years and only create what is needed:
erlangen:~ # fdisk -l -o device,size,type /dev/nvme1n1
...
Disk model: Samsung SSD 970 EVO Plus 2TB
...
Device Size Type
/dev/nvme1n1p1 512M EFI System
/dev/nvme1n1p2 1.8T Linux filesystem
erlangen:~ #
Yeah, I’ll make sure to delete unwanted SWAPs on secondary internal drives during my next installation, and if I forget, I’ll see whether I can easily wipe a partition using Expert and combine it with Guided subsequently.
I’m only referring to when I inevitably have to reinstall. There’s no need to keep around SWAP partitions during that, right? However, I’m gonna play around with things like what you suggest in a VM since someone at Bugzilla sensibly suggested that.
Swap has advantages and is required for stuff like hibernation, suspend and so on. Most people don‘t follow Karls advice as he has some out of world setups that are not feasable for normal and power users. And his opinion that „ dealing with swap is a hassle“ is FUD and not backed by facts.
@hui on Tumbleweed and MicroOS that has/is changed… kernel lockdown and secure boot == no hibernate, suspend to RAM (probably), containers… Times they are a changing…