Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Linux is the most widespread operating system, globally – but how is it built? Few people are better to answer this than Greg Kroah-Hartman (Greg K-H): Greg has been a Linux kernel maintainer for 25 years, and one of the 3 Linux Kernel Foundation Fellows (the other two are...

GergelyOrosz's profile picture

Gergely Orosz

288,309 subscribers

50,945 Aufrufe • vor 1 Jahr •via X (Twitter)

Wissenschaft & Technologie
LIVE

Anya Rossi• Live Now

Private livecam show

7 Kommentare

Profilbild von Chidi-ebere .C🐘
Chidi-ebere .C🐘vor 1 Jahr

@gregkh Amazing. Bookmarked !

Profilbild von SecBriefs | Making Cybersecurity Simple
SecBriefs | Making Cybersecurity Simplevor 1 Jahr

🐍Python + 🔐Cybersecurity: The ultimate combo for secure, resilient apps. 🎯 Who’s this book for? ✔Python enthusiasts ✔Coders who care about security ✔Anyone who hates jargon but loves clarity 📖"Cybersecurity Dictionary for Everyone", on Amazon:

Profilbild von Yu Yang
Yu Yangvor 1 Jahr

@gregkh This is a cool way to manage projects only through git and email 👏👏

Profilbild von Vishwajit
Vishwajitvor 1 Jahr

@gregkh Incredible watch!

Profilbild von Maciej Gajewski
Maciej Gajewskivor 1 Jahr

@gregkh Oh, that's a treat!

Profilbild von Liberty
Libertyvor 1 Jahr

@gregkh In the full video he said zig and what?

Profilbild von Georgios Andrianakis
Georgios Andrianakisvor 1 Jahr

@gregkh I can't remember the last time I listened to a tech podcast that contains so much wisdom!

Ähnliche Videos

Which coding agent is right for you? 🤔 This question poses a major challenge to developers and teams. That's why we’re launching the Developer Productivity AI Arena, an open-source platform that will allow the community to benchmark, rank, and contribute datasets – and hopefully bring about a collective solution to this shared problem. JetBrains intends to contribute the project to the Linux Foundation for transparent governance. 🔗 Learn more and see how to get involved:
1:01

Which coding agent is right for you? 🤔 This question poses a major challenge to developers and teams. That's why we’re launching the Developer Productivity AI Arena, an open-source platform that will allow the community to benchmark, rank, and contribute datasets – and hopefully bring about a collective solution to this shared problem. JetBrains intends to contribute the project to the Linux Foundation for transparent governance. 🔗 Learn more and see how to get involved:

JetBrains

16,745 Aufrufe • vor 8 Monaten

Kubernetes is the second-largest open-source project in the world. What does it do—and why is it so widely adopted? Kat Cosgrove has led several Kubernetes releases and joined The Pragmatic Engineer podcast to share the history of Kubernetes, how it's built, when it is a good (or not so good) use case, and how you can contribute to it (and why it's a good thing to do for professional and career growth). Brought to you by •⁠ WorkOS — The modern identity platform for B2B SaaS •⁠ Modal — The cloud platform for building AI applications •⁠ Cortex — Your Portal to Engineering Excellence Watch or listen: • YouTube: • Spotify: • Apple: • Summary and transcript: Three of my takeaways from this great conversation: 𝟭. 𝗞𝘂𝗯𝗲𝗿𝗻𝗲𝘁𝗲𝘀 𝗵𝗲𝗹𝗽𝘀 𝘄𝗶𝘁𝗵 𝗺𝗮𝗻𝗮𝗴𝗶𝗻𝗴 𝗹𝗮𝗿𝗴𝗲-𝘀𝗰𝗮𝗹𝗲 𝗯𝗮𝗰𝗸𝗲𝗻𝗱 𝗮𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀. Google originally built an in-house tool to manage the tens of thousands (then hundreds of thousands and later millions) of machines: this internal tool is called Borg. The roots of Kubernetes come from Borg: but Google has since donated the project to the Cloud Native Computing Foundation (CNCF) – and today, Kubernetes is the second largest open source project, after Linux. We previously did a deepdive on How Linux is built, and touched on Google’s SRE roots in What is Reliability Engineering? 𝟮. 𝗞𝘂𝗯𝗲𝗿𝗻𝗲𝘁𝗲𝘀 𝗶𝘀 𝗮 𝘃𝗲𝗿𝘆 𝘄𝗲𝗹𝗹-𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲𝗱 𝗮𝗻𝗱 𝗼𝗿𝗴𝗮𝗻𝗶𝘇𝗲𝗱 𝗼𝗽𝗲𝗻 𝘀𝗼𝘂𝗿𝗰𝗲 𝗽𝗿𝗼𝗷𝗲𝗰𝘁. The structure of the project and all processes are well documented. The project has around 150-200 maintainers, has a few dozen SIGs (Special Interest Groups) and releases run on a 14-16 week cycle. 𝟯. 𝗧𝗵𝗲 “𝗹𝗲𝗮𝗱” 𝗮𝗻𝗱 “𝘀𝗵𝗮𝗱𝗼𝘄” 𝗰𝗼𝗻𝗰𝗲𝗽𝘁 𝗶𝘀 𝗮 𝗰𝗹𝗲𝘃𝗲𝗿 𝗼𝗻𝗲, 𝘂𝘁𝗶𝗹𝗶𝘇𝗲𝗱 𝗯𝘆 𝗞𝘂𝗯𝗲𝗿𝗻𝗲𝘁𝗲𝘀. The Release Team within Kubernetes owns releases, and the Release Team has about 20-30 people participating in each release. More than of the members on the Release Team are “shadows” who get to learn on the job how a release is done – and, hopefully, in a release or two, become leads themselves!
0:55

