| 00:04.11 | *** join/#maemo-ssu LaoLang_cool (~LaoLang_c@221.226.175.141) |
| 00:52.37 | jonwil | ~seen pali |
| 00:52.38 | infobot | pali <~pali@Maemo/community/contributor/Pali> was last seen on IRC in channel #maemo-ssu, 2d 13h 32m 26s ago, saying: 'freemangordon, do you know state of portrait keyboard?'. |
| 00:53.51 | DocScrutinizer05 | jonwil: maybe you should just post your comments to the general public, pali will likely read them in backscroll/chanlog. Others might be interested and able to help as well |
| 00:55.46 | jonwil | well its not really comments but some specific questions about changes he made :) |
| 01:02.49 | *** join/#maemo-ssu joshgillies (~josh@ppp108-33.static.internode.on.net) |
| 01:25.49 | *** join/#maemo-ssu jonwil (~jonwil@27-33-137-199.static.tpgi.com.au) |
| 03:52.40 | *** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn) |
| 04:03.47 | *** join/#maemo-ssu DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg) |
| 05:06.58 | *** join/#maemo-ssu jonwil_ (~jonwil@27-33-137-199.static.tpgi.com.au) |
| 07:04.10 | *** join/#maemo-ssu luf (~luf@ip-89-102-208-114.net.upcbroadband.cz) |
| 07:11.12 | luf | merlin1991: ping |
| 07:45.44 | *** join/#maemo-ssu LaoLang_cool (~LaoLang_c@221.226.175.141) |
| 07:50.09 | *** join/#maemo-ssu dhbiker (~dhbiker@APN-122-82-143-gprs.simobil.net) |
| 08:31.39 | *** join/#maemo-ssu kolp (~quassel@212.255.18.4) |
| 08:40.59 | Sicelo | hmm |
| 09:03.50 | *** join/#maemo-ssu dhbiker (~dhbiker@APN-123-19-22-gprs.simobil.net) |
| 10:27.07 | *** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu) |
| 11:05.55 | *** join/#maemo-ssu FIQ|n900 (~FIQ@unaffiliated/fiq) |
| 11:06.45 | FIQ|n900 | ~changelog |
| 11:06.45 | infobot | i heard changelog is dpkg-deb --fsys-tarfile whatever.deb | tar xOf - '*changelog.Debian.gz' | gzip -d | less |
| 11:07.51 | freemangordon | luf: don't you sleep man? :P |
| 11:25.28 | freemangordon | kerio: going to try to thumb-compile libjpeg, any idea for benchmarks? |
| 11:26.33 | freemangordon | WTF?!? |
| 11:26.57 | freemangordon | no source code ?!? |
| 11:27.24 | jon_y | freemangordon: libjpeg? |
| 11:27.30 | freemangordon | yep |
| 11:27.47 | jon_y | you could probably find it as libjpeg6 or jpeg7 in the wild |
| 11:28.41 | freemangordon | jon_y: so? how I am sure the ABI is the same :( |
| 11:29.04 | jon_y | good point, test it and see if an app crashes :) |
| 11:29.19 | jon_y | or look at the libjpeg headers for clues if there are any |
| 11:29.35 | jon_y | or compare symbols in the lib |
| 11:29.45 | freemangordon | sure, but this is huge amount of work |
| 11:29.48 | FIQ|n900 | i wonder what HAM decides is good in terms of battery for maemo updates? |
| 11:29.53 | *** join/#maemo-ssu NIN101 (~NIN@p5DD28124.dip0.t-ipconnect.de) |
| 11:29.58 | FIQ|n900 | say I have a *really* slow connection |
| 11:30.08 | FIQ|n900 | will it adjust? |
| 11:30.21 | FIQ|n900 | or just try to install as battery runs dry |
| 11:30.37 | jon_y | I don't think it checks |
| 11:31.00 | FIQ|n900 | it does check battery before doing a maemo update |
| 11:31.08 | freemangordon | :nod: |
| 11:31.12 | FIQ|n900 | but *when*? after or before download? |
| 11:31.19 | freemangordon | before |
| 11:31.24 | freemangordon | iirc |
| 11:31.25 | FIQ|n900 | genius |
| 11:31.27 | FIQ|n900 | or not |
| 11:31.33 | FIQ|n900 | well |
| 11:31.37 | FIQ|n900 | it should check both |
| 11:31.39 | freemangordon | actually not sure |
| 11:31.53 | freemangordon | it might be after the download |
| 11:32.12 | FIQ|n900 | you can stop the update when it downloads |
| 11:32.25 | FIQ|n900 | but I don't think you can do other stuff when it do |
| 11:32.37 | FIQ|n900 | (as checking the battery) |
| 11:40.15 | *** join/#maemo-ssu povbot (~supybot@office.pov.lt) |
| 11:40.17 | *** mode/#maemo-ssu [+v povbot] by ChanServ |
| 11:46.57 | freemangordon | perfect, libjpeg has tons of NEON optimizations made by Nokia, but no source code :( |
| 11:47.38 | jon_y | what is the license? |
| 11:48.28 | jon_y | if BSD/Apache, there isn't anything you can do about it |
| 11:48.51 | freemangordon | jon_y: it is even worse |
| 11:49.24 | jon_y | <PROTECTED> |
| 11:49.54 | freemangordon | the license |
| 11:50.06 | jon_y | what is it licensed under? |
| 11:50.51 | freemangordon | it's own license, similar to BSD |
| 11:51.33 | jon_y | yeah, weak copyleft suck |
| 11:51.38 | freemangordon | I found the original code, but NEON patches are missing, ofc |
| 11:52.11 | jon_y | not sure if asking nicely for the code will net you anything |
| 11:52.42 | freemangordon | from deian changelog: "-- Gary Birkett <gary.birkett@collabora.co.uk> Wed, 10 Jan 2010 14:10:00 +0000" |
| 11:52.50 | freemangordon | *debian |
| 11:52.56 | freemangordon | I'd rather not ask ;) |
| 11:53.34 | jon_y | the neon code came from debian maintainers? |
| 11:53.48 | freemangordon | that guy is dead afaik |
| 11:54.08 | jon_y | oh, I did not know that |
| 11:54.49 | jon_y | http://forum.meego.com/showthread.php?t=4524 |
| 11:54.49 | *** join/#maemo-ssu tg (~irc@2001:738:2001:2078:0:215:11:82) |
| 11:55.19 | freemangordon | exactly |
| 11:55.31 | freemangordon | gonna check what is the situation in meego |
| 11:57.42 | freemangordon | hmm, the same guy that changed maemo patches is the committer to libjpeg-turbo neon optimizations |
| 12:00.38 | freemangordon | well, seems like patches are there. at least some of them: |
| 12:00.39 | freemangordon | http://git.linaro.org/gitweb?p=people/tomgall/meego/libjpeg-turbo.git;a=summary |
| 12:01.38 | jon_y | you can tell what parts are missing? |
| 12:02.37 | freemangordon | hard to say if anything is missing, I have only patch names from debian/changelog |
| 12:03.33 | freemangordon | and those patches are for libjpeg-turbo, not for libjpeg |
| 12:04.00 | jon_y | are they API/ABI similar? |
| 12:04.14 | freemangordon | I may ask merlin1991 to politely ask Siarhei Siamashka for the original patches |
| 12:04.27 | freemangordon | jon_y: NFC |
| 12:14.12 | DocScrutinizer05 | freemangordon: try to find other collabora (ex-)employess |
| 12:15.02 | DocScrutinizer05 | ~lcuk |
| 12:15.03 | infobot | well, lcuk is a mighty good developer, best known for his work on liqbase and helping Nokia with the Identity project during the onedotzero event in London. |
| 12:15.20 | freemangordon | DocScrutinizer05: seems we need to pester that guy ^^^. And there is some : |
| 12:15.22 | freemangordon | + * Copyright (C) 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. |
| 12:15.22 | freemangordon | + * Contact: Alexander Bokovoy <alexander.bokovoy@nokia.com> |
| 12:15.35 | DocScrutinizer05 | lcuk is dead |
| 12:15.44 | freemangordon | (that guy is Siarhei Siamashka) |
| 12:15.48 | DocScrutinizer05 | aah |
| 12:15.59 | freemangordon | he is the same in debian/changelog |
| 12:16.30 | freemangordon | for maemo libjpeg neon patches, seems lcuk was just a maintainer |
| 12:16.49 | freemangordon | merlin1991: ^^^ |
| 12:17.11 | freemangordon | I am aware lcuk is dead |
| 12:35.12 | *** join/#maemo-ssu BCMM (~BCMM@unaffiliated/bcmm) |
| 12:54.59 | jonwil | I always wondered why Nokia didn't open source libjpeg |
| 12:55.25 | jonwil | but it seems the answer is "because they made nice optimizations to it they didn't want everyone else to have" :) |
| 12:55.35 | freemangordon | yeah :( |
| 12:56.06 | jonwil | Same probably applies to other stuff in SDK non-free like vorbis |
| 12:58.48 | *** join/#maemo-ssu FIQ|n900 (~FIQ@unaffiliated/fiq) |
| 12:59.12 | FIQ|n900 | is >50% really "too little" for HAM? |
| 13:01.48 | freemangordon | kerio: a new thumby bb-power in in the repo |
| 13:01.55 | freemangordon | *is in |
| 13:59.20 | luf | freemangordon: never sleeping man asking me when I sleep? :D |
| 14:01.55 | luf | freemangordon: what about bluez? Is it ok or it doesn't work for you? |
| 14:05.26 | freemangordon | hehe |
| 14:05.41 | freemangordon | no problems so far on my devel device |
| 14:05.48 | freemangordon | but i didn;t use it much |
| 14:05.58 | luf | freemangordon: is this changelog for libpng ok? |
| 14:05.59 | luf | <PROTECTED> |
| 14:05.59 | luf | <PROTECTED> |
| 14:05.59 | luf | <PROTECTED> |
| 14:05.59 | luf | <PROTECTED> |
| 14:06.15 | luf | Or should I give their your credits? |
| 14:06.24 | freemangordon | luf: pull the latest from gitorious |
| 14:06.29 | freemangordon | I changed it |
| 14:06.47 | luf | Right I tried it last in the morning :) |
| 14:06.52 | freemangordon | debian/changelog that is |
| 14:07.29 | luf | Ok. |
| 14:08.08 | freemangordon | luf: BTW if you are going to edit it, don;t increase the vesrsion number please |
| 14:08.11 | freemangordon | *version |
| 14:08.26 | luf | No I'm not going to change it. |
| 14:08.44 | freemangordon | ok. as I already pushed it i -thumb repo |
| 14:08.45 | luf | As I wrote I checked it in the morning and there were no such change. |
| 14:08.59 | freemangordon | I know, I did it an hour ago |
| 14:11.35 | freemangordon | luf: so, zlib NEON patch brings no benefit? |
| 14:12.41 | freemangordon | BTW what path is optimized - inflation or deflation? |
| 14:12.54 | luf | freemangordon: it brings some benefit. But it's not so big as I hoped. |
| 14:13.06 | freemangordon | well, every bit helps |
| 14:13.12 | luf | deflation - for sure. I'm not sure about inflation. |
| 14:13.33 | luf | I'm too bored with all the benchmarks :) |
| 14:13.43 | freemangordon | BTW it might do better with gcc4.7.2, there are some comments in the patch re gcc not doing its best in some loop |
| 14:14.21 | freemangordon | luf: how did you benchmark it? |
| 14:14.28 | luf | I think also the package is -Os (maybe -O<something else> should help too. |
| 14:14.39 | luf | zpipe |
| 14:14.40 | freemangordon | WTF is that? |
| 14:15.17 | freemangordon | yeah, for ARM -02 is the pest |
| 14:15.21 | luf | http://pastebin.com/1QWkuSS7 |
| 14:15.22 | freemangordon | *best |
| 14:16.11 | luf | ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) |
| 14:16.12 | luf | CFLAGS=-O0 |
| 14:16.12 | luf | else |
| 14:16.12 | luf | # By default, optimise for osso |
| 14:16.12 | luf | CFLAGS=-Os |
| 14:16.12 | luf | endif |
| 14:16.26 | luf | This is from rules ... (from last maemo package). |
| 14:16.45 | luf | ... and also in the package I compiled. |
| 14:17.10 | freemangordon | luf: -Os is optimize for speed |
| 14:17.57 | freemangordon | luf: where to find zpipe? |
| 14:18.07 | luf | on zlib.net |
| 14:18.23 | luf | http://www.zlib.net/zpipe.c |
| 14:18.30 | freemangordon | ok |
| 14:19.25 | freemangordon | anyway, i'll leave that for the next year :D |
| 14:24.33 | luf | So long time with not supporting maemo? :D |
| 14:24.55 | luf | Keep your time ;) |
| 14:25.06 | freemangordon | :D |
| 14:25.16 | freemangordon | I'm feeling lazy now |
| 14:25.32 | freemangordon | and TBH it is tklock I have to do first |
| 14:25.43 | luf | I'm glad that someone cooperate with me. |
| 14:25.51 | freemangordon | on lazyness? |
| 14:26.00 | freemangordon | :P |
| 14:26.05 | luf | Yeah the question of my reboots ... |
| 14:26.15 | luf | Any hint to see what was happen? |
| 14:26.39 | luf | Now the dev N900 keeps running. |
| 14:28.14 | luf | BTW I want to upload zlib (and also recompiled libpng - againist new zlib) into cssu-devel. But I'm not sure if merlin1991 is ok with that. Also I need the patched libxml2 for it ... |
| 14:29.08 | ShadowJK | i thought -Os was size |
| 14:30.31 | freemangordon | ShadowJK: could be |
| 14:30.42 | freemangordon | luf: cssu-devel is exactly for that |
| 14:31.12 | freemangordon | though i'd expect the code to bo on gitorious before .deb lands in cssu-devel |
| 14:31.17 | luf | freemangordon: not if you and merlin1991 and others don't agree with upgrading zlib ;) |
| 14:31.43 | luf | And of course git repo (after agreement). |
| 14:32.02 | freemangordon | luf: anyone is against upgrading? |
| 14:32.14 | luf | you were ... |
| 14:32.27 | luf | due to libxml2 bug with newer zlib. |
| 14:32.28 | freemangordon | hmm, nooo |
| 14:32.42 | luf | No way to check all the apps depending on zlib. |
| 14:33.13 | freemangordon | I was not against, I just wanted to know the possible implications |
| 14:33.25 | luf | :) |
| 14:34.06 | freemangordon | luf: i'd say put it in -devel |
| 14:35.03 | freemangordon | luf: keep in mind you have to put libxml there too |
| 14:48.05 | luf | I'll wait for merlin1991 ;) with agreement and also git repo creation. |
| 14:48.30 | freemangordon | :nod: |
| 14:50.13 | freemangordon | luf: re your reboot |
| 14:50.24 | freemangordon | install sp-rich-core and upload coredumps |
| 14:50.32 | freemangordon | or debug them yourself |
| 14:50.43 | kerio | what does the sp- prefix mean? |
| 14:50.53 | freemangordon | NFC |
| 14:51.09 | kerio | it's the same as sp-oops-extract, right? |
| 14:51.21 | freemangordon | same? |
| 14:52.09 | freemangordon | luf: http://maemo.org/development/tools/doc/chinook/sp-rich-core/ |
| 14:52.27 | freemangordon | not sure if there is an entry for fremantle |
| 14:52.32 | freemangordon | on wiki that is |
| 14:55.18 | *** join/#maemo-ssu arcean (~Arcean@aafq143.neoplus.adsl.tpnet.pl) |
| 15:00.27 | freemangordon | luf: we should upgrade libpng in microb-engine too |
| 15:00.47 | freemangordon | or tell microb to use system libpng |
| 15:01.55 | freemangordon | hmm, it seems it already uses that] |
| 15:03.18 | freemangordon | hmm, no |
| 15:05.59 | *** join/#maemo-ssu FIQ|n900 (~FIQ@unaffiliated/fiq) |
| 15:06.43 | FIQ|n900 | where can I report bugs in HAM in the read only state? not at all? |
| 15:08.27 | freemangordon | on TMO |
| 15:08.54 | FIQ|n900 | hmmmmmmmm |
| 15:09.00 | FIQ|n900 | in the cssu thread I suppose |
| 15:12.24 | FIQ|n900 | i.e. http://talk.maemo.org/showthread.php?t=80525 |
| 15:12.53 | freemangordon | yep, if you are on -testing |
| 15:13.26 | FIQ|n900 | well it likely affects all cssu flavours and pre-cssu |
| 15:13.41 | FIQ|n900 | but I can't test on anything else than testing |
| 15:13.57 | freemangordon | this thread should be ok then |
| 15:15.33 | FIQ|n900 | also, @ first post, latest is 7, not 5 :P |
| 15:16.19 | luf | freemangordon: what cores are you talking about? |
| 15:16.57 | freemangordon | luf: coredumps |
| 15:17.30 | freemangordon | luf: BTW we may want this http://sourceforge.net/projects/libpng-apng/files/libpng12/1.2.49/ included in libpng |
| 15:17.47 | freemangordon | so we can build microb with system libpng and zlib |
| 15:18.06 | luf | what coredumps? I don't see such things. The device crashed and rebooted. |
| 15:18.19 | freemangordon | luf: you need sp-rich-core installed |
| 15:18.27 | freemangordon | read the wiki article |
| 15:18.33 | FIQ|n900 | posted the issue |
| 15:19.38 | freemangordon | thanks |
| 15:20.20 | luf | freemangordon: what wiki article? |
| 15:20.35 | freemangordon | <PROTECTED> |
| 15:21.50 | FIQ|n900 | freemangordon: should I report apt issues in the same thread? |
| 15:21.59 | freemangordon | yep |
| 15:22.03 | FIQ|n900 | ok |
| 15:22.42 | luf | Ugh I saw no wiki in the url. I see it and it's for next crash ... |
| 15:23.09 | luf | freemangordon: why we need apng? Any feature request? |
| 15:23.18 | freemangordon | luf: microb needs it |
| 15:23.30 | freemangordon | now microb uses it own libpng |
| 15:24.00 | freemangordon | if we add apng support in libpng, we can build microb to use system libpng, which is NEON-optimized ;) |
| 15:24.04 | luf | Ok. However I vote for step by step ... Test the current libpng+neon patches first. |
| 15:24.04 | freemangordon | (will be) |
| 15:25.11 | freemangordon | :) |
| 15:25.29 | luf | freemangordon: I'm not sure if something segfault ... I think I saw some suggestion about crash info somewhere .... |
| 15:26.03 | freemangordon | luf: install sp-rich-core and make sure you have the correct directories created. as described on wiki |
| 15:26.26 | freemangordon | if you have kenel oops, check in /dev/mtd2 |
| 15:26.44 | luf | freemangordon: how to check? |
| 15:27.07 | freemangordon | cat it |
| 15:27.51 | luf | /media/mmc1 is on rootfs? |
| 15:28.02 | freemangordon | no, it is uSD card |
| 15:28.20 | luf | I see no such thing in mount ... |
| 15:28.32 | freemangordon | do you have uSD |
| 15:28.34 | freemangordon | ? |
| 15:28.51 | luf | No if it's additional card. |
| 15:29.17 | freemangordon | additional card? |
| 15:29.22 | freemangordon | micro SD |
| 15:30.09 | luf | Should it be next to camera lens? |
| 15:30.25 | luf | I don't put any uSD. I have N900 as I bought it. |
| 15:30.44 | freemangordon | if you don't have micro SD card in the device, you should create the directory somewhere in /home/user/ |
| 15:31.00 | freemangordon | not sure exactly ehere though |
| 15:31.23 | luf | No problem I'll symlink it to /media/mmc1/code-dumps |
| 15:31.40 | *** join/#maemo-ssu FIQ|n900 (~FIQ@unaffiliated/fiq) |
| 15:31.46 | freemangordon | luf: don;t |
| 15:31.57 | freemangordon | create it in /home/user/MyDocs |
| 15:32.05 | FIQ|n900 | "not enough battery" with battery over 50%... ok |
| 15:32.20 | luf | mkdir /home/user/MyDocs/core-dumps/ |
| 15:32.25 | freemangordon | and run some application that crash (segfaults for example) |
| 15:32.30 | freemangordon | yep |
| 15:32.33 | FIQ|n900 | not my fault if apt takes an hour (literally) to load all packages subject to update lol |
| 15:32.57 | freemangordon | luf: make sure you have as many debug packages installed as possible |
| 15:33.10 | FIQ|n900 | s/apt/HAM/ |
| 15:33.29 | luf | freemangordon: It's like space shuttle launch :D |
| 15:33.40 | freemangordon | luf: only the first time :P |
| 15:33.51 | luf | I have no apps which segfault :D |
| 15:33.58 | freemangordon | compile one :P |
| 15:34.18 | FIQ|n900 | "let's break stuff intentionally" :3 |
| 15:34.26 | luf | Ugh and you said you're the lazy one? :D I see you don't know me. |
| 15:34.30 | freemangordon | (int*)NULL = 'lif'; |
| 15:34.39 | freemangordon | oops |
| 15:34.42 | freemangordon | (int*)NULL = 'luf'; |
| 15:34.48 | freemangordon | *(int*)NULL = 'luf'; |
| 15:35.10 | FIQ|n900 | "oops, made something which actually works" |
| 15:35.20 | freemangordon | hehe |
| 15:35.35 | FIQ|n900 | wow |
| 15:35.41 | FIQ|n900 | disabled devel |
| 15:35.55 | FIQ|n900 | and apt took 5min instead of 1h to load updates |
| 15:36.19 | FIQ|n900 | though i'll still have to wait for other battery to charge |
| 15:37.35 | *** join/#maemo-ssu FIQ|n900 (~FIQ@unaffiliated/fiq) |
| 15:39.46 | luf | strange the example from wiki doesn't crash :D |
| 15:40.35 | freemangordon | whaat? |
| 15:40.40 | luf | Ok I get it. |
| 15:40.51 | luf | And I see .lzo in core-dumps in MyDocs ... |
| 15:40.57 | freemangordon | great |
| 15:41.01 | freemangordon | that's it |
| 15:41.03 | luf | I used -O2 to be faster :D |
| 15:41.13 | freemangordon | now you need sp-richcore-extract :P |
| 15:41.32 | luf | Hmmm I have to leave now. |
| 15:41.42 | freemangordon | http://maemo.org/development/documentation/man_pages/rich-core-extract/ |
| 15:41.50 | freemangordon | ok |
| 15:41.59 | luf | So happy new year ;) And of course a lot of enthusiasm for maemo ... |
| 15:42.11 | freemangordon | the same for you |
| 15:42.21 | freemangordon | :P |
| 16:09.58 | *** join/#maemo-ssu FredrIQ|n900 (~FIQ@unaffiliated/fiq) |
| 16:44.09 | *** join/#maemo-ssu AndrewX192 (~andrew@002369d5e799.click-network.com) |
| 16:44.09 | *** join/#maemo-ssu AndrewX192 (~andrew@unaffiliated/andrewx192) |
| 17:05.09 | DocScrutinizer05 | kerio: sp-rich-core and sp-oops-extract are completely different tools |
| 17:06.15 | kerio | i figure |
| 17:10.47 | *** join/#maemo-ssu FIQ|n900 (~FIQ@unaffiliated/fiq) |
| 17:10.55 | DocScrutinizer05 | ((<freemangordon> and run some application that crash (segfaults for example))) killall -SIGBUS app |
| 17:11.11 | FIQ|n900 | ah, seems HAM check both before and after download |
| 17:11.21 | FIQ|n900 | anyway |
| 17:11.37 | FIQ|n900 | does HAM and battery indicator use different ways of determing charge? |
| 17:11.58 | FIQ|n900 | indicator showed 70%ish before download, HAM accepted and started dl |
| 17:12.18 | FIQ|n900 | then refused to update once downloaded, battery still shows 70%ish |
| 17:12.50 | DocScrutinizer05 | HAM may use a simplified methos not depending on HAL |
| 17:13.07 | DocScrutinizer05 | like probing raw bat voltage for example |
| 17:13.37 | DocScrutinizer05 | at least that's what NOLO does for deciding to allow flashing |
| 17:13.43 | DocScrutinizer05 | afaik |
| 17:13.57 | FIQ|n900 | ok |
| 17:15.24 | FIQ|n900 | have HAM deleted downloaded file now? -.- |
| 17:15.32 | FIQ|n900 | or will it actually use what it downloaded earlier |
| 17:16.26 | FIQ|n900 | assuming a new update isn't out the next time I try (a hour or so from now) |
| 17:16.44 | DocScrutinizer05 | I doubt it's that smart |
| 17:16.57 | FIQ|n900 | :( |
| 17:17.02 | kerio | DocScrutinizer05: nah, it probably just asks hald |
| 17:17.19 | FIQ|n900 | then trying to update up here is just a waste of time |
| 17:17.20 | kerio | otherwise it wouldn't work if you had pali's replacement |
| 17:17.34 | kerio | DocScrutinizer05: otoh, apt caches do exist |
| 17:17.38 | FIQ|n900 | and then I should wait before proper connection again |
| 17:17.44 | kerio | FIQ|n900: check /home/.apt-archive-cache |
| 17:18.05 | DocScrutinizer05 | also check HAM settings in redpill mode |
| 17:18.07 | FIQ|n900 | assuming you mean /home/opt? |
| 17:18.17 | FIQ|n900 | DocScrutinizer05: which setting exactly? |
| 17:18.19 | kerio | assuming is bad |
| 17:18.20 | DocScrutinizer05 | I seem to recall a "delete cache" option |
| 17:18.25 | kerio | it makes an ass out of u and some poor guy named ming |
| 17:18.39 | kerio | i meant /home/.apt-archive-cache |
| 17:18.46 | DocScrutinizer05 | kerio |
| 17:18.48 | DocScrutinizer05 | nope |
| 17:18.55 | FIQ|n900 | nothing there |
| 17:19.08 | DocScrutinizer05 | you meant ~user/.apt-archive-cache I guess |
| 17:19.09 | FIQ|n900 | and placing it in /home sounds weird in general |
| 17:19.22 | kerio | DocScrutinizer05: just check it, dawg |
| 17:19.39 | FIQ|n900 | also I don't have any of these directories |
| 17:19.45 | FIQ|n900 | er |
| 17:20.03 | FIQ|n900 | *also I don't have this in /home, ~ or /opt |
| 17:20.08 | kerio | \_o_/ |
| 17:20.15 | DocScrutinizer05 | IroN900:~# locate .apt-archive-cache |
| 17:20.17 | DocScrutinizer05 | locate: Warnung: Die Datenbank "/var/cache/locate/locatedb" ist älter als 8 Tage (Das Alter ist 99,0 Tage). |
| 17:20.18 | DocScrutinizer05 | /home/user/MyDocs/.apt-archive-cache |
| 17:20.19 | DocScrutinizer05 | /home/user/MyDocs/.apt-archive-cache/lock |
| 17:20.21 | DocScrutinizer05 | /home/user/MyDocs/.apt-archive-cache/partial |
| 17:20.22 | DocScrutinizer05 | /rescue/.apt-archive-cache |
| 17:20.39 | FIQ|n900 | yes I have it there |
| 17:20.45 | kerio | weird |
| 17:20.49 | kerio | why do i have that in /home then |
| 17:20.56 | FIQ|n900 | well maybe at least |
| 17:21.02 | FIQ|n900 | the directory is there :p |
| 17:21.16 | FIQ|n900 | and contain lots of .deb files |
| 17:21.58 | FIQ|n900 | [18:18:20] <DocScrutinizer05> I seem to recall a "delete cache" option |
| 17:22.19 | FIQ|n900 | "Clean apt cache" you mean? |
| 17:22.25 | DocScrutinizer05 | yup |
| 17:22.29 | FIQ|n900 | I have an option like that |
| 17:22.34 | DocScrutinizer05 | might be related, no? |
| 17:22.37 | FIQ|n900 | And it's checked |
| 17:22.41 | FIQ|n900 | yeah |
| 17:22.57 | FIQ|n900 | but uhh |
| 17:23.05 | FIQ|n900 | it doesn't seem to work |
| 17:23.23 | FIQ|n900 | as even if it's checked, I have lots of .deb files in the archive directory |
| 17:23.44 | DocScrutinizer05 | so maybe it's sth different |
| 17:24.44 | FIQ|n900 | but this is odd |
| 17:24.53 | FIQ|n900 | latest .deb is downloaded dec 25 |
| 17:24.54 | FIQ|n900 | ie last week |
| 17:24.55 | DocScrutinizer05 | I seem to recall there been /var/apt/cache or sth as well |
| 17:25.04 | DocScrutinizer05 | once a few years ago |
| 17:25.17 | FIQ|n900 | but I also have a "partial" directory, latest modified 15min ago |
| 17:25.28 | FIQ|n900 | but it's empty |
| 17:26.11 | DocScrutinizer05 | I once suggested to clean it, and that dude wanted to kill me for that suggestion |
| 17:27.08 | DocScrutinizer05 | <PROTECTED> |
| 17:27.27 | DocScrutinizer05 | <PROTECTED> |
| 17:27.33 | FIQ|n900 | DocScrutinizer05: assuming /var/cache/apt, that directory seems to exist |
| 17:27.44 | FIQ|n900 | but it was modified a long time ago |
| 17:28.14 | DocScrutinizer05 | <PROTECTED> |
| 17:28.29 | DocScrutinizer05 | well, the last one been silly |
| 17:28.54 | kerio | DocScrutinizer05: which dude wanted to kill you for that? :O |
| 17:29.05 | FIQ|n900 | correction: the directory was modified today for 2h ago, but I misread |
| 17:29.11 | FIQ|n900 | -but |
| 17:29.28 | DocScrutinizer05 | the dude on IRC who *NEEDED* his device resurrected til next morning |
| 17:29.55 | DocScrutinizer05 | but uptdate to PR1.1 failed with usual "use Nokia suite" |
| 17:30.52 | FIQ|n900 | "resurrected" "update to PR1.1" wut? |
| 17:30.53 | DocScrutinizer05 | I was silly enough to not clearly explain what I meant with "clean it" |
| 17:31.17 | DocScrutinizer05 | FIQ|n900: loooong ago |
| 17:32.45 | DocScrutinizer05 | btw get locate, it's cooolman! |
| 17:33.19 | DocScrutinizer05 | and since my patch even updatedb works |
| 17:35.07 | FIQ|n900 | locate being in repos? |
| 18:31.00 | DocScrutinizer05 | yup |
| 18:31.44 | DocScrutinizer05 | I think it's not in findutils pkg anymore, but rather own pkg. maybe not |
| 18:33.33 | DocScrutinizer05 | findutils-gnu - utilities for finding files--find, xargs |
| 18:33.35 | DocScrutinizer05 | locate - maintain and query an index of a directory tree |
| 18:33.51 | DocScrutinizer05 | locate need findutils |
| 18:34.39 | DocScrutinizer05 | I patched updatedb by adding one char "g" ;-D |
| 18:34.55 | DocScrutinizer05 | so now it works with gnu-find |
| 18:35.16 | DocScrutinizer05 | messybox find is brainfsckd as usual and doesn't work for updatedb |
| 18:35.31 | FIQ|n900 | :P |
| 18:35.41 | DocScrutinizer05 | that patch been moved to repo eventually |
| 18:37.47 | DocScrutinizer05 | fires up a manual updatedb, just for the fun of it (I didn't feel like setting up a cron job for that) |
| 18:38.57 | FIQ|n900 | Hmmm |
| 18:39.08 | DocScrutinizer05 | hmmm? |
| 18:39.20 | FIQ|n900 | nbm |
| 18:39.21 | FIQ|n900 | *nvm |
| 18:40.00 | DocScrutinizer05 | IroN900:~# time updatedb |
| 18:40.02 | DocScrutinizer05 | <PROTECTED> |
| 18:40.03 | DocScrutinizer05 | real 1m28.969s |
| 18:40.05 | DocScrutinizer05 | user 0m49.398s |
| 18:40.06 | DocScrutinizer05 | sys 0m17.164s |
| 18:40.13 | DocScrutinizer05 | not half as bad as I anticipated |
| 18:56.37 | *** join/#maemo-ssu FIQ|n900 (~FIQ@unaffiliated/fiq) |
| 18:56.50 | FIQ|n900 | hm |
| 18:56.58 | FIQ|n900 | something odd happened |
| 18:57.33 | FIQ|n900 | instead of simply rebooting postupdate, HAM gave a two-line notice that I didn't manage to read before it rebooted |
| 18:58.21 | FIQ|n900 | "The operating system has been updated. The device will reboot. Errors(...)" it said (something like it at least) |
| 18:58.38 | FIQ|n900 | Did an error occur or what? Couldn't really read all of it lol |
| 19:03.14 | DocScrutinizer05 | find /var ~user/MyDocs/ -mtime 1 |
| 19:06.28 | FIQ|n900 | also once I moved some stuff from home to mydocs |
| 19:06.36 | FIQ|n900 | er wrong channel |
| 19:07.17 | DocScrutinizer05 | find /var ~user/MyDocs/ -mtime 1 -ls 2>/dev/null |
| 19:07.58 | DocScrutinizer05 | hope you'll be able to spot something in there that has logs about that "error" |
| 19:08.29 | DocScrutinizer05 | or otherwise indicates what went wrong |
| 19:08.38 | FIQ|n900 | nothing |
| 19:08.56 | DocScrutinizer05 | sth in syslog? |
| 19:09.19 | DocScrutinizer05 | not at end but before or immediately after last boot |
| 19:09.48 | FIQ|n900 | where is this? |
| 19:10.54 | DocScrutinizer05 | <PROTECTED> |
| 19:10.55 | DocScrutinizer05 | in less |
| 19:11.34 | DocScrutinizer05 | less '+/syslog.*restart' /var7log7syslog |
| 19:11.41 | DocScrutinizer05 | err |
| 19:11.47 | DocScrutinizer05 | s/7/// |
| 19:12.11 | FIQ|n900 | no such file |
| 19:12.24 | DocScrutinizer05 | hmm, then you got no syslog running |
| 19:12.27 | FIQ|n900 | (and yes I corrected your spelling) |
| 19:12.42 | DocScrutinizer05 | if you used / unstead 7 |
| 19:12.57 | FIQ|n900 | yes, / instead of 7 |
| 19:13.05 | FIQ|n900 | was what I meant :p |
| 19:13.37 | DocScrutinizer05 | then you're probably out of luck to find any info about what happened |
| 19:13.43 | FIQ|n900 | oh well |
| 19:13.49 | FIQ|n900 | hopefully it was all ok |
| 19:14.42 | DocScrutinizer05 | you could search whole device for new files |
| 19:14.50 | DocScrutinizer05 | might take a while |
| 19:15.04 | DocScrutinizer05 | find / -mtime 1 -ls 2>/dev/null |
| 19:19.24 | FIQ|n900 | not worth the effort imo |
| 19:19.27 | *** join/#maemo-ssu kolp (~quassel@212.255.18.4) |
| 19:19.32 | FIQ|n900 | because I've noticed nothing wrong |
| 19:20.51 | DocScrutinizer05 | sth odd with my shell foo |
| 19:21.29 | DocScrutinizer05 | above line doesn't find my /var/log/syslog despite Modify: 2012-12-31 20:00:09.000000000 +0100 |
| 19:21.57 | DocScrutinizer05 | actually above line doesn't find *anything* |
| 19:22.04 | DocScrutinizer05 | :-S |
| 19:22.19 | DocScrutinizer05 | is going to retire |
| 19:22.43 | DocScrutinizer05 | nah, not really since at least on my laptop it works as expected |
| 19:23.08 | DocScrutinizer05 | nfc what idiocy is built in to maemo again |
| 19:23.17 | FIQ|n900 | busybox find? |
| 19:25.05 | DocScrutinizer05 | IroN900:~# find --version |
| 19:25.06 | DocScrutinizer05 | find (GNU findutils) 4.4.2 |
| 19:25.15 | DocScrutinizer05 | N*F*C |
| 19:25.15 | FIQ|n900 | ok |
| 19:26.09 | DocScrutinizer05 | MEH!!!! |
| 19:26.14 | DocScrutinizer05 | -mtime -1 |
| 19:26.20 | DocScrutinizer05 | WTF?! |
| 19:27.09 | *** join/#maemo-ssu kolp (~quassel@212.255.18.4) |
| 19:27.18 | DocScrutinizer05 | <PROTECTED> |
| 19:27.19 | DocScrutinizer05 | <PROTECTED> |
| 19:27.49 | DocScrutinizer05 | which idiot changed sematics of -mtime in gnu-find? |
| 19:31.46 | FIQ|n900 | lol |
| 19:33.08 | DocScrutinizer05 | would you agree that there's not written "File's data was last modified <now>+n*24 hours" ? |
| 19:40.08 | DocScrutinizer05 | ok, you cheered too soon, I won't retire. Will bash the shit out of somebody instead ;-P |
| 19:41.44 | Raimu | :) |
| 19:42.07 | DocScrutinizer05 | at least if that individual changed -mtime semantics on purpose |
| 19:42.48 | *** join/#maemo-ssu Estel_ (~Estel@178235127192.piaseczno.vectranet.pl) |
| 19:42.48 | *** join/#maemo-ssu Estel_ (~Estel@Maemo/community/contributor/Estel-) |
| 19:43.26 | DocScrutinizer05 | it took me like 3 years to wrap my mind around that somewhat weird semantics of "n*24h ago", now somebody going to change it??? |
| 19:44.45 | Estel_ | quick question to CSSU team, if you don't mind |
| 19:45.34 | Estel_ | last version (again) changes things related to initial system boot - /usr/lib/genfstab (as before), and /etc/event.d/rcS-late, in particular |
| 19:45.48 | DocScrutinizer05 | I'm afraid we'll get into same old discussion about your notion of "CSSU team" not in line with reality |
| 19:46.52 | Estel_ | as person using different filesystem for /home, I had, obviously, to change ext3 to ext4 in those two files (and overall, to bring personal modifications of rcS-late to new one) |
| 19:47.12 | ShadowJK | oh hai estel, long time no see :) |
| 19:47.14 | Estel_ | now, my question: |
| 19:47.23 | Estel_ | hello ShadowJK :) nice to see you still here |
| 19:47.58 | Estel_ | well, in fact, I was lurking here all the time, just haven't had time nor will to talk |
| 19:48.06 | Estel_ | as for question... |
| 19:48.31 | Estel_ | is there any other thing/config option/file/whatever, that users of different filesystems (than ext3) should consider... |
| 19:48.51 | Estel_ | while using latest CSSU (thumb variant, in particular, but it shouldn't matter in this case) |
| 19:48.56 | Estel_ | ? |
| 19:49.08 | ShadowJK | was considering switching to ext4 |
| 19:49.24 | ShadowJK | last time I benchmarked, ext4 looked nice on flash |
| 19:49.29 | ShadowJK | nucer than ext3, that is |
| 19:49.47 | Estel_ | is using ext4 happily, for ages |
| 19:49.58 | DocScrutinizer05 | basically it was much desirable when standard CSSU files as mentioned above would already take care about non-default filesystems |
| 19:50.00 | *** join/#maemo-ssu NIN101 (~NIN@p5DD28124.dip0.t-ipconnect.de) |
| 19:50.11 | Estel_ | yea, benchmarks look nice. I dont't feel "obvious" improvements in real life, though - for sure no regressions, still |
| 19:51.09 | DocScrutinizer05 | if they don't, it could be considered a valid bug |
| 19:51.13 | DocScrutinizer05 | against CSSU |
| 19:51.30 | ShadowJK | Probably ext4 and also fixing sqlite would bring a major reduction in jitter and stutter |
| 19:52.28 | Estel_ | fun fact - last time CSSU update put ext4/reiserfs into reboot loop, I was the one who reported reasons for it (found them during debugging session with freemangordon, as I was blaming CSSU). Now, months later, when installing CSSU on family member's device, I was hit ny reboot loop - just to find out, after day of searching, my own report about reasons :P |
| 19:52.53 | Estel_ | ShadowJK, define fixing sqlite? |
| 19:53.52 | Estel_ | also, I've heard about some parameters via tuenefs, that we should set to make ext4 even more efficient in our device's case... (ones that work only on ext4, not older ext's), but never tried them |
| 19:54.08 | Estel_ | something about fragments and blocks? /noob mode |
| 19:54.14 | FIQ|n900 | what about disabling journal |
| 19:54.37 | ShadowJK | FIQ|n900; no |
| 19:54.43 | FIQ|n900 | ok |
| 19:54.52 | ShadowJK | if anything, we want an absolutely massively humongous journal |
| 19:54.58 | FIQ|n900 | i've heard there's no point on it in n900 |
| 19:55.17 | DocScrutinizer05 | btw the above question is a tad fuzzy and hard to answer, at least it's not exactly related to CSSU |
| 19:55.25 | DocScrutinizer05 | (any other files) |
| 19:55.25 | Estel_ | well, journal saved my as* dozens times |
| 19:55.41 | ShadowJK | Well, none of the file integrity procedures in any filesystem (besides ubifs) works on flash anyway |
| 19:55.47 | Estel_ | well, I mean only files related to last CSSU update |
| 19:56.15 | Estel_ | I've found two files mentioned above, that need manual tweaking from recovery shell to allow device boot... |
| 19:56.21 | FIQ|n900 | ..then why should you keep it? |
| 19:56.28 | FIQ|n900 | @ ShadowJK |
| 19:56.44 | DocScrutinizer05 | file a bug, they should allow boot from arbitrary filesystems when we already touch them |
| 19:56.48 | Estel_ | still, no idea, if I should also change something else, to avoid non-critical (not putting me into bootloop) functions of latest cssu update |
| 19:56.51 | ShadowJK | So journal or no journal from file integirty point of view probably makes little difference, although having journal present stops fsck, and fsck gets confused by flash dropping random megabytes here and there |
| 19:57.11 | FIQ|n900 | ok |
| 19:57.35 | ShadowJK | But journal is written sequentially, which gives us speed boost. Of course, later when journal is comitted we take the penalty for writing non-sequential.. |
| 19:57.57 | Estel_ | DocScrutinizer05, I can, but wasnt it you who replied - last time - that CSSU won't ever support different filesystems, officially? |
| 19:58.16 | DocScrutinizer05 | ShadowJK: the trick is to write-back journal during times when system is idle |
| 19:58.46 | DocScrutinizer05 | err, if anything I answered CSSU can't support user mods on system files |
| 19:59.13 | ShadowJK | As for sqlite, same thing really, allegedly for harmattan/meego they were investigating a mode that essentially made sqlite journal-only |
| 19:59.14 | DocScrutinizer05 | which might sound similar to your ears |
| 19:59.37 | Estel_ | ShadowJK, what you have written may be reason, why my home gest TOTALLY fcked sometimes, when small thing gets wrong (i.e. one file get busted wrong way by crash, and fsck gest confused = wipe out half of my inodes)? |
| 19:59.53 | ShadowJK | For sure, sqlite writing one row/record/whatever and calling fsync 5 times takes about 5 secs |
| 20:00.13 | Estel_ | (then fail to repair anything, as e2fs is ancient on N900, and segfaults during restoration phase...) |
| 20:00.16 | DocScrutinizer05 | if I actually answered CSSU will never support non-default filesystems then I uttered BS |
| 20:00.17 | ShadowJK | Yeah I tried fsck on /home once, big big mistake :) |
| 20:00.21 | FIQ|n900 | speaking of fsck, is fscking MyDocs safe? |
| 20:00.30 | ShadowJK | if it's unmounted |
| 20:00.48 | FIQ|n900 | well it isn't but i was going to umount it before doing it so.. :p |
| 20:01.45 | DocScrutinizer05 | fsck of MyDocs never really worked, it takes AGES |
| 20:02.02 | DocScrutinizer05 | like... DAYS |
| 20:02.17 | Estel_ | well, ShadowJK, guy named BadHabit released, one, actual Debian's e2fsprogs (that don't segfault on N900) - but, still, it won't work *really* well on N900, due to flash? |
| 20:02.24 | FIQ|n900 | DocScrutinizer05: hmm.. |
| 20:02.26 | Estel_ | DocScrutinizer05, hm? |
| 20:02.32 | ShadowJK | Estel_; I'd say so |
| 20:02.34 | FIQ|n900 | i was going to remove bogus files in mydocs |
| 20:02.40 | FIQ|n900 | which it didn't allow me to |
| 20:02.46 | Estel_ | I'm doing fsck.vfat /dev/mmcblk0p1 many times (MyDpocs unmounted) |
| 20:02.49 | FIQ|n900 | due to "IO errors" |
| 20:02.52 | Estel_ | never got any problems with it? |
| 20:03.19 | DocScrutinizer05 | well, it might work occasionally, depending on amount of mess and number of files there |
| 20:03.19 | ShadowJK | FIQ|n900; check dmesg also for physical io errors :s |
| 20:03.39 | DocScrutinizer05 | problem is RAM for fsck |
| 20:03.49 | DocScrutinizer05 | eventually enters swap hell |
| 20:04.01 | DocScrutinizer05 | then everything comes to a grinding halt |
| 20:04.47 | DocScrutinizer05 | while fsck on a clean fs should usually work |
| 20:04.51 | FIQ|n900 | ShadowJK: "[ 4910.734466] invalid access to FAT (entry 0x350d7ff6)" like these? |
| 20:04.52 | ShadowJK | I think I've only done it via pc |
| 20:05.02 | ShadowJK | those are filesystem errors |
| 20:05.12 | DocScrutinizer05 | via PC should work |
| 20:05.40 | FIQ|n900 | this started by a system freeze when I mv-ed some files from ~ |
| 20:05.45 | Estel_ | hm, I remember fsck.vfat repairing errors on my microSD vfat, once. Never took ages. Any community project touched fsck.vfat? |
| 20:06.12 | FIQ|n900 | "[ 4910.734436] FAT: Filesystem error (dev mmcblk0p1)" is shown numerous times when I ls the directory |
| 20:06.18 | Estel_ | also, keep in mind that I have radically uncommon swap settings ( ShadowJK would sympatize) |
| 20:06.27 | DocScrutinizer05 | as explained above it depends on swap usage and number of errors to fix |
| 20:06.37 | ShadowJK | has swap+ext3 on uSD :-) |
| 20:06.42 | DocScrutinizer05 | uSD has a hw interface independant of swap |
| 20:07.02 | ShadowJK | gpodder's .gpodder on uSD too, so that /home is idle when gpodder downloads to Mydocs :) |
| 20:07.31 | Estel_ | :) 2x 2GB swap on microSD (only one used at once), and very uncommon settings re swap I/O, batching, etc |
| 20:07.52 | FIQ|n900 | also now by listing the directory, MyDocs seems to have remounted to read-only |
| 20:08.05 | FIQ|n900 | s/listing/removing/ (trying to) |
| 20:08.26 | DocScrutinizer05 | FIQ|n900: use mass storage mode, do fsck from PC |
| 20:08.54 | DocScrutinizer05 | I never did it but I heard it works, and usually flawlessly |
| 20:09.04 | Estel_ | well, anyway, my question about any other things related to different (than ext3) filesystem present on device, and last cssu release, still apply. I wonder who touched upstart and ke-recv in last CSSU? |
| 20:09.10 | Estel_ | ke-recv is for sure Pali's work |
| 20:09.30 | FIQ|n900 | "FATs differ but appear to be intact. Use which FAT ?" what? |
| 20:09.35 | FIQ|n900 | DocScrutinizer05: hmm |
| 20:09.58 | DocScrutinizer05 | FIQ|n900: difficult |
| 20:10.03 | Estel_ | noticed new panic settings in rcS-late, merged them with my rcS-late. obviously, updated genfstab. I wonder, if something else should be considered. |
| 20:10.19 | ShadowJK | FIQ|n900; you've got a backup of before-fsck, right.. |
| 20:10.24 | Estel_ | FIQ|n900, most of the times, use older one |
| 20:10.58 | FIQ|n900 | ShadowJK: tbh no, as I don't really have anything important in it |
| 20:11.15 | FIQ|n900 | unless maemo settings go there, which I was unaware of if it did |
| 20:11.21 | Estel_ | being scientifically curious about results? |
| 20:11.29 | ShadowJK | Heh, has that "fsck if mount fails" in rcS-late always been there, or is that cssu? |
| 20:11.43 | DocScrutinizer05 | FIQ|n900: my suggestion: copy everything to PC, mkfs.vfat, copy PC->MyDocs |
| 20:11.45 | Estel_ | always been there |
| 20:12.16 | DocScrutinizer05 | ShadowJK: I already blamed a massive bug about it |
| 20:12.45 | FIQ|n900 | "copy everything to PC" as in, dd-ing the fs to a file? |
| 20:12.46 | DocScrutinizer05 | it doesn't show ANY idication to user about fsck ongoing and possibly slowing down boot to minutes or hours |
| 20:13.32 | DocScrutinizer05 | FIQ|n900: copy as in cp -a |
| 20:14.02 | ShadowJK | Well also in my experience fsck is more harmful than no fsck :s |
| 20:14.15 | DocScrutinizer05 | FIQ|n900: dd would also copy the borked fs metainfo |
| 20:14.16 | ShadowJK | maybe fsck was added after optification stuff |
| 20:14.19 | Estel_ | exactly |
| 20:14.28 | Estel_ | especially which parts of procedure segfaulting ;) |
| 20:14.36 | Estel_ | always segfaulting, btw |
| 20:15.01 | FIQ|n900 | DocScrutinizer05: that's my point, wasn't the goal to clean the fs on computer? |
| 20:15.14 | DocScrutinizer05 | if fsck.ext2 is segfaulting, please rise a bug against CSSU, it needs to get fixed |
| 20:16.04 | DocScrutinizer05 | FIQ|n900: nah, copy stuff to PC, mkfs on N900, copy stuff back to N900 to the virgin fs |
| 20:16.21 | FIQ|n900 | got it |
| 20:16.34 | DocScrutinizer05 | will fix fs as well as defragment and create a backup on PC |
| 20:16.54 | FIQ|n900 | though i'll wait a while and eventually come back asking next week as I don't have computer here |
| 20:16.57 | DocScrutinizer05 | and most likely be faster than fsck |
| 20:17.11 | FIQ|n900 | and just try to avoid using mydocs meanwhile |
| 20:17.17 | DocScrutinizer05 | well, then try fsck |
| 20:17.20 | DocScrutinizer05 | on device |
| 20:17.24 | FIQ|n900 | now? |
| 20:17.27 | FIQ|n900 | ok |
| 20:17.34 | DocScrutinizer05 | abort if it fails to finish in ~30min |
| 20:18.01 | FIQ|n900 | FATs differ but appear to be intact. Use which FAT ? -- what does this mean? |
| 20:18.08 | FIQ|n900 | (I rarely if ever use fsck) |
| 20:18.21 | DocScrutinizer05 | there are FAT copies, if one fails |
| 20:18.25 | FIQ|n900 | 1:use first FAT, 2:use second |
| 20:18.30 | Estel_ | well, there are certain cases, when another sub-program need to be called |
| 20:18.36 | Estel_ | something about lost+found? |
| 20:18.44 | Estel_ | it's part of fsck procedure in this case |
| 20:18.58 | ShadowJK | fsck would call fsck.ext3 |
| 20:19.03 | Estel_ | so, it doesn't fail *always*, it segfault when fsck try to repair serious things |
| 20:19.05 | DocScrutinizer05 | FIQ|n900: up to you which to use, probably 1st is the one which alreeady has files deleted |
| 20:19.05 | ShadowJK | but that's about it afaik |
| 20:19.13 | DocScrutinizer05 | while 2nd hasn't yet |
| 20:19.18 | Estel_ | ShadowJK, then 2nd pass comes |
| 20:19.40 | Estel_ | damn how was it called |
| 20:19.46 | Estel_ | gimme a sec |
| 20:19.51 | FIQ|n900 | hmm wait, battery low |
| 20:20.00 | FIQ|n900 | i'll screw this for the coming 20min |
| 20:20.10 | DocScrutinizer05 | charger? |
| 20:20.29 | FIQ|n900 | I use an external charger |
| 20:20.29 | DocScrutinizer05 | or broken USB? |
| 20:20.37 | DocScrutinizer05 | aah :-/ |
| 20:21.16 | FIQ|n900 | well i have 2 batteries, so just waiting until this one dies before switching and resuming trying to fix mydocs |
| 20:21.38 | *** join/#maemo-ssu NIN101 (~NIN@p5DD28124.dip0.t-ipconnect.de) |
| 20:22.52 | DocScrutinizer05 | Estel_: I'm not aware of any other files that would need special care when fs-type of /home got changed |
| 20:23.20 | DocScrutinizer05 | for fs-type of MyDocs you might need to check the scripts that export mass storage |
| 20:23.39 | Estel_ | thanks. Yea, aware of mydocs (using fat there, anyway) |
| 20:23.45 | DocScrutinizer05 | yw |
| 20:23.47 | Estel_ | e2fsck |
| 20:23.52 | DocScrutinizer05 | no warranty though |
| 20:23.53 | Estel_ | this segfaults on 2nd pass |
| 20:24.07 | Estel_ | if directories/files need 2nd pass |
| 20:24.17 | DocScrutinizer05 | I'll blame werner almesberger ;-P |
| 20:24.31 | Estel_ | damn, I'm quite bad at explaining it. Go, make backuo, then do a mess in filesystem and try fsck on device :P |
| 20:25.10 | DocScrutinizer05 | ehmmm, maybe I already did? |
| 20:25.29 | DocScrutinizer05 | (blame wpwrak) |
| 20:25.59 | DocScrutinizer05 | seem to recall discussions with him about bugs in fsck |
| 20:26.12 | DocScrutinizer05 | oooh, fsck.vfat |
| 20:26.19 | DocScrutinizer05 | iirc |
| 20:26.31 | Estel_ | I would quote exact way to replace faulty Maemo's version with debian one, but *of course* I can't scroll my PM box to second page, on device, due to awesome TMO theme, supporting 1024 as lowest |
| 20:26.45 | Estel_ | and cutting half of buttons, no matter of zoom |
| 20:26.56 | DocScrutinizer05 | >>dosfstools were written by Werner Almesberger<< |
| 20:27.09 | DocScrutinizer05 | man fsck.vfat |
| 20:27.44 | DocScrutinizer05 | >>This version of e2fsck was written by Theodore Ts'o<< |
| 20:36.56 | *** join/#maemo-ssu FredrIQ|n900 (~FIQ@unaffiliated/fiq) |
| 20:36.58 | FredrIQ|n900 | well ok |
| 20:37.02 | FredrIQ|n900 | battery died |
| 20:37.14 | FredrIQ|n900 | now to fsck MyDocs |
| 20:42.56 | FIQ|n900 | wow MyDocs seem to be really messed up |
| 20:44.11 | FIQ|n900 | after a while of asking whether to drop files with bad names, it ended up asking "Free cluster summary wrong (257837 vs. really 262121)" and prompted for correct or don't correct |
| 20:44.27 | FIQ|n900 | both answers led to aborting the operation completely |
| 20:45.53 | FIQ|n900 | the last output from it before this was " Start cluster beyond limit (4294967295 > 442378). Truncating file." |
| 20:48.42 | FIQ|n900 | so DocScrutinizer05 what do you suggest? |
| 20:49.04 | *** join/#maemo-ssu Estel_ (~Estel@178235127192.piaseczno.vectranet.pl) |
| 20:49.04 | *** join/#maemo-ssu Estel_ (~Estel@Maemo/community/contributor/Estel-) |
| 20:58.26 | FIQ|n900 | another question |
| 20:58.37 | FIQ|n900 | is user settings stored in MyDocs or just media data? |
| 20:58.52 | kerio | application-dependent |
| 20:59.01 | kerio | usually in ~/.something |
| 20:59.12 | FIQ|n900 | because if it's the latter I might as well backup critical stuff (i.e. backupmenu entries for example) and just reformat |
| 20:59.30 | FIQ|n900 | hmm ok |
| 20:59.52 | FIQ|n900 | I tried fsck -a atm |
| 21:00.16 | FIQ|n900 | because that one allowed me to proceed after that odd question which simply aborted no matter what I did |
| 21:00.23 | kerio | run backupmenu or rescueos, export the whole emmc via mass storage, fsck from a computer |
| 21:00.32 | FIQ|n900 | broken usb |
| 21:00.55 | FIQ|n900 | and no computer access atm anyway |
| 21:10.05 | FIQ|n900 | ok after 10min fsck -a exits with error: "Unable to create unique name" |
| 21:11.33 | DocScrutinizer05 | FIQ|n900: you have a uSD? |
| 21:13.01 | FIQ|n900 | hmm |
| 21:13.09 | FIQ|n900 | yes but not sure if inserted |
| 21:13.09 | FIQ|n900 | sec |
| 21:13.37 | FIQ|n900 | no |
| 21:13.38 | FIQ|n900 | then I don't have it |
| 21:13.45 | FIQ|n900 | (unless I wait a week) |
| 21:14.30 | DocScrutinizer05 | copy everything (that still exists after that fsck run) to uSD (don't forget to take care about unfreezing measures for large cop^K |
| 21:15.50 | FIQ|n900 | I don't think fsck has done anything at all.. |
| 21:16.05 | FIQ|n900 | it simply exited with no apparent operation |
| 21:16.27 | FIQ|n900 | DocScrutinizer05: no uSD until 6th |
| 21:16.36 | ShadowJK | i think it needs -w to actually do stuff :) |
| 21:16.40 | FIQ|n900 | also anti-freeze is already in place |
| 21:17.03 | FIQ|n900 | uhm default is "simulate"? |
| 21:17.06 | FIQ|n900 | or? :p |
| 21:19.23 | FIQ|n900 | ah it does figure what to do first, then write to disk |
| 21:19.25 | ShadowJK | i seem to remember it's funny |
| 21:19.31 | FIQ|n900 | but as it failed, nothing altered |
| 21:20.00 | FIQ|n900 | unless -w (write immediately) is set |
| 21:20.21 | DocScrutinizer05 | o/ |
| 21:20.26 | DocScrutinizer05 | and happy new year |
| 21:20.44 | FIQ|n900 | same |
| 21:20.53 | FIQ|n900 | so.. |
| 21:20.57 | FIQ|n900 | hm |
| 21:21.22 | FIQ|n900 | i'm kinda stuck in current state atm as I'm not home |
| 21:26.44 | FIQ|n900 | also interesting is that MyDocs seems mostly intact, as I discovered the corruption just now (I used to think it simply copied half of the stuff then nothing) |
| 21:27.03 | FIQ|n900 | which is a month since i did this... |
| 21:27.50 | FIQ|n900 | and mydocs is in rw unless I show or try to modify these files |
| 21:28.22 | FIQ|n900 | so imo it *should* be possible to solve just by removing them (which seems impossible) |
| 21:32.27 | *** join/#maemo-ssu nox- (noident@freebsd/developer/nox) |
| 21:36.48 | FIQ|n900 | or should have been* |
| 21:37.09 | FIQ|n900 | as it was a long time ago, fs becomes more messed up |
| 21:46.33 | FIQ|n900 | problem appears to be solved by fsck -w |
| 21:47.14 | FIQ|n900 | and by the looks of it, file system still contains the stuff I'm interested in (besides the file I mv-ed last month, but that was kind of obvious) |
| 21:48.21 | FIQ|n900 | reason for my willing to continue fix even though I risk have lost stuff is that I didn't want to damage the fs even more by continuing to use it |
| 21:56.42 | DocScrutinizer05 | congrats |
| 21:58.32 | FIQ|n900 | ty |
| 22:36.51 | *** join/#maemo-ssu jonwil (~jonwil@27-33-137-199.static.tpgi.com.au) |
| 22:37.51 | jonwil | ~seen pali |
| 22:37.55 | infobot | pali <~pali@Maemo/community/contributor/Pali> was last seen on IRC in channel #maemo-ssu, 3d 11h 17m 43s ago, saying: 'freemangordon, do you know state of portrait keyboard?'. |
| 23:18.52 | *** join/#maemo-ssu FIQ|n900 (~FIQ@unaffiliated/fiq) |