#Kernel compilation

[forlinx]

🖥️ Learn how to enable virtual networking on Linux 4.1.15 with Forlinx's FETMX6ULL-C platform! Follow the detailed configuration methods for a seamless setup.

[yiffos-official]

i randomly found my matching ram at the cashies for 10$ today so now i'm up 2 32gb of ram.

time 2 compile many many things

[dgdraws]

OC tober Day 11: Symbolism/Themes

They are very much cool jock girl 4 rich mean girl. Ellis is constantly draping her leather jacket around Isa's shoulders as she cools down and picks the viscera from her nails. Despite the fact Ellis could probably catch a bullet with her teeth, Isa insists on standing between her and danger, sometimes so proactively Ellis has to talk her "princess" down from some truly unhinged plans. Their players are married irl and it is a treat to watch them get to go nuclear for each other.

Reposting this gigantic illustration from our New York After the End vtm game 🧛‍♀️

This one is full of symbolism, from official vtm lore to real maps of nyc's watershed.

Ellis and Isa are the oldest vampires in our coterie, a gangrel and a lasombra respectively. Their shared penchant for vampiric history brought them together in the late 80's and they slowburned for a few decades before finally admiting their feelings in the "present" of 2007. Kindred weave a tangled web so Kath (my pc) is very glad to have these two nerds around to unravel the mysteries that pursue them. Ellis and Isa may be the brains, but they're also the brawn. Ellis can punch your heart straight out of your chest and Isa gleefully plumbs the depths of her mastery over shadows and the abyss to throw people around the room at the slightest provocation.

^one more for the road :)

[sympathischeufos]

.

[unidentifiedfuckingthing]

til the dsi/3ds only lets you use fat32 sd cards. even though you can put games on there right?? and 3ds games are often exactly 4gb on the cartridge and fat32 only allows files up to exactly 4gb?? is there not any header shit that would make it larger as a file in a filesystem??? i guess maybe that makes it easier for me because afaict fat32 is hardcoded into the linux kernel where exfat is a module

[alpine-official]

"I use Linux as my operating system," I state proudly to the unkempt, bearded man. He swivels around in his desk chair with a devilish gleam in his eyes, ready to mansplain with extreme precision. "Actually", he says with a grin, "Linux is just the kernel. You use GNU+Linux!' I don't miss a beat and reply with a smirk, "I use Alpine, a distro that doesn't include the GNU Coreutils, or any other GNU code. It's Linux, but it's not GNU+Linux." The smile quickly drops from the man's face. His body begins convulsing and he foams at the mouth and drops to the floor with a sickly thud. As he writhes around he screams "I-IT WAS COMPILED WITH GCC! THAT MEANS IT'S STILL GNU!" Coolly, I reply "If windows were compiled with GCC, would that make it GNU?" I interrupt his response with "-and work is being made on the kernel to make it more compiler-agnostic. Even if you were correct, you won't be for long." With a sickly wheeze, the last of the man's life is ejected from his body. He lies on the floor, cold and limp. I've womansplained him to death.

[techav]

On Celebrating Errors

Isn't it beautiful? The lovely formatted tables of register and stack contents, the trace of function addresses and parameters, the error message ... it's the most beautiful kernel panic I have ever seen.

Why on earth would I be so excited to see a computer crash? What could possibly be beautiful about a kernel panic?

This kernel panic is well-earned. I fought hard to get it.

This kernel panic came from a current NetBSD kernel, freshly compiled and running on Wrap030, my 68030 homebrew computer. It is the result of hours upon hours of work reading through existing code, scattered documentation and notes, writing and rewriting, and endless compiling.

And it's just the start.

As I've said before, a goal of this project has always been to build something capable of running some kind of Unix-like operating system. Now that I finally have all the necessary pieces of hardware, plus a good bootloader in ROM, it's time to give it a shot. I'm not that great with this type of programming, but I have been getting better. I might just be able to brute force my way through hacking together something functional.

It is hard.