Kubernetes is the second-largest open-source project in the world. What does it do—and why is it so widely adopted? Kat Cosgrove has led several Kubernetes releases and joined The Pragmatic Engineer podcast to share the history of Kubernetes, how it's built, when it is a good (or not so good) use case, and how you can contribute to it (and why it's a good thing to do for professional and career growth). Brought to you by •⁠ WorkOS — The modern identity platform for B2B SaaS •⁠ Modal — The cloud platform for building AI applications •⁠ Cortex — Your Portal to Engineering Excellence Watch or listen: • YouTube: • Spotify: • Apple: • Summary and transcript: Three of my takeaways from this great conversation: 𝟭. 𝗞𝘂𝗯𝗲𝗿𝗻𝗲𝘁𝗲𝘀 𝗵𝗲𝗹𝗽𝘀 𝘄𝗶𝘁𝗵 𝗺𝗮𝗻𝗮𝗴𝗶𝗻𝗴 𝗹𝗮𝗿𝗴𝗲-𝘀𝗰𝗮𝗹𝗲 𝗯𝗮𝗰𝗸𝗲𝗻𝗱 𝗮𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀. Google originally built an in-house tool to manage the tens of thousands (then hundreds of thousands and later millions) of machines: this internal tool is called Borg. The roots of Kubernetes come from Borg: but Google has since donated the project to the Cloud Native Computing Foundation (CNCF) – and today, Kubernetes is the second largest open source project, after Linux. We previously did a deepdive on How Linux is built, and touched on Google’s SRE roots in What is Reliability Engineering? 𝟮. 𝗞𝘂𝗯𝗲𝗿𝗻𝗲𝘁𝗲𝘀 𝗶𝘀 𝗮 𝘃𝗲𝗿𝘆 𝘄𝗲𝗹𝗹-𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲𝗱 𝗮𝗻𝗱 𝗼𝗿𝗴𝗮𝗻𝗶𝘇𝗲𝗱 𝗼𝗽𝗲𝗻 𝘀𝗼𝘂𝗿𝗰𝗲 𝗽𝗿𝗼𝗷𝗲𝗰𝘁. The structure of the project and all processes are well documented. The project has around 150-200 maintainers, has a few dozen SIGs (Special Interest Groups) and releases run on a 14-16 week cycle. 𝟯. 𝗧𝗵𝗲 “𝗹𝗲𝗮𝗱” 𝗮𝗻𝗱 “𝘀𝗵𝗮𝗱𝗼𝘄” 𝗰𝗼𝗻𝗰𝗲𝗽𝘁 𝗶𝘀 𝗮 𝗰𝗹𝗲𝘃𝗲𝗿 𝗼𝗻𝗲, 𝘂𝘁𝗶𝗹𝗶𝘇𝗲𝗱 𝗯𝘆 𝗞𝘂𝗯𝗲𝗿𝗻𝗲𝘁𝗲𝘀. The Release Team within Kubernetes owns releases, and the Release Team has about 20-30 people participating in each release. More than of the members on the Release Team are “shadows” who get to learn on the job how a release is done – and, hopefully, in a release or two, become leads themselves!

Gergely Orosz

22,268 Aufrufe • vor 1 Jahr

Anthropic just announced it’s donating MCP to the Linux Foundation, under a new Agentic AI Foundation called ✨AAIF✨, co-founded by Anthropic, OpenAI, and Block. So it’s not just one announcement… it’s actually two … here’s a quick breakdown: 1️⃣ MCP moves to the Linux Foundation MCP launched just a year ago and already has over 97 million SDK downloads. By donating it to the Linux Foundation, MCP becomes open, vendor-neutral, and community-governed — which is exactly what a widely adopted protocol needs to scale. 2️⃣ The launch of AAIF The Linux Foundation just launched a new Agentic AI Foundation - AAIF - and MCP is one of its founding contributions but there are 2 others: It’s joined by Block’s goose framework and OpenAI’s AGENTS spec…..creating a shared home for open-source agent standards ❤️🏡 📖 Official announcement:
1:11

Anthropic just announced it’s donating MCP to the Linux Foundation, under a new Agentic AI Foundation called ✨AAIF✨, co-founded by Anthropic, OpenAI, and Block. So it’s not just one announcement… it’s actually two … here’s a quick breakdown: 1️⃣ MCP moves to the Linux Foundation MCP launched just a year ago and already has over 97 million SDK downloads. By donating it to the Linux Foundation, MCP becomes open, vendor-neutral, and community-governed — which is exactly what a widely adopted protocol needs to scale. 2️⃣ The launch of AAIF The Linux Foundation just launched a new Agentic AI Foundation - AAIF - and MCP is one of its founding contributions but there are 2 others: It’s joined by Block’s goose framework and OpenAI’s AGENTS spec…..creating a shared home for open-source agent standards ❤️🏡 📖 Official announcement:

Linda Vivah (Haviv)

27,579 Aufrufe • vor 7 Monaten

A LINUX KERNEL DEVELOPER PROVED THE THING YOU PUSH CODE TO IS SECRETLY A DATABASE THAT CAN VERSION ALMOST ANYTHING AND THAT MOST DEVS HAVE ONLY EVER TOUCHED A TENTH OF IT 42 minutes from Josh Triplett -- a longtime Linux kernel and Debian developer -- showing that Git is a general-purpose, tamper-evident versioning engine that just happens to be famous for code. -> The moment it clicks, Git stops being "Where my code lives" and becomes what it really is underneath: a content-addressable store that can version almost anything -- your configs, your notes, your servers' state, entire datasets. People run whole wikis on it. They version their entire machine's configuration with it. They ship websites by pushing to it. They track data too big to email. None of it is a hack -- it's the same handful of objects you already use for code, pointed somewhere new. Treating Git as a code-only tool was never the ceiling -> it's a versioning engine for anything, and the people who see that automate what the rest of the team still does by hand. And as AI agents start spitting out not just code but configs, docs and data, the one system that can version and audit all of it at once is already sitting on your machine. You learned five commands to survive. This is the talk that shows you were standing on top of a database the whole time. It changes what you think the tool is even for. Bookmark & Watch it today ↓
42:24

A LINUX KERNEL DEVELOPER PROVED THE THING YOU PUSH CODE TO IS SECRETLY A DATABASE THAT CAN VERSION ALMOST ANYTHING AND THAT MOST DEVS HAVE ONLY EVER TOUCHED A TENTH OF IT 42 minutes from Josh Triplett -- a longtime Linux kernel and Debian developer -- showing that Git is a general-purpose, tamper-evident versioning engine that just happens to be famous for code. -> The moment it clicks, Git stops being "Where my code lives" and becomes what it really is underneath: a content-addressable store that can version almost anything -- your configs, your notes, your servers' state, entire datasets. People run whole wikis on it. They version their entire machine's configuration with it. They ship websites by pushing to it. They track data too big to email. None of it is a hack -- it's the same handful of objects you already use for code, pointed somewhere new. Treating Git as a code-only tool was never the ceiling -> it's a versioning engine for anything, and the people who see that automate what the rest of the team still does by hand. And as AI agents start spitting out not just code but configs, docs and data, the one system that can version and audit all of it at once is already sitting on your machine. You learned five commands to survive. This is the talk that shows you were standing on top of a database the whole time. It changes what you think the tool is even for. Bookmark & Watch it today ↓

slash1s

383,343 Aufrufe • vor 1 Monat

