This patch:
---------------------------------------------------------------------------
diff --git a/templates/pxedefault.template b/templates/pxedefault.template
index bb09893..206c028 100644
--- a/templates/pxedefault.template
+++ b/templates/pxedefault.template
@@ -8,7 +8,7 @@ ONTIMEOUT local
LABEL local
MENU LABEL (local)
MENU DEFAULT
- LOCALBOOT 0
+ LOCALBOOT -1
---------------------------------------------------------------------------
Returns control of booting process to BIOS.
- LOCALBOOT 0 makes an attempt to boot from local device, like
0x80, etc
- LOCALBOOT -1 informs BIOS that PXE has failed and then bios will
process next entry into its boot sequence.
For example, the boot sequence (BIOS) I follow is:
1st- Boot from PXE
2nd- HDD
3rd- CD-ROM
So localboot 0 works for me ok, as "-1" does, but probably on some
servers with iSCSI booting, the sequence could be something like:
1st PXE
2nd iSCSI
3rd CD-ROM
And as that system doesn't have a local disk, this one would fail
¿anone tested this?
Regards
Pablo
--
Pablo Iranzo Gómez
(http://Alufis35.uv.es/~iranzo/)
(PGPKey Available on http://www.uv.es/~iranzop/PGPKey.pgp)
--
Postulado de Boling sobre la Ley de Murphy:
Si se encuentra bien, no se preocupe. Se le pasará
On Sat, 3 May 2008, Pablo Iranzo Gómez wrote:
> This patch makes the mac passed to OMSHELL to be lowercase
>
> Regards
> Pablo
>
>
>
> --
> Pablo Iranzo Gómez
> (http://Alufis35.uv.es/~iranzo/)
> (PGPKey Available on http://www.uv.es/~iranzop/PGPKey.pgp)
> --
> Postulado de Boling sobre la Ley de Murphy:
>
> Si se encuentra bien, no se preocupe. Se le pasará
>
> On Sat, 3 May 2008, Pablo Iranzo Gómez wrote:
>
> > Hi
> > This patch fixes a typo in sync code for removing dinamically
> > leases (the function was renamed but this call was not renamed
> > accordingly).
> >
> > There's also a patch for settings file to show isc_set_host_name
> >
> > And if interesting, changing ksdevice for bootif to use the one
> > used in PXE
> >
> > Regards
> > Pablo
> >
> > PD: buildiso works fine and found nothing wrong with the rest yet
> >
> >
> > --
> > Pablo Iranzo Gómez
> > (http://Alufis35.uv.es/~iranzo/)
> > (PGPKey Available on http://www.uv.es/~iranzop/PGPKey.pgp)
> > --
> > Postulado de Boling sobre la Ley de Murphy:
> >
> > Si se encuentra bien, no se preocupe. Se le pasará
> >
> > On Fri, 2 May 2008, Michael DeHaan wrote:
> >
> > > Subhendu Ghosh wrote:
> > > > Michael DeHaan wrote:
> > > >> With John Eckersberg's recent patch (and likely future extensions),
> > > >> Cobbler will be acquiring very good support for bind, so Cobbler can
> > > >> manage DHCP and DNS at the same time using more scalable tools.
> > > >> Similarly, we can now manage DHCP without restarts (Pablo Iranzo
> > > >> Gomez's patch). So then, I'm wondering what are the reasons we
> > > >> would have for continuing to support dnsmasq?
> > > >>
> > > >> If you would be affected by removal of dnsmasq support, I'd like to
> > > >> hear from you, as to why you would like it to stay in place. This
> > > >> does not neccessarily eliminate the ability to have seperate options
> > > >> in Cobbler for (more modular) DHCP/DNS choices in the future.
> > > >> (Likely this is something we could use /etc/cobbler/modules.conf for).
> > > >>
> > > >> --Michael
> > > >>
> > > >
> > > > dnsmasq is useful for small test networks that are running isolated
> > > > from the rest of the infrastructure. Having it available as an
> > > > optional module simplifies quick deployment and removal.
> > > >
> > > > I am thinking along the lines of - project x poc x test - in a
> > > > consulting toolbag.
> > > >
> > > > That said I would much rather have BIND support over dnsmaq.
> > > >
> > > > -sg
> > >
> > > I decided to modularize the code more and am keeping dnsmasq (and supporting
> > > it in addition to BIND). For those not familiar, the reason dnsmasq is
> > > different
> > > is that it supports *both* dnsmasq and dhcp at the same time. It
> > > actually also contains
> > > a miniature TFTP server, but since the distro already has one we like,
> > > we don't use that.
> > >
> > > How it's working at the moment in 0.9.X (devel/git), FWIW:
> > >
> > > Go into /etc/cobbler/modules.conf
> > >
> > > [dns]
> > > module = manage_bind
> > > [dhcp]
> > > module = manage_isc
> > >
> > > (Or set both fields to manage_dnsmasq for dnsmasq)
> > >
> > > [dns]
> > > module = manage_dnsmasq
> > > [dhcp]
> > > module = manage_dnsmasq
> > >
> > > And in /var/lib/cobbler/settings, there are seperate booleans for:
> > >
> > > manage_dhcp: 0/1
> > > manage_dns: 0/1
> > >
> > > So you can use ISC without BIND, and BIND without ISC, or dnsmasq for
> > > only half
> > > of what it does, etc.
> > >
> > > These are still driven by templates in /etc/cobbler -- one each for BIND
> > > (named), ISC, and dnsmasq.
> > >
> > > I am sorely due for writing a "what's new" in 1.0 document for the Wiki,
> > > that will describe what the
> > > upgrade process is and what all the changelog features are.
> > >
> > > omapi is seperately enabled in /var/lib/cobbler/settings:
> > >
> > > omapi_enabled: 0/1
> > > omapi_port: 647
> > >
> > > This only applies when manage_dhcp is enabled and the module in use is ISC.
> > >
> > > Given this is going to require some good testing, so I'll do a test
> > > release before adding anything else.
> > > I think this cleans things up nicely and still allows people to add
> > > their own DHCP/DNS servers into
> > > modules fairly cleanly if they use something different, without having
> > > to have a bunch of "ifs" in the sync code.
> > >
> > > Folks are welcome to try this now, though there are no doubt a few bugs
> > > which we will be ironing out next week.
> > >
> > > The Wiki needs to be updated also to include more docs on this and
> > > sample template files. I'll also probably be moving
> > > more of the static HTML from cobbler.et.redhat.com to the Wiki so people
> > > can update it when they come up with
> > > interesting tricks as well as corrections.
> > >
> > > --Michael
> > >
> > >
> > > >
> > > > _______________________________________________
> > > > et-mgmt-tools mailing list
> > > > et-mgmt-tools@xxxxxxxxxx
> > > > https://www.redhat.com/mailman/listinfo/et-mgmt-tools
> > >
> > > _______________________________________________
> > > et-mgmt-tools mailing list
> > > et-mgmt-tools@xxxxxxxxxx
> > > https://www.redhat.com/mailman/listinfo/et-mgmt-tools
> > >
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
