I would just start over before you get any more attached to it.
this post was submitted on 05 Mar 2024
14 points (75.0% liked)
Linux
47353 readers
1345 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
- 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
founded 5 years ago
MODERATORS
Why? I chowned and chmod the mount points only (not recursively) and now the system is functioning correctly
Use the pacrepairfile utility and you can set them to the distro shipped permissions easily https://man.archlinux.org/man/pacrepairfile.1
For now, as far as you know.
I can't see a reason for it to fail since the root user was functioning just fine, shit got buggy as soon as other users tried to read from the fs
Not sure about what permission changes you did, but my system has various permissions depending on the files or folders, so a general recursive change may give you a functioning system, but with broken security
i didn't change permissions recursivly, only for the mountpoints root
Just do the installation again...fixing the permissions maybe easy or extremely hard, depending on how far the problems go. And I don't think you will learn much besides of how the chown command works.
Not with modern package management systems. In the pacutils package is the pacrepairfile tool that is specifically made for repairing file permissions https://man.archlinux.org/man/pacrepairfile.1
I think the point a lot of people are making is that because it's a fresh install it might have been quicker and faster to just reinstall versus whatever kind of checking and troubleshooting you'd have to do with the permissions.
It was only the root of the partitions that I messed up, and I guess the bugs were caused because the Mint live boot only gave the user read permissions (no group or others can read) so I believe shit is fine, plus it's a fresh installation so there's that too
Whenever I break something and can't figure it out, I just make sure anything important is backed up and do a clean reinstall. Someone else might have a better answer though
Seriously nobody gave me an answer, I looked it up from my 2nd machine running Arch and shit is working now
Good on you for getting it fixed. One of the reasons Linux is a great OS in my opinion is that everything is in the file system and not in some arcane hidden thing. So every problem is solvable without a reinstall if you're motivated enough to figure it out.
It depends on how interested/motivated you are in finding out exactly why things aren't working. If you just want a working system without the hassle, since it's a fresh install, I'd recommend just reinstalling.
Things weren't working because of the owner+permission being set by Mint instead of the Arch installer, it prevented non-root from reading anything off the system, now that I chmod the mount points, things are functioning well
I'm surprised it booted lol
I'm surprised it installed just normally