du

I was compiling a custom kernel, and I wanted to test the size of the image file. These are the results: ls -la | grep vmlinux -rwxr-xr-x 1 root root 8167158 May 21 12:14 vmlinux du -h vmlinux 3.8M vmlinux size vmlinux text data bss dec hex filename 2221248 676148 544768 3442164 3485f4 vmlinux Since all of them show different sizes, which one is closest to the actual image size? Why are they different? They are all correct, they just show different sizes. ls shows size of the file (when you open and read it, that's how many bytes you will get) du shows actual disk usage which can be smaller

I have a PowerShell script that uses du.exe ( Disk Usage originally from Sysinternals) to calculate the size of directories. If I run du c:\Backup in the console, it works as expected, but the same line of code run in ISE or PowerGui gives the expected result plus the error + du <<<< c:\backup + CategoryInfo : NotSpecified: (:String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError Why is that? How do I avoid this error? I tried invoke-expression, using & , but no go. Thanks for the help. To avoid this you can redirect stderr to null e.g.: du 2> $null Essentially the console

why is the output of du often so different from du -b ? -b is shorthand for --apparent-size --block-size=1 . only using --apparent-size gives me the same result most of the time, but --block-size=1 seems to do the trick. i wonder if the output is then correct even, and which numbers are the ones i want? (i.e. actual filesize, if copied to another storage device) Apparent size is the number of bytes your applications think are in the file. It's the amount of data that would be transferred over the network (not counting protocol headers) if you decided to send the file over FTP or HTTP. It's