There is some documentation available. The man(9) pages are useful, and NetBSD has a great guide to setting up the build environment for cross-compiling the kernel. There are some published papers on what some people went through to port NetBSD to this system or that. But there's nothing that really explains what all these source code files are, and which parts really need to be modified to run on a different system.

I had a few false starts, but ultimately found an existing 68k architecture, cesfic, which was a bare minimum configuration that could serve well as a foundation for my purposes. I copied the cesfic source directory, changed all instances of the name to wrap030, made sure it still compiled, then set about removing everything that I didn't need. It still compiled, so now it's was time to add in what I did need.

... how ... do I ... ?

This is where things get overwhelming very quickly. There is documentation on the core functions required for a new driver, there's documentation on the autoconf system that attaches drivers to devices in the tree, and there's plenty of drivers already to reference. But where to start?

I started by trying to add the com driver for the 16550 UARTs I'm using. It doesn't compile because I'm missing dependencies. The missing functions are missing because of a breaking change to bus.h at some point; the com driver expects the new format but the cesfic port still uses the old. So I needed to pull in the missing functions from another m68k arch. Which then required more missing functions and headers to be pulled in. Eventually it compiled without error again, but that doesn't mean it will actually run. I still needed to add support for my new programmable timer, customize the startup process, update hardware addresses, make sure it was targeting 68030 instead of 68040 ...

So many parts and pieces that need to be updated. Each one requiring searching for the original function or variable declaration to confirm expected types or implementation, then searching for existing usages to figure out what it needs ... which then requires searching for more functions and variable types.

But I got something that at least appeared to have all the right parts and compiled without error. It was time to throw it on a disk, load it up, and see what happened.

Nothing happened, of course. It crashed immediately.

I have no debugging workflow I can rely on here, and at this stage there isn't even a kernel console yet. All I could do was add little print macros to the locore startup code and see where it failed. Guess, test, and revise.

I spent a week debugging the MMU initialization. If the MMU isn't properly configured, everything comes to an abrupt halt. Ultimately, I replaced the cesfic machine-specific initialization code and pmap bootstrapping code with functions from yet another m68k arch. And spent another day debugging before realizing I had missed a section that had comments suggesting it wasn't for the 68030 CPU, but turned out to be critical for operation of kernel memory allocation.

Until this point, I was able to rely on the low-level exception handling built into my bootloader if my code caused a CPU exception. But with the MMU working, that code was no longer mapped.

So then came another few hours learning how to create a minimal early console driver. An early console is used by the kernel prior to the real console getting initialized. In this case, I'm using the MC6850 on my mainboard for the early console, since that's what my bootloader uses. And finally the kernel was able to speak for itself.

It printed its own panic.

The first thing the kernel does is initialize the console. Which requires that com driver and all the machine-specific code I had to write. The kernel is failing at its step #1.

But at least it can tell me that now. And given all the work necessary to get to this point, that kernel panic data printing to the terminal is absolutely beautiful.

[debian-official]

Linux ask game

1 - what was your first distro? 2 - what was your biggest linux fuckup? 3 - have you ever run rm / on real hardware? 4 - do you dual boot or have a secondary machine with windows? 5 - did you change your default shell? 6 - are you afraid of git? 7 - what was the first machine you installed linux on? 8 - do you know your way around vim keybinds? 9 - what is your favourite non-os software? 10- biggest linux pet peeve? 11- biggest annoyance with the community? 12- do you like your current distro? 13- Xenia or Tux? 14- what software are you never using again? 15- stock distro or hours of yak shaving? 16- have you compiled the kernel?

[exiledandwanderingfox]

So we all know that authors have their little things that they use every now and then, just something they go back to.

Now it’s rude to make fun of authors. However: I don’t know if I really consider SJM an author, and she happens to be a vile person in general, so here’s a list a bunch of people and I compiled of her overused phrases and things she should’ve done her research on before writing.

Overused SJM phrases:

-simpering smile

-watery bowels

-I didn’t let myself think about it

