Puppy Linux Discussion Forum

[MagicZaurus]

Thanks a lot jamesbond for packaging this all so nicely together. I didn't have time to test it, but with all your efforts netbooting Puppy has become so much easier.

[jamesbond]

Thanks for your kind words, MagicZaurus.

gcmartin found a bug in mknetboot.sh (this is due to Xdialog/GTK bug). Here's a fix - it's not perfect, but at least it works.

cheers!

[mhanifpriatama]

Maybe helps some one.
I use another way. I used for my small internet cafe.
My server uses lupu511, my client uses lupu503.

On server :
1. Install dnsmasq
2. create /etc/dnsmasq.conf
3. write code inside dnsmasq.conf :

[mhanifpriatama]

I did this on my lupu 520 thin-client :
put my script on rc.local

[Master_wrong]

Thank you for the script.

so you put the script on rc.local, the remaster, the the remastered iso is used to boot the client via pxe ?

correct ?

[Aitch]

Hi all

For anyone still struggling with PXE booting, I've just come home from a Linux/Cloud Show at Barbican, UK, and saw this demo'd, at the show

http://ipxe.org/

I don't know if it's any use/can be incorporated into puppy, but it seemed impressive with a wide range of network cards supported, and range of implementation formats

[gcmartin]

Thanks @Aitch

This is a client-side application. Thus, it ONLY applies to the client one is trying to have starting over the LAN.

This is something that one can use if his PC's PXE motherboard support is problematic (doesn't work) or if the PC someone is trying to use doesn't have a PXE LAN function on the motherboard so this might allow him to find the PXE server on the LAN (although I haven't tried it yet) and boot their machine using the ISA/PCI LAN card in their PC.

The PXE server should could care less. It will serve whomever makes the request for service. iPXE running on a LAN machine will allow the requesting PC to make that request if his machine cannot do it under its own power.

Hope this helps

[mhanifpriatama]

[mhanifpriatama]

Just report, may be useful.

If I want to customize thin-client lupu-520.sfs, I remaster it.
But, this thing eat time a lot.
So, I just customize initrd.gz :
1. extract initrd.gz
2. put a script, exp : aa.sh
3. little hack the init script : copy aa.sh to initrd/mnt/data

How to run that script?
Do remaster, or edit the lupu-520.sfs.
Then add these line to rc.local :

[Master_wrong]

hi mhanifpriatama,


thank you...

oh another sfs loading hack

that can be useful...

[mhanifpriatama]

anyone knows, how to make nfs client run at initrd.gz, so can look at pup.sfs on virtual drive?

[gcmartin]

Hi @Mhanifpriatama

[vezuve]

Hello,
Online translation-traduction en ligne
I would like to know if there is the possibility of having the pupsave on the server, so that the customer (slave) puppy could have access by network.
Originale
Je voudrais savoir si il y a la possibilité d'avoir le pupsave sur le serveur, afin que le puppy client (esclave) puisse avoir accès par le réseau.
@+

[mhanifpriatama]

thanks gc.martin,
I want my server run nfs server. I think that kernel module.
So, my server can offer drive-sharing (like virtual hard drive).
I want my client run nfs-client. I think that kernel module too.
So, my client can see the virtual drive.

If nfs-client can run before loading my lupu_520.sfs, I can place it at virtual drive, then the init script can mount it.

I think this will solve the old computer client with very low ram.

Sorry. My native is not english.

[mhanifpriatama]

@vezuve, I think we have same Idea but differ purpose.
upload of pupsave file is init script job. I think, I must do some experiment. I'll report it if I success.
Of course, if any one have known a lot of init's work, and also nfs work, may be this is an easy things.
And ... I am not a bash programmer.