Although that windows 7 is 100% legal, I doubt I can install it on the new pc.
I don’t mind if I can’t use windows any more or might have to look for win 10.
The think I do want is again a dual boot pc.
Why I love dual boot is simple, if you mess up one OS, you still can use the other one to go online. ( I only have one pc )
Now my Questions.
What are my options ?
leap and thumble weed ?
leap 42.3 and leap 15 ?
Leap 15 is gonna to be the main os.
Maybe Arch as back up os ?
If I get that running I might actual learn about Linux.
Second Question.
My current mobo does not have uefi, should I expect trouble installing leap 15 ? Or are those issues resolved by now ?
I remember reading about issues with Linux, when uefi came alive. ( years ago now )
Hi, multibooting here since… don’t remember lol!
Second question first: the openSUSE install media can boot in UEFI mode or MBR/Legacy mode depending on the firmware in the target system, so either way you should be safe.
I usually have a “daily workhorse” installed on a large root partition as my main, stable OS (currently Leap 15.0, will be 15.1 in a matter of weeks).
Then I have a couple of “test” OSs, usually beta releases or minimal installs of other Linuxes I like to play with, including Tumbleweed occasionally.
I don’t remember messing up my “main” install in years, while the others are there to play, like sandboxes, and might be wiped and reinstalled occasionally.
Please be aware that if you do a default install of openSUSE on BTRFS on a partition larger than 50 GB, you will get snapshots as a bonus, so you can revert the system to a previous state in case of trouble.
As to what kind of “secondary” OS to choose, that depends on you. Arch is a good playground to learn, test, break things (often) and get good docs in their wiki.
Tumbleweed is a good option to test bleeding edge technology (that occasionally breaks) and get good support here…
And if you still need Win* for the occasional bank site that only understands Redmond dialects, I would install one in a virtual machine, not as a “backup” OS…
Anyway, as always with Linux, it’s your system… and your choice.
Have fun.
Like Aliens vs Predator 2 ( current pc is now 9 years old )
I do have some other Alien games, that need windows to run.
Also have Alien Isolation, but that one runs on Linux , like F1 2017, but my phenom II X4 cant run it, its missing an instruction set.
My new Ryzen 5 should fix that.
Might be worth to have a look at the specific games and play on Linux.
If it was not for games, there would no windows on my pc.
Going a bit of topic, I am not amused the new Doom does not have a Linux version.
I did find a video though, of somebody running it on ubunto with vulkan, so there might be hope there.
Hi
From my experience you should be fine using the win 7 key, why run 32 bit, the key will work for 64bit. Once win 7 installed and activated, then download the win X iso image from MS, mount the iso image under windows and run the setup program to upgrade.
What is your disk setup going to be?
If UEFI, pre define via a USB rescue of live image, I would suggest the following for one disk;
Use gdisk for;
sda1 - 260MB type ef00 (for win and openSUSE boot)
sda2 - 16MB type 0c01 (for win)
sda3 - 40 GB type 8300 for /
sda4 - XGB type 8300 for /home
sda5 - XGB type 0700 for windows
sda6 - XGB type 8200 for swap (1.5 times ram or don’t suspend can be reduced to minimal I run ~1GB])
Limited only by your imagination. Multiboot is as much art as science. I’ve been doing it more than 25 years, with more than 20 multiboot PCs for some definition of “current” working and kept current. Average number of installations per PC is well in excess of 10, with two having more than 40 and others with more than 30.
leap and thumble weed ?
leap 42.3 and leap 15 ?
Leap 15 is gonna to be the main os.
All doable.
My current mobo does not have uefi, should I expect trouble installing leap 15 ? Or are those issues resolved by now ?
I remember reading about issues with Linux, when uefi came alive. ( years ago now )
Some hardware imposes obstacles, but only on the newest hardware are they insurmountable, and then only for a period of time until the developers get the software caught up to it. Any hardware a year or more older than the OS release should be well enough supported to expect no serious trouble.
I recommend you choose to use UEFI if it is available. The boot process for BIOS/MBR booting is quite different from using UEFI. UEFI facilitates multiboot.
If using multiboot with multiple installations of same name, such as TW and Leap, the first thing to do after the first OS is installed is to customize the line GRUB_DISTRIBUTOR= in /etc/default/grub so that it does not say opensuse. On my TW it reads opensusetw. On my 15.0 it reads opensuse150. On my 15.1 is reads opensuse151. By default it reads opensuse, so a second installation will overwrite the content of opensuse in /boot/efi/EFI/. On mine, /boot/efi/EFI/ contains opensusetw, opensuse150, opensuse151, debian10, tubuntu and others.
Another recommendation is taking control from the start. That means deciding what you want and accepting nothing else WRT space allocation on your boot device whether SSD, NVME or rotating rust. Among decisions to make:
How much space to allocate to /home
Whether to have /home on a separate filesystem
Whether to share /home among different installations
How many OS installations to eventually have. e.g. stable (Leap), rolling (TW), beta (15.2), alien1 (debian), alien2 (mint), alien3 (Fedora) Windows, etc.
How much space each OS’ / should have or need
Whether you need or want a swap partition, and if so what size
Whether to use LVM
Whose bootloader menu you want to see, and how to keep other installations from hijacking it
Possible use of RAID
Once you have these planned, start up a partitioner and implement your plan. The partitioner built into Leap and TW can be used for this, but in part since I’m not an LVM user, I always do it before starting the first installation, and simply tell each installer which partition to mount for each purpose.
When assembling a desktop machine a ATX or µATX mainboard with 6 SATA connectors is fine. Watch for low power consumption of the CPU.
From the above link the AMD Ryzen 5 2600, ASRock B450M Pro4 and G.Skill Aegis F4-3000C16D-16GISB are a very reasonable choice. Consider buying 32GB RAM (2x16GB). RAM is ten times faster than most M.2 SSDs.
Turn off Compatibility Support Module and use Uefi only and you will be fine.
I will give it a try, the win7 is an oem version on dvd, something ms does not like.The answer to why 32 bit, is again games.
Back then most games were still 32 bit.
I am thinking two hard disk, one for each os.
Were can I find what ef00, 0c01 and 8300 and such means ?
guus@linux-0pkp:~> sudo gdisk /dev/sda
[sudo] wachtwoord voor root:
GPT fdisk (gdisk) version 0.8.8
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory. THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by
typing 'q' if you don't want to convert your MBR partitions
to GPT format!
***************************************************************
I get this on sda and sdb.
Of course typed q then. Lets not fix something that is working.
Being familiar with BIOS/MBR I continued using both when assembling the i3-4130 (2014) and the i7-6700K (2106). When I switched the machines to UEFI/GPT in 2018 I wished I had started with UEFI from the beginning.
The idea was that you press “L” to list the partition types (to see what the various codes stand for). And then you type “q” to quit without changing anything.
Typing “L” at that point would have done no harm, but if you are still using MSDOS disks there is no use for GPT partition codes.
You can see MSDOS partition codes by issuing:
fdisk /dev/sda
then typing “l” (lower case L) but of course the codes are somewhat different from what malcolmlewis suggested.
I downloaded leap 15.1 off course with bit-torrent.
Always makes me smile, to use bit torrent ones in a while, for what it was made to do, download Linux distro’s.
Now I wait for new parts to arrive. Wil have to so some more reading and make up my mind. Burn a dvd or use an usb stick for the opensuse install.
Still have an usb stick for leap 42.3, probably gonna use that one for leap 15.1.
I don’t think I should start a new topic for it, but have a weird minor problem.
I wanted to format the usb stick, that was made to install leap 42.3
When I plugged it in, nothing …
Then started yast , and yast did see it, so I deleted all partitions.
Then formatted the stick, and when I plug it in, it shows again in Dolphin.
But its called: openSUSE-Leap-42.3-DVD-x86_64033
How do I fix this or, should I just ignore it and just use the program to make an install usb stick from the leap image.
I ones did it before but can’t recall the name of the program right now.
Will that program rename the usb stick to leap 15.1 iso something ?
I installed imagewriter and am a bit confused on why I had to install it. ( what did I use the last time ?)
Wrote the iso to the usb, and after I rebooted my pc and hit F8 to select a device to boot from, I could select the usb stick, then was greeted with openSUSE, that asked me what I wanted to do.
Install, boot from hard disk and so on.
Now I only have to build the pc to install it on. Waiting for parts always feels like it takes for ever, but I am ready
It seems that you found most of the answers yourself.
And, yes, I have to install “imagewriter” if I want to use it. I normally use “dd_rescue” from the command line instead of “imagewriter”. But I also have to install “dd_rescue”. However, I could have just used “dd”, which is part of a normal install.
That’s common behaviour. Bootable ISO 9660 sticks are not auto-mounted with default system settings, so file managers (Dolphin, Nautilus…) do not “see” them as soon as they are inserted.
But the device files are there, so that disk utilities like YaST, GParted, ImageWriter or command line tools like gdisk etc. indeed can do their job with those devices, or you can manually mount them to see their content. So, nothing odd on your system.
BTW, when you delete all partitions with YaST-Partitioner e.g. the disk label (“Leap 42.3…”) remains there until explicitly removed (with parted or other tool) or overwritten, e.g. when you write a new image onto the stick.
