simosx
Joined 11 years ago
Joined 11 years ago
They don't need to change the internal use of 'apache'.
The ASF will keep 'apache.org' but the huge problem is that they will NEVER accept to add a reference on the front page of the website "If you want to find more about the Apache indigenous tribe, click here".
About a decade ago, Allwinner was providing an "SDK" to vendors to customize the Linux kernel for their devices. This "SDK" was a tarball of the compiled Linux kernel. In it, there were object files for drivers by third-parties for devices in the SoC that Allwinner sourced from other companies. Allwinner had the source code but obviously could not release it. They did not think better, and included those object files because it helps device integrators (mainly Android) to get the job done.
How do you deal with this issue with this blatant GPL violation? Obviously, you do not alienate the company. They fcked up but it's not the end of the world. They cannot release the source code of parts they do not own. You build a relationship and get them through to the right path.
But what happened in reality? A colossal fck-up. An attempt to "blackmail" the company to release the full source code and enforce the GPL. Listen to this, an attempt to enforce the GPL to a company "located in China". Not even on vendors that sell products in Europe or the US.
This alienated any attempts to get Allwinner's upper management to work with Linux. Allwinner made an effort and released some stuff (https://github.com/allwinner-zh) including the bootloader source and documentation (2015). The damage was done.
In 2016, Linus and other kernel developers posted their position on enforcing the GPL (https://lwn.net/Articles/698452/). Very pragmatic and should have been followed with Allwinner.
Flutter is cross-platform. Canonical is doing the work for Linux. Toyota is doing the work for embedded devices (to use in their cars). Microsoft is doing the work for their foldable tablets. At the moment, Flutter has the momentum to be the UI for everything. Whether it will pan out, we will be here to see.
You can learn to use the windows controls on the left. I got used to using them and it takes a few days to feel at home. When sadly Ubuntu switched back to GNOME Shell and reverted this change, it felt really unnatural to have those windows controls on the wrong side. Still, you get used to it after a few days.
You get three options to run Ubuntu server.
The first option is to run Ubuntu server in a VM, and most users will want to run Ubuntu server in a VM. Multipass is a tool that helps you run Ubuntu server in a VM. Multipass is just a front-end for KVM when you use a Linux distribution. If you use Windows, it is a front-end for Hyper-V, etc.
The second option is to perform a manual installation, which means that you get the ISO and do your thing.
Between the two, most people would want to install Ubuntu Server in a VM rather than on baremetal. I think it makes sense to put that first. If a person is a power-user, then can read on and select Option 2.
I see that there is a perceived negativity on anything Ubuntu that if something is different, it is perceived as something bad is happening.
There is a usability package 'command-not-found', which is a handler for the shell and runs when the command you tried to run, was not found.
You mentioned though that you tried to install a package, the package was not found and got a suggestion to use snaps or something. There is no such thing as far as I know.
There are two packages, 'chromium-browser' and 'lxd'. In Ubuntu 20.04, both these packages are now only available as snap packages. If you try to install them with `apt install`, you get a notification that they are now only available as snap packages, and the installer transparently installs the snap package for you. This has been discussed a lot before implementing, and also here. The gist is that when you `sudo apt install chromium-browser`, you want the installation to work, not get an error message to run `sudo snap install chromium` instead.
It comes from the ancient times of rulers and peasants when people actually believed in unspecified innate qualities that differentiate people from each other.
"talent" is so much ingrained into culture that people take its vague existence for granted. I think that "talent" is used as a praise for the purposes of attracting/luring someone to do all the work.
Plants first appeared around 400 million years ago or later [2]. In fact, early plants required symbiosis with fungi to grow. Even now, plants grow better if they have symbiosis with fungi and most plants (such as tomatoes) can grow symbiotically with fungi. But it is cheaper to use fertilizers, and those are used instead. Still, forest ecosystems still depend on fungi and require them as a way to recycle plant material (fallen leaves, dead plants and trees).
Evolutionary, fungi existed well before plants managed to evolve.
1. https://en.wikipedia.org/wiki/Evolution_of_fungi
2. https://en.wikipedia.org/wiki/Evolutionary_history_of_plants
I suppose the rational is that updates should happen. You can take your time to hold updates for up to sixty days but they should happen anyway.
The certbot snap package is published by the EFF/LetsEncrypt themselves.
You could also trick snapd that you are on a metered Internet connection, therefore avoid updates.
See the stats for the Skype snap package for the range of Linux distributions, https://snapcraft.io/skype
That is, create your snap package and publish it on the Snap Store. Do not request to pre-approve any permissions. Arrange with your users to enable those permissions on demand.
For Ubuntu 20.04, it has been explained (in 2019!) that Chromium will be only available as a snap package. To help users transition, the command `sudo apt install chromium-browser` would install the snap package. It is better than "package not found".
It is so simple, but if you are stuck in a negative sentiment on snaps (read this thread), you get crazy.
There is a negative sentiment around snap packages. Even if you are an experienced Linux user, you fall into that negative sentiment and even if an issue is small, it is a deal-breaker for you.
The "chromium" issue has been explained in 2019. Ubuntu 20.04 does not plan to package "chromium" as a deb package (too difficult to maintain properly), therefore there was a need for a backup plan if users were trying to install it.