Bugzilla – Bug 1220301
[Enhancement] Installation of another occurence of Tumbleweed, totally independent
Last modified: 2024-03-01 01:18:09 UTC
It would be a good thing to get the ability to install another occurrence of Tumbleweed totally independent. When I say totally independent, I mean : - on its own disk - with its own swap - its own /home - its own UEFI Today it is possible to do that, but we need : - to disconnect the disk of the first occurrence of Tumbleweed - insert a card with the ISO - go to the bios to select the card to boot with it - boot the PC - install Tumbleweed - in the two OS, uncheck, in the boot settings, the parameter "Update NVRAM Entry" Today with NVMe SSD it is more complicate because : - the nvme ssd is screwed and in my case under the big CPU radiator. I must unmount the radiator to access to the SSD of the first OS. Thus, I can't disconnect it. - I must ignore what the installer want to do (installation on the disk of the first OS) - I must indicate to the installer what disk to use - I must know the good size to use for / and swap - It is very techie - You do this with the fear to erase the disk of the first OS I want an installation as easy as a dual OS installation. We need a choice to make a dual OS installation on the same disk or on another disk. The reason why : I need a very high reliability. Thanks
This is possible even now, and has been possible since YaST exists (i.e. since late 1999). Probably the standard storage proposal won't do that for you since it's a very nonstandard setup. It will work for sure with the expert partitioner, and maybe also with the guided storage setup (but I haven't tried that). It's very simple to create the necessary partitions, including the root partition, a swap partition that is not shared with any other OS on that machine, your separate /home, and whatever else you might want. What's the problem with that? I don't know what you mean with "its own UEFI"; do you mean the ESP (Efi System Partition)? AFAIK there can be only one on a machine, and that is defined by the EFI standard; this is where the EFI bootloader lets you select what OS to boot. You can't have more than one of them. As a YaST developer since 10/1999 I have constantly been installing multiple instances of SUSE Linux, Ubuntu, Windows and whatever in parallel on the same machine; on one disk, on multiple disks, in all kinds of permutations. I am doing this on a regular basis, and I have done that with at least a dozen machines over time. So, what exactly is it that you are missing? What makes you think you have to physically disconnect any disks to achieve this? I think you are making this artificially overcomplicated; you might be overthinking the problem. Maybe take a step back and simply try again without confusing yourself.
And BTW if you need high reliability, the first thing to do is not rely on one single machine. Hardware can break, and humans make mistakes. If you need a rock-solid setup, better have at least one machine on standby. If you only have one, that machine becomes a single point of failure, and the reason for that failure is more often than not the human operator, i.e. yourself.
No feedback.
I have 6 PCs with two separate 64bit TW installations, and 4 with two or three separate 32bit TW installations. All 10 have at least 10 separate Gnu/Linux installations (with openSUSE the most common and most used), such as with Slowroll and/or Leap in addition to TW. The openSUSE installer is clearly the best I've ever encountered.