Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 2 days, 6 hrs ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 2 days, 7 hrs ago -
Maemo repository (3)
to Community by torsen - 2 days, 22 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 3 days, 20 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 5 days, 2 hrs ago - more...
|
2009-12-20
, 23:04
|
|
Posts: 236 |
Thanked: 223 times |
Joined on Oct 2009
@ NE UK
|
#42
|
Originally Posted by fnordianslip
The -x switch is supposed to make it not do that.
Might it be the case that du follows links into other file-systems and includes the size of their contents?
-x, --one-file-system
skip directories on different file systems
Maybe that's not operational here, where du is just a symlink to busybox. But it claims to support the switch:
~ $ du --help
BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso26+0m5) multi-call binary
Usage: du [-aHLdclsxhmk] [FILE]...
| The Following User Says Thank You to kwotski For This Useful Post: | ||
|
|
2009-12-20
, 23:11
|
|
Posts: 1,208 |
Thanked: 1,028 times |
Joined on Oct 2007
|
#43
|
Originally Posted by roamerjiang
Maybe you should show step by step what is the problem? According to your previous message package was properly uninstalled.
i just reinstalled the mplayer, and then uninstalled it again from application manager, but result is still the same. any suggestion that i can uninstall it properly? thank you very much because my fbreader also get same problem
|
|
2009-12-21
, 03:27
|
|
Posts: 62 |
Thanked: 10 times |
Joined on Oct 2009
|
#44
|
Originally Posted by mikkov
thanks for your reply. I'm sorry that i'm quite new to linux system. how can i show it step by step? or is there any command link i can use in xterminal to do that?
Maybe you should show step by step what is the problem? According to your previous message package was properly uninstalled.
|
|
2009-12-21
, 08:17
|
|
Posts: 236 |
Thanked: 223 times |
Joined on Oct 2009
@ NE UK
|
#45
|
Originally Posted by roamerjiang
I think he's just asking for you to explain what your problem is, slowly and thoroughly, one step at a time.
thow can i show it step by step?
If you read the posts above, it's been said a couple of times that the dpkg output you posted looks normal. i.e. the "problem" is not visible.
|
|
2009-12-21
, 14:16
|
|
Posts: 278 |
Thanked: 209 times |
Joined on Dec 2009
|
#46
|
I've completed the list of non-opt usage in the first post. Hope it's useful for some
|
|
2009-12-21
, 19:19
|
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#47
|
Originally Posted by roamerjiang
Maybe I can help you guys here. If you are receiving this information when using dpkg then mplayer is removed from your system. That first field that says "RC" means that the package was removed, but configuration files left.
~ $ dpkg -l mplayer
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
rc mplayer 1.0svn4 The Ultimate Movie Player port for N900
If dpkg --purge was used to remove the package, or the package was never installed, then the first two letters would be "un". If the package is installed, you would see "ii".
Another, more english way to view this, is using:
Code:
~$ dpkg --status xserver-xephyr Package: xserver-xephyr Status: unknown ok not-installed Priority: optional Section: x11
|
|
2009-12-22
, 07:14
|
|
Posts: 118 |
Thanked: 45 times |
Joined on Dec 2009
@ Germany
|
#48
|
Originally Posted by kwotski
I changed your script, so that the line
The -x switch is supposed to make it not do that.
Maybe that's not operational here, where du is just a symlink to busybox. But it claims to support the switch:
$du = `du -s /$_`;
now is
$du = `du -xs /$_`;
But it looks like "du" still follows the links. I tried in on mc which I manually moved away from rootfs. Although I'm not sure what your script does at that point of time - or in which directory "du" thinks it is.
Sorry, but I don't know perl - the only thing is that I heard people say it is a write only language (no read
).So, does anyone now, how to modify that script to don't follow symbolic links?
 |
|
2009-12-22
, 10:43
|
|
Posts: 850 |
Thanked: 626 times |
Joined on Sep 2009
@ Vienna, Austria
|
#49
|
"du" does NOT follow symbolic links, i just tested it.
btw, -P is the du-switch to deactivate symlinks, but it's not present on the tablet, and it's supposed to be default anyways.
what makes you say that du follows links? any hard evidence?
btw, -P is the du-switch to deactivate symlinks, but it's not present on the tablet, and it's supposed to be default anyways.
what makes you say that du follows links? any hard evidence?
__________________
"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-22
, 11:06
|
|
Posts: 236 |
Thanked: 223 times |
Joined on Oct 2009
@ NE UK
|
#50
|
I didn't actually test this before posting the script, because I assumed du behaviour would be normal (i.e. don't follow symlinks) but here's a quick test which seems to show it is normal:
the -x switch is not relevant to symlinks in particular. It's to tell du not to look at disk usage on separate filesystems which are mounted under the directory it's looking at.
So
du -s /
would give the disk usage for everything under / including /home and /home/user/MyDocs, which are separate filesystems, but
du -sx /
would only give the disk usage for the filesystem that / was part of.
Or, to give another example:
The first result is bigger because it's counting /home/user/MyDocs. The second result doesn't look at that, because it's a separate mount to /home, and the -x switch has been given.
So in short the script shouldn't need any change to do the Right Thing in relation to symlinks 
Edit:
Nope, it did the Wrong Thing in relation to symlinked directories. Please get the new version (from the original place) if you're having trouble with that.
Last edited by kwotski; 2009-12-23 at 10:50.
~# mkdir ttt
~# ln -s /usr/share ttt/test
~# ln -s /usr/share test2
~# du -s /usr/share
76716 /usr/share
~# du -s ttt test2 /usr/share
0 ttt
0 test2
76716 /usr/share
~#
So
du -s /
would give the disk usage for everything under / including /home and /home/user/MyDocs, which are separate filesystems, but
du -sx /
would only give the disk usage for the filesystem that / was part of.
Or, to give another example:
# du -s /home
2195060 /home
~# du -sx /home
204468 /home
the script shouldn't need any change to do the Right Thing in relation to symlinks Edit:
Nope, it did the Wrong Thing in relation to symlinked directories. Please get the new version (from the original place) if you're having trouble with that.
Last edited by kwotski; 2009-12-23 at 10:50.
Class .. : Lame hacker & beardy boffin
Humour . : [#######---] Alignment: Apathetic anarchist
Patience : [####------] Weapon(s): My cat, my code.
Agro ... : |#---------] Relic(s) : N900, MacBookPro, NSLU2, N800, SheevaPlug, Eee-901, Core2-Quad, PS3
"In theory, theory and practice are the same. In practice, they're not."
--
Beware of extras-devel.