discuss: Thread: [Proposal] PXE Server HOWTO


[<<] [<] Page 1 of 3 [>] [>>]
Subject: [Proposal] PXE Server HOWTO
From: "Keith Strachan" ####@####.####
Date: 24 Jan 2002 18:35:13 -0000
Message-Id: <OFEBKLGALELIGOPDHMKEKEGNCBAA.kstrach@optushome.com.au>

Hi All,

I'm in the process of writing a new HOWTO that explains the intricacies of
using PXE and how to actually get it to work.  After spending weeks
searching the net, reading through various other howto's, not one explained
how it hangs together, what makes it work as a default mechanism, most were
tailored around a specific product or group of products, and even some of
those, were not exactly "functional".

None covered emerging technologies such as support for IA64 architecture
hardware, let alone covered the various types of servers available from
other vendors.

I'm currently about a fifth of the way through writing this in DocBook.sgml
book format, as article format didn't quite suit my needs, and apologies to
the guys at LDP, but unless you guys can come up with a template for use
that is a little more explanatory, and a little easier to use.... or someone
write an application that can simplify doing documentation (there are a lot
of people out there that would like to write doco, but the tools are
extremely lacking). Sitting down writing code to write a document is not
exactly what I enjoy when all I want to do is write doco. :)

anyway, back to my original subject, my PXE Server HOWTO... any comments,
suggestions would be appreciated.... should I continue ?? :)

regards

Keith Strachan
Strachan IT Consulting
Australia


Subject: Re: [Proposal] PXE Server HOWTO
From: David Merrill ####@####.####
Date: 24 Jan 2002 21:25:33 -0000
Message-Id: <20020124221646.GB32580@lupercalia.net>

On Fri, Jan 25, 2002 at 05:35:55AM +1100, Keith Strachan wrote:
> Hi All,
> 
> I'm in the process of writing a new HOWTO that explains the intricacies of
> using PXE and how to actually get it to work.  After spending weeks
> searching the net, reading through various other howto's, not one explained
> how it hangs together, what makes it work as a default mechanism, most were
> tailored around a specific product or group of products, and even some of
> those, were not exactly "functional".
> 
> None covered emerging technologies such as support for IA64 architecture
> hardware, let alone covered the various types of servers available from
> other vendors.
> 
> I'm currently about a fifth of the way through writing this in DocBook.sgml
> book format, as article format didn't quite suit my needs, and apologies to
> the guys at LDP, but unless you guys can come up with a template for use
> that is a little more explanatory, and a little easier to use.... or someone
> write an application that can simplify doing documentation (there are a lot
> of people out there that would like to write doco, but the tools are
> extremely lacking). Sitting down writing code to write a document is not
> exactly what I enjoy when all I want to do is write doco. :)

See http://www.linuxdoc.org/HOWTO/WikiText-HOWTO/ and see if that
would suit your needs.

> anyway, back to my original subject, my PXE Server HOWTO... any comments,
> suggestions would be appreciated.... should I continue ?? :)

I don't even know what PXE *is*. :-/

But if it's used on Linux, we're interested in the document.

-- 
David C. Merrill                         http://www.lupercalia.net
Linux Documentation Project                   ####@####.####
Collection Editor & Coordinator            http://www.linuxdoc.org

As Microsoft moves further and further from its core, it starts to run into
competitors who are extremely good at what they do, know their domains a
lot better than Microsoft, and are extremely proactive. Companies like Sun
and IBM and Oracle don't just roll over and die.
	--Michael Borrus, Berkeley Roundtable on the International Economy
Subject: RE: [Proposal] PXE Server HOWTO
From: "Randy Tata" ####@####.####
Date: 26 Jan 2002 01:22:25 -0000
Message-Id: <002501c1a607$df974820$758d28d8@talcon1>

Keith,

Yes!

A PXE Server HOWTO would be cool.. I've been using On CCM w/PXE on Intel
cards to install windows and all of it's apps via the network for years, and
haven't found much out there on PXE either (other than at intel).  I've
always wondered if anybody else had thought of setting up something similar
to On CCM on Linux.   A PXE Server is built-in to RedHat now, right?  Let me
know if you need any help with sgml/xml markup, etc.

David,

