|
|
Log in / Subscribe / Register

The journald design is horrible to the point of useless

The journald design is horrible to the point of useless

Posted Nov 21, 2011 23:50 UTC (Mon) by alankila (guest, #47141)
In reply to: The journald design is horrible to the point of useless by josh
Parent article: That newfangled Journal thing

Observing this discussion, there seems to be a faint pattern.

There seems to be a tremendous dislike for using shared libraries. Perhaps it too is part of unix heritage, as at one point these things did not exist and code that was meant to be used from multiple programs was written in the kernel.

Perhaps the "unix way" is to make sure that whatever you do, "cat" can be used to read the data, and if it takes a kernel module to construct that file on the fly for cat to read, that is more acceptable than to have a binary file and some iterator functions in a library...?


to post comments

The journald design is horrible to the point of useless

Posted Nov 23, 2011 14:45 UTC (Wed) by nix (subscriber, #2304) [Link]

These days, you don't need a kernel module, you can use FUSE. If the FUSE filesystem works by using some shared library, that's great: it means you don't have to duplicate code. But filesystem interfaces are still as important, or more so, than library interfaces in the Unix world.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds