this post was submitted on 06 Sep 2024
1213 points (95.6% liked)

Linux

48670 readers
421 users here now

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

Related Communities

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

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 34 points 3 months 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.

[–] [email protected] 16 points 3 months ago* (last edited 3 months 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.

[–] [email protected] -2 points 3 months ago (1 children)

Per the graphic, it means Unix System Resources....

[–] [email protected] 12 points 3 months ago* (last edited 3 months ago) (3 children)

I don't trust a graphic which explains /boot as "system boot loader files"...

[–] [email protected] 4 points 3 months ago (1 children)

Why? What's inaccurate about it? I have no idea and would like to learn.

[–] [email protected] 10 points 3 months ago* (last edited 3 months 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"

[–] [email protected] 4 points 3 months 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).

[–] [email protected] 1 points 3 months ago

Well that's a shame for me. This graphic finally made the Linux file directory structure make sense to me