Add finit.config=/etc/custom.conf cmdline (kernel) for different finit.conf file

[hongkongkiwi]

I would like (for testing) to specify a different /etc/finit.conf file. Is it possible to pass a kernel param to specify what config file init uses?

[troglobit]

Nope, only at configure time using --with-config=/path/to/file. It's sort of like /etc/inittab in SysV init.

[troglobit]

Similar to #224, neat request if finit.config=/path/to/file existed then overrides for tests and similar would be possible.

[hongkongkiwi]

This would be useful to me, if implemented, perhaps we could hardcode allowed filenames at compile time? That way user cannot arbitrarily specify a filename and then when something is passed finit just checks against kv to see if it was allowed at compile time.

Might help to mitigate any possible security issues? Just a thought today about this.

[troglobit]

Good idea, I was a bit concerned about the security aspects as well! Thanks :)

[hongkongkiwi]

What about this?

• RCSD dir is configurable in finit.conf (value in finit.conf overrides any hardcoded setting, if compiled in RCSD dir is blank and no setting set in conf then disable completely).
• finit.config=/etc/finit.conf is configurable to point to a different .conf file via kernel cmdline arg

This works since finit.conf is read first (right?)

[troglobit]

Yes, that would work. (I'm assuming you meant finit.config=/etc/finit.conf, not fstab :)

[hongkongkiwi]

Yep! :)

[hongkongkiwi]

I wanted to clarify this feature request a bit and narrow it down.

1. Change rcsd dir to be read from finit.conf something like rcsd_dir=/etc/mydir (otherwise fallback to whatever is configured at compile time, or just fail if nothing configured, similar to how fstab works)
2. Finit conf can be specified from kernel comdline
   finit.conf=/etc/finit.conf with fallback to compile time value or, finit should drop to rescue shell if no finit.conf passed and no compile time fallback specified.

I think these two changes are very powerful and allow the user to specify completely different sets of scenarios. For example, you might want a factory test mode which you can simply specify that with kernel cmdline finit.conf=/etc/factory_test.conf and a completely specific and special set of behaviour would start.

A similar functionality can be used with runlevels, but your limited to a few scenarios with no way to specifically name each one. Also, there are some hardcoded functionality which cannot be changed with runlevels (e.g. in my above example the rcsd_dir), so being able to specify a different finit.conf (which in turn specifies it's own rcsd_dir) would be extremely powerful.

The above changes (I think) should be backwards compatible, so existing users won't see a difference.

[troglobit]

100% agree from me. Thank you for taking the time to pin this down <3

[troglobit]

There, finally completed! :-)

We now have the following kernel command line option:

-- finit.config=/etc/factory.conf

... and top-level configuration directive (from /etc/factory.conf):

rcsd /etc/factory.d