Just throwing these out there as reference. https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/pdf/Installation_Guide/Red_Hat_Enterprise_Linux-6-Installation_Guide-en-US.pdf <quote> Only the most commonly used commands are available in the pre-installation environment: arping, awk, basename, bash, bunzip2, bzcat, cat, chattr, chgrp, chmod, chown, chroot, ... umount, uniq, vconfig, vi, wc, wget, xargs, zcat. ^^^^^^^ </quote> So it was only last year that RH got all traces of vconfig out of the standard scripts and tools. Good for them. However, there are lots of references like these: http://www.serkey.com/vlan-configuration-native-vlan-and-setting-pvid-bcu5dw.html http://wiki.xensource.com/xenwiki/XenNetworking These directly reference vconfig, include official sources, and are reasonably recent. I'm not arguing that IP-Utils hasn't been the "more correct" solution for years or that any new script I write I should use the right tool. Only pointing out that vconfig is very much entrenched into the psyche of sysadmins, many of whom still use RHEL4 and RHEL5 as well as Ubuntu and other rot and we very much don't intend to have multiple versions of our scripts. Vconfig has been a stable in such things as vif-bridge scripts for KVM or Xen for years. If you look at CloudStack and I'll bet anything OpenStack has them by the bushel too. But as has been said, "yum install vconfig" and we can go away chuffed. If the intent is for "minimal" to be pure and legacy free, then I can live with it.