• 0 Posts
  • 6 Comments
Joined 1 year ago
cake
Cake day: June 29th, 2024

help-circle

  • The only thing I still use Postman for at work is when running API performance benchmarks, as I wasn’t yet motivated enough to write a curl wrapper to do such tests and plot the results. Especially when doing things like ramp up etc. it becomes more than a simple for-loop.

    Can someone recommend an existing command line tool for that?


  • Do most packages usually have a manual entry ?

    Usually there are manual pages for commands, for libraries and drivers like libwacom it is less common, and they are not necessarily the same as the package name. Some packages also just have a Readme file or an HTML manual installed under /usr/share/doc or similar.

    When unsure, I often just check the list of files that belong to a package, most package managers can do it. E.g. on Debian-based (i.e. apt using) distros, dpkg -L $packagename will list it, in arch based distros it is pacman -Ql $packagename.




  • My theory for why it created copies: The files you listed look like they are all subdirectories from /dev, which is (usually) a separate filesystem. When you try to move a file or directory across filesystems, the OS can’t just change the link, it has to actually copy the files and then remove the original. As a directory is a set of links to files, and the copies are different files, directories are just newly created with the same name in the new location instead of copying the directory filesystem entry. It looks like mv creates these target directories, before it checks if it actually has permission to remove the source, but checks file permissions, before it copies them