19:30 <larsc> And a Tux that pops up and ask you "It looks like you want to bind a device to a driver, do you need any help with that?"

19:33 <wpwrak> yeah, that tux would be really handy, too

19:33 <wpwrak> i don't know how much time i've already wasted trying to figure out how it got that darn bureaucracy wrong this time, when it's just some stupid typo in the name

19:34 <wpwrak> kewl. the actual code seems to work on the first try. at least something :)

19:35 <larsc> I always check /sys/bus/foobar/devices and /sys/bus/foobar/drivers. If both the device and the driver are present but not bound this is usually a good indication that the strings don't match

19:38 <wpwrak> hmm, didn't even see my driver show up in devices/ until i fixed that typo

19:43 <wpwrak> kewl. driver works like a charm. almost suspiciously well :)

20:33 <wpwrak> hmm, interesting highway intersection: https://maps.google.com/?ll=-34.784342,-58.522947&spn=0.014839,0.032809&t=h&z=16

20:34 <wpwrak> looks quite regular, but has interesting features. e.g. if coming from the south, making a right turns seems to be a bit of an adventure. you probably need a gps to get back on track when you miss the right path on the trifurcation

20:35 <wpwrak> the 2nd chance when coming from the southeast and wanting to go west is also cute

21:37 <kristianpaul> cute indeed :)

21:39 <kristianpaul> i wonder if you could get in a loop on it

21:44 <larsc> you can stay on the middle loop forever

21:49 <wpwrak> yeah, but that's very common

21:52 <wpwrak> i should add that signposting around here is usually poorly done and more confusing than helpful. so i'm pretty sure a lot of people who don't know the exit will end up in the wrong branch on that multiple-choice right turn.