IRC log for #maemo on 20200115

01:37.45*** join/#maemo horseshoecrab (~crab@shenzhen.dim-sum.org)
01:44.10*** join/#maemo horseshoecrab (~crab@shenzhen.dim-sum.org)
02:02.35*** join/#maemo horseshoecrab (~crab@shenzhen.dim-sum.org)
03:49.11*** join/#maemo AndrewX192 (~andrew@unaffiliated/andrewx192)
04:44.06*** join/#maemo tm (~sinnlos@unaffiliated/tm)
05:19.50*** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg)
06:29.26*** join/#maemo horseshoecrab (~crab@shenzhen.dim-sum.org)
06:35.52*** join/#maemo horseshoecrab (~crab@shenzhen.dim-sum.org)
06:54.19*** join/#maemo horseshoecrab (~crab@shenzhen.dim-sum.org)
07:03.05*** join/#maemo horseshoecrab (~crab@wongtaisin.dim-sum.org)
07:45.06*** join/#maemo Pali (~pali@Maemo/community/contributor/Pali)
07:55.40*** join/#maemo Vajb (~Vajb@2001:999:60:5fe7:8ad6:9f43:167f:216)
08:41.54*** join/#maemo jskarvad (~jskarvad@redhat/jskarvad)
08:46.18*** join/#maemo Kabouik_ (~kabouik@147.99.217.201)
09:00.58*** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian)
09:43.21*** join/#maemo eMHa__ (~mh@217.5.215.149)
11:40.42*** join/#maemo script (~script@mail.scriptkiller.de)
11:45.31*** join/#maemo badcloud_ (844308a4@system-35.cs.tau.ac.il)
11:47.25*** join/#maemo halftux (~halftux@193.149.11.238)
11:58.34enycmeows
12:18.55badcloud_opens a tin of tuna
12:31.27*** join/#maemo peetah (~peetah@cha92-9-82-236-202-86.fbx.proxad.net)
12:56.45*** join/#maemo Vajb (~Vajb@91-158-49-42.elisa-laajakaista.fi)
13:00.26*** join/#maemo jskarvad (~jskarvad@redhat/jskarvad)
13:14.58*** join/#maemo Kabouik_ (~kabouik@147.99.217.201)
13:44.24*** join/#maemo ^[ (sid43445@ircpuzzles/2015/april-fools/sixth/zgrep)
13:53.21*** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg)
14:00.48*** join/#maemo enyc (~enyc@muddle.enyc.org.uk)
14:16.53badcloud_I tried making a desktop file for osso-xterm which would run bash. "Exec=/usr/bin/osso-xterm -e bash" didn't work, even though running that command from osso-xterm brings up a new window with bash
14:17.40badcloud_Is there any way to have a hildon menu entry which launches osso-xterm with bash?
14:18.00badcloud_Instead of ash
14:18.18badcloud_I don't want to change default shell in /etc/passwd
14:18.43badcloud_Just have a separate entry in hildon
14:19.51KotCzarnymake a script?
14:21.00badcloud_Sure, why not
14:39.45badcloud_It seems to work only when running the script within an existing osso-xterm window
14:40.54badcloud_I tried /usr/bin/maemo-summoner /usr/bin/osso-xterm.launch -e bash
14:55.50*** join/#maemo badcloud_ (844308a4@system-35.cs.tau.ac.il)
15:00.57bencohbadcloud_: try adding Terminal=true
15:04.37badcloud_Nope, it just quits after opening an osso-xterm window, thinking a lot (spinning animation) and then quitting
15:08.51*** join/#maemo halftux (~halftux@193.149.11.238)
15:15.39badcloud_Why's it gotta be so convoluted, Nokia??
15:15.51badcloud_shakes fists at the air
15:16.28KotCzarnyi think its not nokia, that whole app bussiness was earlier
15:17.29badcloud_Gotcha
15:19.31halftuxbadcloud_: try this Exec=/usr/bin/osso-xterm 'bash'
15:20.09KotCzarnyumm
15:20.14KotCzarnyshouldnt it be full path?
15:20.21KotCzarnyie. /usr/bin/bash or whatever?
15:20.39KotCzarnysince bash is not officially installed, check where it is
15:22.51halftuxcould be that a full path is needed, but remove the -e and put it in inverted commas
15:25.27badcloud_which bash gave me /bin/bash
15:25.49badcloud_I tried inverted commas
15:26.19badcloud_How is leste in this regard, easier to customize?
15:27.37halftuxwhich bash version you have installed?
15:27.53badcloud_4
15:28.42badcloud_Bear in mind that when I run any variant of the Exec value in an existing xterm window, works fine
15:29.13badcloud_osso-xterm -e bash works
15:29.33badcloud_osso-xterm bash does too
15:30.36badcloud_So does '/usr/bin/maemo-summoner /usr/bin/osso-xterm.launch  -e bash'
15:30.51badcloud_It's only from the hildon menu that things go south
15:30.54KotCzarnyfull path?
15:32.05badcloud_Yup
15:33.10badcloud_Exec=/usr/bin/osso-xterm -e `/bin/bash/` was my last attempt
15:33.18KotCzarnyum
15:33.20badcloud_using inverted commas
15:33.24KotCzarny<PROTECTED>
15:33.31KotCzarnyand drop backticks
15:34.29badcloud_Yes, /bin/bash is where bash is
15:34.35badcloud_Still nothing
15:37.21badcloud_Please tell me that leste is easier to configure
15:37.47KotCzarnyi strongly suspect what are you trying to achieve is doable, just some stupid typo somewhere
15:38.35badcloud_I'll post my .desktop file later when I get a chance
15:39.05badcloud_Ciao for now
15:39.10KotCzarny:)
16:34.12*** join/#maemo Pali (~pali@Maemo/community/contributor/Pali)
16:37.48halftuxPali: Hello Pali I have a question regarding 0xFFFF and the dump fiasco option. First I getting initfs_tmp is empty, removing it. And later Error: Cannot open image file initfs_tmp: No such file. However I get a fiasco file is it save to flash it? Can I ignore this message?
16:38.22Palihello
16:38.35Palican you please post full log?
16:39.38halftuxis there a log option or should I redirect the output to > log.txt
16:39.46Palirecord
16:39.51Palior post output from terminal
16:50.57halftuxok I will do it later still at work
17:03.18*** join/#maemo badcloud_ (844308a4@system-35.cs.tau.ac.il)
17:03.22badcloud_https://pastebin.com/nSyjdui5
17:03.38badcloud_^ the osso-xterm bash desktop file
17:04.12*** join/#maemo troulouliou_div2 (~troulouli@unaffiliated/troulouliou-div2/x-0271439)
17:12.34*** join/#maemo troulouliou_div2 (~troulouli@unaffiliated/troulouliou-div2/x-0271439)
18:08.57halftuxbadcloud_: it is a bit tricky with bash but it works
18:09.41halftuxmake sure in desktop file there is no line X-Osso-Service=xterm
18:10.27halftuxExec=/usr/bin/osso-xterm '/opt/bash.sh'
18:13.02halftuxbash script: #!/bin/sh [newline] sleep 2 [newline] /usr/bin/osso-xterm '/bin/bash' [newline] return
18:14.52halftuxthats it
18:17.40badcloud_Wow, bravo
18:18.55badcloud_Thanks :)
18:19.01halftuxnp
18:20.16halftuxgoing offline will be back later if you still facing a problem with it
18:20.29KotCzarnyyou exec osso-xterm twice
18:20.44halftuxyes and with return I close the first one
18:20.51KotCzarnywhy not just make it /bin/sh /yourscript ?
18:22.01KotCzarnyanyway, as long it works..
18:22.17halftuxlol yeah should also work thinking to complicated sometimes
18:23.01halftuxcya later
18:32.54*** join/#maemo timeless (sid4015@firefox/developer/timeless)
18:37.46*** join/#maemo ^[ (sid43445@ircpuzzles/2015/april-fools/sixth/zgrep)
18:48.42DocScrutinizer05https://www.youtube.com/watch?v=ZBq7VMIkgPk
18:49.00DocScrutinizer05TLBLEED
18:59.36DocScrutinizer05sorry, not exactly news
19:01.41*** join/#maemo eMHa__ (~mh@p5089D88C.dip0.t-ipconnect.de)
19:01.42DocScrutinizer05badcloud_: >>Terminal=false<< HMMM??
19:02.26badcloud_I tried it with true as well
19:02.51badcloud_halftux's script did the trick though
19:12.01DocScrutinizer05this works for a script for me https://termbin.com/hgh7
19:12.22DocScrutinizer05not bash though
19:12.33DocScrutinizer05I wonder if bash is special
19:16.20badcloud_Thanks
19:26.38*** join/#maemo florian (~florian_k@Maemo/community/contributor/florian)
19:38.55DocScrutinizer05could you try echo "/bin/bash" >>/etc/shells; ?
19:39.48DocScrutinizer05sorry when I'm a tad lazy trying that on my own phone
19:40.12DocScrutinizer05since I already got this and possibly other mods already
19:41.07DocScrutinizer05changing login shell on etc/passwd is strongly deprecated, it may result in system boot failure
19:42.08DocScrutinizer05thanks to subtle differences between bash and messybox which are relied upon in startup scripts
19:45.24DocScrutinizer05man 5 shells  >>/etc/shells is a text file which contains the full pathnames of valid login shells<<
19:46.18DocScrutinizer05good question if starting an xterm would invoke a *login* shell
19:48.47DocScrutinizer05though  >>Be  aware  that  there are programs which consult this file to find out if a user is a normal user; for example, FTP daemons traditionally disallow access to users with shells not included in this file.<<
19:49.44DocScrutinizer05your description of what works and what doesn't sounds much like a specific login shell problem
19:53.52MaxdamantusI just have my shell set to /bin/bash .. should be able to do something like `chsh -s /bin/bash`
19:58.48*** join/#maemo florian (~florian_k@Maemo/community/contributor/florian)
20:00.32DocScrutinizer05>>On OSX, by default, the Terminal application runs a login shell. (As I explain, the program that starts the shell decides whether the shell acts as a login shell.) That's not the normal way to do things. <<  https://unix.stackexchange.com/questions/38175/difference-between-login-shell-and-non-login-shell
20:02.45MaxdamantusI think that's talking about a different meaning of "login shell". It's talking there about whether or not it passes `-l` to the shell.
20:03.06MaxdamantusI think reading /etc/passwd to figure out what shell to use is a fairly standard behaviour for terminals. urxvt does it.
20:03.30*** join/#maemo halftux (~pi@i577A6090.versanet.de)
20:04.43MaxdamantusA regular xterm (not osso) does it too.
20:05.03halftuxin principle no script is needed checked again the mistacke was only this line in the desktop file X-Osso-Service=xterm
20:05.24halftuxmistake
20:07.23halftuxbadcloud_: only removing X-Osso-Service=xterm will solve the issue no other steps are needed
20:07.25DocScrutinizer05though   man xterm >>-ls     This option indicates that the shell that is started in the xterm window will be a login shell (i.e., the first character of argv[0] will be a dash, indicating to the shell that it should read the user's .login or .profile).<< // man 5 shells  >>/etc/shells is a text file which contains the full pathnames of valid login shells<<
20:08.50DocScrutinizer05X-Osso-Service=xterm  means: "send a dbus-msg to either start (if no instance is running) or bring to front and focus an already running instance of xterm" AFAIK
20:10.07DocScrutinizer05obviously you need a different name for an xterm with different behavior than the one defined in dbus config
20:12.13badcloud_Fixed the desktop file
20:15.33KotCzarnysee? i knew it was something trivial
20:15.35KotCzarny:)
20:15.46halftux:)
20:16.27DocScrutinizer05still wonders if osso-xterm checks /etc/shells
20:16.54KotCzarnyosso-xterm runs user's shell then a command inside that shell
20:17.06DocScrutinizer05err
20:17.12MaxdamantusMy N900 doesn't have an /etc/shells file
20:17.21DocScrutinizer05this is an answer to my question?
20:18.02DocScrutinizer05also doesn't seem correct
20:18.09MaxdamantusI think /etc/shells is just something used by `chsh`, not the terminal/login mechanism.
20:18.23DocScrutinizer05<PROTECTED>
20:18.27Maxdamantusthat is, it should prevent people from putting non-standard shells into their line in /etc/passwd
20:19.12Maxdamantusbut obviously root can just edit the /etc/passwd file directly to avoid that limitation.
20:20.20DocScrutinizer05quite possibly osso-xterm is a simplified generic xterm, it still may accept commands to run *instead* of shell rather than *in* shell
20:20.25Maxdamantusman chsh >> The only restriction placed on the login shell is that the command name must be listed in /etc/shells, unless the invoker is the superuser, and then any value may be added.
21:20.19DocScrutinizer05ayayayay https://termbin.com/jgm4
21:45.13halftuxlooks ugly
22:12.27halftuxPali: http://www.setius.net/downs/maemo/dump0.log
22:12.54Paliwhat arguments have you used?
22:13.52halftux0xFFFF -E dump0.fiasco &> dump0.log
22:14.30Paliseems that you have desynced stdout and stderr
22:14.39Paliat first lines is stderr and then stdout
22:14.48Palibut nevermind...
22:15.17Pali"File initfs_tmp is empty, removing it..." --> this is OK, stock Maemo on N900 does not use initfs
22:15.22Paliso it is empty
22:15.43halftuxgreat I know sdcard was to small with this attempt
22:16.10Pali"Error: Not enough free space (have: 27616083968, need: 28995223552)" --> this is due to small SD card
22:16.18Paliyou cannot put dump of SD card to SD card
22:16.42Pali"Error: Cannot open image file mmc_tmp: No such file or directory" --> this is just a reason for previous error
22:17.00Pali"Error: Cannot open image file initfs_tmp: No such file or directory" --> ignore this, 0xFFFF should probably do not show such message
22:17.06halftuxI see I thought it is emmc
22:17.48Paliyea, you are right, this is eMMC MyDocs, not SD card
22:18.10halftuxI needed to umount /home/usr/MyDocs
22:18.44halftuxand this whole image can be flashed back?
22:18.50halftuxwith emmc?
22:18.58Paliit is complicated
22:19.26Pali\/opt is stored on second partition of eMMC and this stuff is not backed up
22:19.27halftuxwhy that it is a none working fiasco file?
22:19.43Paliand this stuff cannot be even put into FIASCO image
22:19.59Paliso there is no way for do whole backup+restore
22:20.26halftuxah I see, is there a way to back it up seperatly und push it back?
22:20.43Paliyou can do backup of /opt manually
22:20.56DocScrutinizer05halftux: -v for those who love ugly
22:20.56Palie.g. via unix dd
22:21.10Palirestore is problematic
22:21.24Paliwithout /opt Maemo system does not bootup
22:21.34halftuxrescue os?
22:21.36Palibut there is a way, look at my "bootmenu"
22:21.37DocScrutinizer05/usr/share/applications/hildon # update-desktop-database  
22:21.39DocScrutinizer05/usr/share/applications/hildon #
22:22.00Paliit can export whole eMMC via USB prior to booting Maemo
22:22.20Paliso if rootfs has installed bootmenu, and rootfs is in fiasco dump
22:22.38Paliyou would be able to restore rootfs, jump into bootmenu, export eMMC via USB
22:22.43Paliand then restore /opt
22:23.06PaliI do not know what is supported by backupmenu, but maybe something similar is possible
22:23.39halftuxok I will have a look thank you for your explanation
22:23.46Paliflashing MyDocs is problematic, IIRC it erases /opt
22:23.46DocScrutinizer05well, technically I think you could put /home on FIASCO
22:24.07DocScrutinizer05aka EMMC
22:24.18Palino, you cannot
22:24.31PalieMMC fiasco can contain only MyDocs part
22:24.37DocScrutinizer05ooh
22:24.47Palipart /home is IIRC maped to /opt
22:24.57Paliit is on same partition
22:25.09Palithere is symlink or bind mount or other technique
22:25.45Palibut I do not remember all details, at least I was not able to put /opt or /home into fiasco image
22:26.03Palibut that is not a final proof that it is impossible
22:26.54halftuxbut it is interesting, is stock /opt empty?
22:27.53Paliyes, stock /opt is empty, but stock rootfs has some init scripts which moves some parts from /usr to /opt
22:28.03DocScrutinizer05basically yes, though root image runs optify
22:28.14Paliinit scripts which do that only on first boot of stock rootfs
22:28.16DocScrutinizer05~optification
22:28.17infobotoptification is a inventive duct tape workaround to reclaim space in fs root, done due to the fact the systeminit *and* partitioning is FUBAR,  http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging,_Deploying_and_Distributing/Installing_under_opt_and_MyDocs, or ""OMG - I wish they looked into FHS and moved /usr to eMMC"", http://www.pathname.com/fhs/pub/fhs-2.3.html#PURPOSE2 bullet1,2 and fhs-2.3.html#PURPOSE16 dot3"
22:28.36Paliand all maemo applications from extras install DEB packages to /opt
22:29.05DocScrutinizer05hmm, I think they also run optify
22:29.23DocScrutinizer05or at least that's one of the options
22:36.42DocScrutinizer05https://termbin.com/ac0l
22:47.05DocScrutinizer05https://termbin.com/dc19
22:47.36Palianother problem of 0xFFFF is that it does not have implementation of flashing eMMC images (I had not time to finish it)
22:47.43halftuxPali: when I using your fiasco for cloning N900 HW:2101 to N900 HW:2104 I need to extract the fiasco and correct the xloader.bin and nolo.bin?
22:49.41halftuxah I see now your message that is sad I thought the original eMMC
22:49.55Paliseems that 2101 and 2104 HW revs uses different bootloader
22:50.18PaliNokia's flasher-3.5 can flash eMMC images viac USB
22:50.27Palibut 0xFFFF does not implement it
22:51.13Palianyway, here is a quick fix to hide those error messages about missing files: https://github.com/pali/0xFFFF/commit/e94279eecbfdd1988912ac7ce24e6d4d702695a1
22:51.23DocScrutinizer05you generally shall not flash NOLO
22:51.46Palithat is truth, unless you have old version
22:52.30Pali0xFFFF has some filter argument to specify which image types from FIASCO images would be flashed
22:52.44Paliso unpack & pack could be avoided
22:52.48halftuxah ok thats something
22:52.49DocScrutinizer05how could you? was NOLO ever updated? and if yes, what for?
22:53.05Paliyes, PR1.3 has new version of NOLO as in PR1.0
22:53.24Paliand IIRC Nokia distributed all devices with PR1.0 version
22:53.39DocScrutinizer05wow
22:53.45DocScrutinizer05forgot
22:53.58Palibut if you are going to unpack FIASCO, do not forget about metadata
22:54.14Paliso when building a new fiasco, do not forget for specififying image version and HW revision
22:54.29Paliand type
22:55.03DocScrutinizer05I actually wonder how Nokia made COMBINED that did not have optification already done on them
22:55.17halftuxwhat is image version?
22:56.35halftuxor better what does it mean in your example you have 1.0
22:56.38Palie.g. version of NOLO, version of kernel or version of rootfs
22:56.54Paliuse "-i" argument to show it
22:57.28halftuxok thank you lots of input this evening :)
22:58.35Palithere is an unfinished attempt for writing support for flashing eMMC images: https://github.com/pali/0xFFFF/issues/6
22:58.44Paliif somebody want to finish it I can help
23:00.37halftuxhmm I will look if I am able to understand
23:37.29*** join/#maemo r00t|home (~r00t@ip4d16d844.dynamic.kabel-deutschland.de)
23:41.09*** join/#maemo RedW (~redw@89-67-10-209.dynamic.chello.pl)

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