PXE is pre-boot execution environment.  Basically you boot off your network
card (by boot ROM or ROM Img on floppy), dhcp an address, and load a pre-os
environment from a server which can allow you to partition, format, install,
etc. to the client machine.  I'm sure you've seen "network" as a choice in
your BIOS boot order selection.  This would be a HUGE step in the right
direction of enabling system administrators to easily do mass roll-outs of
Linux over Windows clients (for that microsoft-free utopian society :)

Randy Tata
Talcon Information Systems


-----Original Message-----
From: Keith Strachan ####@####.####
Sent: Thursday, January 24, 2002 1:36 PM
To: discuss
Subject: [Proposal] PXE Server HOWTO


Hi All,

I'm in the process of writing a new HOWTO that explains the intricacies of
using PXE and how to actually get it to work.  After spending weeks
searching the net, reading through various other howto's, not one explained
how it hangs together, what makes it work as a default mechanism, most were
tailored around a specific product or group of products, and even some of
those, were not exactly "functional".

None covered emerging technologies such as support for IA64 architecture
hardware, let alone covered the various types of servers available from
other vendors.

I'm currently about a fifth of the way through writing this in DocBook.sgml
book format, as article format didn't quite suit my needs, and apologies to
the guys at LDP, but unless you guys can come up with a template for use
that is a little more explanatory, and a little easier to use.... or someone
write an application that can simplify doing documentation (there are a lot
of people out there that would like to write doco, but the tools are
extremely lacking). Sitting down writing code to write a document is not
exactly what I enjoy when all I want to do is write doco. :)

anyway, back to my original subject, my PXE Server HOWTO... any comments,
suggestions would be appreciated.... should I continue ?? :)

regards

Keith Strachan
Strachan IT Consulting
Australia



_________________________
http://list.linuxdoc.org/

Subject: Re: [Proposal] PXE Server HOWTO
From: David Merrill ####@####.####
Date: 26 Jan 2002 02:45:31 -0000
Message-Id: <20020126033644.GB19026@lupercalia.net>

On Fri, Jan 25, 2002 at 08:22:08PM -0500, Randy Tata wrote:
> Keith,
> 
> Yes!
> 
> A PXE Server HOWTO would be cool.. I've been using On CCM w/PXE on Intel
> cards to install windows and all of it's apps via the network for years, and
> haven't found much out there on PXE either (other than at intel).  I've
> always wondered if anybody else had thought of setting up something similar
> to On CCM on Linux.   A PXE Server is built-in to RedHat now, right?  Let me
> know if you need any help with sgml/xml markup, etc.
> 
> David,
> 
> PXE is pre-boot execution environment.  Basically you boot off your network
> card (by boot ROM or ROM Img on floppy), dhcp an address, and load a pre-os
> environment from a server which can allow you to partition, format, install,
> etc. to the client machine.  I'm sure you've seen "network" as a choice in
> your BIOS boot order selection.  This would be a HUGE step in the right
> direction of enabling system administrators to easily do mass roll-outs of
> Linux over Windows clients (for that microsoft-free utopian society :)

Ah. Yes, it does sound VERY cool. Very cool indeed.

And it sounds like maybe you have someone who would at least proofread
and check your work, and maybe even help? ;-)

I am strongly in favor of sharing the load for a HOWTO. I like to see
them regularly maintained, and having multiple maintainers spreads the
load.

Take care,

-- 
David C. Merrill                         http://www.lupercalia.net
Linux Documentation Project                   ####@####.####
Collection Editor & Coordinator            http://www.linuxdoc.org

Everybody in the communications business is paranoid of Microsoft, including
me.
	--News Corporation CEO Rupert Murdoch
Subject: RE: [Proposal] PXE Server HOWTO
From: "Keith Strachan" ####@####.####
Date: 26 Jan 2002 04:30:22 -0000
Message-Id: <OFEBKLGALELIGOPDHMKEGEHKCBAA.kstrach@optushome.com.au>

Peter,

Sounds like we're on a similar path, but I'm "wanting" to take it a few
steps further forward.  I'm sure yourself, and I could both benefit from our
experiences.  From what you've referred me to re:LTSP, I've not gotten that
far myself as yet. I had a tinker, and then gave up due to lack of sleep.
The work your currently doing is most probably going to be of benefit to
whatever doco I manage to pump out.  I've read the info from H Peter Anvin,
and yes, I have to agree there are pitfalls with the implementation,
however, as you are also aware, in many cases, we're stuck with what we've
got :).

