[12:15] <Chipzz> question about https://www.debian.org/doc/debian-policy/footnotes.html#f3 : how does ubuntu refer to these? as areas or as components?
[12:26] <highvoltage> Chipzz: I think the word you're looking for is 'pockets'
[12:26] <Chipzz> hmmm. heh. yay consistency :)
[12:27] <Chipzz> related question:
[12:27] <Chipzz> https://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections
[12:28] <Chipzz> are the subsections in ubuntu the same as in debian?
[12:28] <Chipzz> and does the naming of the section work the same as in debian or different?
[12:28] <Chipzz> (prepending the area/component/pocket to the section if it is not 'main'?)
[13:10] <cjwatson> highvoltage: no
[13:10] <cjwatson> Chipzz: we refer to them as "components"
[13:11] <cjwatson> pockets => release, proposed, updates, security, backports; different axis
[13:11] <cjwatson> Chipzz: we have the same (sub)sections and use that same naming
[13:12] <Chipzz> cjwatson: so the prefered nomenclature (considering both debian and ubuntu) would be component?
[13:13] <cjwatson> yes
[13:13] <cjwatson> "area" is extremely old terminology and predates all the current archive management software
[13:14] <Chipzz> I'm guessing the omission of the component in the Section when the component is main is why main in ubuntu is called main, and not something else?
[13:14] <cjwatson> kind of; why bother changing it
[13:14] <Chipzz> well restricted has a different name :)
[13:14] <cjwatson> *shrug*
[13:14] <Chipzz> but different axis too I guess :)
[13:14] <cjwatson> main is indeed special-cased enough that it would be troublesome to change
[13:15] <Chipzz> not arguing; more like trying to understand why things are the way they are :)
[13:15] <cjwatson> well sometimes the answer is just "because"
[13:15] <Chipzz> :)
[13:15] <cjwatson> stuff like this was set up very early
[13:16] <cjwatson> and to start with there was nothing but "main"
[13:16] <Chipzz> in debian I assume?
[13:16] <cjwatson> I meant in Ubuntu
[13:16] <Chipzz> ubuntu has had restricted etc for like forever, right?
[13:16] <cjwatson> depends on your definition of forever
[13:17] <cjwatson> the very early (well before going public) archive started out with just main IIRC
[13:17] <Chipzz> ah k :) but it's not very important anyway, merely curious :)
[13:18] <cjwatson> when it was just "we need something we've built to run our machines on"
[13:18] <Chipzz> (well the initial question I did ask for a reason, the latter not so much)
[13:19] <cjwatson> (I think "pocket" is terrible terminology, as it really doesn't tell you anything about their semantics; something like "stream" or "channel" maybe would have been better; but it's far too late to change now)
[13:24] <Chipzz> cjwatson: anyway, thanks for your time, I'm gonna get back to hacking now :)
[13:29] <cjwatson> np
[14:29] <highvoltage> cjwatson: ah ok, I misunderstood what was meant by 'area'
[17:15] <metaphysician> In 14.04, there is a bug in /usr/lib/pm-utils/power.d/wireless script at line 23. It should "enabled" at the end of path /sys/class/net/$1/device/enable. Wireless power saving does not get applied
[17:16] <metaphysician> where $1 is the interface
[17:20] <metaphysician> I always get an ENOENT error in /var/log/pm-powersave.log when that hook runs, inspite of active wlan0.