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.
It seems you've also asked about this on reddit, as well as in the IRC channel. I didn't answer on IRC because you dropped off before I had the chance, but I did on reddit. You asked an additional question here - "Where are the configs stored?" - and so I'll answer here as well, including this new question into consideration.
Some background to make sure we're on the same page:
Bedrock Linux gets its components from other distros. Stuff like configuring networking or configuring init or configuring your DE are all distro-specific and depend on which distro you've chosen to provide that feature.
Bedrock Linux specific configuration is all in /bedrock/etc/, but that's mostly about glue to make components for other distros to work and likely not what you're looking for here. The location of networking configuration files depends on which distro you decided to have provide your networking components - you'll have to see that distro's documentation. Odds are what you'll be editing are local files, so keep the explicit path concept I mentioned above in mind.
Bedrock Linux transparently integrations a lot of components from various distros, but not quite all. There's a known limitation regarding having things from some strata hook into another stratum's init system. If you install sshd from Arch Linux, but use runit to boot from Void Linux, Void Linux's runit won't know to start Arch's sshd at boot - Bedrock Linux does not currently make that "just work". (It's a pretty hard problem - we may not get it working any time soon.)
Continuing with the same thing I said on reddit:
It sounds like you have gotten the networking stuff you want working, just not persistent after reboots. Correct? If so, I see two likely sources of your issue:
You're setting up networking from one stratum and getting your init from another. This means the init you're using isn't reading whatever configuration is supposed to tell init to run the networking code at boot due to the above mentioned known issue.
The easiest fix for this is to just get networking from the same distro as you get init. It doesn't take advantage of Bedrock Linux's features in this respect, but it's easiest to make work, and you can still take advantage of Bedrock Linux features elsewhere.
If you want to get networking and init from different distros/strata, the work around for the above mentioned issue is to manually make init-specific configuration to run the networking code at boot. For example, if you're using systemd from Arch, you could make a unit file with that as the ExecStart= line. You'll have to see the documentation for the specific distro/init you're using to boot for this, sadly; I can't give you an answer that works for everything. Most distros/inits either support /etc/rc.local or can be easily made to do so, which makes it a good choice in case you later want to take init hop as it should then continue to work across init choices. One note additional: since (in this guess for where your trouble lies) you're getting init and networking from different distros, I'd recommend explicitly specifying which ifconfig you're using with brc - so you'd probably want something like /bedrock/bin/brc <stratum> ifconfig <device> up.
You're getting the networking and init from the same distro/stratum - that is, the above mentioned init hook issue isn't relevant here - and you're missing some required step. You'll have to see the documentation for the specific distro/init you're using to boot for this, sadly; I can't give you an answer that works for everything. For example, if you're getting your init and networking from Arch, you could see the Arch Linux wiki page. This isn't a cop-out trying to push you away; I'm happy to help, it's just there's no way to cover all the possible instructions here for all the possible distros/networking stacks/inits.
Hopefully that points you in the right direction. If not, do let me know and I'll see what I can do.
Last edited by ParadigmComplex; 12-27-2016 at 05:13 PM.
Reason: Rephrasing to avoid possible misinterpretated tone
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.