@tumulus_scrolls
@lemmy.fmhy.mlThere is !linuxmemes@lemmy.world and !linuxmemes@lemmy.fmhy.ml.
I mean... "who needs features in 2022" is onto something. But I use both, for various Nvidia and laziness related reasons, and have a dim idea what they do inside, as probably most flamers on the topic.
Feedback: to see an example one has to click through to another file in the repo.
Is it a subset of Markdown or YAML? It is a type of decision that it would be good to be upfront with to the users. It also gives you a framework for further thinking and development, and some out of the box parsability.
Obvious things I don't see mentioned:
history | grep whatever
(or other useful piping), though your older commands are forgotten eventually. You can mess with the values of HISTSIZE
and HISTFILESIZE
environment variables in your system.Context just before that quote:
As we understand it, this contract clearly states that the terms do not intend to contradict any rights to copy, modify, redistribute and/or reinstall the software as many times and as many places as the customer likes (see §1.4). Additionally, though, the contract indicates that if the customer engages in these activities, that Red Hat reserves the right to cancel that contract and make no further contracts with the customer for support and update services.
This is rich, don't know how many people are aware of that.
I was looking into Arch-based environment and wondered if there is an option for a scenario where you don't have to update for a few weeks for example, because you don't use that computer or whatever. But you still want to try the Arch configurability and wiki docs for it.
From what you're saying, it's still actually all rolling release. From my (flawed? correct me) understanding it is different from Ubuntu or Fedora, where you can update an outdated OS state and it isn't supposed to break. Possibly barring changing OS versions.