add support for "unspecified" configuration entries

[anonymous]

add support for "unspecified" configuration entries.

Imagine I configure some setting properly only for debian and macosx computers. I would like bcfg2 to complain if (someday) I bind (by mistake) some computer that is neither debian nor macosx. Adding an "unspecifed".

for instance:

<FileInfo>
    <Group name='debian'>
      <Permissions owner='root' group='root' perms='0644'/>
    </Group>
    <Group name='macosx'>
      <Permissions owner='root' group='wheel' perms='0644'/>
    </Group>
    <unspecified/>
</FileInfo>

This would allow the one that writes some configuration specification to prevent another one to use in an unwanted way.

[James Colleen <…>]

​content writing india is something you need to consider before embarking on a digital marketing plan for your startup.

[Thomas Davidson <…>]

asasv csd

[Thomas Davidson <…>]

Thank you for this opportunity to speak out. I want to share my problem and the solution that I found.I recently created a video blog on the YouTube? platform and was faced with the fact that in order to get to the top, you need to have a lot of views, after a little searching on the Internet, I found an excellent service that helped me solve this problem. If you, like me, are new to social media blogging, I recommend using this service: ​https://viplikes.net/buy-youtube-views .