IRC log for #maemo on 20170414

00:21.56*** join/#maemo infobot (ibot@rikers.org)
00:21.56*** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~lf ~tabletsdev ~combined ~emmc ~flasher sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet
00:22.26*** join/#maemo LauRoman (~LauRoman@5-14-54-134.residential.rdsnet.ro)
01:11.08*** join/#maemo inz (inz@irc.inz.fi)
01:34.49*** join/#maemo sfa (~sfa@108-89-35-42.lightspeed.sntcca.sbcglobal.net)
01:39.42*** join/#maemo cyphase (~cyphase@unaffiliated/cyphase)
01:46.15*** join/#maemo Natch (~Natch@h-155-122.a444.priv.bahnhof.se)
02:08.56*** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
02:09.33*** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
02:49.03*** join/#maemo vahe (~vahe@130.193.124.163)
03:14.44*** join/#maemo crazyguy` (~user@ip54540084.speed.planet.nl)
03:40.02*** join/#maemo pagurus` (~user@p4FDC3213.dip0.t-ipconnect.de)
03:41.03*** join/#maemo pagurus` (~user@p4FDC3213.dip0.t-ipconnect.de)
03:44.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
03:47.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
03:50.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
03:53.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
03:56.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
03:59.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
04:02.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
04:05.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
04:08.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
04:11.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
04:14.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
04:17.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
04:20.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
04:23.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
04:26.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
04:29.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
04:32.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
04:35.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
04:38.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
04:41.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
04:42.46*** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg)
04:44.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
04:47.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
04:50.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
04:53.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
04:56.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
04:59.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
05:02.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
05:05.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
05:08.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
05:11.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
05:14.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
05:17.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
05:20.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
05:23.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
05:26.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
05:29.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
05:32.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
05:35.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
05:38.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
05:41.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
05:44.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
05:47.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
05:50.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
05:53.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
05:56.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
05:59.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
06:01.45*** join/#maemo dafox (~dafox@188.207.110.140)
06:02.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
06:05.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
06:07.58*** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
06:08.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
06:08.50*** join/#maemo geaaru (~geaaru@host139-6-dynamic.54-82-r.retail.telecomitalia.it)
06:09.30*** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
06:11.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
06:14.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
06:17.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
06:20.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
06:23.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
06:26.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
06:29.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
06:32.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
06:35.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
06:38.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
06:41.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
06:44.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
06:47.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
06:50.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
06:53.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
06:56.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
06:59.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
07:00.19*** join/#maemo florian (~fuchs@x4d0943de.dyn.telefonica.de)
07:02.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
07:05.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
07:07.57*** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
07:08.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
07:10.56*** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
07:11.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
07:14.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
07:17.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
07:19.36*** join/#maemo Pali (~pali@Maemo/community/contributor/Pali)
07:20.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
07:23.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
07:26.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
07:29.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
07:32.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
07:35.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
07:38.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
07:41.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
07:44.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
07:47.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
07:50.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
07:53.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
07:56.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
07:58.20*** join/#maemo shentey (~shentey@x4e350172.dyn.telefonica.de)
07:59.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
08:00.20bencohpagurus: could you please fix your connection? :)
08:00.30bencohfreemangordon: didn't you reverse devlock/codelock "recently"?
08:01.57freemangordonummm, I think so, lemme check
08:02.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
08:02.31freemangordonbencoh: https://github.com/community-ssu/libdevlock
08:03.02bencohah, thanks :)
08:03.34freemangordonbencoh: though, iirc there are more modules, like https://github.com/community-ssu/codelockui
08:03.45freemangordonI am not sure that one is fully REed
08:05.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
08:05.48bencohI'd like to add an option to disable the "turn off device" dialog when clicking outside the codelock dialog
08:06.01bencohthat's probably in codelockui
08:06.04freemangordonmhm
08:06.17freemangordonI guess you first have to RE it completely
08:06.31freemangordonif it is not already done
08:07.26bencohlemme check what's already installed on my device (I haven't added your latest REed bits - afaict0
08:08.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
08:08.26freemangordonbencoh: yeah, look at https://github.com/community-ssu/codelockui/blob/master/codelockui.c#L210
08:08.40freemangordonbencoh: I can provide my IDA db
08:08.59bencohdoes IDA work properly in wine? :]
08:09.05bencohactually I'd have to download it as well
08:09.15freemangordonyes, it is ok in wine
08:09.40bencohwhat is this reponse_signal supposed to do?
08:09.48freemangordonNFC :)
08:09.55bencoh:-)
08:09.57freemangordoncheck the source
08:10.18freemangordonbencoh: it is jonwil that did most of the REing work, I added just one finction
08:10.22freemangordon*function
08:11.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
08:11.03bencohah
08:11.42freemangordonbencoh: looking at hexrays code, it seems this function make a "secu_ib_lockcodenotchanged" note and actually changes the code in cal
08:11.43bencohhmm, funny, there's already a response_cb which is implemented
08:11.54bencohchanges the code?
08:11.59bencohah, the lock code
08:12.13freemangordonmhm
08:12.24freemangordonit is pretty large function, some 100 loc
08:12.34freemangordonhmm, less
08:12.59freemangordonalso, this is in hexrays, if REed properly it should be about 30-40 loc
08:14.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
08:17.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
08:20.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
08:20.32freemangordonbencoh: wanna IDA db?
08:20.56bencohsure. IDA doesn't work with wine for some obscure and stupid reason here, though
08:21.37freemangordonbencoh: what "doesn't work" mean?
08:22.09freemangordonbencoh: what os and IDA version?
08:22.20freemangordons/os/distro
08:23.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
08:23.31bencoh(old)macosx, ida free 5.0, and I had to comment out a line in idagui.cfg because for some reason it failed after trying to map an invalid key
08:23.41bencohlooks like it works, eventually
08:26.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
08:29.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
08:32.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
08:35.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
08:38.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
08:40.37*** join/#maemo SmilyOrg (~SmilzOrg@ip5f5bd58b.dynamic.kabel-deutschland.de)
08:41.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
08:44.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
08:47.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
08:50.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
08:53.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
08:53.14*** join/#maemo cyphase (~cyphase@unaffiliated/cyphase)
08:56.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
08:59.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
09:02.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
09:05.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
09:08.02*** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
09:08.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
09:09.04*** join/#maemo pcfe (~pcfe@ip5b4091eb.dynamic.kabel-deutschland.de)
09:09.06*** join/#maemo pcfe (~pcfe@redhat/pcfe)
09:09.40*** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
09:11.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
09:14.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
09:17.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
09:20.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
09:21.47*** join/#maemo Smily (~SmilzOrg@ip5f5bd58b.dynamic.kabel-deutschland.de)
09:23.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
09:24.24*** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au)
09:26.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
09:29.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
09:32.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
09:35.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
09:35.32KotCzarnycan anyone ban him temporarily?
09:38.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
09:39.53L29Ahwho?
09:41.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
09:41.10KotCzarny^
09:41.34*** join/#maemo jon_y (~enforcer@2001:e68:4075:f96c:f64d:30ff:fe63:5a5a)
09:42.15L29Ahme?
09:43.26freemangordonbencoh: jonwil joined, you may ask him re naming :)
09:43.41jonwilnaming of what?
09:44.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
09:44.04KotCzarnynaming of the One that shouldnt be named, muahaha
09:47.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
09:47.12freemangordonjonwil: z prefix in your IDA decompiled functions :)
09:47.32jonwilwhich binary are we talking about?
09:47.38freemangordoncodelockui
09:48.51jonwilOk after checking the IDB I believe the $ functions are the ones that were cloned and the z ones are the ones that weren't fully cloned
09:49.02jonwili.e. baring bugs the $ functions should be done
09:49.05jonwiland the z ones are the ones that need cloning still
09:49.21jonwilthat's how I did it for that particular idb anyway
09:50.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
09:50.22freemangordonyeah, my understanding as well, but still, it is better for you to confirm it
09:50.33freemangordons/for you/you
09:51.01freemangordonanyway, /me is going afk for a couple of hours, bbl
09:51.08jonwilIf someone is going to finish cloning codelockui, that's great :)
09:51.26freemangordonwell, bencoh said he wants to implement new functionality
09:51.47freemangordonfor that to happen, he needs to finish RE first
09:51.56jonwilyeah
09:51.58freemangordonhowever, bye
09:52.01jonwilok
09:52.03jonwilcya
09:53.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
09:56.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
09:59.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:02.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:05.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:08.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:11.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:14.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:14.47*** join/#maemo sicelo900-2g (~sicelo@unaffiliated/sicelo)
10:17.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:19.38*** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
10:20.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:23.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:26.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:29.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:32.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:35.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:38.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:41.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:44.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:47.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:50.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:53.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:56.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:59.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
10:59.33*** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
11:02.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
11:05.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
11:07.01*** join/#maemo l_bratch (~l_bratch@2a06:5840:13a::9993)
11:07.41*** join/#maemo sicelo (~sicelo@unaffiliated/sicelo)
11:08.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
11:09.53*** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
11:11.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
11:14.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
11:17.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
11:20.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
11:23.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
11:25.03*** join/#maemo sicelo900-2g (~sicelo@169.239.28.253)
11:26.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
11:29.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
11:32.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
11:33.34*** join/#maemo sicelo900-2g (~sicelo@unaffiliated/sicelo)
11:35.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
11:38.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
11:41.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
11:44.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
11:47.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
11:50.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
11:53.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
11:56.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
11:59.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
12:02.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
12:05.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
12:06.38*** join/#maemo cyteen (~cyteen@146.66.58.6)
12:08.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
12:11.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
12:14.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
12:17.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
12:20.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
12:23.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
12:23.18*** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
12:26.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
12:29.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
12:32.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
12:35.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
12:38.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
12:41.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
12:44.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
12:47.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
12:50.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
12:50.32*** join/#maemo xy2_ (~xy2_@mlv95-h01-176-134-46-233.dsl.sta.abo.bbox.fr)
12:53.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
12:54.03*** join/#maemo xy2_ (~xy2_@mlv95-h01-176-134-46-233.dsl.sta.abo.bbox.fr)
12:56.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
12:59.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
13:01.48*** join/#maemo Kabouik_ (~kabouik@32.232.202.84.customer.cdi.no)
13:02.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
13:02.18*** join/#maemo Kabouik_ (~kabouik@32.232.202.84.customer.cdi.no)
13:05.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
13:06.08*** join/#maemo xy2_ (~xy2_@mlv95-h01-176-134-46-233.dsl.sta.abo.bbox.fr)
13:07.40*** join/#maemo cyteen_ (~cyteen@146.66.58.6)
13:08.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
13:11.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
13:14.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
13:17.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
13:20.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
13:23.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
13:24.43*** join/#maemo xy2_ (~xy2_@mlv95-h01-176-134-46-233.dsl.sta.abo.bbox.fr)
13:26.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
13:29.03*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
13:32.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
13:32.26*** join/#maemo BCMM (~BCMM@unaffiliated/bcmm)
13:35.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
13:38.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
13:41.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
13:44.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
13:46.05*** join/#maemo cyteen_ (~cyteen@146.66.58.6)
13:47.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
13:50.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
13:53.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
13:54.35*** join/#maemo freemangordon (~ivo@46.249.74.23)
13:56.02*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
13:58.31*** join/#maemo xy2_ (~xy2_@223.245.16.93.rev.sfr.net)
14:02.33*** join/#maemo pagurus (~user@p4FDC3213.dip0.t-ipconnect.de)
14:19.15*** join/#maemo xy2_ (~xy2_@223.245.16.93.rev.sfr.net)
14:26.36dreamerhmm, seems my device has issues to connect to gps. any good way to debug this?
14:26.49dreamerI tried both maps app and cloudgps
14:27.21dreameranother app that uses gps also didn't work yesterday
14:42.04freemangordondreamer: SUPL server is dead for a month or so
14:42.22freemangordonjust give it a couple of minutes and it will have lock
14:48.21dreamerfreemangordon: I disabled suppl/network lock in the gps settings. should that improve performance?
14:55.07freemangordonno
15:07.52sicelo:-) will make it worse
15:13.19sicelooh wait? supl dead?
15:15.15siceloseems to be working for me .. with the line '52.22.201.16 supl.nokia.com
15:15.22sicelo<PROTECTED>
15:16.44*** join/#maemo sicelo900-2g (~sicelo@8ta-146-101-86.telkomadsl.co.za)
15:22.02*** join/#maemo sicelo900-2g (~sicelo@unaffiliated/sicelo)
15:43.56*** join/#maemo xy2_ (~xy2_@mlv95-h01-176-134-46-233.dsl.sta.abo.bbox.fr)
15:44.29*** join/#maemo zgrepc (sid43445@ircpuzzles/2015/april-fools/sixth/zgrep)
15:54.55*** join/#maemo vahe (~vahe@130.193.124.163)
15:59.43peetahsicelo: what is this ip ?
16:01.16KotCzarnyprobably what it resolved to before
16:01.47KotCzarnystill, there is a high chance that service will go down entirely
16:02.21KotCzarnyOrganization:   Amazon Technologies Inc. (AT-88-Z)
16:02.23KotCzarnyhehe
16:03.09KotCzarnydistributed services
16:03.53peetahKotCzarny: that's why I'm asking :)
16:04.46peetahwho controls it ? and why would it be ok to use it as a replacement for supl.nokia.com ?
16:05.51sicelo900-2git is/was supl.nokia.com :)
16:06.50sicelo900-2gand yes it works. is it safe? well ... how safe is supl.google.com? or any other? :p
16:08.47sicelo900-2ghttp://talk.maemo.org/showthread.php?p=1525029#post1525029
16:09.13sicelo900-2gbut May 15 is precariously close ...
16:13.17peetahsicelo900-2g: thanks for the tmo thread
16:19.13DocScrutinizer05~gps
16:19.13infoboti heard gps is http://russnelson.com/ipaq/gps/ or qpegps.sf.net or gpsqpe.sf.net
16:19.40DocScrutinizer05~#maemo gps is http://talk.maemo.org/showthread.php?p=1525029#post1525029
16:19.40infobotDocScrutinizer05: okay
16:19.46DocScrutinizer05~gps
16:19.46infobotrumour has it, gps is http://talk.maemo.org/showthread.php?p=1525029#post1525029
16:32.37Enrico_MenottiHi all. I'm struggling with xkb, still on Debian. But I think this may be of more general interest, maybe also for Maemo and for Devuan. So I'd ask some things, if any of you may help me. Please let me know whether this be the right place.
16:53.11Enrico_MenottiI'm having difficulties with the type PC_FN_LEVEL2, which is defined in a specific file: <xkbroot>/types/nokia. Somewhat, this file is not read by xkb. So I looked into the rules files, and although I can find the nokiarx51 model in many of them, I don't understand where the type file is referred to.
17:01.48*** join/#maemo xy2_ (~xy2_@5.245.16.93.rev.sfr.net)
17:21.37freemangordonwhy the fuck an ebay seller in Berlin wouldn't want to ship a battery to Bulgaria is beyond what I can grok :(
17:22.56freemangordonDocScrutinizer05: could you help with that one? http://www.ebay.com/itm/PolarCell-Akku-Nokia-N97-mini-E5-00-E7-00-N8-00-BL-4D-Accu-Batterie-Battery-/370584735149#shpCntId
17:24.05DocScrutinizer05what exactly do you want me to do?
17:24.16*** join/#maemo Venemo (~venemo@fedora/Venemo)
17:24.28freemangordonbuy 4 of those and send them to me?
17:24.45freemangordonjust asking
17:25.09freemangordonthe batteries of my n950 devices died
17:25.15DocScrutinizer05np
17:25.32freemangordonand I see n950 as a viable test bed for maemo-devuan
17:25.59DocScrutinizer05it is
17:26.40DocScrutinizer054?
17:26.48freemangordonDocScrutinizer05: ok, I will have some more thinking on whether to bother you with that, or just to buy original Nokia batteries from the shop next to my place
17:26.59DocScrutinizer05ok
17:27.01freemangordonwell, one to put in the device and one spare x2
17:27.14DocScrutinizer05ping me when you made up your mind
17:27.18freemangordonok, thanks
17:27.47DocScrutinizer05also you could simply make him send them to me instead
17:28.08DocScrutinizer05I'll just apply a new addr sticker and forward the parcel
17:28.14freemangordonhmm, yeah
17:28.51DocScrutinizer05though, you know there are nasty new regulations about LiIon shipping?
17:30.57DocScrutinizer05there are still ways to ship those. But the nasty thing is that customs/parcel
17:31.11DocScrutinizer05service don't understand them
17:32.27*** join/#maemo Venemo (~venemo@fedora/Venemo)
17:32.49DocScrutinizer05they have sent back to me a N900 with battery separately packed, with the comment "device has battery inserted" - which is clearly *allowed* by the regulations (though not the way it actually was in my parcel)
17:33.31DocScrutinizer05maybe they meant "this is what your parcel does NOT comply with: battery inserted"
17:35.18*** join/#maemo Timur_ (~Timur@fedora/Venemo)
17:35.40freemangordonyep, I heard, but I doubt dhl/ups don't know about them and how to comply
17:39.52DocScrutinizer05they know, but packaging is the customer's job
17:42.32DocScrutinizer05idiocy #1: you may send a phone with battery built in, but you may not regularly send a device with battery in same package. Though you *could* do that when you make sure it complies with obscure requirements which the checks generally assume are met by parcels from Samsung, Nokia and others, but assume are NOT met by parcels from 'nobody' like me and you, even when we explicitly state on outside that they are met
17:43.28DocScrutinizer05it's a huge mess
17:48.45DocScrutinizer05idiocy #2: they have regulations about e.g. percentage of charge for the LiIon cell for shipping (all relevant for airmail delivery) which they can't check at customs
17:50.11DocScrutinizer05isiocy #2a: the customs/checks generally have no faintest clue about the technical details like WattHours of a cell, etc
17:51.17DocScrutinizer05it all boils down to: you can send LiIon when your company name is sufficiently known to the carrier's checker dudes
17:52.00DocScrutinizer05or when you insert he battery into an electronic device so in x-ray it doesn't show up as separate LiIon cell
17:53.52*** join/#maemo shentey (~shentey@x4e352dee.dyn.telefonica.de)
17:55.14DocScrutinizer05considers making PCB with 100um copper layer holding only a text "ITA-4711 compliant security package" and wrap that PCB with LiIon cell into putty
17:55.53DocScrutinizer05so those drones can clearly see it on their x-ray
17:58.48DocScrutinizer05http://www.dhl.ch/de/express/versand/kundenberatung/lithium_batterien.html  https://www.ups.com/media/news/de/intl_lithium_battery_regulations.pdf  https://www.heise.de/ct/ausgabe/2016-9-Transportvorschriften-fuer-Lithium-Ionen-Akkus-3166865.html
17:59.18DocScrutinizer05sorry, you'll have to find google translate yourself :-)
18:01.07DocScrutinizer05>>In der Folge verweigert die Deutsche Post den Auslandsversand ALLER Akkus. Man kann also streng genommen nicht mal mehr eine Taschenlampe mit AA-Mignon-Akkus verschicken. Klasse, einfach toll.<<
18:02.40*** join/#maemo RedW (~redw@89-74-182-178.dynamic.chello.pl)
18:07.10DocScrutinizer05https://www.heise.de/ct/zcontent/16/09-hocmsmeta/1461497180961019/contentimages/mue.Packanweisung.mbr_IG.jpg
18:09.31*** join/#maemo Venemo (~venemo@fedora/Venemo)
18:11.06*** join/#maemo Venemo (~venemo@fedora/Venemo)
18:41.03*** join/#maemo Venemo (~venemo@fedora/Venemo)
18:49.51DocScrutinizer05freemangordon: according to http://susepaste.org/74825427 (from https://www.ups.com/media/news/de/intl_lithium_battery_regulations.pdf) they could send up to 8 Polarcell in one package when they add the right stickers to the outside, make sure SOC=30%, and pack them correctly to avoid shortcircuits and damage from drop <= 120cm height
18:51.53DocScrutinizer05but you need to check Bulgaria customs regulations irrespective of IATA stuff
18:52.38jogaany thoughts about this one? https://www.indiegogo.com/projects/gemini-pda-android-linux-keyboard-mobile-device-phone#/
18:53.31jogaseems pretty sleek, eventually I need to find something to replace the n900 :)
18:55.09DocScrutinizer05looks good
18:55.27DocScrutinizer05yet to see how they solve the cellmo problem
18:56.12DocScrutinizer05you might find in the end that the "linux dual boot option" doesn't support phone functions
18:56.31freemangordonhmm sailfish/ubuntu OS - smells like libhybris
18:56.48DocScrutinizer05or that this "linux" is as crippled and locked down like e.g. in N9
18:57.33jogaDocScrutinizer05, I guess that would be a concern... since they're saying they'll support linux I guess they must've given it some thought too
18:58.45DocScrutinizer05don't expect too much thought given by manufacturers. E.G jolla didn't even think about reflashing the device when it been completely nuked by whatever mishap
18:58.58jogabut as long as someone produces a decent device I'm happy, hopefully some other options will be available too
18:59.09jogadoh
18:59.16raveloI'm following this project also
18:59.20jogaI don't know much about jolla myself
18:59.55raveloaccording to one of the last newsposts it does not like they support calling in linux
18:59.55*** join/#maemo robink (~quassel@unaffilated/robink)
19:00.06freemangordonravelo: are there any details on that "linux support"?
19:00.06joga:I
19:00.23ravelofreemangordon, I try to look it up
19:00.40*** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
19:01.06jogatbh I could live fine with a tiny phone-phone and that thing, since my use of n900 currently is 99.9% ssh anyway
19:01.21ravelo"The key device drivers that we will need are of course the screen, keyboard, memory management, battery management, WiFi and we have a commitment with our manufacturing partners’ design house to enable us to do this."
19:01.34jogawell, not necessarily fine if I couldn't get network heh
19:01.41jogabut that can be arranged I guess
19:02.03raveloothers mentioned that Mediatek is not that open and has old Linux kernels
19:02.07raveloin comments
19:02.19freemangordonravelo: not a word about GPU drivers
19:02.51ravelo"he plan is to develop as many Linux drivers for the device in the time available to support a variety of distros"
19:03.01ravelowhich for me sounds not so clear
19:03.11freemangordonand WTF is "memory management driver"?
19:03.14ravelothe reason for developing device drivers is not to support more distros
19:04.12ravelothey up to now only had the idea for the keyboard and chose mediatek
19:04.23ravelonow they did a trip to china and had some meetings
19:04.50DocScrutinizer05freemangordon: most recent SoC+cellmo share storage and RAM between (linux) APE CPU and modem, so they depend on 'linux' APE securely avoiding users mess with the radio stack in any way
19:05.28raveloit looks like the boss did some successfull projects in the past, but more software than hardware
19:05.29jogasometimes I feel like buying an old 80s portable with a chunky keyboard, putting rpi with 4g in there and call it a day
19:07.01DocScrutinizer05freemangordon: so "memory management driver" most likely is exactly that: make sure APE has no access to radio stack to avoid hackers messing with e.g. IMEI (to start with)
19:08.04DocScrutinizer05to assure system integrity on that level, they need to employ some shit like AEGIS, or more generally speaking TrustedComputing
19:08.13DocScrutinizer05~trust
19:08.13infobotit has been said that trust is safe, or http://www.youtube.com/watch?v=0cbS_lDJuJg
19:09.14ravelohttps://talk.maemo.org/showthread.php?t=99022 -> discussion about gemini pda
19:10.27freemangordonDocScrutinizer05: I wonder how MM driver and AEGIS-like stuff goes with debian or ubuntu
19:10.29ravelomaybe you should also notice that the boss joined a company as director after a crowdfunding of 500.000 EUR and up to now they don't look like they will ever ship a device (zx vega spectrum plus)
19:10.55raveloat least up to now
19:12.38DocScrutinizer05freemangordon: there are aegis like projects in debian already, since ages.
19:13.21DocScrutinizer05along UEFI, secureboot, systemd, whatnot the buzzwords
19:13.22*** join/#maemo xy2_ (~xy2_@mlv95-h01-176-134-46-233.dsl.sta.abo.bbox.fr)
19:13.50jogaravelo, hmh, interesting..
19:33.03ravelojoga: maybe wait until first devices ship, then buy for 399,00
19:33.10raveloif you are interested
19:38.20*** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
19:49.46*** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
19:53.49Enrico_MenottiHey guys, anybody may help me with the question I asked at half past six?
19:57.47*** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
20:03.36*** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
20:03.45*** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
20:03.48sicelodid you follow the steps on wiki verbatim?
20:04.39Enrico_MenottiLet me check.
20:07.17Enrico_MenottiI could not do all the reported steps. For example, setxkbmap did not work (command not found).
20:10.57sicelothen you should install it :)
20:11.32siceloi haven't needed to play with my mappings in a long time, but i never had a problem in debian following the wiki
20:12.10Enrico_MenottiAlso with systemd running?
20:12.31sicelono. pre-systemd times.
20:12.42siceloi don't see what systemd has to do with this though
20:14.23Enrico_MenottiAh. As I have read around, systemd has also something to do with locales. But I may be completely wrong.
20:17.33sicelowell i admitted that my knowledge is 'old' .. but even systemd should then set correct locale? and you adjust the correct files for your locale? i don't see where problem would be
20:20.07Enrico_MenottiI have a keyboard with two arrows. It works fine, except for the up and down arrows: instead of being fn + left and fn + right, they are shift + left and shift + right. After some investigation, I found out this is caused by xkb being unable to recognise the type "PC_FN_LEVEL2".
20:20.37Enrico_MenottiAlso, I need to set up some additional symbols. E.g., ~, |, esc, ...
20:26.26DocScrutinizer05regarding the "linux dualboot" >>we are exploring a number of Linux flavours. We will make a final decision in due course and will let you know. ...<< https://talk.maemo.org/showthread.php?p=1524641  WTF why would I need THEM to decide *which* "Linux flavours" they allow me to install?
20:26.52DocScrutinizer05seems to me they have a pretty flawed indea of what's "Linux"
20:30.44DocScrutinizer05or it just means they provide a TrustedConouting solution for that thing which will turn your linux into something like Harmattan or Android, wher you can't do stuff even when you might manage to gain root access
20:31.03DocScrutinizer05TrustedComputing*
20:31.44*** join/#maemo dafox (~dafox@ip565ed369.direct-adsl.nl)
20:31.56DocScrutinizer05not my idea of what I want for a PDA/smartphone
20:33.09*** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au)
20:33.42TheKit<joga> any thoughts about this one? https://www.indiegogo.com/projects/gemini-pda-android-linux-keyboard-mobile-device-phone#/
20:33.42TheKit<joga> seems pretty sleek, eventually I need to find something to replace the n900 :)
20:34.17TheKitif you can afford two extra inches, I would probably advice to look at GPD Pocket
20:36.06TheKitit uses Intel Atom SoC, so Linux without libhybris and manufacturer successfully did other devices before
20:38.04jogaseems pretty nice too at first glance
20:39.01*** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
20:39.08*** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
20:42.44*** join/#maemo cyteen (~cyteen@146.66.58.6)
20:46.56TheKit<DocScrutinizer05> freemangordon: so "memory management driver" most likely is exactly that: make sure APE has no access to radio stack to avoid hackers messing with e.g. IMEI (to start with)
20:47.14TheKitMediaTek-based devices usually have no problems with changing IMEI to whatever value you like :)
20:47.49ShadowJKMy N900 had 180 days uptime
20:48.24ShadowJKThen my gf unplugged it to charge her camera and 3 days later I notice
20:49.02DocScrutinizer05DAMN!
20:49.07DocScrutinizer05:-D
20:51.30siceloyay! 180. i'm at 54 (highest uptime i ever had)
20:52.05KotCzarnyuptime, shrooptime
20:53.11ShadowJKindeed
20:53.31DocScrutinizer05t900:~# uptime
20:53.33DocScrutinizer05<PROTECTED>
20:53.35ShadowJKMy N900 serves as backup disk space and VPN router these days. uptime is unimpressive in that.
20:54.20KotCzarnymine usually dies because i neglect to charge it when low
20:55.19KotCzarnyso usually 5 days
20:55.26*** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
20:55.27KotCzarnysometimes up to 20-30
20:55.50DocScrutinizer05*cough*
20:55.52DocScrutinizer05t900:~# ls -l /var/log/syslog
20:55.54DocScrutinizer05-rw-r--r--    1 root     root     65675189 Apr 14 23:46 /var/log/syslog
20:57.43DocScrutinizer05http://paste.ubuntu.com/24382909
21:02.44DocScrutinizer05hmm, swap help welcomes me
21:02.49DocScrutinizer05hell
21:04.57KotCzarnyhttps://pastebin.com/raw/HiM2imcN
21:05.09KotCzarny41M free
21:05.12KotCzarnyhue hue
21:05.23DocScrutinizer05http://paste.ubuntu.com/24382959
21:08.22*** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
21:09.20DocScrutinizer05funny ubifs, when deleting a 66MB file only frees up ~15MB
21:10.43DocScrutinizer05http://paste.ubuntu.com/24382989
21:11.17DocScrutinizer05-rw-r--r--    1 root     root       206251 Apr 15 00:02 /var/log/syslog
21:11.28DocScrutinizer05F U tracker
21:16.21ShadowJKI forget, does "file /var/log/syslog" display how much physical space the file takes up?
21:16.39DocScrutinizer05prolly not
21:16.48DocScrutinizer05ls neither
21:16.54DocScrutinizer05;-)
21:17.13ShadowJKI know there was something that showed both
21:17.32DocScrutinizer05umm yep, forgot what it been
21:17.37DocScrutinizer05stat?
21:17.44ShadowJKhm
21:24.06DocScrutinizer05http://stackoverflow.com/questions/31394106/in-which-case-will-the-physical-size-of-a-file-be-smaller-than-the-logical-size
21:26.30DocScrutinizer05or du ?
21:27.02*** join/#maemo Maxdamantus (~Maxdamant@unaffiliated/maxdamantus)
21:28.10ShadowJKstat doesn't do it
21:36.44DocScrutinizer05hmmph  http://paste.ubuntu.com/24383077
21:42.42DocScrutinizer05t900:~# stat  /var/log/syslog
21:42.43DocScrutinizer05<PROTECTED>
21:42.45DocScrutinizer05<PROTECTED>
21:43.21DocScrutinizer05F U messybox
21:44.29DocScrutinizer05I read this as virtual size 5773, phy size 16 * 4096
21:47.10DocScrutinizer05no, IO Block doesn't match
21:47.18DocScrutinizer05no, IO Block doesn't match %B
21:47.43DocScrutinizer05so virtual size 5773, phy size 16 * 512
21:48.26DocScrutinizer05prolly allocates 8 blocks at a time though
21:48.53DocScrutinizer05thus with >4k size, it uses 16 blocks aka 8k
21:50.13DocScrutinizer05thinks a block always = 512, by definition
21:51.10DocScrutinizer05except in tools like mkfs where you specify blocksize
21:53.18DocScrutinizer05https://linux.die.net/man/8/mkfs.ext3
21:58.58DocScrutinizer05http://paste.ubuntu.com/24383168 not even stat itself *really* knows ;-P
21:59.29DocScrutinizer05"Block size: 4096       Fundamental block size: 4096" vs %B=512
22:17.42*** join/#maemo N-Mi_ (~nicolas@adsl.n-mi.com)
22:59.26*** join/#maemo florian (~fuchs@Maemo/community/contributor/florian)

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