| * enyc meows | 12:58 | |
| * badcloud_ opens a tin of tuna | 13:18 | |
| badcloud_ | 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 | 15:16 |
|---|---|---|
| badcloud_ | Is there any way to have a hildon menu entry which launches osso-xterm with bash? | 15:17 |
| badcloud_ | Instead of ash | 15:18 |
| badcloud_ | I don't want to change default shell in /etc/passwd | 15:18 |
| badcloud_ | Just have a separate entry in hildon | 15:18 |
| KotCzarny | make a script? | 15:19 |
| badcloud_ | Sure, why not | 15:21 |
| badcloud_ | It seems to work only when running the script within an existing osso-xterm window | 15:39 |
| badcloud_ | I tried /usr/bin/maemo-summoner /usr/bin/osso-xterm.launch -e bash | 15:40 |
| bencoh | badcloud_: try adding Terminal=true | 16:00 |
| badcloud_ | Nope, it just quits after opening an osso-xterm window, thinking a lot (spinning animation) and then quitting | 16:04 |
| badcloud_ | Why's it gotta be so convoluted, Nokia?? | 16:15 |
| * badcloud_ shakes fists at the air | 16:15 | |
| KotCzarny | i think its not nokia, that whole app bussiness was earlier | 16:16 |
| badcloud_ | Gotcha | 16:17 |
| halftux | badcloud_: try this Exec=/usr/bin/osso-xterm 'bash' | 16:19 |
| KotCzarny | umm | 16:20 |
| KotCzarny | shouldnt it be full path? | 16:20 |
| KotCzarny | ie. /usr/bin/bash or whatever? | 16:20 |
| KotCzarny | since bash is not officially installed, check where it is | 16:20 |
| halftux | could be that a full path is needed, but remove the -e and put it in inverted commas | 16:22 |
| badcloud_ | which bash gave me /bin/bash | 16:25 |
| badcloud_ | I tried inverted commas | 16:25 |
| badcloud_ | How is leste in this regard, easier to customize? | 16:26 |
| halftux | which bash version you have installed? | 16:27 |
| badcloud_ | 4 | 16:27 |
| badcloud_ | Bear in mind that when I run any variant of the Exec value in an existing xterm window, works fine | 16:28 |
| badcloud_ | osso-xterm -e bash works | 16:29 |
| badcloud_ | osso-xterm bash does too | 16:29 |
| badcloud_ | So does '/usr/bin/maemo-summoner /usr/bin/osso-xterm.launch -e bash' | 16:30 |
| badcloud_ | It's only from the hildon menu that things go south | 16:30 |
| KotCzarny | full path? | 16:30 |
| badcloud_ | Yup | 16:32 |
| badcloud_ | Exec=/usr/bin/osso-xterm -e `/bin/bash/` was my last attempt | 16:33 |
| KotCzarny | um | 16:33 |
| badcloud_ | using inverted commas | 16:33 |
| KotCzarny | /bin/bash ? | 16:33 |
| KotCzarny | and drop backticks | 16:33 |
| badcloud_ | Yes, /bin/bash is where bash is | 16:34 |
| badcloud_ | Still nothing | 16:34 |
| badcloud_ | Please tell me that leste is easier to configure | 16:37 |
| KotCzarny | i strongly suspect what are you trying to achieve is doable, just some stupid typo somewhere | 16:37 |
| badcloud_ | I'll post my .desktop file later when I get a chance | 16:38 |
| badcloud_ | Ciao for now | 16:39 |
| KotCzarny | :) | 16:39 |
| halftux | Pali: 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? | 17:37 |
| Pali | hello | 17:38 |
| Pali | can you please post full log? | 17:38 |
| halftux | is there a log option or should I redirect the output to > log.txt | 17:39 |
| Pali | record | 17:39 |
| Pali | or post output from terminal | 17:39 |
| halftux | ok I will do it later still at work | 17:50 |
| badcloud_ | https://pastebin.com/nSyjdui5 | 18:03 |
| badcloud_ | ^ the osso-xterm bash desktop file | 18:03 |
| halftux | badcloud_: it is a bit tricky with bash but it works | 19:08 |
| halftux | make sure in desktop file there is no line X-Osso-Service=xterm | 19:09 |
| halftux | Exec=/usr/bin/osso-xterm '/opt/bash.sh' | 19:10 |
| halftux | bash script: #!/bin/sh [newline] sleep 2 [newline] /usr/bin/osso-xterm '/bin/bash' [newline] return | 19:13 |
| halftux | thats it | 19:14 |
| badcloud_ | Wow, bravo | 19:17 |
| badcloud_ | Thanks :) | 19:18 |
| halftux | np | 19:19 |
| halftux | going offline will be back later if you still facing a problem with it | 19:20 |
| KotCzarny | you exec osso-xterm twice | 19:20 |
| halftux | yes and with return I close the first one | 19:20 |
| KotCzarny | why not just make it /bin/sh /yourscript ? | 19:20 |
| KotCzarny | anyway, as long it works.. | 19:22 |
| halftux | lol yeah should also work thinking to complicated sometimes | 19:22 |
| halftux | cya later | 19:23 |
| DocScrutinizer05 | https://www.youtube.com/watch?v=ZBq7VMIkgPk | 19:48 |
| DocScrutinizer05 | TLBLEED | 19:49 |
| DocScrutinizer05 | sorry, not exactly news | 19:59 |
| DocScrutinizer05 | badcloud_: >>Terminal=false<< HMMM?? | 20:01 |
| badcloud_ | I tried it with true as well | 20:02 |
| badcloud_ | halftux's script did the trick though | 20:02 |
| DocScrutinizer05 | this works for a script for me https://termbin.com/hgh7 | 20:12 |
| DocScrutinizer05 | not bash though | 20:12 |
| DocScrutinizer05 | I wonder if bash is special | 20:12 |
| badcloud_ | Thanks | 20:16 |
| DocScrutinizer05 | could you try echo "/bin/bash" >>/etc/shells; ? | 20:38 |
| DocScrutinizer05 | sorry when I'm a tad lazy trying that on my own phone | 20:39 |
| DocScrutinizer05 | since I already got this and possibly other mods already | 20:40 |
| DocScrutinizer05 | changing login shell on etc/passwd is strongly deprecated, it may result in system boot failure | 20:41 |
| DocScrutinizer05 | thanks to subtle differences between bash and messybox which are relied upon in startup scripts | 20:42 |
| DocScrutinizer05 | man 5 shells >>/etc/shells is a text file which contains the full pathnames of valid login shells<< | 20:45 |
| DocScrutinizer05 | good question if starting an xterm would invoke a *login* shell | 20:46 |
| DocScrutinizer05 | though >>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.<< | 20:48 |
| DocScrutinizer05 | your description of what works and what doesn't sounds much like a specific login shell problem | 20:49 |
| Maxdamantus | I just have my shell set to /bin/bash .. should be able to do something like `chsh -s /bin/bash` | 20:53 |
| DocScrutinizer05 | >>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 | 21:00 |
| Maxdamantus | I 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. | 21:02 |
| Maxdamantus | I think reading /etc/passwd to figure out what shell to use is a fairly standard behaviour for terminals. urxvt does it. | 21:03 |
| Maxdamantus | A regular xterm (not osso) does it too. | 21:04 |
| halftux | in principle no script is needed checked again the mistacke was only this line in the desktop file X-Osso-Service=xterm | 21:05 |
| halftux | mistake | 21:05 |
| halftux | badcloud_: only removing X-Osso-Service=xterm will solve the issue no other steps are needed | 21:07 |
| DocScrutinizer05 | though 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<< | 21:07 |
| DocScrutinizer05 | X-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 | 21:08 |
| DocScrutinizer05 | obviously you need a different name for an xterm with different behavior than the one defined in dbus config | 21:10 |
| badcloud_ | Fixed the desktop file | 21:12 |
| KotCzarny | see? i knew it was something trivial | 21:15 |
| KotCzarny | :) | 21:15 |
| halftux | :) | 21:15 |
| * DocScrutinizer05 still wonders if osso-xterm checks /etc/shells | 21:16 | |
| KotCzarny | osso-xterm runs user's shell then a command inside that shell | 21:16 |
| DocScrutinizer05 | err | 21:17 |
| Maxdamantus | My N900 doesn't have an /etc/shells file | 21:17 |
| DocScrutinizer05 | this is an answer to my question? | 21:17 |
| DocScrutinizer05 | also doesn't seem correct | 21:18 |
| Maxdamantus | I think /etc/shells is just something used by `chsh`, not the terminal/login mechanism. | 21:18 |
| DocScrutinizer05 | xterm [-toolkitoption ...] [-option ...] [shell] | 21:18 |
| Maxdamantus | that is, it should prevent people from putting non-standard shells into their line in /etc/passwd | 21:18 |
| Maxdamantus | but obviously root can just edit the /etc/passwd file directly to avoid that limitation. | 21:19 |
| DocScrutinizer05 | quite possibly osso-xterm is a simplified generic xterm, it still may accept commands to run *instead* of shell rather than *in* shell | 21:20 |
| Maxdamantus | man 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 |
| DocScrutinizer05 | ayayayay https://termbin.com/jgm4 | 22:20 |
| halftux | looks ugly | 22:45 |
| halftux | Pali: http://www.setius.net/downs/maemo/dump0.log | 23:12 |
| Pali | what arguments have you used? | 23:12 |
| halftux | 0xFFFF -E dump0.fiasco &> dump0.log | 23:13 |
| Pali | seems that you have desynced stdout and stderr | 23:14 |
| Pali | at first lines is stderr and then stdout | 23:14 |
| Pali | but nevermind... | 23:14 |
| Pali | "File initfs_tmp is empty, removing it..." --> this is OK, stock Maemo on N900 does not use initfs | 23:15 |
| Pali | so it is empty | 23:15 |
| halftux | great I know sdcard was to small with this attempt | 23:15 |
| Pali | "Error: Not enough free space (have: 27616083968, need: 28995223552)" --> this is due to small SD card | 23:16 |
| Pali | you cannot put dump of SD card to SD card | 23:16 |
| Pali | "Error: Cannot open image file mmc_tmp: No such file or directory" --> this is just a reason for previous error | 23:16 |
| Pali | "Error: Cannot open image file initfs_tmp: No such file or directory" --> ignore this, 0xFFFF should probably do not show such message | 23:17 |
| halftux | I see I thought it is emmc | 23:17 |
| Pali | yea, you are right, this is eMMC MyDocs, not SD card | 23:17 |
| halftux | I needed to umount /home/usr/MyDocs | 23:18 |
| halftux | and this whole image can be flashed back? | 23:18 |
| halftux | with emmc? | 23:18 |
| Pali | it is complicated | 23:18 |
| Pali | \/opt is stored on second partition of eMMC and this stuff is not backed up | 23:19 |
| halftux | why that it is a none working fiasco file? | 23:19 |
| Pali | and this stuff cannot be even put into FIASCO image | 23:19 |
| Pali | so there is no way for do whole backup+restore | 23:19 |
| halftux | ah I see, is there a way to back it up seperatly und push it back? | 23:20 |
| Pali | you can do backup of /opt manually | 23:20 |
| DocScrutinizer05 | halftux: -v for those who love ugly | 23:20 |
| Pali | e.g. via unix dd | 23:20 |
| Pali | restore is problematic | 23:21 |
| Pali | without /opt Maemo system does not bootup | 23:21 |
| halftux | rescue os? | 23:21 |
| Pali | but there is a way, look at my "bootmenu" | 23:21 |
| DocScrutinizer05 | /usr/share/applications/hildon # update-desktop-database | 23:21 |
| DocScrutinizer05 | /usr/share/applications/hildon # | 23:21 |
| Pali | it can export whole eMMC via USB prior to booting Maemo | 23:22 |
| Pali | so if rootfs has installed bootmenu, and rootfs is in fiasco dump | 23:22 |
| Pali | you would be able to restore rootfs, jump into bootmenu, export eMMC via USB | 23:22 |
| Pali | and then restore /opt | 23:22 |
| Pali | I do not know what is supported by backupmenu, but maybe something similar is possible | 23:23 |
| halftux | ok I will have a look thank you for your explanation | 23:23 |
| Pali | flashing MyDocs is problematic, IIRC it erases /opt | 23:23 |
| DocScrutinizer05 | well, technically I think you could put /home on FIASCO | 23:23 |
| DocScrutinizer05 | aka EMMC | 23:24 |
| Pali | no, you cannot | 23:24 |
| Pali | eMMC fiasco can contain only MyDocs part | 23:24 |
| DocScrutinizer05 | ooh | 23:24 |
| Pali | part /home is IIRC maped to /opt | 23:24 |
| Pali | it is on same partition | 23:24 |
| Pali | there is symlink or bind mount or other technique | 23:25 |
| Pali | but I do not remember all details, at least I was not able to put /opt or /home into fiasco image | 23:25 |
| Pali | but that is not a final proof that it is impossible | 23:26 |
| halftux | but it is interesting, is stock /opt empty? | 23:26 |
| Pali | yes, stock /opt is empty, but stock rootfs has some init scripts which moves some parts from /usr to /opt | 23:27 |
| DocScrutinizer05 | basically yes, though root image runs optify | 23:28 |
| Pali | init scripts which do that only on first boot of stock rootfs | 23:28 |
| DocScrutinizer05 | ~optification | 23:28 |
| infobot | optification 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" | 23:28 |
| Pali | and all maemo applications from extras install DEB packages to /opt | 23:28 |
| DocScrutinizer05 | hmm, I think they also run optify | 23:29 |
| DocScrutinizer05 | or at least that's one of the options | 23:29 |
| DocScrutinizer05 | https://termbin.com/ac0l | 23:36 |
| DocScrutinizer05 | https://termbin.com/dc19 | 23:47 |
| Pali | another problem of 0xFFFF is that it does not have implementation of flashing eMMC images (I had not time to finish it) | 23:47 |
| halftux | Pali: 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? | 23:47 |
| halftux | ah I see now your message that is sad I thought the original eMMC | 23:49 |
| Pali | seems that 2101 and 2104 HW revs uses different bootloader | 23:49 |
| Pali | Nokia's flasher-3.5 can flash eMMC images viac USB | 23:50 |
| Pali | but 0xFFFF does not implement it | 23:50 |
| Pali | anyway, here is a quick fix to hide those error messages about missing files: https://github.com/pali/0xFFFF/commit/e94279eecbfdd1988912ac7ce24e6d4d702695a1 | 23:51 |
| DocScrutinizer05 | you generally shall not flash NOLO | 23:51 |
| Pali | that is truth, unless you have old version | 23:51 |
| Pali | 0xFFFF has some filter argument to specify which image types from FIASCO images would be flashed | 23:52 |
| Pali | so unpack & pack could be avoided | 23:52 |
| halftux | ah ok thats something | 23:52 |
| DocScrutinizer05 | how could you? was NOLO ever updated? and if yes, what for? | 23:52 |
| Pali | yes, PR1.3 has new version of NOLO as in PR1.0 | 23:53 |
| Pali | and IIRC Nokia distributed all devices with PR1.0 version | 23:53 |
| DocScrutinizer05 | wow | 23:53 |
| DocScrutinizer05 | forgot | 23:53 |
| Pali | but if you are going to unpack FIASCO, do not forget about metadata | 23:53 |
| Pali | so when building a new fiasco, do not forget for specififying image version and HW revision | 23:54 |
| Pali | and type | 23:54 |
| DocScrutinizer05 | I actually wonder how Nokia made COMBINED that did not have optification already done on them | 23:55 |
| halftux | what is image version? | 23:55 |
| halftux | or better what does it mean in your example you have 1.0 | 23:56 |
| Pali | e.g. version of NOLO, version of kernel or version of rootfs | 23:56 |
| Pali | use "-i" argument to show it | 23:56 |
| halftux | ok thank you lots of input this evening :) | 23:57 |
| Pali | there is an unfinished attempt for writing support for flashing eMMC images: https://github.com/pali/0xFFFF/issues/6 | 23:58 |
| Pali | if somebody want to finish it I can help | 23:58 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!