| 20 May 2021 |
|  Reventlov joined the room. | 20:38:38 |
| 4 Apr 2025 |
 @adam:robins.wtf | Is that configurable to send to multiple output devices? I have a few systems where getting serial and graphical display outputs simultaneously would be helpful | 13:40:26 |
| 20 May 2021 |
|  colemickens 🏳️🌈 changed their display name from colemickens to colemickens 🏳️🌈. | 21:05:06 |
| 4 Apr 2025 |
|  @qbit:tapenet.org left the room. | 16:12:33 |
| 20 May 2021 |
|  Dandellion joined the room. | 21:05:29 |
| 4 Apr 2025 |
 ElvishJerricco | This is what confuses me. Like on an rpi, I do get systemd's Starting Foo... style messages on both HDMI and serial outputs | 17:19:38 |
| 20 May 2021 |
|  pie_ joined the room. | 21:12:38 |
| 4 Apr 2025 |
 K900 | HDMI is just a VT | 17:27:43 |
| 20 May 2021 |
|  Las joined the room. | 21:26:15 |
| 4 Apr 2025 |
| K900 | I'm pretty sure those are special cased? | 17:27:50 |
| 20 May 2021 |
|  makefu set a profile picture. | 23:12:34 |
| 4 Apr 2025 |
| ElvishJerricco | by who? the kernel or systemd? | 17:42:43 |
| 21 May 2021 |
|  o1lo0lol1o joined the room. | 00:45:53 |
| 4 Apr 2025 |
 gdamjan | systemd is smart enough to use all consoles, but the kernel only uses a single console | 17:42:47 |
| 21 May 2021 |
|  a3don joined the room. | 02:28:56 |
| 4 Apr 2025 |
| ElvishJerricco | gdamjan: that's definitely not true | 17:43:02 |
| 21 May 2021 |
| a3don left the room. | 02:34:04 |
| 4 Apr 2025 |
| ElvishJerricco | the kernel will use one console of each type, e.g. one serial and one VT | 17:43:17 |
| 21 May 2021 |
|  NinjaTrappeur joined the room. | 06:59:55 |
| 4 Apr 2025 |
| ElvishJerricco | but /dev/console only corresponds to one of those | 17:43:41 |
| 21 May 2021 |
|  niksnut joined the room. | 08:11:36 |
| 4 Apr 2025 |
| ElvishJerricco | well, more accurately, among the console= kernel params, it will use one of each type | 17:45:24 |
| 21 May 2021 |
|  evils joined the room. | 08:47:40 |
| 4 Apr 2025 |
| gdamjan | I stand corrected https://docs.kernel.org/admin-guide/serial-console.html | 17:46:50 |
| 21 May 2021 |
|  Emil Karlson joined the room. | 08:55:14 |
| 4 Apr 2025 |
| ElvishJerricco | yea that's what I quoted from last night :) | 17:47:02 |
| 21 May 2021 |
|  higebu joined the room. | 10:20:13 |
| 4 Apr 2025 |
| ElvishJerricco | I think systemd only logs to its systemd.log_target= parameter, which is (effectively) by default the console target, which I think means just /dev/console but might be all console= params. | 17:50:20 |
| 21 May 2021 |
|  colmeka joined the room. | 11:35:18 |
| 4 Apr 2025 |
| ElvishJerricco | But that's systemd's own log_* functions; I think it doesn't actually redirect its stdout / stderr at all. And I think the /etc/systemd/system-shutdown/ programs inherit systemd's stdout, which is why our shutdown script's message is no longer going to the serial console | 17:54:20 |
