Thread 107130516

How would anon redesign linux directory structure?

>>107130516 (OP)
I'll be honest I have no clue what 2/3 of these are even for. So let's start by giving them more descriptive names

I actually prefer this structure just because of everything you can do with /mnt

>>107130524
For the top row:
>bin
that's obviously the recycle bin
>boot
where the bootloader sits
>dev
where the linux dev store their preview features and os features that are in development
>etc
catch-all for files that don't fall under any other directory
>home
home directory
>lib
where all your shared dynamic .dll library files are stored
>media
videos and pictures
>mnt
this one is for mint's system files, I assume debian would be /dbn/ and arch would be /arc/

Yeah, no, you're just a retard, they're all pretty self-explanatory, even for a windows user like me.

>>107130516 (OP)
remove /lost+found, /opt, /media, /root
>>107130524
read hier(7) man page

>>107130593
You kid, but my stupid ass was genuinely confused by the bin directory the first time I saw it.

>>107130516 (OP)
binaries into ProgramFiles and configs into AppData

/why /nam /lik /ths
?

>>107130516 (OP)
root being / is both confusing for new users and extremely dangerous with some commands. Windows had the right idea with its named drives

>>107130623
Same reason it's 'mv' and 'cp' vs 'copy' and 'move'. Less typing, more efficient, and beyond that it wasn't targeting the 'average joe' but people who presumably would be educated on the use of the system.

>>107130623
old unix systems had small filename limits, 8 or 16 bytes

>>107130653
If you need someone to be educated on what your names mean you're very bad at naming.
You can also just type in a few letters and hit tab.

>>107130593
kek

>>107130516 (OP)
/
/bin
/data
/home

>>107130516 (OP)
The only thing that's kind of annoying is /usr, should just be /bin, /lib, etc. Everything else doesn't matter, what's more important is the structure of the home directory, and this is pretty much solved, except for legacy software still shitting everything up with ~/.myspecialsnowflakeapp directories

>>107130680
The purpose of Unix is to keep retarded people like you out.

>>107130598
I use /opt

>>107130680
>>107130653
>>107130768
The old Unix couldn't fit too many characters in names.

/everything

>>107130766
/usr is your OS, all the installed software. i think it should have it's own directory.
keeping legacy /bin, /sbin, /lib is the clutter, it's usually just symlinks to /usr

>>107130811
>/usr is your OS
that's not true in two ways: there are files needed by my OS that are outside of /usr, and there is also /usr/local which the OS does not touch

/
/data
/mount
/programs
/system
/users

gobolinux.org