U-Boot menu now works on Flipper One Now you can choose different kernels and systemd targets before the Linux kernel boots. * It's our LCD/buttons driver plus a slightly modified vanilla U-Boot menu. Will try to upstream it to U-Boot. * This is a temporary solution for testing the selection of different OS profiles. In the final version of Flipper OS, we’ll most likely draw the boot menu using a small program compiled into initramfs, after the kernel has started. But as a temporary solution, it works perfect. * I’m still not happy with the cold boot time: from powering on the processor to having a working menu. Here’s the boot log with timestamps, captured from the processor console: * Our patched U-Boot:
2:56

U-Boot menu now works on Flipper One Now you can choose different kernels and systemd targets before the Linux kernel boots. * It's our LCD/buttons driver plus a slightly modified vanilla U-Boot menu. Will try to upstream it to U-Boot. * This is a temporary solution for testing the selection of different OS profiles. In the final version of Flipper OS, we’ll most likely draw the boot menu using a small program compiled into initramfs, after the kernel has started. But as a temporary solution, it works perfect. * I’m still not happy with the cold boot time: from powering on the processor to having a working menu. Here’s the boot log with timestamps, captured from the processor console: * Our patched U-Boot:

Flipper R&D

32,267 Aufrufe • vor 20 Tagen

I got so tired of everyone raving about how great cmux is. Panes this. Browser that. EXHAUSTING. And that's because I'm on Linux, where we get none of the coolest toys. So...I built it myself. And my God. You were right. It's amazing. Introducing Limux, a a GPU-accelerated terminal workspace manager for Linux, powered by Ghostty's rendering engine, with split panes, tabbed workspaces, and a built-in browser. Think cmux, but native Linux. If you're interested in something like this, be sure to leave a comment and I'll release it. Special thanks to Manaflow and Mitchell Hashimoto for making this possible.
1:30

I got so tired of everyone raving about how great cmux is. Panes this. Browser that. EXHAUSTING. And that's because I'm on Linux, where we get none of the coolest toys. So...I built it myself. And my God. You were right. It's amazing. Introducing Limux, a a GPU-accelerated terminal workspace manager for Linux, powered by Ghostty's rendering engine, with split panes, tabbed workspaces, and a built-in browser. Think cmux, but native Linux. If you're interested in something like this, be sure to leave a comment and I'll release it. Special thanks to Manaflow and Mitchell Hashimoto for making this possible.

am.will

108,847 Aufrufe • vor 3 Monaten

Tobi talks about how people think we can't do big infrastructure investments like we used to, which is true, but he argues it's because so many of our most talented people have been creating herculean monuments in software instead of the real world. "People talk about the incredible infrastructure we used to build in the '60s. How quickly we built subways and now it takes forever and so on. There is an observed degradation of a lot of these kind of projects. The web browser, Linux, all these kind of things are projects at a scale beyond what the pyramids are."
2:11

Tobi talks about how people think we can't do big infrastructure investments like we used to, which is true, but he argues it's because so many of our most talented people have been creating herculean monuments in software instead of the real world. "People talk about the incredible infrastructure we used to build in the '60s. How quickly we built subways and now it takes forever and so on. There is an observed degradation of a lot of these kind of projects. The web browser, Linux, all these kind of things are projects at a scale beyond what the pyramids are."

Jack Altman

15,161 Aufrufe • vor 1 Monat

Look at how giddy certain individuals are when they get to cheerlead for Greg Abbott and rub how much (probably) dirty money he has in your face. Meanwhile the rest of us are out here struggling to make ends meet or face losing their home under the very conditions that Greg has caused. These people are completely removed from reality. That's what they think of us. They view us all as dumb cattle that have to vote for whoever has the most money. Because candidate X has more special interest big donor money, We The People get stuck with the special interest approved candidate? Notice how they never talk about the issues or the competition of ideas. It's never about who has a better vision or plan for Texas, it's always pot shots about money or some other ridiculous attack. We are running this thing, in many ways, like an unconventional warfare operation. Without disclosing tactics, techniques, and procedures, those operations do not require nearly the expenditure in dollars to achieve results as opposed to something more conventional. What’s being done and communicated about money is a method of voter suppression. It’s meant to demoralize voters on one side to make it appear that their support for a candidate is isolated and they’re all alone…that the candidate they support could never win because “look at the numbers”. This is called Bandwagon Effect and Demoralization. It’s a psychological manipulation tactic meant to suppress voters that exploit the conformity bias. It leads to people thinking “my vote won’t matter”. Greg and his sycophantic supporters are counting on this to be effective. If things were as hopeless as these idiots lead folks to believe, why would Greg be actively campaigning leading up to the Republican primary? I mean if there really is no chance for any challenger, why is Greg and his campaign doing the things they’re doing? There’d be no need to waste the time and resources on campaigning, it’d be better to save that for the general election against the democrat machine. But that’s not what we see is it? Greg is actively making the rounds and campaigning; his campaign staff is active and working. They may not be using the words primary (because doing so does nothing but hurt them), but they are out there and working every day. Greg is constantly getting in front of MSM or sympathetic State and national radio/podcast hosts. He’s utilizing known paid influencers on social media to echo his more recent “actions” to build the illusion of support and reinforce that Bandwagon Effect. He’s reaching out to members of the Texas legislature to desperately get them to sign on to his ridiculous big-nothingburger of a property tax plan…and then very publicly posting up when one of them signs on and “supports” it. Every time Doc attends a Republican committee event at the county level to talk (or has someone there on his behalf), Greg Abbott has a surrogate there actively campaigning for Greg in response. Greg and his team are so concerned with the numbers and what’s happening inside the party, they have to try and wrestle back control and narrative within the party. Just on social media, we’ve seen a 250% increase in activity on Greg’s campaign account since the summer. On multiple occasions Greg has either lifted direct sections of Doc Pete Chambers plans and policy or the concepts. Suddenly he’s figured out how to take action on the things that people are up in arms about, right before the primary election? On more than one occasion Greg and his campaign have been forced to put out a statement or propose some new “action” (optics) less than 24 hours after Doc or Doc’s campaign has posted about something. Ladies and gentlemen, those are not the actions of a candidate who has it in the bag and “there’s no threat”. Think about it this way. We admittedly have a fraction of the resources that Greg Abbott has, after he’s spent decades in politics…but little ole Doc with “no money” and “no chance” is forcing the leader of the 2nd largest State in the country and 8th largest economy in the world to sweat, forcing him to take actions he otherwise wouldn’t be taking…that is very significant and telling about how Greg and his team view Doc. So let the naysayers scream into the void and expose their true nature to everyone. We will continue on making Greg’s team backpedal and take actions they otherwise wouldn’t be taking. Anyone who’s ever participated in maneuver warfare at the operational and strategic level will know exactly what we are talking about. #TexasNeedsADoc
0:38

