On 12/20/2016 11:49 AM, Carlos E. R. wrote:
That is absurd. You are telling me to make my own tools, and I say I want open source tools that directly read the journal and dynamically apply to it point and click functions like filter or follow event.
Unless the journal developers create those tools, the journal is irrelevant to me.
UNIX, and by implication Linux, has always been about making your own tools and assembling them using pipes and filters and regular expressions and the like. Languages like Perl and Python are really supersets of the shell which directly incorporate some things that were external programs[1], such as using regular expressions in a more general way than just GREP or SED. One paper from the 1980s shows how you can build a relational database using the file system, the shell, grep, sed, cut, paste. UNIX/Linux is pretty much predicated on the idea that you build tools out of these primitives. We take this for granted, but back when it was something revolutionary since the "mainframe" world was all about submitting requests to the IT department to have a program written .... In this sense, MS-DOS and Windows were great steps backwards. All these GUI tools we take for granted are actually scripted. Some, like YAST, are a lot of script, but then there is a lot to YAST. The upside is that it is very modular :-) I've mentioned the GUI interface to MySQL databases that presents a table view but also lets you make SQL queries - phpMyAdmin. That too was put together using a scripting language, PHP. Some scripting languages, Perl, Python, PHP come with compliers. Others, shell, Ruby, have compilers for a limited subset. The moment we use a pipeline, taking a log file, greping it, then using awk or cut to sort out the fields we want to see and pretty-print as a table, or print as a CSV to import into OOCalc, by definition we are programming. In the halcyon days of IBM Mainframes this is the kind thing, generating reports that were filtered various ways, that took a special request of a program to the IT department and MAYBE they would deal with it within the next three months with a FORTRAN or COBOL programme. We do it with a one-liner without thinking much about it, its just built around the grep and a regular expression ... so what? We choose not to call it 'programming' any more that people who do their accounts and budgets and projections and keep track of their investments using a spreadsheet think that entering formula is programming. Some of us are more ambitious than others. Some of us see the boundary between a CLI expression that has a nested loop and goes on for 10 lines as just another thing we type in directly, not even put in a file and mark executable. There are some amazing Perl "one-liners" like that which arose from a competition for the same :-) (Go Google) I'll have to pour through my web history, but I recall seeing a page which had a plug-in for manipulating the journal database directly, I think it was in PHP. I hope not; I'm not familiar with PHP. Hmm, something like this, but for a scripting language like Perl or Python http://www.openlmi.org/provider_journald Perhaps .. https://www.freedesktop.org/software/systemd/python-systemd/journal.html# [1] This happened with the shell as well, it incorporated the external programs 'echo', 'test' -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org