32 points

A good first approximation.

So where in this setup would you mount a network share? Or am additional hard drive for storage? The latter is neither removable nor temporary. Also /run is quite more than what this makes it seem (e.g. user mounts can be located there), there is practically only one system path for executables (/usr/bin)…

Not saying that the graphic is inherently wrong or bad, but one shouldn’t think it’s the end all be all.

permalink
report
reply
7 points

I do /volumX for additional hard drives.

For most network share I use /mnt/$server.

permalink
report
parent
reply
5 points

Or /home/me/drive

permalink
report
parent
reply
9 points

For most network share I use /mnt/$server.

I use /mnt/$proto/$server, though that level of organization was probably overkill. Whatever…

I do /volumX for additional hard drives.

permalink
report
parent
reply
4 points

I’m gonna blow everyone’s mind… I have my Linux system in a relatively small 4gb drive, and my home in a 4Tb drive. I mount my 4tb drive to /home/me as someone already said.

If my SSD for my OS takes a shit as people say, all you do is install it again, change fstab to swap the home directory and you’re back in business like nothing happened. That’s like 10 minutes install time on a good SSD these days. The other guy who mentioned this, didn’t point this out. The idea of separating my home folder into its own drive didn’t occur to me for years and years of using Linux. Every wrong update I was there copying home like a total windows 11 noob. I also install my extra drives and shares on /mnt, that’s standard.

permalink
report
parent
reply
3 points

On debian when i mount an ftp server through my file browser it uses gvfs

This will mount it to /run/user/1000/gvfs/ftp:host=<IP>,port=<PORT>,user=<fpt-user>

permalink
report
parent
reply
20 points

It feels like /opt 's official meaning is completely lost on developers/packagers (depending on who’s at fault), every single directory in my /opt belongs to standalone software that should just be put into either /usr/lib or /usr/share with some symlinks or scripts into /usr/bin.

permalink
report
reply
2 points

I’ve also seen creating there deployment or configuration stack of your choice.

permalink
report
parent
reply
240 points

i always thought /usr stood for “user”. Please tell me I’m not the only one

permalink
report
reply
64 points

You’re not the only one 😅 🙋

permalink
report
parent
reply
40 points

I thought it was United System Resources.
And I still don’t know what’s the point in separating /bin, /sbin, /usr/bin and /usr/sbin.
Also /mnt and /media
Or why it’s /root and not /home/root

permalink
report
parent
reply
6 points

I think /mnt is where you manually mount a hard drive or other device if you’re just doing it temporarily, and /media has sub folders for stuff like cdrom drives or thumb drives?

permalink
report
parent
reply
5 points

Yeah, but why?
You can mount a hard drive anywhere, and why not put all the cdrom and thumbdrive folders in /mnt, too?

permalink
report
parent
reply
4 points

/sbin are system binaries, eg root only stuff, dunno the rest but I would guess there are some historical reasons for the bin usr/bin separation

permalink
report
parent
reply
3 points

I know the distinction between /bin and /sbin, I just don’t know what purpose it serves.

Historically, /bin contained binaries that were needed before /usr was mounted during the boot process (/usr was usually on a networked drive).
Nowadays that’s obsolete, and most distros go ahead and merge the directories.

permalink
report
parent
reply
24 points

/home is often on a separate volume. You’d want root to be available in a maintenance situation where /home may not be mounted.

I don’t recall the reasons for the addition but /media is newer than /mnt.

permalink
report
parent
reply
10 points

I don’t recall the reasons for the addition but /media is newer than /mnt.

Something to do with hard-coded mounts in /etc/fstab vs. dynamically-mounted removable media (USB drives etc.), I think.

permalink
report
parent
reply
47 points

Mostly historical reasons, /home was often a network mounted directory, but /root must be local.

And only regular users have their home in /home

permalink
report
parent
reply
4 points

Idk why I feel compelled to add this info, but / doesn’t have to be local as long as the necessary kernel modules for mounting it are available in the initrd or built into the kernel.

permalink
report
parent
reply
14 points