Look at how giddy certain individuals are when they get to cheerlead for Greg Abbott and rub how much (probably) dirty money he has in your face. Meanwhile the rest of us are out here struggling to make ends meet or face losing their home under the very conditions that Greg has caused. These people are completely removed from reality. That's what they think of us. They view us all as dumb cattle that have to vote for whoever has the most money. Because candidate X has more special interest big donor money, We The People get stuck with the special interest approved candidate? Notice how they never talk about the issues or the competition of ideas. It's never about who has a better vision or plan for Texas, it's always pot shots about money or some other ridiculous attack. We are running this thing, in many ways, like an unconventional warfare operation. Without disclosing tactics, techniques, and procedures, those operations do not require nearly the expenditure in dollars to achieve results as opposed to something more conventional. What’s being done and communicated about money is a method of voter suppression. It’s meant to demoralize voters on one side to make it appear that their support for a candidate is isolated and they’re all alone…that the candidate they support could never win because “look at the numbers”. This is called Bandwagon Effect and Demoralization. It’s a psychological manipulation tactic meant to suppress voters that exploit the conformity bias. It leads to people thinking “my vote won’t matter”. Greg and his sycophantic supporters are counting on this to be effective. If things were as hopeless as these idiots lead folks to believe, why would Greg be actively campaigning leading up to the Republican primary? I mean if there really is no chance for any challenger, why is Greg and his campaign doing the things they’re doing? There’d be no need to waste the time and resources on campaigning, it’d be better to save that for the general election against the democrat machine. But that’s not what we see is it? Greg is actively making the rounds and campaigning; his campaign staff is active and working. They may not be using the words primary (because doing so does nothing but hurt them), but they are out there and working every day. Greg is constantly getting in front of MSM or sympathetic State and national radio/podcast hosts. He’s utilizing known paid influencers on social media to echo his more recent “actions” to build the illusion of support and reinforce that Bandwagon Effect. He’s reaching out to members of the Texas legislature to desperately get them to sign on to his ridiculous big-nothingburger of a property tax plan…and then very publicly posting up when one of them signs on and “supports” it. Every time Doc attends a Republican committee event at the county level to talk (or has someone there on his behalf), Greg Abbott has a surrogate there actively campaigning for Greg in response. Greg and his team are so concerned with the numbers and what’s happening inside the party, they have to try and wrestle back control and narrative within the party. Just on social media, we’ve seen a 250% increase in activity on Greg’s campaign account since the summer. On multiple occasions Greg has either lifted direct sections of Doc Pete Chambers plans and policy or the concepts. Suddenly he’s figured out how to take action on the things that people are up in arms about, right before the primary election? On more than one occasion Greg and his campaign have been forced to put out a statement or propose some new “action” (optics) less than 24 hours after Doc or Doc’s campaign has posted about something. Ladies and gentlemen, those are not the actions of a candidate who has it in the bag and “there’s no threat”. Think about it this way. We admittedly have a fraction of the resources that Greg Abbott has, after he’s spent decades in politics…but little ole Doc with “no money” and “no chance” is forcing the leader of the 2nd largest State in the country and 8th largest economy in the world to sweat, forcing him to take actions he otherwise wouldn’t be taking…that is very significant and telling about how Greg and his team view Doc. So let the naysayers scream into the void and expose their true nature to everyone. We will continue on making Greg’s team backpedal and take actions they otherwise wouldn’t be taking. Anyone who’s ever participated in maneuver warfare at the operational and strategic level will know exactly what we are talking about. #TexasNeedsADoc

DocPeteChambersForTexas

17,547 Aufrufe • vor 5 Monaten

This is big... Anthropic just announced a model so powerful they won't release it to the public out of fear over the damage it will cause 😨 Claude Mythos Preview found thousands of zero-day exploits in every major operating system and web browser... The numbers are hard to believe: > $50 to find a 27-year-old bug in OpenBSD, one of the most security-hardened operating systems ever built > Under $1,000 to find AND build a fully working remote code execution exploit on FreeBSD that grants unauthenticated root access from anywhere on the internet > Under $2,000 to chain together multiple Linux kernel vulnerabilities into a complete privilege escalation exploit For context: these are the kinds of findings that previously required elite security researchers working for weeks. Anthropic engineers with no formal security training asked Mythos to find exploits overnight. They woke up to working code the next morning. The results were so impressive Anthropic assembled Apple, Google, Microsoft, Amazon, NVIDIA, and seven other organizations into Project Glasswing: A $100M defensive coalition. They're not releasing this model publicly. Instead, they're racing to patch the world's infrastructure before models like this proliferate.
4:14

This is big... Anthropic just announced a model so powerful they won't release it to the public out of fear over the damage it will cause 😨 Claude Mythos Preview found thousands of zero-day exploits in every major operating system and web browser... The numbers are hard to believe: > $50 to find a 27-year-old bug in OpenBSD, one of the most security-hardened operating systems ever built > Under $1,000 to find AND build a fully working remote code execution exploit on FreeBSD that grants unauthenticated root access from anywhere on the internet > Under $2,000 to chain together multiple Linux kernel vulnerabilities into a complete privilege escalation exploit For context: these are the kinds of findings that previously required elite security researchers working for weeks. Anthropic engineers with no formal security training asked Mythos to find exploits overnight. They woke up to working code the next morning. The results were so impressive Anthropic assembled Apple, Google, Microsoft, Amazon, NVIDIA, and seven other organizations into Project Glasswing: A $100M defensive coalition. They're not releasing this model publicly. Instead, they're racing to patch the world's infrastructure before models like this proliferate.

Josh Kale

4,061,377 Aufrufe • vor 3 Monaten

