I wrote to the address in the #GPLv2 license notice and received the #GPLv3 license | Mendhak / Code
#GPLv2
真的有人寄信要 GPL 授權的 copy...
Hacker News 上看到 2022 年的文章：「I wrote to the address in the GPLv2 license notice (2022) (mendhak.com)」，原文在「I wrote to the address in the GPLv2 license notice and received the GPLv3 license」。 作者在 GPLv2 看到這段： You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 5…
#copy #fsf #gnu #gpl #gplv2 #gplv3 #hard #license #mail #public
I wrote to the address in the GPLv2 license notice
https://code.mendhak.com/gpl-v2-address-letter/
#HackerNews #GPLv2 #OpenSource #SoftwareLicensing #HackerNews #TechCommunity #GPL
Android: sviluppo interno da aprile (ma resta open source)
#Android #AOSP #CodiceSorgente #Developer #GMS #Google #GoogleMobileServices #GPLv2 #KernelLinux #Notizie #Novità #OpenSource #Sviluppatori #Sviluppo #TechNews #Tecnologia
https://www.ceotech.it/android-sviluppo-interno-da-aprile-ma-resta-open-source/
@AugierLe42e I assume that port is fixed to a specific USB Hub / Controller / Port and the button is similarly linked to some GPIO / I²C / PS/2 port...
- What you can do is check
lsusbfor #USB devices and see if the specific port in question has a USB mass storage device or SATA bridge chip attached to it when said button is pressed.
If #QNAP used #Linux they should've provided those drivers / scripts as part of their #GPLv2 obligations to buyers/owners of said #NAS boxes.
- Just don't expect any of that code to be useable, as @landley can attest from the #BusyBox license enforcement…
Either way if you can reliably identify the port & detect the button presses that should be sufficient to build like a #bash or #python script to basically detect the drive, mount it and cp -r /dev/$DRIVE/ /home/copied_drives/$LABEL/
- It may need some fiddling and will most likely only work reliably on unencrypted drives with ext2-ext4, btrfs, ntfs, fat32, exfat filesystems...
Pretty shure you'll have to tweak a bit unless you want to use /dev/by-uuid/$UUID and the UUIDs of the partitions as name...
🍏 macOS No Longer Ships with Emacs
— Bozhidar Batsov
｢ The answer to the first question turned out to be Apple being opposed to using anything licensed under GPL v3, and so it happens that Emacs 22.1 was the last Emacs version licensed under GPL v2 ｣
https://batsov.com/articles/2025/01/12/macos-no-longer-ships-with-emacs/
You can find us on #GitHub obviously, as well:
https://github.com/LibreQoE/LibreQoS
#QualityOfExperience #OpenSource #QoE #FLOSS #bufferbloat #latency #jitter #ISP #WISP #FISP #QoS #broadband #QualityOfService #FWA #InternetServiceProvider #fiber RFC8290 #FQ_CoDel #sch_CAKE #FQCoDel #schCAKE #WiFi #speedtest
@FritzAdalis @fl0und3r @fence Granted, #OpenBSD usually removes #complexity and stuff that can't be #secured to their standards, and I do applaud them for that.
- Even tho it comes at the cost of a system that isn't easy to get started with, since one's experience and intuition from #Linux won't help one here...
That being said even tho I despise #Netflix, they moved to #FreeBSD as that cuts down on their specific hardware needs, which is ne net and gross positive for the world and #BSD's as they'll need less hardware, datacenter floorspace, cooling, power and thus reduce the impact of their business.
- Tho it's not because Netflix is envoirmentally concious or some other #greenwashing reason, but because their infrastructure is more expensive than personnel and cutting down 5% cost at that is saving them millions even if they pay their BSD engineers 10x to their Linux counterparts.
OFC for #commercial users, BSDs are always more preferable as #GPLv2 of #Linux would basically make it hard to do the "security by obscurity" part of #DRM & #CopyProtection they want on stuff like #GameConsoles.
- BSD is way more permissive and I do like that.
Sadly for many, Linux won for most "mainstream" applications to the point that outside nieche cases, it's a rounding error in statistics.
- That being said many innovations do get adopted where possible, like #OpenZFS support (tho AFAIK OpenBSD lacks that for the aforementioned complexity reasons)...
@prem_k @silentexception Well, #FLOSS does not require that they need to make it simple for one to do so.
Both #grsecurity & #RedHad comply to #GPLv2 by merely providing #paywalled access to their repos.
They don't need to provide instructions to make reproduceable builds nor documentation nor resources to do so!
I also love the argument of controlling the upstreaming pace because in other words "the drivers aren't ready yet" ... @tuxedocomputers why do you sell it to customers if the drivers aren't ready enough for upstreaming...
https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers/-/issues/137
#tuxedo #gplv2 #linux
FreeCAD Version 1.0 Released - #FreeCAD is an open-source parametric 3D #CAD (Computer-Aided Design) modeling tool. It's primarily used for designing and engineering products in various fields such as mechanical engineering, product design, and architecture.
This release marks FreeCAD's readiness for extensive real-world applications, reflecting the dedicated efforts of its community.
https://blog.freecad.org/2024/11/19/freecad-version-1-0-released/
7/ To follow up once more, likely for the last time:
Werner Sembach relicensed the last of the formerly GPL3+ed #Linux #kernel drivers from @tuxedocomputers to #GPLv2 about an hour ago after all external contributors have agreed to that move. 👏
https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers/-/commits/main
Cc: @waldi #LinuxKernel
TIL: @tuxedocomputers released #Linux #kernel drivers for their machines under the #GPLv3, which makes it impossible for competitors and distros to ship them pre-compiled, as that license is incompatible with the #LinuxKernel's #GPLv2 only license.
They did this purposely, allegedly to "keep control of the upstream pacing" – and want to re-license the code while upstreaming.
https://github.com/tuxedocomputers/tuxedo-keyboard/issues/61
https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers/-/issues/137
https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers/-/issues/138
That you copied GPLv2-licensed software is not a defense to an infringement claim in China (or Germany) https://www.ifross.org/?q=node/1676 #copyleft #GPL #GPLv2
@libreleah thanks.
Personally, I think maintainers should choose their license wisely beforehand:
There are reasons why I chose to put some projects under #CCBYNCSA, some #GPLv3 and some #0BSD.
In some cases I did fork stuff under #MIT which I'd not change the license of - even if it would be compatible - because I literally changed nothing in terms of code and also didn't see any advantage in doing so to begin with.
Espechally in the case of #DuckStation this is bad because we ain't talking about the whole #GPLv2-only vs. GPLv3+ drama or #grsecurity #paywalling (which is an asshole move but legal )...
- Maybe the dev(s) - unlike #Capcom - weren't fully aware of this issue, but even big Companies (i.e. #AVM) got forced into compliance...
Lets just hope a friendly (!!!) reminder makes them realize, apologize and undo the change...
@carlwgeorge @vermaden @samurro @tara @vkc @BrodieOnLinux TBH, being just marginally better than #Oracle and #Microsoft is the only reason I'd use #RHEL over #Solaris or god forbid #Windows, tho I'm glad #Linux isn't controlled entirely by #RedHat and that I can use #OpenSUSE and #UbuntuLTS and their parent companies didn't gave me or my (fmr.) clients/employers the finger...
But hey, go keep lying to yourself with the corporate propaganda of open source sustainability because if you think that #FLOSS needs to be #profitable you haven't understood why people choose #Copyleft licenses like the #GPLv2 and espechally #GPLv3 and how Red Hat is providing arguments to push for "#AssholeLicensing" a la #AGPLv3.
Your dismissals of criticism are childish and your way to flood my notifications with bs replies just to then flee the discussion like a coward is a really bad way to pull rank.
- This behaviour reminds me of "channers" that refexively reply "You have an anime pfp, your opinion doesn't matter!" as if that's a way to engage with potential clients!
Just because I'm not a CxO doesn't mean I know how to (dis-)recommend suppliers and underpin that with past experiences, as clients/employers trust in my judgement.
"A Promise Without a Remedy: The Supposed Incompatibility of the #GPLv2 and #Apachev2 Licenses"
An old legal issue in #freeSoftware #FOSS revisited. Kudos to Pam @pchestek for challenging the status quo. This makes a compelling argument.
@SweetAIBelle @OS1337 shure.
I'm convinced that a fully-fledged image of that would be similar to #toybox's #mkroot, which is @landley 's reference implementation for a toxbox + #musl / #linux system.
- Last time I checked it came out just below 4 MB, but that was the premade image using only the stuff toybox included [and linux & being statically compiled against musl] like #gzip instead of #xz for compression, so there already is room to shave a few hundred kB without reducing functionality out of the get-go as I've seen with my build tests of #kernel666...
Either way, we're close to his reference matterial AFAICT and I do think that OS/1337 can become a good and solid foundation for #minimalist & #embedded systems.
For comparison:
#YoctoLinux is quite #THICC in comparison (using LSB & #GNUtils for the most part!) and stuff like #OpenADK seems to be overly complex...
- tho #Viprinet hasn't updated their stuff in like 8 years and I sincerely hope that's just them loginwalling access to #SourceCode like #grsecurity to paying customers only and not them such old Kernels.
Speaking of #grsec, I wounder if Bruce Perens actually sued them for allegedly violating #GPLv2 when in fact said license allows #paywalling aka. restricting access to buyers of the product it contains.
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst