google/ibiblio for main sfs and dropbox for save file

[technosaurus]

I think I have gotten the largest part of this solved but will need to do a few more things.

init will need to be modified to:
1. automatically connect to internet - this is possible using kernel parameter such as essid=myconnection wepkey=.......
(need a little help here)
2. then we would need to get the main sfs from somewhere ... another kernel param such as sfsurl=code.google.com/.../puppy-6.0.sfs (it could be hard coded, but easier to build a local version this way).
Can we just union mount it over the initramfs? (or tmpfs with the tinycore patch)?
3. the last part is a bit trickier, each time we shutdown we would need to optionally unmount, (compress?) & re-upload a savefile, dropbox is one option - I built a script that will do it via curl, but would need another kernel parameter for that ...saveurl=www.dropbox.com/.../mysave.4fs.
Same question as previous - union over initramfs?
4. have all of the commands in the initramfs to support above (all of which can be supported by busybox and curl - any other options that _would_ work with busybox would be nice, but curl was the only tool I found that worked for dropbox, please tell me if there is a better site/tool)

... just trying to work it out in my head first - anyone have recommendations that I am overlooking (other than needing quite a bit of ram)

[Lobster]

Remarkable.
Which components to store online and which locally?
What is the idea behind this?

[Dingo]

I do not recommend dropbox for massive use and high bandwidth consuming

dropbox has a very little tolerance regarding bandwidth use

in fact, when a certain limit (unknown) is reached, dropbox blocks download links

[technosaurus]

each user would need their own dropbox account and it would only need to be used at boot... maybe a few times a day and a compressed save file is quite small if no extra apps are installed (just documents and settings in $HOME reduce to ~100kb compressed 2fs.bz2 from any size save file) that shouldn't raise any flags - the main sfs could be on google code and pfix=ram boots would only need that for cloud computing.

The only thing you would need are the bootloader (grub, syslinux, isolinux, etc...) and kernel image with a builtin initramfs.

The pfix=ram style mode I can get onto a floppy (and of course cd or usb) including a basic jwm desktop and terminal to tell you it is downloading the sfs etc... theoretically it wouldn't even need to support any filesystems at all - thus preventing you (or your kids in my case) from accidentally modifying the hard drive(s)
The full version would be similar, but the filesystem modules could be in the main sfs along with all the apps.

[edoc]

Is the purpose of this adventure another "cloud" Puppy?

Will the boot code be modifiable to use locations other than google and dropbox?