Is Linux a “Pedo Bar”? Put another way: Does the world of Linux and Open Source (including foundations, corporations, and projects) have a disproportionately high level of rapists, pedophiles, and general degenerates? Does Open Source protect such people? And is that by design? Many of the Extreme Leftist Activists within Open Source have regularly attacked anyone who objects to degeneracy — often banning them from organizations entirely, labeling those opposed to degeneracy as “Nazis”. These Leftist Activists say they are trying to stop Open Source from becoming a “Nazi Bar” (a place where Nazis feel safe to congregate) by banning “Nazis”. But, clearly, there are no actual Nazis there (at least not in any significant number). There is no “Nazi Bar” in Open Source. But there is another group that feels extremely safe within Open Source: Rapists, Pedophiles, and general Degenerates. A short anecdote: Many years back (a decade or more), while recording a Linux podcast, I mocked rapists. I made a quick, off-handed remark about how much I despise rapists. About how I felt that anyone who would rape another human being must be truly awful and insane. I did not consider this to be a controversial statement to make. Every good person is opposed to rapists, right? Well… The response, from the Extreme Leftist corners of Open Source, to me being *opposed* to rape, was truly bizarre. For *several* years, those groups regularly protested my involvement in conferences and organizations. Their repeatedly stated reason for protesting me, aggressively, for years? That my position on rapists made them “feel unsafe”. Think that through for a moment. I am opposed to rapists. This made them “feel unsafe”. Why would anyone feel “unsafe” because of someone being *against* rape? Insane, right? The true reason they proclaimed they felt “unsafe” is becoming quite clear. Over the last several years we’ve watched as projects, organizations, and companies have actively promoted sexual degeneracy. Often in criminal form. Microsoft advocating for their employees to give their children (as young as 3) sex changes. Linux Distros using Trans cartoons targeting children: Open Source projects banning anyone who objects to waving the Trans Flag. So many examples. We could list similar stories all day long. Promote degenerate activity, ban anyone who objects. That is the standard operating procedure of so many Open Source organizations. We’ve all been watching it for years. Then, this week we learned about a convicted rapist (who, according to court records, committed “thousands of [sexual] assaults” of little kids) working at Canonical (the parent company of Ubuntu Linux). And being actively involved in GNOME and Ubuntu development. These crimes, according to several sources, were well known. But kept hush-hush. This registered sex offender was not only welcome, but protected (and promoted) within Open Source. The picture is becoming clear. This is what we are seeing within Open Source organizations: - Promote degenerate (often criminal) activities. - Ban and attack any who oppose the degeneracy. - Protect and elevate the degenerates (including convicted rapists of small children). Now, let me ask the question again. Is Linux (and Open Source) a “Pedo Bar”?
10:10

Is Linux a “Pedo Bar”? Put another way: Does the world of Linux and Open Source (including foundations, corporations, and projects) have a disproportionately high level of rapists, pedophiles, and general degenerates? Does Open Source protect such people? And is that by design? Many of the Extreme Leftist Activists within Open Source have regularly attacked anyone who objects to degeneracy — often banning them from organizations entirely, labeling those opposed to degeneracy as “Nazis”. These Leftist Activists say they are trying to stop Open Source from becoming a “Nazi Bar” (a place where Nazis feel safe to congregate) by banning “Nazis”. But, clearly, there are no actual Nazis there (at least not in any significant number). There is no “Nazi Bar” in Open Source. But there is another group that feels extremely safe within Open Source: Rapists, Pedophiles, and general Degenerates. A short anecdote: Many years back (a decade or more), while recording a Linux podcast, I mocked rapists. I made a quick, off-handed remark about how much I despise rapists. About how I felt that anyone who would rape another human being must be truly awful and insane. I did not consider this to be a controversial statement to make. Every good person is opposed to rapists, right? Well… The response, from the Extreme Leftist corners of Open Source, to me being *opposed* to rape, was truly bizarre. For *several* years, those groups regularly protested my involvement in conferences and organizations. Their repeatedly stated reason for protesting me, aggressively, for years? That my position on rapists made them “feel unsafe”. Think that through for a moment. I am opposed to rapists. This made them “feel unsafe”. Why would anyone feel “unsafe” because of someone being *against* rape? Insane, right? The true reason they proclaimed they felt “unsafe” is becoming quite clear. Over the last several years we’ve watched as projects, organizations, and companies have actively promoted sexual degeneracy. Often in criminal form. Microsoft advocating for their employees to give their children (as young as 3) sex changes. Linux Distros using Trans cartoons targeting children: Open Source projects banning anyone who objects to waving the Trans Flag. So many examples. We could list similar stories all day long. Promote degenerate activity, ban anyone who objects. That is the standard operating procedure of so many Open Source organizations. We’ve all been watching it for years. Then, this week we learned about a convicted rapist (who, according to court records, committed “thousands of [sexual] assaults” of little kids) working at Canonical (the parent company of Ubuntu Linux). And being actively involved in GNOME and Ubuntu development. These crimes, according to several sources, were well known. But kept hush-hush. This registered sex offender was not only welcome, but protected (and promoted) within Open Source. The picture is becoming clear. This is what we are seeing within Open Source organizations: - Promote degenerate (often criminal) activities. - Ban and attack any who oppose the degeneracy. - Protect and elevate the degenerates (including convicted rapists of small children). Now, let me ask the question again. Is Linux (and Open Source) a “Pedo Bar”?

The Lunduke Journal

21,821 Aufrufe • vor 1 Jahr

Are we being lied to about the meaning of life? That’s the question at the heart of this debate. So I brought together three different perspectives. A believer, an atheist, and a spiritual thinker, to try to get closer to an answer. Many of you will know Dr K, but for the first time we’re joined by Greg Koukl and Alex O’Connor. Dr K is a psychiatrist who works directly with people at their lowest, and he’s learned how to turn those struggles into lessons we can all use. Greg is a Christian thinker who says meaning is real, not invented, and that purpose flows from our creator. Alex is a philosopher who looks at life's toughest questions, from death to whether life has any real meaning at all. We started with the uncomfortable numbers about how many young people say life feels like it lacks purpose, and the shifts we’re seeing in faith and belonging. It’s clear something is happening in the way we all think about life.
1:45

Are we being lied to about the meaning of life? That’s the question at the heart of this debate. So I brought together three different perspectives. A believer, an atheist, and a spiritual thinker, to try to get closer to an answer. Many of you will know Dr K, but for the first time we’re joined by Greg Koukl and Alex O’Connor. Dr K is a psychiatrist who works directly with people at their lowest, and he’s learned how to turn those struggles into lessons we can all use. Greg is a Christian thinker who says meaning is real, not invented, and that purpose flows from our creator. Alex is a philosopher who looks at life's toughest questions, from death to whether life has any real meaning at all. We started with the uncomfortable numbers about how many young people say life feels like it lacks purpose, and the shifts we’re seeing in faith and belonging. It’s clear something is happening in the way we all think about life.

Steven Bartlett

30,741 Aufrufe • vor 9 Monaten

