140 million? Am I close?
LeFantome
joined 1 year ago
I do not really see hostility or taking down. More of a difference of opinion or experience.
Also, this is not a private email thread. It is a public forum. Whatever advice you get risks becoming guidance for the community. I think it is perfectly reasonable, even responsible, for people to respond with their thoughts on security.
You can ignore the advice not to implement this capability on your personal machine. That is your call. However, this should not become standard practice by Linux users.
Thank you for answering at some point in the thread the use cases that drove your question. I was very curious.
When I have needed “Run as Administrator” in Windows, it has typically been to run the command line. The reason Windows needs this is because it has lacked “sudo”. The next release of Windows is adding it as a feature ( going the other way ).
I have used Linux for decades as well and really not needed this. Partially this is because tools that require root access are typically configured to ask for it already.
Your “need to delete a file” use case made sense to me but I do not run into it. Perhaps my file systems are mounted differently. Perhaps I am not manipulating files of other users ( sounds right ). Or maybe I am more likely to be at the command line. Your “edit files as root” use cases leads me to believe I use the command line more as that is certainly something I would be doing from the terminal. I have to edit files as root everyday but it is always from the terminal. I am not encountering files that I cannot edit in my file manager though as I would have navigated to those files in the terminal to begin with. Clicking around in a file manager to get to system files is not even something that would have occurred to me. If I am using the file manager, it is to manage my own files ( mostly media and documents ).
No judgement. Do things how you want. I was just curious what you were using this for. When I use Windows, I use “Run as Administrator” all the time. In Linux, I did not even notice it was missing. Going back to Windows makes me miss “sudo” in the terminal though. I am not the only one obviously as they are now adding it to Windows too.
That is a great analogy.
Linux can support ext2 two ways today: explicitly and as a side effect of ext4 support. All this change does is remove the explicit support.
We can remove the explicit CD support provided by a dedicated drive because the DVD drive will provide it as a side-effect.
You will still be able to mount an ext2 file system with the kernel until ext4 support is removed. That is still going to be a long, long time.
Just use ext3 with journaling turned off.
I had problems with Manjaro, would not recommend it, and now use EndeavourOS.
That said, you did a fantastic write-up here. Really well done.
I don’t need EOS and Arch to merge. I would be happy if Arch would just include yay or paru in the main repos so you could use the AUR out of the box.
The problems with Manjaro are not just people using non-stable branches or even project governance ( though that had unfortunate moments ). The biggest issues I had were the disagreements that Manjaro had with the AUR due to missing or outdated packages. As you point out, these packages are merely delayed. However, the decisions made about system state today can carry forward into the future and are not always unwound once the core packages finally update. I had issues with pamac as well where it would install old packages instead of new ones unless I cleared the cache all the time. Maybe that was somehow my fault. I use plain old yay and paru now with the occasional pacseek for good measure.
Manjaro is still a good looking OS though. I think most people prefer the green to the purple in EOS. Lots of people love the look of Garuda but, for me, it is too much.
Again, really nice write-up. I hope Manjaro continues to serve you well.
In addition to being useful for gamers, these are probably about to be the least likely to change APIs in the kernel.
If you have 4 MB of RAM or less, I would recommend 32 bit regardless of CPU.
The machine he linked to has 2 GB of RAM. A 64 bit distro will eat half of it getting to an empty desktop and a couple browser tabs will eat the rest.
Anything with more RAM, I completely agree with you.
1 in 2 professional developers use Linux ( many of the others probably use Macs ).
If you are working with containers ( the cloud ), Linux is the native environment. So Linux provides a great environment for most of what is headed for AWS or Azure. If you are building websites ( eg. React ), Linux is the nicest environment to work in. Node is best on Linux. Java and Python IDEs work great on Linux. C / C++ work is often embedded with is often Linux and again the tooling works great on Linux. The more offbeat your platform choice, the more likely it is to be Linux first ( Gleam anyone? ). Even the .NET experience is great on Linux ( maybe better than Windows depending on what you are building ).
“96.3% of the top one million web servers are running Linux. (ZDNet)”
That right there is why Microsoft cares less and less every day about Windows, as Azure continues to grow as the company cash cow.
Their share of the 53% of “professional developers” that do not use Linux keeps them interested on the desktop.
Well, to be fair, the other reason that Microsoft still cares about Windows is that Office is their other cash cow. As more and more people move to Office 365, they will start to care less about that too ( as the web versions work great on Linux ).
What happened to being able to use VirtualBox as a front-end to KVM? That seemed like the best of both worlds.