All right, I hereby ask creating new repository foreman-bootloaders under
theforeman organization. Since 1.14 is almost done, I would like to have
first nightly builds available so users can start testing this.

On Wed, Nov 23, 2016 at 2:13 PM, Lukas Zapletal <l...@redhat.com> wrote:

> Any other opinions? Are folks fine with my proposal? I am not going to do
> RFE for this one, it's small thing.
>
> LZ
>
> On Wed, Nov 16, 2016 at 3:00 PM, Lukas Zapletal <l...@redhat.com> wrote:
>
>>
>> On Wed, Nov 16, 2016 at 2:02 PM, Daniel Lobato Garcia <
>> elobat...@gmail.com> wrote:
>>
>>> Thanks, this is very helpful and should probably be delivered with
>>> Foreman itself. As far as I know you'd need to overwrite the bootloaders
>>> if you change to Debian-family OSs (rendering provisioning with RH
>>> family broken). If that issue could be solved I think it'd make sense to
>>> install this package along the TFTP smart proxy
>>>
>>> How could that work so that we don't have to overwrite the bootloaders
>>> every time we want to provision a host of a different OS family?
>>>
>>
>> Can you elaborate on the error you see? I don't understand how PXE loader
>> can change behavior of kernel command line, it's being rendered by
>> provision templates, therefore for Debian family you simply associate the
>> correct template and this should work with Grub2 from Fedora or CentOS.
>>
>>
>> --
>> Later,
>>   Lukas @lzap Zapletal
>>
>
>
>
> --
> Later,
>   Lukas @lzap Zapletal
>



-- 
Later,
  Lukas @lzap Zapletal

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to