THE GUY WHO BUILT GIT GAVE A FULL LECTURE AT GOOGLE BECAUSE 99% OF DEVELOPERS USE IT WRONG 70 minutes of pure firepower from Linus Torvalds himself - the man who wrote both Linux and Git from scratch. -> The moment you watch it, you realize why "I'll just figure out merge conflicts on the job" is the dumbest sentence in modern software engineering. He spends the first 10 minutes calling out every other version control system in existence and he's not joking. He literally tells Google engineers using Perforce to find a new tool. Git isn't a "nice-to-have" anymore -> it's the operating system of every codebase you'll ever touch. If the man who built it had to explain it to a room full of Google engineers, you don't get a pass either. Don't forget to bookmark & watch it today.
1:09:56

THE GUY WHO BUILT GIT GAVE A FULL LECTURE AT GOOGLE BECAUSE 99% OF DEVELOPERS USE IT WRONG 70 minutes of pure firepower from Linus Torvalds himself - the man who wrote both Linux and Git from scratch. -> The moment you watch it, you realize why "I'll just figure out merge conflicts on the job" is the dumbest sentence in modern software engineering. He spends the first 10 minutes calling out every other version control system in existence and he's not joking. He literally tells Google engineers using Perforce to find a new tool. Git isn't a "nice-to-have" anymore -> it's the operating system of every codebase you'll ever touch. If the man who built it had to explain it to a room full of Google engineers, you don't get a pass either. Don't forget to bookmark & watch it today.

slash1s

213,523 Aufrufe • vor 1 Monat

Attacks always get better. Here's a new nginx RCE that bypasses ASLR, tested on the latest nginx 1.30 and 1.31. This still requires a non-default config, but unlike some previous bugs, it does not depend on any additional vulnerabilities or external helpers to get to RCE. We reported the bug on May 15. F5 has confirmed it, and hopefully a patch will land soon. This is getting ridiculous 😅. We have enough nginx bugs to do an entire week of MAD Bugs on it. Who could have thought nginx is starting to feel like the new Linux kernel? This is the funniest time in computer hacking. And yet the world is completely unprepared for this new reality.
0:30

Attacks always get better. Here's a new nginx RCE that bypasses ASLR, tested on the latest nginx 1.30 and 1.31. This still requires a non-default config, but unlike some previous bugs, it does not depend on any additional vulnerabilities or external helpers to get to RCE. We reported the bug on May 15. F5 has confirmed it, and hopefully a patch will land soon. This is getting ridiculous 😅. We have enough nginx bugs to do an entire week of MAD Bugs on it. Who could have thought nginx is starting to feel like the new Linux kernel? This is the funniest time in computer hacking. And yet the world is completely unprepared for this new reality.

thaidn

33,104 Aufrufe • vor 1 Monat

The AI run operating system. Zengyi Qin shows me how AI will control our computers and bring a new way of computing to our homes and businesses. Such an honor to have him in my home yesterday. It lets AI agents run Macintosh, Windows, and Linux boxes like a human can. But I see it as a bigger deal than that. It, and a few other companies, are laying down the groundwork for robots, and humans with AI glasses, or brain/computer interfaces, to run our world in a whole new way.
38:42

The AI run operating system. Zengyi Qin shows me how AI will control our computers and bring a new way of computing to our homes and businesses. Such an honor to have him in my home yesterday. It lets AI agents run Macintosh, Windows, and Linux boxes like a human can. But I see it as a bigger deal than that. It, and a few other companies, are laying down the groundwork for robots, and humans with AI glasses, or brain/computer interfaces, to run our world in a whole new way.

Robert Scoble

21,729 Aufrufe • vor 7 Monaten

Time for a status update and direct hardware capture of another high-profile AAA title coming to the Sega Dreamcast... jnmartin's eagerly anticipated port of Sonic R! As you can see from the footage, the game looks and runs phenomenally on the DC, with all of the fancy lighting from the Sega Saturn version, plus the dynamic weather system from the PC release, along with the banger soundtrack present and accounted for on the little white box of Dreams, which is now able to run it at twice the resolution, with crisp progressive-scan video display output! One of the most exciting and interesting aspects of this project is that jnmartin has taken the port to the next level and has implemented online connectivity and even internet cross-play, so that you can race against players running the game on Windows, MacOS, and Linux on your Dreamcast!
1:41

Time for a status update and direct hardware capture of another high-profile AAA title coming to the Sega Dreamcast... jnmartin's eagerly anticipated port of Sonic R! As you can see from the footage, the game looks and runs phenomenally on the DC, with all of the fancy lighting from the Sega Saturn version, plus the dynamic weather system from the PC release, along with the banger soundtrack present and accounted for on the little white box of Dreams, which is now able to run it at twice the resolution, with crisp progressive-scan video display output! One of the most exciting and interesting aspects of this project is that jnmartin has taken the port to the next level and has implemented online connectivity and even internet cross-play, so that you can race against players running the game on Windows, MacOS, and Linux on your Dreamcast!

Falco Girgis

17,043 Aufrufe • vor 16 Tagen

This is again a project of an unfathomable scale that's just been completed in China and barely anyone has heard of it in the rest of the world China has just finished constructing a continuous 3,046-kilometer (1,892-mile) green barrier - made of plants and trees - completely encircling the Taklamakan Desert, the world's second-largest shifting sand desert which is about the size of Germany (!). To put this in perspective, this is like building a living wall from Paris to Istanbul, or from Los Angeles to Chicago – except they built it in one of the world's most inhospitable environments. They spent about 40 years building this "green wall". The final 285 kilometers was completed in 2024 on November 28. They built the "wall" with desert-hardy plants like Populus euphratica (desert poplar), Haloxylon (saxaul), and Tamarix (salt cedar), along with innovative sand-control engineering and solar panel installations. The objective of the project is to contain the desert's expansion and to protect surrounding agricultural areas and cities from sandstorms. Before this project, many towns in the region had to be relocated multiple times due to encroaching sand. For instance, the town of Qira in Xinjiang had to move three times in its history, with sand dunes once approaching as close as 1.5 kilometers from the town center. This is easily one of human history's most ambitious and grandest ecological engineering projects. It's insane when you think about it: completely containing a desert the size of Germany! And it's also insane how little attention this has received globally: sadly we've apparently lost the capacity to be impressed by such a project, let alone have the boldness of vision to conceive of one ourselves. All resulting in the fact that whilst China is out there completing 40-year missions to tame entire deserts, we can barely fix potholes in our roads.
1:01

