Active Topics
-
[HOWTO] Comprehensive Firmware Flashing Guide for N9 (1,580)
to Nokia N9 / N950 by aspergerguy - 10 hrs, 32 mins ago -
Nokia N9-00 Prototype Build S1.12 (RM-680 codename "Dali") (250)
to Nokia N9 / N950 by en0s - 3 days, 6 hrs ago -
[Announce] Maebble - Pebble support for Maemo (118)
to Applications by glo-worm - 3 days, 19 hrs ago -
Possible to flash Leste to eMMC? (6)
to Maemo 7 / Leste by Eri - 4 days, 9 hrs ago - more...
|
2009-12-14
, 08:22
|
|
Posts: 279 |
Thanked: 95 times |
Joined on Sep 2009
|
#22
|
Originally Posted by kyle
when i do vi /etc/fstab there are no entries related to phython. Where else they can be mounted/binded from?
It looks like you have installed some package that was poorly "optified" using bind mounts instead of symbolic links. My guess is that it left some entries in /etc/fstab. If those directories are all empty now then you can just remove the corresponding lines in fstab and be done with it.
|
|
2009-12-14
, 16:10
|
|
Posts: 486 |
Thanked: 251 times |
Joined on Oct 2009
|
#23
|
Originally Posted by Nathan
Why can't the proper spot be in /opt?
Actually the newest version of Python uses a "Bind" method to mount the /opt folder for python. This is NORMAL behavior for python now. This allows all of Python to appear as if it is in the proper spot; but because it is so large and we don't actually want it in the /usr folder.
Nathan
 |
|
2009-12-14
, 16:23
|
|
Posts: 850 |
Thanked: 626 times |
Joined on Sep 2009
@ Vienna, Austria
|
#24
|
Originally Posted by j.s
Well, because!
Why can't the proper spot be in /opt?
__________________
"What we perceive is not nature itself, but nature exposed to our method of questioning."
-- Werner Karl Heisenberg
"What we perceive is not nature itself, but nature exposed to our method of questioning."
-- Werner Karl Heisenberg
|
|
2009-12-14
, 17:25
|
|
Posts: 850 |
Thanked: 626 times |
Joined on Sep 2009
@ Vienna, Austria
|
#26
|
Originally Posted by j.s
no, it's not.
python is an add-on application software package.
it's a runtime library required by other applications and as such part of the system.
__________________
"What we perceive is not nature itself, but nature exposed to our method of questioning."
-- Werner Karl Heisenberg
"What we perceive is not nature itself, but nature exposed to our method of questioning."
-- Werner Karl Heisenberg
 |
|
2009-12-14
, 17:36
|
|
Posts: 445 |
Thanked: 572 times |
Joined on Oct 2009
@ Oxford
|
#27
|
I think it's pretty well established that the 'optification' plan is a grade A ugly hack, so doing something different on the grounds of FHS compliance is eccentric to say the least.
And as for:
And as for:
Originally Posted by wierdo
Surely the obvious solution is to hand craft the symlinks to link whole directories, not each file they contain? Sure, it's more effort than the automatic tool, but no more than manually creating a bind mount based setup is.
Symbolic links take up (a small amount of) space and directory entries. A lot of directory entries if a complex app with a lot of files is run through the optify tool.
For something like python, the bind mounts are far better.
|
|
2009-12-14
, 17:38
|
|
Posts: 1,255 |
Thanked: 393 times |
Joined on Oct 2009
@ US
|
#28
|
The thread title alone is just so wrong
 |
|
2009-12-14
, 18:00
|
|
Posts: 696 |
Thanked: 1,012 times |
Joined on Mar 2006
@ Asturies, Spain
|
#29
|
The optification methods for Python were discussed in the mailing lists, and the best solution was to do the bind method.
Some links on the discussion:
http://lists.maemo.org/pipermail/mae...er/022323.html
http://lists.maemo.org/pipermail/mae...er/021348.html
https://garage.maemo.org/pipermail/p...er/001091.html
There are more places with the python optification discussion, but those three aren't bad for starters.
Some links on the discussion:
http://lists.maemo.org/pipermail/mae...er/022323.html
http://lists.maemo.org/pipermail/mae...er/021348.html
https://garage.maemo.org/pipermail/p...er/001091.html
There are more places with the python optification discussion, but those three aren't bad for starters.
| The Following User Says Thank You to yerga For This Useful Post: | ||
|
|
2009-12-14
, 18:19
|
|
Posts: 65 |
Thanked: 21 times |
Joined on Feb 2008
|
#30
|
Originally Posted by fpp
While I understand what is being described in this thread in a general sense, I'm not at all clear on the practical implications...
There is an optified version but it's not in Extras yet.
Is the current binding version of Python perfectly okay?
Does it place much of a storage burden on root storage space (as suggested earlier in this thread)?
Should we delay and wait for the optified version?
Will the optified version automatically replace the current version when it hits extras? Or do we need to even worry about that at all?
__________________
Just another perl hacker coding python in a bottle.
Just another perl hacker coding python in a bottle.
For something like python, the bind mounts are far better.
And to the OP: They aren't taking up space on /usr. If the tool you are using claims those directories are taking up space on /usr, the tool is broken.