[03:00] <lotuspsychje> good morning
[07:41] <ducasse> good morning
[07:48] <lordievader> Good morning
[09:59] <lotuspsychje> hey TJ-
[11:17] <lotuspsychje> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908478
[11:17] <lotuspsychje> its raining similar bugs
[11:22] <jeremy31> Another one using mt76x02_lib
[11:30] <jeremy31> The fix was never added to the upstream 5.4 kernel
[12:08] <lotuspsychje> oO
[12:08] <lotuspsychje> jeremy31: and i alread filed a bug on that same dongle on bionic once, where HWE had to fix it
[12:09] <lotuspsychje> now we dealing just the same on 20.04
[12:09] <lotuspsychje> but how this make sudo freeze and influence eth and whole system still puzzles me
[12:35] <jeremy31> Not sure why it would affect eth
[12:38] <jeremy31> Likely because it causes issues with mac80211 and ieee80211
[12:48] <marcoagpinto> Heya
[20:44] <croraf> wget -qO - https://www.mongodb.org/static/pgp/server-4.4.asc | sudo apt-key add -
[20:45] <croraf> Can someone explain me this file. wget downloads the file on the url, -q0 is i guess the quite mode, what is the minus behind q0
[20:45] <sarnold> output to stdout
[20:46] <sarnold> -q is quiet
[20:46] <sarnold> -O selects output
[20:46] <croraf> SO O - means what?
[20:47] <croraf> aha, to output to stdout
[20:47] <croraf> and this stdout get's piped into apt-key add?
[20:48] <croraf> what does the last -, after add mean
[20:49] <oerheks>  Lastly, you tell apt-key to read the information from it's standard input (the "-" filename at the end).
[20:49] <croraf> I'm confused, -q says the output is turned off?, and -0 directs the output to stdout
[20:49] <croraf> WHy direct, if output is turned off
[20:53] <sarnold> -q is quiet, not no output
[20:56] <croraf> "- q Turn off Wget's output"
[20:56] <croraf> from the manpages sarnold
[20:56] <oerheks> quiet to humans, not to the socket.
[20:57] <sarnold> croraf: compare wget -qO - https://www.mongodb.org/static/pgp/server-4.4.asc  vswget -O - https://www.mongodb.org/static/pgp/server-4.4.asc
[21:01] <croraf> -q version removes some info from the stdout?
[21:02] <sarnold> yes, which makes using -O - much more useful :)
[21:02] <croraf> It leaves only the payload?
[21:03] <croraf> But this means that -q description in the manpages is completely wrong.
[21:03] <croraf> Both this metadata and the actual payload are sent to stdout, just with -q the request metadata is silent.
[21:03] <croraf> Right?
[21:09] <sarnold> more like 'status output' than 'request metadata'..  try adding -S to see the server-sent headers
[21:21] <croraf> sarnold, but this "status output" is also sent on the stdout, as the request body?
[21:21] <croraf> *response
[21:25] <sarnold> croraf: there's a billion command line options that you can mix and match to get whatever you need; these tools are used for network debugging, webclient debugging, webserver debugging, interactively retrieving files, scripted retrieving files, mirroring entire sites, etc etc etc
[21:25] <sarnold> croraf: not every option will be immediately obvious why it exists but someone somewhere found it useful to have each one for solving a problem :)
[21:26] <croraf> I understand that. I asked if this "status output" is also sent on the stdout, right?
[21:26] <croraf> same as the request body?
[21:26] <croraf> With the intention to confirm that -q description in man is wrong.
[21:26] <croraf> sarnold,
[21:27] <leftyfb> croraf: then file a bug with wget
[21:28] <croraf> I might, if you confirm it is a bug?
[21:31] <leftyfb> croraf: wget works fine for me as does it's man page. I'm not the one with an issue with it. Feel free to file a bug if you feel it is a bug
[21:39] <croraf> I asked if the description "-q   Turn off Wget's output." is wrong? You don't think this description is wrong?
[21:39] <croraf> leftyfb,
[21:40] <leftyfb> no, it turns off the output to the users terminal
[21:40] <oerheks> quiet to humans, not to the socket.
[21:42] <croraf> oerheks, what do you mean by not to the socket
[21:42] <croraf> it completely turns of the output for the "status information".
[21:43] <croraf> But -O can still put the response body into the output.
[21:46] <sarnold> or any other file you select
[21:46] <sarnold> or a socket somewhere else
[21:51] <croraf> Yes.