Seems I remember 2 tools that already do that. You may want to look over their work. "Emerge" and "Netboot Me"

I'm sure there are other web PXE tools that do this. But, I'm not sure how they accomplish it. I willing to help if I can.

Hope this helps_________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

If you want to boot from a website (as your debian links alluded), it's very easy. All you need is the gpxe *) boot disk (cd/usb/floppy - choose whatever you want), and boot from it. When the computer boots, press Ctrl-B, and type:
Code:
dhcp net0
chain http://your-web-server/your-single-file-puppy

The webserver obviously can be anything, it can be ibiblio (if someone uploads the single-file-puppy there), or it can be local webserver as in my screenshot. Your single-file-puppy can be created in this way:
1. Use mknetboot.sh to get the humoungous initrd.gz and vmlinuz.
2. Use wraplinux to combine this humoungous initrd.gz and vmlinuz together.
There you have it!

*) I used gpxe because ipxe, at the time of writing, doesn't work for me. And it only provides iso download for CD, other media is not supported (ie you have to compile it yourself).
**) those mknbi tools referred in the debian links is now known as "wraplinux", which is what I use.
***) you don't even need to use wraplinux really. Only the mknetboot.sh step is required, because you can do this in gpxe as well
Code:
dhcp net0
kernel http://your-web-server/vmlinuz
initrd http://your-web-server/initrd.gz
boot

as i already set up webserver at my linux mint so the location of the
files at linux-mint is at ---> /var/www
its working and puppy, btw we need to set permission so we can download the files.
also we need to press ctrl-b rather quick.

Posted: Mon 25 Apr 2011, 01:46 Post subject:
What do you guys think of using memdisk to PXE boot?

What do you guys think about using memdisk to simulate a CDROM from an ISO image in order to PXE boot Puppy Linux?

We'd have to push the maintainers to add a couple of 6kB kernel modules and then run the 4kB 'memdiskfind' binary from the syslinux package at http://ftp.debian.org/pool/main/s/syslinux but after that, it would just be a simple matter of putting this in pxelinux.cfg

Code:

LINUX memdisk
INITRD lupu-525.iso
APPEND iso

and it should PXE boot pretty much as if there were a Puppy CD in a physical CDROM drive.

Do you guys think that people would balk at adding 17kB (7kB compressed) to the initrd.gz?

I have already seen, but it does not work or I do not understand
but I finally managed to run with a save in the initrd.
I see init changed.

1. A pupsave inside initrd is gone once the computer is rebooted. Might as well run from RAM then.
2. The idea of loading pup.sfs from NBD/CIFS/SSHFS/whatever is so that you don't have to load the entire pup.sfs into RAM (which is the case if pup.sfs is embedded into initrd). Thus, more RAM available for the apps with trade-off that apps launch becomes slower (because it has to access the network share)._________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.

Posted: Thu 28 Apr 2011, 01:11 Post subject:
Re: What do you guys think of using memdisk to PXE boot?

dlou99 wrote:

What do you guys think about using memdisk to simulate a CDROM from an ISO image in order to PXE boot Puppy Linux?

We'd have to push the maintainers to add a couple of 6kB kernel modules and then run the 4kB 'memdiskfind' binary from the syslinux package at http://ftp.debian.org/pool/main/s/syslinux but after that, it would just be a simple matter of putting this in pxelinux.cfg

Code:

LINUX memdisk
INITRD lupu-525.iso
APPEND iso

and it should PXE boot pretty much as if there were a Puppy CD in a physical CDROM drive.

Do you guys think that people would balk at adding 17kB (7kB compressed) to the initrd.gz?

Sounds interesting. Fatdog64 already has the required modules, all that is needed is to move these modules from pup.sfs to initrd. Fatdog also has memdiskfind, but currently it's a dynamically linked, so it has to be recompiled with klibc or dietlibc to make it standalone so that it can be put into initrd (or if a static memdiskfind is already available, just use it). Then all we need is to patch /init with code to load the iso from MTD device instead of /dev/sr0._________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.

2. The idea of loading pup.sfs from NBD/CIFS/SSHFS/whatever is so that you don't have to load the entire pup.sfs into RAM (which is the case if pup.sfs is embedded into initrd). Thus, more RAM available for the apps with trade-off that apps launch becomes slower (because it has to access the network share).

The downside is that you have to have a bloatload of network drivers in the initrd and either figure out which to load or go and load all of them.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum