You know, I think this Explorer is exactly the tool many of us lacked. Reading the Linux kernel source always felt daunting — thousands of files, confusing paths, complex structure. This feels like a “map” that helps you orient yourself, see how parts interconnect, how VFS works, how modules tie together. Yeah, sometimes a feature breaks (API limits, errors opening directories), but even so — this is a great way to peek “under the hood,” understand the architecture, and take the first step. Big thanks to the folks behind it.
Linux Kernel Explorer
31–40 of 101 posts
Re: Linux Kernel Explorer
#32Can I somehow deploy it locally?
Re: Linux Kernel Explorer
#33Earlier quoted context omitted.
Talmud - the original hypertext (tm) (*maybe, not 100% sure)
see also Pi, the movie, although it's more about numbers and the Kabbalah :) https://en.wikipedia.org/wiki/Pi_(film)
Long-time HN lurker here! Was excited to see this discussion around my major interests of Talmud, Kabbalah, and tech.
There are a lot of misconceptions and mystique surrounding the Talmud. I'd like to take the opportunity to clarify some fundamental aspects, as relates to the discussion here:
The famous "Talmud page" (discussed in the links in the parent comment) was set by a Christian printer in the 16th century.
It emulated a common layout in medieval Christian manuscripts for Christian primary texts and commentaries [0].
The analogy of the Talmud to a hypertext isn't especially apt, IMO. The Talmud indeed extensively cites Bible and Mishnah, and uses lots of technical terms. In this regard, a better analogy is to legal literature (which is what the Talmud in fact is). While being couched as a (fictional) "conversation"/dialogue between rabbis who lived over the course of ~400 years (100 CE to 500 CE).
In fact, Kabbalah (as another commenter mentioned) is a better example of a “hypertext,” since it’s full of recurring symbols that point to different Sefirot and other core concepts.
(By way of credentials: I hold an MA in academic Talmud and Kabbalah, write on these subjects in several venues, and have presented at academic workshops. Over the past two years, I’ve also been developing digital-humanities projects related to this work.)
References:
[0] https://seforimblog.com/2023/06/from-print-to-pixel-digital-...
[1] https://www.ezrabrand.com/p/beyond-the-mystique-correcting-c...
Re: Linux Kernel Explorer
#34I really like this reactive guide style interface, which maybe could be quite a good project idea like mdBook[1] but also you to insert quizzes/examples alongside static notes
Re: Linux Kernel Explorer
#35Were the quiz questions generated by a human or AI?
Re: Linux Kernel Explorer
#36Earlier quoted context omitted.
see also Pi, the movie, although it's more about numbers and the Kabbalah :) https://en.wikipedia.org/wiki/Pi_(film)
Long-time HN lurker here! Was excited to see this discussion around my major interests of Talmud, Kabbalah, and tech. There are a lot of misconceptions and mystique surrounding the Talmud. I'd like to take the opportunity to clarify some fundamental aspects, as relates to the discussion here: The famous "Talmud page" (discussed in the links in the parent comment) was set by a Christian printer in the 16th century. It…
[flagged]
Re: Linux Kernel Explorer
#37You know, I think this Explorer is exactly the tool many of us lacked. Reading the Linux kernel source always felt daunting — thousands of files, confusing paths, complex structure. This feels like a “map” that helps you orient yourself, see how parts interconnect, how VFS works, how modules tie together. Yeah, sometimes a feature breaks (API limits, errors opening directories), but even so — this is a great way to p…
I don't get it. I can't pull master, I can't grep, I can't edit and I certainly can't gmake there.
What's the use?
Re: Linux Kernel Explorer
#38[dead]
Re: Linux Kernel Explorer
#39You know, I think this Explorer is exactly the tool many of us lacked. Reading the Linux kernel source always felt daunting — thousands of files, confusing paths, complex structure. This feels like a “map” that helps you orient yourself, see how parts interconnect, how VFS works, how modules tie together. Yeah, sometimes a feature breaks (API limits, errors opening directories), but even so — this is a great way to p…
I don't get it. I can't pull master, I can't grep, I can't edit and I certainly can't gmake there. What's the use?
I believe it's a navigation tool, with pointers to important parts of the code. Useful for those that want to learn about the code base but do not know where to get started.
Re: Linux Kernel Explorer
#40I love this idea. I like exploring code of interesting projects even if I don't intend to ever work on them, but in complex software I don't know much about it's hard to even find where are the most important basic parts. This allows me to easily find and see how some things in the kernel look like. Found a bug: in the Chapter 2, when I click on "open" next to "mm/" or other dirs, I get an error: " Failed to load fil…
Yes it's good idea and nicely executed. For the same reason I created a couple of projects with the same goal of lowering the barrier to entry to the linux kernel: - an app to follow the UDP packet flow in the linux kernel source code: https://dmkskd.github.io/linux-kernel-network-stack-visualiz... - a (hopefully) simple way to play with the linux kernel source code on a mac: https://github.com/dmkskd/linux-kernel-de…
I love your UDP packet flow tool, kudos for making that! I've always wondered how packets move through an OS. Also interesting how many gotos I see all over the place, even though everyone says "goto is the devil". Then again maybe this code was written long before that "proverb" came into existence.