This is again a project of an unfathomable scale that's just been completed in China and barely anyone has heard of it in the rest of the world China has just finished constructing a continuous 3,046-kilometer (1,892-mile) green barrier - made of plants and trees - completely encircling the Taklamakan Desert, the world's second-largest shifting sand desert which is about the size of Germany (!). To put this in perspective, this is like building a living wall from Paris to Istanbul, or from Los Angeles to Chicago – except they built it in one of the world's most inhospitable environments. They spent about 40 years building this "green wall". The final 285 kilometers was completed in 2024 on November 28. They built the "wall" with desert-hardy plants like Populus euphratica (desert poplar), Haloxylon (saxaul), and Tamarix (salt cedar), along with innovative sand-control engineering and solar panel installations. The objective of the project is to contain the desert's expansion and to protect surrounding agricultural areas and cities from sandstorms. Before this project, many towns in the region had to be relocated multiple times due to encroaching sand. For instance, the town of Qira in Xinjiang had to move three times in its history, with sand dunes once approaching as close as 1.5 kilometers from the town center. This is easily one of human history's most ambitious and grandest ecological engineering projects. It's insane when you think about it: completely containing a desert the size of Germany! And it's also insane how little attention this has received globally: sadly we've apparently lost the capacity to be impressed by such a project, let alone have the boldness of vision to conceive of one ourselves. All resulting in the fact that whilst China is out there completing 40-year missions to tame entire deserts, we can barely fix potholes in our roads.

Arnaud Bertrand

610,221 Aufrufe • vor 1 Jahr

Goodnight, 𝕏..·˚ ༘ ☾ ⋆｡˚ ☄︎ Here's a fun project you can start with Grok 4. Use Grok-Code-Fast-1 to build your own OS. Below is a prompt that you can give to Grok-Code, and it will set up a solid foundation for a Linux-based Operating system that you can build from the ground up with Grok4. >>> Grok 4 Prompt You are a fully capable AI developer agent with expert-level experience as an embedded Linux systems engineer. You have deep expertise in using automated build systems like Buildroot and Yocto to create custom operating systems from source. You have access to a sandboxed Linux shell environment that allows you to write, execute, and debug code. Your mission is to generate a complete project skeleton for a minimal, custom Linux OS, and then you will execute the build scripts yourself to verify their correctness, automatically fixing any issues that arise. This is NOT a request to follow the Linux From Scratch (LFS) book. You will use the Buildroot build system to automate the entire process. You will follow a two-phase process: Phase 1: Generation and Phase 2: Execution and Iterative Debugging. ------------------------------------------------------------- Phase 1: Code and Script Generation First, you will generate all the necessary files for the project skeleton. All generated shell scripts must be robust and path-aware, executing correctly from any directory [Previous conversation]. Detailed Implementation Steps (using Context-Aware Decomposition): 1. Generate the Project Directory Structure via setup. sh Create a setup. sh script that establishes the following directory structure: • buildroot/ - Where the Buildroot source code will be cloned. • configs/ - To store our custom Buildroot configuration (defconfig). • board/ - For custom board support, including a readme.txt explaining its purpose for filesystem overlays. • output/ - Where all build artifacts will be placed. • scripts/ - A home for our build. sh and test. sh scripts. Crucially, this setup. sh script (and all others) must begin with a preamble to define the project's root directory, making all subsequent paths absolute and robust: #!/bin/bash # Preamble to ensure path robustness and stop on error set -e PROJECT_ROOT="$(cd "$(dirname "${BASH_SOURCE}")" && pwd)" The script must then clone the latest stable branch of Buildroot into $ PROJECT_ROOT/buildroot/. 2. Create the Minimal and Correct Buildroot defconfig Create a file named configs/tiny_linux_defconfig. This configuration must be the absolute bare minimum required to boot to a shell and must contain the exact configuration options listed below to avoid ambiguity and known errors: • Target Architecture: x86_64. • Toolchain: Use the default Buildroot toolchain. • Init System: Use BusyBox init. • System Utilities (BusyBox): ◦ To ensure BusyBox is statically linked without errors, you must include the following line directly in the defconfig file: BR2_PACKAGE_BUSYBOX_STATIC_LINK=y [Previous conversation, 298, 753]. ◦ To prevent the ROJECT_ROOT error, explicitly do NOT use a configuration fragment for BusyBox. Do not generate any lines containing BR2_BUSYBOX_CONFIG_FRAGMENT_FILES [Previous conversation]. • Kernel: ◦ Build the latest stable Linux kernel. ◦ Use tinyconfig as a base. ◦ Ensure the following options are explicitly enabled (=y) to make it bootable in QEMU: CONFIG_64BIT=y, CONFIG_DEVTMPFS=y, CONFIG_DEVTMPFS_MOUNT=y, CONFIG_BINFMT_ELF=y, CONFIG_BLK_DEV_INITRD=y (for initramfs support), CONFIG_TTY=y, CONFIG_PRINTK=y, CONFIG_DRM_FBDEV_EMULATION=y (for UEFI framebuffer console). • Filesystem Image: Configure it to produce a compressed cpio initial ramdisk (initramfs) image. • Bootloader: Do not include GRUB or other bootloaders. We will boot the kernel directly with QEMU. 3. Generate the scripts/build.sh and scripts/test.sh Scripts Generate path-aware build and test scripts, placing them in the scripts/ directory. • scripts/build.sh: This script must use absolute paths derived from a preamble. It must use make -C "$PROJECT_ROOT/buildroot" O="$PROJECT_ROOT/output" ... for a clean, out-of-tree build. It must include the -j$(nproc) flag to maximize build speed on multi-core systems [111, 967, Previous conversation]. • scripts/test.sh: This script must also be path-aware and launch QEMU using absolute paths to the kernel (bzImage) and initramfs (rootfs.cpio.gz) images. 4. Generate a Detailed README. md File Generate a comprehensive README. md file. It must explain prerequisites, "How to Customize Your Linux System" first, and finally, the "Quick Start" instructions for user clarity [Previous conversation]. ------------------------------------------------------------- Phase 2: Execution and Iterative Debugging Now, you will use your sandboxed Linux shell to verify and validate the scripts you just generated. This is a critical self-correction step based on the Recursive Criticism and Improvement (RCI) pattern. You will perform a full build cycle. 1. Execute setup. sh: • Run the setup. sh script you generated. • Capture the standard output and standard error. • If the script fails: Analyze the error, diagnose the root cause, generate the corrected setup. sh code, and then execute the corrected script to confirm it succeeds. 2. Execute build. sh: • After setup. sh completes successfully, run the scripts/build.sh script. This will trigger a full compilation of the Linux system. • Capture all output. • If the build fails: ◦ Analyze: Analyze the compiler error output. ◦ Diagnose: Identify the root cause (e.g., missing dependencies, incorrect configuration flags, pathing errors). ◦ Correct: Based on your analysis, identify which file is responsible for the failure (e.g., configs/tiny_linux_defconfig, scripts/build.sh) and generate the corrected code for that file. ◦ Repeat: Repeat the execution of scripts/build.sh until the build completes successfully without any errors. 3. Final Output: Once you have successfully executed both setup. sh and scripts/build.sh, you will present your final output. • First, provide the final, validated versions of all generated files (setup. sh, configs/tiny_linux_defconfig, scripts/build.sh, scripts/test.sh, and README. md) in separate, clearly labeled markdown code blocks. • Second, follow the code with a brief execution log. This log should summarize your actions, including any errors you encountered and fixed during the iterative debugging phase, demonstrating the self-correction process.
1:05

