I think all of us run into this problem… the free space on a storage medium is getting smaller and smaller and you are not really sure why this is the case. For such cases I use a graphical tool to see the biggest space waster – as I am QT guy I am using filelight.
The last two days I found again some time to hack on the em8300/dxr3 driver. I see the end comming of all my work, but I need to change the way I work. I have renamed the old project on github to v4l2-em8300-old and created a new one. Yes you have heard it correctly – a new one. I think that I have enough knowledge to start from scratch. The new repository can be found here: https://github.com/austriancoder/v4l2-em8300
Every developer should know this – and its a free course… for what are you waiting? Click Me
Lets image you are working on a coreboot port for some mainboard and you are a very glad guy cause you have a jtag interface or something similar and you notice a hang, which could be caused by a never ending loop or some other mysterious stuff – all you know is the current instruction pointer. objdump -S ./build/cbfs/fallback/coreboot_ram.elf and search for the address of the instruction pointer – may it help you to figure out whats going on 🙂
Sometimes it is needed to compare two filesystems, which can be done quite easily: diff -rq /mnt/fs1 /mnt/fs2