On Feb 28, 2011, at 1:12 PM, Scott Henson wrote: Rather than expose comment, it should probably be a new field. Otherwise someone might be caught by surprise... :p

On Tue, Mar 1, 2011 at 1:17 AM, petermity <6t12-n6js(a)dea.spamcon.org&gt; wrote: I think you should use the comments field instead of creating another field with the same purpose as the one that already exists. You could make it configurable in settings if you want to have them be in your menu so there are no surprises.

Scott Henson <shenson(a)redhat.com&gt; wrote: To me, it seems better to have a separate setting. The comment is for the Cobbler developer/maintainer. The new menu description item is for the users of the Cobbler system.

But given that the field is potentially used for quite a lot of information, would that not generally be too much info for inclusion in a boot menu, would it not be better to have the comments field as a large field that can contain plenty of info, and a separate field that is used for a concise boot menu item description? Paul This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.

On Wed, 2 Mar 2011 08:15:32 -0500, Jonathan Sabo <jsabo(a)criminal.org&gt; wrote: Yeah, duplication would be my problem as well. The thing is, that once the comment is exposed in the pxe template, you can process it in whatever way you see fit. So if you want to have some complex string data type in there that python/cheetah can parse and then extract the description, that would work. Having said the above, we have talked in the past about a misc field. Something that could contain a python/json dictionary and allow the user to stuff whatever they want in there. I'd be fine adding something like this in to make the above easier to do. -- Scott Henson Red Hat CIS Operator WVU Alum BSAE/BSME

petermity <6t12-n6js(a)dea.spamcon.org&gt; wrote: I submitted an enhancement issue for menu descriptions: https://fedorahosted.org/cobbler/ticket/654 Although the above paragraph didn't trigger any discussion yet, I submitted an enhancement issue for it as well: https://fedorahosted.org/cobbler/ticket/655#preview