The web page about Knoppix looks interesting, it looked like a really modified setup.

So Puppy-2.x.x versions will work good for PupServers? Great!

Your error sounds exactly like the one I'm getting on the new build of it.
The file: /var/log/messages said that libwrap had refused connection from the client.
I haven't figured out just what the difference was between the old & new versions.
HOW DID YOU FIX YOUR PROBLEM?

The sound from YouTube shouldn't be messed up, I've played movies over the LAN.
But YouTube connects to the web, so maybe that's the problem.
Try putting one of the YouTube songs into the PupServer's /docs share dir. & play it (if you can).
Or try playing some Mp3s in the /docs share, that's where I had the media files.

Booting over a WAN should be possable but slow, & if there were lots of clients...

The option hosts allow specifies which hosts are permitted to access a Samba service. By default, we allow hosts from IP class C 192.168.1.4 and our localhost 127.0.0.1 to access the Samba server. Note that the localhost must always be set or you will receive some error messages. '

I loaded Simplepup0.3.1 on a 1 GB USB flash drive and so far I couldnt boot it.I've tried puppy211 and it loaded just fine but I run out of memory (I got 128MB RAM on a thin client).On a previous post u asked how to control the loading of squash files and "save files".Did anybody answer that?
Should I create a swap file on the USB on a different partition?
Or maybe I should try a different version of puppy which runs good of an USB?

gabev: I had the same problem, Dougal & I discussed it in another post.
I had to solve my problem by modifing the boot code (not easy to do).
Puppy2 ONLY has the boot control argument of: PMEDIA=usbflash
Puppy211 should work in 128mb of memory I think... (I don't use any Puppy2.x.x).

ATTENTION: You DO NOT want to use ANY Flash device for a swap partition or file!
The CPU constantly writes to the swap partition/file & will WEAR the USB OUT!

There's an app. that's a network protocol for swapping over the network.
When I finish LanPuppy I'll look into it more.
For the moment LanPuppy's need 64mb to 128mb of memory.

I did finally installed the DSL linux on the usb stick and I'm pleased by the performance , faster than all 2.x.x versions of puppy that i've tried so far.But I still wanna try a puppy version which is built around 2.4.x kernel.
Anyway on the same thin client machine (128MB RAM) when I boot using LanPuppy everything runs really fast.

The client gets its IP add. & then fails trying to tftp vmlinuz & image.gz
xinet.conf is exactly the same file I used for the first LanPuppy.
So I know it's a good file & further more nothing in it needs to be changed.
Yet my messages file reports that libwrap(xinet) refused the client's connection.

At least LanPuppy's Users & Hosts admin. dialogs are done & look to be working.
I think it'll work, if I can just get it to boot...
Then desktop setup, testing, & then remaster both PupServer & LanPuppy.

I'll do tommorrow a diging into my error files to see if I had previously the same problems.I remmember I turned off the allow hosts rules in samba cfg and my thin client was able to boot from the pupserver.
I will post the environment plus the errors on different configurations maybe you can compare with yours errors.

Success! I thought about what you said & realized Xinet uses /etc/hosts.allow & hosts.deny.
In the new server build I didn't sync those files, now it goes straight through!
Then I got a wonderful string of errors that I'm now working on...
But at least now development can continue as before.

Like you had all kinda errors and after I remove those 2 lines I was able to connect .I know is a security risk to run it like that , but I did it just for testing pleasure, to see how it runs .

Since then I was trying to start simplePup from a USB stick but with no luck and jump to DSL which I preffer because has an excellent autoconfiguration script .Now I'm trying to make mydsl as small as possible , but didnt start yet .

LanPuppy is an excellent aplication which can be used in a office environment very well. Beats Windows by miles.

I saw your post regarding the integration of LanPuppy with 109CE .Especially regarding networking & wireless auto config. at first boot.This is a feature of DSL for which I left Puppy linux in the background.but with dsl I have another problem, it doesnt have a latest Sylpheed version nor Claws mail and when I tried to compile it I run into dependencies problems ...Puppy linux is really very fast ,especially the ones which are built on 2.4.x kernel.The main functions I need are the autoconfig for the network (like dsl) and an email client which can autoexecute a command when new email arrives ( like Sylpheed 2.X.X or Claws-mail).So far didnt have any luck.....

Yep, Knoppix has the best hardware detection & setup thanks to Klaus Knopper.
DSL was the first small distro. I tried, but it lacked so very much that I abandon it.
Hummm... How about a Debian based distro. with SquashFS instead of CloopFS?
Then most of the Knoppix auto. boot scripts would work for it!

Auto. NIC & networking setup is easy enough, I don't know why Puppy doesn't do it.
Puppy-2 has problems with having to setup WIFI on every boot... it seems.
I would think auto. WIFI setup wouldn't be much of a problem either.
All you do is click a button or two to do it, auto. setup should be easy.

There doesn't seem to be hardly any interest at all in Puppy 110.
So I'm guessing that Puppy-1 will be all but dead by the start of 2007.
It's a shame because of all the work that's been done in it's behalf.
Lots of folks effort & many many packages that will go into the trash bin.

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