| 00:00.01 | HtheB | (guys at #harmattan are asleep I gues) |
| 00:00.49 | HtheB | http://talk.maemo.org/showthread.php?p=1331232#post1331232 |
| 00:01.48 | *** join/#maemo Woody14619a (~Woody@2620:4:4000:11:e835:757c:1fd1:ddff) |
| 00:01.48 | *** join/#maemo Woody14619a (~Woody@Maemo/community/contributor/Woody14619) |
| 00:04.38 | kerio | amospalla: it's not something you install on a n900 |
| 00:04.51 | kerio | at least, it's not intended to be as such |
| 00:05.20 | amospalla | kerio: yeah, right, but, can I put it on my n900 without any multiboot thing? that is what I mean |
| 00:05.25 | *** join/#maemo Muelli (~muelli@port-33182.pppoe.wtnet.de) |
| 00:06.58 | amospalla | like kernel-power-bootimg or multiboot package |
| 00:10.14 | *** join/#maemo pvanhoof (~philip@codeminded.be) |
| 00:34.19 | *** join/#maemo uen| (~uen@p5DCB2848.dip.t-dialin.net) |
| 00:45.22 | *** join/#maemo RzR (~RzR@82.236.136.171) |
| 00:54.21 | *** join/#maemo RzR (~RzR@82.236.136.171) |
| 01:01.08 | *** part/#maemo Aoyagi (~opera@222.18.broadband15.iol.cz) |
| 01:04.51 | *** join/#maemo RzR (~RzR@82.236.136.171) |
| 01:26.37 | *** join/#maemo ron0062000 (~ron006200@cpe-72-181-242-49.tx.res.rr.com) |
| 01:29.41 | *** join/#maemo Hurrian (~Hurrian@124.6.157.37) |
| 01:48.11 | *** join/#maemo Luke-Jr (~luke-jr@2001:470:5:265:222:4dff:fe50:4c49) |
| 01:52.54 | *** join/#maemo NeutrinoPower (~neutrino@HSI-KBW-078-042-162-195.hsi3.kabel-badenwuerttemberg.de) |
| 01:52.57 | *** join/#maemo Aoyagi (~opera@222.18.broadband15.iol.cz) |
| 01:56.13 | *** join/#maemo FlameReaper-PC (~honoo-pc@203.106.65.1) |
| 01:57.52 | *** join/#maemo vblazquez (~vic@32.9.77.188.dynamic.jazztel.es) |
| 01:58.12 | *** join/#maemo gn00b (~gn00b@75-172-168-30.phnx.qwest.net) |
| 02:20.12 | *** join/#maemo norrsken_ (~quassel@g227113087.adsl.alicedsl.de) |
| 02:43.22 | *** join/#maemo FlameReaper-PC (~honoo-pc@203.106.65.1) |
| 02:54.19 | *** join/#maemo RzR (~RzR@82.236.136.171) |
| 03:00.34 | *** join/#maemo maybeHere (~cl@p5B1654A6.dip.t-dialin.net) |
| 03:03.36 | *** join/#maemo sirdancealot (~sirdancea@98.82.broadband5.iol.cz) |
| 03:24.48 | *** join/#maemo mavhc (~mavhc@cpc3-basf10-2-0-cust617.12-3.cable.virginmedia.com) |
| 03:40.44 | *** join/#maemo Muelli (~muelli@port-33182.pppoe.wtnet.de) |
| 03:45.45 | *** join/#maemo MetalGearSolid (~MetalGear@175.145.225.6) |
| 04:01.02 | *** join/#maemo dockane (~dockane@dsdf-4db5ff10.pool.mediaWays.net) |
| 04:02.30 | *** join/#maemo MCLOVINiZME (mcLovin@c-69-254-169-147.hsd1.al.comcast.net) |
| 04:02.34 | *** part/#maemo MCLOVINiZME (mcLovin@c-69-254-169-147.hsd1.al.comcast.net) |
| 04:03.40 | *** join/#maemo DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg) |
| 04:08.58 | *** join/#maemo GI_Jack (~GI_Jack@pdpc/supporter/active/gi-jack) |
| 04:08.59 | GI_Jack | sup |
| 04:14.30 | *** join/#maemo gn00b (~gn00b@75-172-168-30.phnx.qwest.net) |
| 04:16.40 | *** join/#maemo hardaker (~hardaker@mail.hardakers.net) |
| 04:26.57 | *** join/#maemo RzR (~RzR@82.236.136.171) |
| 04:28.55 | *** join/#maemo topro (~topro@host-62-245-142-50.customer.m-online.net) |
| 04:36.26 | *** join/#maemo RzR (~RzR@82.236.136.171) |
| 04:44.27 | *** join/#maemo RzR (~RzR@82.236.136.171) |
| 04:50.11 | *** join/#maemo radic (~radic@dslb-178-002-209-012.pools.arcor-ip.net) |
| 04:56.58 | *** join/#maemo RzR (~RzR@82.236.136.171) |
| 05:11.59 | *** join/#maemo RzR (~RzR@82.236.136.171) |
| 05:12.38 | *** join/#maemo kaawee_ (~user@port-92-206-53-106.dynamic.qsc.de) |
| 05:13.26 | *** join/#maemo Hurrian (~Hurrian@121.54.58.209) |
| 05:13.56 | *** join/#maemo Hurrian (~Hurrian@121.54.58.209) |
| 05:14.29 | *** join/#maemo RzR (~RzR@82.236.136.171) |
| 05:20.02 | *** join/#maemo RzR (~RzR@82.236.136.171) |
| 05:22.40 | *** join/#maemo sLumPia (~sLumPia@182.2.197.57) |
| 05:23.58 | *** join/#maemo trumee (~parul@93.186.150.40) |
| 05:33.01 | *** join/#maemo RzR (~RzR@82.236.136.171) |
| 05:41.37 | *** join/#maemo jpinx (~jpinx@unaffiliated/jpinx) |
| 05:45.31 | *** join/#maemo RzR (~RzR@82.236.136.171) |
| 05:49.31 | *** join/#maemo RzR (~RzR@82.236.136.171) |
| 05:54.03 | *** join/#maemo RzR (~RzR@82.236.136.171) |
| 05:56.18 | DocScrutinizer05 | amospalla: no |
| 06:05.08 | *** join/#maemo croppa (~stuart@CPE-120-146-137-99.static.nsw.bigpond.net.au) |
| 06:09.05 | *** join/#maemo valerius (~user@95.153.164.131) |
| 06:20.31 | *** join/#maemo gn00b (~gn00b@75-172-168-30.phnx.qwest.net) |
| 06:31.44 | *** join/#maemo gantenbein (~gantenbei@79.165.56.123) |
| 06:50.54 | *** join/#maemo totalizator (~totalizat@89-79-239-132.dynamic.chello.pl) |
| 06:54.14 | *** join/#maemo kolp (~quassel@212.255.229.148) |
| 06:58.22 | *** join/#maemo disco_stu_droid (~wrt54gl@190.211.81.139) |
| 07:13.52 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 07:19.19 | *** join/#maemo OkropNick (kuba@host-n1-110-97.telpol.net.pl) |
| 07:24.39 | *** join/#maemo LauRoman (~LauRoman@5-14-92-176.residential.rdsnet.ro) |
| 07:43.41 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 07:46.35 | *** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 07:48.22 | *** join/#maemo Timmy (~quassel@unaffiliated/timmyt) |
| 07:50.29 | Timmy | I want to use mplayer on easy debian but there is no audio. how can i fix it? i can remember somewhere there was a guy about making changes in /etc/asound.conf but i actually don't remember what that was |
| 07:58.59 | DocScrutinizer05 | Timmy: well, the main problem is: maemo is using pulseaudio with Nokia proprietary policies (see alsaped which is oddly named since it's actually PAped aiui), PA in turn occupies the underlying ALSA soundcard exclusively. And any app using ALSA:default as audio output is in fact only using a alsa->PA compatibility plugin and thus still goes thru PA with its policies |
| 08:01.13 | Timmy | DocScrutinizer05: so you have any idea how i can fix mplayer on easy debian to play audio? |
| 08:01.28 | DocScrutinizer05 | changes in /etc/asound.conf *might* enable normal ALSA sound for apps like mplayer, but the downside most certainly is that it will likely fubar all PA based sound |
| 08:06.28 | *** join/#maemo cityLights (~nivw@bzq-218-29-26.cablep.bezeqint.net) |
| 08:08.46 | DocScrutinizer05 | http://www.xmarks.com/site/library.maemodocs.nokia.com/fremantle/ seems to suggest we lost huge parts of documentation forever |
| 08:18.07 | *** join/#maemo valerius (~user@85.26.180.150) |
| 08:25.12 | Timmy | DocScrutinizer05: here it is : http://talk.maemo.org/showpost.php?p=1289207&postcount=2858 |
| 08:28.56 | *** join/#maemo thauta (thautako@tuomi.oulu.fi) |
| 08:29.26 | *** part/#maemo thauta (thautako@tuomi.oulu.fi) |
| 08:29.41 | *** join/#maemo utanapischti (~username@p4FF2FDDA.dip.t-dialin.net) |
| 08:30.21 | DocScrutinizer05 | that redefines alsa:default as direct access to hw audiocard with no plugin stack at all in between. Which means a) you get no mixing, b) no reate/formate conversions c) it either will fail since PA has opened that audiocard exclusively, or you need to kill PA and thus break audio for whole rest of device which uses PA for all audio |
| 08:32.27 | DocScrutinizer05 | also this advice is about easydebian which is a chroot and thus has unclear but for sure no standard audio config at all |
| 08:33.21 | Timmy | DocScrutinizer05: you think it is possible to upgrade the mplayer of maemo to the latest version available? |
| 08:33.37 | DocScrutinizer05 | sure, why not |
| 08:33.55 | Timmy | DocScrutinizer05: that is because this version doen't display the rtl subtitles correctly |
| 08:34.11 | DocScrutinizer05 | it's however questionable if it will work OOTB and without massive patching for all plugins |
| 08:36.02 | DocScrutinizer05 | mplayer afaik is using an alternative decoder set to what mafw/gstreamer is using, and that alternative decoders need to take into account the particular hw and drivers found in maemo |
| 08:36.53 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 08:37.54 | DocScrutinizer05 | http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Architecture/Multimedia_Domain http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Using_Multimedia_Components/Media_Application_Framework_(MAFW) |
| 08:38.31 | Timmy | DocScrutinizer05: i don't know what's wrong with mplayer on easy debian, in the past when i entered those configurations into asound.conf, both of vlc and mplayer were working well. but after flashing the device, only vlc plays the audio |
| 08:41.34 | DocScrutinizer05 | particularly in diagrams in first page I linked above, see PulseAudio block and how it exposes ALSA (compatibility leagcy plugin) API upward to userspace but otoh uses ALSA device drivers in kernel (see downwards from PA block) |
| 08:42.55 | DocScrutinizer05 | Timmy: *where* are you changing that /etc/alsa.conf? In easybeb chroot or on host system maemo? |
| 08:42.57 | *** join/#maemo futpib (~futpib@89.106.197.47) |
| 08:43.22 | DocScrutinizer05 | Also notice that even the "hint" you linked to says you need to kill PA |
| 08:43.47 | Timmy | on easy deb and that was not alsa.conf, that was asound.conf |
| 08:43.49 | DocScrutinizer05 | which sure as hell is hot will kill audio for every normal app on maemo |
| 08:44.22 | *** join/#maemo Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr) |
| 08:44.31 | kerio | sending audio through the real alsa will fuck up your speakers |
| 08:44.38 | Timmy | and also this debian image is not a new one, this is what i have configured and used before |
| 08:44.51 | DocScrutinizer05 | kerio: that too, eventually |
| 08:45.32 | *** join/#maemo sixwheeledbeast (~paul@cl-1547.lon-02.gb.sixxs.net) |
| 08:46.48 | *** join/#maemo _rd (~rd@p57B489EB.dip0.t-ipconnect.de) |
| 08:53.22 | Timmy | i want to get the latest version of easy debian from http://qole.org/files/ but i don't know which one is the latest, can someone help me to choose one? |
| 08:54.26 | *** join/#maemo rcg (~rcg@2a02:908:e252:e101:9094:b4ec:40bb:1000) |
| 09:02.25 | Pali | DocScrutinizer05, any ETA for non working maemo.org package interface? |
| 09:02.44 | *** join/#maemo Timmy (~quassel@unaffiliated/timmyt) |
| 09:03.32 | Pali | after 5 months I'd like to push packages to extras-testing & extras... |
| 09:03.50 | freemangordon | :) |
| 09:11.06 | DocScrutinizer05 | Pali: I resigned from coordinating and supervising maemo infra. So no, I don't know |
| 09:11.48 | Pali | now I'm uploading ipv6 packages to extras-devel..., but still I cannot login to maemo.org/packages, so I cannot promote anything... |
| 09:12.01 | *** join/#maemo Macer (mace@scientiam.org) |
| 09:12.03 | freemangordon | DocScrutinizer05: what? since when? |
| 09:12.09 | Pali | DocScrutinizer05, who is responsible for it now? |
| 09:12.56 | DocScrutinizer05 | nobody? |
| 09:13.00 | DocScrutinizer05 | HiFo? |
| 09:13.15 | *** join/#maemo NIN101 (~NIN@p5DD2900B.dip0.t-ipconnect.de) |
| 09:13.44 | freemangordon | DocScrutinizer05: last you know - who had acces to those VM? |
| 09:13.52 | freemangordon | *access |
| 09:13.56 | DocScrutinizer05 | which ones |
| 09:14.10 | *** join/#maemo mvp (~mvp@port463.ds1-abc.adsl.cybercity.dk) |
| 09:15.11 | freemangordon | DocScrutinizer05: I guess it is garage, though not sure |
| 09:15.24 | freemangordon | abd autobuilder |
| 09:15.27 | freemangordon | *and |
| 09:18.14 | DocScrutinizer05 | well, last I know got officially established been Woody14619a:maintainer of garage, jacekowski:maintainer_ins_spe of builder. But builder_the_service_ is spread across several VM |
| 09:19.11 | freemangordon | Pali:I guess we should pester them than |
| 09:19.16 | freemangordon | Woody14619a: ping |
| 09:20.46 | Pali | DocScrutinizer05, access to website components maemo.org/packages/view/<name_of_package>/ |
| 09:20.50 | Pali | and fix logging |
| 09:21.34 | freemangordon | feels like he is back in the kindergarden |
| 09:22.13 | *** join/#maemo M4rtinK (~M4rtinK@mail.melf.eu) |
| 09:22.34 | DocScrutinizer05 | feels like having escaped from such kindergarden finally |
| 09:24.42 | freemangordon | Pali: we either have to find the guy who is responsible and pester him or find the login and fix it. |
| 09:26.41 | freemangordon | Pali: BTW it seems noone is responsible for fixing CSSU repo, too |
| 09:27.11 | DocScrutinizer05 | that's merlin1991:maintainer_of_repo |
| 09:27.44 | freemangordon | DocScrutinizer05: last thing I know is that repo is roken, so he can't upload |
| 09:27.51 | freemangordon | broken even |
| 09:28.13 | DocScrutinizer05 | so? |
| 09:28.29 | DocScrutinizer05 | who's going to fix it? |
| 09:28.36 | freemangordon | DocScrutinizer05: exactly :) |
| 09:28.37 | DocScrutinizer05 | maintainer, no? |
| 09:28.48 | freemangordon | no, as I assume maintainer has no root access |
| 09:29.07 | DocScrutinizer05 | so what? |
| 09:29.22 | freemangordon | so he can't fix it |
| 09:29.32 | DocScrutinizer05 | you got a sysop for that, to request for stuff getting done that needs root access |
| 09:29.50 | freemangordon | ok, so I neeed to pester merlin1991, got it :) |
| 09:29.56 | kerio | freemangordon: i assume he's got write access to the repos |
| 09:30.13 | *** join/#maemo pvanhoof (~philip@codeminded.be) |
| 09:30.44 | freemangordon | kerio: afaik there is some problem with permissions. |
| 09:31.04 | DocScrutinizer05 | freemangordon: see? you got it instantly. Others seem not willing to get it |
| 09:31.10 | DocScrutinizer05 | that's why I resigned |
| 09:31.36 | freemangordon | DocScrutinizer05: then keep talking with me only :P |
| 09:31.45 | *** join/#maemo Smily (Smily@89.142.53.57) |
| 09:32.54 | freemangordon | DocScrutinizer05: i guess I should check on wiki for maintainers, no? |
| 09:33.36 | DocScrutinizer05 | I mustn't hand out root perms to everybody on maemo.org. We got a sysop for that who also takes responsibility for keeping the system integrity |
| 09:33.45 | freemangordon | sure |
| 09:33.57 | DocScrutinizer05 | some maintainers don't accept that fact |
| 09:34.11 | freemangordon | my point is - in order to find that sysop, i have to check on wiki, ain;t? |
| 09:34.21 | DocScrutinizer05 | sysop is warfare |
| 09:34.28 | freemangordon | aah, ok |
| 09:35.13 | DocScrutinizer05 | but you shouldn't pester sysop about maintainer stuff. For example warfare has no idea about repos or autobuilder, basically |
| 09:35.23 | freemangordon | got it |
| 09:35.36 | freemangordon | I am just trying to figure out who is who |
| 09:35.37 | DocScrutinizer05 | it needs a request from maintainer who should know what needs to get done, and sysop will do it for them |
| 09:35.46 | freemangordon | :nod: |
| 09:35.47 | kerio | DocScrutinizer05: so it should be "i need `$command` to be run as root on $machine for $reason"? |
| 09:35.59 | freemangordon | kerio: maybe not that formal |
| 09:36.01 | DocScrutinizer05 | yes, exactly |
| 09:36.08 | kerio | it's hard to be unformal when you have to expand variables |
| 09:38.06 | DocScrutinizer05 | jacekowski and woody bitched at me about "do you honestly suggest I shall put up such a request for everything I need to get done, and then wayit 30min or even an hour for it to get processed?" then ragequit |
| 09:38.50 | kerio | well, if they have such an amount of requests maybe they do need more permissions |
| 09:38.55 | kerio | but not *all* permissions! |
| 09:39.33 | DocScrutinizer05 | kerio: I thouhgt same, and tried to use a policy based on cooperation and common sense. This didn't fly |
| 09:39.39 | freemangordon | DocScrutinizer05: I don;t know what that conversation was, but I could imagine. Having a formal request for every nit is a nightmare and contraproductive, I agree |
| 09:40.33 | freemangordon | but I guess a temp rights elevation is always possible if needed |
| 09:42.33 | *** join/#maemo _rd (~rd@p57B489EB.dip0.t-ipconnect.de) |
| 09:42.38 | DocScrutinizer05 | freemangordon: no, it's not. It just requires more discipline and higher competence form maintainers. Like: instead of requesting "please add +x to /local/bin/xyz" maintainer needs to ask for "please add my account to group+we of /local/bin" |
| 09:42.51 | *** join/#maemo Timmy (~quassel@unaffiliated/timmyt) |
| 09:42.57 | Macer | kerio: lol |
| 09:43.02 | DocScrutinizer05 | (no it's not been about nightmare) |
| 09:43.04 | kerio | ? |
| 09:43.09 | *** join/#maemo pvanhoof (~philip@codeminded.be) |
| 09:43.22 | Macer | "i need `$command` to be run as root on $machine for $reason"? |
| 09:44.04 | DocScrutinizer05 | Macer: what? |
| 09:44.30 | Macer | jut thought that was a bit funny :) |
| 09:44.37 | DocScrutinizer05 | Macer: you obviously never worked in a corporate environment |
| 09:44.55 | Macer | ok? |
| 09:45.19 | Macer | it wasn't what he said. it was how he worded it. |
| 09:45.25 | DocScrutinizer05 | usually you don't even have admin permissions of your very own local PC there |
| 09:45.55 | freemangordon | DocScrutinizer05: and I guess FOSS community is a differnt beast |
| 09:45.56 | kerio | natural languages would be better with variable substitution |
| 09:46.09 | Macer | kerio: that it would ;) |
| 09:46.26 | DocScrutinizer05 | now in a corporate environment you have very few problems with accountability. For a FOSS projecr there basically is no accountability |
| 09:46.33 | Macer | kerio: lead with "for" heh |
| 09:47.06 | DocScrutinizer05 | so the less you can allow everybody to have root permissions on everything |
| 09:47.32 | Macer | DocScrutinizer05: is there a reason so many would require root to begin with? |
| 09:47.48 | Macer | i figure most things would be able to be grouped |
| 09:48.05 | DocScrutinizer05 | I thought you could when you educate those who got those permissions about what they may and what they MUST NOT do with them. But that been an epic fail and I'm responsible for that failure |
| 09:48.43 | Macer | heh. oh nooooo. you're playing with fire giving more than a handful of people that sort of control over the system heh |
| 09:48.59 | Macer | especially if one were to go rougue on you |
| 09:49.02 | DocScrutinizer05 | heh it been ~4 people heh |
| 09:49.22 | DocScrutinizer05 | and they had no "control over the system" |
| 09:49.46 | Macer | almost makes you wish you could make like 5 clones of yourself huh? |
| 09:49.49 | DocScrutinizer05 | they had just locally elevated permissions |
| 09:50.02 | kerio | Macer: he already did, notice the name |
| 09:50.04 | Pali | kerio, do you know if there is in maemo extras some package which enabling sudo for user user? |
| 09:50.07 | Macer | lol |
| 09:50.20 | kerio | Pali: there's sudser, but it works awfully |
| 09:50.29 | Pali | what it doing? |
| 09:50.44 | kerio | setting up a password and adding passwordful or passwordless sudo |
| 09:50.48 | Macer | i miss lcuk :-/ used to be comedy hour every time he was here |
| 09:50.53 | DocScrutinizer05 | Pali: edit /etc/sudoers.d/* |
| 09:51.08 | Pali | DocScrutinizer05, I done it 2 years ago :D |
| 09:51.09 | DocScrutinizer05 | add your own plicy, run update-sudoers |
| 09:51.18 | Pali | but I'm asking if there is package which doing it |
| 09:51.34 | DocScrutinizer05 | there are several, one worse than the other |
| 09:51.40 | Pali | now trying to fix sudo/root problem in maemo |
| 09:51.41 | kerio | iirc sudser left my sudoers in an inconsistent state |
| 09:51.50 | kerio | which broke... everything, really |
| 09:52.01 | DocScrutinizer05 | sudser is BS |
| 09:52.06 | DocScrutinizer05 | afaik |
| 09:52.08 | kerio | Pali: ssh root@localhost |
| 09:52.27 | Pali | kerio, that working too |
| 09:52.29 | DocScrutinizer05 | Pali: sudo/root problem? which problem? |
| 09:52.43 | Pali | DocScrutinizer05, sudo gainroot |
| 09:52.50 | DocScrutinizer05 | nobody ever reported about a problem |
| 09:53.14 | Pali | we talked about it more times |
| 09:53.43 | DocScrutinizer05 | yes, and you always refused to deliver any sound rationale why it needs any fixing |
| 09:54.37 | kerio | sudo gainroot works as intended |
| 09:54.37 | DocScrutinizer05 | and particularly how that fixing could be done in a non-intrusive non-breaking-compatibility way |
| 09:54.42 | kerio | if rd mode is enabled, give a root shell |
| 09:55.31 | Pali | but if you have rootsh installed without rd mode it enable it too |
| 09:55.43 | kerio | ah yeah, rootsh is horrendous |
| 09:55.43 | DocScrutinizer05 | no, it doesn't |
| 09:56.00 | DocScrutinizer05 | err, sorry, missed the rootsh part |
| 09:56.03 | *** join/#maemo arcean (~arcean@aacv198.neoplus.adsl.tpnet.pl) |
| 09:56.20 | DocScrutinizer05 | whatever rootsh does, you CAN NOT fix it since it already exists |
| 09:56.35 | kerio | ah indeed |
| 09:56.47 | Pali | I will look into packages which using rootsh |
| 09:56.57 | DocScrutinizer05 | SO WHAT? |
| 09:57.26 | Pali | and fix using stupid rootsh calls |
| 09:57.32 | DocScrutinizer05 | you can't fix a privilege escalation done in XY0.1 by publishing XY0.2 |
| 09:57.47 | Pali | then we can add password for user and root |
| 09:57.58 | DocScrutinizer05 | unless you forbid downgrading like in HARM |
| 09:58.30 | kerio | >implying local privilege escalation is even remotely (sic!) fixable in fremantle |
| 09:58.37 | Pali | DocScrutinizer05, look why package XYZ need calling gainroot, fix to use directly sudo and add sudoers.d config file |
| 09:58.59 | DocScrutinizer05 | sure, sane thing |
| 09:59.14 | Pali | then it is possible to ask password before enabling root shell (via gainroot or other script) |
| 09:59.23 | DocScrutinizer05 | will not make rootsh-v${current} vanish |
| 10:00.16 | DocScrutinizer05 | you can publish a new package "sane-rootsh" that conflicts with rootsh even |
| 10:00.33 | DocScrutinizer05 | but messing around with original rootsh pkg won't help anything |
| 10:02.56 | DocScrutinizer05 | even if you did, there are still a dozen other fsckdup pkgs like sudser and easyroot or whatsthename that do even worse shit than rootsh pkg does |
| 10:12.34 | DocScrutinizer05 | so honestly, I thin best approach is to create a new project/package "secure sane sudo (formerly know as rootsh)" and make it conflict in dependencies with rootsh and and all other known-borked root access packages |
| 10:12.41 | DocScrutinizer05 | think* |
| 10:13.12 | DocScrutinizer05 | users are free to install it, and see what it gives them |
| 10:13.48 | DocScrutinizer05 | they will find all the broken apps that depend on rootsh getting removed as conflicting dependencies. |
| 10:14.09 | DocScrutinizer05 | unless those apps have been updated to not depend on rootsh anymore |
| 10:14.36 | DocScrutinizer05 | clean easy-to-ggrok straight approach |
| 10:15.35 | DocScrutinizer05 | I'd be willing to support it any way me/council/techstaff can (and may) do |
| 10:15.45 | DocScrutinizer05 | like helping with promotion |
| 10:15.56 | *** join/#maemo _rd (~rd@p57B489EB.dip0.t-ipconnect.de) |
| 10:16.41 | DocScrutinizer05 | grep across whole repo for particular keystrings like "sudo" in and program text |
| 10:16.56 | DocScrutinizer05 | any* |
| 10:20.18 | _rd | Is there a good way to track which fremantle packages see updates in extras? |
| 10:20.41 | DocScrutinizer05 | define "see" |
| 10:22.51 | _rd | Well...on my n900 I just see updates on cssu, modrana, and navit. Navit I do myself. |
| 10:23.34 | _rd | I am wondering, if there are any ohter interesting areas work goes in, which I simply do not see...because I have not installed the apps. |
| 10:23.59 | _rd | Something like a log of uploaded packages would be nice |
| 10:24.47 | _rd | I could download Packages files and diff them every few days, but there might be a more direct way |
| 10:25.01 | DocScrutinizer05 | so you're asking for a list of maemo(-devel?) packages with mtime newer err... 1 week? |
| 10:26.37 | *** part/#maemo Timmy (~quassel@unaffiliated/timmyt) |
| 10:26.40 | DocScrutinizer05 | _rd: you don't need to download them every few days. Since HAM is doing that for you, only when there are changes, usually once a day, per default |
| 10:26.44 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 10:28.03 | DocScrutinizer05 | so all you'd need to do is safe away old packages.gz and if there appears a new version on your device. you do a diff to old version you saved and then save new version to the backup location |
| 10:28.17 | DocScrutinizer05 | s/safe/save/ |
| 10:28.49 | _rd | yes, but HAM only tells me on updated packages which changed. |
| 10:28.58 | _rd | sorry.... |
| 10:28.59 | DocScrutinizer05 | so what? |
| 10:29.18 | _rd | HAM only tells me on installed packages which updated |
| 10:29.22 | DocScrutinizer05 | did I say you should ask HAM about new packages, or did I suggest to do a diff? |
| 10:29.50 | _rd | I would like to see a list of all updates, also for packages which I have not (yet?) installed. |
| 10:30.01 | _rd | ....aah. |
| 10:30.04 | kerio | _rd: http://maemo.org/packages/repository/latest/fremantle_extras-devel_free_armel/all/ |
| 10:30.07 | DocScrutinizer05 | so all you'd need to do is save away old packages.gz and if there appears a new version on your device. you do a diff to old version you saved and then save new version to the backup location |
| 10:30.21 | _rd | you say I could use the Package file, which is already on the n900. |
| 10:30.23 | _rd | understood. |
| 10:30.39 | _rd | If I do that from a PC, downloading directly might be more convenient. |
| 10:30.49 | DocScrutinizer05 | yeah |
| 10:30.54 | DocScrutinizer05 | obviously |
| 10:31.31 | _rd | kerio: many thanks, that is what I was looking for. |
| 10:31.37 | _rd | ....actually it is much better :-) |
| 10:32.21 | DocScrutinizer05 | doesn't have packages that are not in "user" probably |
| 10:33.15 | DocScrutinizer05 | also seems to not show any date when those "latest" actually got updated |
| 10:34.09 | amospalla | do you know of any doc or text to guide the installation of rescueos ? |
| 10:34.26 | kerio | amospalla: short answer: don't do it |
| 10:34.41 | kerio | it's unsupported, and not meant to work |
| 10:35.15 | kerio | NIN101: have you considered putting something that can charge from a usb host instead of the wallcharger? |
| 10:36.18 | amospalla | kerio: oh, it was on rescueos url, am I supposed to use flasher everytime I use it, so it's not meant to be copied in any way into n900 |
| 10:36.45 | kerio | that's the gist of it, yes |
| 10:37.03 | kerio | uboot *can* boot it on-device, and it works fine |
| 10:37.12 | *** join/#maemo florian (~fuchs@sign-4db60eaf.pool.mediaWays.net) |
| 10:37.13 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 10:37.16 | kerio | but configuring uboot isn't that easy |
| 10:37.37 | Pali | somebody who has time should write wiki page about uboot bootmenu :-) |
| 10:40.11 | amospalla | kerio: that's why I was asking, about installation on the device itself, but I prefer not to deal with boot, I do not want to break anything |
| 10:40.14 | amospalla | thanks |
| 10:40.33 | amospalla | it's ok if I can boot it with cable |
| 10:40.47 | amospalla | in fact, it is a great idea make it that way |
| 10:40.55 | kerio | ~rescueOS |
| 10:40.55 | infobot | from memory, rescue-os is http://206.253.166.96/N900/rescueOS/ |
| 10:42.10 | DocScrutinizer05 | honestly rescueOS is a poor choice for any OS to get actually installed on eMMC or uSD to boot it per uBoot from there. It's simply not meant to get used this way |
| 10:42.40 | kerio | found it damn useful more than once |
| 10:42.54 | kerio | yes, they were all situations where i was literally sitting at a computer |
| 10:42.57 | DocScrutinizer05 | there are quite a number of better choices |
| 10:42.59 | kerio | like most of the time in my life |
| 10:43.23 | kerio | but plugging in a cable and typing a command is still more hassle than selecting a menu entry :) |
| 10:43.25 | *** join/#maemo jpinx (~jpinx@unaffiliated/jpinx) |
| 10:44.38 | NIN101 | kerio: yeah, considered, not done yet... |
| 10:44.59 | DocScrutinizer05 | ideal choice was a auxiliary maemo installed to a separate partition, with support to mount the main OS partitions to /original-maemo/* |
| 10:45.01 | kerio | DocScrutinizer05: are there "official" charge scripts? |
| 10:45.12 | amospalla | it is not something I'm usually using, it's ok dealing with cable when I have to use that |
| 10:45.38 | kerio | DocScrutinizer05: that's not ideal at all, having to load h-d and all the other crap when you just need a terminal to run a command consumes time |
| 10:45.41 | amospalla | bootmenu did the job sometimes, but it is not the same |
| 10:45.44 | DocScrutinizer05 | kerio: well, on maemo.cloud-7.de and ShadowJK's server it is as official as it gets |
| 10:45.47 | NIN101 | and yes, rescueOS is not meant to be preinstalled somewhere, only booted when needed. |
| 10:46.38 | amospalla | with bootmenu I have some kind of rescue shell, but have to do it through cable network and ssh, because using the device itself does not work correctly |
| 10:46.54 | amospalla | and I doubt it does charge |
| 10:48.24 | DocScrutinizer05 | http://maemo.cloud-7.de/maemo5/patches_n_tools/charge21_500mA-USBlimit__UNTESTED.sh should not conflict with server USBhost charging |
| 10:48.30 | DocScrutinizer05 | for the limit to 500 |
| 10:49.16 | kerio | NIN101: you could also try the bq2415x-charger and bq27x00-battery modules |
| 10:49.26 | kerio | for automagical everything |
| 10:49.44 | Pali | DocScrutinizer05, correct me if I'm wrong, but isnt max current for usb2.0 only 100mA until enumeration is done? |
| 10:49.59 | DocScrutinizer05 | Pali: per spec yes |
| 10:50.33 | DocScrutinizer05 | but those PCs that enforce that also fail to power any fan or mugwarmer or kbd-light |
| 10:50.47 | NIN101 | yeah I pondered about including the "UNTESTED" 500ma script, but I can't risk to test anything of this kind as I have only one N900 and I am not very experienced at this topic in general. |
| 10:50.50 | DocScrutinizer05 | well, maybe kbd-light doesn't need >100 |
| 10:51.19 | kerio | 1) make initrd with kernel-power modules |
| 10:51.25 | DocScrutinizer05 | NIN101: it's kinda tested meanwhile. And for sure it's not dangerous in any kind |
| 10:51.29 | kerio | 2) modprobe bq2415x-charger |
| 10:51.42 | DocScrutinizer05 | kerio: bwahahaha |
| 10:52.32 | kerio | it can't be too hard to port the bq24k module to 2.6.37 |
| 10:54.26 | *** join/#maemo _rd (~rd@p57B489EB.dip0.t-ipconnect.de) |
| 10:54.29 | kerio | Pali: what happens to the bq24k module if there's no usb gadget module to do the detection? |
| 10:54.43 | kerio | does it do nothing at all? or does it draw the 100mA? |
| 10:54.53 | _rd | which browsers do you use on the n900? Built-in microb? |
| 10:55.01 | DocScrutinizer05 | kerio: wtf would anybody want to do that, for rescueOS? |
| 10:55.24 | Pali | kerio, it will be in none/off state |
| 10:55.59 | Pali | in maemo 2.6.28 kernel is glue between musb and bq27x00_battery which is stored in board-rx51-peripherals.c file |
| 10:56.42 | Pali | s/bq27x00_battery/bq2415x_charger/ |
| 10:57.07 | Pali | in upstream kernel is (or will be) direct calls between isp1704_charger (which doing charger detection) and bq2415x_charger |
| 11:01.45 | _rd | which browsers do you use on the n900? Built-in microb? |
| 11:03.29 | *** join/#maemo disco_stu_droid (~wrt54gl@190.211.81.139) |
| 11:05.31 | *** join/#maemo kolp_ (~quassel@212.255.229.148) |
| 11:05.45 | *** join/#maemo arcean (~arcean@aacv198.neoplus.adsl.tpnet.pl) |
| 11:06.09 | sixwheeledbeast | _rd: select one they all have there pros and cons, I use Opera 11 many use MicroB with Flash tweak. |
| 11:06.36 | *** join/#maemo robink_ (~quassel@unaffilated/robink) |
| 11:06.56 | *** join/#maemo Sc0rpius (~naikel@190.79.197.57) |
| 11:06.57 | *** join/#maemo Raimu-Z (~raimu@kameli.net) |
| 11:07.13 | *** join/#maemo till (till@vispillo.org) |
| 11:07.28 | *** join/#maemo vblazquez (~vic@32.9.77.188.dynamic.jazztel.es) |
| 11:08.01 | *** join/#maemo sirdancealot (~sirdancea@98.82.broadband5.iol.cz) |
| 11:08.09 | *** join/#maemo divVerent (~divVerent@xonotic/core-team/divVerent) |
| 11:11.04 | _rd | you think of tweakflashver as "Flash tweak" ? |
| 11:12.19 | DocScrutinizer05 | Pali: those direct calls will fuckup hostmode and most likely even USB at large |
| 11:12.24 | sixwheeledbeast | yep, hopefully alopex will rule the browser space soon... |
| 11:13.30 | DocScrutinizer05 | Pali: since, to detect charger, 170x needs to reconfigure the datalines, and that will brwak adat transmissions |
| 11:13.36 | DocScrutinizer05 | break* |
| 11:13.46 | DocScrutinizer05 | break data* even |
| 11:14.12 | Pali | DocScrutinizer05, I have patches for musb and that 1704 driver to (semi)-fix that in upstream |
| 11:14.25 | Pali | but there is bigger problem: in upstream host mode not working |
| 11:14.57 | Pali | there is code for force host mode, but it cause instant kernel panic |
| 11:15.38 | DocScrutinizer05 | well, you could argue a botch liike N900 hostmode has no place in upstream anyway |
| 11:15.55 | Pali | so I rather fix charger detection which do not break peripheral usb mode for upstream kernel |
| 11:16.02 | DocScrutinizer05 | for sure it's colliding with any sane USB code in upstream |
| 11:16.28 | DocScrutinizer05 | hmm, good luck with that |
| 11:16.32 | DocScrutinizer05 | it can't get done |
| 11:16.45 | Pali | DocScrutinizer05, our hostmode code in n900 kernel is adding code for choosing speed via testmode musb param (or how it is called) |
| 11:16.59 | Pali | access to that register is in upstream kernel via debugfs |
| 11:17.17 | Pali | but cat /sys/debug/.../that_file cause kernel panic on n900 |
| 11:17.32 | DocScrutinizer05 | *shrug* |
| 11:17.50 | Pali | but needed code for force host mode for n900 is in upstream |
| 11:18.01 | DocScrutinizer05 | I'm honestly deprecating to try and upstream H-E-N hostmode kernel patches |
| 11:18.09 | Pali | api is different, not using /proc, but code is here |
| 11:18.26 | DocScrutinizer05 | it's absolutely nonsensical |
| 11:19.57 | DocScrutinizer05 | and you *can not* fix the conflict between charger detection and data-transmission in kernel space, since 1707 has no idea if there is a data transmission happening resp a session established |
| 11:20.56 | DocScrutinizer05 | so, to "fix2 that, you'd need to add metric tons of useless cruft to kernel drivers, to make assumptions about state of USB |
| 11:22.05 | DocScrutinizer05 | I explained all that during hostmode development, and then again several times after that to KP devels |
| 11:27.35 | *** join/#maemo udovdh (~udovdh@pindarots.xs4all.nl) |
| 11:28.09 | DocScrutinizer05 | paul fertser (coder of original final version of hostmode kernel) discussed that with me when we developed those patches. He's a die-hard FOSS and upstream and debian-only guy, and he agreed that N900 hostmode *must not* go to upstream, since it's a terrible botch that can't get done right and also it's useless in upstream since there never agin will be a similar hardware that could re-use that botch |
| 11:29.25 | DocScrutinizer05 | so bringing it upstream is a PITA and a bloat at best, but most probably can't get done at all, in a compliant way |
| 11:30.33 | DocScrutinizer05 | or let me put it this way: IF it would've been possible and reasonable to bring H-E-N kernel upstream, it would've been there since very beginning |
| 11:31.30 | amospalla | huh, after 4 months without upgrade, apt-get upgrade wants to upgrade 47 packages (some are hildon*, pulseaudio*), is this expected? |
| 11:31.32 | DocScrutinizer05 | and Paul is a rather gifted and experienced kernel developer who knows his shit |
| 11:32.00 | DocScrutinizer05 | amospalla: maybe not |
| 11:32.13 | amospalla | I'm using cssu thumb |
| 11:32.37 | amospalla | so, until there does not appear a new cssu update, I should not touch that |
| 11:32.56 | DocScrutinizer05 | guys are messing with repo atm, we seen some hashsum errors sneaking in again, and most likely it's best to _not_ update for a while |
| 11:33.24 | amospalla | ok, understood, thanks DocScrutinizer05 |
| 11:33.36 | DocScrutinizer05 | meh, cssu-thumb, that's again a completely different story |
| 11:33.44 | DocScrutinizer05 | ask freemangordon |
| 11:35.41 | Pali | DocScrutinizer05, charger detection is called when charger is connected, isp driver enabling musb after detection is complete |
| 11:36.13 | DocScrutinizer05 | yes, but then again you get layering violations that you can't upstream |
| 11:36.23 | Pali | this is already in upstream |
| 11:36.46 | DocScrutinizer05 | yeah, and it's not working, according to what you said |
| 11:37.04 | Pali | not working is other part |
| 11:37.25 | Pali | because musb driver started using omap mailbox api instead some old |
| 11:37.34 | Pali | which still using isp driver |
| 11:37.52 | Pali | but musb or isp can be upgraded to use new "notify" api |
| 11:39.36 | Pali | I created patch which add optional hotplug/removable file_storeage gadget to g_nokia.ko |
| 11:39.58 | Pali | so you do not want to switch and load/unload g_file_storage and g_nokia |
| 11:40.17 | Pali | you can export what you want (only file_storage or only usb network or both) |
| 11:40.29 | Pali | but usb maintainer rejected my patch |
| 11:40.49 | Pali | because only *nokia* can device what to do with their g_nokia.ko driver in upstream |
| 11:41.09 | *** join/#maemo NeutrinoPower (~neutrino@HSI-KBW-078-042-162-195.hsi3.kabel-badenwuerttemberg.de) |
| 11:41.46 | DocScrutinizer05 | see? |
| 11:41.49 | Pali | and he did not understand that nokia does not care about their linux driver in upstream anymore and also they are not working on n900 anymore |
| 11:42.21 | Pali | so I do not know if something can be patched for nokia n900 support... |
| 11:45.31 | *** join/#maemo frafl (~Thunderbi@e178066027.adsl.alicedsl.de) |
| 11:47.20 | *** join/#maemo sq-one (~sq-one@p57977681.dip.t-dialin.net) |
| 11:48.11 | DocScrutinizer05 | Pali: I honestly don't feel like going thru all that again. I explained we discussed *all* that during _several_ weeks when developing H-E-N hostmode kernel patches. And the guy who been most die-hard radical upsteam/debian-only and almost refused to touch maemo at all _because_ it wasn't completely upstream compliant, this guy concluded that his own patches can't go upstream and there is not even any rationale why they should. We found |
| 11:48.12 | DocScrutinizer05 | layering problems of all sorts, and there were other more general argumants as well that suggested hostmode botch MUST NOT go upstream and CAN NOT go upstream, since on one edge you always run into "doesn't work with standard kernels" or "doesn't make sense at all" |
| 11:48.43 | DocScrutinizer05 | I'm honestly not going to discuss all this again with you, now that you think you can do better than we did 3 or 4 years ago |
| 11:49.38 | Pali | DocScrutinizer05, upstreaming our host mode patches from 2.6.28 kernel are not needed |
| 11:49.52 | Pali | I think that all needed code is already in upstream kernel |
| 11:50.08 | DocScrutinizer05 | think what you like |
| 11:53.50 | *** join/#maemo tx0h (~tx@f052050055.adsl.alicedsl.de) |
| 11:56.24 | *** join/#maemo mvp (~mvp@port463.ds1-abc.adsl.cybercity.dk) |
| 12:01.44 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 12:07.38 | *** join/#maemo WielkiTost (~dos@unaffiliated/dos1) |
| 12:32.16 | *** join/#maemo rcg (~rcg@2a02:908:e252:e101:9094:b4ec:40bb:1000) |
| 12:35.45 | *** join/#maemo jben1 (~jben@alpha.jben.info) |
| 12:46.36 | *** join/#maemo RiD (GhostRider@2.83.34.147) |
| 12:46.50 | *** part/#maemo Aoyagi (~opera@222.18.broadband15.iol.cz) |
| 12:51.55 | *** join/#maemo Aoyagi (~opera@222.18.broadband15.iol.cz) |
| 12:53.04 | *** join/#maemo Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 13:01.36 | ShadowJK | 196M free on MyDocs :o |
| 13:15.39 | *** join/#maemo pvanhoof (~philip@codeminded.be) |
| 13:16.56 | *** join/#maemo Hurrian (~Hurrian@121.54.2.104) |
| 13:34.34 | *** join/#maemo Creteil (~administr@62-193-60-146.stella-net.net) |
| 13:34.38 | Creteil | hi all |
| 13:34.52 | Creteil | someone know what is the username of jacekowski on TMO ? |
| 13:35.03 | *** join/#maemo Timmy (~quassel@unaffiliated/timmyt) |
| 13:35.43 | Creteil | I have to put credits to him for the help he provide during my last package build on autobuilder .... |
| 13:36.16 | Timmy | is there any program/application for linux to manage the n900? something similar to the nokia pc suite. the only thing i want to do is to send and receive sms through my computer |
| 13:36.56 | amospalla | Timmy: there is some command line utility, to do that |
| 13:37.15 | Timmy | like what? |
| 13:38.25 | amospalla | first result on google "n900 sms send": http://talk.maemo.org/showthread.php?t=69661 |
| 13:40.45 | Skry | you could try gammu, no idea if it works with N900 but have used it with few other Nokias and huawei dongle successfylly |
| 13:40.56 | *** part/#maemo Creteil (~administr@62-193-60-146.stella-net.net) |
| 13:44.29 | *** join/#maemo Muelli (~muelli@port-33182.pppoe.wtnet.de) |
| 13:45.05 | DocScrutinizer05 | Pali: I talked with Paul and it seems he's still interested in upstreaming hostmode patches. He might give a helping hand, now that I convinced him that *kernel* on N900 is working properly, even the upstream one |
| 13:45.57 | Pali | DocScrutinizer05, nice to hear :-) |
| 13:46.39 | Pali | DocScrutinizer05, here is 3.8 kernel with n900 patches: https://gitorious.org/linux-n900/linux-n900 |
| 13:46.49 | DocScrutinizer05 | he also denied that there were any insurmountable obstacles with it |
| 13:46.51 | Pali | some of them will be included in 3.9/3.10 |
| 13:47.24 | DocScrutinizer05 | so probably I told BS, sorry |
| 13:47.32 | Skry | Pali: btw I rebased your patches to 3.9-rc1, boots :) |
| 13:47.54 | Pali | Skry, I started cleaning my patches |
| 13:48.05 | Skry | nice |
| 13:48.15 | Pali | I will push new version of cleaned patches when I finish it |
| 13:48.30 | Skry | ok, could you ping me when that happens? |
| 13:49.25 | *** join/#maemo _rd (~rd@p57B489EB.dip0.t-ipconnect.de) |
| 13:49.30 | Skry | Pali: did you have working audio? I get insta-crash with both 3.8 and 3.9. I was thinking if our configs are different and would that be the reason-- |
| 13:49.57 | Pali | audio not working... |
| 13:50.15 | Pali | maemo not crashing, but no sound |
| 13:50.36 | Skry | yeah, too bad. that's currently the only thing keeping me from updating arch packaging to 3.9 :\ |
| 13:55.55 | *** join/#maemo hardaker (~hardaker@mail.hardakers.net) |
| 13:59.01 | *** join/#maemo kolp (~quassel@212.255.229.148) |
| 14:09.43 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 14:35.37 | *** join/#maemo arcean_ (~arcean@aaem235.neoplus.adsl.tpnet.pl) |
| 14:56.49 | *** join/#maemo Timmy (~quassel@unaffiliated/timmyt) |
| 15:03.23 | *** join/#maemo kaawee_ (~user@port-92-206-53-106.dynamic.qsc.de) |
| 15:21.19 | *** join/#maemo _rd (~rd@p57B489EB.dip0.t-ipconnect.de) |
| 15:49.48 | *** join/#maemo at1as (~at1as@ppp-69-214-7-184.dsl.klmzmi.ameritech.net) |
| 16:00.48 | *** join/#maemo thauta_ (thautako@tuomi.oulu.fi) |
| 16:01.01 | *** part/#maemo thauta_ (thautako@tuomi.oulu.fi) |
| 16:12.06 | *** join/#maemo MikaT (~mtapoja@projects.sse.fi) |
| 16:21.59 | *** join/#maemo keesj (~keesj@dellpc132.few.vu.nl) |
| 16:24.55 | Macer | hm |
| 16:25.06 | Macer | i'm a bit confused as to how phones advertise their freqs nowadays |
| 16:25.32 | Macer | quad band GSM (850MHz, 900MHz, 1800MHz, 1900MHz) |
| 16:26.16 | Macer | is t-mobile US now 1800? |
| 16:28.54 | *** join/#maemo FReaper-PC (~honoo-pc@203.106.65.1) |
| 16:30.54 | *** join/#maemo florian (~fuchs@sign-4db60eaf.pool.mediaWays.net) |
| 16:30.55 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 16:42.30 | *** join/#maemo _rd (~rd@p57B489EB.dip0.t-ipconnect.de) |
| 16:42.45 | *** join/#maemo rcg (~rcg@2a02:908:e252:e101:9094:b4ec:40bb:1000) |
| 16:49.14 | *** join/#maemo rd_ (~rd@p57B48044.dip0.t-ipconnect.de) |
| 17:01.07 | ShadowJK | 1800 is used in europe |
| 17:01.39 | ShadowJK | basically, 900 became full in cities, so 1800 was added |
| 17:03.16 | ShadowJK | tmobile is 850/1900 or something, simultaneously |
| 17:03.27 | ShadowJK | ie one is used for transmit and the other for receive |
| 17:04.10 | sixwheeledbeast | Macer: https://en.wikipedia.org/wiki/GSM_frequency_bands |
| 17:04.24 | Macer | i looked at that |
| 17:04.30 | Macer | and it makes 0 sense as well ;) |
| 17:04.38 | Macer | freqs are listed twice |
| 17:05.12 | sixwheeledbeast | what do you mean? |
| 17:05.16 | Macer | like take 1900MHz.. according toe wikipedia it is an edge freq OR a UMTS/HSPA/HSPA+ freq |
| 17:05.21 | Macer | so does that depend on the device? |
| 17:05.31 | Macer | plus doesn't it use 1700 for uplink and 1900 for downlink? |
| 17:05.38 | Macer | that is where i get confused |
| 17:06.00 | Macer | http://www.amazon.com/G13-Black-Quad-band-Watch-UNLOCKED/dp/B0064U47HC/ref=pd_sim_cps_2 |
| 17:06.04 | Macer | i was looking at that thing |
| 17:06.07 | Macer | looks kind of neat |
| 17:07.12 | Macer | Unlocked, quad-band GSM 850/900/1800/1900 MHz |
| 17:07.25 | Macer | and what uses that 1800MHz freq? is that japan or something? |
| 17:08.29 | sixwheeledbeast | "the quad-band phone, also known as a world phone, supporting all four major GSM bands, allowing for global use" except non-gsm like japan |
| 17:08.34 | ShadowJK | In europe UMTS and GSM/edge are both on 900MHz, though obviously the operators themselves have allocated part of their 900MHz holding for 3g and some for 2g |
| 17:09.06 | ShadowJK | 1800 remains 2g only, but may be opened up to have both 2g and lte |
| 17:09.22 | ShadowJK | and 2100 is umts/lte shared, I think |
| 17:10.19 | Macer | sixwheeledbeast: so that means regardless of carrier it should support GSM 3G? |
| 17:10.36 | Macer | or does it just mean you can talk on it but 3G or faster maybe not? |
| 17:11.43 | ShadowJK | that device has no 3g. |
| 17:13.13 | sixwheeledbeast | Macer: depends on the country |
| 17:13.58 | ShadowJK | No, I'm pretty sure as the device doesn't have 3g/umts radio, 3g will not work anywhere, regardless of country :) |
| 17:14.14 | Macer | ShadowJK: but the same goes for actual phones which do have the 3G modems |
| 17:14.32 | Macer | the listing for quad bands is usually the same with the oddball 1700MHz being here and there |
| 17:14.54 | sixwheeledbeast | sorry no not that device as ShadowJK i mean 3G devices |
| 17:15.15 | sixwheeledbeast | 1700 is japan AFAIK |
| 17:16.00 | Macer | Unlocked quad-band GSM cell phone compatible with 850/900/1800/1900 frequencies and US/International 3G compatibility via 850/900/1700/1900/2100 UMTS/HSDPA plus GPRS/EDGE capabilities |
| 17:16.22 | Macer | i'm pretty sure tmobile us uses 1700 for hspa+ |
| 17:16.28 | Macer | that's an e7 |
| 17:16.59 | sixwheeledbeast | https://en.wikipedia.org/wiki/UMTS_frequency_bands |
| 17:17.35 | ShadowJK | ooh pentaband umts |
| 17:17.57 | sixwheeledbeast | quad band will normally be 850/900/1800/1900 to cover most of the world. |
| 17:18.18 | *** join/#maemo Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr) |
| 17:18.51 | Macer | Band II (W-CDMA 1900) in North America and South America (ITU Region 2). |
| 17:18.55 | Macer | Band IV (W-CDMA 1700 or Advanced Wireless Services) in the United States (T-Mobile USA), Canada (WIND Mobile, Mobilicity, Vidéotron) and Chile (VTR Movil, Nextel Chile) |
| 17:19.08 | Macer | points at 1700 and t-mobile usa |
| 17:19.25 | Macer | i believe tmob calls that the AWS band |
| 17:20.38 | Macer | they seriously need to make a simpler way of doing this :) |
| 17:20.57 | Macer | ShadowJK: yeah. e7 supports everything heh |
| 17:21.04 | Macer | i honestly just got it for the qwerty tho |
| 17:22.21 | Macer | http://maemo.org/community/brainstorm/view/850-1900_mhz_frequency_support/ |
| 17:22.24 | Macer | oldie but goodie |
| 17:23.41 | *** join/#maemo Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr) |
| 17:24.48 | *** join/#maemo Timmy (~quassel@unaffiliated/timmyt) |
| 17:26.35 | Macer | my point being that the n900 doesn't support the 1900MHz freq? |
| 17:26.36 | *** join/#maemo tg (~irc@2001:738:2001:2078:0:215:11:82) |
| 17:27.23 | Macer | http://www.nokia.com/gb-en/products/phone/n900/specifications/ |
| 17:27.40 | Macer | yet in its listed freq bands.... it has it listed.. it just doesn't support it for data :) |
| 17:28.12 | Macer | am i the only one not grasping how overly complicated these bands are ? heh |
| 17:29.40 | Macer | and... marina harisson is kind of cute |
| 17:30.56 | sixwheeledbeast | N900 = quad band for GSM and three band for UMTS. No 1900 for data, from what I gather. |
| 17:34.36 | ShadowJK | Well data on gsm on 1900 |
| 17:35.28 | sixwheeledbeast | yes, sorry 3G data. |
| 17:38.24 | ShadowJK | And of course, support for 2g on 1900 is useless for talking to a 3g tower on 1900 :) |
| 17:43.51 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 17:49.06 | *** join/#maemo dRbiG (drbig@unhallowed.pl) |
| 17:49.13 | DocScrutinizer05 | there's no specific "data" capability for any band |
| 17:50.12 | DocScrutinizer05 | either the modem can use a band, or it can't. If the data transferred is GSM-codecvoice data or http:// browser data is relatively irrelevant for the modem |
| 17:51.37 | DocScrutinizer05 | and yes, the problem with N900 in USA been that it doesn't support 3G/UMTS on a band that's originally meant to be 2G/GSM |
| 17:54.46 | *** join/#maemo guerby (~guerby@nc10d-ipv6.tetaneutral.net) |
| 18:02.51 | *** join/#maemo hardaker (~hardaker@mail.hardakers.net) |
| 18:21.56 | *** join/#maemo sunny_s (~sunny_s@86.57.254.135) |
| 18:23.37 | *** join/#maemo bennypr0fane (~ben@81.16.106.32) |
| 18:24.31 | bennypr0fane | what is the quickest/easiest way to copy-paste a long filepath in Maemo? |
| 18:25.58 | sixwheeledbeast | copy and paste in what? Terminal? |
| 18:26.27 | bennypr0fane | yes, into terminal |
| 18:26.49 | bennypr0fane | e.g. I have a .deb that I want to dpkg |
| 18:27.02 | bennypr0fane | and its path+filename are really long |
| 18:27.29 | bennypr0fane | how would you copy-paste that path into terminal? |
| 18:27.37 | *** join/#maemo Guest50382 (~rd@p57B48044.dip0.t-ipconnect.de) |
| 18:27.58 | sixwheeledbeast | copy it onto the clipboard then paste using the top menu in XTerm |
| 18:28.33 | bennypr0fane | <PROTECTED> |
| 18:28.38 | bennypr0fane | same procedure here? |
| 18:28.55 | bennypr0fane | I tried that before, didn't work |
| 18:29.00 | bennypr0fane | nothing happened |
| 18:29.20 | sixwheeledbeast | text or whole file? |
| 18:29.41 | bennypr0fane | do you copy it from Maemo stock file manger, or another one? |
| 18:29.49 | bennypr0fane | whole file |
| 18:30.16 | bennypr0fane | I mean if you copy just the file name, you still have to type the path first |
| 18:31.38 | bennypr0fane | and a different issue, apt-get -f install suggests to remove kernel-power-flasher, I wonder if I should do that? won't this touch the kernel itself? |
| 18:32.38 | sixwheeledbeast | I use hamsterfiler to copy full locations, if that's what you mean. |
| 18:34.35 | bennypr0fane | ok. how exactly in hamsterfiler? in Maemo stock fm, if you try to copy sth., you immediately have to specify where to copy it to. If you don't, I think it's not kept on the clipboard |
| 18:35.36 | bennypr0fane | I'd have to install Hamsterfiler. need to resolve this apt-get issue though bfore I can install anything |
| 18:36.15 | *** join/#maemo RiD2 (RiD@bl22-146-178.dsl.telepac.pt) |
| 18:38.12 | *** join/#maemo jpinx (~jpinx@unaffiliated/jpinx) |
| 18:43.00 | sixwheeledbeast | it hamster you can select the location text at the top of the page, highlight and copy it to clipboard |
| 18:43.09 | sixwheeledbeast | s/it/in/ |
| 18:44.55 | *** join/#maemo otep_ (~quassel@AP-203.167.4.11.sysads.com) |
| 18:46.09 | bennypr0fane | my HAM is kinda broken, it won't list application catalogues |
| 18:46.23 | bennypr0fane | just empty frame |
| 18:48.13 | sixwheeledbeast | patience, close all and wait. |
| 18:48.38 | bennypr0fane | hamsterfiler seems to be all the rage now. it's better than filebox, isn't it? |
| 18:50.15 | sixwheeledbeast | I think so yes, also the dev is still supporting it. |
| 18:50.36 | sixwheeledbeast | it works a bit different to filebox but you get used to it. |
| 18:51.38 | bennypr0fane | actually I've never quite gotten used to Filebox |
| 18:52.34 | bennypr0fane | so I hope this one'll come more naturally to me |
| 18:52.57 | sixwheeledbeast | the save last location option is very useful |
| 18:55.37 | sixwheeledbeast | also other features like grid view, fullscreen mode, open with... |
| 18:57.10 | *** join/#maemo internetishard (~root@c-98-210-156-199.hsd1.ca.comcast.net) |
| 18:57.19 | sixwheeledbeast | just started using bookmarks option too |
| 18:57.33 | internetishard | any idea where the passwords are stored for accounts on the n900? |
| 18:57.38 | internetishard | Are they in plaintext? |
| 19:12.54 | *** join/#maemo arcean (~Tomek@apn-46-76-221-129.dynamic.gprs.plus.pl) |
| 19:27.36 | *** join/#maemo sardini (~halXI@2a01:e35:1386:4120:41e3:9cb2:d4d9:463d) |
| 19:27.39 | sardini | hi, |
| 19:30.55 | *** join/#maemo bef0rd (~bef0rd@unaffiliated/beford) |
| 19:37.11 | *** join/#maemo gantenbein (~gantenbei@79.165.56.123) |
| 19:40.36 | *** join/#maemo hardaker (~hardaker@mail.hardakers.net) |
| 19:40.38 | kerio | internetishard: IM account? |
| 19:40.41 | RiD | internetishard signons.sqlite from .mozilla/microb/ i think |
| 19:40.43 | kerio | they must be saved in plaintext |
| 19:40.49 | RiD | for microb that is* |
| 19:41.29 | *** join/#maemo shamus (~shmaus@ip-206-192-195-49.marylandheights.ip.cablemo.net) |
| 19:42.07 | RiD | the ones from microb are encrypted |
| 19:43.20 | *** join/#maemo sunny_s (~sunny_s@86.57.254.135) |
| 19:43.48 | *** join/#maemo pvanhoof (~philip@codeminded.be) |
| 19:45.14 | *** join/#maemo hardaker (~hardaker@mail.hardakers.net) |
| 19:48.13 | *** join/#maemo mvp (~mvp@port463.ds1-abc.adsl.cybercity.dk) |
| 19:50.20 | *** join/#maemo SmilyOrg (Smily@BSN-142-190-112.dial-up.dsl.siol.net) |
| 19:53.52 | *** join/#maemo Guest50382 (~rd@p57B48044.dip0.t-ipconnect.de) |
| 19:55.48 | *** join/#maemo scoobertron (~tom@93.186.157.52) |
| 20:03.12 | *** join/#maemo messerting (~messertin@cm-84.211.113.209.getinternet.no) |
| 20:08.22 | *** join/#maemo hardaker (~hardaker@mail.hardakers.net) |
| 20:12.39 | *** join/#maemo luf (~luf@ip-94-112-59-161.net.upcbroadband.cz) |
| 20:14.31 | *** join/#maemo bef0rd (~bef0rd@unaffiliated/beford) |
| 20:23.07 | *** join/#maemo scoobert1on (~tom@93.186.157.52) |
| 20:27.09 | *** join/#maemo e-yes (~e-yes@94.45.165.112) |
| 20:34.19 | *** join/#maemo Guest50382 (~rd@p57B48044.dip0.t-ipconnect.de) |
| 20:41.39 | internetishard | kerio: gmail account |
| 20:41.52 | kerio | still cleartext |
| 20:42.08 | *** join/#maemo lxp (~lxp@193-83-209-119.adsl.highway.telekom.at) |
| 20:48.08 | internetishard | kerio: any idea where the modest dot file is? |
| 20:50.47 | *** join/#maemo db9j (~db9j@cpc27-bolt13-2-0-cust15.10-3.cable.virginmedia.com) |
| 20:51.12 | db9j | where do I place a program in the n900 so it runs at boot |
| 20:52.19 | *** join/#maemo LauRoman (~LauRoman@5-14-92-176.residential.rdsnet.ro) |
| 20:53.59 | sixwheeledbeast | make an event for it using upstart? |
| 20:54.16 | db9j | could you explain how please |
| 20:56.32 | *** join/#maemo sunny_s (~sunny_s@86.57.254.135) |
| 20:58.41 | sixwheeledbeast | make a text file of the correct format in "/etc/event.d/foo", please note broken files here may cause bootloop |
| 20:59.19 | db9j | if you get into a boot loop does it need to be reflashed |
| 21:00.14 | sixwheeledbeast | yes or backupmenu uboot resuce shell etc |
| 21:00.54 | sixwheeledbeast | http://upstart.ubuntu.com/index.html |
| 21:01.25 | *** join/#maemo nox- (noident@freebsd/developer/nox) |
| 21:08.41 | db9j | sixwheeledbeast, does this look ok |
| 21:08.46 | db9j | start on stopped rcS |
| 21:08.46 | db9j | console output |
| 21:08.46 | db9j | respawn |
| 21:08.46 | db9j | script |
| 21:08.46 | db9j | exec /usr/local/sbin/voip.py start |
| 21:08.46 | db9j | end script |
| 21:10.44 | sixwheeledbeast | whats is for? |
| 21:10.53 | sixwheeledbeast | s/is/it/ |
| 21:11.19 | db9j | I am playing around with voip on my n900 |
| 21:11.49 | db9j | there are some bugs with the n900 when it uses sip |
| 21:12.24 | sixwheeledbeast | well hard to tell, better on pastebin. but theres no stop command |
| 21:12.29 | db9j | I have found some workarounds and this one stops the chirpyness of calls when you use sip |
| 21:13.04 | sixwheeledbeast | also "on hildon-desktop" is better rcs maybe a bit early for running python stuffs |
| 21:13.06 | db9j | normally I use pastbin but there was only a few lines |
| 21:14.42 | db9j | how would you run this then? all this bit does is to hold the cpu frequency to 600 while a sip call is open |
| 21:15.28 | db9j | so it can run near the end after most of the other stuff has loaded |
| 21:15.31 | sixwheeledbeast | using kernel-power? |
| 21:15.35 | db9j | yes |
| 21:15.54 | sixwheeledbeast | why not lock 600000 in a profile and load that? |
| 21:16.26 | db9j | well that would mean it would be running at 600 all the time |
| 21:16.49 | db9j | this just runs the cpu at 600 while a sip call is being made |
| 21:16.57 | db9j | then it reverts |
| 21:17.34 | db9j | it stops the cpu from moving up and down in frequency while a call is taking place |
| 21:18.40 | sixwheeledbeast | can you load different profiles pre and post call? |
| 21:19.04 | sixwheeledbeast | s/can you/you could/ |
| 21:19.18 | db9j | dont know |
| 21:20.03 | kerio | db9j: are you sure that that doesn't already happen? |
| 21:20.26 | db9j | it does not happen as far as I can tell |
| 21:20.29 | *** join/#maemo Guest50382 (~rd@p57B48044.dip0.t-ipconnect.de) |
| 21:20.52 | sixwheeledbeast | nods agreeing with kerio |
| 21:20.56 | *** join/#maemo vblazquez (~vic@32.9.77.188.dynamic.jazztel.es) |
| 21:21.04 | kerio | i think it does, for normal calls |
| 21:21.16 | db9j | this is what causes the chirpyness in sip calls |
| 21:21.33 | db9j | yes it does lock for normal calls |
| 21:21.45 | db9j | but not sip calls |
| 21:22.41 | db9j | I just need a way to make it run on boot otherwise I will have to manually run it each time |
| 21:30.04 | sixwheeledbeast | db9j: http://pastebin.com/ichhbT1g I am imaging this, however I am no upstart guru. |
| 21:31.08 | db9j | thanks I am reading up |
| 21:38.27 | *** join/#maemo Dragnslcr (~scott@c-76-118-7-184.hsd1.ma.comcast.net) |
| 21:39.37 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 21:41.27 | DocScrutinizer05 | meh, isn't it amazing? always dreaming about the big red button, and when you caary it in your pocket, it doesn't feel attractive anymore |
| 21:43.13 | DocScrutinizer05 | anyway seems ML are working again, and no matter how pissed I feel about manager if tech, I'll make sure similar regressions are limited to the inevitable |
| 21:43.16 | RiD | what are you talking about |
| 21:43.42 | DocScrutinizer05 | s/ if / of /. |
| 21:44.47 | DocScrutinizer05 | even if that means fixing of other infra services is slowing down |
| 21:46.58 | DocScrutinizer05 | a friend off mine (and sysop in Fermany's largest IT service provider): "Highlander principle doesn't apply for IT - there's always another one who's willing to play to the rules" |
| 21:47.24 | DocScrutinizer05 | a friend of mine (and sysop in Germany's largest IT service provider): "Highlander principle doesn't apply for IT - there's always another one who's willing to play to the rules" |
| 21:47.30 | DocScrutinizer05 | (sorry) |
| 21:52.36 | *** join/#maemo GI_Jack (~GI_Jack@pdpc/supporter/active/gi-jack) |
| 21:52.54 | *** part/#maemo valeriusN (root@icq.jabber.tsure.ru) |
| 21:53.34 | GI_Jack | sup |
| 21:54.28 | kerio | DocScrutinizer05: <3 |
| 21:54.53 | GI_Jack | I recently got my n900 working again this week |
| 21:55.15 | kerio | RiD: doc isn't pissed off at the world (in general) and at the maemo.org tech staff (in particular) |
| 21:55.18 | kerio | *anymore |
| 21:56.58 | RiD | GI_Jack what was the issue? |
| 21:57.35 | GI_Jack | the infamous "All communications are disabled", i.e. the GSM modem and GPS taking a crap |
| 21:58.28 | RiD | i fear for the day mine starts doing that |
| 21:58.37 | RiD | it scared me once already. Turns out it was dust. |
| 21:58.44 | GI_Jack | so I after 2 years of the thing sitting on my desk, I found the thread with the fix, disassmbled it, cleaned the dust out, took off the metal shielding on the GSM modem, put the springs in it as described and bing, works like new |
| 21:58.46 | RiD | that was over a year |
| 21:59.09 | GI_Jack | the actual body itself was pretty worn out, so I have a new one comming I found on ebay |
| 21:59.19 | RiD | how does your keyboard look? |
| 21:59.24 | GI_Jack | keyboard is terrible |
| 21:59.29 | RiD | mine too :( |
| 21:59.35 | RiD | the led doesn't make it any better |
| 21:59.37 | GI_Jack | you can find them for $4 a piece on ebay |
| 21:59.43 | GI_Jack | and they are easy to replace |
| 21:59.47 | RiD | yes, but aren't most of these fake? |
| 21:59.51 | GI_Jack | I hope not |
| 22:00.04 | GI_Jack | we'll see |
| 22:00.08 | RiD | i noticed many images with different fonts, letter placements, etc. |
| 22:00.23 | GI_Jack | the actual keypad is a purely passive mechanical device |
| 22:00.34 | GI_Jack | so having a genuine nokia keyboard matters not |
| 22:00.42 | GI_Jack | the actual buttons are on the motherboard |
| 22:00.50 | RiD | i know, but the fake ones are so ugly! |
| 22:01.12 | GI_Jack | the ones I saw looked decent enough |
| 22:01.27 | GI_Jack | if you had enough talnet you could 3 print a new body for the n900 |
| 22:01.44 | GI_Jack | when I get the new body, I am going to paint it |
| 22:01.51 | GI_Jack | there will be a thread on maemo.org |
| 22:02.06 | RiD | paint it with some fluorescent pink |
| 22:02.07 | RiD | bling bling |
| 22:02.20 | GI_Jack | RID - neon orange and neon green |
| 22:02.27 | RiD | is that your actual idea |
| 22:02.30 | GI_Jack | yes |
| 22:02.37 | GI_Jack | I paint flash drives like that |
| 22:02.37 | RiD | haha |
| 22:02.42 | GI_Jack | and hand them out at hacker cons |
| 22:02.51 | RiD | when you mention neon, you mean glown in the dark? |
| 22:03.04 | GI_Jack | no, I mean krylon neon paint |
| 22:04.21 | GI_Jack | http://www.lifeandhome.com/11oz-yellow-orange-spray-paint.html?gclid=CIqy8_OtlrYCFcqd4AodX3AAsw |
| 22:04.25 | GI_Jack | say it with krylon baby |
| 22:04.47 | RiD | ultraviolet, i see |
| 22:05.14 | *** join/#maemo hardaker (~hardaker@mail.hardakers.net) |
| 22:05.26 | GI_Jack | I do it nice, I sand the flash drives down with a sander, wash them, dry them, thick coat of grey primer, let that set, and then either a base coat of green or orange(double coat actually) |
| 22:05.54 | GI_Jack | then when it dries, I tear some masking tape, and cover the object, and then spray it twice with the other color |
| 22:06.02 | GI_Jack | and when that is done, a double coat of clear |
| 22:07.01 | GI_Jack | now I just need a theme to go with it, so far I've found the theme customizer, and a nice orange green cammo wallpaper |
| 22:10.41 | RiD | http://www.ebay.com/itm/Black-Direction-Numeric-Keypad-Key-Nokia-N900-/121019794590?_trksid=p2045573.m2042&_trkparms=aid%3D111000%26algo%3DREC.CURRENT%26ao%3D1%26asc%3D27%26meid%3D6478216251093521991%26pid%3D100033%26prg%3D1011%26rk%3D1%26sd%3D121019794590%26 |
| 22:10.45 | RiD | doesn't look that bad |
| 22:10.51 | RiD | oh sorry for the huge link |
| 22:10.54 | sixwheeledbeast | well if it went missing you would recognise it |
| 22:11.29 | RiD | haha |
| 22:11.30 | sixwheeledbeast | beware of theme customizer potentially buggy on repo versions |
| 22:13.42 | GI_Jack | I don't care as long as it works |
| 22:13.55 | GI_Jack | I do like the LED backlight, but with the LED backlight I really can't paint the keys |
| 22:18.36 | sixwheeledbeast | anybody wish help a qt newbie, with a source file? |
| 22:19.12 | *** join/#maemo eMHa (~mh@HSI-KBW-149-172-0-168.hsi13.kabel-badenwuerttemberg.de) |
| 22:20.22 | M4rtinK | modRana 0.41.1 has been released ! now with multi-map overlay support in the QML GUI :) |
| 22:20.37 | M4rtinK | for more info, see the release post on TMO: http://talk.maemo.org/showpost.php?p=1331462&postcount=1314 |
| 22:21.14 | sixwheeledbeast | 41.4 or 40.1? |
| 22:21.31 | sixwheeledbeast | s/41.4/41.1/ |
| 22:21.56 | ZogG_laptop | <PROTECTED> |
| 22:24.16 | *** join/#maemo hazchemix (~user@a82-161-131-15.adsl.xs4all.nl) |
| 22:24.27 | *** join/#maemo valeriusN (root@80.250.181.195) |
| 22:24.34 | *** part/#maemo hazchemix (~user@a82-161-131-15.adsl.xs4all.nl) |
| 22:25.12 | M4rtinK | sixwheeledbeast: oh, yeah a typo: 0.40.1 is correct |
| 22:25.23 | M4rtinK | sixwheeledbeast: thanks for the correction :) |
| 22:25.33 | sixwheeledbeast | :P |
| 22:26.06 | sixwheeledbeast | wouldn't want to miss a version. |
| 22:26.22 | M4rtinK | BTW, regarding modRanas version numbering - I just increment the version by 0.01 every time some significant feature is added |
| 22:26.32 | M4rtinK | since 0.01 :) |
| 22:31.29 | M4rtinK | also, all 0.04 - 0.40 changelogs are here: http://modrana.org/trac/wiki/ChangelogEN :) |
| 22:38.00 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 22:38.52 | *** join/#maemo unclouded (~neil@2001:4428:200:80fc:c076:8c29:88fc:68a3) |
| 22:39.06 | *** join/#maemo sirdancealo2 (~sirdancea@98.82.broadband5.iol.cz) |
| 22:40.42 | *** join/#maemo Wizzup_ (~Wizzup@old.villavu.com) |
| 22:42.39 | *** join/#maemo Chiku|dc (Chiku01@2a01:e35:8b73:8620:2508:9399:e905:2225) |
| 22:42.39 | *** join/#maemo Chiku|dc (Chiku01@unaffiliated/chiku) |
| 22:42.53 | *** join/#maemo sunny_s (~sunny_s@86.57.254.135) |
| 22:46.55 | *** join/#maemo bef0rd (~bef0rd@unaffiliated/beford) |
| 22:52.43 | *** join/#maemo hazchemix (~user@a82-161-131-15.adsl.xs4all.nl) |
| 22:52.57 | *** join/#maemo hazchemix (~user@a82-161-131-15.adsl.xs4all.nl) |
| 22:53.03 | *** part/#maemo hazchemix (~user@a82-161-131-15.adsl.xs4all.nl) |
| 22:59.09 | *** join/#maemo M4rtinK (~M4rtinK@mail.melf.eu) |