On Wed, Sep 14, 2016 at 5:03 PM, Holger Wünsche <[email protected]> wrote: > > I think the problem might be fstab or the point, where the initramfs gives > controll to the kernel.
The initramfs doesn't ever really give control to the kernel (well, at least not any more than any process does anytime it invokes a system call). The last thing the initramfs does is exec init, which then assumes control. > Since if I am not mistaken (I just say what I recall reading while searching > for a solution) the initramfs just gets the system running and then the > kernel should remount the root-partition. If you're using an initramfs the kernel will not mount anything at any time unless some process with sufficient capabilities asks it to. The initramfs typically mounts the root partition, and then execs init. Anything beyond that is done by init or whatever processes it spawns, such as openrc. Offhand I don't remember if modern initramfs solutions mount root as read-write; openrc will probably check for this in any case and remount if it is read-only (I could be wrong on that). If something other than root isn't mounted correctly, the fault probably lies in your fstab or openrc, or you're missing a necessary driver/etc. -- Rich
