#licence
///Compostage collectif///
Mise en place d'un composteur collectif.
https://tube.hoga.fr/w/n211ZLdsyRSnzPRMDLrYzV
Toutes les infos, expos, photos... libres et gratuites sur https://compost.graineahumus.org
#compostage #collectif #licence #libre #compost #contributions
///Photos libres ou ouvertes///
Besoins de photos pour illustrer ?
Plus de 15 sites référencés sur https://libre.graineahumus.org
Espace, nourriture, paysages, science... Nombreux thèmes disponibles !
#libre_graineahumus #annuaire #licence #libre #domaine_public #contributions
///The Mutopia Project///
Partitions de musique dans le domaine public ou en creative commons.
https://www.mutopiaproject.org/
Un projet présent sur https://libre.graineahumus.org
#Partitions #musique #licence #libre #domaine_public #contributions
///Contribulle///
Offres et demandes de contributions sur tous types de projets en licences libres.
https://contribulle.org/
#contribulle #contribution #licence #libre #projet #contribatelier
Est-ce qu'il y a des personnes qui ont fait une licence de médiation et gestion d'actions culturelles et qui voudrait bien en discuter avec ma grande qui doit choisir aujourd'hui dans quelle fac elle va? Une question est notamment est-ce que la licence suffit pour bosser ou il faut un master?
Ça a été très vite: décision d'entrer à la fac il y a 10 jours environ, voeux sur parcours sup remplis hier, décision à prendre aujourd'hui entre 4 licences.
Merci 💕
US Seeks License To Encircle Russia, China With Biolabs
Documents found during Moscow’s operation in Ukraine revealed that the US was running an extensive biological research effort there. Over $200 million was spent on 46 biolabs researching deadly diseases. Russia, China, and some EU countries still await Washington’s responses about these labs.
https://www.blacklistednews.com/article/85279/us-seeks-license-to-encircle-russia-china-with.html
Tout l'été Les Ordis Libres vous présentent leur #exposition (1/16) :
Aujourd'hui la définition d'un logiciel libre en 4 libertés : Utiliser, Copier, Étudier, Modifier
https://lesordislibres.fr/images/sampledata/lesordislibres/panneaux/panneaux_jpg/panneau-01_v5.1.jpg
Cette exposition sera présente à la fête de l'Humanité du 15 au 17 septembre sur l'espace Numérique.
Pour aider à financer cet espace :
https://www.helloasso.com/associations/les-ordis-libres/collectes/fete-de-l-humanite-2023-espace-numerique-libre
YOUR RIGHT TO TRAVEL Drive
https://www.youtube.com/watch?v=4DZuLhhUmEo
In this presentation I discuss you right to travel vs drive and provide case law which clearly shows that a RIGHT can not be Converted to a Privilege. I Discuss the meaning of some legal words and the meaning of each. It is my hope that the viewer will see the deception and analyse things in a deeper way moving forward.
Email Deniedtruth@yahoo.com
#Banque centrale : les données #biométriques vont accélérer l'obtention d'un #prêt
Par ordre de la #Banque de Russie, les données biométriques seront désormais incluses dans les applications mobiles des banques, découle du projet d'instruction "Sur les critères pour les applications mobiles des banques avec une #licence #universelle".
Autrement dit, les banques pourront désormais émettre des prêts et ouvrir des dépôts via l'application uniquement lorsqu'elle pourra enregistrer de nouveaux clients à l'aide des données du système biométrique unifié (UBS). Ce document entrera en vigueur 10 jours après sa publication, et quant aux commentaires y afférents, ils seront acceptés jusqu'au 28 juillet. A noter que cette exigence ne s'applique pas aux banques qui désactivent leur application mobile dans les six mois suivant la publication du document. Aujourd'hui, la plupart des prêts et des dépôts sont traités via des applications mobiles, et une #carte bancaire est principalement utilisée pour les enregistrer. L'identification, bien sûr, n'est pas requise, puisque l'établissement de crédit dispose déjà de toutes les données. À première vue, ce projet est plus pertinent pour les nouveaux clients, mais en fait, les banques ont reçu un #ultimatum - à partir du 1er septembre, identifiez les clients dans une application mobile via l'EBS ou arrêtez d'émettre des prêts en l'utilisant. Maintenant, l'application mobile devra être finalisée, y compris l'identification via le même EBS, ce qui nécessitera 10 à 15 millions de roubles. Selon le chef du Conseil national des paiements, Alma #Baeva, "tout n'est pas si fluide avec la sécurité dans un système biométrique unique", et les acteurs du marché eux-mêmes l'ont dit plus d'une fois. Or, selon elle, l'État « a vraiment besoin » que les citoyens « rendent » leurs données biométriques. Bien entendu, le projet "Sur l'identification à distance" conviendra aux particuliers, car cette innovation leur permettra de recevoir des services financiers à distance et dans différentes banques, en confirmant simplement leur identité à l'aide de données personnelles biométriques, par exemple des voix, des images faciales, etc. . . De plus, le développement de cette plateforme transférera les services financiers vers l'environnement numérique, augmentera leur accessibilité au consommateur et augmentera la concurrence sur le marché financier. Soit dit en passant, ce service sera également disponible pour les personnes à mobilité réduite. Il est à noter que la procédure d'identification de l'utilisateur est #gratuite. Afin de compléter l'enregistrement initial, un citoyen devra simplement se rendre dans une banque qui a le droit d'enregistrer des individus dans le système unifié d'identification et d'authentification (ESIA) et le système biométrique unifié. Une telle banque effectuera toutes les procédures nécessaires - prendre une photo, enregistrer un échantillon de voix et envoyer ces échantillons biométriques à l'EBS. Il est à noter que pour bénéficier de services dans une nouvelle banque, un citoyen pourra se rendre sur le site internet ou l'application mobile d'un établissement de crédit et, à l'aide d'une identification à distance, bénéficier de ces services. L'étape suivante est l'autorisation dans l'EIES et la confirmation de vos données biométriques à l'aide d'une tablette, d'un smartphone, d'un ordinateur portable ou d'un ordinateur avec caméra et microphone, pour lequel vous devrez télécharger l'application EBS.
https://wek.ru/cb-biometricheskie-dannye-uskoryat-poluchenie-kredita
#russie
#politique #société #dictature #fascisme #censure #manipulation #démocratie #oligarchie
#questionner #comprendre #agir #revolution #MondeDAprès #résistance
#complot #complotisme #capitalisme #escroquerie #corruption #terrorisme #exclus
Open Source is about enabling users "Amazon, Microsoft, Google" and the White House, want to help make Open Source more secure... [caption id="attachment_26251" align="alignnone" width="430"] https://www.youtube.com/watch?v=U-8KopUKMzA\[/caption\] https://www.golem.de/news/openssf-150-millionen-us-dollar-sollen-open-source-absichern-2205-165382.html https://www.golem.de/news/openssf-linux-foundation-will-security-praxis-vereinheitlichen-2008-150036.html src of src: "White House OSS Mobilization Plan" 2022: https://openssf.org/blog/2022/05/11/testimony-to-the-us-house-committee-on-science-and-technology/ 2020: "The OpenSSF is[...]
#linux #gnu #gnulinux #opensource #administration #sysops #dev #c #development #rust #go #google #security #itsec #cybersec #cybersecurity #kernel #linus #torvalds #mozilla #licence #licencing #patents #patent
Originally posted at: https://dwaves.de/2022/05/16/rust-vs-go-open-source-is-about-enabling-users-rust-lang-will-complement-c-around-the-gnu-linux-kernel-for-better-safety-amazon-microsoft-google-and-the-white-house-want-to-make-open-sour/
Open Source is about enabling users
“Amazon, Microsoft, Google” and the White House, want to help make Open Source more secure…
- https://www.golem.de/news/openssf-150-millionen-us-dollar-sollen-open-source-absichern-2205-165382.html
-
- src of src: “White House OSS Mobilization Plan”
- 2022: https://openssf.org/blog/2022/05/11/testimony-to-the-us-house-committee-on-science-and-technology/
- 2020: “The OpenSSF is a cross-industry collaboration that brings together leaders to improve the security of open source software (OSS) by:
- building a broader community with targeted initiatives and best practices
- It combines efforts from the Core Infrastructure Initiative, GitHub’s Open Source Security Coalition and other open source security work from founding governing board members GitHub, Google, IBM, JPMorgan Chase, Microsoft, NCC Group, OWASP Foundation and Red Hat, among others.
- Additional founding members include ElevenPaths, GitLab, HackerOne, Intel, Okta, Purdue, SAFECode, StackHawk, Trail of Bits, Uber and VMware.
- Open source software has become pervasive in data centers, consumer devices and services, representing its value among technologists and businesses alike.
- Because of its development process, open source that ultimately reaches end users has a chain of contributors and dependencies.
- It is important that those responsible for their user or organization’s security are able to understand and verify the security of this dependency chain.” (src linuxfoundation.org)
so far so good eh?
How will this exactly play out? What will be the “modi operandi”? (Pentagon & JP Morgan Bank, are interested in making the software supply chain more secure, as the IT of banks (!!!) not very good (say the banks THEMSELVES (that fired a lot of IT staff to save on money))
Just an idea for the govs & big corps with the money:
- put up a “Open Source” “kickstarter” like website
- where companies & gov can put up their requirements
- Open Source developers either accept to tackle those requirements
- or:
- post their own projects & investors can allocate their resorces to Open Source
- ABSOLUTE transparency is critical here, not a “pay to play” “taking power” “taking over” “Open Source” “influencing” sealing deals behind closed doors.
long version:
https://peertube.co.uk/w/jKvQozs7xDqpQvbwQFdKbF
The Star Trek economy: will it ever exist?
Afaik Dutch historian Rutger Bregman confirms in his book “Humankind: A Hopeful History” (BE WARNED: it is a realist’s thriller!), that “the nature” of humans (also under constant development), is as such, that only a small percentage are reckless “psychopaths”,
the majority of mankind rather wants to help each other, than shoot each other.
Rust “second in command” around the GNU Linux Kernel
Because Rust lang promises improvements around cyber/itsecurity (no more buffer over/underruns), it might become “second in command” around the Kernel.
The cons: Rust is more C++ than C, which might be a problem for the (long term) C nerds.
Unless (Linus?) & Greg (or someone else) wants to develop a brand new “C” “2.0” lang + compiler designed around security…
Unless Google wants to change it’s Go lang licence…
…Rust it is.
Is Go (a more C like) alternative?
(2018: developer Voit wrote a Network driver (GNU Linux kernel module) in Go)
https://www.net.in.tum.de/fileadmin/bibtex/publications/theses/2018-ixy-go.pdf
C ixy vs Go ixy: performance (only) “10% slower then the C implementation under optimal circumstance” (optimal meaning: system’s CPU needs fast single threading)
“One of the biggest problem during development was low-level memory management.”
“Specifically register access has proven itself to be difficult in Go”
“On the other hand we were surprised about the garbage collection.”
“Originally named as the reason why Go is nor suited for systems programming, our analysis has proven otherwise”
“easier to read and does not require much understanding of the language itself in order to understand the code, especially compared to some C constructs like function pointer, pointer casting and other more intricate operations” (src)
the Go lang licencing MumboJumbo:
“Copyright (c) 2009 The Go Authors. All rights reserved.”
“Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
* Neither the name of Google Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
“AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.”
that’s not all… there is more licencing mumbojumbo for all those Free Software Foundation & lawyerzzz:
‘Additional IP Rights Grant (Patents)’
‘”This implementation” means the copyrightable works distributed by Google as part of the Go project.
Google hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section)
patent license to make, have made, use, offer to sell, sell, import, transfer and otherwise run, modify and propagate
the contents of this implementation of Go,
where such license applies only to those patent claims,
both currently owned or controlled by Google and acquired in the future,
licensable by Google that are necessarily infringed by this implementation of Go.
This grant does not include claims that would be infringed only as a consequence of further modification of this implementation.
If you or your agent or exclusive licensee institute or order or agree to the institution of patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that this implementation of Go or any code incorporated within this implementation of Go constitutes direct or contributory patent infringement,
or inducement of patent infringement, then any patent rights granted to you under this License for this implementation of Go shall terminate as of the date such litigation is filed.’
src: https://raw.githubusercontent.com/golang/go/master/PATENTS
While the sources of the Go lang are indeed accessible via github, it’s licence is neither GPL 2.0 nor GPL 3.0 nor Apache licence nor MIT licence and thus questionable if:
- Google can be trusted (?)
- the Go lang licence is “compact” but (currently) not at all Open Source compatible (not a word about if modifcations are allowed)
- why did Google not simply pick a “well known” Open source licence? https://opensource.org/licenses
One fine day, Google might to decide, to change the licence, and from this to:
- stop providing the (latest) source code (the old one yes, not the new one)
- re-distribute Go only in it’s binary form
- charge licence fees for it’s usage
- it is called: “building up dependencies, then cashing in on something that used to be free” (as Oracle did with Java)
- until it was out of the testing-phase
- and every developer and every company was using it/became dependant on it
- it is called: “building up dependencies, then cashing in on something that used to be free” (as Oracle did with Java)
Next problem: Rust (src here) was started by Mozilla, is used by Mozilla for Firefox, but Mozilla has build up financial dependencies to Google.
(Rust in contrast is licenced under MIT & Apache licence https://www.rust-lang.org/policies/licenses)
While this is all not really: K.I.S.S (the UNIX philosophy of Keep it Super Simple)
No dispair, just do your best.
Sticking to the default?
The problem is that systems designed & “Made in the 1970s” (C compiler, Phones, Mail), were not designed around security (because it was not really a problem in those days).
So…
- unless Google won’t change the Go lang licence to something Open Source compatible
- unless Linus & Greg or someone else wants to build a C 2.0 around security, Rust is it.
The Go lang licencing problem is the ZFS Oracle licencing problematic all over again:
In other words: Licences (money) have more than once, instead of enabling developers & users, have hindered developers & users.
Another company that M$ successfully killed by buying it…
Another example how Microsoft successfully made this planet worse:
IT WAS AN EXCELLENT learning platform, with high quality video learning courses with…
- 2000 courses in German
- 1200 courses in Spanish
- 1300 courses in French
- 500 courses in Japanese (as of September 2017)
- 0 in English? (a bit strange, but this company was from Austria and has focused on the EU market, that might be one reason)
Microsoft bought it up… now it is… dead? MS killed it. #wtf?
Now a high quality Video2Brain Rust videos would be needed (luckily – again – Youtube volunteers are chipping in THANKS! (MS maybe transfer some money to them? eh? thanks!))
PS: so that’s my take, could not ask that question via…
stackoverflow.com and serverfault.com suck and DESPERATELY needs competition
#linux #gnu #gnulinux #opensource #administration #sysops #dev #c #development #rust #go #google #security #itsec #cybersec #cybersecurity #kernel #linus #torvalds #mozilla #licence #licencing #patents #patent
Originally posted at: https://dwaves.de/2022/05/16/rst-vs-go-open-source-is-about-enabling-users-rust-lang-will-complement-c-around-the-gnu-linux-kernel-for-better-safety-amazon-microsoft-google-and-the-white-house-want-to-make-open-sourc/
“FOSS means that effort is shared across organizations and lowers maintenance costs significantly” (src: comment by JohnFOSS on itsfoss.com)
getting the naming right: Why is it GNU Linux and not just Linux?
[video width=”576″ height=”462″ mp4=”https://dwaves.de/wp-content/uploads/2022/01/Stallman-getting-the-naming-right-Why-is-ist-GNU-Linux-and-not-just-Linux.mp4″\]\[/video\]
- because it would given the developers who wrote the c compiler gcc (many contributors) and libc (many contributors) that compiles the kernel (and a lot of other stuff) no credit
Linus talking about GPL v3 vs GPL v2 (the better one)
[video width=”578″ height=”348″ mp4=”https://dwaves.de/wp-content/uploads/2022/01/GNU-Linux-DebConf-Linus-talking-about-GPL-v3-vs-GPL-v2-the-better-one.mp4″\]\[/video\]
- ### the (GPL 2.0) intented social contract is: “i give you sourcecode, give me back your changes”
- Linus drew criticism over his “stubbornness” to stick with GPL 2.0 e.g. Oracle’s Sun’s ZFS filesystem is released under a GPL incompatible licence, that as seen in this video statement, that is completely on purpose, just as it is (probably) on purpose by Oracle’s Sun to be DELIBERATELY incompatible with GPL (it seems to be a Microsoft-like a fake-support for the Open Source movement attempt companies like that “want to do marketing as Open Source but not really do Open Source”)
- GPL 2.0: (spdx.org calls it “Deprecated”? calling this the successor version)
- GPL-2.0+.txt
- GPL-2.0+.pdf (Courier like Font)
- GPL-2.0+ (Liberation Sans, Arial like font)
- GPL 2.0: (spdx.org calls it “Deprecated”? calling this the successor version)
- Tivoization /ˈtiːvoʊɪˌzeɪʃən/ is the creation of a system that incorporates software under the terms of a copyleft software license like the GNU General Public License (GNU GPL), but uses hardware restrictions or digital rights management (DRM) to prevent users from running modified versions of the software on that hardware. Richard Stallman coined the term in reference to TiVo‘s use of GNU GPL licensed software on the TiVo brand digital video recorders (DVR), which actively blocks users from running modified software on its hardware by design.[1][2] Stallman believes this practice denies users some of the freedom that the GNU GPL was designed to protect.[3] The Free Software Foundation refers to tivoized hardware as “tyrant devices”.[4] (creditz: wiki)
- Linux kernel licensing rules ============================
- The Linux Kernel is provided under the terms of the GNU General Public License version 2 only (GPL-2.0), as provided in LICENSES/preferred/GPL-2.0, with an explicit syscall exception described in LICENSES/exceptions/Linux-syscall-note, as described in the COPYING file.This documentation file provides a description of how each source file should be annotated to make its license clear and unambiguous. It doesn’t replace the Kernel’s license.The license described in the COPYING file applies to the kernel source as a whole, though individual source files can have a different license which is required to be compatible with the GPL-2.0:
GPL-1.0+ : GNU General Public License v1.0 or later <a href="https://spdx.org/licenses/GPL-2.0-or-later.html">GPL-2.0+ : GNU General Public License v2.0 or later</a> <a href="https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/LICENSES/preferred/GPL-2.0?h=v5.17-rc2">https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/LICENSES/preferred/GPL-2.0?h=v5.17-rc2</a> LGPL-2.0 : GNU Library General Public License v2 only LGPL-2.0+ : GNU Library General Public License v2 or later LGPL-2.1 : GNU Lesser General Public License v2.1 only LGPL-2.1+ : GNU Lesser General Public License v2.1 or later
src: https://docs.kernel.org/process/license-rules.html
- actually there is a whole folder “LICENCE” that is shipped with the kernel sources, which has the following subfolders:
- deprecated
- dual
- exceptions
- preferred
- here is a list of all sorts of free licences https://spdx.org/licenses/ (RSS Feed)- Can I use the word “Linux” or the Tux logo?
hereby creditz shall be given to Larry_Ewing for creating the Tux Logo
Linux is a registered trademark of Linus Torvalds and its use is governed by the Linux Trademark Institute. Please consult the following page for further information: Trademark Usage
The Tux penguin logo was created by Larry Ewing using Gimp software. It is free to use, including commercially, as long as you give Larry Ewing proper credit (“if someone asks”). For any other permissions, please reach out to Mr. Larry Ewing directly. (src)
- I heard that Linux ships with non-free “blobs” (pieces of software that are binary closed source)
- Before many devices are able to communicate with the OS, they must first be initialized with the “firmware” provided by the device manufacturer.
- This firmware is not part of Linux and isn’t “executed” by the kernel — it is merely uploaded to the device during the driver initialization stage.
- While some firmware images are built from free software, a large subset of it is only available for redistribution in binary-only form.
- To avoid any licensing confusion, firmware blobs were moved from the main Linux tree into a separate repository called linux-firmware.
- It is possible to use Linux without any non-free firmware binaries, but usually at the cost of rendering a lot of hardware inoperable.
- Furthermore, many devices that do not require a firmware blob during driver initialization simply already come with non-free firmware preinstalled on them.
- If your goal is to run a 100% free-as-in-freedom setup, you will often need to go a lot further than just avoiding loadable binary-only firmware blobs.
- src: https://kernel.org/category/faq.html
Links:
https://www.linuxplumbersconf.org/
because this site https://lpc2021.org/ is massively broken (WTF LPC?) who wants to watch the 2021 conference will have to rely on Google: https://www.youtube.com/playlist?list=PLVsQ_xZBEyN2c21jFUgqI2iMa094zXanH
manpage of man: man.man.txt
#linux #gnu #gnulinux #opensource #administration #sysops #gpl #fsf #eff #licence #licensing #license #gnu-linux #gcc #kernel #linus #stallman
Originally posted at: https://dwaves.de/2022/01/31/why-is-it-gnu-linux-and-not-just-linux-linus-talking-about-gpl-v3-vs-gpl-v2-the-better-one-the-social-gpl-contract-is-i-give-you-sourcecode-give-me-back-your-changes-non-free-binary/
ZFS is probably THE most controversial filesytem in the known universe:
“FOSS means that effort is shared across organizations and lowers maintenance costs significantly” (src: comment by JohnFOSS on itsfoss.com)
“The whole purpose behind ZFS was to provide a next-gen filesystem for UNIX and UNIX-like operating systems.” (src: comment by JohnK3 on itsfoss.com)
“The performance is good, the reliability and protection of data is unparalleled, and the flexibility is great, allowing you to configure pools and their caches as you see fit. The fact that it is independent of RAID hardware is another bonus, because you can rescue pools on any system, if a server goes down. No looking around for a compatible RAID controller or storage device.”
“after what they did to all of SUN’s open source projects after acquiring them. Oracle is best considered an evil corporation, and anti-open source.”
“it is sad – however – that licensing issues often get in the way of the best solutions being used” (src: comment by mattlach on itsfoss.com)
“Zfs is greatly needed in Linux by anyone having to deal with very large amounts of data. This need is growing larger and larger every year that passes.” (src: comment by Tman7 on itsfoss.com)
“I need ZFS, because In the country were I live, we have 2-12 power-fails/week. I had many music files (ext4) corrupted during the last 10 years.” (src: comment by Bert Nijhof on itsfoss.com)
“some functionalities in ZFS does not have parallels in other filesystems. It’s not only about performance but also stability and recovery flexibility that drives most to choose ZFS.” (src: comment by Rubens on itsfoss.com)
“Some BtrFS features outperform ZFS, to the point where I would not consider wasting my time installing ZFS on anything. I love what BtrFS is doing for me, and I won’t downgrade to ext4 or any other fs. So at this point BtrFS is the only fs for me.” (src: comment by Russell W Behne on itsfoss.com)
“Btrfs Storage Technology: The copy-on-write (COW) file system, natively supported by the Linux kernel, implements features such as snapshots, built-in RAID, and self-healing via checksumming for data and metadata. It allows taking subvolume snapshots and supports offline storage migration while keeping snapshots. For users of enterprise storage systems, Btrfs provides file system integrity after unexpected power loss, helps prevent bitrot, and is designed for high-capacity and high-performance storage servers.” (src: storagereview.com)
BTRFS is GPL 3.0 licenced btw.
bachelor projects are written about btrfs vs zfs (2015)
so…
ext4 is good for notebooks & desktops & workstations (that do regular backups on a separate, external, then disconnected medium)
is zfs “better” on/for servers? (this user says: even on single disk systems, zfs is “better” as it prevents bit-rot-file-corruption)
with server-hardware one means:
- computers with massive computational resources (CPUs, RAM & disks)
- at least 2 disks for RAID1 (mirroring = safety)
- or better: 4 disks for RAID10 (striping + mirroring = speed + safety)
- zfs wants direct access to disks without any hardware raid controller or caches in between, so it is “fine” with simple SATA onboard connections or hba cards that do nothing but provide SATA / SAS / NVMe ports or hardware raid controllers that behave like hba cards (JBOD, some need firmware flashed, some need to be jumpered)
- fun fact: this is not the default for servers. servers (usually) come with LSI (or other vendor) hardware raid cards, that might be possible to JBOD jumper or flash) but that would mean: zfs is only good for servers WITHOUT hardware raid cards X-D (and those are (currently still) rare X-D)
- but they would be “perfect” fit for a consumer-hardware PC (having only SATA ports) used as server (many companies not only Google but also Proxmox and even Hetzner test out that way of operation, but it might not be the perfect fit for every admin, that rather spends some bucks extra and wants to provide companies with the most reliable hardware possible (redundant power supplies etc.)
- maybe that is also a cluster vs mainframe “thinking”
- so in a cluster, if some nodes fail, it does not matter, as other nodes take over and are replaced fast (but some server has to store the central database, that is not allowed to fail X-D)
- in a non-cluster environment, things might be very different
- fun fact: this is not the default for servers. servers (usually) come with LSI (or other vendor) hardware raid cards, that might be possible to JBOD jumper or flash) but that would mean: zfs is only good for servers WITHOUT hardware raid cards X-D (and those are (currently still) rare X-D)
- “to EEC or not to EEC the RAM”, that is the question?:
- zfs also runs on machines without EEC but:
- in semi-professional purposes non-EEC might be okay
- for companies with critical data maximum error correction EEC is a must (as magnetic fields / sunflares could potentially flip some bits in RAM, then write the faulty data back to disk, ZFS can not correct that)
- “authors of a 2010 study that examined the ability of file systems to detect and prevent data corruption, with particular focus on ZFS, observed that ZFS itself is effective in detecting and correcting data errors on storage devices, but that it assumes data in RAM is “safe”, and not prone to error”
- “One of the main architects of ZFS, Matt Ahrens, explains there is an option to enable checksumming of data in memory by using the ZFS_DEBUG_MODIFY flag (zfs_flags=0x10) which addresses these concerns.[73]” (wiki)
- zfs also runs on machines without EEC but:
zfs: snapshots!
zfs has awesome features such as:
- snapshots:
- allows to recover from “ooops just deleted everything” errors and ransomeware attacks (unless the ransomeware is zfs “aware” and deletes all snapshots)
- extundelete does not work well for ext4
- testdisk -> photorec can recover data from ext4 but not the /directory/structure/filenames!!!
- ext4 can do snapshots as well with lvm2, but those lvm2 snapshots are more temporary “buffers” that can run out of changes-written-space and are then disgarded, so not “real” and “permanent” snapshots that can be restored or copied to a different system without time-limitation.
- zfs comes with data compression to safe disk space (won’t work well for “binary” data such as jpg or mp4 but anything text)
many more featuers:
- Protection against data corruption. Integrity checking for both data and metadata.
- Continuous integrity verification and automatic “self-healing” repair
- Data redundancy with mirroring, RAID-Z1/2/3 [and DRAID]
- Support for high storage capacities — up to 256 trillion yobibytes (2^128 bytes)
- Space-saving with transparent compression using LZ4, GZIP or ZSTD
- Hardware-accelerated native encryption
- Efficient storage with snapshots and copy-on-write clones
- Efficient local or remote replication — send only changed blocks with ZFS send and receive
(src)
how much space do snapshots use?
look at WRITTEN, not at USED.
https://papers.freebsd.org/2019/bsdcan/ahrens-how_zfs_snapshots_really_work/
performance?
so on a single-drive system, performance wise ext4 is what the user wants.
on multi-drive systems, the opposite might be true, zfs outperforming ext4.
it is a filesystem + a volumen manager! 🙂
“is not necessary nor recommended to partition the drives before creating the zfs filesystem” (src, src of src)
http://perftuner.blogspot.com/2017/02/zfs-zettabyte-file-system.html
RAID10?
there is no raid10 in zfs, only raid5, which means: at least one disk is used for checksums
- “raid5 or raidz distributes parity along with the data
- can lose 1x physical drive before a raid failure.
- Because parity needs to be calculated raid 5 is slower then raid0, but raid 5 is much safer.
- RAID 5 requires at least 3x hard disks in which one(1) full disk of space is used for parity.
- raid6 or raidz2 distributes parity along with the data
- can lose 2x physical drives instead of just one like raid 5.
- Because more parity needs to be calculated raid 6 is slower then raid5, but raid6 is safer.
- raidz2 requires at least 4x disks and will use two(2) disks of space for parity.
- raid7 or raidz3 distributes parity just like raid 5 and 6
- but raid7 can lose 3x physical drives.
- Since triple parity needs to be calculated raid 7 is slower then raid5 and raid 6, but raid 7 is the safest of the three.
- raidz3 requires at least 4x, but should be used with no less then 5x disks, of which 3x disks of space are used for parity.
- raid10 or raid1+0 is mirroring and striping of data.
- The simplest raid10 array has 4x disks and consists of two pairs of mirrors.
- Disk 1 and 2 are mirrors and separately disk 3 and 4 are another mirror.
- Data is then striped (think raid0) across both mirrors.
- One can lose one drive in each mirror and the data is still safe.
- One can not lose both drives which make up one mirror, for example drives 1 and 2 can not be lost at the same time.
- Raid 10 ‘s advantage is reading data is fast.
- The disadvantages are the writes are slow (multiple mirrors) and capacity is low.”
ZFS supports SSD/NVMe caching + RAM caching:
more RAM is better than an dedicated SSD/NVMe cache, BUT zfs can do both! which is remarkable.
(the optimum probably being RAM + SSD/NVMe caching)
ubuntu makes zfs the default filesystem
ZFS & Ubuntu 20.04 LTS
“our ZFS support with ZSys is still experimental.”
https://ubuntu.com/blog/zfs-focus-on-ubuntu-20-04-lts-whats-new
ZFS licence problems/incompatibility with GPL 2.0 #wtf Oracle! again?
Linus: “And honestly, there is no way I can merge any of the ZFS efforts until I get an official letter from Oracle that is signed by their main legal counsel or preferably by Larry Ellison himself that says that yes, it’s ok to do so and treat the end result as GPL’d.” (itsfoss.com)
comment by vagrantprodigy: “Another sad example of Linus letting very limited exposure to something (and very out of date, and frankly, incorrect information about it’s licensing) impact the Linux world as a whole. There are no licensing issues, OPENZFS is maintained, and the performance and reliability is better than the alternatives.” (itsfoss.com)
it is Open Source, but not GPL licenced: for Linus, that’s a no go and quiet frankly, yes it is a problem.
“this article missed the fact that CDDL was DESIGNED to be incompatible with the GPL” (comment by S O on itsfoss.com)
it can also be called “bait”
“There is always a thing called “in roads”, where it can also be called “bait”.
“The article says a lot in this respect.
“That Microsoft founder Bill Gate comment a long time ago was that “nothing should be for free.”
That too rings out loud, especially in today’s American/European/World of “corporate business practices” where they want what they consider to be their share of things created by others.
Just to be able to take, with not doing any of the real work.
That the basis of the GNU Gnu Pub. License (GPL) 2.0 basically says here it is, free, and the Com. Dev. & Dist.
License (CDDL) 1.0 says use it for free, find our bugs, but we still have options on its use, later on downstream.
..
And nothing really is for free, when it is offered by some businesses, but initial free use is one way to find all the bugs, and then begin charging costs.
And it it has been incorporated into a linux distribution, then the linux distribution could later come to a legal halt, a legal gotcha in a court of law.
In this respect, the article is a good caution to bear in mind, that the differences in licensing can have consequences, later in time.Good article to encourage linux users to also bear in mind, that using any programs that are not GNU Gen. Pub. License (GPL) 2.0 can later on have consequences for use having affect on a lot of people, big time.
That businesses (corportions have long life spans) want to dominate markets with their products, and competition is not wanted.
So, how do you eliminate or hinder the competition?
… Keep Linux free as well as free from legal downstream entanglements.”
(comment by Bruce Lockert on itsfoss.com)
Imagine this: just as with Java, Oracle might decide to change the licence on any day Oracle seems fit to “cash in” on the ZFS users and demand purchasing a licence… #wtf Oracle
Guess one is not alone with that thinking: “Linus has nailed the coffin of ZFS! It adds no value to open source and freedom. It rather restricts it. It is a waste of effort. Another attack at open source. Very clever disguised under an obscure license to trap the ordinary user in a payed environment in the future.” (comment by Tuxedo on itsfoss.com)
GNU Linux Debian warns during installation:
“Licenses of OpenZFS and Linux are incompatible”
- OpenZFS is licensed under the Common Development and Distribution License (CDDL), and the Linux kernel is licensed under the GNU General Public License Version 2 (GPL-2).
- While both are free open source licenses they are restrictive licenses.
- The combination of them causes problems because it prevents using pieces of code exclusively available under one license with pieces of code exclusively available under the other in the same binary.
- You are going to build OpenZFS using DKMS in such a way that they are not going to be built into one monolithic binary.
- Please be aware that distributing both of the binaries in the same media (disk images, virtual appliances, etc) may lead to infringing.
“You cannot change the license when forking (only the copyright owners can), and with the same license the legal concerns remain the same. So forking is not a solution.” (comment by MestreLion on itsfoss.com)
OpenZFS 2.0
“This effort is fast-forwarding delivery of advances like dataset encryption, major performance improvements, and compatibility with Linux ZFS pools.” (src: truenas.com)
tricky.
of course users can say “haha” 
“accidentally deleted millions of files” “no backups” “now snapshots would be great”
or come up with a smart file system, tha can do snapshots.
how to on GNU Linux Debian 11:
https://openzfs.github.io/openzfs-docs/Getting%20Started/Debian/index.html
note:
with ext4 it was recommended to put GNU Linux /root and /swap on a dedicated SSD/NVMe (that then regularly backs up to the larger raid10)
but than the user would miss out on the zfs awesome restore snapshot features, which would mean:
- no more fear of updates
- take snapshot before update
- do system update (moving between major versions of Debian 9 -> 10 can be problematic, sometimes it works, sometimes it will not)
- test the system according to list of use cases (“this used to work, this too”)
- if update breaks stuff -> boot from a usb stick -> roll back snapshot (YET TO BE TESTED!)
Links:
https://openzfs.org/wiki/Main_Page
#linux #gnu #gnulinux #opensource #administration #sysops #zfs #openzfs #filesystem #filesystems #ubuntu #btrfs #ext4 #gnu-linux #oracle #licence
Originally posted at: https://dwaves.de/2022/01/20/the-most-controversial-filesytem-in-the-known-universe-zfs-so-ext4-is-faster-on-single-disk-systems-btrfs-with-snapshots-but-without-the-zfs-licensing-problems/
Deepdocs Films - Nothing to Hide (VOSTFR, 2017) - Ploud Video France
Nothing to Hide (2017) est un #documentaire franco-allemand de Marc Meillassoux et Mihaela Gladovic, qui s'intéresse aux #effets de la #surveillance de masse sur les #individus et la #société.
Le film aborde la question de la surveillance de masse et son degré d'acceptation par la #population résumé par l'argument « je n'ai rien à cacher ».
#Documentaire dédié à l'acceptation de la #surveillance dans la #population à travers l'argument "je n'ai rien à cacher". "Passionnant" (Inrocks), "Qui ouvre les yeux" (Forbes), "Inquiétant" (France 24).
Plus d' #informations sur #NothingToHide et sa suite Disparaître sur deepdocs.euLe #film est mis à disposition gracieusement sur internet sous licence Creative Commons 4.0 CC-BY-NC-ND (Attribution - Non Commercial - No Derivatives) permettant:
1) de voir et de partager gratuitement le film en ligne en quatre langues ( #anglais, #français, #allemand, #espagnol) si les #auteurs et le site #internet sont cités.
2) d’organiser des #projections #publiques si celles-ci sont gratuites et ouvertes à tou(te)s. Les #lycées peuvent ainsi #télécharger et #projeter le #film.
3) Important: La #licence #CreativeCommons ND NC ne permet pas d’éditer, d’extraire et de remixer les images du film sans l’autorisation explicite des auteurs.
4) Pour les séances ou diffusions commerciales, les distributeurs sont invités à contacter les auteurs. Les diffusions organisées par des associations requérant des cotisations annuelles ou organisées dans le cadre d’un évènement payant (conférence, symposium) sont considérées comme commerciales.
আমি আগেই বলেছিলাম, এই 'গ্রাহক পরিষেবা কেন্দ্র' গুলো খুলে সিস্টেম করার ফলে সীমাহীন দূর্নীতি হবে। আর সেটাই এবার সত্যি প্রমাণিত হল। কোটি কোটি টাকার দূর্নীতি গ্রাহক পরিষেবা কেন্দ্রে। ১০হাজার, ২০হাজারের ওপরের ট্রানজাকশন ব্র্যাঞ্চে না করে ঐ কেন্দ্রগুলিতে করতে বাধ্য করছে বিভিন্ন ব্যাঙ্ক। আমি বলে দিচ্ছি, এটা ব্যাঙ্কের সব ট্রানজাকশন শুধুমাত্র অনলাইনে করতে বাধ্য করাবার ষড়যন্ত্রের প্রথম ধাপ। #গ্রাহকপরিষেবাকেন্দ্র #bank #customerservicepoint #private #licence #fraud
https://www.anandabazar.com/west-bengal/howrah-hooghly/huge-amount-of-money-laundering-in-a-public-owned-bank-alleged-gurap-residents-dgtld/cid/1302657
