4
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Mar 2024
4 points (64.3% liked)
Linux
48143 readers
741 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
Also check
ls -ld /to view the permissions of/itself. Sounds like whatever happened to boot also happened to the root. A quickchown root:root /should make dbus happy. Don't recursively chown or chmod the root partition, that can result in a worse situation. Hopefully only/and/bootwere affected.Yes I only created / and /boot from the Mint live boot
Do I need to run another chown for the boot partition? If so is chown root:root /boot the correct command?
Update: chowning didn't fix dbus failing
Update 2: the warnings did go away though
Update 3: the dbus errors did change
Update 4: I think my / and /boot permissions are messed up to, they are drwx-----
So that's why the wrong IDs came from. Technically the filesystem doesn't know about names, it knows about IDs, and software just look at
/etc/passwdand/etc/groupsto go ID<>name./should be 0755 (drwxr-xr-x). Boot, you can chown it all to root and 0755 for directories and 0644 for files safely. The reason you can't for the root is, you'll likely break executable state or SUID bits that sudo needs to be sudo.The permissions inside the partition were set correctly, it was only the "root" of the partition that went off, I only created the partition using Mint, while Arch did the whole installation and wrote all the files
Either way I chown both / and /boot to root:root and chmod both / and /boot to 0755 (looked these up from my other Arch machine) and the bugs are gone