Active Topics
-
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 54 mins ago -
The N900 is now 15 years old! (6)
to Nokia N900 by Macros - 1 day, 21 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 2 days, 9 hrs ago -
n770 youtube video (0)
to General by nmdv - 6 days, 9 hrs ago - more...
Rushmore |
2009-10-23
, 13:19
|
|
Posts: 1,255 |
Thanked: 393 times |
Joined on Oct 2009
@ US
|
#31
|
If this problem is due 100% to not using verified repository apps, this thread should be the main example of why non-techies should avoid "rogue" sites for apps when the N900 is released. At least until the dust settles and the community has had time to absorb the OS changes for app installs.
|
|
2009-10-23
, 13:24
|
|
Posts: 3 |
Thanked: 1 time |
Joined on Sep 2009
|
#32
|
This is not too surprising, and the official Nokia N900 website specs...
Up to 1 GB of application memory (256 MB RAM, 768 MB virtual memory)
is spot on with:
http://wiki.maemo.org/Documentation/...opt_and_MyDocs
Unfortunately, the fact that 100MB is free of the 256MB (rest used by the system) is somewhat disheartening.
I don't see this as being fixed by Nokia as a bug, its what they reported in the first place and developers will work around it as they already have.
Up to 1 GB of application memory (256 MB RAM, 768 MB virtual memory)
is spot on with:
http://wiki.maemo.org/Documentation/...opt_and_MyDocs
Unfortunately, the fact that 100MB is free of the 256MB (rest used by the system) is somewhat disheartening.
I don't see this as being fixed by Nokia as a bug, its what they reported in the first place and developers will work around it as they already have.
 |
|
2009-10-23
, 13:27
|
|
Posts: 2,355 |
Thanked: 5,249 times |
Joined on Jan 2009
@ Barcelona
|
#33
|
Originally Posted by mjdavis
Nope, not the same. 256 MiB is RAM. The 256MiB we're talking here is OneNAND, and contains the root filesystem, kernel, boot loader... (basically, firmware).
Up to 1 GB of application memory (256 MB RAM, 768 MB virtual memory)
is spot on with:
http://wiki.maemo.org/Documentation/...opt_and_MyDocs
|
|
2009-10-23
, 13:28
|
|
Posts: 1,208 |
Thanked: 1,028 times |
Joined on Oct 2007
|
#34
|
Originally Posted by javispedro
Yes there is. That's because many of the testers haven't noticed (or don't care?) non optified apps.
Is there any app in extras (-stable) not optified? How could that happen?
|
|
2009-10-23
, 13:32
|
|
Posts: 262 |
Thanked: 232 times |
Joined on Aug 2009
|
#35
|
Originally Posted by javispedro
This is nothing. I've seen people claim the N900 has 256 MB of RAM and swaps on 768 MB of ROM
Nope, not the same. 256 MiB is RAM. The 256MiB we're talking here is OneNAND, and contains the root filesystem, kernel, boot loader... (basically, firmware).
|
|
2009-10-23
, 13:35
|
|
Posts: 388 |
Thanked: 842 times |
Joined on Sep 2009
@ Finland
|
#36
|
Originally Posted by mikkov
So it seems that the QA process is very nice in theory, but does not work in practice. Is it possible to make an automated check for optification to bypass the "human factor"?
Yes there is. That's because many of the testers haven't noticed (or don't care?) non optified apps.
|
|
2009-10-23
, 13:35
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#37
|
Since we already have a clear criteria of optification requirements, it's really something that should be part of of the development process - testers looking into optification process should be the exception (e.g. when there is a good reason for an app or part NOT being optified).
| The Following User Says Thank You to attila77 For This Useful Post: | ||
|
|
2009-10-23
, 13:54
|
|
Posts: 3 |
Thanked: 1 time |
Joined on Sep 2009
|
#38
|
So how do the developers feel about these limitations? Is it really a non-issue and will be corrected once all developers correct their apps to use /opt?
I still feel that the potential to run out of space in / before /opt is full because of the need to place some files in /lib or /etc. Hopefully I'm corrected here as I am seeing the same old Smartphone constraints on our "Mobile Computer" here.
I still feel that the potential to run out of space in / before /opt is full because of the need to place some files in /lib or /etc. Hopefully I'm corrected here as I am seeing the same old Smartphone constraints on our "Mobile Computer" here.
| The Following User Says Thank You to mjdavis For This Useful Post: | ||
|
|
2009-10-23
, 14:05
|
|
Posts: 1,255 |
Thanked: 393 times |
Joined on Oct 2009
@ US
|
#39
|
Originally Posted by mjdavis
Good point. Is there another option for those files, or will certain apps have not choice in order to function correctly? This would suggest a contraint to the installation process.
So how do the developers feel about these limitations? Is it really a non-issue and will be corrected once all developers correct their apps to use /opt?
I still feel that the potential to run out of space in / before /opt is full because of the need to place some files in /lib or /etc. Hopefully I'm corrected here as I am seeing the same old Smartphone constraints on our "Mobile Computer" here.
Man I miss my Amiga- greatest app and memory management evah!
Last edited by Rushmore; 2009-10-23 at 14:20.
 |
|
2009-10-23
, 14:07
|
|
Posts: 1,107 |
Thanked: 720 times |
Joined on Mar 2007
@ Germany
|
#40
|
Agree with javispedro. Any extras-devel app is there for testing and bugreports and should be used as such. Be sure to check any extras-devel app carefully before and after install. I even suggest rebooting after installing an extras-devel app because it might have just trashed your system into reboot-loop.
You can du -s /usr/share/* | sort -n
(and /usr/lib/*) to see what is taking up space on your root fs.
You can du -s /usr/share/* | sort -n
(and /usr/lib/*) to see what is taking up space on your root fs.