About to install Tumbleweed on my main desktop, I just have a few questions before to proceed (coming from Ubuntu LTS and I think snap just killed me)
I’ve tested the install on a VM and checked that the applications I need for my daily work are available in the repos and can be installed without much tinkering.
During the install, The suggested partitioning did not give me the /home partition I was expecting. Only going through guided did I have the choice to create a separate /home. Any pros reasons why /home is not created by the suggested option ?
I suppose the Wireless (BCM4360) will not be detected during installation? If so, I would need to prepare a cable.
Post-install, other than the few application I need, I will also install the multimedia Codecs.
Reading here: Codecs - openSUSE User Documentation Project
I am not sure to understand this part: “The only limitation is that this method will consider Packman as the unique provider of all codecs — not just the proprietary ones which openSUSE cannot provide. Proceed if this limitation is acceptable for you”
I was reading that to keep the Tumbleweed as stable as possible, it is best to keep to “official” repos. So, is it best to add the Essentials Packman as a repo, or to use the OPI method?
(hopefully, the above question makes sense)
And last, before the jump, I am looking for a stable distro. Reading here and there, Tumbleweed is a very good candidate. I was not expecting this from a rolling distro, and was at first going for Leap. MicroOS appeared on my list just hours ago.
So Tumbleweed, to keep it “clean” is there any do/dont that I should be aware off? I will only have a few software installed, mostly via Flatpak (except Steam)
I wasn’t expecting that. Good to know.
But brings back a question my my list because of : don’t install from Open Build Service
Same link as yours, on the Post-installation best-of it says : “To do this we recommend using the
opi – Open Build Service Package Installer”
There’s no way around it … Or am i missing something?
It’s a recommendation, not a hard-and-fast rule. Just be aware that if you don’t follow the recommendations, you may need to do a little work to keep things up-to-date. Keeping the number of repositories to a minimum is a generally good recommendation regardless of which distro you use - more repos means more complexity, and home: repos may or may not be updated (as they are, by definition, the home repo for anyone who wants to try using OBS to build something).
Some users want a separate partition for /home because they are used to it for legacy reasons, or want a different file system. There are a few measures to be taken for VM images, databases when stored in a CoW filesystem like Btrfs, some people might prefer to stick to more traditional filesystems for that. In the end is a bit of a personal choice, as it isn’t a limitation really. Mind you by default /home is a subvolume separate from the root installation but still a single partition. A subvolume is like a separate volume in many ways, with the benefit of being able to allocate storage from a single “unused pool”.
home: repositories include whatever the maintainer (many times just there without maintenance) wanted to build. It might be just an app, which should not compromise systems’ stability, but it might want to replace system libraries built in different ways, which are more riskier. On top of that, those repositories are not peer-reviewed for security issues, so you should take it in consideration.
With btrfs partitions are replaced by subvolumes. /home has its own subvolume.
You mean that openSUSE on the other hand includes whatever maintainers did not want to build but were forced to do so, presumably on a gun point?
Your definition applies to any repository. Any repository includes whatever maintainers wanted to build. Any repository has packages that decay because they are not maintained. It is just that for Factory there is some automatic process to remove from repositories packages that do not build anymore. But it does not help users who actually needed these packages.
What makes you think packages in standard repositories are?
Clearly that’s not what @awerlang’s meaning is. They were simply saying that home: repos are created by anyone who wants to build something, and they may or may not have any intent or desire to maintain it.
I count myself as one of those individuals. If you use anything from home:hendersj, you do so at your own risk, because I build things there for my own edification and use.
It’s always been that way with the home: repositories.
“I suppose the Wireless (BCM4360) will not be detected during installation? If so, I would need to prepare a cable.”
You are likely correct, but it is possible the wireless will be detected. However, it is always better safe than sorry, so plan to work around it either with a cable or otherwise.
I generally use the full image on USB stick to install completely offline, and then update the system after it connects to the network. This way, I do not have to worry about spotty connections, correct wireless or wired detection and so on.
That’s true, I was referring to situations where a system library found in factory is rebuilt in a home: repository, but with different settings or patches added/removed in a way that can bring instability, in particular if unmaintained.
I’m not implying the opposite is true for any other type of repository (official, third-party vendor, etc). That said, TW does include security reviews at least for a subset of packages e.g. Bug 1134132 – AUDIT-STALE: deepin-file-manager: new dbus of deepin-file-manager
I could not wait for the weekend and did the installation during lunchtime.
The good: I am able to write this post from a running Tumbleweed. Yeah !
The less good (and maybe I should open a new post, I’m not sure about this) is that I had an error than seemed critical at the very end of the installation. Message was something full, can’t write, or something like that. (Should have take a picture)
And, I have few error at boot, many about acpi, other about blacklist.
acpi , I think I can add a no_acpi at boot to get rid off the acpi error messages. Is there a downside to this?
blacklist: Problem blacklisting hash (-13) = Re: [PATCH] certs: Prevent spurious errors on repeated blacklisting - Mickaël Salaün I guess I will just have to live with it, and it is probably due to the more recent kernel I am now using.
Which reminds me that I need to create a new snapshot after the one created on first boot.
So, I suppose only 2 real question remain :
Which log can I use to find out the error message I got at the end of the installation? Currently going through Journal entries, but cannot find the message.
Is there a way for me to check the current stability of the system? (very vague question) to see if any impact from the error messages.
That being said, I’ve installed the wireless drivers, the Remote Desktop Client (back to work).
I have a separate /home partition XFS (old habits die hard)
Activated both Packman repos. But I will deactivate the non-essential one, I thought the broadcom-wl was in there, but it is in the main.