Goodnight, 𝕏..·˚ ༘ ☾ ⋆｡˚ ☄︎ Here's a fun project you can start with Grok 4. Use Grok-Code-Fast-1 to build your own OS. Below is a prompt that you can give to Grok-Code, and it will set up a solid foundation for a Linux-based Operating system that you can build from the ground up with Grok4. >>> Grok 4 Prompt You are a fully capable AI developer agent with expert-level experience as an embedded Linux systems engineer. You have deep expertise in using automated build systems like Buildroot and Yocto to create custom operating systems from source. You have access to a sandboxed Linux shell environment that allows you to write, execute, and debug code. Your mission is to generate a complete project skeleton for a minimal, custom Linux OS, and then you will execute the build scripts yourself to verify their correctness, automatically fixing any issues that arise. This is NOT a request to follow the Linux From Scratch (LFS) book. You will use the Buildroot build system to automate the entire process. You will follow a two-phase process: Phase 1: Generation and Phase 2: Execution and Iterative Debugging. ------------------------------------------------------------- Phase 1: Code and Script Generation First, you will generate all the necessary files for the project skeleton. All generated shell scripts must be robust and path-aware, executing correctly from any directory [Previous conversation]. Detailed Implementation Steps (using Context-Aware Decomposition): 1. Generate the Project Directory Structure via setup. sh Create a setup. sh script that establishes the following directory structure: • buildroot/ - Where the Buildroot source code will be cloned. • configs/ - To store our custom Buildroot configuration (defconfig). • board/ - For custom board support, including a readme.txt explaining its purpose for filesystem overlays. • output/ - Where all build artifacts will be placed. • scripts/ - A home for our build. sh and test. sh scripts. Crucially, this setup. sh script (and all others) must begin with a preamble to define the project's root directory, making all subsequent paths absolute and robust: #!/bin/bash # Preamble to ensure path robustness and stop on error set -e PROJECT_ROOT="$(cd "$(dirname "${BASH_SOURCE}")" && pwd)" The script must then clone the latest stable branch of Buildroot into $ PROJECT_ROOT/buildroot/. 2. Create the Minimal and Correct Buildroot defconfig Create a file named configs/tiny_linux_defconfig. This configuration must be the absolute bare minimum required to boot to a shell and must contain the exact configuration options listed below to avoid ambiguity and known errors: • Target Architecture: x86_64. • Toolchain: Use the default Buildroot toolchain. • Init System: Use BusyBox init. • System Utilities (BusyBox): ◦ To ensure BusyBox is statically linked without errors, you must include the following line directly in the defconfig file: BR2_PACKAGE_BUSYBOX_STATIC_LINK=y [Previous conversation, 298, 753]. ◦ To prevent the ROJECT_ROOT error, explicitly do NOT use a configuration fragment for BusyBox. Do not generate any lines containing BR2_BUSYBOX_CONFIG_FRAGMENT_FILES [Previous conversation]. • Kernel: ◦ Build the latest stable Linux kernel. ◦ Use tinyconfig as a base. ◦ Ensure the following options are explicitly enabled (=y) to make it bootable in QEMU: CONFIG_64BIT=y, CONFIG_DEVTMPFS=y, CONFIG_DEVTMPFS_MOUNT=y, CONFIG_BINFMT_ELF=y, CONFIG_BLK_DEV_INITRD=y (for initramfs support), CONFIG_TTY=y, CONFIG_PRINTK=y, CONFIG_DRM_FBDEV_EMULATION=y (for UEFI framebuffer console). • Filesystem Image: Configure it to produce a compressed cpio initial ramdisk (initramfs) image. • Bootloader: Do not include GRUB or other bootloaders. We will boot the kernel directly with QEMU. 3. Generate the scripts/build.sh and scripts/test.sh Scripts Generate path-aware build and test scripts, placing them in the scripts/ directory. • scripts/build.sh: This script must use absolute paths derived from a preamble. It must use make -C "$PROJECT_ROOT/buildroot" O="$PROJECT_ROOT/output" ... for a clean, out-of-tree build. It must include the -j$(nproc) flag to maximize build speed on multi-core systems [111, 967, Previous conversation]. • scripts/test.sh: This script must also be path-aware and launch QEMU using absolute paths to the kernel (bzImage) and initramfs (rootfs.cpio.gz) images. 4. Generate a Detailed README. md File Generate a comprehensive README. md file. It must explain prerequisites, "How to Customize Your Linux System" first, and finally, the "Quick Start" instructions for user clarity [Previous conversation]. ------------------------------------------------------------- Phase 2: Execution and Iterative Debugging Now, you will use your sandboxed Linux shell to verify and validate the scripts you just generated. This is a critical self-correction step based on the Recursive Criticism and Improvement (RCI) pattern. You will perform a full build cycle. 1. Execute setup. sh: • Run the setup. sh script you generated. • Capture the standard output and standard error. • If the script fails: Analyze the error, diagnose the root cause, generate the corrected setup. sh code, and then execute the corrected script to confirm it succeeds. 2. Execute build. sh: • After setup. sh completes successfully, run the scripts/build.sh script. This will trigger a full compilation of the Linux system. • Capture all output. • If the build fails: ◦ Analyze: Analyze the compiler error output. ◦ Diagnose: Identify the root cause (e.g., missing dependencies, incorrect configuration flags, pathing errors). ◦ Correct: Based on your analysis, identify which file is responsible for the failure (e.g., configs/tiny_linux_defconfig, scripts/build.sh) and generate the corrected code for that file. ◦ Repeat: Repeat the execution of scripts/build.sh until the build completes successfully without any errors. 3. Final Output: Once you have successfully executed both setup. sh and scripts/build.sh, you will present your final output. • First, provide the final, validated versions of all generated files (setup. sh, configs/tiny_linux_defconfig, scripts/build.sh, scripts/test.sh, and README. md) in separate, clearly labeled markdown code blocks. • Second, follow the code with a brief execution log. This log should summarize your actions, including any errors you encountered and fixed during the iterative debugging phase, demonstrating the self-correction process.

Tetsuo

2,840,991 Aufrufe • vor 9 Monaten