It obviously depends on how you boot (UEFI/BIOS) and where bootloader is installed.
It indicates that, Henk began programming more than a few years ago – <https://en.wikipedia.org/wiki/Foobar>.
- There’s also this definition – <What does foobar> mean?;
Which points to a definition in the “The New Hacker’s Dictionary” –
Probably originally propagated through DECsystem manuals by Digital Equipment Corporation (DEC) in 1960s and early 1970s; confirmed sightings there go back to 1972.
The DECsystem 10 was a 36-bit mainframe – later, a cheaper variant, the DECSYSTEM-20 was produced which, eventually, was succeeded by the VAX-11 32-bit machines …
- Another definition is here (the PDP-1 was an 18-bit machine) – <https://iq.opengenus.org/foo-bar/>
2 major organizations are behind the popularization of the terms namely Digital Equipment Corporation (DEC) and Massachusetts Institute of Technology (MIT). The first seen use of the terms date back to 1964 from 3 major projects namely:
- PDP-1 from Digital Equipment Corporation
- LISP by John McCarthy at Massachusetts Institute of Technology (MIT)
- Project on Mathematics and Computation (Project MAC)
not obvious to me, as I have not clue regarding this boot stuff :-p
Here it’s legacy and the default of the installer (MBR i guess)…
Defaults change over time.
Thanks - sorry this took SO LONG to get back to! (My time’s often not my own nowadays…) This is my current repository list. I’m also trying to set it up with ${releasever} compatibility. I still don’t think I need those “backports” repos, but there is software from there installed on my system. (maybe got there from some version of one click install or some such…)
[FONT=monospace]> zypper lr
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh
---+-------------------------------+-------------------------------------------------------------------+---------+-----------+--------
1 | brave-browser | brave-browser | Yes | (r ) Yes | Yes
2 | http-ftp.gwdg.de-4e218b07 | Packman Repository | Yes | (r ) Yes | Yes
3 | openSUSE_Leap_${releasever}_1 | science/openSUSE_Leap_15.3/ | Yes | (r ) Yes | Yes
4 | openSUSE_Leap_${releasever}_2 | hamradio/openSUSE_Leap_15.3/ | Yes | (r ) Yes | Yes
5 | openSUSE_Leap_${releasever}_3 | opensuse.org/repositories/network:/im:/signal/openSUSE_Leap_15.3/ | Yes | (r ) Yes | Yes
6 | openSUSE_Leap_15.3 | games/openSUSE_Leap_15.3/ | Yes | (r ) Yes | Yes
7 | repo-backports-update | Update repository of openSUSE Backports | Yes | (r ) Yes | Yes
8 | repo-oss | Main Repository | Yes | (r ) Yes | Yes
9 | repo-sle-update | Update repository with updates from SUSE Linux Enterprise 15 | Yes | (r ) Yes | Yes
10 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes
[/FONT]
…trying to list more info - but not sure this is working out to be useful. The sed $releasever code snipped seems to have worked.
[CODE]zypper lr -u
Repository priorities are without effect. All enabled repositories share the same priority.
[FONT=monospace]# | Alias | Name | Enabled | GPG Check | Refresh | URI
—±------------------------------±------------------------------------------------------------------±--------±----------±--------±----------------------------------------------------------------------------------
1 | brave-browser | brave-browser | Yes | (r ) Yes | Yes | https://brave-browser-rpm-release.s3.brave.com/x86_64/
2 | http-ftp.gwdg.de-4e218b07 | Packman Repository | Yes | (r ) Yes | Yes | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.3/
3 | openSUSE_Leap_${releasever}1 | science/openSUSE_Leap_15.3/ | Yes | (r ) Yes | Yes | http://download.opensuse.org/repositories/science/openSUSE_Leap_15.3/
4 | openSUSE_Leap${releasever}2 | hamradio/openSUSE_Leap_15.3/ | Yes | (r ) Yes | Yes | https://download.opensuse.org/repositories/hamradio/openSUSE_Leap_15.3/
5 | openSUSE_Leap${releasever}_3 | opensuse.org/repositories/network:/im:/signal/openSUSE_Leap_15.3/ | Yes | (r ) Yes | Yes | https://download.opensuse.org/repositories/network:/im:/signal/openSUSE_Leap_15.3/
6 | openSUSE_Leap_15.3 | games/openSUSE_Leap_15.3/ | Yes | (r ) Yes | Yes | http://download.opensuse.org/repositories/games/openSUSE_Leap_15.3/
7 | repo-backports-update | Update repository of openSUSE Backports | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/backports/
8 | repo-oss | Main Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.3/repo/oss/
9 | repo-sle-update | Update repository with updates from SUSE Linux Enterprise 15 | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/sle/
10 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/oss
[/FONT]
Oops! Per earlier comment - yes, I do need backports repos. :embarrassed:
I’ve edited it down to a visually manageable size for determining propriety for a zypper upgrade to 15.4. You’ll note some URIs have had “openSUSE_Leap_” strings purged to match the current mirror URIs. I would expect sudo zypper clean; zypper ref; zypper dup with the above URIs in their proper places in /etc/zypp/repos.d/ to result in a satisfactory upgrade from 15.3 to 15.4, as long as done before any of the remainder that still include “openSUSE_Leap_” trim them to match the new template.
“…as long as done before any of the remainder that still include “openSUSE_Leap_” trim them to match the new template.”
Thank You!
I can’t read this sentence correctly, I think. It reads like two sentences, with possibly opposite intent, concatenated (shown in two different colors). There may be a conjunction or something missing between them that makes this hard for me to parse. I get really paranoid trying to follow instructions that seem ambiguous. Can you restate, please?
It means, don’t do sudo zypper clean; zypper ref; zypper dup until after you’ve done the prep work, expunging openSUSE_Leap_ from .repo file URIs that do not exist any longer (if they ever did), aka those that need openSUSE_Leap_ purged from the URI to be valid. If you can’t open the URI in a web browser, it probably doesn’t exist, thus needs to be corrected before package management can use it. If you get a 404 result trying any .repo URI, open the parent directory to see what does exist there, where you will probably see what the URI in your .repo file needs to be.
I have no idea what this sentence says either. @pattim make sure you get it right or you’ll be doing a fresh install.
I used a “dry run” string to see what would happen with nothing actually being done.
sudo zypper --releasever=15.4 dup --dry-run --download-only --auto-agree-with-licenses --allow-vendor-change
tom kosvic
I have no idea what this sentence says either. @pattim make sure you get it right or you’ll be doing a fresh install.
I used a “dry run” string to see what would happen with nothing actually being done. After manually changing the “extra” OBS repos like science, graphics, electronics, etc to their new naming format in 15.4, I ran:
sudo zypper --releasever=15.4 dup --dry-run --download-only --auto-agree-with-licenses --allow-vendor-change
After seeing that this completed satisfactorily, I ran same command without “dry run”. Update went fine.
tom kosvic