Re: Configure PXES to run local programs while disconnected from the network.

Diego Torres Milano <[email protected]>
Newsgroups gmane.linux.pxes.devel
Organization IN3
Message-ID <1091302338.6282.36.camel@zebra>
On Sat, 2004-07-31 at 14:55, Gary Kypers wrote:
> Here is what I am trying to do:
> 
> - I have a client computer connected to measuring
> devices.
> - The client should boot from the network and run
> programs locally.
> - The measurementes need to be continuous.
> - At the client there is an on-board 48MB IDE DOM
> (Disk-On-Module) that is /dev/hda1
> - The purpose of the DOM is to capture the measurement
> information in case of network interruption or server
> unavaliability.
> - I had tried LTSP, mounting the /dev/hda1 DOM under
> the root filesystem. Everything worked fine until I
> disconnected the network to simmulate network
> unavailability. Since LTSP mounts its root via nfs and
> the DOM is mounted on root, the lack of network
> contact kills the ability to write to the local DOM
> (it has to go through root which is nfs).
That's the main advantage of PXES. The root filesystem is not mounted
via nfs and everything can be local and no network is needed.
If you have some spare space in the DOM you can also install PXES
locally. You only need 4 Mb for a text only PXES session and about 7 Mb
for a local graphical desktop.
> 
> Please note that my point of view may be limiting my
> ability to understand PXES. I think PXES is supposed
> to be a terminal that accesses a server and runs
> programs on the server? What I am trying to do is to
> have an unattended workstation running a daemon. So
> bear with me please!
Perfectly possible. One of the PXES sessions is a local graphical
desktop (in only 7 Mb ! or even less).
I've been implemented customized PXES text only session, even running
dialog and other newt applications in less than 4 Mb.

> 
> I am trying to set up PXES to:
> 1) boot off the network (done except for "ERROR"
> below).
> 2) load nfs share on server
>   I imagine there is an rc.d/rc.local file that can
> contain instructions to mount drives, configure local
> serial devices and lauch local programs. (I could do
> the nfs mount it via fstab I suppose, but I prefer the
> control of rc).
> 3) load program from nfs share and execute locally (at
> client)
> 4) Mount the DOM (/dev/hda1) on the local root fs. 
>    In "Optional Local Devices" "shared devices
> configuration" I have the "hard disk" checked off. But
> this might be only the server's hard disk? Not the
> local hard disk (since it is not "shared").
> 5) Be tolerant of server unavailability
> 6) write to local ramdisk and local /dev/hda1 (48MB
> IDE DOM) even if the network is unavailable 
> 
> 
> 
> ERROR: telnet.sh (0) is respawning too fast. Please
> check the configuration.
> 
> This may not be important since I can get a local
> session open via <Alt><F4>.
> 
> PROBLEM: Even though the "General Configuration" "wait
> for key press before connecting login server"  is not
> checked off the terminal waits at a "boot:" prompt.
> Answer: There is a timeout which can be specified in
> the configuration
> Question: Where is the configuration item located?
> 
> 
> Any help is greatly appreciated
> 
> Grey
> 
> 
> 
> 		
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - Send 10MB messages!
> http://promotions.yahoo.com/new_mail
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source Technology
> Group. Come see the changes on the new OSTG site. www.ostg.com
> _______________________________________________
> pxes-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/pxes-devel



-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.