▲ 1215 ▼ Linux Directory Structure - FHS (lemm.ee) submitted 2 years ago* (last edited 2 years ago) by sag@lemm.ee to c/linux@lemmy.ml 193 comments fedilink hide all child comments
[–] geneva_convenience@lemmy.ml 62 points 2 years ago* (4 children) wait /usr doesn't mean user? /etc has to be the worst name in there permalink fedilink source hideshow 8 child comments replies: [–] cogman@lemmy.world 34 points 2 years ago (2 children) usr does mean user. It was the place for user managed stuff originally. The home directory used to be a sub directory of the usr directory. The meaning and purpose of unix directories has very organically evolved. Heck, it's still evolving. For example, the new .config directory in the home directory. permalink fedilink source parent hideshow 4 child comments replies: [–] JATtho@lemmy.world 16 points 2 years ago* For example, the new .config directory in the home directory. I hope slowly but surely no program will ever dump its config(s) as ~/.xyz.conf (or even worse in a program specific ~/.thisapp/; The ~/.config/ scheme works as long as the programs don't repeat the bad way of dumping files as ~/.config/thisconfig.txt. (I'm looking at you kde folks..) A unique dir in .config directory should be mandatory. If I ever need to shed some cruft accumulated over the years in ~/.config/ this would make it a lot easier. permalink fedilink source parent [–] AngryCommieKender@lemmy.world -2 points 2 years ago (1 child) Per the graphic, it means Unix System Resources.... permalink fedilink source parent hideshow 2 child comments replies: [–] dafo@lemmy.world 12 points 2 years ago* (3 children) I don't trust a graphic which explains /boot as "system boot loader files"... permalink fedilink source parent hideshow 6 child comments replies: [–] Peter1986C@lemmings.world 4 points 2 years ago It kind of makes sense on many BIOS/UEFI-less systems where e.g. Uboot is used. And it does contain things like kernel images, sometimes initRD files etc. (which may not be bootloader files but are still system boot files). permalink fedilink source parent [–] irreticent@lemmy.world 4 points 2 years ago (1 child) Why? What's inaccurate about it? I have no idea and would like to learn. permalink fedilink source parent hideshow 2 child comments replies: [–] dafo@lemmy.world 10 points 2 years ago* It's not wrong, but it feels a bit like some tech articles you'll see which are obviously just created to fluff up a CV. I wouldn't say avyttring here is flat out wrong, just kinda... lacking. But yeah, /boot holds "system boot loader files", sure, but that's a bit vague. It should contain your kernel and initramcpio and IIRC Grub also had its config here. That's pretty much it. I would've rather said /boot contains the kernel. "device files" it's so vague that it's almost wrong IMO. At first glaze I would've thought that it means drivers rather than, say, "interfaces to devices" permalink fedilink source parent [–] AngryCommieKender@lemmy.world 1 point 2 years ago Well that's a shame for me. This graphic finally made the Linux file directory structure make sense to me permalink fedilink source parent [–] filcuk@lemmy.zip 11 points 2 years ago (4 children) I wonder why that isn't /cfg? Is there a historical reason? permalink fedilink source parent hideshow 8 child comments replies: [–] CrabAndBroom@lemmy.ml 21 points 2 years ago (1 child) According to this, it's been around since the 70's and was originally just a catch-all for files that didn't fit in the other default directories, but over time has come to be mostly used for config files. I assume it would cause utter mayhem to try and change the name now so I guess it just sticks. Someone suggested "Edit To Configure" as a backronym to try and make it make more sense if that helps anyone lol. permalink fedilink source parent hideshow 2 child comments replies: [–] ulterno@lemmy.kde.social 6 points 2 years ago I too expected it to be "et cetera". permalink fedilink source parent [–] cm0002@lemmy.world 10 points 2 years ago (1 child) Is there a historical reason? If you're asking that in anything Linux related, it's probably a Yes 99% of the time LMAO permalink fedilink source parent hideshow 2 child comments replies: [–] orangeboats@lemmy.world 8 points 2 years ago (2 children) Not just Linux... 99% of the time you see something weird in the computing world, the reason is going to be "because history." permalink fedilink source parent hideshow 4 child comments replies: [–] cm0002@lemmy.world 8 points 2 years ago Looks at the entire networking stack Yup (unfortunately) permalink fedilink source parent [–] Myavatargotsnowedon@lemmy.ml 2 points 2 years ago Windows 11 is still reserving A and B drive for floppy discs. permalink fedilink source parent [–] pixelblut@feddit.org 2 points 2 years ago Try naming a folder "CON" in Windows and learn the magic of old spaghetti code by a multi billion dollar company. permalink fedilink source parent [–] Revan343@lemmy.ca 1 point 2 years ago It's probably the standard in both POSIX and the Single UNIX Specification, so I guess ask Ken Thompson? permalink fedilink source parent [–] InverseParallax@lemmy.world 2 points 2 years ago It meant user, as in user-installed programs and libraries for this system over the core system programs and libraries of the operating system in /bin and /lib. Someone learned it wrong, but otherwise I think the image is right. permalink fedilink source parent [+] Laser@feddit.org 1 point 2 years ago [deleted] permalink fedilink source parent
[–] cogman@lemmy.world 34 points 2 years ago (2 children) usr does mean user. It was the place for user managed stuff originally. The home directory used to be a sub directory of the usr directory. The meaning and purpose of unix directories has very organically evolved. Heck, it's still evolving. For example, the new .config directory in the home directory. permalink fedilink source parent hideshow 4 child comments replies: [–] JATtho@lemmy.world 16 points 2 years ago* For example, the new .config directory in the home directory. I hope slowly but surely no program will ever dump its config(s) as ~/.xyz.conf (or even worse in a program specific ~/.thisapp/; The ~/.config/ scheme works as long as the programs don't repeat the bad way of dumping files as ~/.config/thisconfig.txt. (I'm looking at you kde folks..) A unique dir in .config directory should be mandatory. If I ever need to shed some cruft accumulated over the years in ~/.config/ this would make it a lot easier. permalink fedilink source parent [–] AngryCommieKender@lemmy.world -2 points 2 years ago (1 child) Per the graphic, it means Unix System Resources.... permalink fedilink source parent hideshow 2 child comments replies: [–] dafo@lemmy.world 12 points 2 years ago* (3 children) I don't trust a graphic which explains /boot as "system boot loader files"... permalink fedilink source parent hideshow 6 child comments replies: [–] Peter1986C@lemmings.world 4 points 2 years ago It kind of makes sense on many BIOS/UEFI-less systems where e.g. Uboot is used. And it does contain things like kernel images, sometimes initRD files etc. (which may not be bootloader files but are still system boot files). permalink fedilink source parent [–] irreticent@lemmy.world 4 points 2 years ago (1 child) Why? What's inaccurate about it? I have no idea and would like to learn. permalink fedilink source parent hideshow 2 child comments replies: [–] dafo@lemmy.world 10 points 2 years ago* It's not wrong, but it feels a bit like some tech articles you'll see which are obviously just created to fluff up a CV. I wouldn't say avyttring here is flat out wrong, just kinda... lacking. But yeah, /boot holds "system boot loader files", sure, but that's a bit vague. It should contain your kernel and initramcpio and IIRC Grub also had its config here. That's pretty much it. I would've rather said /boot contains the kernel. "device files" it's so vague that it's almost wrong IMO. At first glaze I would've thought that it means drivers rather than, say, "interfaces to devices" permalink fedilink source parent [–] AngryCommieKender@lemmy.world 1 point 2 years ago Well that's a shame for me. This graphic finally made the Linux file directory structure make sense to me permalink fedilink source parent
[–] JATtho@lemmy.world 16 points 2 years ago* For example, the new .config directory in the home directory. I hope slowly but surely no program will ever dump its config(s) as ~/.xyz.conf (or even worse in a program specific ~/.thisapp/; The ~/.config/ scheme works as long as the programs don't repeat the bad way of dumping files as ~/.config/thisconfig.txt. (I'm looking at you kde folks..) A unique dir in .config directory should be mandatory. If I ever need to shed some cruft accumulated over the years in ~/.config/ this would make it a lot easier. permalink fedilink source parent
[–] AngryCommieKender@lemmy.world -2 points 2 years ago (1 child) Per the graphic, it means Unix System Resources.... permalink fedilink source parent hideshow 2 child comments replies: [–] dafo@lemmy.world 12 points 2 years ago* (3 children) I don't trust a graphic which explains /boot as "system boot loader files"... permalink fedilink source parent hideshow 6 child comments replies: [–] Peter1986C@lemmings.world 4 points 2 years ago It kind of makes sense on many BIOS/UEFI-less systems where e.g. Uboot is used. And it does contain things like kernel images, sometimes initRD files etc. (which may not be bootloader files but are still system boot files). permalink fedilink source parent [–] irreticent@lemmy.world 4 points 2 years ago (1 child) Why? What's inaccurate about it? I have no idea and would like to learn. permalink fedilink source parent hideshow 2 child comments replies: [–] dafo@lemmy.world 10 points 2 years ago* It's not wrong, but it feels a bit like some tech articles you'll see which are obviously just created to fluff up a CV. I wouldn't say avyttring here is flat out wrong, just kinda... lacking. But yeah, /boot holds "system boot loader files", sure, but that's a bit vague. It should contain your kernel and initramcpio and IIRC Grub also had its config here. That's pretty much it. I would've rather said /boot contains the kernel. "device files" it's so vague that it's almost wrong IMO. At first glaze I would've thought that it means drivers rather than, say, "interfaces to devices" permalink fedilink source parent [–] AngryCommieKender@lemmy.world 1 point 2 years ago Well that's a shame for me. This graphic finally made the Linux file directory structure make sense to me permalink fedilink source parent
[–] dafo@lemmy.world 12 points 2 years ago* (3 children) I don't trust a graphic which explains /boot as "system boot loader files"... permalink fedilink source parent hideshow 6 child comments replies: [–] Peter1986C@lemmings.world 4 points 2 years ago It kind of makes sense on many BIOS/UEFI-less systems where e.g. Uboot is used. And it does contain things like kernel images, sometimes initRD files etc. (which may not be bootloader files but are still system boot files). permalink fedilink source parent [–] irreticent@lemmy.world 4 points 2 years ago (1 child) Why? What's inaccurate about it? I have no idea and would like to learn. permalink fedilink source parent hideshow 2 child comments replies: [–] dafo@lemmy.world 10 points 2 years ago* It's not wrong, but it feels a bit like some tech articles you'll see which are obviously just created to fluff up a CV. I wouldn't say avyttring here is flat out wrong, just kinda... lacking. But yeah, /boot holds "system boot loader files", sure, but that's a bit vague. It should contain your kernel and initramcpio and IIRC Grub also had its config here. That's pretty much it. I would've rather said /boot contains the kernel. "device files" it's so vague that it's almost wrong IMO. At first glaze I would've thought that it means drivers rather than, say, "interfaces to devices" permalink fedilink source parent [–] AngryCommieKender@lemmy.world 1 point 2 years ago Well that's a shame for me. This graphic finally made the Linux file directory structure make sense to me permalink fedilink source parent
[–] Peter1986C@lemmings.world 4 points 2 years ago It kind of makes sense on many BIOS/UEFI-less systems where e.g. Uboot is used. And it does contain things like kernel images, sometimes initRD files etc. (which may not be bootloader files but are still system boot files). permalink fedilink source parent
[–] irreticent@lemmy.world 4 points 2 years ago (1 child) Why? What's inaccurate about it? I have no idea and would like to learn. permalink fedilink source parent hideshow 2 child comments replies: [–] dafo@lemmy.world 10 points 2 years ago* It's not wrong, but it feels a bit like some tech articles you'll see which are obviously just created to fluff up a CV. I wouldn't say avyttring here is flat out wrong, just kinda... lacking. But yeah, /boot holds "system boot loader files", sure, but that's a bit vague. It should contain your kernel and initramcpio and IIRC Grub also had its config here. That's pretty much it. I would've rather said /boot contains the kernel. "device files" it's so vague that it's almost wrong IMO. At first glaze I would've thought that it means drivers rather than, say, "interfaces to devices" permalink fedilink source parent
[–] dafo@lemmy.world 10 points 2 years ago* It's not wrong, but it feels a bit like some tech articles you'll see which are obviously just created to fluff up a CV. I wouldn't say avyttring here is flat out wrong, just kinda... lacking. But yeah, /boot holds "system boot loader files", sure, but that's a bit vague. It should contain your kernel and initramcpio and IIRC Grub also had its config here. That's pretty much it. I would've rather said /boot contains the kernel. "device files" it's so vague that it's almost wrong IMO. At first glaze I would've thought that it means drivers rather than, say, "interfaces to devices" permalink fedilink source parent
[–] AngryCommieKender@lemmy.world 1 point 2 years ago Well that's a shame for me. This graphic finally made the Linux file directory structure make sense to me permalink fedilink source parent
[–] filcuk@lemmy.zip 11 points 2 years ago (4 children) I wonder why that isn't /cfg? Is there a historical reason? permalink fedilink source parent hideshow 8 child comments replies: [–] CrabAndBroom@lemmy.ml 21 points 2 years ago (1 child) According to this, it's been around since the 70's and was originally just a catch-all for files that didn't fit in the other default directories, but over time has come to be mostly used for config files. I assume it would cause utter mayhem to try and change the name now so I guess it just sticks. Someone suggested "Edit To Configure" as a backronym to try and make it make more sense if that helps anyone lol. permalink fedilink source parent hideshow 2 child comments replies: [–] ulterno@lemmy.kde.social 6 points 2 years ago I too expected it to be "et cetera". permalink fedilink source parent [–] cm0002@lemmy.world 10 points 2 years ago (1 child) Is there a historical reason? If you're asking that in anything Linux related, it's probably a Yes 99% of the time LMAO permalink fedilink source parent hideshow 2 child comments replies: [–] orangeboats@lemmy.world 8 points 2 years ago (2 children) Not just Linux... 99% of the time you see something weird in the computing world, the reason is going to be "because history." permalink fedilink source parent hideshow 4 child comments replies: [–] cm0002@lemmy.world 8 points 2 years ago Looks at the entire networking stack Yup (unfortunately) permalink fedilink source parent [–] Myavatargotsnowedon@lemmy.ml 2 points 2 years ago Windows 11 is still reserving A and B drive for floppy discs. permalink fedilink source parent [–] pixelblut@feddit.org 2 points 2 years ago Try naming a folder "CON" in Windows and learn the magic of old spaghetti code by a multi billion dollar company. permalink fedilink source parent [–] Revan343@lemmy.ca 1 point 2 years ago It's probably the standard in both POSIX and the Single UNIX Specification, so I guess ask Ken Thompson? permalink fedilink source parent
[–] CrabAndBroom@lemmy.ml 21 points 2 years ago (1 child) According to this, it's been around since the 70's and was originally just a catch-all for files that didn't fit in the other default directories, but over time has come to be mostly used for config files. I assume it would cause utter mayhem to try and change the name now so I guess it just sticks. Someone suggested "Edit To Configure" as a backronym to try and make it make more sense if that helps anyone lol. permalink fedilink source parent hideshow 2 child comments replies: [–] ulterno@lemmy.kde.social 6 points 2 years ago I too expected it to be "et cetera". permalink fedilink source parent
[–] ulterno@lemmy.kde.social 6 points 2 years ago I too expected it to be "et cetera". permalink fedilink source parent
[–] cm0002@lemmy.world 10 points 2 years ago (1 child) Is there a historical reason? If you're asking that in anything Linux related, it's probably a Yes 99% of the time LMAO permalink fedilink source parent hideshow 2 child comments replies: [–] orangeboats@lemmy.world 8 points 2 years ago (2 children) Not just Linux... 99% of the time you see something weird in the computing world, the reason is going to be "because history." permalink fedilink source parent hideshow 4 child comments replies: [–] cm0002@lemmy.world 8 points 2 years ago Looks at the entire networking stack Yup (unfortunately) permalink fedilink source parent [–] Myavatargotsnowedon@lemmy.ml 2 points 2 years ago Windows 11 is still reserving A and B drive for floppy discs. permalink fedilink source parent
[–] orangeboats@lemmy.world 8 points 2 years ago (2 children) Not just Linux... 99% of the time you see something weird in the computing world, the reason is going to be "because history." permalink fedilink source parent hideshow 4 child comments replies: [–] cm0002@lemmy.world 8 points 2 years ago Looks at the entire networking stack Yup (unfortunately) permalink fedilink source parent [–] Myavatargotsnowedon@lemmy.ml 2 points 2 years ago Windows 11 is still reserving A and B drive for floppy discs. permalink fedilink source parent
[–] cm0002@lemmy.world 8 points 2 years ago Looks at the entire networking stack Yup (unfortunately) permalink fedilink source parent
[–] Myavatargotsnowedon@lemmy.ml 2 points 2 years ago Windows 11 is still reserving A and B drive for floppy discs. permalink fedilink source parent
[–] pixelblut@feddit.org 2 points 2 years ago Try naming a folder "CON" in Windows and learn the magic of old spaghetti code by a multi billion dollar company. permalink fedilink source parent
[–] Revan343@lemmy.ca 1 point 2 years ago It's probably the standard in both POSIX and the Single UNIX Specification, so I guess ask Ken Thompson? permalink fedilink source parent
[–] InverseParallax@lemmy.world 2 points 2 years ago It meant user, as in user-installed programs and libraries for this system over the core system programs and libraries of the operating system in /bin and /lib. Someone learned it wrong, but otherwise I think the image is right. permalink fedilink source parent