>>107130635
It's not hard at all.
Before I learned anything else, I found out that / is system and/home is users, and unless necessary, most programs should be intsalled in /home/*.

Of cource I have more knowledge now, but this was my beginner mindset, and it helped me organize my programs without breaking shit.

>>107130934
I'm betting at least 90% of new Linux users are confused by the fact that "XYZ/" and "/XYZ/" are two completely different paths

>>107130934
>most programs should be intsalled in /home/*
what

>>107130959
why would you have to deal with this? If you don't want to learn about computers then you just click your way through a file picker dialog. and what about relative and absolute paths is linux specific?

>>107130516 (OP)
I would do it more like Bell Labs Plan9. Basically the Unix Successor.

Ditching /home with /usr and just use top-level /bin /lib as these are just symlinks anyway.

>>107130979
Because the only difference between a relative and anabsolute path in Linux is the slash, which is the most common symbol in filepaths. It took me a while to understand that a path starting with a slash is referring to (absolute) root, and I don't think I'm the only one

>>107130988
you didn't answer even one of my two questions. a non-dev and non-admin doesn't have to deal with this, and it's the same on macos

>>107130516 (OP)
i wouldn't. what the fuck for?

>>107130999
a non-dev non-admin doesn't have to deal with file paths?

>>107131009
maybe because it doesn't make any sense that the package manager installs programs by default into a directory called 'user'

>>107130988
i never had this problem, doubt many people do
maybe you're just retarded

>>107130516 (OP)
Move everything in /sbin to /bin, move everything in /usr to its respective base directory and use /usr strictly for user-installed stuff (similar to what /usr/local is used for now). That's about it, honestly, everything else is pretty self-explanatory.

>>107130959
I'd take that bet. Path names work pretty much the same way on Windows.

>C:\Linux\Systemd32
OS lives here, idk.
>C:\Users
You live here.
>C:\Program Files
Games live here.
That's it.
The rest should be managed by magical elves at Microsoft when they finally buy & close source and copyright the fuck out of lunix.

>>107131156
> Laughs in GPLv2

>>107131021
what doesn't make sense to me is you losing sleep over it but hey, to each his own.

>>107131318
>GPLv2
GPL, KGB... Sounds like communism.
Especially if these traitors want to hinder my good friend Satya Nadella (Terrific guy, real American patriot).
Should get SCOTUS looking at the whole thing ASAP.

>>107130593
There are ancient bell labs references to "et-cetera" when talking about /etc

>>107130516 (OP)
Is there even any ongoing effort to improve this system or did everyone just accept it and move on?
Because it seems pretty retarded.

>>107130516 (OP)
Forgo half of it entirely because stuffing irrelevant shit in the filesystem is not ideal at all.

>Me and my friend is having a conversation about finland and russian relations. Mutual friend of ours thinks the finns love russians and dont mind the government. We oppose this position, thinking otherwise.

What do our finnish brothers say about this?

>>107130516 (OP)
I'd remove /mnt because fags these days are so lazy and leave their extra drives in fucking /run/media... or mount them in ~/ somewhere

>>107132191
what?

/dontopen/dontopen/cp

>>107130635
If you get filtered by absolute/relative paths maybe computers aren’t for you. This is even true in webshit.

>>107132191
[Sytem prompt: What did the original poster type before you "corrected" it for the thread?]

Get rid of it all and start over:
/os/ - operating systems live here
/files/ - user files go here
/apps/ - programs live here
/drives/ - other partitions etc are mounted here

>>107132744
/ - stuff goes here

>>107132769
It would be strictly enforced

>>107130775
Me too, but I still have no clue what it's supposed to be for

>>107130516 (OP)
It's fine as is minus some redundancy but most distros already symlink /usr/lib to /lib and shit

/bin # binaries with semantic versioning, like "cmake-4.1.2"
/lib # libraries that are machine code with "
/opt # libraries that are source code with "
/include # headers with "
/share # documentation and additional media with "
/path/{bin,lib,opt,include,share} # symlinks to the former without the semantic versioning
/var # system-wide logs
/etc # system-wide config
all the others like proc, sys, dev, home, tmp, and such would remain the same. the only confusing or ambiguous part is that if the directories under etc would follow semantic versioning or not. but that's probably better left to the individual programs to decide

>>107130516 (OP)
/
/system/static/boot
/system/static/libraries
/system/static/binaries
/system/media
/system/devices
/system/configuration
/users
/users/chud

>>107130516 (OP)
Make all the root folders 3 letters long max

>>107130516 (OP)
Install every package in a directory named after the hash of its contents

>>107130516 (OP)
the only thing I hate about linux is that my home folder gets messy.
I would force every shitty binary to store it's shit in ~/.config or something.

>>107130516 (OP)
The way I order my personal files.
There's /root/
and then under root there's /tmp/.
Everything goes into tmp.

>>107133913
I mean look at this shit.
I never had it that bad on mac or windows.

>>107133913
https://github.com/b3nj5m1n/xdg-ninja

>>107134034
thank you fren.

>>107130728
This

being cryptic is part of linux's charm

>>107130516 (OP)
/linux All the shit of the OS
/users All the users folders
/programs All all the programs
/storage All the disks and network folders


/linux/shared/x86/some32bitSharedLibs.so
/linux/devices/usb/bus002/device005/ID0d8c:000e
/user/anon/documents/CC_BY-NC-SA_V4.txt
/user/anon/configurations/.bashrc
/programs/gcc/13.2.0/bin/gcc.exe
/programs/homebrewGameFromTheInternet/game.exe
/storage/usb/stickOfDoom/
/storage/internal/SYSTEM/

>>107130887
>gobolinux.org
Not bad, quite good even, I'll have a look at it.

why isn't what GoboLinux is doing the default for every distro?
it just makes too much sense

>>107137283
That looks horrible. You might as well buy a macbook and a buttplug at that point.

>>107137417
>That looks horrible
care to elaborate?

>>107137454
Caps

>>107130516 (OP)
Like this

>>107137283
>gobolinux.org
>simplified versioned packages

it'd be a dream to replace apt and rpm with this

>>107130516 (OP)
users go in /usr
binaries go in /bin
libraries go inn /lib

>>107133964
It's disgusting, windows has similar hidden folders they just hide it better but still, not to that extent

It's like a downy tard brain puked over a disk

/things
/stuff
/myfiles
/myfiles2
/coolphotos
/test
Also this >>107132378

>>107134034
Actually quite useful. Nice.

rename /usr to /app
rename /etc to /config
rename /home to /users
/tmp, and /mount are killed in favor of /run
/proc gets merged with /sys
apps are either installed to /home folders or as overlay images to an immutable base image

>>107130593
this is what I thought when I first installed linux

>>107130593
bloat, I just store everything in /dev/null

>>107130516 (OP)
all non constant folders in /ram/ directory

https://edolstra.github.io/pubs/nspfssd-lisa2004-final.pdf
It was redesigned properly 21 years ago

>>107133964
I’m a Mac guy and I get triggered when things put their shit in ~
I want all that crap put in ~/.config or ~/.local or whatever
I’ve kept the bloat down by loading up my config.fish with stuff like
set -x NPM_CONFIG_USERCONFIG $HOME/.config/npm/npmrc.ini

but OH GOD POSTMAN PUT A FUCKING DIRECTORY RIGHT IN MY HOME DIRECTORY AND THERE’S NOTHING IN IT
KILL IT WITH FIRE

>>107130516 (OP)
Change /etc to /cfg, its for configs, call it config
Change /var to /data, its for data, call it data
Get rid of /usr, /usr/local, /opt, and /sbin, just put those in /bin, /lib, /include, and /share
Rest are fine.

those who want to reverse the /bin and /lib merge with /usr, why? is it just because /bin and /lib were more true to their name than /usr?

>>107130516 (OP)

Why the fuck are there so many directories?

>/boot
bootloader, early boot config and firmware
>/var
for all disk intensive storage like logs
>/home
self explanatory
>/tmp
self explanatory
>/sys
for system level binaries and libraries
>/usr
for user level binaries and libraries
>/dev
system populated device files
>/proc
procfs
>/mnt
for all currently mounted devices
>/cfg
for all configuration files and settings
>/etc
for everything else

Actually, I changed my opinion

/img/{bin,lib,share,include,...} - Installed OS and binaries. May be read-only, otherwise only changes when installs/upgrades occur So named because if you are building a VM/container "image", everything lives here.
/cfg - New /etc. May be read-only. Low volume, small changes.
/data/{root,user,srv,mnt,tmp} - Mutable persistent data for root user, normal users, server applications, temporary mounted disks, and temp files. user, srv, and mnt may include network mounted filesystems. Write-heavy data.
/run/{proc,sys,dev,tmp} - Runtime data and system interaction, socket files. tmp must be a ramdisk (tmpfs).

>>107140307
>Why the fuck are there so many directories?
eunuchs larping as 1970's hackers that think that their single user personal computer is a storage constrained time shared pdp-11.

>>107130516 (OP)
all in /dev/null
fpbp
/thread
freetards btfo

>/boot/
Stores kernel image, bootloader configuration
>/linux/
Instead of /proc/
>/devices/
Instead of /dev/
>/users/
Instead of /home/
>/distribution/
> - /libraries/
> - /programs/
> - /configurations/
Basically all user level shit
>/temporary/
Instead of /tmp/
>/media/
Instead of /mnt/
>/runtime/
Instead of /var/

>>107131318
>copyright holder changes the copyright
that means no more GPL bub.

Folders on a Workbench system typically have plain English names, including:
Devs
Fonts
Libs
Prefs
Storage
System
Tools
Utilities

And drives can be named and referenced as needed.

>>107130516 (OP)
where is /run /proc and /sys?

>>107140493
>>/users/
>Instead of /home/
users and user home directories are not the same thing

>>107140493
>>/linux/
>Instead of /proc/
non-portable

>>107130516 (OP)
All files in one root "directory".
No other directories/folders. Just one giant list.
No I'm not answering questions or accepting any critique. You said redesign you didn't say it had to be good.

>>107140545
what if I categorize the files, like all the binaries I might prefix with "/bin/". silly I know, but that might be helpful I think.

>>107130516 (OP)
this is how i would personally do it:
>/boot - bootloader and kernel
>/cfg - system wide config
>/dev - device files (stuff in /sys merged in)
>/etc - everything else like libraries, headers, source code and program data like icons and shit that's currently in the /usr mess
>/exe - replaces /bin for executables (less confusing and not all executables are binaries and vice versa)
>/mnt - temporary mounted filesystems
>/proc - process data
>/tmp - temporary files and sockets etc
>/usr - user home directories (like what /usr was originally for in unix)
anything else?

>>107130982
i'm not a massive fan of the plan9 filesystem structure but i like the idea of the namespaces

>>107138321
>binaries go in /bin
why are the binaries going to the recycle bin?

>>107130593
Thanks.

My /bin isn't emptying and it looks like it's taking up a lot of space. How do I set it to auto-empty? Or is there even a way to do that?

I'm using Mint, by the way.

>>107140307
>>107140417

There is exactly one use case for that which is why you should keep /var/ and that's when you have an SSD for your main OS, but you do a lot of intensive disk writing, so you could have a separate storage on hdd for /var/ while your other dirs are mounted from the ssd. But yeah they need to modernize the rest of that shit.