Lennart Poettering
Lennart Poettering
so i'd be a bit conservative with this. I frankly don#t understand what the code precisely does. I#d not try to work around a bug that we don#t know if...
So, this makes sense to me, but i never laid my hands on a kernel like this. @keszybz can you give a blessing to this too as a better python...
lgtm, but @keszybz is our resident python guru, will leave the final review to him
so looks good in general, i just would like some care taken that we work sensibly in an environment with /var/ being still absent.
i do wonder how useful this is going to be IRL, i.e. given that we are an early boot service, possibly already running in the initrd, where we can't really...
so, to be fully correct we would have to tell networkd when /var/ is around, similar to how we do it for journald. And then later, tell it when /var/...
hmm, i am a bit concerned about making this a per-interface thing and a per-dhcp thing. I don't see the point of making it so fine grained. After all we...
yeah, we ignore $TERM set in the env block in PID 1 since the kernel sets that incorrectly (it always sets it to TERM=linux, even if not on a VT)....
the ellipsification of the boot status lines has nothing to do with $TERM. why would it? if you want to set TERM for the console, literally add `TERM=foobar` to the...
if you want to make the terminal width wider, you can use the `systemd.tty.columns.console=` kernel command line setting to set any width you like.