I think I officially have a hoarding problem...
this post was submitted on 30 Jun 2026
262 points (98.2% liked)
Selfhosted
60409 readers
1063 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Pardon my stupidity BUT why include stdout to Devnull? Why not omit and simply 'du -sh /home'
There’s probably a bunch of permissions errors, filesystems warnings for cross-filesystem mounts or links, etc. all going to stderr. Linux output streams are a bit odd, 1 is stdout and 2 is stderr. So the command is redirecting the “noise” to null and just printing the actual command output. That would be my assessment, but OP could probably give a more correct answer..!
Nope, you are exactly on.
Noob, just use sudo, less chars!
Oddly enough, still generates errors. (There are stuff in user directories that are set to 600.... so even root can't browse/open.)
Are you sure? Root can see everything.
On a network, it can't.
NFS mount probably.
Well now I have to try this. Missing that executable bit would make sense. But last time I did this on / I didn't get errors 🤔
There's also some stuff in Proc and run that won't let you.
2> means stderr.... Keeps the "can't access ...." Out of the display.
That's stderr, not stdout