Bedrock LinuxThis forum is for the discussion of Bedrock Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've got Ubuntu-Mate and Arch getting along together on one box and I'd like Gentoo and Arch on another. With Ubuntu it was just a matter of adding rw to Grub, but for the life of me I can't keep Gentoo from changing back to read-only, and there it stays.
I have enjoyed myself immensely with this distribution. Many thanks.
What you mean by "changing back"? Kernel mounts root filesystem ro, this is a feature. Then kernel runs init system and it is supposed to remount root filesystem rw. So either there is filesystem corruption (then it remains ro as precaution) or your init system does not run properly.
The kernel boots as rw and a line on the screen reads "Changing to ro" or words to that effect. It's as though it's trying to mount as rw and then changes to ro.
Whether or not this is the case the init system ran fine without Bedrock installed.
Last edited by pressman57; 01-23-2018 at 04:19 PM.
What you mean by "changing back"? Kernel mounts root filesystem ro, this is a feature. Then kernel runs init system and it is supposed to remount root filesystem rw. So either there is filesystem corruption (then it remains ro as precaution) or your init system does not run properly.
Bedrock Linux tries to squeeze its own initialization code between the initrd and init-proper. As of the current release, this relies on the filesystem being read-write. Since many initrds support telling the initrd to mount the filesystem read-write by putting `rw` on the boot loader kernel line, the Bedrock Linux installation instructions indicate a user should do this. However, apparently that's not a universal standard. No filesystem corruption issues necessary here, nor issues with the (eventual) init.
Rather than require people mess with the bootloader, I plan on having the early Bedrock Linux code remount the filesystem read-write itself in the next release.
Quote:
Originally Posted by pressman57
Hi all. Thanks for reading.
I've got Ubuntu-Mate and Arch getting along together on one box and I'd like Gentoo and Arch on another. With Ubuntu it was just a matter of adding rw to Grub, but for the life of me I can't keep Gentoo from changing back to read-only, and there it stays.
I have enjoyed myself immensely with this distribution. Many thanks.
It looks like Gentoo's initrd uses different flags from the other initrds I've tested when I wrote those instructions. Most Gentoo people apparently figured out what they needed to do to make it work and fixed it themselves such that I never noted the fact I need to change the instructions there. Looking at IRC logs, I found someone who I think uses a Gentoo initrd stating:
In part of Gentoo where the instructions indicate you should put `rw init=/bedrock/sbin/brn`, try putting `rw rootflags=rw init=/bedrock/sbin/brn real_init=/bedrock/sbin/brn` instead. See if that does it. If it does, let me know and I'll update the installation instructions to mention it accordingly.
If not, we can get the Bedrock Linux subsystem that expects read-write to just remount it itself. This is probably what I should have done originally instead of asking people to mess with their boot loader. I didn't realize at the time that `rw` in the kernel line was not a universal standard. So, if the above proposal fails, let's try getting `brn` to mount the filesystem read-write. Open up `/bedrock/sbin/brn` (or maybe boot with some other medium if required then mount bedrock into it then `<mount-point>/bedrock/sbin/brn>`. You should see something like this:
I can't confidently comment on your issue with networking without more detail. Ideally you shouldn't have to do anything special, but it's possible you ran into a bug in Bedrock Linux. There are some known quirks with how it handles /etc/resolv.conf which may be a likely culprit. I'm experimenting with clean solutions for them for the next release, but it'll be a bit.
EDIT: If you are doing a hijack install, you should be able to test networking before hijacking. If it works before hijack, but not immediately afterwards, that's probably Bedrock's fault.
Last edited by ParadigmComplex; 01-27-2018 at 02:51 PM.
Ahh, gotcha. I lost context, sorry. Okay, that's good to know - I'll make sure the 'mount -o remount,rw /' method is in use for the next release. Even if you could get it working by messing with the bootloader, that's one installation step we can remove.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.