<qyliss>
IdleBot_5e50c57d: have you done anything to crosvm to stop it wanting syslog?
<IdleBot_5e50c57d>
Nope. I just gave it a socat socket to /dev/null inside the container
<qyliss>
How? I don't actually know how syslog works.
<IdleBot_5e50c57d>
Zero syslog involved. /dev/log is just a normal socket, crosvm wants to connect to it and send its valuable thoughts. Syslog does not replies to the log submissions anyway
<qyliss>
oh, right. interesting.
<qyliss>
The code I read had some horrible hacks for finding syslog file descriptors or something
<IdleBot_5e50c57d>
I have also read that code when checking what is the cheapest way to tell it to shut up
<qyliss>
ahh
<IdleBot_5e50c57d>
Gave up and just let it have something called /dev/log
<qyliss>
> failed to initialize syslog: guess of fd for syslog connection was invalid
<qyliss>
I thought I'd try to build crosvm in a Debian container so I could give non-Nix build instructions for the blog post I'm writing.
<qyliss>
But maybe doing it in a container is a fool's errand
<IdleBot_5e50c57d>
Well, in container you can do the same thing as I do, no?
<qyliss>
I tried that and got the above error
<qyliss>
I think I might give up on a step by step anyway, because people are still going to have to build their own initrds and stuff anyway, and I'm not going to be writing a tutorial for that.
<IdleBot_5e50c57d>
Just as a check: you had a world-writeable listening unix domain socket called /dev/log ?
<qyliss>
shit no
<qyliss>
symlinking to /dev/null is... not that :P
<IdleBot_5e50c57d>
I do not suddenly use socat when symlinking works