0 Persons are tagged with #linus

#linus

theaitetos@diaspora.psyco.fr
theaitetos

Smells Like BRICSX

It appears the maintainers of #Linux are dumb enough to embrace the Grand Bifurcation and write off the #majority of the #human #population:

Following yesterday’s news first featured on #Phoronix of several #Linux #driver #maintainers being de-listed from their #maintainer positions within the mainline Linux #kernel over their connections to #Russia, #LinusTorvalds has today commented on the matter.

Since yesterday there’s been a lot of concern and mixed views over a number of Linux kernel maintainers being de-listed from the kernel’s MAINTAINERS file seemingly over being Russian or using Russian email addresses. In response to the patch posting from last week has also been proposals to revert that prior patch, some of the affected maintainers voicing their surprise over this sudden move, and some being upset over the lack of public clarity into the seemingly new “compliance requirements” imposed on the Linux kernel.

#GregKroah-Hartman who authored the patch dropping the various maintainers has yet to comment on the mailing list thread, but a few minutes ago Linus Torvalds chimed in with his opinion. Linux creator Linus Torvalds wrote:

“Ok, lots of Russian trolls out and about. It’s entirely clear why the change was done, it’s not getting reverted, and using multiple random anonymous accounts to try to “grass root” it by Russian troll factories isn’t going to change anything.

And FYI for the actual innocent bystanders who aren’t troll farm accounts – the “various compliance requirements” are not just a US thing.

If you haven’t heard of Russian sanctions yet, you should try to read the news some day. And by “news”, I don’t mean Russian state-sponsored spam.

As to sending me a revert patch – please use whatever mush you call brains. I’m Finnish. Did you think I’d be supporting Russian aggression? Apparently it’s not just lack of real news, it’s lack of history knowledge too.”

It’s not as if the Russians are simply going to throw up their hands and start using #Windows11. This promises to be the Mother of All Forks, and given the recently expressed position of #BRICS on the #illegality of #Western #sanctions, I doubt any of the BRICS countries are going to stick with the #original #Linux version.

This is where the fatal #flaw of having a weak central figure like Torvalds in charge inevitably comes into play. #Succession plans are difficult enough for strong Alphas to accomplish successfully, but when a mild-mannered Delta is the man in charge, some sort of future #debacle is all but guaranteed.

#Linus, it’s not that anyone thinks you’re supporting Russian aggression. It’s just that we assumed you wouldn’t be #retarded enough to publicly #endorse the #division of the #global #Linux #community and the creation of a #Sino-Russian #alternative #operating-system. But we were wrong.

6 Likes
3 Comments
1 Shares
canoodle@nerdpol.ch
SilouettE

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 Source more secure

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/

canoodle@nerdpol.ch
SilouettE

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 Source more secure

Open Source is about enabling users

“Amazon, Microsoft, Google” and the White House, want to help make Open Source more secure…

https://www.youtube.com/watch?v=U-8KopUKMzA

https://www.youtube.com/watch?v=U-8KopUKMzA

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.

https://en.wikipedia.org/wiki/Star_Trek:_First_Contact

https://en.wikipedia.org/wiki/Star_Trek:_First_Contact

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

https://en.wikipedia.org/wiki/Rust_(programming_language)

https://en.wikipedia.org/wiki/Rust_(programming_language)

https://en.wikipedia.org/wiki/Rust_(programming_language)

https://en.wikipedia.org/wiki/Rust_(programming_language)

https://foundation.rust-lang.org/

https://foundation.rust-lang.org/

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?

https://en.wikipedia.org/wiki/Go_(programming_language)

https://en.wikipedia.org/wiki/Go_(programming_language)

(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:

  1. Google can be trusted (?)
  2. the Go lang licence is “compact” but (currently) not at all Open Source compatible (not a word about if modifcations are allowed)
  3. 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:

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:

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/

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:

Ever heared of Video2Brain?

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

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/

One person like that
1 Comments
canoodle@nerdpol.ch
SilouettE

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 "blobs"

“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\]

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”)
    • 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?

Tux_FlickFlack

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

mandb.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/

raschmi@pod.geraspora.de
(((Tousled on Tour)))

Kürbis - Public Domain

Weiße Rose

#dwr #foto #fotografieren #mywork #goodmorning #fbg #fbd #jamendo #CC #mastobikes

#Tousled #Crane on #Tour

Guten Morgen #Welt!

Auf den großen #Kürbis habe ich nicht gewartet, …

… aber gefühlt wie #Linus, habe ich mich! Die dunkelsten und wahrscheinlich auch schmutzigsten #Feldwege, habe ich die Nacht aufgesucht und auf eine #Wolkenlücke gewartet. Keine Chance! Aber dies sind #Stunden die ich für mich gut nutzen konnte. Es gab zwar keine #Aurora #Borealis aber gute #Gedanken und #Ideen für mich.

Jemand 'n #Kaffee?

Bleibt senkrecht und gesund!

https://www.jamendo.com/track/1095394/aurora-borealis

#Frühstück #Kaffee #Kakao #Welt #Tee

11 Likes
5 Comments
canoodle@nerdpol.ch
SilouettE

DevC - Linus Torvalds "Nothing better than C"

[video width=”492″ height=”426″ mp4=”https://dwaves.de/wp-content/uploads/2021/08/Linus-Torvalds-Nothing-better-than-C.mp4″\]\[/video\]

what is great about C?

  • - the simplicity of the compiler that just run’s anywhere
    • still THE most resource efficient language
      • with C the user does not have to buy a new computer every 3 years, because of updates slowing down the system so much it become inefficient
    • still THE language that can speak best to hardware
    • the syntax can be called ugly sometimes, but not as ugly as C++ X-D

everyone understands what this does:

cat boolstd.c
#include 
#include 

int main(void) {
    // set to true
    bool b1 = 1;

    // this is correct, it will print
    if(b1)
    {
        printf("Bool b1 is true \n");
    }

    // set to false
    _Bool b2 = 2;

    // this is false, will not print
    if(b2 == false)
    {
        printf("Bool b2 is false \n");
    }

    // requires 
    bool b3 = true;

    // this is correct, it will print
    if(b3 == true)
    {
        printf("Bool b3 is true \n");
    }

    // requires 
    bool b4 = false;

    if(b4 == false)
    {
        printf("Bool b4 is false \n");
    }
}

the problems of C:

  • security problems need to be adressed (all those buffer over- and underruns)

… security/safety plus multi core computing is what RUST tries to adress

RUST the safer C/C++?

https://dwaves.de/2019/08/17/rust-most-loved-programming-language-ever-c-with-safety-new-programming-language-from-mozilla-for-mozilla-and-safety-now-also-with-step-debugging/

#linux #gnu #gnulinux #opensource #administration #sysops #dev #devrust #rust #devc #c #linus

Originally posted at: https://dwaves.de/2021/08/19/devc-linus-torvalds-nothing-better-than-c/