----- Original Message ----- | On Fri, Aug 17, 2012 at 1:05 PM, James A. Peltier <jpeltier at sfu.ca> | wrote: | > | > | > I see many reasons to have people rewrite their scripts. It's so | > that we can move forward with technology. | | It's technology, not fashion. If the 'new' breaks old documented | processes it isn't moving forward, it is just different. If it is | really better, it should easily maintain backwards compatibility. | | -- | Les Mikesell | lesmikesell at gmail.com My case is that the new fashion has been that way for years as deemed by the Upstream Provider. If the end user that being us admins, can't keep up with the vendors way of doing this then we should be sysadmins. vconfig isn't used any more. It hasn't been used in years. It was provided as a dependancy previously and as mentioned that dependency was removed. The fact that the original poster has not updated his scripts to keep up to date with the Upstream Provider's methods of doing this is the original poster's fault not that of CentOS team. Can it be added, sure! Does it need to be added when the user can and *should* upgrade their scripts, IMHO, no. -- James A. Peltier Manager, IT Services - Research Computing Group Simon Fraser University - Burnaby Campus Phone : 778-782-6573 Fax : 778-782-3045 E-Mail : jpeltier at sfu.ca Website : http://www.sfu.ca/itservices http://blogs.sfu.ca/people/jpeltier Success is to be measured not so much by the position that one has reached in life but as by the obstacles they have overcome. - Booker T. Washington