Skip to main content

A New Light of Kernel

After the resignation two of my kernel heroes, Con Kolivas and Hans Reiser, I've stopped following Linux kernel changelog. The thing was, I didn't think anything special would came from the kernel and yes there wasn't. If you noticed after the lost, innovations that came from outside Linux kernel was diminished.

Before kernel 2.6.21, there was so many (alright, few maybe) kernel patches out there that grown with ideas such as Suspend from Disk, Xen, SD (was a rewrite from Staircase) scheduler, Reiser4, Memory Swappiness, and many tweaks. Hmm... I don't like to remember any of them now, because it's hurt to do it with the trolling and negative comments between devs.

Anyway, ReiserFS still my fave until now but it is getting old and old. With the avaibility of size, new technologies around and, especially, with the impression of ReiserFS is set to be deprecated I am getting anxious of its future. Of course, officially they don't but it seems like after the imprisonment of Hans, many likely thinks that ReiserFS is dead.

Oh, btw, this post is not supposed to be a rant. I will go to the point. Ahem.

Reiser4 filesystem had so many great features and the prominent thing was plugin, the ability to add new capability and to seperate core Reiser4 filesystem and extending it with new feature without breaking compability. It was a great idea, but, yeah, it broke many kernel conventions which angered the kernel devs, especially with Hans' attitude. The inclusion request was turned into flame wars.

Okay, the interesting part is now, with the prominent use of ZFS, Linux filesystem left behind. Luckily, a new filesystem which called BTRFS (B-Tree Filesystem) [WIKI] is now being actively developed. It was developed by Oracle but will be included in the Linux kernel 2.6.29. What made me interested is the part that it has Reiser4 concepts. But, hey, I didn't research that much right now.

I will wait kernel 2.6.29, buy a new harddrive, and starts to hack again. Until the time, I'll just collecting money for my new cellphone. [So depressing that the phones suggested only can be bought outside this country] :D

REFERENCE:
[WIKI] http://en.wikipedia.org/wiki/Btrfs
[1] http://btrfs.boxacle.net/
[2] http://btrfs.wiki.kernel.org/index.php/Main_Page
Labels:

Comments

  1. Anonymous12:59 PM

    monolithic is ancient stuff. try hurd or minix hehe

    ReplyDelete
  2. Anonymous6:32 PM

    >>monolithic is ancient stuff. try hurd or minix hehe

    Oh please... no more "Torvalds vs Tanenbaum" debate...

    XD

    ReplyDelete
  3. jpmrblood11:03 PM

    Now, if we can at least convert some modern hardware driver from Linux to Hurd, then I will take Hurd.

    ReplyDelete
  4. Anonymous7:54 AM

    gmn mo ngonvert, driver2 gituan banyak yg ga dikasi akses source. binary only

    tp lucu jg, sekarang urusan driver (even it's just binary) lebi gampang di Ubuntu daripada di windos

    ReplyDelete

Post a Comment

Popular posts from this blog

STAN vs. UI

Ugh, kasihan banget adek gue. Saking kepinteran dia jadi dapet Akuntansi UI dan STAN. Jadi bingung mau masuk yang mana. Beberapa orang (termasuk orang tua gue), menyarankan masuk STAN. Gue malah memperburuk suasana dengan membela memasuki Akuntansi UI, maklum bela almamater. Duh, gue jadi merasa bersalah bikin dia ragu-ragu. Kira-kira enakan masuk mana, yah? Gue juga gak tahu keuntungan masing-masing. Hasil debat sementara: ~ Untuk jangka panjang masuk UI, untuk jangka pendek STAN. ~~Tapi, dia itu kan cewek, ntar pas menikah kemungkinan besar karir terhambat. Eits, ntar, dulu, sekarang kan jamannya emansipasi, bisa aja cowoknya yang jadi BRT. ~ STAN sarang korupsi, kalo masuk STAN jadi pegawai negeri. Kalo mau kaya harus korupsi. Tapi kalo masuk UI, lulus masuk jadi akuntan publik. Sekarang ini, orang membayar akuntan publik untuk memanipulasi nilai pajak dan aset. *SIGH*. Jadi gak ada yang beres ~ dll. Yah, udah gue jadi bingung, apa lagi dia nanya saran gue. Buah, gue gak pengalaman ...
62 comments
Read more

Installing Goodix Fingerprint Reader Driver on Fedora

I currently have a Lenovo Thinkpad L14 laptop equipped with fingerprint. I was `belok` from KDE Neon to use Fedora 40 because of someone. Now I am tempted to enable my fingerprint: lsusb | grep -i fingerprint Bus 001 Device 004: ID 27c6:55b4 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Dump the firmware Assuming this is a fresh install, lets do some magic by getting some dependencies: sudo dnf install gcc git python-pip python-devel openssl Let's get the source code: git clone --recurse-submodules https://github.com/goodix-fp-linux-dev/goodix-fp-dump.git cd goodix-fp-dump Create an isolated Python environment: python -m venv .v source .v/bin/activate Do the magic: sudo su pip install -r requirements.txt python run_55b4.py exit There are some python scripts available. I run run_55b4.py because my device ID is 27c6: 55b4 . It will spell some nonsense, which is a good thing. That nonsense actually the firmware captured by our device. Also, I typed exit becaus...
2 comments
Read more

Vibe Coding Workflow

I am currently working for having A.I. workflow for generating projects. There are two things that need to be tackled for that: 1) hallucinations; and 2) old codes. I have met several patterns to tackle those two and just need to formulate the patterns into a general flow. Thankfully, a video of building fullstack app using A.I. from Raf Dev channel inspired me to make the formulation. He used multiple A.I. engines to his need: He used Google Gemini to onboard his ideas and summarized it. He forked a boilerplate of NextJS project into a new project. Then, he added the summary from Google Gemini into a file for context. He used QWEN Code, a QWEN3 code engine that is a fork from Gemini CLI, to build the project. When working with an existing project, A.I. will take the whole project as a context. It also means that it will stick with the version used by the libraries. It also will try to update its knowledge based on the common pattern in the project. Most of the time, it will use the c...
Post a Comment
Read more