

Woah! Thanks for taking the time to write the detailed response. Will take a look at the source code. Really appreciate the effort ❤️
Woah! Thanks for taking the time to write the detailed response. Will take a look at the source code. Really appreciate the effort ❤️
I added more comments on the original post which describes the situation a bit more.
Don’t know what’s a good way to get the comments linked to this post.
Do take a look if you are interested.
Standards are set of rules. But still different vendors implement them separately. For e.g. TCP/IP stack implementation is a bit different in Windows and Linux but end user generally never realises this because it’s close enough that things still work. I want to know what is the sequence of events when Linux creates a Response packet for a ping Request it received.
I know. I felt while writing the post that this feels wrong writing those words in same sentence. The scenario is that we would deploy the hardware on customer premises so it has to be supported and very reliable(hence enterprise grade). But i personally think that all enterprise grade hardware is way overkill for running ansible playbooks. So was trying to see if there is an intersection point between these opposite requirements.
If you want extra users I believe you can create them in ignition file, so that way they get created when MicroOS is deployed.
Basically anything you want as part of ‘default’ setup has to be configured via ignition file.