Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 18 hrs, 35 mins ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 19 hrs, 49 mins ago -
Maemo repository (3)
to Community by torsen - 1 day, 11 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 2 days, 8 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 3 days, 15 hrs ago - more...
|
2012-05-22
, 06:17
|
|
Posts: 135 |
Thanked: 158 times |
Joined on Sep 2009
@ Germany
|
#2
|
My english is not so good and i have not the best knowledge but i will help. Maybe is this better. Only an idea. 
postinstall
postrm
I dont know. Only an Idea.
postinstall
Code:
#!/bin/sh # mkdir /usr/share/policy/etc/FasterN9 mkdir /usr/share/policy/etc/noswap-backup cp -a /usr/share/policy/etc/noswap/* /usr/share/policy/etc/noswap-backup/ cp -a /usr/share/policy/etc/noswap/* /usr/share/policy/etc/FasterN9/ rm /usr/share/policy/etc/current rm /usr/share/policy/etc/FasterN9/syspart.conf ln -s /opt/FasterN9/config/syspart.conf /usr/share/policy/etc/FasterN9 ln -s /usr/share/policy/etc/FasterN9 /usr/share/policy/etc/current
postrm
Code:
#!/bin/sh # rm -rf /usr/share/policy/etc/FasterN9 rm /usr/share/policy/etc/current cp -a /usr/share/policy/etc/noswap-backup/* /usr/share/policy/etc/noswap/ ln -s /usr/share/policy/etc/noswap /usr/share/policy/etc/current
|
|
2012-05-22
, 19:26
|
|
Posts: 143 |
Thanked: 205 times |
Joined on Apr 2008
|
#3
|
Originally Posted by traysh
Maybe always forcing will help to suppress errors, like
postinstall script:
Code:#!/bin/sh # mkdir /usr/share/policy/etc/FasterN9 cp -a /usr/share/policy/etc/noswap/* /usr/share/policy/etc/FasterN9/ rm /usr/share/policy/etc/current rm /usr/share/policy/etc/FasterN9/syspart.conf ln -s /opt/FasterN9/config/syspart.conf /usr/share/policy/etc/FasterN9 ln -s /usr/share/policy/etc/FasterN9 /usr/share/policy/etc/current
Code:
#!/bin/sh # rmdir -rf /usr/share/policy/etc/FasterN9 cp -a /usr/share/policy/etc/noswap /usr/share/policy/etc/FasterN9 ln -sf /opt/FasterN9/config/syspart.conf /usr/share/policy/etc/FasterN9/syspart.conf ln -sf /usr/share/policy/etc/FasterN9 /usr/share/policy/etc/current
Originally Posted by traysh
postrm script:
Code:#!/bin/sh # rm -rf /usr/share/policy/etc/FasterN9 rm /usr/share/policy/etc/current ln -s /usr/share/policy/etc/noswap /usr/share/policy/etc/current
Code:
#!/bin/sh # ln -sf /usr/share/policy/etc/noswap /usr/share/policy/etc/current rm -rf /usr/share/policy/etc/FasterN9
|
|
2012-05-22
, 20:13
|
|
Posts: 324 |
Thanked: 739 times |
Joined on Jun 2009
@ São Paulo, Brazil
|
#4
|
Thank you all. Changed the scripts and now I think everything is fine.
|
|
2012-05-22
, 20:51
|
|
Posts: 1,313 |
Thanked: 2,978 times |
Joined on Jun 2011
@ Finland
|
#5
|
Originally Posted by traysh
This suggests that "current" is the one used by N9 when booted. Generally speaking, the scripts should be made so that the "current" is always valid. In other words, preparations in other directories must be done fully before pointing "current" to it. Also current should never be in a state that it doesn't exist, or bad things will happen.
The original firmware has:
/usr/share/policy/etc/noswap (folder)
/usr/share/policy/etc/current (link to /usr/share/policy/etc/noswap)
/usr/share/policy/etc/noswap/syspart.conf (file)
So with that I suggest following changes:
postinstall script:
Code:
#!/bin/sh # mkdir /usr/share/policy/etc/FasterN9 cp -a /usr/share/policy/etc/noswap/* /usr/share/policy/etc/FasterN9/ # Removing current should not be done here, as if something happens after removing but before rest of installation is finished, device might brick. # rm /usr/share/policy/etc/current rm /usr/share/policy/etc/FasterN9/syspart.conf ln -s /opt/FasterN9/config/syspart.conf /usr/share/policy/etc/FasterN9 # Here is the final link from current to FasterN9. The options instruct overwrite and treating the destination as file ln -nsf /usr/share/policy/etc/FasterN9 /usr/share/policy/etc/current
Code:
#!/bin/sh # # We can't remove FasterN9 before current points to correct entry # rm -rf /usr/share/policy/etc/FasterN9 # rm /usr/share/policy/etc/current ln -nsf /usr/share/policy/etc/noswap /usr/share/policy/etc/current # Now FasterN9 can be removed rm -rf /usr/share/policy/etc/FasterN9
Still, even with your original script I'd think it would be highly unlikely to go into bad state. The most likely culprit is the postrm script that should be prerm. But there was a couple cases out of hundreds, so you never know... Btw. I haven't tested these commands so there can be some mistakes, but the principle should be sound.
__________________
My N9/N950 projects:
My N9/N950 projects:
I made this package (FasterN9) that basically installs a custom /usr/share/policy/etc/current/syspart.conf in the phone in order to make it less laggy. It works pretty fine, but that's not why I come to you.
The problem is that I read 2 reports from users that uninstalled it in order to update to the next version (not required but shouldn't hurt) and got "the device is malfunctioning". The package was downloaded 679 times now and lots of users did uninstalled it without getting that error, so I'm confused about what is the cause.
Nobody had this error after installing or during usage, only after uninstalling. I myself did installed and uninstalled some times before releasing in order to avoid this kind of problem and didn't got that. I think maybe somehow the changes the postrm script tried to do in the FS were still waiting in a kernel buffer when the phone rebooted and were lost. Is that possible? If so, just adding a sync to the script would fix it.
I'll paste here the postinstall and postrm scripts. Any comments or suggestions are welcome.
The original firmware has:
/usr/share/policy/etc/noswap (folder)
/usr/share/policy/etc/current (link to /usr/share/policy/etc/noswap)
/usr/share/policy/etc/noswap/syspart.conf (file)
FasterN9 package has:
/opt/FasterN9/config/syspart.conf (file)
postinstall script: