| fingertips | Why does lspci persist in reporting the wrong model for the wireless chip? This happened after loading a non working kernel module driver. Before loading it no model number was reported.Now, after unloading it the wrong model persists to be reported.Is this a sign that wrong firmware was sent to the chip? | 00:29 |
|---|---|---|
| fingertips | apw I have the source on the machine now | 05:07 |
| fingertips | apw deb-pkg error 2 | 06:31 |
| didrocks | apw: hey, following our discussion yesterday, I tried to unshare C function for having private mount points (actually umount in this case). But it was always umouting in the parent namespace as well. I then tried this with the unshare bin: http://paste.ubuntu.com/9152105/ | 17:05 |
| didrocks | I tried mounting as well with --make-rprivate, which isn't needed from the documentation in a child mount namespace | 17:06 |
| didrocks | I guess there is clearly something I didn't understand :) | 17:06 |
| === psivaa-holiday is now known as psivaa | ||
| didrocks | apw: ah, I guess I got it, / in my namespace is by default shared, so I need to mount --make-rslave / (to have parent changes reflected) beforehand | 17:13 |
| apw | didrocks, sounds good | 17:13 |
| === alexbligh1 is now known as alexbligh | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!