-vulgar gesture

-he climaxed with a roar

-seed

-kernel

-she bared her teeth

-claws and talons and teeth

-bellowed

-shook the mountains

-slid his hands into his pockets

-and —- and —- and —- and —-

-Picked lung off their shoulder

-invisible lint

-he came with a roar

-velvet wrapped steel

-his wings twitched

-his balls tightened

Running list of things SJM should have done her research on:

-village dynamics

-growing crops and flowers

-household duties in this time period (medieval???)

- hunting

-painting

-gardening

-dancing

-religion and mythology

-medicine

-battle

-sibling dynamics

-reading

-historically accurate diseases

-instrument playing

-international relations

-sizing in relation

-infastructure

-Do they breed as fast as humans though?

-Basic Biology and Anatomy

-economics

-money in general

-red hair

-Hybern vs Prythian

-PTSD, Trauma, Trauma Responses

-sexual trauma/assault/violence/exploration

-does divorce exist? is the bond/mating ceremony stronger then the marriage?

-reading disabilities

-any sort of art research

-chronic pain

-immigration control in fantasy cities?

-systemic issues within a city

-poverty in a city

[machine-saint]

there was an article going around my social media elsewhere that was talking about how programming language design needs feminism. i think there are good notes in the article about English-centricism, and i can't speak as to whether or not the problems the paper identifies (emphasis on formal theory over "is this pleasant to use") are actually a problem, but i was struck by this quote (in the paper embedded at the bottom)

The current standards of evaluation in the PL community are set from a masculine perspective as well, valuing formalism and formal methods over user studies, quantitative over qualitative work, and the examining of technical aspects over context and people.

because... i had previously seen people argue that the "C is good enough, just don't write bad code lmao" attitude that you see a lot of the time is also masculine, because it's very individualist and "the compiler should get out of my way" type thinking. this came to a head recently with the whole Rust-in-the-kernel thing.

so we have a situation where in one case, formalism is masculine. in another, lack of formalism is masculine. and i think this is my problem with a lot of this sort of feminist stuff: it makes these big sweeping statements about how such-and-such behavior is masculine and doesn't consider cases where the opposite is also masculine.

i think the paper also oversteps by effectively using "feminism" to mean "ask[ing] why things are the way they are, and by that [examining] how we can make them more fair", regardless of whether or not gender has anything to do with it. so "feminism" sort of gets scope-crept in a way that i don't think is conducive; if i were to advocate for installing a wheelchair ramp or a curb cut, this is now feminism.

don't take this as a referendum on All Of Feminism, i'm just annoyed

[yesterdays-xkcd]

This really is a true story, and she doesn't know I put it in my comic because her wifi hasn't worked for weeks.

Cautionary [Explained]

Transcript Under the Cut

Linux: A True Story: [Cueball talks on a cell phone.] Week One: Phone: Hey, it's your cousin. I got a new computer but don't want Windows. Can you help me install "Linux"? Cueball: Sure.

