Re: (no subject)

Hi Guys,

I figure ... if you get a PXE boot floppy image (source on the PXES
site).

Just like how you get ntloader to boot linux ie. dd the first 512 bytes
(MBR) off your linux drive and point ntloader at it so I reckon you
could probably do the same with a PXE floopy boot record :)

http://www.wlug.org.nz/HowToLinuxNTLoader

James

On Wed, 2003-12-03 at 04:35, Diego Torres Milano wrote:

> Leonardo Fuchs wrote:
> 
> >Well, first of all..thank you all very much! I'll take your tips to try to
> >resolve my Fixed ip issue.
> >I know messing with every station to configure a static ip isn't the most
> >beautifull solution, but, would you find a better one when you want to save
> >network bandwidth?
> >
> You should face the upgrade problem, because installing software that 
> need to be upgraded in a client disk is one of the problems PXES (and 
> thin clients in general) tries to solve.
> I've deployed very large installation in remote locations with bandwith 
> limitations and the TFTP/DNS sec/DHCP relay, linux appliance (could be 
> other thin client as well) is the best solution I've found, it's really 
> fault tolerant and ready for mission critical.
> 
> >Pehaps, i would have all my servers in a secure location on a central office
> >and my stations on a branch office..i would like to have only KVM data on my
> >Wan Link...
> >
> >thank you all again,
> >
> >Leo
> >----- Original Message ----- 
> >From: "Chris Gianelloni" <[email protected]>
> >To: <[email protected]>
> >Sent: Tuesday, December 02, 2003 10:00 AM
> >Subject: Re: [pxes-devel] (no subject)
> >
> >On Mon, 2003-12-01 at 10:31, [email protected] wrote:
> >  
> >
> >>hey, but this way you would make me to create a pxes image for every
> >>client i have (and that would make a DHCP server solution the best thing
> >>around to resolve this issue), But this is not what i am asking - sorry, i
> >>did not make the right question.
> >> The idea is to create a single image and then write this on the D.O.C.
> >>chip. Then, since pxes boots from the D.O.C. an administrator could
> >>manually configure the Ip address information on every thin client by
> >>running a bash script or modifying some configuration file.
> >>
> >>is there a way?
> >>    
> >>
> >
> >Sure there's a way, but simply running a DHCP server would be WAY
> >easier.  You could easily mount the initrd as a loopback and edit the rc
> >files in /etc/init.d manually to use a static address per machine, but
> >that is an ugly hack and requires much more administrative overhead.  In
> >my opinion, it just isn't worth the effort.
> >
> >  
> >
> >>>You can add ip=... to the kernel command line.
> >>>Check the kernel documentation or take a look at
> >>>/opt/pxes-0.7/stock/dist/etc/init.d/rc.ip. My advice: set up a DHCP
> >>>server.
> >>>
> >>>On Thu, Nov 27, 2003 at 04:17:04PM -0200, [email protected] wrote:
> >>>      
> >>>
> >>>>I need to set pxes in a D.O.C. chip, so i'll need a pxes image with
> >>>>fixed ip addresses. Is there any way to configure ip addressing
> >>>>information in the pxes image? some bash script pehaps?
> >>>>
> >>>>thanks,
> >>>>
> >>>>Leonaro
> >>>> >-- Original Message --
> >>>> >From: "Tim Bates" <tin@ii...>
> >>>> >To: <pxes-devel@li...>
> >>>> >Reply-To: pxes-devel@li...
> >>>> >Date: Wed, 26 Nov 2003 19:14:30 +1100
> >>>> >Subject: Re: [pxes-devel] PXES with fixed IP
> >>>> >
> >>>> >
> >>>> >> The HOWTO's on the site are clear to me, but how can I use a fixed
> >>>>IP
> >>>> for
> >>>> my
> >>>> > clients. Do I have to modify a ini-file or so ?
> >>>> > Could somebody help me? I've little experience with Linux (bash).
> >>>>
> >>>> The IP addresses for the clients are set using DH
> >>>> >P. You can set fixed IP
> >>>> addresses based on the Ethernet (hardware) address of the client
> >>>>cards. I assume you will be using a MS DHCP server, which means I
> >>>>cant really give you an example config, but there should be enough
> >>>>info in the help for DHCP
> >>>>
> >>>> >onfig in Windows server.
> >>>>
> >>>> Tim Bates
> >>>>
> >>>>
> >>>>
> >>>> -------------------------------------------------------
> >>>> This SF.net email is sponsored by: SF.net Giveback Program. Does
> >>>>SourceForge.net help you be more productive?  Does it help you create
> >>>>better code?
> >>>> >SHARE THE LOVE, and help us help
> >>>> YOU!  Click Here: http://sourceforge.net/donate/
> >>>> _______________________________________________
> >>>> pxes-devel mailing list
> >>>> pxes-devel@li...
> >>>> https://lists.sourceforge.net/lists/listinfo/pxes-devel
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> -------------------------------------------------------
> >>>> This SF.net email is sponsored by: SF.net Giveback Program. Does
> >>>>SourceForge.net help you be more productive?  Does it help you create
> >>>>better code?  SHARE THE LOVE, and help us help YOU!  Click Here:
> >>>> http://sourceforge.net/donate/
> >>>> _______________________________________________
> >>>> pxes-devel mailing list
> >>>> pxes-devel@li...
> >>>> https://lists.sourceforge.net/lists/listinfo/pxes-devel
> >>>>
> >>>>
> >>>>
> >>>> -------------------------------------------------------
> >>>> This SF.net email is sponsored by: SF.net Giveback Program. Does
> >>>>SourceForge.net help you be more productive?  Does it help you create
> >>>>better code?  SHARE THE LOVE, and help us help YOU!  Click Here:
> >>>> http://sourceforge.net/donate/
> >>>> _______________________________________________
> >>>> pxes-devel mailing list
> >>>> pxes-devel@li...
> >>>> https://lists.sourceforge.net/lists/listinfo/pxes-devel
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>-------------------------------------------------------
> >>>>This SF.net email is sponsored by: SF.net Giveback Program.
> >>>>Does SourceForge.net help you be more productive?  Does it
> >>>>help you create better code?  SHARE THE LOVE, and help us help
> >>>>YOU!  Click Here: http://sourceforge.net/donate/
> >>>>_______________________________________________
> >>>>pxes-devel mailing list
> >>>>[email protected]
> >>>>https://lists.sourceforge.net/lists/listinfo/pxes-devel
> >>>>        
> >>>>
> >>>--
> >>><table BORDER=0 CELLSPACING=0 CELLPADDING=2 BGCOLOR="#FFFFFF" >
> >>><tr><td>
> >>><pre><font size=-1>    ______  ________
> >>>
> >>>   /  /   \/  /___  )  I  N   T   E   G   R   A   C   I   O   N
> >>>  /  /       /___  /   I  N   F   O   R   M   A   T   I   C   A
> >>> /__/__/\___/_____'
> >>>
> >>></font> Diego Torres Milano <font size=-2>Maipu 42 Office 164 -
> >>>(C1084ABB) Buenos Aires  Argentina </font> <b><a
> >>>href="mailto:[email protected]">[email protected]</a></b>  <font size=-2>
> >>> Tel: +5411 4331-2233 Fax +5411 4331-3377
> >>><i>www.in3.com.ar</i></font></pre> </td></tr>
> >>></table>
> >>>
> >>>
> >>>-------------------------------------------------------
> >>>This SF.net email is sponsored by: SF.net Giveback Program.
> >>>Does SourceForge.net help you be more productive?  Does it
> >>>help you create better code?  SHARE THE LOVE, and help us help
> >>>YOU!  Click Here: http://sourceforge.net/donate/
> >>>_______________________________________________
> >>>pxes-devel mailing list
> >>>[email protected]
> >>>https://lists.sourceforge.net/lists/listinfo/pxes-devel
> >>>      
> >>>
> >>
> >>
> >>
> >>-------------------------------------------------------
> >>This SF.net email is sponsored by: SF.net Giveback Program.
> >>Does SourceForge.net help you be more productive?  Does it
> >>help you create better code?  SHARE THE LOVE, and help us help
> >>YOU!  Click Here: http://sourceforge.net/donate/
> >>_______________________________________________
> >>pxes-devel mailing list
> >>[email protected]
> >>https://lists.sourceforge.net/lists/listinfo/pxes-devel
> >>    
> >>






This e-mail is solely for the use of the intended recipient and may
contain information which is confidential or privileged. Unauthorised
use of its contents is prohibited. If you receive this e-mail in error,
please notify the sender immediately via e-mail and then delete the
original e-mail.