Important Configuration Files
 

I'm trying to alter a few things in my system and I have some files I need to locate/configure to do so.

In what path/file are the system paths first defined? i.e. Path to kerenel, user directory, install paths etc. Are these standard to the distribution or can they be modifield?

How can I make a read only file system writable without being able to take ownership of the disk or remount/eject the disk where it resides?

Should ps aux display process 0?

Is there anyway to interact with the firmware in linux?

Been trying to find these answers for awhile and havent had much success. Thanks in advance

Is this thread basically re-wording your other thread: https://www.linuxquestions.org/quest...ll-4175593443/ ? If so please don't and ask a moderator to merge threads.

I didn't intend it to be. The reason I'm asking stem from the same issue but I thought it would be easier to have specific context independent questions in a seperate thread. I can merge them if it will help better understand the situation, but IMO they arent related

Thanks for explaining. While I agree question separation is a good thing and while a prima facie your questions seem context-independent they are too specific and too much geared towards answering your other threads questions. What's worse is that if one were to answer questions here in a generic way you might get the wrong idea for solving your other threads problem! I'd rather like to avoid that.

In Linux the file system is standardised across distros. The running kernel is in /boot, user's home directories are in /home. Programs are installed in /bin, /sbin, /usr/bin and /usr/sbin, and so on. Look up the File System Standard.
You need to use the mount command with root access to do this on a one-off basis. For a permanent change, you need to edit (as root) the /etc/fstab file. Judging by your other post, both these options are problematic for you.
No. There is no PID 0. If there were, it would be the kernel.

You can interact with a UEFI chip using efibootmgr. I don't know if you can access any other firmware.

Thanks but I think im oversimplifying the issue as I'm certain it's not as simple as changing a few lines in a configuration file. IF this were the case wouldn't reinstalling the OS reconfigure everything to an out of the box state?

I've tried this (multiple times) to no avail. I shared the details in a seperate thread hoping to invoke some critical thinking. I am new to this and need help but I've educated myself on the issue and have been trouble shooting it for months.

To be more direct Im looking for a way to manipulate/inspect the handoff from hardware to software as I think this is where my problem and solution are. If my terminaology is a little off please correct me. I'll do the critical thinking part but Im looking for ways to manage the Pre-boot process HOB/PEI producer consumer handoff. Im confident that it's a memory allocation/Boot device selection issue or someone has physically taken apart my computer and reinstalled hardware that they can remotely (from 30-40 ft away) control. Is there an interface for managing these processes?

yes and no, yes each Linux system follows a certain standard to how and where things are put, BUT, this is not written in granite. you can create your own system and give it whatever distribution for files you want or shove them all into one directory.

become the owner. that is what security is for. so to not let you do what your asking to try and bypass.

that is a debate for the world to decide.

assembly language
now you may rest easy. :D