1 |
On Sat, 17 Dec 2016 15:35:38 +0100, Heiko Baums wrote: |
2 |
|
3 |
> Am 17.12.2016 um 14:17 schrieb Neil Bothwick: |
4 |
> |
5 |
> > I'm running the Debian 7 version of Raspbian on a number of Pis, all |
6 |
> > without systemd. Yes, I am happy using systemd, but I can't be arsed |
7 |
> > changing them when they continue to work perfectly well. |
8 |
> |
9 |
> Then explain me how this is done. Btw., Debian's and Raspbian's software |
10 |
> repositories are somewhat outdated. But that's a different Debian |
11 |
> related subject. |
12 |
|
13 |
If you can't work that out for yourself, what are you doing running |
14 |
Gentoo. I'm stating it can be done, I have neither the time nor the |
15 |
inclination to document it. |
16 |
|
17 |
> > Boot from a live CD, like Ubuntu, and read the journals. There's |
18 |
> > always a solution that doesn't involve flaming. |
19 |
> |
20 |
> Why would I boot from a Live CD if I have a PC with an installed OS |
21 |
> particularly just to be able to read some simple log files? |
22 |
> |
23 |
> So, no that's not a reasonable solution. |
24 |
|
25 |
I never claimed it was reasonable, you asked for a way to read them if |
26 |
you don't have systemd installed and I suggested a way. It takes seconds |
27 |
to boot a VM from an Ubuntu ISO. No, it's not elegant, but it does solve |
28 |
the problem. I do think a standalone reader for systemd journals would |
29 |
be a nice idea, but I'm not going to code it and I'm certainly not going |
30 |
to demand t as a right. |
31 |
|
32 |
> And that doesn't have anything to do with flaming. But that's typical |
33 |
> for those Poettering fanboys, too, since the beginning. They ask for |
34 |
> "technical" arguments. If "technical" arguments are given to them, then |
35 |
> those arguments suddenly are no technical arguments. Then this is |
36 |
> flaming. And Poettering and his fanboys just insult their critics, even |
37 |
> in the official "technical" systemd documentation. |
38 |
|
39 |
Technical arguments as opposed to to the ad hominem arguments you prefer? |
40 |
|
41 |
I am not a fanboy, I like some of the features of systemd while others |
42 |
really annoy me. I run a several systems without systemd simply because I |
43 |
see no point in changing a working system. |
44 |
|
45 |
But if you intend to dismiss anyone with a standpoint that does not |
46 |
precisely align with yours as a fanboy, there is no point in continuing |
47 |
this discussion. I am sorry that the pointers I gave do not meet your |
48 |
exacting standards and promise to refrain from doing so again. |
49 |
|
50 |
> > When I first tried systemd, I wasn't confident of my ability to work |
51 |
> > with the journal, so I installed syslog-ng and had traditional log |
52 |
> > files alongside the journal. In fact I ran it like that for quite |
53 |
> > some because the log monitor I was using didn't work with the |
54 |
> > journal. |
55 |
> |
56 |
> Yes, that's the solution. Install an old very well tested and useful |
57 |
> system logger which does the job perfectly on its own alongside of a |
58 |
> crappy system logger just to be able to read the binary log files again |
59 |
> with simple system tools which come along with EVERY distro like cat, |
60 |
> less, grep etc. And running two programs which have the same purpose in |
61 |
> the background don't need more system resources then just running one of |
62 |
> them, particularly on hardware like the Pi? |
63 |
> |
64 |
> Did you and the other Poettering fanboys think about this logic? I guess |
65 |
> not. |
66 |
|
67 |
Excellent, adding distortion to the ad hominem insults. I was simply |
68 |
pointing out that systemd does not preclude the use of an alternative |
69 |
logger. |
70 |
|
71 |
> > I never said it was easy. |
72 |
> |
73 |
> Should be easy. |
74 |
|
75 |
Why? Because you demand so? |
76 |
|
77 |
|
78 |
-- |
79 |
Neil Bothwick |
80 |
|
81 |
Fragile. Do not turn umop ap1sdn! |