Pretty sure they meant the whole “do one thing, do it well, and prefer composition” part.
But I’m more interested in what parts of systemd don’t follow the file metaphor, and what things you think shouldn’t follow that metaphor? How would you interact with those things?
That’s all fine and good, but that’s not quite related to the “everything is a file” metaphor. The data is still stored in files and accessed using conventional io and the command itself is routinely piped to other commands.
Everything being a file is extremely pervasive in unix, and I couldn’t think of what systemd was doing that went in opposition to the metaphor.
not everything needs to be a file.
in fact most things shouldn’t.
Pretty sure they meant the whole “do one thing, do it well, and prefer composition” part.
But I’m more interested in what parts of systemd don’t follow the file metaphor, and what things you think shouldn’t follow that metaphor? How would you interact with those things?
journalctl. I don’t give a damn as to where the logs are, and I just have telljournalctlto give me the logs for whatever I want.That’s all fine and good, but that’s not quite related to the “everything is a file” metaphor. The data is still stored in files and accessed using conventional io and the command itself is routinely piped to other commands.
Everything being a file is extremely pervasive in unix, and I couldn’t think of what systemd was doing that went in opposition to the metaphor.
But for a tool that read log configs and find that out for you, you’ve let Timers into your home.
Heh? Why?
That ain’t the Unix Philosophy I was refering to.