----- Jörgen Maas <jorgen.maas(a)gmail.com> wrote:
On Wed, Nov 23, 2011 at 3:25 AM, Dan White <ygor(a)comcast.net>
wrote:
> Good to see you on the list, Michael. I thought you had moved on.
> So it looks like the current buildiso will not give me what I am asking for.
> Dang.
>
> I was hoping for a standalone loader that I could customize to the system level.
> This is because the DHCP in the environment I am in is run by the Microsoft Side of
the House and I have not been able to get consistent behavior from the first part of the
Cobbler net-boot process.
>
> Reference:
https://fedorahosted.org/pipermail/cobbler/2011-November/006889.html
>
> Is buildiso.py self-contained ? I would be willing to take a shot at getting it to
do what I want.
> Seems like a good feature to contribute for me to the stew.
>
Can you please explain the exact use case please? What do you mean
with a standalone loader? With the standalone ISO you basically get
the installation media from your Linux distro with associated
profiles/systems and the isolinux menu so you can still use kickstarts
for handsoff installations.
If you are using standalone ISO installations (you'd do this because
netbooting isn't available), so what does DHCP have to do with it ?
Thanks.
Sorry if I have confused.
I started out with a classic Cobbler Server, net/PXE-booting the clients to install.
However, the folks controlling DHCP are pro-Microsoft/anti-Linux and are uncooperative.
If I do my own DHCP, it will cause problems -- possibly technical problems, most
definitely bureaucratic/security problems.
So my intent is to find an alternate workflow that could remove the DHCP-related
obstacle.
Does that clarify ?
“Sometimes I think the surest sign that intelligent life exists elsewhere in the universe
is that none of it has tried to contact us.”
Bill Waterson (Calvin & Hobbes)