I'm about to restructure my doco that I have so far, as someone has given me
a location to a template that I might be able to utilise more efficiently
than what I've been attempting to use, but what I'd like to do is send you a
mail possibly on monday as what I'm intending to cover topic wise in the PXE
HOWTO, and what we could possibly do to merge our documentation together.
There is another person, Randy Tata, whom also has offered assistance with
his experiences, and I think that the three of us may be able to put out a
decent document that will allow people, network admins and corporations
better utilise their available systems.

I have a friend who is very experienced in Macintosh environments, I'll be
asking him if he can contribute info regarding Mac OS/X (seeing as it is
Unix based)

Randy,

My SGML/XML knowledge is very lacking, but I'm learning fast :) but of
course, any help when I get stuck would be very appreciated.


But, first things first, I'll send out a summary of topics, and sections
that I'm considering covering, and comments, additions, of criticisms would
be appreciated.  If you both can, could you send me drafts of whatever you
have currently as far as doco, or URL's for me to have a look see at.  I'll
send along on monday my drafts as to what I have done so far as well.

regards

Keith Strachan






-----Original Message-----
From: Peter Lister ####@####.####
Sent: Saturday, 26 January 2002 4:56 AM
To: Keith Strachan
Cc: ####@####.####
Subject: Re: [Proposal] PXE Server HOWTO



> I'm in the process of writing a new HOWTO that explains the intricacies of
> using PXE and how to actually get it to work.  After spending weeks
> searching the net, reading through various other howto's, not one
explained
> how it hangs together, what makes it work as a default mechanism, most
were
> tailored around a specific product or group of products, and even some of
> those, were not exactly "functional".

I've been lurking on ####@####.#### after proposing a PXE
mini-howto a few months back. I've got something in the editor; a couple
of others have produced specific guides, and I was intending to add
these as appendices. Have you seen Marty Connor's ltsp howto?

http://www.ltsp.org/documentation/pxe.howto.html

My intention is a specific Linux-via-PXE mini-howto, i.e. "you just took
a new system with a PXE rom out of the box, here's how to get a Linux
kernel running ASAP". My main interest is server clusters, but it's
equally applicable to LTSP clients. So my emphasis is Linux NBPs -
pxelinux vs Etherboot vs others, and DHCP and TFTP settings they need.
Anything else would be a reference to Intel's docs or to other net boot
howtos.

> None covered emerging technologies such as support for IA64 architecture
> hardware, let alone covered the various types of servers available from
> other vendors.

> anyway, back to my original subject, my PXE Server HOWTO... any comments,
> suggestions would be appreciated.... should I continue ?? :)

By PXE *server* you mean server software specifically for PXE, yes?
Stuff that talks Intel MTFTP? Way outside my experience, so no conflict
here, I think. It sounds like my ideas and yours are fairly
complementary. I'd like to improve the various other netboot related
howtos as well, given that I now have quite some experience here.

I should add by the way, that I don't *like* PXE: it is a clunky design,
implemented badly. My colleague who wrote the PXE code for Etherboot
laughs at it; H Peter Anvin, who wrote pxelinux, has a list of
implementation bugs and design flaws. One of my sections will be how to
replace it with something better, e.g. flashing Etherboot. However it's
what many of us are stuck with coutesy of vendors, site policies and the
need to be able to use Windoze.




Subject: Re: [Proposal] PXE Server HOWTO
From: Charles Curley ####@####.####
Date: 26 Jan 2002 14:00:18 -0000
Message-Id: <20020126065924.A19892@trib.com>

On Fri, Jan 25, 2002 at 08:22:08PM -0500, Randy Tata wrote:
> Keith,
> 
> Yes!
> 


> 
> PXE is pre-boot execution environment.  Basically you boot off your network
> card (by boot ROM or ROM Img on floppy), dhcp an address, and load a pre-os
> environment from a server which can allow you to partition, format, install,
> etc. to the client machine.  I'm sure you've seen "network" as a choice in
> your BIOS boot order selection.  This would be a HUGE step in the right
> direction of enabling system administrators to easily do mass roll-outs of
> Linux over Windows clients (for that microsoft-free utopian society :)

