0
tyrion

New to building Armbian - where to put optional configs?

Recommended Posts

hey there,

compilation noob here.

 

I want to build my own image via vagrant and set it up already, because Armbian is the only OS* which provides an integrated option for an encrypted rootfs (preferrably on another drive than the sd-card, because of performance) without manually fiddling around. See: https://github.com/armbian/build/issues/947

 

My plan is to build it with the optional config, as written in post 2 of the link above:

CRYPTROOT_ENABLE=yes

CRYPTROOT_PASSPHRASE="MYSECRECTPASS"

CRYPTROOT_SSH_UNLOCK=yes

CRYPTROOT_SSH_PORT=2222

 

But I don't know where to put the optional build options and it's not clear to me where to look that up.

I would be very thankful if someone give me a hint where to look - the documentation is not really "noobfriendly" or I'm not looking hard enough, maybe both ;)

 

thank you in advance for any help.

 

*) there may be other ones, but until now I couldn't find any

Share this post


Link to post
Share on other sites

Thank you and sorry for my late answer.

Maybe I misunderstand something, because I can't get it to work...

I copied the kernelconfig from ~/armbian/config/kernel and added at the beginning of the file the four optional parameters unchanged to test if the compilation process is actually using the config. The path to the config is ~/armbian/userpatches/linux-odroidxu4-dev.config which is pretty much the same as written in the documentation -> userpatches/linux-$KERNELFAMILY-$KERNELBRANCH.config but I cannot see at the beginning of the build process that it's using my manually edited config.

 

What should be the actual content of the config file? Only those optional parameters or the whole config as written in the conf directory plus the optional parameters? And where can I see (if not at the beginning of the build process) which config has been used by the compilation process?

Share this post


Link to post
Share on other sites

I see. It looks like I failed to merge LUKS encrypting function to the master branch and it is normal that is not yet mentioned in a documentation. I also haven't tried it yet. @zador.blood.stained I didn't pay much attention to its development ... Is it ready to merge and since I already dump the "development" branch ... do I need to restore it to merge it properly with commits and comments?

 

@tyrion Wait that we sort this out first.

Share this post


Link to post
Share on other sites
2 hours ago, Igor said:

It looks like I failed to merge LUKS encrypting function to the master branch and it is normal that is not yet mentioned in a documentation. I also haven't tried it yet. @zador.blood.stained I didn't pay much attention to its development ...

LUKS encryption was not merged to master as I tried to simplify and rework it, but did not finist it yet, not to mention that it needs more testing with different kernels.

 

2 hours ago, Igor said:

do I need to restore it to merge it properly with commits and comments?

The only thing I didn't pull to a separate branch was resize2s modification, but we can get the code from here, no need to restore the "development" branch

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
0