cjd8

What a moronic thing to say...

Funny, I'm working on a simple tool that pulls the atom feed of the latest patches from lore with Python, and I just slip a User-Agent header into the requests.get() and it works great.

I recently started a blog documenting my kernel work, and thought that I should create a series that helps people make their first contribution. Please let me know whether you have any ideas!

Not bad, I'd still use Claws-mail for reading and replying to kernel mailing lists, but good to know that people are developing tools with which you don't have to rely on an ancient email client.

Reminds me a lot of hkml, which you mentioned in the readme :)

> rewrite of already popular technology in a different language > look at commit history > "Claude xxx committed yyy ago"

I'm sorry, but what is this need to just vibe code a port of an existing technology to a different language/framework/etc.? If it's just a personal challenge then sure I guess, but this surely can't be used as a real product?

I would assume that it's not just the fuel, but also the construction materials etc. It's in the article that they had to grind down the surfaces of the spent fuel pool, the residue from that would probably weigh a lot on its own!

>Huh... I thought Linux actually required MMUs. I was under the impression it'd never run on these old consoles because of that. Learned something new today.

There have been variants of the kernel around for some time that can run on microcontrollers without an MMU (mainly uCLinux).

Ah, well in the Czech Republic universities get funding based on the number of currently enrolled students, not graduates. Some places will therefore accept 1000 into a CS program, only to have <100 people actually graduate.

As for the appeal - these usually aren't successful, even my thesis advisor said that he probably wouldn't go out of his way to talk to the analysis course examiner etc. etc.

There is, however I didn't really have a valid reason for an appeal so I just went ahead with it and started applying for jobs.

Essentially all Czech universities have a rule where you can only twice enroll in the same course - failing to do so will lead to termination. Nevertheless I still have my credits so I'll try to get them accepted at the new university.

It was mostly painful to see people I had courses with graduate just this month, however I do have a good software engineering job so all is well?

Hard to say, different language - different problems. Nevertheless Sashiko gets the big picture and its main concerns are race conditions, bad register mapping etc., issues that concern C code style are minimal (at least in the patches I write haha)

Great job! A few months ago I was kicked out of university for failing my Real Analysis course a second time (4 years of CS suddenly gone, thesis was half done) and had to get a full time job. Now I got accepted to a different public university to study on a weekend basis. This article makes me less anxious about my upcoming studies.

Thanks! Feel free to add more "fortunes" by submitting a pull request.

Realizing that I don't do any programming for fun anymore, I made a program that prints the horoscope for the PID of a Linux process. The Fowler-No-Voll hash ensures uniqueness for each day, guaranteeing a deterministic output. A friend of mine added support for tarot cards. I recommend just appending the command to your .bashrc to get the horoscope of your current running bash instance. Pull requests are welcome!

okay, banner is a classic, but dadadodo is pretty interesting

Not a kernel veteran, but I do send patches and reviews occasionally and as mentioned in the article, Sashiko is a big help. It can detect very obscure race conditions, stack leaks and other bugs that could cause a kernel panic. It's also really good at analyzing subsystem-specific nuances (in the IIO subsystem for example, it can get chip parameters from a datasheet and actually check whether the code reflects it correctly, e. g. with timing).