This sounds like it could be useful for bare metal restore, aka
complete backup & recovery. I have a HOWTO in the pipeline on exactly
that, so will be interested to see what you come up with.

-- 

		-- C^2

The world's most effective anti-virus software: Linux.

Looking for fine software and/or web pages?
http://w3.trib.com/~ccurley

--> -->
 
 
<type 'exceptions.IOError'>
Python 2.5.2: /usr/bin/python
Sat Jun 15 05:21:56 2024

A problem occurred in a Python script. Here is the sequence of function calls leading up to the error, in the order they occurred.

 /opt/ezmlm-browse-0.20/<string> in ()
 /opt/ezmlm-browse-0.20/main.py in main()
  424 
  425         if path is not None:
  426                 main_path(path)
  427         else:
  428                 main_form()
global main_form = <function main_form at 0x875ac6c>
 /opt/ezmlm-browse-0.20/main.py in main_form()
  378         except ImportError:
  379                 die(ctxt, "Invalid command")
  380         module.do(ctxt)
  381 
  382 def main():
module = <module 'commands.showthread' from '/opt/ezmlm-browse-0.20/commands/showthread.pyc'>, module.do = <function do at 0x8778294>, global ctxt = {'HTTP_X_FORWARDED_SERVER': 'glitch', 'HTTP_REFE...HTTP_ACCEPT_ENCODING': 'gzip, br, zstd, deflate'}
 /opt/ezmlm-browse-0.20/commands/showthread.py in do(ctxt={'HTTP_X_FORWARDED_SERVER': 'glitch', 'HTTP_REFE...HTTP_ACCEPT_ENCODING': 'gzip, br, zstd, deflate'})
    9         ctxt.update(ezmlm.thread(ctxt[THREADID]))
   10         header(ctxt, 'Thread: ' + ctxt[SUBJECT], 'showthread')
   11         do_list(ctxt, 'msgs', ctxt[MSGSPERPAGE], ctxt[MESSAGES],
   12                         lambda:sub_showmsg(ctxt, ctxt[MSGNUM]))
   13         footer(ctxt)