They hold “system binaries” meant for root user. It’s not a hard distinction but many if not most Linux fundamentals have their roots in very early computing, mainframes, Bell and Xerox, and this good idea has been carried into the here&now. Not sure about the provenance of this one, but it makes sense. isn’t /mnt /media different between distros? These aren’t hard and fast rules - some distros choose to keep files elsewhere from the “standard”.

/bin and /usr/bin, one is typically a symbolic link to another - they used to be stored on disks of different size, cost, and speed.

https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s16.html

https://unix.stackexchange.com/questions/5915/difference-between-bin-and-usr-bin

permalink
report
parent
reply
22 points

And I still don’t know what’s the point in separating /bin, /sbin, /usr/bin and /usr/sbin.

This goes back to the olden days when disk space was measured in kilo and megabytes. /sbin/ and /usr/sbin have the files needed to start a bare bone Unix/Linux system, so that you could boot from a 800kb floppy and mount all other directories via network or other storage devices as needed.

permalink
report
parent
reply
2 points

Is there a reason to keep this structure other than „we’ve always been doing it like that“/backwards compatibility?

permalink
report
parent
reply

@FQQD @sag U So Rong 🙂

permalink
report
parent
reply
20 points

I think it originally did under old Unix, it was what /home is nowadays; “Unix System Resources” is a backronym.

permalink
report
parent
reply
3 points
*

You are correct and this can be seen in some of the old AT&T demos from the '80s floating around on YouTube. There is even a chart that specifically labels a directory like /usr/bwk as the user’s home.

Plan 9 also uses this old convention; users live under /usr and there is no /home.

permalink
report
parent
reply
80 points

Ken Thompson and Dennis Ritchie created Unix on a PDP-7 in 1969. Well around 1971 they upgraded to a PDP-11 with a pair of RK05 disk packs (1.5 megabytes each) for storage.

When the operating system grew too big to fit on the first RK05 disk pack (their root filesystem) they let it leak into the second one, which is where all the user home directories lived (which is why the mount was called /usr). They replicated all the OS directories under there (/bin, /sbin, /lib, /tmp…) and wrote files to those new directories because their original disk was out of space. When they got a third disk, they mounted it on /home and relocated all the user directories to there so the OS could consume all the space on both disks and grow to THREE WHOLE MEGABYTES. And thereafter /usr is used to store user programs while /home is used to store user data.

source: http://lists.busybox.net/pipermail/busybox/2010-December/074114.html

permalink
report
parent
reply
19 points

THREE WHOLE MEGABYTES

Me in 2024 holding a 4TB NVMe stick: Still not enough (it’s never enough)

permalink
report
parent
reply
2 points

Same, but with a 22TB drive for /data loooool

permalink
report
parent
reply
10 points

This thread is 3 MB

permalink
report
parent
reply
4 points

Yup same. I always wondered why there was a user folder when we already have home.

permalink
report
parent
reply
4 points

Same. I actually feel like I remember the professor of my only unix class saying that. Hoping I’m wrong.

permalink
report
parent
reply
5 points

I was just about to post the same thing. I’ve been using Linux for almost 10 years. I never really understood the folder layout anyway into this detail. My reasoning always was that /lib was more system-wide and /usr/lib was for stuff installed for me only. That never made sense though, since there is only one /usr and not one for every user. But I never really thought further, I just let it be.

permalink
report
parent
reply
16 points

It’s always been for USeR binaries. It’s the first time I’ve seen this bizarre backronym (40 years of Unix here).

permalink
report
parent
reply
3 points

Likewise.

It’s also only just now dawning on me /bin is short for /binaries. I always thought it was like… A bin. like a junk drawer hidden in a cupboard

permalink
report
parent
reply
5 points

immuatables be all about /var

permalink
report
reply
4 points

NixOS enters the room wearing a “/nix/store” t-shirt.

permalink
report
parent
reply
2 points

Nix really has a kickass way of doing this. Won’t conflict anywhere and always let’s you know what is managed by Nix.

permalink
report
parent
reply
2 points

A blast from the past!

permalink
report
reply

Linux

!linux@lemmy.ml

Create post

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word “Linux” in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

  • Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
  • No misinformation
  • No NSFW content
  • No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

Community stats

  • 6.7K

    Monthly active users

  • 4.1K

    Posts

  • 56K

    Comments