/bin

>$PATH

Attached: 1554758154807.jpg (971x565, 139K)

Flatpak doesn't have this problem

man hier

Attached: paulquits.jpg (612x612, 186K)

>kernel binaries
>C:\Windows\System32
>C:\Windows\SysWOW64
Notice how on an x86_64 system, system32 holds 64-bit binaries and syswow64 holds 32-bit binaries.
>%PATH%
>/app/bin

you forgot /usr/local/bin you absolute fuck

what if you're a non binary?

take solace in the fact that you can't be executed

man hier didn't werk for me anymore.
>Found man file-hierarchy by running whatis -s 7 -r . , tho.

Damn... UNIX is really elegant and well-designed...

Fucking linuxfags

/bin/ : Core system binaries
/sbin/ : Core system super user binaries
/usr/bin/ : Common binaries included in most installs
/usr/sbin/ : Common super user binaries included in most installs
/usr/local/bin/ : User installed binaries
/usr/local/sbin/ : User installed super user binaries

Attached: 1554666474347.jpg (538x513, 106K)

I know. It's fucking retarded they redirect 32-bit programs to new paths instead of letting them be and making new directories for 64-bit programs instead.
Redirects are sometimes faulty and a 32 bit program still installs into 64 bit programs' directory.
C:\Program Files
C:\Program Files (amd64)
C:\Windows
C:\Windows\System32
C:\Windows\System64
These directories make more sense.

The only reason of this separation that the UNIX greybeards didn't have enough disk space on their PDP-11 machines, so they had to move half of the binaries to an another disk mounted at usr. And people just blindly followed their nonsense after that.

UNIX filesystem hierarchy is the lowest effort and highest efficiency gatekeeping.

>a 32 bit program still installs into 64 bit programs' directory.
Or worse, a 64 bit program installs to the 32 bit program directory. Looking at you, Chrome.

Attached: 1519351612398.jpg (404x500, 92K)

steam's default library is also in 32 bit programs
dunno if steam itself is 32 bit, but all games in the default library will run out of the 32 bit folder, regardless of what they are

Why do winfags still use 32-bit software in 2019?

>/usr/share/docs
>/usr/docs
no such thing
>/usr/doc
it's been removed, the only distro that I ever seen that still use it is a niche distro like slackware
similar to /usr/man

>linuxfags
*unix-likefags

/lib
/lib32
/lib64

FreeBSD doesn't install binaries to /usr/bin/

name something more infuriating than
~/.shitprogram.conf
KEEP YOUR SHIT IN ~/.local AND ~/.config AND ~/.cache YOU FUCKING IDIOTS AND STOP LITTERING MY HOME FOLDER

~/shitprogram.conf

These are the worst ones. Fucking PacketTracer

ebin

>/

but it has /usr/local/bin dumbfuck

Yes, and it's used as the main directory for user installed binaries, unlike Linux which almost always uses /usr/bin/.
Linux and FreeBSD are both Unix-likes, but they use different filesystem hierarchies.

Attached: 7bd890922780e874faee9d3307e08bec.png (600x600, 304K)

~/Shit_Ported_Windows_Game/shit_config.wtfdb

>user installed binaries
read
>/usr/local/bin/ : User installed binaries

You're reading it wrong. "User installed binaries" means the stuff you install after install. Pretty much anything you install with a package manager is put in /usr/local/bin/ or /usr/local/sbin/ on FreeBSD.
With Linux package managers almost always install to /usr/bin/ and /usr/sbin/.
The hierarchy is different.

>Notice how on an x86_64 system, system32 holds 64-bit binaries and syswow64 holds 32-bit binaries.
That's ugly, because system32 is the default place for $current_arch. Syswow64 means sys Windows on Windows64

/boot/
/cmd/
/dev/
/etc/
/lib/
/opt/
- /opt/debian
- /opt/arch
/proc/
/sys/
/var/

>not running a tiny custom Busybox/Linux setup with chroots for distro packages
shig

>*BSD
>Yes, and it's used as the main directory for user installed binaries
>Linux
>User installed binaries
Why are you using the same term?

/usr/bin/ on FreeBSD contains the userland that's installed with the system.
/bin/ contains only the bare essentials that are central to the system itself such as pwd, cp, date, dd, echo, etc.
On Linux, /bin/ contains most of the userland
/usr/bin contains the rest, as well as any packages installed through package managers.
/usr/local/bin is where user installed binaries are placed, such as ones they compiled/downloaded themselves.
Different hierarchies for the exact same directories.

Attached: Hata.no.Kokoro.full.1544783.jpg (800x1090, 995K)

~/.shitprogram.conf is worse than ~/shitprogram.conf though, I don't see a reason to hide config files as those are the files you edit the most.

C:\Users\{Username}\.Average_from_linux_ported_program\
%userprofile%\.Average_from_linux_ported_program\
People who do this should get fucking gassed.
You wouldn't like me storing shit in /C/Users/{username}/Shit_program/ on Linux either.

Gobo Linux is more based than Gentoo
Change my mind

Attached: 2019-04-12_23-53.png (1581x726, 994K)

>/usr/local/bin
>/opt/bin

Seriously, the UNIX filesystem hierarchy is a complete clusterfuck.
All directories just mean something entirely different on different operating systems and most of the reasons for the different subdirectories don't even exist anymore.

it's very interesting but man the repository is sparse

/usr/local/bin either on linux or bsd is the same, it's just the package manager that decides where to put them
also stop avatarfagging, reaction pics are fine

They're similar, not the same.
freebsd.org/cgi/man.cgi?query=hier&sektion=7&manpath=freebsd-release-ports
/usr/ contains the majority of user utilities and applications
local/ local executables, libraries, etc. Also used as
the default destination for the ports(7) framework.
Within local/, the general layout sketched out by
hier for /usr should be used. Exceptions are the
man directory (directly under local/ rather than
under local/share/), ports documentation (in
share/doc/_port_/), and /usr/local/etc (mimics
/etc).

linux.die.net/man/7/hier
/usr/local
This is where programs which are local to the site typically go.

/usr/local/ is not just a package manager choice. It affects everything from where your daemon config files are (/usr/local/etc/) to where your webserver and even home dir are (/usr/local/www/ and /usr/local/home/ respectively).
And I'm not avatar fagging. All my images were reaction pictures. One was smug, one was angry, one was neutral in the face of an argument.

I meant /usr/home/ not /usr/local/home.

Steam is 32-bit

This thread gave me cancer

Sage

>t. linux foundation

bump

>/usr/bin is for user-installed/packaged binaries
Wrong. It's literally just because Ken Thompson and Dennis Ritchie ran out of space on their PDP-7 root filesystem. They added an expansion disk at /usr to store new programs that couldn't fit in root, but you still have to keep enough programs in root to boot the system and mount /usr. We have initramfs now so that's redundant.