global sub_showmsg = <function sub_showmsg at 0x875a1ec>, ctxt = {'HTTP_X_FORWARDED_SERVER': 'glitch', 'HTTP_REFE...HTTP_ACCEPT_ENCODING': 'gzip, br, zstd, deflate'}, global MSGNUM = 'msgnum'
 /opt/ezmlm-browse-0.20/globalfns.py in do_list(ctxt={'HTTP_X_FORWARDED_SERVER': 'glitch', 'HTTP_REFE...HTTP_ACCEPT_ENCODING': 'gzip, br, zstd, deflate'}, name='msgs', perpage=10, values=[{'author': u'Keith Strachan', 'authorid': 'kpkbkmalahgkhoddiipa', 'date': '24 Jan 2002 18:35:13 -0000', 'month': 200201, 'msgnum': 2155, 'subject': u'[Proposal] PXE Server HOWTO', 'threadid': 'hjidhfcmaanogoghefno', 'timestamp': 1011897313.0}, {'author': u'David Merrill', 'authorid': 'lagflfnealnmhgbpnfbe', 'date': '24 Jan 2002 21:25:33 -0000', 'month': 200201, 'msgnum': 2158, 'subject': u'Re: [Proposal] PXE Server HOWTO', 'threadid': 'hjidhfcmaanogoghefno', 'timestamp': 1011907533.0}, {'author': u'Randy Tata', 'authorid': 'baiggcchbjhbafmfkggg', 'date': '26 Jan 2002 01:22:25 -0000', 'month': 200201, 'msgnum': 2181, 'subject': u'Re: [Proposal] PXE Server HOWTO', 'threadid': 'hjidhfcmaanogoghefno', 'timestamp': 1012008145.0}, {'author': u'David Merrill', 'authorid': 'lagflfnealnmhgbpnfbe', 'date': '26 Jan 2002 02:45:31 -0000', 'month': 200201, 'msgnum': 2182, 'subject': u'Re: [Proposal] PXE Server HOWTO', 'threadid': 'hjidhfcmaanogoghefno', 'timestamp': 1012013131.0}, {'author': u'Keith Strachan', 'authorid': 'kpkbkmalahgkhoddiipa', 'date': '26 Jan 2002 04:30:22 -0000', 'month': 200201, 'msgnum': 2183, 'subject': u'Re: [Proposal] PXE Server HOWTO', 'threadid': 'hjidhfcmaanogoghefno', 'timestamp': 1012019422.0}, {'author': u'Charles Curley', 'authorid': 'blnflnoieggjgfeejfli', 'date': '26 Jan 2002 14:00:18 -0000', 'month': 200201, 'msgnum': 2184, 'subject': u'Re: [Proposal] PXE Server HOWTO', 'threadid': 'hjidhfcmaanogoghefno', 'timestamp': 1012053618.0}, {'author': u'Charles Curley', 'authorid': 'blnflnoieggjgfeejfli', 'date': '26 Jan 2002 20:53:07 -0000', 'month': 200201, 'msgnum': 2191, 'subject': u'Re: [Proposal] PXE Server HOWTO', 'threadid': 'hjidhfcmaanogoghefno', 'timestamp': 1012078387.0}, {'author': u'Markus Gutschke', 'authorid': 'ccckhidhcakkcjofagjo', 'date': '26 Jan 2002 20:56:44 -0000', 'month': 200201, 'msgnum': 2192, 'subject': u'Re: [Proposal] PXE Server HOWTO', 'threadid': 'hjidhfcmaanogoghefno', 'timestamp': 1012078604.0}, {'author': u'Keith Strachan', 'authorid': 'kpkbkmalahgkhoddiipa', 'date': '27 Jan 2002 01:33:03 -0000', 'month': 200201, 'msgnum': 2193, 'subject': u'Re: [Proposal] PXE Server HOWTO', 'threadid': 'hjidhfcmaanogoghefno', 'timestamp': 1012095183.0}, {'author': u'Markus Gutschke', 'authorid': 'ccckhidhcakkcjofagjo', 'date': '27 Jan 2002 01:58:06 -0000', 'month': 200201, 'msgnum': 2194, 'subject': u'Re: [Proposal] PXE Server HOWTO', 'threadid': 'hjidhfcmaanogoghefno', 'timestamp': 1012096686.0}], peritem=<function <lambda> at 0x877848c>)
  128                 write(template % ctxt)
  129                 if peritem:
  130                         peritem()
  131                 ctxt[ROW] += 1
  132 
peritem = <function <lambda> at 0x877848c>
 /opt/ezmlm-browse-0.20/commands/showthread.py in ()
    9         ctxt.update(ezmlm.thread(ctxt[THREADID]))
   10         header(ctxt, 'Thread: ' + ctxt[SUBJECT], 'showthread')
   11         do_list(ctxt, 'msgs', ctxt[MSGSPERPAGE], ctxt[MESSAGES],
   12                         lambda:sub_showmsg(ctxt, ctxt[MSGNUM]))
   13         footer(ctxt)
global sub_showmsg = <function sub_showmsg at 0x875a1ec>, ctxt = {'HTTP_X_FORWARDED_SERVER': 'glitch', 'HTTP_REFE...HTTP_ACCEPT_ENCODING': 'gzip, br, zstd, deflate'}, global MSGNUM = 'msgnum'
 /opt/ezmlm-browse-0.20/globalfns.py in sub_showmsg(ctxt={'HTTP_X_FORWARDED_SERVER': 'glitch', 'HTTP_REFE...HTTP_ACCEPT_ENCODING': 'gzip, br, zstd, deflate'}, msgnum=2184)
  229         format_timestamp(ctxt, ctxt)
  230         write(html('msg-header') % ctxt)
  231         rec_showpart(ctxt, msg, 0)
  232         write(html('msg-footer') % ctxt)
  233         ctxt.pop()
