=== fmasi_afk is now known as fmasi | ||
apw | yo | 09:16 |
---|---|---|
ppisati | why command line completion on tangerine triggers git? | 10:05 |
ppisati | i'm stuck, looking at top with a git process sucking up 100% of cpu | 10:05 |
ppisati | just because i tab-bed inside a git tree (from a saucy-amd64 chroot) | 10:06 |
ppisati | bah | 10:08 |
ppisati | and all those moments will be lost in time, like tears in rain... | 10:09 |
apw | ppisati, :) here have another moment, i have a couple of spares | 10:16 |
* ppisati goes out for a run... | 10:48 | |
=== fmasi is now known as fmasi_afk | ||
=== fmasi_afk is now known as fmasi | ||
manjo | smb, you have any bandwidth to take a look at kvm issue I am seeing ? | 15:19 |
smb | manjo, I can look as long as you don't expect results :-P | 15:20 |
manjo | :) alright .. can we switch channels to hwe ? | 15:20 |
ppisati | rtg: "TTY: hvc_dcc: probe for a JTAG connection before registering" - do you plan to pull this? or you need a formal git email/patch? | 15:25 |
rsalveti | rtg: can you check bug 1231196? it's basically a side effect of /proc/net/wireless being useless with mako | 15:25 |
rtg | ppisati, how about the patch that was actually accepted in linux-next ? in the meantime infinity has implemented a work around. | 15:26 |
rtg | rsalveti, gimme a bit | 15:27 |
ppisati | rtg: i didn't see that patch | 15:27 |
* ppisati goess looking | 15:27 | |
ppisati | *goes | 15:27 |
rtg | ppisati, should be on linux-next by now though I have not checked | 15:27 |
rtg | rsalveti, so, what _is_ the wifi device on the N4 ? | 16:32 |
rsalveti | rtg: you mean the driver? drivers/staging/prima | 16:34 |
rtg | rsalveti, ah, no wonder I couldn't find it | 16:34 |
rtg | rsalveti, assuming NetworkManager is using Wext to talk to this driver, I think we're screwed for stats (the stats entry point is NULL), e.g., .get_wireless_stats = NULL. | 16:42 |
rsalveti | oh, not even implemented | 16:43 |
rtg | no, but lemme look at the procfs entry | 16:43 |
rtg | rsalveti, https://bugs.launchpad.net/ubuntu/+source/linux-mako/+bug/1231196/comments/3 | 17:07 |
rsalveti | rtg: thanks | 17:13 |
manjo | ppisati, you are my hero! | 17:16 |
ppisati | manjo: IBAN IT123456000000666 <- money transfer go here | 17:17 |
manjo | ppetraki, bank of nigeria ? | 17:17 |
manjo | ppisati, ^ | 17:17 |
ppisati | poor ppetraki :) | 17:18 |
ppetraki | \o/ | 17:18 |
ppisati | manjo: why the hell would i tell you to transfer money to a scam account?!?!? | 17:18 |
rtg | kind of what I was wondering too | 17:19 |
manjo | ppisati, beer the universal currency | 17:19 |
ppisati | ppetraki: at the next UDS i want to take a picture with you, just for the hell of it... :) | 17:19 |
ppetraki | ppisati, certainly | 17:19 |
manjo | ppisati, I charge $beer for pics | 17:21 |
* ppisati -> reallife | 17:25 | |
wxl | it was suggested i come here (seems strange to me) to ask a question about sudo. sudo -H -u user whoami echoes the target user, yet sudo -H -u user echo $HOME echoes the invoking user's home. only Defaults in sudoers is the normal old env_reset and secure_path, which doesn't appear to conflict. any ideas what's wrong? | 17:28 |
mjg59 | $HOME is expanded by the shell before sudo is executed. whoami is executed by sudo. | 17:30 |
wxl | ok, well that makes sense. possible to delay expansion (in a non-interactive way)? | 17:31 |
wxl | oh well, i'll figure it out. thanks for the help | 17:48 |
=== fmasi is now known as fmasi_afk | ||
=== fmasi_afk is now known as fmasi | ||
=== fmasi is now known as fmasi_afk | ||
* rtg -> EOD | 20:33 | |
=== fmasi_afk is now known as fmasi | ||
=== fmasi is now known as fmasi_afk |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!