Recently I have written an article on " How to Install OpenSUSE Leap 15.2." <https://trendoceans.com/how-to-install-opensuse-leap-15-2/> If you Guys can review this article, it will be amazing because you all are masters, which avoids issue during the following guide for new users. We all want users should have the best experience without any humdrum, and this will be possible if you review this article and share feedback with me. I hope so you guys we will share feedback soon. Article Links https://trendoceans.com/how-to-install-opensuse-leap-15-2/ Regards, Gagan Trend Oceans
On 08/02/2021 05.36, Vegan Tech wrote:
Recently I have written an article on " How to Install OpenSUSE Leap 15.2." <https://trendoceans.com/how-to-install-opensuse-leap-15-2/> If you Guys can review this article, it will be amazing because you all are masters, which avoids issue during the following guide for new users.
First error right at the start, in the tittle: it is NOT OpenSUSE. It is openSUSE.
We all want users should have the best experience without any humdrum, and this will be possible if you review this article and share feedback with me. I hope so you guys we will share feedback soon.
Article Links https://trendoceans.com/how-to-install-opensuse-leap-15-2/ <https://trendoceans.com/how-to-install-opensuse-leap-15-2/>
* Arguably, the fastest download method is a proper metalink client, because it uses all methods. Further info: <https://en.opensuse.org/SDB:Download_help#Checksums> * You recommend using "balenaEtcher, ventoy or dd" to create a bootable usb stick. Well, neither balenaEtcher nor ventoy are tested and approved methods with openSUSE. * For using dd, you say: sudo dd if=/[ISOFILE-LOCATION] of=/dev/[PARTITION NAME] status=progress Well, this is WRONG. The openSUSE iso has to be copied to the whole "disk", not to a partition. sudo dd if=/[ISOFILE-LOCATION] of=/dev/[DISK] status=progress * You should simply link to our instructions page on creating the USB stick, at <https://en.opensuse.org/SDB:Live_USB_stick> * These repository descriptions are reversed, and neither are fully correct: Update Repository(Non-OSS):- It is used to download proprietary software license. Non-OSS Repository:- This must be enabled to get the latest security patches and updates while installing OpenSUSE 15.2 * This phrase is not correct: «In case of multi-boot make sure to select Hardware Clock Set to UTC to avoid conflict between System time» - No, if you double boot to Windows you need to use local time on the hardware clock, unless you do a certain registry change in windows which is documented in our wiki (<https://en.opensuse.org/SDB:Configuring_the_clock#Other_OS>) * After seeing you go in that much detail till now, I'm surprised you do not look at the boot details, in the summary "installation settings" screen, or at the "Software" section, which is where additional software can be selected to install. Also you you could look at the myriad possible partition details. * You say at the end «can ask Question in OpenSUSE Official forum.», making no mention of other help channels we have. Have a look: <https://en.opensuse.org/openSUSE:Communication_channels> -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Hi,
We all want users should have the best experience without any humdrum, and this will be possible if you review this article and share feedback with me. I hope so you guys we will share feedback soon.
Article Links https://trendoceans.com/how-to-install-opensuse-leap-15-2/ <https://trendoceans.com/how-to-install-opensuse-leap-15-2/>
* Arguably, the fastest download method is a proper metalink client, because it uses all methods. Further info: <https://en.opensuse.org/SDB:Download_help#Checksums>
* You recommend using "balenaEtcher, ventoy or dd" to create a bootable usb stick. Well, neither balenaEtcher nor ventoy are tested and approved methods with openSUSE.
I'd like to point out that I've been using ventoy for my installations and for me it works perfectly fine. Also I recommend it to people when they ask when how to make a bootable USB (not always for openSUSE though).
* For using dd, you say:
sudo dd if=/[ISOFILE-LOCATION] of=/dev/[PARTITION NAME] status=progress
Well, this is WRONG. The openSUSE iso has to be copied to the whole "disk", not to a partition.
sudo dd if=/[ISOFILE-LOCATION] of=/dev/[DISK] status=progress
/Syds
On 10/02/2021 09.14, Syds Bearda wrote:
Hi,
We all want users should have the best experience without any humdrum, and this will be possible if you review this article and share feedback with me. I hope so you guys we will share feedback soon.
Article Links https://trendoceans.com/how-to-install-opensuse-leap-15-2/ <https://trendoceans.com/how-to-install-opensuse-leap-15-2/>
* Arguably, the fastest download method is a proper metalink client, because it uses all methods. Further info: <https://en.opensuse.org/SDB:Download_help#Checksums>
* You recommend using "balenaEtcher, ventoy or dd" to create a bootable usb stick. Well, neither balenaEtcher nor ventoy are tested and approved methods with openSUSE.
I'd like to point out that I've been using ventoy for my installations and for me it works perfectly fine. Also I recommend it to people when they ask when how to make a bootable USB (not always for openSUSE though).
Problem is, from what I read at the Ventoy site, that Ventoy can *modify* what it writes, to "make it bootable". This is WRONG with openSUSE images, which are created "ready", intended to just be copied without any modification or trick to the DVD or USB stick. And it has to be written to the raw media, not not to a partition. This is crucial. And this is what the next paragraph is about:
* For using dd, you say:
sudo dd if=/[ISOFILE-LOCATION] of=/dev/[PARTITION NAME] status=progress
Well, this is WRONG. The openSUSE iso has to be copied to the whole "disk", not to a partition.
sudo dd if=/[ISOFILE-LOCATION] of=/dev/[DISK] status=progress
/Syds
If you propose to install the openSUSE image to a partition and make it bootable using Ventoy, you have not understood how openSUSE installation works. Sorry. Ah, and I forgot to mention that the above suggested dd command is terribly slow as given. This is several times faster (single line, mail wraps): time dd if=/path/ISOFILE.iso of=/dev/sdX oflag=direct bs=16M status=progress -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Le 10/02/2021 à 11:57, Carlos E. R. a écrit :
Problem is, from what I read at the Ventoy site, that Ventoy can *modify* what it writes, to "make it bootable".
not the iso. I use Ventoy and it works more or less, depending on the machine it's used with. One create a ventoy dusk/pen, then copy any iso on the relevant folder (cp, Dolphins, whatever). Ventoy creates a boot menu jdd -- http://dodin.org
On 10/02/2021 19.57, jdd@dodin.org wrote:
Le 10/02/2021 à 11:57, Carlos E. R. a écrit :
Problem is, from what I read at the Ventoy site, that Ventoy can *modify* what it writes, to "make it bootable".
not the iso. I use Ventoy and it works more or less, depending on the machine it's used with.
One create a ventoy dusk/pen, then copy any iso on the relevant folder (cp, Dolphins, whatever). Ventoy creates a boot menu
Ok, so it is not the ideal tool to put the openSUSE install media on an USB stick, as it does modifications which are not tested by our testing system (https://en.opensuse.org/openSUSE:OpenQA). Then people come here with weird problems that were caused for not following our instructions. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Le 10/02/2021 à 20:07, Carlos E. R. a écrit :
On 10/02/2021 19.57, jdd@dodin.org wrote:
Le 10/02/2021 à 11:57, Carlos E. R. a écrit :
Problem is, from what I read at the Ventoy site, that Ventoy can *modify* what it writes, to "make it bootable".
not the iso. I use Ventoy and it works more or less, depending on the machine it's used with.
One create a ventoy disk/pen, then copy any iso on the relevant folder (cp, Dolphins, whatever). Ventoy creates a boot menu
Ok, so it is not the ideal tool to put the openSUSE install media on an USB stick, as it does modifications which are not tested by our testing system (https://en.opensuse.org/openSUSE:OpenQA). Then people come here with weird problems that were caused for not following our instructions.
it do not change the iso at all, it just replace the bios if it can jdd -- http://dodin.org
On 10/02/2021 20.09, jdd@dodin.org wrote:
Le 10/02/2021 à 20:07, Carlos E. R. a écrit :
On 10/02/2021 19.57, jdd@dodin.org wrote:
Le 10/02/2021 à 11:57, Carlos E. R. a écrit :
Problem is, from what I read at the Ventoy site, that Ventoy can *modify* what it writes, to "make it bootable".
not the iso. I use Ventoy and it works more or less, depending on the machine it's used with.
One create a ventoy disk/pen, then copy any iso on the relevant folder (cp, Dolphins, whatever). Ventoy creates a boot menu
Ok, so it is not the ideal tool to put the openSUSE install media on an USB stick, as it does modifications which are not tested by our testing system (https://en.opensuse.org/openSUSE:OpenQA). Then people come here with weird problems that were caused for not following our instructions.
it do not change the iso at all, it just replace the bios if it can
I guess you don't really mean "replace the bios". Only a sophisticated and evil virus can replace my computer bios :-D -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Le 10/02/2021 à 20:12, Carlos E. R. a écrit :
I guess you don't really mean "replace the bios". Only a sophisticated and evil virus can replace my computer bios :-D
at run time only, but to boot anything one need this jdd -- http://dodin.org
On 10/02/2021 20.20, jdd@dodin.org wrote:
Le 10/02/2021 à 20:12, Carlos E. R. a écrit :
I guess you don't really mean "replace the bios". Only a sophisticated and evil virus can replace my computer bios :-D
at run time only, but to boot anything one need this
There must be a language issue here. The BIOS can not be modified, it is a ROM chip. You must be meaning something else. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 10/02/2021 21.49, Bengt Gördén wrote:
On 2021-02-10 20:24, Carlos E. R. wrote:
The BIOS can not be modified, it is a ROM chip. You must be meaning something else.
No. BIOS _were_ in a ROM once. Now days its in flash.
I know very well, and it is irrelevant for this thread. I can't see what an openSUSE installation disk can do with "replace the bios" has jdd says. It has to be a language issue on the side of jdd, so can you explain what he means? -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 2021-02-10 21:56, Carlos E.R. wrote:
I know very well, and it is irrelevant for this thread. I can't see what an openSUSE installation disk can do with "replace the bios" has jdd says.
You're right. It's totally irrelevant.
It has to be a language issue on the side of jdd, so can you explain what he means?
Unfortunately not. But if may guess, I suspect that he means that you don't need to go though hoops to boot an iso from an usb if you use Ventoy. Just copy the iso to the usb and Ventoy picks it up and creates a grub config (or similar) so it boots that iso. Not that it changes bios in any way. As a side note. Some years ago I made a multiboot usb (recipe from somewhere on the net. don't remember where) that booted iso's from a directory in a partition on a usb. I had a script to change grub whenever I copied a new iso to the directory. It was quite handy but a bit tricky to set up depending on how the boot process was for the particular iso so I eventually got tired of it and just ditched it. But I might take it up again if Ventoy is as good as it promises. -- /bengan
On 10/02/2021 22.37, Bengt Gördén wrote:
On 2021-02-10 21:56, Carlos E.R. wrote:
I know very well, and it is irrelevant for this thread. I can't see what an openSUSE installation disk can do with "replace the bios" has jdd says.
You're right. It's totally irrelevant.
It has to be a language issue on the side of jdd, so can you explain what he means?
Unfortunately not. But if may guess, I suspect that he means that you don't need to go though hoops to boot an iso from an usb if you use Ventoy. Just copy the iso to the usb and Ventoy picks it up and creates a grub config (or similar) so it boots that iso. Not that it changes bios in any way.
As a side note. Some years ago I made a multiboot usb (recipe from somewhere on the net. don't remember where) that booted iso's from a directory in a partition on a usb. I had a script to change grub whenever I copied a new iso to the directory. It was quite handy but a bit tricky to set up depending on how the boot process was for the particular iso so I eventually got tired of it and just ditched it. But I might take it up again if Ventoy is as good as it promises.
Yes, that's a possibility, and interesting for people doing distro testing. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Le 10/02/2021 à 21:49, Bengt Gördén a écrit :
On 2021-02-10 20:24, Carlos E. R. wrote:
The BIOS can not be modified, it is a ROM chip. You must be meaning something else.
No. BIOS _were_ in a ROM once. Now days its in flash.
anyway it can be sort of changed at run time when booting - or not... jdd -- http://dodin.org
Vegan Tech wrote:
Recently I have written an article on " How to Install OpenSUSE Leap 15.2." <https://trendoceans.com/how-to-install-opensuse-leap-15-2/> If you Guys can review this article, it will be amazing because you all are masters, which avoids issue during the following guide for new users.
We all want users should have the best experience without any humdrum, and this will be possible if you review this article and share feedback with me. I hope so you guys we will share feedback soon.
Article Links https://trendoceans.com/how-to-install-opensuse-leap-15-2/
Minimum 1Gb RAM ? Unless you have swap, 1Gb won't suffice for the installation. Once installed, a no-GUI system will run in less than 512Mb. A new user may not be too worried about these, so maybe just for completeness: openSUSE runs on a lot more than Intel or AMD hardware. For starters, also on Raspberry Pi, many small ARM boards, IBM mainframes and PowerPC. Installation sources - you can also boot the installer on a machine with PXE. (my usual procedure). For the ARM boards, we (openSUSE) provide JeOS images for SD cards. -- Per Jessen, Zürich (2.6°C) Meber, openSUSE Heroes.
On Wed, Feb 10, 2021 at 12:13 PM Per Jessen <per@computer.org> wrote:
Minimum 1Gb RAM ? Unless you have swap, 1Gb won't suffice for the installation.
GUI installation. Text mode should still be possible (probably even with less RAM).
Once installed, a no-GUI system will run in less than 512Mb.
Depends on what will be running, of course.
Andrei Borzenkov wrote:
On Wed, Feb 10, 2021 at 12:13 PM Per Jessen <per@computer.org> wrote:
Minimum 1Gb RAM ? Unless you have swap, 1Gb won't suffice for the installation.
GUI installation. Text mode should still be possible (probably even with less RAM).
Text mode too. I hardly ever run a GUI-mode installation (and certainly not on 1Gb only), but YaST has gotten stuck once or twice (on 1Gb machines) when I haven't had any swap activated. It's not very often that I do it though. I think I may have written a bugreport too.
Once installed, a no-GUI system will run in less than 512Mb.
Depends on what will be running, of course.
Good point :-) Just for comparison, I have a number of small ARM boards, 512Mb RAM - they run the usual basic stuff plus syslog, postfix and thttpd. On the one right here, it looks like 400Mb RAM (I'll have to check what happened to the rest), with about 90Mb free. -- Per Jessen, Zürich (3.0°C)
Per Jessen wrote:
Andrei Borzenkov wrote:
On Wed, Feb 10, 2021 at 12:13 PM Per Jessen <per@computer.org> wrote:
Minimum 1Gb RAM ? Unless you have swap, 1Gb won't suffice for the installation.
GUI installation. Text mode should still be possible (probably even with less RAM).
Text mode too. I hardly ever run a GUI-mode installation (and certainly not on 1Gb only), but YaST has gotten stuck once or twice (on 1Gb machines) when I haven't had any swap activated. It's not very often that I do it though. I think I may have written a bugreport too.
Mostly because I happened to be doing some tidying up and found a 1U box with 1Gb of memory, but also because I tend to get a nagging doubt when Andrei disagrees with me :-) I started an install of Leap 15.2 over ssh, plain ncurses, no swap. The system reported approx 971Mb memory (in 'top') - I started up YaST and before it finished adding repos, the oom killer stepped in. -- Per Jessen, Zürich (1.2°C)
Per Jessen wrote:
Mostly because I happened to be doing some tidying up and found a 1U box with 1Gb of memory, but also because I tend to get a nagging doubt when Andrei disagrees with me :-) I started an install of Leap 15.2 over ssh, plain ncurses, no swap. The system reported approx 971Mb memory (in 'top') - I started up YaST and before it finished adding repos, the oom killer stepped in.
Yes, before someone beats me to it - if you don't activate on-line repos, a Leap 15.2 installation can be done in 1Gb of memory. -- Per Jessen, Zürich (1.1°C)
10.02.2021 18:58, Per Jessen пишет:
Per Jessen wrote:
Mostly because I happened to be doing some tidying up and found a 1U box with 1Gb of memory, but also because I tend to get a nagging doubt when Andrei disagrees with me :-) I started an install of Leap 15.2 over ssh, plain ncurses, no swap. The system reported approx 971Mb memory (in 'top') - I started up YaST and before it finished adding repos, the oom killer stepped in.
Yes, before someone beats me to it - if you don't activate on-line repos, a Leap 15.2 installation can be done in 1Gb of memory.
Yes, I was about to mention it. In the past installer actually did not OOM but simply appeared to be hung completely. There was bug report about it ... https://bugzilla.opensuse.org/show_bug.cgi?id=1132650 ... what familiar names :)
On 10/02/2021 19.27, Andrei Borzenkov wrote:
10.02.2021 18:58, Per Jessen пишет:
Per Jessen wrote:
Mostly because I happened to be doing some tidying up and found a 1U box with 1Gb of memory, but also because I tend to get a nagging doubt when Andrei disagrees with me :-) I started an install of Leap 15.2 over ssh, plain ncurses, no swap. The system reported approx 971Mb memory (in 'top') - I started up YaST and before it finished adding repos, the oom killer stepped in.
Yes, before someone beats me to it - if you don't activate on-line repos, a Leap 15.2 installation can be done in 1Gb of memory.
Yes, I was about to mention it. In the past installer actually did not OOM but simply appeared to be hung completely. There was bug report about it ... https://bugzilla.opensuse.org/show_bug.cgi?id=1132650 ... what familiar names :)
:-) I reported a similar issue long ago (42.2 beta): http://bugzilla.opensuse.org/show_bug.cgi?id=999776 Back then, 1G was more than enough. I read myself saying: The optimal procedure in low memory would be to boot with "startshell=1" as booot parameter, which gets to a text console; there use fdisk, mkswap and swapon, and finally, type "exit" to start the installer, in graphical mode. It runs quite snappy :-) The bug, where I asked for YaST to warn of low memory without crashing first, was closed wontfix by the "automated batch bugzilla cleanup" when it grew too old. And there was a duplicate of this bug, too. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
participants (9)
-
Andrei Borzenkov -
Bengt Gördén -
Carlos E. R. -
Carlos E. R. -
Carlos E.R. -
jdd＠dodin.org -
Per Jessen -
Syds Bearda -
Vegan Tech