Subhendu Ghosh wrote:
Is this creating a dependency on syslinux > 3.62 which started
supporting
submenus? Or something independent?
Well, originally, it was something independent.
Basically you can have a menu launch another menu with syslinux, and
this is what that would be doing.
However:
http://www.gossamer-threads.com/lists/syslinux/announce/9394
This makes me want to investigate further.
Either way, we do carry a syslinux with the cobbler RPM so you can
deploy x86/x86_64 from other arches (as unlikely as that is), so we
could include
a newer version as needed without making requirements to use a specific
distro for the cobbler server. That's what we do now to avoid the same,
particularly as things like EL 4 have a older syslinux, than, say, F10.
Glenn Bailey wrote:
>> I'm thinking it could be done like this:
>>
>> cobbler distro edit --name=foo --menu-path="alpha/beta"
>> cobbler profile add --name=bar --name=baz
>>
>> This would add generate baz at the menu level alpha/beta/foo/bar
>>
>> Because distro is intended with "alpha/beta".
>>
> That would make sense, with the "/" being the divider? So ya, like:
>
> Alpha:
> Beta:
> Foo:
> Bar:
>
> ?
>
> The the "menu" items themselves would be separate from distros hence being
> able to make them whatever you want. Possibly have this as a config option
> to not confuse other folks? example: pxe_sub_menu: on or off
>
>
>> Now what happens if we specify the profile to go in a certain place?
>>
>> cobbler profile edit --name=bar --menu-
>> path="webservers/special/veryspecial"
>>
>> This would ignore the distro options and put the pxe menu entry under
>> webservers/special/veryspecial/bar
>>
> or ya, if the "--menu" option wasn't specified it would default to the
> root menu like you said. that would fix my stated config option item
> stated above, ha!
>
> --
> glenn
> terremark worldwide
>
>
>