[Cueball's cousin sits in an office chair with her laptop on her lap. She is on the phone.] Week Two: Cousin: It says my XORG is broken. What's an "XORG"? Where can I look that up? Cueball: Hmm, lemme show you man pages.

[Cueball's cousin crouches on the floor with the laptop on her lap. She is still on the phone.] Week Six: Cousin: Due to auto-config issues, I'm leaving Ubuntu for Debian. Cueball: Uh. Cousin: Or Gentoo. Cueball: Uh oh.

[Cueball's cousin lies on her stomach with the laptop on the floor. On the floor are several pieces of paper and a book. Cueball stands to her left.] Week Twelve: Cueball: You haven't answered your phone in days. Cousin: Can't sleep. Must compile kernel. Cueball: I'm too late.

[Box with text:] Parents: talk to your kids about Linux... Before somebody else does.

[codingquill]

What happens when you start your computer ? ( Booting a computer )

We studied this in the lecture today, and it was quite interesting. What makes something a hundred times simpler than it is? Creating a story about it. That's why I made this super fun dialog that will help you understand it all.

I've set up a drive to compile everything I create related to the Linux operating system. Feel free to explore it for more details on the topics discussed in the conversation below. Check it out here.

Have a fun read, my dear coders!

In the digital expanse of the computer, Pixel, the inquisitive parasite, is on a microventure with Binary, a wise digital guide. Together, they delve into the electronic wonders, uncovering the secrets hidden in the machine's core.

Pixel: (zooming around) Hey there! Pixel here, on a mission to demystify the tech wonders . There's a creature named Binary who knows all the ins and outs. Let's find them!

Binary: (appearing with a flicker of pixels) Pixel, greetings! Ready to explore what happens inside here?

Pixel: Absolutely! I want the full scoop. How does this thing come alive when the human outside clicks on "start"?

Binary: (with a digital chuckle) Ah, the magic of user interaction. Follow me, and I'll reveal the secrets.

(They traverse through the circuits, arriving at a glowing portal.)

Pixel: (inquiring) What's the deal with this glowing door?

Binary: (hovering) Pixel, behold the BIOS - our machine's awakening. When the human clicks "start," the BIOS kicks in, checking if our components are ready for action.

(They proceed to observe a tiny program in action.)

Pixel: (curious) Look at that little messenger running around. What's it up to?

Binary: (explaining) That, Pixel, is the bootloader. It plays courier between the BIOS and the operating system, bringing it to life.

Pixel: (excitedly buzzing) Okay! How does the computer know where to find the operating system?

Binary: Ah, Pixel, that's a tale that takes us deep into the heart of the hard disk. Follow me.

(They weave through the digital pathways, arriving at the hard disk.)

Pixel: (curious) Huh? Tell me everything!

Binary: Within this hard disk lies the treasure chest of the operating system. Let's start with the Master Boot Record (MBR).

(They approach the MBR, Binary pointing to its intricate code.)

Binary: The MBR is like the keeper of the keys. It holds crucial information about our partitions and how to find the operating system.

Pixel: (wide-eyed) What's inside?

Binary: (pointing) Take a look. This is the primary boot loader, the first spark that ignites the OS journey.

(They travel into the MBR, where lines of code reveal the primary boot loader.)

Pixel: (in awe) This tiny thing sets the whole show in motion?

Binary: (explaining) Indeed. It knows how to find the kernel of the operating system, which is the core of its existence.

(They proceed to the first partition, where the Linux kernel resides.)

Pixel: (peering into the files) This is where the OS lives, right?

Binary: (nodding) Correct, Pixel. Here lies the Linux kernel. Notice those configuration files? They're like the OS's guidebook, all written in text.

(They venture to another partition, finding it empty.)

Pixel: (confused) What's the story with this empty space?

Binary: (smirking) Sometimes, Pixel, there are barren lands on the hard disk, waiting for a purpose. It's a canvas yet to be painted.

Pixel: (reflecting) Wow! It's like a whole universe in here. I had no idea the operating system had its roots in the hard disk.

(They continue their microventure, navigating the binary landscapes of the computer's inner world.Pixel gazes at the screen where choices appear.)

Pixel: What's happening here?

Binary: (revealing) This is where the user picks the operating system. The computer patiently waits for a decision. If none comes, it follows the default path.

(They delve deeper into the digital code, where applications start blooming.)

Pixel: (amazed) It's like a digital garden of applications! What's the enchantment behind this?

Binary: (sharing) Here, Pixel, is where the applications sprout to life. The operating system nurtures them, and they blossom into the programs you see on the screen.

Pixel: (excited) But how does the machine know when the human clicks "start"?

Binary: It's the BIOS that senses this initiation. When the human triggers "start," the BIOS awakens, and we embark on this mesmerizing journey.

[pa-dead]

I'm going to put my head through a wall qualcomm I hate you why cant you upstream your GODDAMN DRIVERS already I'm sick of this hack reverse engineered shit

I have been trying to get ALARM to boot on my snapdragon laptop for the past 3 days I don't wanna have to learn to compile my own kernel but Ubuntu is the only working distro currently

I may simply perish

[debian-sid]

Hold my beer it’s time to compile a kernel

[sunny-days-and-warm-mournings]

It is finally finished!! I am done and is so happy!!!

This is an AU exploring the concept of Sūn Wùkōng/Dàshèng as a Yaksha and Tu Di Gong, rather than being a Yaoguai Warlord during his later years reigning as the Monkey King.

This AU follows the beginning (with some changes here and there) up until Wùkōng's shenanigans with Ao Guang, then he went on a separate path from Wu Cheng'en's novel.

In this iteration our favourite Monkey explored the realms as he burned up time, but then he took a particular interest in the humans' ways of producing food. Since Dàshèng was so used to the grandeur and bounties of Huagoushan (being surrounded by such lush forests and mountains that never withered nor died) he sort of took pity on them before deciding to help them grow their crops much better.

But this is just the very much shortened summary of the beginning of this AU, and I have compiled some research and even more lore in my Google Documents just to expand on this idea more.

This— Westward To Tathāgatagarbha Lore Google Documents

This is the Google Document of my AU, which I highly recommend for you to read! It explains all the other details and such on this story! I did my best on making them but there would be still mistakes that I have yet to find, but it should be decent!!

This is a more casual look for Dàshèng/Wùkōng for this AU as well as some brief pointers! I made this before the portrait so some things might have changed.

(Don't mind him holding a cup of beer it's fine.)

Taken from the server (with some hints for the next half of the archives/docs) which instantly kickstarted this whole thing haahahjjjss, but it really was so fun talking about it to others! They gave me more inspiration that I can handle.

And what is Tathāgatagarbha you ask? (Brief)

In Buddhist philosophy, Buddha-nature is the potential for all sentient beings to become a Buddha or the fact that all beings already have a pure buddha-essence within. "Buddha-nature" is the common English translation for several related Mahayana Buddhist terms, most notably tathāgatagarbha and buddhadhātu, but also sugatagarbha, and buddhagarbha. Tathāgatagarbha can mean "the womb" or "embryo" (garbha) of the "thus-gone one" (tathāgata), and can also mean "containing a tathāgata". Buddhadhātu can mean "buddha-element," "buddha-realm" or "buddha-substrate"

The Chinese translated the term tathāgatagarbha as rúláizàng (如来藏), or "Tathāgata's (rúlái) storehouse" (zàng). According to Brown, "storehouse" may indicate both "that which enfolds or contains something", or "that which is itself enfolded, hidden or contained by another." The Tibetan translation is de bzhin gshegs pa'i snying po, which cannot be translated as "womb" (mngal or lhums), but as "embryonic essence", "kernel" or "heart".

The term tathagatagarbha first appears in the Tathāgatagarbha sūtras, which date to the 2nd and third centuries CE.

There will be more to this in the future when I'm finished researching more about it.

Also, speaking of people that inspire me, I'm calling my dear friends here who I think might like this: @digitalagepulao @kaijufluffs @sketching-shark @lavaflowe @sixteenthchapel @jttw-monkeybusiness and @hcdragoncat !!

Special thanks to Pardal and Grandpa Sun for getting me to write more of this too :D I had such great fun!

I have so much more to add to the docs and here but this is all for now :) and honestly this is one of the greatest projects I've started aside from the older ones. I'll come back again soon with more additions and art! And lore (And maybe some interactions with a few West Heaven occupants??)!!!

[verilog-official]

been trying to install gentoo for forever

I thought it'd be easy because I have so much experience with Linux and how it generally works, messing around with the actual system a fair amount

but like gentoo is a whole different beast

it might be due to the fact that it's a different kernel config (I've only ever extensively used Debian) but like

it's also annoying how I have to wait so long for things to compile. I'm kinda considering setting up some sort of compilation server on my more powerful computer at home or something that outsources the compiling to it but idk how to do that