global rec_showpart = <function rec_showpart at 0x875a1b4>, ctxt = {'HTTP_X_FORWARDED_SERVER': 'glitch', 'HTTP_REFE...HTTP_ACCEPT_ENCODING': 'gzip, br, zstd, deflate'}, msg = <email.message.Message instance at 0x87d58ec>
 /opt/ezmlm-browse-0.20/globalfns.py in rec_showpart(ctxt={'HTTP_X_FORWARDED_SERVER': 'glitch', 'HTTP_REFE...HTTP_ACCEPT_ENCODING': 'gzip, br, zstd, deflate'}, part=<email.message.Message instance at 0x87d58ec>, partnum=1)
  205                 else:
  206                         for p in part.get_payload():
  207                                 partnum = rec_showpart(ctxt, p, partnum+1)
  208         else:
  209                 write(html('msg-sep') % ctxt)
partnum = 1, global rec_showpart = <function rec_showpart at 0x875a1b4>, ctxt = {'HTTP_X_FORWARDED_SERVER': 'glitch', 'HTTP_REFE...HTTP_ACCEPT_ENCODING': 'gzip, br, zstd, deflate'}, p = <email.message.Message instance at 0x87d588c>
 /opt/ezmlm-browse-0.20/globalfns.py in rec_showpart(ctxt={'HTTP_X_FORWARDED_SERVER': 'glitch', 'HTTP_REFE...HTTP_ACCEPT_ENCODING': 'gzip, br, zstd, deflate'}, part=<email.message.Message instance at 0x87d588c>, partnum=2)
  208         else:
  209                 write(html('msg-sep') % ctxt)
  210                 sub_showpart(ctxt, part)
  211         return partnum
  212 
global sub_showpart = <function sub_showpart at 0x875a144>, ctxt = {'HTTP_X_FORWARDED_SERVER': 'glitch', 'HTTP_REFE...HTTP_ACCEPT_ENCODING': 'gzip, br, zstd, deflate'}, part = <email.message.Message instance at 0x87d588c>
 /opt/ezmlm-browse-0.20/globalfns.py in sub_showpart(ctxt={'HTTP_X_FORWARDED_SERVER': 'glitch', 'HTTP_REFE...HTTP_ACCEPT_ENCODING': 'gzip, br, zstd, deflate'}, part=<email.message.Message instance at 0x87d588c>)
  164         type = ctxt[TYPE] = part.get_content_type()
  165         ctxt[FILENAME] = part.get_filename()
  166         template = html('msg-' + type.replace('/', '-'))
  167         if not template:
  168                 template = html('msg-' + type[:type.find('/')])
global template = <function template at 0x8752e9c>, global html = <function html at 0x8752ed4>, type = 'application/pgp-signature', type.replace = <built-in method replace of str object at 0x87d4ad8>
 /opt/ezmlm-browse-0.20/globalfns.py in html(name='msg-application-pgp-signature')
   40 
   41 def html(name):
   42         return template(name + '.html')
   43 
   44 def xml(name):
global template = <function template at 0x8752e9c>, name = 'msg-application-pgp-signature'
 /opt/ezmlm-browse-0.20/globalfns.py in template(filename='msg-application-pgp-signature.html')
   31         except IOError:
   32                 if not _template_zipfile:
   33                         _template_zipfile = zipfile.ZipFile(sys.argv[0])
   34                 try:
   35                         f = _template_zipfile.open(n).read()
global _template_zipfile = None, global zipfile = <module 'zipfile' from '/usr/lib/python2.5/zipfile.pyc'>, zipfile.ZipFile = <class zipfile.ZipFile at 0x86eba7c>, global sys = <module 'sys' (built-in)>, sys.argv = ['-c', '/opt/ezmlm-browse-0.20']
 /usr/lib/python2.5/zipfile.py in __init__(self=<zipfile.ZipFile instance at 0x87d524c>, file='-c', mode='r', compression=0, allowZip64=False)
  337             self.filename = file
  338             modeDict = {'r' : 'rb', 'w': 'wb', 'a' : 'r+b'}
  339             self.fp = open(file, modeDict[mode])
  340         else:
  341             self._filePassed = 1
self = <zipfile.ZipFile instance at 0x87d524c>, self.fp = None, builtin open = <built-in function open>, file = '-c', modeDict = {'a': 'r+b', 'r': 'rb', 'w': 'wb'}, mode = 'r'

<type 'exceptions.IOError'>: [Errno 2] No such file or directory: '-c'
      args = (2, 'No such file or directory')
      errno = 2
      filename = '-c'
      message = ''
      strerror = 'No such file or directory'