LanPuppy...At Last... [ Testing & Suggestions ]
Posted: Sun 30 Jul 2006, 03:11
I've been working on LanPuppy for about 8 months (much too long, it should have been quicker).
Lots of folks here have contributed, I wanted to make a list but didn't want to leave anyone out.
The last bit of help was by Ted Dog, who was also one of the first to help when I first came here.
I've kept it simple & as similar to the standard Puppy as I could with only a few changes over all.
The PupServer / LanPuppy package seems to work well, the tools I've made aren't as tested.
I haven't made a manual as such, but raffy suggested that I post it anyway to get it going.
So as bug reports & suggestions for improvements come in, & I answer Qs, I'll compile Docs.
LanPuppy / PupServer setup:
The PupServer is built on EmptyCrust-1.0.7, other Puppy 1 versions would probably work also.
The PupServer is a frugal setup (3 base Puppy files), with Samba server DotPup installed.
The LanPuppy1-01.pup package checks for Samba server install & if networking is setup.
It installs DHCP3, Xinet, Tftp-hpa, & makes dirs.: /docs, /public, /homes, /tftpboot, & /lanpup.
I've been using SimplePup for a client as I like it, most any Puppy 1 versions should work.
I use a frugal install on the H.D., it might work on a full H.D. install, I haven't tried it.
I don't use CDs to run Puppy, but a little modification would allow the setup to work on a CD.
PXE network booting:
PCs with a BIOS PXE network boot option should work for client PCs.
Also PXE ready NICs, on eBay I bought 10: "3com-905c-tx-m" used for $3 each!
Alot of the Intel NICs do PXE boot also, but I haven't used any of them.
I just tested out a EtherBoot PXE Floppy Disk, & it's worked on all the PCs I've got, WOW!
I'm posting this from a 2.4 AMD PC that booted with the floppy from a 1.7 Celeron PC.
Limitations:
The number of clients is controlled by the HOME share dirs., for more clients add more dirs.
The clients run as root user with no login same as Puppy, so there's one setup per client.
This will work well for homes, keosks, churches, small offices, & maybe classrooms.
I'm sure many will want a login with separate users & work spaces for a more robust setup.
When booting, each client briefly uses a common IP add. (x.x.x.9), so stagger booting.
Save & Squash files:
One change is the "save" file is used for settings & app. installs, work space is a share.
The "save" file can be as small as 8 MB, but to install apps. it must be larger.
There's a dir.: /homes/pup-BASE for a base save file, if you want custom settings.
Ideally I'll make an "everything" squash file (any help offers?), so no apps. to install.
All the clients use the same squash file, so there's only one, so it can be HUGE (1 - 2 GB?).
With some modifing,the clients could share the same app. install dir. (/root/.usr)... trick!
Tools:
I've written tools to help administer LanPuppy, but I haven't spent much time testing them.
Better tools are needed, but as LanPuppy changes different tools will be needed.
The main tool is: "xmklanpup", it extracts a Puppy ISO file & modifies it into a LanPuppy.
"xhomesadd" makes client HOME share dirs. & copies a base "save" file, if there's one.
"xmntroot" allows the administrator to mount the clients "save" file to work with it.
"xbootmount" is a PupServer utility to auto. mount H.D.s at bootup.
I want to make a DotPup tool from the package: "MakePxeBootFloppy.tar.gz".
Abilities:
240 clients are allowed (IP add. x.x.x.11 to .250), that can be booted by WakeOnLan.
The usr_devx.sfs developers file & MU's usr_more.sfs MegaPup file work... not tested.
PupServer supplies internet info, so new client's have web access immediately, no setup!
PupServer could boot any PXE ready Linux distro. (Knoppix, DSL) & even Win95 & Win98!
A WinBlows PC can also be a boot server with an app. called tftpd32, but then... WHY?
I'll work with LanPuppy1 for a bit to debug it, then I'll look at using Puppy2 for clients.
PupServer install:
Put EmptyCrust Puppy on a H.D. & setup to boot, install Samba server & LanPuppy.
After installing LanPuppy the Samba & boot servers are running, no need to reboot PupServer.
Then run: xmklanpup, select a Puppy ISO file to use for a client & it's converted to a LanPuppy.
The 3 main files (vmlinuz, image.gz, usr_cram.fs) are put in: /tftpboot/(ISO file name).
To setup the new LanPuppy, copy: vmlinuz & image.gz to: /tftpboot, & usr_cram.fs to: /lanpup/sys
The setup is ready to go, boot a PXE client PC with a PXE BIOS, a PXE NIC, or the PXE floppy.
NOTE: This package is a test release, but will remain available so folks can make their own setups.
After testing & improvement is done I intend to make a ready-to-go PupServer version of Puppy.
And a few ready-to-go client versions, OR just one client version & a HUGE "everything" squash file.
I'm sure there's all kinds of stuff I've forgotten to mention, but it'll all come out in the Qs.
Here's LanPuppy1-01.pup & MakePxeBootFloppy.tar.gz (PXE boot floppy disk).
Lots of folks here have contributed, I wanted to make a list but didn't want to leave anyone out.
The last bit of help was by Ted Dog, who was also one of the first to help when I first came here.
I've kept it simple & as similar to the standard Puppy as I could with only a few changes over all.
The PupServer / LanPuppy package seems to work well, the tools I've made aren't as tested.
I haven't made a manual as such, but raffy suggested that I post it anyway to get it going.
So as bug reports & suggestions for improvements come in, & I answer Qs, I'll compile Docs.
LanPuppy / PupServer setup:
The PupServer is built on EmptyCrust-1.0.7, other Puppy 1 versions would probably work also.
The PupServer is a frugal setup (3 base Puppy files), with Samba server DotPup installed.
The LanPuppy1-01.pup package checks for Samba server install & if networking is setup.
It installs DHCP3, Xinet, Tftp-hpa, & makes dirs.: /docs, /public, /homes, /tftpboot, & /lanpup.
I've been using SimplePup for a client as I like it, most any Puppy 1 versions should work.
I use a frugal install on the H.D., it might work on a full H.D. install, I haven't tried it.
I don't use CDs to run Puppy, but a little modification would allow the setup to work on a CD.
PXE network booting:
PCs with a BIOS PXE network boot option should work for client PCs.
Also PXE ready NICs, on eBay I bought 10: "3com-905c-tx-m" used for $3 each!
Alot of the Intel NICs do PXE boot also, but I haven't used any of them.
I just tested out a EtherBoot PXE Floppy Disk, & it's worked on all the PCs I've got, WOW!
I'm posting this from a 2.4 AMD PC that booted with the floppy from a 1.7 Celeron PC.
Limitations:
The number of clients is controlled by the HOME share dirs., for more clients add more dirs.
The clients run as root user with no login same as Puppy, so there's one setup per client.
This will work well for homes, keosks, churches, small offices, & maybe classrooms.
I'm sure many will want a login with separate users & work spaces for a more robust setup.
When booting, each client briefly uses a common IP add. (x.x.x.9), so stagger booting.
Save & Squash files:
One change is the "save" file is used for settings & app. installs, work space is a share.
The "save" file can be as small as 8 MB, but to install apps. it must be larger.
There's a dir.: /homes/pup-BASE for a base save file, if you want custom settings.
Ideally I'll make an "everything" squash file (any help offers?), so no apps. to install.
All the clients use the same squash file, so there's only one, so it can be HUGE (1 - 2 GB?).
With some modifing,the clients could share the same app. install dir. (/root/.usr)... trick!
Tools:
I've written tools to help administer LanPuppy, but I haven't spent much time testing them.
Better tools are needed, but as LanPuppy changes different tools will be needed.
The main tool is: "xmklanpup", it extracts a Puppy ISO file & modifies it into a LanPuppy.
"xhomesadd" makes client HOME share dirs. & copies a base "save" file, if there's one.
"xmntroot" allows the administrator to mount the clients "save" file to work with it.
"xbootmount" is a PupServer utility to auto. mount H.D.s at bootup.
I want to make a DotPup tool from the package: "MakePxeBootFloppy.tar.gz".
Abilities:
240 clients are allowed (IP add. x.x.x.11 to .250), that can be booted by WakeOnLan.
The usr_devx.sfs developers file & MU's usr_more.sfs MegaPup file work... not tested.
PupServer supplies internet info, so new client's have web access immediately, no setup!
PupServer could boot any PXE ready Linux distro. (Knoppix, DSL) & even Win95 & Win98!
A WinBlows PC can also be a boot server with an app. called tftpd32, but then... WHY?
I'll work with LanPuppy1 for a bit to debug it, then I'll look at using Puppy2 for clients.
PupServer install:
Put EmptyCrust Puppy on a H.D. & setup to boot, install Samba server & LanPuppy.
After installing LanPuppy the Samba & boot servers are running, no need to reboot PupServer.
Then run: xmklanpup, select a Puppy ISO file to use for a client & it's converted to a LanPuppy.
The 3 main files (vmlinuz, image.gz, usr_cram.fs) are put in: /tftpboot/(ISO file name).
To setup the new LanPuppy, copy: vmlinuz & image.gz to: /tftpboot, & usr_cram.fs to: /lanpup/sys
The setup is ready to go, boot a PXE client PC with a PXE BIOS, a PXE NIC, or the PXE floppy.
NOTE: This package is a test release, but will remain available so folks can make their own setups.
After testing & improvement is done I intend to make a ready-to-go PupServer version of Puppy.
And a few ready-to-go client versions, OR just one client version & a HUGE "everything" squash file.
I'm sure there's all kinds of stuff I've forgotten to mention, but it'll all come out in the Qs.
Here's LanPuppy1-01.pup & MakePxeBootFloppy.tar.gz (PXE boot floppy disk).