Linux Mint 22 “Wilma” released!
Closed source isn’t a crime. However trying to ruin a company with exclusionary tactics can be. Linux kernel devs and Wayland devs have all conspired to harm a company.
Maybe. But wishes don't have to be possible. :)
I appreciate the fruit of NVidia's efforts... But that they were forced into it by a pack of wolves is morally wrong, and those responsible need to be ousted from open source, blacklisted from any IT work forever for needlessly inflicting harm on a company and it's users over a licensing preference.
Which will still be enough for Linus to prevent NVidia from getting full access to the kernel internals.
How is it nonsense? Linus himself in the kernel mailing list and in public speaking has repeatedly gone after NVidia due to their licensing. In the kernel, he's repeatedly cut NVidia off from using various kernel internals because they aren't open source; attempting to cripple their driver. That's fact. Check your history on it.
As for wayland, it could have been written to do absolutely anything they wanted it to do and be. They chose to not support NVidia due to the licensing, purposely choosing an incompatible way to display to try and force NVidia to change or to for NVidia to fall from it's spot as market leader.
I feel bad for NVidia, caving this. An open source driver coming out, them adding features to work with wayland instead of the other way around. It wreaks of extortion by the kernel and wayland devs, to damage market share if the devs don't get what they want. I hope they get sued for it and lose everything for it. It casts a terrible light on the open source community that it would make companies either capitulate, or the community tries to cut the company off at the knees. It was wrong and should be severely punished to prevent it ever happening again. As it is, no hardware company should trust Linux or offer to support it in any way, because it might turn around and bite you as it did NVidia.
It's not a conspiracy. Here's Linus, himself, publicly picking a fight with NVidia. All because of a driver not being open source. I love open source, I love the GPL, but no individual or company should be required to do business that way. It's up to them, as is their right.
Could have been, if Linux kernel devs and wayland devs weren't trying to break it all the time.
It's not NVidia's fault. Never has been. It was a religious war over licensing of the driver.
That would be giving into the Linux kernel and wayland driver bigots who set out to destroy NVidia on Linux, simply because of the driver's license. Linus, the kernel dev team, and wayland devs sought to break NVidia at every turn. A company that provided us with the best graphics cards on Linux for over a decade, because they couldn't get in and mess with NVidia's code and steal their secrets from their drivers. Don't give into to that level of zealotry. If anything, NVidia and their users should sue Linus and all the wayland devs for the years of crap they've pulled. All over a license. I love Linux, and am forever indebted to Linus for starting it... but this zealotry over licensing is why GNU never got off the ground itself; and they should be spanked for what they did to us. Wayland devs especially, they should be banned from opensource dev work forever and crippled financially for the crime they've committed.
I suspect you use them more extensively, than I. Mine are limited usually to the extended acls, which I then use getfacl to generate a dump of all the acls of the files and sub directories I am transferring or 7zipping, and include that file in the transfer or 7z bundle. Then use setfacl to apply all those permissions on the receiving end after everything has been copied or extracted.
I'd like a GUI app for generating CLI's for other GUI apps that don't have them already. An application is never complete unless everything can be done via a CLI and/or API.
Stallman, it's time to get over it.
man -k printf
Search the short descriptions and manual page names for the keyword
printf as regular expression. Print out any matches. Equivalent to
apropos printf.
From the system's DMI. You can check it yourself with dmidecode. Those values are largely unchangeable, and those that are, will probably require a tool from the vendor to change, which are usually for internal use only within their company.
Take my upvote.
I'm picturing Daffy Duck and Bugs Bunny swapping hunting signs on a tree... "Linux season!" "GNU season!", back and forth. The rest of us just watching like Elmer Fud.
Deleted
Permanently Deleted
Jump
Don't know about everyone else, but here are some of mine:
- Stick to posix compliance shell code, wherever possible
- Please wrap your variables with { }. Just please.
- Global variables being exported in all caps
- Local variables in lower case
- $() instead of
- Comment anything complicated, comment what section, comment usage
- Include usage output if options are not recognized
- Use case instead of if / elif, where possible
- 80 characters or less per line, where possible
- HERE docs in designated section, marked by comment blocks
- Comment your functions immediately above it's definition
- Add comment "#End of function Xyz" at line immediately below a function, with replacing Xyz with name of that function
- 2 space indentation
- Multi-line strings: First line open with quote and first line of string, followed by a backslash subsequent lines properly indented and backslashed. Last line, properly indented and close quoted.
- Break up multiple piping of commands with |\ and a new line where it makes sense to look nice, assisting readability
- Echo what the script is doing once in a while if the user will be waiting for a while
- Please don't do shar archives, or byte located binary extractions, make a script and a separate tarball - Helps a ton if we have to change it, like say... swapping out a bundled java runtime built for x86_64 with one for aarch64
- If the script will run for a very long time, check for tmux or screen and also the TMOUT variable... Give a warning to the user their connection might time out before the script is done if they don't unset TMOUT, and try using tmux or screen to allow the script to continue in the background, even if you do get disconnected
- Make use of logger
- I try to organize a script this way: 1. Shebang, 2. Initial variable definitions, 3. Functions, 4. runtime execution code, which might be best outside of a function, and calling functions. 5. Clean-up (remove pid and lock files, tmp files, etc etc.)
Then don’t ever get rid of your own place, so you can prove you’ve only been dating, not living together.
No ZFS on root install (encrypted or not). They removed it from the installer. :(