For anyone perhaps not aware, they're talking about speculative CPU execution. In essence, it's where a CPU will try to predict the next set of instructions and load them into the CPU cache for execution, even though they may not be the actual instructions that will be run. It's a way to try to increase performance. It's led to serious security vulnerabilities like Spectre and Meltdown.
@@552jacki3 Yes, that's one aspect of it. Also out of order operations. I don't have time to write a thesis about it in the YT comments section, just trying to give people a basis of the conversation.
@@y00t00b3r Thank you! I like to try to explain things in a way that's not overly technical and hopefully give enough info that someone can look into it in more detail if they wish.
It sounds like Linus or someone in the kernel developer community should write a book about common mistakes when developing processors for the server space and how to avoid them.
Or stop trying to do the job of processor vendors, without any info and having to probe and write custom code to get specific return codes, when the vendors don't provide this, it's not his job to have to dig into, what isn't publicly exposed, as a priority required in creation of a kernel. His A.D.D shows.
Open source instruction set is different than open source hardware. If RISC-V gets put into the server space there is no guarantee that the open source instruction set will translate to open source hardware design is it possible yea because the instruction set is open source but most hardware companies don't want to give away their implementations of the instruction set for free.
I disagree on what companies will give away for free. We already see huge contributions to open source from all manner of organisations and there is power in having a hand in open source. But I think what it will translate to is another layer of fragmentation. RISC-V should not even be called an instruction set. Since anyone will mix and match it sounds like a catalogue to me although I’m not an expert on it. Adhering to the same handful of instructions for all complex operations as Jim Keller points it out is a great idea but will lead to huge variability for the end user who will typically know nothing about why their compliant hardware performs differently to other compliant hardware that does deviate for the same reasons commercial ISAs already do. This isn’t to say RISC V isn’t a brilliant idea. But if Linux is any indication, it will probably be a patchwork of ideas dominated by corporate giants, with end users dealing with transparent yet bewildering decisions. X vs. Wayland comes to mind. Or all the issues that came with systemd. This has already happened in the past where computing had all kinds of bespoke hardware. But I’ve go to admit the RISC V foundation has undoubtedly thought about all of this.
I could and know of about a dozen people who could implement a RISC-V with no more notes than they could write on the palm of their hand. It's not a difficult architecture that really needs people to give their implementation designs away.
That is not about instruction set, at all. That is about RISC-originated technologies of execution optimization - caching, pipelining, branch prediction, superscalar, out-of-order and speculative executions.
Tomasulo is 1967. It isn't secret sauce. But if there were secret sauce, I doubt anyone would be telling me what it is on UA-cam comments, so I suppose it's fair to just say I can't expect an answer of the real things that might matter since.
@@semibiotic And doing that all securely and in the line of site of enough people to verify it's secure would be amazing and I would like it to happen but I have no illusions on it being open hardware in the end if it was I would be even happier cause then any up and coming college team could contribute and extend the implementation.
I do find it interesting that he has all this knowledge of the types of mistakes that get made but feels he can't communicate those things to them in ways they would listen to, even with the recent history of ARM repeating them to point to as a pattern.
ARM is closed source, he can't have a input there, or don't want to give a input because of that, i guess that why he was excited for RISC-V , that where inpput are appreciated and welcomed
i found that part quite interesting. basically he said that in general terms when you try something new and you are successfull, even then some mistakes will be made. I guess it is unavoidable if you don't have a time machine to get he knowledge from hindsight.
More than likely he would probably end up making the same mistakes. The kernel has had security issues as well. Security is a largely intractable problem. Its the whole, "there's no lock that isnt pickable" argument.
That is because those features (superscalar and speculative execution) were actually introduced on RISC/ARM side, and then adopted by x86 and were devepored in parallel on all platforms.
No computer is secure - read Ken Thompson's Turing Lecture "On Trusting Trust." A simple attack if you've ever had your hands on the compiler, assembler or microcode.
I wonder how many years it will take that the hardware manufacturers start adding such bugs intentionally with the intention to reveal them to the public some years later to boost new hardware sales, as everyone wants to update their old hardware to non-buggy new ones. I would be surprised if this hasn't been discussed some years ago already in some of the hardware companies.
The most "horrendous" thing about this secrecy is that mainly the people that abuse the problems are the ones that knows about it, instead of the people that can and want fix it.
Oh, we're talking about the government's grocery list of things you can and cannot do, including the secrecy of backdoors and tunneling. There's nothing like elite coders prioritizing the masquerade of... Pay no attention to those programmers inside your OS entering at will.
Oh, we're talking about the government's grocery list of things you can and cannot do, including the secrecy of backdoors and tunneling. There's nothing like elite coders prioritizing the masquerade of... Pay no attention to those programmers inside your OS entering at will.
it's why NASA picket Commodore's Amiga machines in their logistics & primary rocket computer controller in the late 80s & early 90's, because they where the only ones that gave them everything they wanted 100% open with all the papers, guides.. because everyone they asked said NO! like apple, atari, IBM and others ( for NASA ofc) but, others to like SCALA , newtek..and so on
FYI this took place on April 17, 2024 in Seattle. Too bad this date can't be seen anywhere in the video or in its description. Actually, the date of the event can't be found in the original video of the full keynote either...
If the hardware has at least one problem then the software can not solve it. I am paranoid about the lack of security of this hardware in my plans of building a server that runs bank-confidential apps (or medicare-confidential apps by example).
can't that be mitigated by compartmentalising? If only one app runs on the server no other software can exploit the hardware bug. I guess in most banks the software runs on specific hardware
@@thewhitefalcon8539 Since web developers force you to enable JavaScript execution for almost every webpage today, you have running tons of programs on your private client that can exploit vulnerabilities.
super cool discussion, makes you realise the importance of open source and big techs collaborating with the new and coming hardware and software techs to push towards a unified development scenario. That way everyone is working on something that takes the tech ahead in the broader sense and not just do it privately.
At least RISC-V has the benefit of hindsight. speculative execution exploits are now well known and understood. Trading security for speed will bite you in the ass. Security researchers will find you out. I don't expect this would be much of an issue for RISC-V unless it's designers have their heads in the sand with an it'll be all right attitude.
Er... there's just been like what.. 5 or 6 released CVE for V in the past few weeks and more continue being exposed.. Only reason M2 and M3 aren't more known as yet, is that nobody cares... nobody is going out of their way to buy processors, just to find vulnerabilities. They get revealed when people who know, have the time, decide to have a look and see what they see, when they've got access to hardware and time to deal. RISC-V as an open standard, is among the most likely to have open invitation vectors and doors to nowhere, being design 'features'!
Being attention defecit hyperactive and suffering from creation of the Linux kernel. Not only its creator, maintainer, developer, and security hand maid.. the entire universe of Linux.
Just a number pump if you are new to linux numbering. If the number after the first decimal point gets big for linus's liking he pumps the first number up.
Would having parts of a CPU being a FPGA that could be updated be the solution? I know that real hardware is better but we could maybe sacrifice something to fix that problem no?
Most likely not. CPUs are made to be brutally space efficient, while FPGAs sacrifice a lot of space and performance(!) for the ability to be reprogrammable. besides, current CPUs are already reprogrammable to a degree, with a bytemask loaded on boot.
@@MechMK1 I just imagine a normal CPU that just have a FPGA integrated with like a register that if changed could allow the FPGA to take parts of the jobs. At normal we could use it as a maybe slower PU. I think it would be cool, I don't know if it would make any sense in reality.
@@robotredkitten817 The point of an FPGA is that you're able to reprogram it to solve one specific algorithm extremely efficiently. They're not made for "general purpose computing". If you try to program an FPGA to be "generally usable" the same way a CPU is, then you'll trade your amazing 5 GHz 16 core CPU for a 100 MHz FPGA. And trust me, you don't want that.
Thankfully, you stated what so many missed. Thank you! idk - people.. RISC-V and open standards, invites open inspection, which somehow means, less vulnerabilities exposed? No.
They said the same mistakes will probably be made again. That's a bet with a high probability of success. Not a misunderstanding, not a misconception. Unless you want to play word games with what is a standard and what is an implementation and that not necessarily all implementations will employ spleculative execution. But you see, I'm doing both of our jobs in this discussion.
@@seriouscat2231 It's not a word game, in this case it's an important distinction. The idea that RISC-V is opensource is plain wrong. It's an *open standard*, but almost all of the available RISC-V implementations are closed source. So none of the benefits of open source that Linus mentions are applicable.
@@jaskij, I watched the relevant part again and could not see any misunderstanding. Only the interviewer chose his words poorly once, but everyone understood what he wanted to say. Seems to me you're bringing your personal wishes and frustrations into this. Still zero misconceptions and zero misunderstandings. You have misunderstood that they have misunderstood something.
@@mrhassell Engineering wont solve security, just like it wont produce an unpickable lock. There will always be a compromise between security and usability.
I Love Linux and torvalds the creator there ove. I also learn so much from Comments always in TECH related youtube channels, Many a tme Comments have allowed me, a 74 Years Old with Senility the Answer to Problems I have I still Build Tower based Unix Computers, however I am going blind, only 1 Eye works. Hard to work on Mother Boards with one eye.
Ryzen 5800X on x370 for main system. Am interested in ARM Snapdragon X Elite for my next companion PC... But seems ARM oversold Linux support in a statement, and the varying notebooks available are posing interesting problems from multiple angles for the time being. 😕
My frustraition is that is things ALLWAYS breaks in Linux. I think i spend about 30 hours a week to try figuring what is going on. This week, it was My am5 ethernet on x670-e mb. An ancient problem that has never been fixed around ASPM or performance profiles. So what the ethernet does, it hibernating or updates to slow. Then I lose connection, then the connection dont come back or the card wakes up. Until i restart the pc. This happen atleast once every 3 hours. Then Linux devs are like, yeah.. its been there for over 10 years.. 10 years? Then the platform im on its 2 years old. Then you start to wonder.. what in the world is going on with linux. Why is no one fixing the issue. Now im in Disabling ASPM in Bios, then it works. Then another problem is there.. then you get the answear, you need to go in to bios and disable that. My whole bios is about to get disabled soon. Oh btw, you are on nividia card. you need to disable the firmware. I wonder how much we need to disbable soon
Hardware security becoming more and more relevant makes me think about Apple’s platform where all devices up to and including an $11k+ Mac Pro are non-upgradable.
Only reason more M2 / 3 CVE exploits don't exist.. yet.. 1. Nobody cares. 2. Apple don't provide the hardware to anyone who knows or is able to help them. 3. Nobody gonna buy that!
That sounds like quite simply if you're going to do something complicated in hardware, it needs to have *some* controls in software so the knobs can be turned in case something goes fucky wucky. You'd think that's common sense. I have coded in Python and JS and NASM and done an FPGA and a virtual mplementation of RISC-V. I would *love* to hear specific things that RISC-V should learn from its predecessors. It's not quite perfectly pure hardware but it's surprisingly closer than x86 or ARM and was dramatically nicer to build.
The two biggest lesson are probably: Document everything! Even the implementation details. And: When you go against the spec be very careful that there are no ways to take advantage of that as an attacker. In particular when doing speculative execution be absolutely sure the are no side effects. Specter and Meltdown have shown that things as innocent as cache timing can be enough to leak information. Maybe a third lesson is to have hardware feature flags that can be updated to turn some stuff of, but that only helps after a vulnerability is found in the wild.
Why so serious Linus? You are not responsible for Intel, AMD or Qualcomm. CVE exploits, are not 'public' enough? What's missing? Spectre is an issue, new variants expand the base, proof of concepts recently announced for RISC mobile and Mali GPU, formation relating to driver and cache pointers. They're all speculative, all read cache or pointer/stack overflows, even oldest exploits ever made, going back forever, all started here! Only difference, having become microcodes in processor evolutions, instruction set extensions, which may be either patched.. or ignored.
Hardware should be effective and efficient without any assumptions. Software should be aware of cache and memory, and use such as applicable. It only when hardware design tries to do software tasks, these issues result. Hardware if it focused on speed of execution based on explicit execution calls received, it would up to the software to provide applicable performance. This is in effect what RISC proved... hardware does its instructions fast, and software decides how instructions are queued. We need to stop trying to make hardware guess what software wants, and we need to stop software from defaulting to letting the hardware figure out what we need, we on software side, should explicitly ask for what we need... say own population of cache. Firmware does this all the time... drives the hardware, because device hardware is basically simplistic, if not 'dumb' from a logic perspective. But of course CPU designers think they know better, and think software designers are not smart enough to do their job... this is really exactly what Linux said... because the hardware is closed, software side cannot contribute to the solution process before the hardware is locked in.
looking at some comments and at how messed up the title is it's clear this guy is actually AI generating at least some of his videos. Always has been the linux fast food kind of videos but still.
I guess there a lot NDA stuff and hinder open src is not easy task. As well there should be other people with NDA had to work on base on open src under NDA branch off stuff.
Linus was frusted with Minix and create Linux. He was frusted with code share and he create Github. Was frusted with people using Github to store 'pron' and he sell Github. He was frusted with Nvidia's drivers and say to NVidia go 'frack'. I think frustration is Linus natural spirit state.
Not quite. The internet was invented in 1969(Nice) Linux was invented in 1991 (Could've had a hedgehog as their mascot) The internet predates Linux by a sizeable time.
The real solution is the Mill architecture, or something like it. RISC-V may provide hope for an open platform, but it will never lead to secure systems or an escape from the nightmare of monolithic kernels and browsers. If only we could have invested in an open Mill instead, the computing landscape today might be very different (and much better).
4 місяці тому+1
is this an AI generated shit?"!? this not how ive ever seen linux torvalds!
@@michalsvihla1403 Well, OF COURSE I would like an ANSWER. MOST if not ALL hardware will run Windows. Only a SUBSET of that will allow Linux to run - at least that's what I've heard from EXPERTS, who insist that FIRST you should make sure that Linux supports ALL of your hardware!
@@jakobw135 Linux supports a much larger amount of architectures than windows which only works on x86 and, more recently, arm processors. Almost every machine from the last 3 decades can run some linux distro with enough prodding.
@@phithegamer5787 Nice and re-assuring to know, BUT, why do (SUPPOSED) experts insist that you FIRST have to make sure that your LINUX BOX runs the OS properly?
An internet router like MIPS/debian-mipsel could be made but, rather than STM32, it would have a _(debian blob compatible)_ CPU (RISC-V) as a Public-Domain _(or somewhere between copyleft and GPLv2 could do, with AGPLv3 for network niggling details)_ Open-Source microarchitecture RISC-V CPU _(expecting a Linux monolithic kernel too boot from 4 of HDD or SSD SATA with RAID10)_ in it and then some known-quantity amount of RAM like say 4GB in a _(also unregistered RAM compatible and ECC)_ desktop/ECC-compatible RAM slot and a _(also unregistered RAM compatible and ECC)_ desktop/ECC-compatible slot that can (optionally) take another 16GB _(topping it up to 20GB is for some reason it needed to),_ and just make it DDR3 so it can choose between its unregistered and registered RAM settings. It would be 6G sim-card compatible even though it has ADSL2 via RJ11 ports near the 100Mbps RJ45 ethernet and the 8 USB ports _(and a WAN and other port for straight-to-fibre)_ and it could have Wifi6 and Bluetooth 5.2 and pitch-roll-yaw accelerometer _(like a wii-remote has)_ and a compass and LoRaWAN _(RX and TX send and receive)_ and drivers for S-Band and Ku-Band and software-defined-Radio GNU radio with slowscan TV mode for data. It would have a PCI-e 4x slot at Gen3 to be able to take a better NIC card with VMDq and SR-IOV if better ethernet speeds are need compared to the 100Mbps LAN (not WAN) ports. It would have an IEEE1284 (bootable) and a couple of Serial COM ports to remote into it, and a JTAG and MIPI interface. However, the 100Mbs RJ45 Lan ports on it would be deliberately there for a small driver. An interface to add PoE would be there by you would need to add it later. The RJ11 would also be able to plug in VOIP device, again to add later, keeping cost down. It would have a circuit to detect a battery added later even though it does not come with one and instead, in a power-outlet, would work in a mains electrical plug socket (wall wart). Then _(and this is the important bit)_ basically just give it _(via some whip-round)_ to the Linux Foundation and ask Linus to say what he wants from the instruction set in the RISC-V CPU. Ask Stallman too _(if he can do)._ The router RISC-V CPU would be unlikely to have better processing than say an A53 with protection-rings. So commercially available routers would be able to make glitzy fancy routers with other features without tis open-source router displacing their market value. This open-source router instead would be designed to be solid and do a workman like job and nothing particular fancy. It simply has that 6G and Bluetooth and WiFi at that reasonably modern level so that is continues to work well enough for many years to come. It would also expect to take a MFA FIDO2 hardware security key in a USB port just in case that helps things in future projects. It would probably need some of the USB ports to be capable (or upgradeable) of being USB3.2 with decent power _(converting to or from USB-C)._ Linux is not pronounce like his name 'Linus' _(a running in-joke for geeks),_ so the router should have a naming convention along those lines _(being deliberately slightly inaccurate)_ as with its default Operating System distro. So the Distro could be called thr34k because it is like 'freak' (the previous candidate name for Linux) but spelt wrongly as though it is the number but then the letters are post ironically switched to numbers just to be even wronger. The router itself could be called _"Lee Noose"_ because it is about time, once again, that we all came up with yet another wrong way to say his name. The router should have a couple of interfaces to allow the user to optionally plug in a couple of 128x32 pixel monochrome LCD screens. The CPU could be called the "St. All m'Anne" _(because it is a corruption of Richard Stallman)._ We'll just have to come up with a reason why it is like that and never actually admit it to Stallman _(or Torvalds for his one)_ as to why the name of the CPU is that. We'll say perhaps that The name represents a saint of everything (i.e "all") associated with my Anne. So, let's assume Anne is some person or whatever, and she is "my Anne" like maybe she is betrothed or something. So it means _"The Saint of everything pertaining to my Anne"_ when it is written _"St. All m'Anne"._ It's a stretch but without it, somebody will need to come up with something better. Anne will be represented in a cartoon avatar sticker stuck on the router and then can be a character in SuperTuxKart because mascots need to exist for as many GNU linux things as possible. That avatar and the _"Lee Noose"_ avatar will probably be some sort of fluffy mascot other people haven't already used, rather than an actual human. It would have a 2nd CPU socket just in case it struggles. The RISC-V should have an FPU in it. The point is that it would become popular enough without flooding the market and Stallman and Linus would simply be able to tell the makers in advance what they want from it. It probably would be able to take a modest low-power graphics-card in the PCIe slot and run it is a server with a GUI or desktop computer but that is not the main focus of it. That does mean however that if there is a desire for a "safe option" CPU, the router would have established it, even though it would be quite a tame CPU compared to actual laptops, smartphones and desktop computers _(and big-servers)._ Thereby when people make other _(fancy)_ RISC-V CPU chips _(be they public domain or not),_ they can have the point-of-reference to know what basic little CPU other people are already happy with looks like. The router will be have a target audience like the One-Laptop-Per-Child project in the past, _(so you can buy one in USA, UK and so on and the increased price)_ but displaced people _(with an identity card)_ who want to get one can buy or earn one such as if they set up a business like a coffee shop or something like that _(or they maybe just want to use it in their dwelling on as a carputer but on a bike)._ The router _(essentially with a ALSA compatible 24-Bit soundcard with MIDI on it)_ would have a mic-in and line-in (both stereo) and a stereo line-out just in case not having one causes a problem with VOIP somehow later. It would expect ogg-vorbis-theora even though it could probably do other things. Having MIDI (a joystick port) is useful but is there to ensure linux has a go-to MIDI standard just in case somehow the sound-card existing on the router (largely for VOIP) encounters a problem as a result of not having MIDI. If Torvalds and Stallman refuse to take the money to do it, have some other bargaining chip they are after to incentivise them to do it for that reason. There must be something. The benefit everybody else would have is that it would save a whole bunch of ballache regarding computing-ambiguity _(especially pertaining to the deciduous nature of Reduced Instruction Set Chips)_ and would brighten up these grumble-pill videos of two blokes sitting on 2 chairs like something out of a year 2000 Public Access TV channel show. My comment has no hate in it and I do no harm. I am not appalled or afraid, boasting or envying or complaining... Just saying. Psalms23: Giving thanks and praise to the Lord and peace and love. Also, I'd say Matthew6.
And 8 days later after this video half the internet gets an update from one company and it just so happens to be they didn't test a kernel update. I think it was done on purpose Microsoft and crowdstrike. Just to see how much control they have
@@seriouscat2231 after doing extensive searching the CEO of crowdstrike is tied to Black Rock black rock is tied to the person who shot at the president and this happened after the president was shot but not killed. Bread crumbs don't lie they tell a story if you're willing to be unbiased about the story
What about the growing number of "diversity quotas" in Linux Foundation? Are they imposed by the corporate donors? Does he know how much bloat and useless code they pouring in the kernel? Is he okay with those politics?
Look at how much he's aged lately, poor man's suffering knowing his hands are tied and there's nothing he can do to stop the madness. He's seeing his life's work collapse thanks to the new generation of maintainers not knowing what they are doing and ruining everything. This is what happens when you make your project be part of a large corporate environment... everything becomes political, and they focus more on diversity, meetings and sprints rather than actual software development, and we end up with bloat everywhere... With bloat like this, who needs Windows...?
@@tiranito2834 While I can appreciate the sentiment, the reality is that he's kowtowed to these things and accepted them, as shown by some of his mastodon posts(at least publicly), sooooo... you get what you deserve, I guess?
"Speaks on Linux Hardware SECURITY Issues" - There is nos such thing as Linux Hardware Security Issues. Either they are hardware security issue but then they are not related to Linux at all and will affect any operating system on earth or they are Linux issues but then they are not hardware issues as there is no Linux hardware, Linux is a software operating system kernel.
@@SnowDaemon One of things holding back and preventing Linux from making progress is gatekeepers that zealots and similar people. because of that, many important problems are. NOT solved. Hardware is one of them since those zealots cause regression for desktop environment where Hardware Companies are invested in.
the fact that he didn't changed LInux from GPL2 to GPL3 is a strong indicative of his opinion, he knew that linux wouldn't grow forcing people/companies to open source their code(one opinion that i agree with) instead, because it's free and people/company don't need to open source their code, it grew to dominate every market possible
@@SkyFly19853 > Hardware is one of them since those zealots cause regression for desktop environment where Hardware Companies are invested in. how they do that?, i know that these type of people exist, but they aren't the majority
@SkyFly19853 you keep saying "zealots and gatekeepers". But can you give me an example? I don't think you're wrong, I just want to know why you have these opinions. It seems like you're just saying stuff but have no idea what's actually going on. Because I don't recall Linus preventing financial growth. If anything, he's been one of the main promoters of RHEL and what they're doing. I'm just trying to figure out who you're talking about and what they've done...
he got challenge by me now...sure it will sting him where it hurts now...thank god i did what i must do, replace the dooch someone really cares for real linux kernel...for he, linus is turning his kernel into extension of windows nt kernel lately...might as well throw entire legacy of his out the windows of his...basically linux and windows nt kernel are pretty much alike by now. Both run windows programs...only difference ...amd drivers run lot better under real windows ...not windows with lock up penguin behind it with tears in its eyes . Thats frustrated to see Microsoft ate our linux kernel
init systems like OpenRC, runit, or SysV init.. are superior, well I suppose.. You are saying Rust isn't a flavour, you.. require. Memory safety to reduce bugs and writing kernel drivers, is one of the key points he's addressing this on. Bunch of CVEs relate directly to this, all made recently in RISC lol If they were written in Rust, the problem wouldn't exist.
Which guy is a moron? The one who created Linux when he was 23yrs old (and also Git) or the one interviewing him who's been a SWE for over 40 yrs and is head of OpenSource at Verizon?
What type of CPU are you using?
5800x wbu?
Amd 7900x of course.
4300u with Linux mint
3700x
M3 😅
For anyone perhaps not aware, they're talking about speculative CPU execution. In essence, it's where a CPU will try to predict the next set of instructions and load them into the CPU cache for execution, even though they may not be the actual instructions that will be run. It's a way to try to increase performance. It's led to serious security vulnerabilities like Spectre and Meltdown.
You're referring to branch prediction
@@552jacki3 Yes, that's one aspect of it. Also out of order operations. I don't have time to write a thesis about it in the YT comments section, just trying to give people a basis of the conversation.
@@Onyx-it8gk excellent summary
@@y00t00b3r Thank you! I like to try to explain things in a way that's not overly technical and hopefully give enough info that someone can look into it in more detail if they wish.
Ur explanation is smooth, you got a blog?
It sounds like Linus or someone in the kernel developer community should write a book about common mistakes when developing processors for the server space and how to avoid them.
It's like writing a book on what is happening on github, he did give us git for this purpose I suppose.
Or stop trying to do the job of processor vendors, without any info and having to probe and write custom code to get specific return codes, when the vendors don't provide this, it's not his job to have to dig into, what isn't publicly exposed, as a priority required in creation of a kernel. His A.D.D shows.
Open source instruction set is different than open source hardware. If RISC-V gets put into the server space there is no guarantee that the open source instruction set will translate to open source hardware design is it possible yea because the instruction set is open source but most hardware companies don't want to give away their implementations of the instruction set for free.
I disagree on what companies will give away for free. We already see huge contributions to open source from all manner of organisations and there is power in having a hand in open source. But I think what it will translate to is another layer of fragmentation. RISC-V should not even be called an instruction set. Since anyone will mix and match it sounds like a catalogue to me although I’m not an expert on it. Adhering to the same handful of instructions for all complex operations as Jim Keller points it out is a great idea but will lead to huge variability for the end user who will typically know nothing about why their compliant hardware performs differently to other compliant hardware that does deviate for the same reasons commercial ISAs already do. This isn’t to say RISC V isn’t a brilliant idea. But if Linux is any indication, it will probably be a patchwork of ideas dominated by corporate giants, with end users dealing with transparent yet bewildering decisions. X vs. Wayland comes to mind. Or all the issues that came with systemd. This has already happened in the past where computing had all kinds of bespoke hardware. But I’ve go to admit the RISC V foundation has undoubtedly thought about all of this.
I could and know of about a dozen people who could implement a RISC-V with no more notes than they could write on the palm of their hand. It's not a difficult architecture that really needs people to give their implementation designs away.
That is not about instruction set, at all. That is about RISC-originated technologies of execution optimization - caching, pipelining, branch prediction, superscalar, out-of-order and speculative executions.
Tomasulo is 1967. It isn't secret sauce. But if there were secret sauce, I doubt anyone would be telling me what it is on UA-cam comments, so I suppose it's fair to just say I can't expect an answer of the real things that might matter since.
@@semibiotic And doing that all securely and in the line of site of enough people to verify it's secure would be amazing and I would like it to happen but I have no illusions on it being open hardware in the end if it was I would be even happier cause then any up and coming college team could contribute and extend the implementation.
I do find it interesting that he has all this knowledge of the types of mistakes that get made but feels he can't communicate those things to them in ways they would listen to, even with the recent history of ARM repeating them to point to as a pattern.
ARM is closed source, he can't have a input there, or don't want to give a input because of that, i guess that why he was excited for RISC-V , that where inpput are appreciated and welcomed
i found that part quite interesting. basically he said that in general terms when you try something new and you are successfull, even then some mistakes will be made. I guess it is unavoidable if you don't have a time machine to get he knowledge from hindsight.
More than likely he would probably end up making the same mistakes. The kernel has had security issues as well.
Security is a largely intractable problem. Its the whole, "there's no lock that isnt pickable" argument.
@@jshowao he?
That is because those features (superscalar and speculative execution) were actually introduced on RISC/ARM side, and then adopted by x86 and were devepored in parallel on all platforms.
No computer is secure - read Ken Thompson's Turing Lecture "On Trusting Trust." A simple attack if you've ever had your hands on the compiler, assembler or microcode.
I wonder how many years it will take that the hardware manufacturers start adding such bugs intentionally with the intention to reveal them to the public some years later to boost new hardware sales, as everyone wants to update their old hardware to non-buggy new ones. I would be surprised if this hasn't been discussed some years ago already in some of the hardware companies.
Trust your mechanic to plug your holes
Trust him to make more somewhere else
Genius marketing tbh
Sounds criminal.
@@jnawk83so Tuesday in leading companies
They probably do it at behedst of government
The most "horrendous" thing about this secrecy is that mainly the people that abuse the problems are the ones that knows about it, instead of the people that can and want fix it.
lol - true! very true
Oh, we're talking about the government's grocery list of things you can and cannot do, including the secrecy of backdoors and tunneling.
There's nothing like elite coders prioritizing the masquerade of... Pay no attention to those programmers inside your OS entering at will.
Oh, we're talking about the government's grocery list of things you can and cannot do, including the secrecy of backdoors and tunneling.
There's nothing like elite coders prioritizing the masquerade of... Pay no attention to those programmers inside your OS entering at will.
Oh, we're talking about the government's grocery list of things you can and cannot do, including the secrecy of backdoors and tunneling.
thanks for including the full interview link!
it's why NASA picket Commodore's Amiga machines in their logistics & primary rocket computer controller in the late 80s & early 90's, because they where the only ones that gave them everything they wanted 100% open with all the papers, guides.. because everyone they asked said NO! like apple, atari, IBM and others ( for NASA ofc) but, others to like SCALA , newtek..and so on
FYI this took place on April 17, 2024 in Seattle.
Too bad this date can't be seen anywhere in the video or in its description.
Actually, the date of the event can't be found in the original video of the full keynote either...
If the hardware has at least one problem then the software can not solve it. I am paranoid about the lack of security of this hardware in my plans of building a server that runs bank-confidential apps (or medicare-confidential apps by example).
can't that be mitigated by compartmentalising? If only one app runs on the server no other software can exploit the hardware bug. I guess in most banks the software runs on specific hardware
Speculative execution attacks should only worry you if attackers can run code on your server
@@thewhitefalcon8539 Since web developers force you to enable JavaScript execution for almost every webpage today, you have running tons of programs on your private client that can exploit vulnerabilities.
super cool discussion, makes you realise the importance of open source and big techs collaborating with the new and coming hardware and software techs to push towards a unified development scenario. That way everyone is working on something that takes the tech ahead in the broader sense and not just do it privately.
At least RISC-V has the benefit of hindsight. speculative execution exploits are now well known and understood. Trading security for speed will bite you in the ass. Security researchers will find you out. I don't expect this would be much of an issue for RISC-V unless it's designers have their heads in the sand with an it'll be all right attitude.
Er... there's just been like what.. 5 or 6 released CVE for V in the past few weeks and more continue being exposed..
Only reason M2 and M3 aren't more known as yet, is that nobody cares... nobody is going out of their way to buy processors, just to find vulnerabilities. They get revealed when people who know, have the time, decide to have a look and see what they see, when they've got access to hardware and time to deal. RISC-V as an open standard, is among the most likely to have open invitation vectors and doors to nowhere, being design 'features'!
I think the way you linked to the original video is weird.
With the new UI in description for links it was difficult to find.
Maybe put it on top?
Linux foundation spends only 2% of its revenue on kernel development. Maybe they should spend some money on hardware?
Look who the major funders are of the Linux foundation. It goes without saying as to why kernal funding has decreased.
I understand your frustration
Btw what is the context of the interview? Care to explain?
No
Being attention defecit hyperactive and suffering from creation of the Linux kernel. Not only its creator, maintainer, developer, and security hand maid.. the entire universe of Linux.
Whats coming on Kernel 7.0!?
Just a number pump if you are new to linux numbering. If the number after the first decimal point gets big for linus's liking he pumps the first number up.
A bunch more CVE making it a pAwN n 0daY fo freeze speshial release!
Less funding.
@@nathanbedford9178
Interesting. Why ?
Coming with the year of linux desktop happening
Would having parts of a CPU being a FPGA that could be updated be the solution? I know that real hardware is better but we could maybe sacrifice something to fix that problem no?
that’s interesting
Most likely not. CPUs are made to be brutally space efficient, while FPGAs sacrifice a lot of space and performance(!) for the ability to be reprogrammable. besides, current CPUs are already reprogrammable to a degree, with a bytemask loaded on boot.
@@MechMK1 Would contribute to a larger attack surface as well.
@@MechMK1 I just imagine a normal CPU that just have a FPGA integrated with like a register that if changed could allow the FPGA to take parts of the jobs. At normal we could use it as a maybe slower PU. I think it would be cool, I don't know if it would make any sense in reality.
@@robotredkitten817 The point of an FPGA is that you're able to reprogram it to solve one specific algorithm extremely efficiently. They're not made for "general purpose computing". If you try to program an FPGA to be "generally usable" the same way a CPU is, then you'll trade your amazing 5 GHz 16 core CPU for a 100 MHz FPGA. And trust me, you don't want that.
It's time for RISC to shine! Raspberry pi and custom made laptops for the win!
It already does, pretty happy with my Apple M2
The whole RISC-V part of the discussion... so many misunderstandings and misconceptions.
Thankfully, you stated what so many missed. Thank you! idk - people.. RISC-V and open standards, invites open inspection, which somehow means, less vulnerabilities exposed? No.
They said the same mistakes will probably be made again. That's a bet with a high probability of success. Not a misunderstanding, not a misconception. Unless you want to play word games with what is a standard and what is an implementation and that not necessarily all implementations will employ spleculative execution. But you see, I'm doing both of our jobs in this discussion.
@@seriouscat2231 It's not a word game, in this case it's an important distinction. The idea that RISC-V is opensource is plain wrong. It's an *open standard*, but almost all of the available RISC-V implementations are closed source. So none of the benefits of open source that Linus mentions are applicable.
@@jaskij, I watched the relevant part again and could not see any misunderstanding. Only the interviewer chose his words poorly once, but everyone understood what he wanted to say. Seems to me you're bringing your personal wishes and frustrations into this. Still zero misconceptions and zero misunderstandings. You have misunderstood that they have misunderstood something.
Linux Torvolds? Maybe proofread your titles?
Came here for exactly this reason rofl.
Date of this interview?
2 months ago. Please refer to the link is desc
@@SavvyNikthe link to the Linux foundation, their YT channel, or the original video is currently not in the description
Yeah can't find it either.
looks like editbulk is having some issues.
UA-cam is sadly full of bad clips. No date. No description of the event depicted. Doesn't clearly link to the source video. The usual.
Security will always be a problem.
No problem! Stop worrying.. let someone else take care of it.. the engineering approach that makes these products!
@@mrhassell Engineering wont solve security, just like it wont produce an unpickable lock. There will always be a compromise between security and usability.
linus torvalds should work with risk-v and risk-v laptop manufacturer so they can give us the best linux laptops
I Love Linux and torvalds the creator there ove. I also learn so much from Comments always in TECH related youtube channels, Many a tme Comments have allowed me, a 74 Years Old with Senility the Answer to Problems I have I still Build Tower based Unix Computers, however I am going blind, only 1 Eye works. Hard to work on Mother Boards with one eye.
What the added value was for this re-upload video?
Ryzen 5800X on x370 for main system. Am interested in ARM Snapdragon X Elite for my next companion PC... But seems ARM oversold Linux support in a statement, and the varying notebooks available are posing interesting problems from multiple angles for the time being. 😕
These problems are partly caused by specialisation and compartmentalisation.
Seems to be a blind spot our modern society has in numerous fields.
My frustraition is that is things ALLWAYS breaks in Linux. I think i spend about 30 hours a week to try figuring what is going on. This week, it was My am5 ethernet on x670-e mb. An ancient problem that has never been fixed around ASPM or performance profiles. So what the ethernet does, it hibernating or updates to slow. Then I lose connection, then the connection dont come back or the card wakes up. Until i restart the pc. This happen atleast once every 3 hours. Then Linux devs are like, yeah.. its been there for over 10 years.. 10 years? Then the platform im on its 2 years old. Then you start to wonder.. what in the world is going on with linux. Why is no one fixing the issue. Now im in Disabling ASPM in Bios, then it works. Then another problem is there.. then you get the answear, you need to go in to bios and disable that. My whole bios is about to get disabled soon. Oh btw, you are on nividia card. you need to disable the firmware. I wonder how much we need to disbable soon
Nik isn't Savvy enough to spell Linus' name right. His name isn't Linux LMAO
Even if the hardware is open, the vulnerabilities that will be discovered in it, will still be NDA'ed.
Hardware security becoming more and more relevant makes me think about Apple’s platform where all devices up to and including an $11k+ Mac Pro are non-upgradable.
Only reason more M2 / 3 CVE exploits don't exist.. yet.. 1. Nobody cares. 2. Apple don't provide the hardware to anyone who knows or is able to help them. 3. Nobody gonna buy that!
That sounds like quite simply if you're going to do something complicated in hardware, it needs to have *some* controls in software so the knobs can be turned in case something goes fucky wucky.
You'd think that's common sense.
I have coded in Python and JS and NASM and done an FPGA and a virtual mplementation of RISC-V. I would *love* to hear specific things that RISC-V should learn from its predecessors. It's not quite perfectly pure hardware but it's surprisingly closer than x86 or ARM and was dramatically nicer to build.
The two biggest lesson are probably:
Document everything! Even the implementation details.
And:
When you go against the spec be very careful that there are no ways to take advantage of that as an attacker.
In particular when doing speculative execution be absolutely sure the are no side effects. Specter and Meltdown have shown that things as innocent as cache timing can be enough to leak information.
Maybe a third lesson is to have hardware feature flags that can be updated to turn some stuff of, but that only helps after a vulnerability is found in the wild.
@@antonf.9278 Even the spec though can yield side-channel. You gotta realize, the spec is designed by someone.
Maybe someone has to write a book about the mistakes, so the RISC-V-team can avoid them.
lol - likely.. not even remotely! The factor or care, just isn't there!
Did you monitise this?
My brain
Why so serious Linus? You are not responsible for Intel, AMD or Qualcomm. CVE exploits, are not 'public' enough? What's missing? Spectre is an issue, new variants expand the base, proof of concepts recently announced for RISC mobile and Mali GPU, formation relating to driver and cache pointers. They're all speculative, all read cache or pointer/stack overflows, even oldest exploits ever made, going back forever, all started here! Only difference, having become microcodes in processor evolutions, instruction set extensions, which may be either patched.. or ignored.
Hardware should be effective and efficient without any assumptions. Software should be aware of cache and memory, and use such as applicable. It only when hardware design tries to do software tasks, these issues result. Hardware if it focused on speed of execution based on explicit execution calls received, it would up to the software to provide applicable performance. This is in effect what RISC proved... hardware does its instructions fast, and software decides how instructions are queued. We need to stop trying to make hardware guess what software wants, and we need to stop software from defaulting to letting the hardware figure out what we need, we on software side, should explicitly ask for what we need... say own population of cache. Firmware does this all the time... drives the hardware, because device hardware is basically simplistic, if not 'dumb' from a logic perspective. But of course CPU designers think they know better, and think software designers are not smart enough to do their job... this is really exactly what Linux said... because the hardware is closed, software side cannot contribute to the solution process before the hardware is locked in.
and this is why many of us developers have hung up our hats. We get tired of the insane politics and bs that hinder our ability to do our jobs.
6:00 there are substanially fewer people who do hardware development.
I'm frustrated by all the clickbait
looking at some comments and at how messed up the title is it's clear this guy is actually AI generating at least some of his videos. Always has been the linux fast food kind of videos but still.
I guess there a lot NDA stuff and hinder open src is not easy task. As well there should be other people with NDA had to work on base on open src under NDA branch off stuff.
What is he trying to say? I don’t understand a word he’s repeating over and over. Can someone translate?
Buy a Mac.
Are these vulnerabilities coming up because the code is open source and bad actors can take advantage?
I just like to interject for a moment
why do you pronounce Linus like that
vague and nebulous
linus changed the world by just not accepting poor quality
Interested in Hardware, instead of Appliance a true nerd :p :)
Linus was frusted with Minix and create Linux. He was frusted with code share and he create Github. Was frusted with people using Github to store 'pron' and he sell Github. He was frusted with Nvidia's drivers and say to NVidia go 'frack'.
I think frustration is Linus natural spirit state.
Mr Torvalds,,,Linux is INTERNET!!! we need you to keep on going making Great Linux Software!
Not quite.
The internet was invented in 1969(Nice)
Linux was invented in 1991 (Could've had a hedgehog as their mascot)
The internet predates Linux by a sizeable time.
Risc v isn't the solution. It is just a cheaper solution
It isn't even a solution.
The real solution is the Mill architecture, or something like it. RISC-V may provide hope for an open platform, but it will never lead to secure systems or an escape from the nightmare of monolithic kernels and browsers. If only we could have invested in an open Mill instead, the computing landscape today might be very different (and much better).
is this an AI generated shit?"!? this not how ive ever seen linux torvalds!
When is he not frustrated and swearing at people
middle finger to intel
Which hardware will run Linux optimally, or even normally?
Is that rhetorical or do you expect an answer?
Pretty much every x86 CPU and every GPU except nvidia
@@michalsvihla1403 Well, OF COURSE I would like an ANSWER.
MOST if not ALL hardware will run Windows. Only a SUBSET of that will allow Linux to run - at least that's what I've heard from EXPERTS, who insist that FIRST you should make sure that Linux supports ALL of your hardware!
@@jakobw135 Linux supports a much larger amount of architectures than windows which only works on x86 and, more recently, arm processors. Almost every machine from the last 3 decades can run some linux distro with enough prodding.
@@phithegamer5787 Nice and re-assuring to know, BUT, why do (SUPPOSED) experts insist that you FIRST have to make sure that your LINUX BOX runs the OS properly?
An internet router like MIPS/debian-mipsel could be made but, rather than STM32, it would have a _(debian blob compatible)_ CPU (RISC-V) as a Public-Domain _(or somewhere between copyleft and GPLv2 could do, with AGPLv3 for network niggling details)_ Open-Source microarchitecture RISC-V CPU _(expecting a Linux monolithic kernel too boot from 4 of HDD or SSD SATA with RAID10)_ in it and then some known-quantity amount of RAM like say 4GB in a _(also unregistered RAM compatible and ECC)_ desktop/ECC-compatible RAM slot and a _(also unregistered RAM compatible and ECC)_ desktop/ECC-compatible slot that can (optionally) take another 16GB _(topping it up to 20GB is for some reason it needed to),_ and just make it DDR3 so it can choose between its unregistered and registered RAM settings.
It would be 6G sim-card compatible even though it has ADSL2 via RJ11 ports near the 100Mbps RJ45 ethernet and the 8 USB ports _(and a WAN and other port for straight-to-fibre)_ and it could have Wifi6 and Bluetooth 5.2 and pitch-roll-yaw accelerometer _(like a wii-remote has)_ and a compass and LoRaWAN _(RX and TX send and receive)_ and drivers for S-Band and Ku-Band and software-defined-Radio GNU radio with slowscan TV mode for data. It would have a PCI-e 4x slot at Gen3 to be able to take a better NIC card with VMDq and SR-IOV if better ethernet speeds are need compared to the 100Mbps LAN (not WAN) ports. It would have an IEEE1284 (bootable) and a couple of Serial COM ports to remote into it, and a JTAG and MIPI interface. However, the 100Mbs RJ45 Lan ports on it would be deliberately there for a small driver. An interface to add PoE would be there by you would need to add it later. The RJ11 would also be able to plug in VOIP device, again to add later, keeping cost down. It would have a circuit to detect a battery added later even though it does not come with one and instead, in a power-outlet, would work in a mains electrical plug socket (wall wart).
Then _(and this is the important bit)_ basically just give it _(via some whip-round)_ to the Linux Foundation and ask Linus to say what he wants from the instruction set in the RISC-V CPU. Ask Stallman too _(if he can do)._ The router RISC-V CPU would be unlikely to have better processing than say an A53 with protection-rings. So commercially available routers would be able to make glitzy fancy routers with other features without tis open-source router displacing their market value. This open-source router instead would be designed to be solid and do a workman like job and nothing particular fancy. It simply has that 6G and Bluetooth and WiFi at that reasonably modern level so that is continues to work well enough for many years to come. It would also expect to take a MFA FIDO2 hardware security key in a USB port just in case that helps things in future projects. It would probably need some of the USB ports to be capable (or upgradeable) of being USB3.2 with decent power _(converting to or from USB-C)._
Linux is not pronounce like his name 'Linus' _(a running in-joke for geeks),_ so the router should have a naming convention along those lines _(being deliberately slightly inaccurate)_ as with its default Operating System distro. So the Distro could be called thr34k because it is like 'freak' (the previous candidate name for Linux) but spelt wrongly as though it is the number but then the letters are post ironically switched to numbers just to be even wronger. The router itself could be called _"Lee Noose"_ because it is about time, once again, that we all came up with yet another wrong way to say his name.
The router should have a couple of interfaces to allow the user to optionally plug in a couple of 128x32 pixel monochrome LCD screens. The CPU could be called the "St. All m'Anne" _(because it is a corruption of Richard Stallman)._ We'll just have to come up with a reason why it is like that and never actually admit it to Stallman _(or Torvalds for his one)_ as to why the name of the CPU is that. We'll say perhaps that The name represents a saint of everything (i.e "all") associated with my Anne. So, let's assume Anne is some person or whatever, and she is "my Anne" like maybe she is betrothed or something. So it means _"The Saint of everything pertaining to my Anne"_ when it is written _"St. All m'Anne"._ It's a stretch but without it, somebody will need to come up with something better. Anne will be represented in a cartoon avatar sticker stuck on the router and then can be a character in SuperTuxKart because mascots need to exist for as many GNU linux things as possible. That avatar and the _"Lee Noose"_ avatar will probably be some sort of fluffy mascot other people haven't already used, rather than an actual human.
It would have a 2nd CPU socket just in case it struggles. The RISC-V should have an FPU in it.
The point is that it would become popular enough without flooding the market and Stallman and Linus would simply be able to tell the makers in advance what they want from it. It probably would be able to take a modest low-power graphics-card in the PCIe slot and run it is a server with a GUI or desktop computer but that is not the main focus of it. That does mean however that if there is a desire for a "safe option" CPU, the router would have established it, even though it would be quite a tame CPU compared to actual laptops, smartphones and desktop computers _(and big-servers)._ Thereby when people make other _(fancy)_ RISC-V CPU chips _(be they public domain or not),_ they can have the point-of-reference to know what basic little CPU other people are already happy with looks like.
The router will be have a target audience like the One-Laptop-Per-Child project in the past, _(so you can buy one in USA, UK and so on and the increased price)_ but displaced people _(with an identity card)_ who want to get one can buy or earn one such as if they set up a business like a coffee shop or something like that _(or they maybe just want to use it in their dwelling on as a carputer but on a bike)._ The router _(essentially with a ALSA compatible 24-Bit soundcard with MIDI on it)_ would have a mic-in and line-in (both stereo) and a stereo line-out just in case not having one causes a problem with VOIP somehow later. It would expect ogg-vorbis-theora even though it could probably do other things. Having MIDI (a joystick port) is useful but is there to ensure linux has a go-to MIDI standard just in case somehow the sound-card existing on the router (largely for VOIP) encounters a problem as a result of not having MIDI.
If Torvalds and Stallman refuse to take the money to do it, have some other bargaining chip they are after to incentivise them to do it for that reason. There must be something. The benefit everybody else would have is that it would save a whole bunch of ballache regarding computing-ambiguity _(especially pertaining to the deciduous nature of Reduced Instruction Set Chips)_ and would brighten up these grumble-pill videos of two blokes sitting on 2 chairs like something out of a year 2000 Public Access TV channel show.
My comment has no hate in it and I do no harm. I am not appalled or afraid, boasting or envying or complaining... Just saying. Psalms23: Giving thanks and praise to the Lord and peace and love. Also, I'd say Matthew6.
TLDR. Come on.
@@jondonnelly3I read it, can't help with a TL;DR, didn't understand it.
What a bunch of gibberish.
DDR3, LCD screens, 100Mb LAN. Insane
It's pronounced "Line Us"
en.m.wikipedia.org/wiki/Linus_Torvalds
What about open sourcing the x86 architecture? For the RISC-V architects don't make the same mistakes.
Pentium G620.
Since you can’t pronounce the man’s name, I assume this is AI.
What's Linux hardware?
The title could mean the hardware security issues also affecting linux. Like meltdown and specter .
oddly, he's very silent about Linux security issues. go figure
Oddly that was not the question asked to him. Go figure.
ARM is dead. They found a huge bug you can't fix. Lol. Back to the drawing board boys.
Just dont connect to internet why overcoompilcate stuff jeez...
A ship is safest in port, but that is not what they are built for.
I think he's frustrated
And 8 days later after this video half the internet gets an update from one company and it just so happens to be they didn't test a kernel update. I think it was done on purpose Microsoft and crowdstrike. Just to see how much control they have
That kind of test can be done without anyone noticing. Either it was a honest mistake or they wanted people to notice.
@@seriouscat2231 after doing extensive searching the CEO of crowdstrike is tied to Black Rock black rock is tied to the person who shot at the president and this happened after the president was shot but not killed. Bread crumbs don't lie they tell a story if you're willing to be unbiased about the story
Linus is always frustrated. Not new News!
Internet computing is a Linux thing - robust and safest!
Hes always frustrated
Tanenbaum might have some good advice. 😊
5500u
What about the growing number of "diversity quotas" in Linux Foundation? Are they imposed by the corporate donors? Does he know how much bloat and useless code they pouring in the kernel? Is he okay with those politics?
It's a pandemic much worse than Covid
Look at how much he's aged lately, poor man's suffering knowing his hands are tied and there's nothing he can do to stop the madness. He's seeing his life's work collapse thanks to the new generation of maintainers not knowing what they are doing and ruining everything. This is what happens when you make your project be part of a large corporate environment... everything becomes political, and they focus more on diversity, meetings and sprints rather than actual software development, and we end up with bloat everywhere... With bloat like this, who needs Windows...?
@@tiranito2834 While I can appreciate the sentiment, the reality is that he's kowtowed to these things and accepted them, as shown by some of his mastodon posts(at least publicly), sooooo... you get what you deserve, I guess?
😂
@@vak2586 I wonder why so much uys in IT is so woke... I bet they think they'll be coding AAA games in a South Africa tier country.
"Speaks on Linux Hardware SECURITY Issues" - There is nos such thing as Linux Hardware Security Issues. Either they are hardware security issue but then they are not related to Linux at all and will affect any operating system on earth or they are Linux issues but then they are not hardware issues as there is no Linux hardware, Linux is a software operating system kernel.
he sounds as if he did smthn with his teeth
I use potato, Linux Works Great❤😂
I wonder what he thinks about zealots from Linux and FOSS that despise closed source and ignore financial part of software development...
What are you talking about and what is your point? Do you have examples?
(Im not being argumentative, im genuinely curious what you're talking about)
@@SnowDaemon
One of things holding back and preventing Linux from making progress is gatekeepers that zealots and similar people.
because of that, many important problems are. NOT solved.
Hardware is one of them since those zealots cause regression for desktop environment where Hardware Companies are invested in.
the fact that he didn't changed LInux from GPL2 to GPL3 is a strong indicative of his opinion, he knew that linux wouldn't grow forcing people/companies to open source their code(one opinion that i agree with) instead, because it's free and people/company don't need to open source their code, it grew to dominate every market possible
@@SkyFly19853 > Hardware is one of them since those zealots cause regression for desktop environment where Hardware Companies are invested in.
how they do that?, i know that these type of people exist, but they aren't the majority
@SkyFly19853 you keep saying "zealots and gatekeepers". But can you give me an example? I don't think you're wrong, I just want to know why you have these opinions. It seems like you're just saying stuff but have no idea what's actually going on. Because I don't recall Linus preventing financial growth. If anything, he's been one of the main promoters of RHEL and what they're doing. I'm just trying to figure out who you're talking about and what they've done...
have 2 computers that uses intel and 2 that are using amd and 1 using apple m1
He just needs to chill out a bit and spend less time playing with computers
he got challenge by me now...sure it will sting him where it hurts now...thank god i did what i must do, replace the dooch someone really cares for real linux kernel...for he, linus is turning his kernel into extension of windows nt kernel lately...might as well throw entire legacy of his out the windows of his...basically linux and windows nt kernel are pretty much alike by now. Both run windows programs...only difference ...amd drivers run lot better under real windows ...not windows with lock up penguin behind it with tears in its eyes . Thats frustrated to see Microsoft ate our linux kernel
Better make Linux NTFS .. Then it will boom .. Nobody like's windows anymore ..
Linux is still superior for internet than windows!
What you said makes literally no sense..
Linus has been frustrated for years. All he seems to do any more is complain.
He needs to recruit somehow!
Get Rust out of the kernel and stop using systemd.
init systems like OpenRC, runit, or SysV init.. are superior, well I suppose.. You are saying Rust isn't a flavour, you.. require. Memory safety to reduce bugs and writing kernel drivers, is one of the key points he's addressing this on. Bunch of CVEs relate directly to this, all made recently in RISC lol If they were written in Rust, the problem wouldn't exist.
I love linux os but that guy is an absolute m-oron.
Which guy is a moron?
The one who created Linux when he was 23yrs old (and also Git) or the one interviewing him who's been a SWE for over 40 yrs and is head of OpenSource at Verizon?
"Linux OS" yeah sure.
@@tinglabingGNU/Linux
myself m-rna medicine
Linus