4

Querying partitionmananger --help does not document any verbose mode. Even gparted --help is not implemented. I wish I could use any --verbose mode without more esoteric thingy like using ltrace, because unless checking their sources one can not know if they resort only on libparted or some operations are performed using system commands, hence not being traced.

I don't know nesting strace on ltrace or vice-versa... I guess that would be a lot of standard output?

How to learn what gparted, partitionmanager... libcalls or fdisk, parted... commands are wrapping? I want to learn to use parted and fdisk in order not to need to rely on GUI interfaces such as gparted or partitionmanager, as I currently more or less know how to use the lvm suite of operations but not the more arcane fdisk and parted, but I guess it should help a lot watching actual examples of parted, fdisk and libparted being invoked by the user use of, for instance, gparted.

174140
  • 134

1 Answers1

3

If I understand your question correctly (and I might not), then I think that you wish to determine which libraries are being used by a particular application. In this case ldd is your friend.

ldd /path/to/binary

gparted is actually a script (well it is on my Debian Wheezy box), and to determine the executables which are being called, simply cat /usr/sbin/gparted and read the script. When you find the exectuable files you are interested in, you can run ldd to determine which libraries are being linked to.

If you want a more verbose answer for a particular application, you can always download the source code if the software is open source, and have a look there. Usually you will find a file called INSTALL ( you can get from package developer's website or in most GNU/Linux distributions you may find it also in /usr/share/doc/) which tell you which libraries the software depends on before you can compile it.

gerlos
  • 632
glapworth
  • 86