IRC log for #maemo-ssu on 20120919

00:13.01*** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl)
01:39.39*** join/#maemo-ssu LaoLang_cool (~LaoLang_c@222.190.112.229)
02:29.31*** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn)
03:42.04*** join/#maemo-ssu DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg)
04:24.25*** join/#maemo-ssu SpacedOut (david@SubSpace.fries.net)
05:10.12*** join/#maemo-ssu luf (luf@nat/ibm/x-gmcfjlcssyhcbcbm)
06:00.02freemangordonpeetah: you need libqtm12
06:16.07*** join/#maemo-ssu fw190 (a47e83c0@gateway/web/freenode/ip.164.126.131.192)
06:16.22fw190morning all
06:16.49keriomoin
06:16.50fw190freemangordon: when I try to install bootimage with cssu kernel HAM doesn't allow to do that
06:16.58fw190any hints how to solve this?
06:18.05keriofw190: install a fake package that provides kernel-feature-errata-430973-workaround
06:18.19kerioand make sure you never ever ever ever ever boot with a kernel that's not thumb-enabled
06:18.25fw190I could only use bootimage for uboot with kp 50
06:18.38kerio(i assume you're on cssu-thumb)
06:18.42fw190well I did it twice ;)
06:19.01kerioyou shouldn't, it's undefined behaviour
06:19.14fw190I'm on thumb but from time to time I like to test what Nemomobile looks like
06:19.14kerioprograms may behave strangely before they crash
06:19.26keriowhat does it look like?
06:19.33fw190well with thumb and stock kernel it doesn't boot even
06:19.42fw190well no wit looks much better
06:19.46fw190with the new ui
06:20.02keriofw190: anyway, it's a dependency problem
06:20.14kerioall the thumb packages depend on kernel-feature-errata-430973-workaround
06:20.15fw190ah ok
06:20.24keriowhich is provided by kernel-power-flasher or kernel-cssu-flasher
06:20.30fw190so where from shoul I get this errata
06:20.35fw190and how to install it
06:20.39kerioit's not a "thing"
06:20.41fw190so I can have palis uboot
06:21.13keriomake a fake package
06:21.36fw190uhhhh now you are demanding huge things from a end user ;)
06:22.40DocScrutinizer05the problem is uBoot comes with kernel. AIUI this isn't a thumb kernel, so uBoot isn't compatible with thumb userland
06:22.58*** join/#maemo-ssu freemangordon (~freemango@130-204-50-168.2074221835.ddns.cablebg.net)
06:23.31kerioDocScrutinizer05: the problem is that there's no way to tell apt "i'm only ever going to boot this OS with a thumb-enable kernel, so act as if the dependency is met"
06:23.38kerioyou know, without making an actual package
06:24.13DocScrutinizer05how would you guarantee you never boot with uBoot standard kernel?
06:24.15fw190I remeber that a few kp ago I compiled a power kernel with uboot on the device itself and had Kp wit uboot all in one
06:24.24fw190there was a tutorial somewhere on tmo for this
06:24.34fw190?
06:24.35fw190would it be possible with the lates thing
06:24.43kerioDocScrutinizer05: by... never booting with it?
06:24.44kerioidk
06:24.52keriofw190: you're using uboot, you're not an end user anymore
06:24.53DocScrutinizer05fw190: probably
06:25.16kerio~pali
06:25.16infoboti guess pali is http://atrey.karlin.mff.cuni.cz/~pali/
06:25.22fw190kerio: pali wrote what to do when I like an moron booted stock one ;)
06:25.40keriothere were some prebuilt .debs outside of the repos
06:25.51fw190he wrote what to do to always have booting the kp not the stock one
06:25.51freemangordonfw190: I missed what is your problem with installing -bootimg
06:25.59keriofreemangordon: the usual, unmet deps
06:26.08fw190freemangorson: it doesnt instal froom HAM
06:26.10freemangordonkerio: should not be
06:26.14keriofw190: can you open a terminal and type sudo apt-get install kernel-cssu?
06:26.16keriofreemangordon: he's using uboot
06:26.18freemangordonfw190: but why?
06:26.19kerioor something
06:26.23keriofw190: er, sorry
06:26.26fw190doesn't say
06:26.27keriosudo apt-get install kernel-cssu-bootimg
06:26.37freemangordonfw190: what is in the problems tab?
06:26.45freemangordonkerio: wait a minute
06:26.57fw190it's written in Polsih: something like it can not be installed
06:27.03fw190Polsih
06:27.06keriofreemangordon: he wants to use uboot with cssu-thumb
06:27.07fw190damn
06:27.09fw190Polish
06:27.21freemangordonkerio: yes, i understand that
06:27.39freemangordonfw190: and what is the reason it cannot be installed
06:27.48tadzikhello
06:28.09freemangordontadzik: hi
06:28.20keriofw190: can you pastebin the output of "apt-get install kernel-cssu-bootimg"? don't confirm anything if it asks for a confirmation
06:28.54fw190hmmm My N900 is now a modem with qt hotspot so I don't know if I can apt-get someting
06:29.04fw190will try and report
06:29.07fw190aaaa
06:29.08fw190one more thing
06:29.11kerioyou don't need internet for it
06:29.17kerioapt already knows how the dependencies wor
06:29.18keriok
06:29.26fw190I don't have palis uboot now installed
06:29.38fw190should I have it to test or it is not recomended
06:30.16freemangordonfw190: you need pali's uboot for all of the KP flavours, most probably that is why you cannot install -bootimg
06:30.43kerioyeah, the -bootimg depends on multiboot-kernel-power
06:30.55freemangordonconficts?
06:30.59fw190freemangordon: when I last tried it I had palis uboot
06:31.11fw190funny thing
06:31.13kerioand that pulls in multiboot
06:31.16keriowhich is awful
06:31.17fw190without ubbot it installed
06:31.24fw190without problems
06:31.41keriofw190: ask Pali where's the uboot+kp51 build he ha
06:31.42keriod
06:31.42kerioi know he has one
06:31.42freemangordonfw190: well, you have some dependency problem, run the command kerio posted and we'll see it
06:32.02fw190freemangordon: I just did and it installed without uboot on board
06:32.07fw190without problems
06:33.39keriohmm... free space on the rootfs?
06:33.52kerioalso, do you have multiboot installed?
06:33.54fw19070mb
06:33.56fw190no
06:34.00fw190I do not use multiboot
06:34.06keriohm
06:34.07keriooh well
06:34.07fw190jus have backupmenu
06:35.12fw190ok
06:35.19fw190now I have the uboot image
06:35.24fw190and uboot on board
06:35.44fw190but how to check it on reboot I will have the option for kernel power?
06:35.58Skryfw190: can you install/have you installed uboot from http://talk.maemo.org/showthread.php?t=81613 ?
06:36.02fw190so I don't end up like an idiot with brick for the third time ;)
06:36.22fw190I have the latest uboot from op from Pali
06:37.20freemangordonfw190: you'd better read u-boot thread or ask Pali, it was too long aglo I was playing with u-boot
06:38.08Skryfw190: I can send you the combined uboot+cssu kernel image if I find it on my hdd so you can flash it, if you want
06:38.51Skryor you can do it by yourself from whatever kernel you want
06:39.10Skryhttp://talk.maemo.org/showpost.php?p=1150859&postcount=6
06:39.14fw190wait
06:39.20fw190it installed ok.
06:39.28fw190I will post the output
06:39.33fw190there are some errors
06:45.33*** join/#maemo-ssu fw190 (6df33f5e@gateway/web/freenode/ip.109.243.63.94)
06:45.39fw190I'back
06:45.50fw190here is the output whle instaling boot image
06:46.43fw190http://pastebin.com/7BMCJ3F2
06:48.32Skryit's just complaining about missing kernel for bootmenu entry
06:52.42*** join/#maemo-ssu fw190_ (6df33f5e@gateway/web/freenode/ip.109.243.63.94)
06:52.53fw190_skry: thanks
06:53.00fw190_I removed the entry for kp50
06:53.17fw190_and just did a reboot
06:53.23fw190_and everything works ok
06:53.28Skrycongrats :)
06:53.31fw190_;)
06:54.35fw190_but the funny thing is that even after reflash and on CSSU T I was unable to install uboot bootimage on latest kp from devel or for cssu kernel using HAM
06:54.44fw190_from command line it went well
06:54.50fw190_without problem
06:54.58fw190_except informatinal complaines
06:57.24Skryproblems like that are quite common
06:59.33SkryI never liked debian package management, add HAM to that and things happen or not.
07:01.26*** join/#maemo-ssu andre__ (~andre@ip-89-176-24-140.net.upcbroadband.cz)
07:01.26*** join/#maemo-ssu andre__ (~andre@Maemo/community/bugmaster/andre)
07:03.35fw190_skry: thanks for the info
07:03.52fw190_and thanks to all for helping me out ;)
07:04.14Skrynp
07:06.20Skrytime get some sleep
07:47.16kerioSkry: the debian package management isn't meant to do stuff like that
07:47.20keriofor a reason :)
07:47.56keriopackages for bootloaders mostly only install the utilities to install the bootloader
07:48.39*** join/#maemo-ssu BCMM (~ben@unaffiliated/bcmm)
07:54.22*** join/#maemo-ssu FireFly (~firefly@oftn/member/FireFly)
07:58.51peetahfreemangordon: ok thanks I'll install it later in the day and let you know how it feels compared to FF14
08:01.37kerio=D
08:03.37*** join/#maemo-ssu ivgalvez (~ivgalvez@89.140.113.138.static.user.ono.com)
08:21.24*** join/#maemo-ssu fredrinLap (~fn@cm-84.208.108.15.getinternet.no)
08:30.55*** join/#maemo-ssu arcean (~Arcean@aacu210.neoplus.adsl.tpnet.pl)
08:37.48peetahfreemangordon: libqtm12 package is already installed on my n900
08:46.12*** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172)
09:19.20*** join/#maemo-ssu marcdeop (~marc@176.red-80-28-121.adsl.static.ccgg.telefonica.net)
09:24.53*** join/#maemo-ssu ivgalvez_ (~ivgalvez@89.140.113.138.static.user.ono.com)
09:25.32*** join/#maemo-ssu ivgalvez (~ivgalvez@89.140.113.138.static.user.ono.com)
09:25.55*** join/#maemo-ssu arcean_ (~Arcean@aaen138.neoplus.adsl.tpnet.pl)
09:31.00*** join/#maemo-ssu ivgalvez (~ivgalvez@89.140.113.138.static.user.ono.com)
09:41.04*** join/#maemo-ssu fw190 (6df33f5e@gateway/web/freenode/ip.109.243.63.94)
09:41.37fw190freemangordon: with the latest thum and transitions set to 10 the N900 is fast as lightning
09:41.52fw190just like I would have a new phone A.D. 2012
09:43.31tadzikwhat are "transitions set to 10?"
09:43.54fw190tadzik: there is an app
09:44.00fw190to set the transitions
09:44.09fw190i changed every value to 10
09:44.28fw190so now it doesn't take that much to do things
09:44.31fw190and it feels faster
09:45.05tadzikI installed some "OMG Fastest transitions for N900" from tmo, and it is actually a lot faster
09:45.20tadzikit just removes all the eye-candy for the sake of responsiveness
09:45.32fw190there is an app in the repo so you can tweak it as you wish
09:46.01*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
09:55.02Lava_Crofttadzik: the 'Smooth' transitions?
09:55.27Lava_CroftThe 'smooth' transitions you can find on TMO are actually the best I have come across over the years
09:56.29Lava_Crofttadzik: http://talk.maemo.org/showthread.php?t=83000
09:57.58tadzikI use those from http://talk.maemo.org/showthread.php?t=78591
09:58.13Lava_CroftI used those before, but i really love the animations
09:58.22Lava_Croftthose Smooth ones really are smooth :)
09:58.34tadzikbut are they equally fast?
09:58.51tadzikI don't care much for the jumping icons :)
10:00.12marcdeopthanks for the link, I'm gonna try it
10:02.09Lava_Crofttadzik: no, they are slower
10:02.21Lava_CroftBut thats what i mean, i dont like the istant transitions:)
10:02.27Lava_CroftIf you want speed, stick to what you are using now
10:04.34marcdeopthe transitions are indeed smooth
10:04.38marcdeopgood :)
10:04.40Lava_Croftyeah, it amazed me
10:15.38Skryokay that video got me interested
10:15.54Skrythat looks.. smooth.
10:57.41*** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl)
12:00.53tadzik~seen freemangordon
12:00.57infobotfreemangordon <~freemango@130-204-50-168.2074221835.ddns.cablebg.net> was last seen on IRC in channel #maemo, 4h 23m 50s ago, saying: 'cityLights: what is written in th "problems" tab in application mamanger?'.
12:00.57tadzikinfobot: help
12:01.03tadzikah, ok
14:52.25*** join/#maemo-ssu Pali (~pali@unaffiliated/pali)
15:07.38*** join/#maemo-ssu freemangordon (~freemango@130-204-50-168.2074221835.ddns.cablebg.net)
15:12.58*** join/#maemo-ssu toxaris (~toxaris@s83-180-246-172.cust.tele2.se)
15:18.37freemangordontadzik: are you ready with opera-thumb.deb? :P
15:18.45tadzikfreemangordon: not yet :)
15:18.55tadzikmind if I PM you?
15:19.06freemangordonbut,but.. you had almost 18 hours
15:19.09freemangordon:D:D:D
15:19.13freemangordontadzik: no
15:24.28marcdeophey guys, I've been out of touch from maemo for a few months
15:24.41marcdeopdo you know if there's been any work in idle imap support?
15:41.53*** join/#maemo-ssu NIN101 (~NIN@p5DD2881D.dip0.t-ipconnect.de)
16:15.55*** join/#maemo-ssu lizardo (lizardo@nat/indt/x-xquclnhalwcikndz)
16:49.02*** join/#maemo-ssu Pali (~pali@unaffiliated/pali)
17:03.14freemangordonmerlin1991: http://talk.maemo.org/showpost.php?p=1268398&postcount=737
17:03.22freemangordonis it the same in -testing?
17:12.45*** join/#maemo-ssu fredrinLap (~fn@cm-84.208.108.15.getinternet.no)
17:30.34*** join/#maemo-ssu luf (~luf@ip-89-103-223-164.net.upcbroadband.cz)
17:37.27freemangordonluf: did you manage to fix bluex build?
17:46.01lufNot yet and I see the BT name bug since last phone reboot :(
17:46.26freemangordon:(
17:46.27*** join/#maemo-ssu kerio (kerio@unaffiliated/kerio)
17:57.49lufStrange it survived 3 or 4 reboots. After that I installed backupmenu and after reboot I get the weird BT name.
18:01.12freemangordonhmm
18:01.26freemangordoncould be something related to boot order?
18:01.56lufNo idea.
18:02.55luffreemangordon: Didn't you write that you're able to compile bluez?
18:03.21freemangordononly with gcc 4.2.1 if I don;t do reconfigure
18:03.45freemangordonhmm, and anly the one in the repos (iirc)
18:03.48freemangordonnot yours
18:20.02*** join/#maemo-ssu _ade_ (~arno@52481E0B.cm-4-1a.dynamic.ziggo.nl)
18:21.04lufI can reproduce the strange name behavior :D And I can survive with right name ...
18:21.22freemangordonluf: you're my hero
18:21.35freemangordonnow you only need to fix the packaging :P :D:D:D
18:21.47freemangordonluf: what happens?
18:22.13lufNo I'm not. And I think I'm unable to fix autoconf mess :(
18:22.36_ade_freemangordon: how about a wiki page for gcc 4.7 / thumb2 in scratchbox?
18:22.40*** join/#maemo-ssu Woody14619 (~Woody@66-162-186-66.static.twtelecom.net)
18:22.40*** join/#maemo-ssu Woody14619 (~Woody@Maemo/Community/council/Woody14619)
18:22.41_ade_my last attempt resulted in some strange compiler warning for a simple test program
18:22.53_ade_and the resulting (thumb2) was bigger then the 4.2 compiled version..
18:23.43freemangordon_ade_: it is a very good idea, unfortunately I was short of spare time
18:24.03_ade_who isn't ;-)
18:24.13freemangordon_ade_: btw I don't know how to start a wiki page :D
18:24.35_ade_I just made one for the replacement clock.
18:24.44luffreemangordon: you're bad guy :D
18:24.46freemangordonluf: I was joking about autoconf, I will look at it when I have some spare time
18:25.14luffreemangordon: Yes you don
18:25.24lufdon't have spare time :D
18:26.30lufSo when I enable BT and reboot the BT name persist. When I never enable BT during uptime and reboot the BT name was lost (empty) and it leads to strange name when enable BT.
18:26.48lufI have to try what about enable BT, disable BT, reboot
18:26.52lufUgh.
18:28.58freemangordon_ade_: could you make an empty page, I will fill it's contents
18:29.35_ade_freemangordon: sure
18:29.47freemangordonthanks.
18:30.05_ade_what would be the best title?
18:30.17freemangordonhmm,
18:30.18luffreemangordon: just empty page? I hope _ade_ can help more ...
18:30.36freemangordonluf: don't think so
18:30.41lufok.
18:30.56_ade_I will to the spellingcheck :-)
18:31.08freemangordon_ade_: "CSSU-thumb toolchain setup"?
18:31.22freemangordonluf: ^^^ ?
18:31.23_ade_sound good to me
18:32.00freemangordoncan wiki page title be edited?
18:32.03luf_ade_: every help is good
18:32.18luffreemangordon: what are you asking me for?
18:32.25freemangordonthe name
18:32.32_ade_freemangordon: never tried, but I suppose it can be changed
18:32.33freemangordonany better idea?
18:32.43freemangordonluf: ^^^
18:32.45luffreemangordon: You can remove the page and copy to another in worst case ;)
18:33.05lufI'm sorry I'm one of the worst in naming ...
18:33.38_ade_I will post the wiki link over here later
18:34.00freemangordon_ade_: "CSSU-thumb toolchain setup(gcc4.7.2-linaro)"
18:34.16freemangordon_ade_: ok
18:34.28freemangordonI will try to do it tomorrow
18:34.33luffreemangordon: have you read what I wrote about BT name? It's funny.
18:34.38freemangordonluf: yes
18:35.07_ade_freemangordon: ok
18:36.38freemangordonluf: it seems you're missing some initialization
18:36.54DocScrutinizer05huh? make ampty wiki page??? WUT?
18:37.06freemangordonDocScrutinizer05: not funny
18:37.07kerioMAKE AMPTY WIKI PAGE
18:37.19kerioluf: does the bug appear if you keep bt on?
18:37.44freemangordonDocScrutinizer05: I have NFC where to even start
18:38.00DocScrutinizer05http://wiki.maemo.org/N900_Hardware_Power_management/lkdsökjdshkjdskjfeHglihg
18:38.13_ade_freemangordon:  http://wiki.maemo.org/CSSU-thumb_toolchain_setup_%28gcc4.7.2-linaro%29
18:38.21freemangordon_ade_: thanks
18:38.32DocScrutinizer05http://wiki.maemo.org/N900_Hardware_Power_management/lkdsökjdshkjdskjfeHglihg
18:38.41DocScrutinizer05DAMN
18:38.47DocScrutinizer05http://wiki.maemo.org/LkdsökjdshkjdskjfeHglihg
18:38.57keriomy xchat doesn't want to open that D:
18:39.15Lava_Croftlinks like that only work in proper irc clients
18:39.20kerioLava_Croft: fu
18:39.45DocScrutinizer05freemangordon: see the "There is currently no text in this page, you can search for this page title in other pages or edit this page." ?
18:39.56DocScrutinizer05see it's actually links under it?
18:41.04luffreemangordon: I didn't write the code :)
18:48.58lufkerio: I don't understand you question (I'm sorry my wife come back so we have to discuss a lot of things).
18:49.08keriothe BT name bug
18:49.18lufboot + enable BT + reboot = ok BT name
18:49.22keriodoes it appear if you always keep bluetooth on?
18:49.25kerioalright
18:49.30lufboot + reboot = empty BT name
18:49.51lufI'm trying boot + enable BT + disable BT + reboot
18:50.38lufkerio: I have disabled BT by default after boot.
18:51.18keriohuh, why? :c
18:51.19lufkerio: the bug is for bluze-4.99 (while maemo bluez is 4.60 ;) )
18:51.51lufkerio: because of battery and I use BT rarely when I'm driving ...
18:52.11kerioluf: no carkit? D:
18:52.19keriobut aren't you the dude of the carkit?
18:52.37lufYes I'm ;)
18:53.44lufShit. So if BT is disabled when firing reboot the BT name after reboot is empty. WTF where is the name stored? It doesn't get it from /etc/bluetooth/main.conf or /var/lib/bluetooth/<BT id>/config :(
18:55.07kerioi bet it's something silly
18:55.08keriolike cal
18:55.24lufwhat is cal?
18:56.35kerioit's a land of happiness and magic
18:56.40kerioalso /dev/mtd1
18:57.33lufGreat so it's easy. Just to find the way into the mirror :D
19:01.16DocScrutinizer05BS, BT name isn't in CAL
19:01.51lufDocS: WTF is CAL?
19:02.05kerioi said "i bet"
19:02.13DocScrutinizer05if there's no separate BT names et (NFC if there's even such thing), then it uses /etc/hostname afaik
19:02.20DocScrutinizer05~CAL
19:02.20infobotcal is, like, a calendar. try $(cal 1752)
19:02.30keriono, it doesn't use /etc/hostname
19:02.35DocScrutinizer05~whatiscal
19:02.47DocScrutinizer05MEH!
19:03.03DocScrutinizer05luf: /dev/mtd1 aka "config"
19:04.53lufDocS: thanks.
19:05.10lufShit the magic is more dark than I think ...
19:06.41lufIt's enough to change /var/lib/bluetooth/<BT id>/config: mode on and the name appears ... So it depends if the BT device is on during kernel module or something like that.
19:06.54luf(appears after reboot)
19:07.09luf* during loading kernel module ...
19:07.22lufIt's big bull ....
19:09.06DocScrutinizer05luf: here you are:
19:09.08DocScrutinizer05t900:~# grep -r IroN999 /etc /var /home/user/ 2>/dev/null
19:09.10DocScrutinizer05/var/lib/bluetooth/A8:7E:33:CD:E5:2B/config:name IroN999
19:11.28lufI know but it's ignored if you have mode off (in same file) when you fire reboot.
19:11.45lufI'm working with bluez-4.99 on N900 ;)
19:12.00DocScrutinizer05if BT is off, so how would BT name matter... And to whom even?
19:12.31lufYou want to specify BT name each time you reboot? Don't be silly.
19:13.30lufPlease DocS read the history (last hour or so) at first.
19:14.57lufI appreciate you want help me but this doesn't help me.
19:17.05DocScrutinizer05well, sorry I won't study last hour of backscroll
19:18.43*** join/#maemo-ssu ekze-nyan (~nyan@bakaekze.ru)
19:19.06DocScrutinizer05I just tell you there's three locations for device name: cat var/lib/bluetooth/*/config; cat /etc/hostname; gconftool -g /apps/modest/device_name
19:19.16DocScrutinizer05that's it, do with it whatever you like
19:20.13lufok, thanks
19:21.27DocScrutinizer05of course also in /home/user/.modest/local_folders/*/*/*/*/*/*
19:22.28*** join/#maemo-ssu ekze_nyan (~nyan@bakaekze.ru)
19:22.38lufWhat is modest for?
19:22.51DocScrutinizer05hmm?
19:22.57*** join/#maemo-ssu BCMM (~ben@unaffiliated/bcmm)
19:22.58DocScrutinizer05mail?
19:24.12lufWhy it contains BT name in gconf?
19:24.24DocScrutinizer05I said device name
19:25.04DocScrutinizer05waitwaitwait
19:25.37DocScrutinizer05no, don't wait ;-D
19:25.40lufFor sure it's BT name. My device (hostname) is another.
19:29.06DocScrutinizer05[2012-09-19 20:53:45] <luf> Shit. So if BT is disabled when firing reboot the BT name after reboot is empty. WTF where is the name stored? It doesn't get it from /etc/bluetooth/main.conf or /var/lib/bluetooth/<BT id>/config :(<<  honestly, doesn't make sense to me. The BT name is stored in var/lib/bluetooth/*/config, only there and nowhere else
19:30.47DocScrutinizer05And I'm really sorry I dared to ask how there can be a BT name when BT is off, since - again sorry - I'm too simple to see where from I would get BT name value when BT is off
19:31.36DocScrutinizer05of course BT name is empty when BT is off (unless you talk about /var/lib/bluetooth/<BT id>/config)
19:32.15lufBT device not bluetoothd daemon. And when I activate BT device the BT is empty => get it from driver not from config.
19:32.29DocScrutinizer05(btw I actually *did* read backscroll, before I first answered)
19:32.47lufbluze-4.60 takes value from config all the time. It doesn't matter if BT device is on or off.
19:33.47DocScrutinizer05so where's the problem?
19:34.32DocScrutinizer05you got a bug in some of your BT stack when it doesn't manage to set up BT name according to /var/lib/bluetooth/<BT id>/config
19:34.52DocScrutinizer05I never seen that though
19:35.22lufbluez-4.99 when BT mode off during boot - there is empty value in BT name (in settings). When I enable BT device it put some mess into BT name (chip name) from driver. That's the problem.
19:35.45lufDocScrutinizer05: there are even reports on TMO or bugzilla with bluez-4.60.
19:36.09DocScrutinizer05:shrug:, IO've never experienced that
19:36.38freemangordonluf: so forward-port the patch that reads the name from gconf and you should be ok
19:37.25luffreemangordon: the name is in config too but it doesn't take it into account :(
19:38.35freemangordonluf: iirc you can get the name of the device by a dbus call
19:38.43freemangordonlemme try to find that code for you
19:39.01lufNever mind. I'll try debug the bluetoothd (I know how to "fix it") do I can compare these two situation.
19:39.29luffreemangordon: Yes, it's empty when no dbus call due to no device activation during boot.
19:39.58lufI remember I tried go deeper into the problem 3 month ago.
19:40.26DocScrutinizer05freemangordon: name from gconf???
19:40.33DocScrutinizer05which one?
19:40.36lufToday I can reproduce wrong and right result so I'm one step further :)
19:40.49kerioi thought there was just *one* device name, and you set it in the bluetooth settings panel
19:42.07DocScrutinizer05kerio: until you set /etc/hostname, or device name in modest
19:42.19kerio/etc/hostname is unrelated i think
19:42.28kerioi didn't know modest also knew how to set the device name
19:42.35lufkerio: you're right.
19:42.39DocScrutinizer05*sigh*
19:42.54DocScrutinizer05kerio: modest has *his own* device name
19:42.59keriooic
19:43.04DocScrutinizer05just like system has /etc/hostname
19:43.49DocScrutinizer05kerio: probably you could even argue xchat has another instance of device name, though it's called server name there iirc
19:43.56keriohahahahaha
19:44.58DocScrutinizer05kerio: and yes, the name in var/lib/bluetooth/*/config will be set via the settings/BT dialog only
19:45.37DocScrutinizer05(modulo niche cases like reflashing or reste-to-factory)
19:46.21lufGood the problem is in initialization for sure :D
19:46.22lufBT disabled + boot + BT name empty + enable BT + BT name like RCM2048XY Initial configuration + reboot + BT name back to the correct value :)
19:46.47DocScrutinizer05luf: how T F so you "enable BT"?
19:47.41lufClick on time or icons -> enable BT (or you can use System -> Settings -> Bluetooth -> (un)check Enabled)
19:48.11DocScrutinizer05since I guess the hildon settings dialog will read out the name from var/lib/bluetooth/*/config, fill it in as initial text to the textedit box, and on "save" initializes BT stack with whatever is in that textbox (besides writing it also back to var/lib/bluetooth/*/config)
19:48.44lufYou're wrong.
19:48.57lufThe dialog settings get it from DBUS call :D
19:49.04DocScrutinizer05mhm
19:49.05freemangordon:nod:
19:49.23freemangordonstring Name [readwrite]
19:49.32DocScrutinizer05so where from does DBUS get it then? IOW whom is settings->BT *asking* for the name?
19:49.55freemangordonDocScrutinizer05: what I see in the code:
19:50.00DocScrutinizer05yaknow, each dbus msg has a destination
19:50.01lufbluez.
19:50.16freemangordonir tries "read_pretty_host_name"
19:50.27lufbluetoothd to be precise
19:50.36freemangordonand after that (af the above fails) "read_local_name"
19:50.51DocScrutinizer05LOL
19:50.58DocScrutinizer05makes sense
19:51.00luffreemangordon: it doesn't work neither to set pretty_host_name in bluez.
19:51.02freemangordonread_local_name gets it from /var/lib.../config
19:51.27freemangordonluf: gimme some time to see who calls that
19:51.40luffreemangordon: No it doesn't in case of "initialization problem"
19:51.42freemangordonadaptername_probe() is that
19:51.53DocScrutinizer05still my question: what's dbus destination when settings->BT is the sender?
19:52.09freemangordonluf: maybe it waits for a kernel event
19:52.21freemangordon(which never comes as we use an old kernel)
19:52.38DocScrutinizer05good shot
19:52.50freemangordonluf: handle_inotify_cb :P
19:53.06freemangordonguess who :D
19:53.08DocScrutinizer05freemangordon: realy now?
19:53.13luffreemangordon: I think about it ... but why it works then when the BT is enabled during boot.
19:53.20*** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172)
19:53.55luffreemangordon: ? kp50 is too old? Does KP51 implement it?
19:54.04lufI think about some BT changes in kernel ...
19:54.14freemangordonI can bet it registers inotify_cb, and enumerates already enabled devices
19:54.31freemangordonat least I will do it that way :D
19:54.35luffreemangordon: this sound reasonable ...
19:54.51freemangordonluf: lets find how the old bluez does it
19:55.00lufDoes KP51 implement inotify_cb ?
19:55.11freemangordonluf: does not matter
19:55.14lufold one is dead.
19:55.27lufIt works even with the name very different way.
19:55.40luffreemangordon: why it doesn't matter?
19:55.49freemangordonluf: come on, gimme 5 more minutes :P
19:56.01luf4:48 ...
19:56.11luf4:34 ...
19:56.40lufWe're very good here. We can even take 60 minutes in 40 minutes :D
19:57.10freemangordonlike my new watch? he is "rocket" :P
19:57.16freemangordons/he/it/
19:57.37luf:D So 5 minutes left ...
20:00.12DocScrutinizer05no, he said "5 *more*..."
20:00.24lufDocs: He had -10 mintues ;)
20:00.54DocScrutinizer05actually he had 5 now
20:02.11DocScrutinizer05luf, my abstract virual debugging shows it's obviously the kernel driver or some daemon that gets loaded only when BT gets enabled
20:02.27freemangordonDocScrutinizer05: no
20:02.55freemangordonbluetooth enables (loads, whatever) the adapter in question and waiths a callback event
20:03.07DocScrutinizer05:nod:
20:03.18freemangordonthat event never comes as the kernel does not support inotify
20:03.30DocScrutinizer05still :nod:
20:03.34freemangordon(in bt driver at least)
20:03.57DocScrutinizer05while during boot it does udev-events-playback-late or whatever the script is named
20:04.00freemangordonadapter named ir read from configuration file on "adapter up" event
20:04.15freemangordonDocScrutinizer05: could be, NFC
20:04.35DocScrutinizer05meh
20:04.56freemangordonDocScrutinizer05: but I believe that on bootup already enabled adapters are enumerated and initialized
20:05.42freemangordonAIUI old bluez sets device properties on "adapter enable" dbus call
20:05.53freemangordonluf: ^^^
20:06.07DocScrutinizer05here you are: (4 lines spam!)
20:06.10DocScrutinizer05Sep 19 22:16:24 t900 kernel: [29803.526702] hci_h4p hci_h4p: firmware: requesting bcmfw.bin
20:06.12DocScrutinizer05Sep 19 22:16:24 t900 bluetoothd[909]: HCI dev 0 up
20:06.13DocScrutinizer05Sep 19 22:16:24 t900 bluetoothd[909]: Starting security manager 0
20:06.15DocScrutinizer05Sep 19 22:16:24 t900 bluetoothd[909]: Adapter /org/bluez/909/hci0 has been enabled
20:06.33DocScrutinizer05(this device is 10 min ahead of time)
20:06.51lufShit it isn't so easy ...
20:06.56DocScrutinizer05but those are the 4 lines in syslog, when you enable BT
20:06.58freemangordon4.99 waits for "/org/bluez/909/hci0 has been enabled" inotify
20:07.12freemangordonluf: what is not easy?
20:08.14lufWhen I debugged it (shit I removed the syslog one week ago). It tried to initialize correct name and after that it gets the wrong one. I was unable to find the source.
20:08.35lufBut it sounds very good what you're saying free.
20:09.01DocScrutinizer05and that's dbus (systembus):
20:09.03DocScrutinizer05signal sender=org.freedesktop.DBus -> dest=(null destination) serial=84 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
20:09.05DocScrutinizer05<PROTECTED>
20:09.06DocScrutinizer05<PROTECTED>
20:09.08DocScrutinizer05<PROTECTED>
20:09.08lufI'm sorry I'm upgrading VIO so I'm not so responsible as I want.
20:09.09DocScrutinizer05method call sender=:1.541 -> dest=org.freedesktop.DBus serial=426 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=ReleaseName
20:09.11DocScrutinizer05<PROTECTED>
20:09.17DocScrutinizer05oops, more lines than it looked like
20:10.06freemangordonWTF?
20:10.08freemangordoninotify_add_watch(inot_fd, MACHINE_INFO_DIR, mask)
20:10.18freemangordon#define MACHINE_INFO_DIR "/etc/"
20:10.18freemangordon#define MACHINE_INFO_FILE "machine-info"
20:10.38lufIt's the pretty name ...
20:10.53lufIf I remember it right. But it doesn't work neither.
20:10.56DocScrutinizer05no fsckng such file here, I *bet*
20:11.01freemangordonluf: try echo luf > /etc/machine-info
20:11.10freemangordonwhile BT enabled without name
20:11.18luffreemangordon: ^^^
20:11.24freemangordonluf: I know
20:11.51freemangordonplease try it, to see if the name will appear
20:12.00freemangordon"luf" name I mean
20:12.13DocScrutinizer05nah froblshnarz
20:12.59lufYou don't trust me ... :)D
20:13.43freemangordonluf: elaborate please
20:13.57DocScrutinizer05dafaq, inotify_add_watch(inot_fd, MACHINE_INFO_DIR, mask)  --  now I realize what they're doing
20:14.06lufIn progress ... N900 doesn't boot in one sec ...
20:14.20lufBut you don't trust me. It hurts :D :D
20:14.27freemangordonDocScrutinizer05: and what did you realize?
20:14.43DocScrutinizer05>><freemangordon> while BT enabled without name<<
20:15.04freemangordonluf: you're a big boy, you can stand a little pain :P
20:15.19DocScrutinizer05those donkeyballsuckers use /etc/ for a dynamic file
20:15.28freemangordonyeah
20:15.39freemangordoncalled machine-info :P
20:15.46freemangordonor not?
20:15.54DocScrutinizer05looks like
20:16.08freemangordonluf: could you just touch /etc/fmg?
20:16.28freemangordoninstead of machine-info
20:16.52freemangordon(not sure it will work though, didn;t read the whole code)
20:17.34DocScrutinizer05lazybone
20:17.51freemangordonbut, but.. then we miss some daemon.
20:18.03freemangordonur it is udev to do that?
20:18.06freemangordon*or
20:18.13DocScrutinizer05NFC
20:18.20lufYou're right that you don't trust me.
20:18.20DocScrutinizer05you ate the code
20:18.30freemangordonluf: I know
20:18.40DocScrutinizer05without sharing more than 3 small lines
20:18.40freemangordon:P
20:19.09freemangordonDocScrutinizer05: someone should touch a file in /etc on BT adapter up
20:19.31freemangordonit is not a part of bluez aiui
20:19.37freemangordonluf: what happened?
20:20.21luffreemangordon: but do you dive into 4.99 code to take a look how they initialize it (not machine-info - it's ugly workaround).
20:20.43luffreemangordon: what you expected.
20:20.44freemangordoninitialize what?
20:20.49freemangordonadapter name?
20:20.59freemangordonyes
20:21.01lufBT when the BT device is off during boot.
20:21.12DocScrutinizer05someone should s§inotify_add_watch(inot_fd, MACHINE_INFO_DIR, mask) §dbus-wait-signal("path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged", 'string "com.nokia.connui_bluetooh_status_menu_item-cp_plugin-conbtui"') §
20:21.23freemangordoni looked into the code, that is why I posted inotify_cb here
20:21.37freemangordonDocScrutinizer05: no
20:21.44freemangordongimme 5 more minutes :D:D:D
20:22.00luffreemangordon: 4.99 or 4.60 ?
20:22.07freemangordon4.99
20:22.26freemangordonit is totally different in 4.53 (that is wht I have here)
20:23.23lufWhere do you have 4.53? There is no bluez for win XP ... :D
20:23.45DocScrutinizer05waaait
20:23.46freemangordonfrom repository.maemo.org
20:24.04DocScrutinizer05Sep 19 22:16:24 t900 kernel: [29803.526702] hci_h4p hci_h4p: firmware: requesting bcmfw.bin
20:24.13lufI'm going to switch to another machine ... There is 4.60 in maemo ...
20:24.16DocScrutinizer05set inotify on bcmfw.bin
20:24.28lufI'll be offline for few minutes ...
20:24.58DocScrutinizer05I'm afk for a few beers
20:25.01freemangordonDocScrutinizer05: waaaait, lets see how is that supposed to work with newer kernels :)
20:25.09*** join/#maemo-ssu M4rtinK (~M4rtinK@ip-89-102-207-166.net.upcbroadband.cz)
20:25.49DocScrutinizer05should I guess? udev writing there
20:26.23DocScrutinizer05I'm guessing all the time
20:26.40freemangordonstill NFC
20:26.43*** join/#maemo-ssu luf (~luf@ip-89-103-223-164.net.upcbroadband.cz)
20:26.43freemangordonhttp://www.spinics.net/lists/linux-bluetooth/msg13459.html
20:26.44DocScrutinizer05since evil freemangordon eats all the code all alone
20:27.00freemangordonthis is the commit that does the shit
20:27.45DocScrutinizer05ohfsck, that's too nasty
20:27.45freemangordondoc will like that one:
20:27.48freemangordon"This file is part of systemd's hostnamed functionality:"
20:27.56DocScrutinizer05WAAAAAHHHH!!!
20:28.09DocScrutinizer05see? I said "udev"
20:28.23freemangordonnoo, it is systemd :P
20:28.23DocScrutinizer05udev sufered poettering treatment
20:29.00freemangordonbut it still makes no sense to me
20:29.03DocScrutinizer05"embrace and suffocate"
20:29.32freemangordonwhat will happen (on desktop) when I pull my usb BT adapter?
20:29.40freemangordonwhat in /etc will chage?
20:29.46freemangordonDocScrutinizer05: ^^^?
20:29.58DocScrutinizer05oooh makes perfect sense to me, it's poettering. Only poettering can think of "let's write to /etc/ to signal an event to $random_process"
20:30.17freemangordon~poettering
20:30.17infobot'sth is poettering' means it acts invasive, possessive, destructive, and generally in an egocentric exacerbating negative way. ``this cancer is extremely poettering''
20:30.50freemangordonDocScrutinizer05: anyway, who the hell writes in /etc?
20:30.57DocScrutinizer05nfc
20:31.03freemangordonkernel? i doubt
20:31.08DocScrutinizer05inotify-monitor
20:31.18freemangordonWT is that?
20:31.52luffreemangordon: inotifi is only for the file ...
20:31.57freemangordonluf: hmm, did you check if bluez provides some udev/systemd rules?
20:32.12freemangordonluf: inotify if for the whole /etc
20:32.29DocScrutinizer05inotify-watch and inotify-monitor are commands
20:33.01lufShit. As I expected it's not reboot persistent. If the file exists it ignores the file :D That's what I tested few month ago.
20:33.23DocScrutinizer05luf: you understand inotify?
20:33.44DocScrutinizer05[2012-09-19 22:13:56] <DocScrutinizer05> dafaq, inotify_add_watch(inot_fd, MACHINE_INFO_DIR, mask)  --  now I realize what they're doing
20:33.47freemangordonluf: yes, you need someone to touch a file in /etc after bluetoothd is started
20:33.53lufI know.
20:34.02lufI just want a proof.
20:34.13lufBTW maybe I see my problem ...
20:34.27freemangordontouch /etc/fmg_proof
20:34.33lufNo.
20:34.40freemangordonyes
20:34.42DocScrutinizer05lol
20:34.44lufThe problem in code ...
20:34.52freemangordonwe don't want machine-info in /etc
20:35.20freemangordonluf: what is the problem?
20:35.32DocScrutinizer05figue /me going mad ;-P
20:35.42lufI'm trying to search if I'm not wrong ...
20:36.02lufDo you see:
20:36.02luf/* And disable the name change now */
20:36.02lufadapter_set_allow_name_changes(adapter, FALSE);
20:36.37DocScrutinizer05halebop:~ # ls -l /etc/machine-id
20:36.38DocScrutinizer05-r--r--r-- 1 root root 33 Nov 10  2011 /etc/machine-id
20:36.39freemangordonluf: that happens in case you have /etc/machine-info
20:36.51DocScrutinizer05well, seems old enough?
20:36.56freemangordonluf: and that disables name updates using dbus call
20:37.26freemangordonluf: remove your /etc/machine-info and touch /etc/fmg_proof
20:37.29lufYes. And it enable name updates otherwise. And that is the problem.
20:38.09DocScrutinizer05http://linux.die.net/man/1/inotifywatch
20:38.36freemangordonluf: there is this udev rule:
20:38.38freemangordonACTION=="add", SUBSYSTEM=="bluetooth", RUN+="/usr/local/sbin/bluetoothd --udev"
20:39.54DocScrutinizer05http://linux.die.net/man/1/inotifywait
20:40.03DocScrutinizer05not *monitor
20:41.15lufWhat does the action mean?
20:41.30lufBTW it was enough to remove the machine-info file ...
20:43.39freemangordonluf: yes
20:43.58freemangordonany change in /etc will lead to name re-read
20:44.14freemangordoneven touch /etc should do it
20:44.46freemangordondafaq
20:45.11freemangordonreading /var/lib/... is a backup
20:45.33freemangordonthis is intended to work with exising /etc/machine-info
20:46.00DocScrutinizer05freemangordon: hey, with inotifywatch we could easily find out about all commands and libs used in early boot, before /opt available :-D
20:47.40luffreemangordon: but backup where another name change is allowed.
20:48.10freemangordonluf: yes yes. and we should not have /etc/machine-info anyway
20:48.33freemangordonthe question remains - who TF touches /etc
20:49.29freemangordonanyway, I will have to wakeup really early tomorrow
20:49.30freemangordonso I am kleaving
20:49.30freemangordon*leaving
20:51.15freemangordonnight, wish you luck with finding how exactly udev touches /etc :D
20:51.17DocScrutinizer05on desktop?
20:51.17freemangordonyes
20:51.17DocScrutinizer05hmmm
20:51.18DocScrutinizer05ponders mkfifo
20:51.20freemangordonI mean - when a BT adapter is enableds
20:51.48lufIt uses another way for sure.
20:51.49DocScrutinizer05or even a stale nfs-link ;-P
20:51.55lufgood nigth.
20:51.57freemangordonluf: though I thing we can safely revert http://www.spinics.net/lists/linux-bluetooth/msg13459.html
20:52.14freemangordon(or the patch in bluez tree)
20:52.17freemangordonnight
20:54.40luffreemangordon: not true. There are more changes ... It's not so simple/
20:55.37freemangordonwell, the simple task was for me (to find what/how happens) :P
20:55.48freemangordonnight, really
21:02.56freemangordonluf: an idea - call stupid callback function manually from dbus "adapter_enable" handler
21:19.16luffreemangordon: Were not you going sleep? :D
21:20.00luffreemangordon: I'm looking into it. I don't understand why during boot it can't set adaptername when it can set it in the callback.
21:20.17lufAnd for sure it's called using register_driver ...
21:21.25lufAnd the create/delete/write operation has to be on /etc/machine-info there is a if in the callback.
21:31.00DocScrutinizer51maybe during boot some idiot writes to /etc?
21:31.29lufI don't think so.
21:37.48*** join/#maemo-ssu M4rtinK (~M4rtinK@ip-89-102-207-166.net.upcbroadband.cz)
21:39.47DocScrutinizer51the fsck knows what's mask set to on this buggy line
21:40.14DocScrutinizer51maybe is's already sufficient to read the /etc
21:48.18lufDocScrutinizer51: come on ...
21:48.35luf+if (pevent->len && +    pevent->name != NULL && +    strcmp(pevent->name, MACHINE_INFO_FILE) == 0) { +changed = TRUE;
21:48.58lufI know you don't trust me. But I wrote that the machine-info is checked in the callback.
22:01.46DocScrutinizer05I toldya freemangordon ate all that code without sharing a single char
22:03.18DocScrutinizer05the one who decides it would be a good idea to have a semaphore gile in /etc(!!!) might also fsckup mask and forget to check return values
22:03.33DocScrutinizer05~lart lennart
22:03.33infobottries to shut lennart up
22:03.44DocScrutinizer05~uselss
22:03.49DocScrutinizer05~useless
22:03.49infobotACTION starts crying and hides from docscrutinizer05 in the darkest corner of the room. :(
22:04.04DocScrutinizer05~kill lennart
22:04.04infobotACTION shoots a charged pseudoneutrino gun at lennart
22:05.52DocScrutinizer05torturing poor NAND for such utter bullshit concept (completely ignoring it's not at all safe from arbitrary "race" conditions when other processes mess with the /etc)
22:06.56DocScrutinizer05ooh, he actually did share
22:07.14DocScrutinizer05switches to that rotting browser window
22:08.30DocScrutinizer05God! is that just me or is c source text indigestible in those patches, with that leading "+"
22:13.42DocScrutinizer05if (changed != FALSE) {
22:13.50DocScrutinizer05OOOOUUUUUUUUUUUUUUUUCCHH!!!
22:14.40DocScrutinizer05if (((changed != FALSE) == TRUE ) != FALSE) {
22:15.29DocScrutinizer05if ((((changed != FALSE) == TRUE ) != FALSE)  && (changed == changed) == TRUE)){
22:16.34*** join/#maemo-ssu _rd (~rd@p57B49547.dip0.t-ipconnect.de)
22:16.43DocScrutinizer05just to be sure X-P
22:18.39*** join/#maemo-ssu myuu__ (~miku@pool-108-27-201-196.nycmny.fios.verizon.net)
22:18.58lufYou're sure sure sure of sure :D
22:20.43DocScrutinizer05luf: dafaq am I getting senile or is the while friggin function static gboolean handle_inotify_cb() not returning any meaningful return-value or triggering any meaningful event besides DBG(MACHINE_INFO_DIR MACHINE_INFO_FILE ??
22:20.58DocScrutinizer05s/while/whole/
22:21.43DocScrutinizer05ooh, it indeed triggers manager_foreach_adapter((adapter_cb) adaptername_probe, NULL);
22:22.07lufYeah in time when there is no adapter ;)
22:23.10lufAhh sorry, it triggers what you said.
22:23.41lufThere is aslo register_driver which trigger the same foreach (in time when no adapter is loaded) :D
22:42.14merlin1991did I miss anything today?
22:42.50lufI think nothing urgent. Just DocS as usual want to be sure sure sure of sure :D
22:54.23DocScrutinizer05merlin1991: how's about >>   if ((((changed != FALSE) == TRUE ) != FALSE)  && (changed == changed) == TRUE)){
22:56.14RST38hwhile(0==0) *(void *)0=0;
22:56.24DocScrutinizer05or maybe >> if ((changed != FALSE) && (TRUE == changed))
22:58.13merlin1991ETOOMANYPARENTHESIS
22:58.51DocScrutinizer05ENFCBOOLALGEBRA
22:59.23DocScrutinizer05+if (changed != FALSE) {
22:59.24DocScrutinizer05+DBG(MACHINE_INFO_DIR MACHINE_INFO_FILE
22:59.26DocScrutinizer05+" changed, changing names for adapters");
22:59.28DocScrutinizer05OUUUUUUCH!
23:00.05merlin1991where does all that come from?
23:00.08DocScrutinizer05if (!changed == FALSE)
23:00.14DocScrutinizer05http://www.spinics.net/lists/linux-bluetooth/msg13459.html
23:00.39DocScrutinizer05From: Bastien Nocera <hadess@xxxxxxxxxx>
23:01.18DocScrutinizer05oops
23:01.25DocScrutinizer05if (~changed == FALSE)
23:03.14DocScrutinizer05if !(changed == FALSE)
23:04.52merlin1991DocScrutinizer05: you should combinbe them with ^ aswell
23:05.11DocScrutinizer05lol
23:05.37DocScrutinizer05actually comparing something against TRUE is a terrible idea, in C
23:05.51DocScrutinizer05comparing against FALSE is just silly
23:06.56merlin1991is currently lost, 0 is true and everything else false, or how did it go?
23:07.13DocScrutinizer05I think so
23:07.18DocScrutinizer05nah
23:07.22DocScrutinizer05other way round
23:07.48merlin1991yep
23:08.02merlin1991makes sense
23:08.13merlin1991otherwise if(fp) { ... code would be stupid :D
23:08.15DocScrutinizer05there's one FALSE, and a zillion differnts truthes
23:08.42merlin1991sounds like politics
23:08.47DocScrutinizer05which is quite interesting, philosophically
23:09.02merlin1991you just don't tell them they make more money than they do, everything else is just a shade of the truth ;)
23:27.25*** join/#maemo-ssu arcean (~Arcean@aaen138.neoplus.adsl.tpnet.pl)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.