What is the best Puplet for limited access over a Dial-Up link
PuppyThis forum is for the discussion of Puppy Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
What is the best Puplet for limited access over a Dial-Up link
I'm a Linux newbie, (although I've been using Unix/Linux off and on for several years), but I've just started a new job and I have a requirement to take an embedded PC and collect files from it over a Dial-Up link.
A friend recommended using Puppy because the Embedded PC is using Compact Flash rather than a hard disk, and I certainly like the look of Puppy and it's definitely a good fit for the environment.
My friend also suggested that I establish a TCP/IP link over PPP then use rsync over ssh to periodically collect changes to the files on the remote unit. I'd also want to be able to dial in as a non-root user for obvious security reasons.
This sounds like a very tried and tested set of techniques and applications so I now need help to determine the best choice of Puplet to provide this particular set of functionality !
So does anyone have any suggestions for me please ?
Funnily enough I'd already downloaded the WebServer Puplet because that is pretty much what I'm trying to do, make a lightweight webserver that can accept the Dial-Up connection, (VERY old fashioned I know, but we've got to contend with legacy kit), and collect any new data for centralised storage and later analysis.
Unfortunately my webserver ISO didn't seem to boot properly, unless I completely mis-understood how it should behave, it presented me with an error message :-
"pup_412.sfs not found. Dropping out to initial ramdisk console...",
followed by :-
"/bin/sh: can't access tty; job control turned off".
This was displayed a "#" prompt, at which point I had to concede defeat.
I had expected the grey screen with the Puppy logo in the top right hand corner to appear :-(
I think I'll try and contact the author of WebSrver Puppy and see if he thinks that is what I want.
I can't rule out a bad burn, but I don't think that's the answer.
I AM burning from Windows, because thisa is being done at work and I'm using the company laptop which runs Windows, (surprise, surprise), the Embedded PC that Puppy is intended to run on is sat alongside the laptop, but I'm not allowed to connect it to the company network and therefore it has no Internet connection ;-(
The problem /seems/ to be that the SFS files are suffixed with either 'B' for Browser Puppy or 'W' for Webserver Puppy, (PUP_412W.SFS, as displayed by Windows), but the boot process is looking for "pup_412.sfs", this may be a complete red herring, but to try and find out I've copied the files onto my Windows hard disk, renamed the sfs file and now I've got to remember how to create a bootable CD !! |8-(
I /could/ copy the ISo to a USB stick and transfer it to the Embedded PC which has a USB Burner attached, (for development purposes), and try burning it from there, but I'd have to get my original Puppy working again first !
Once I've established what I actually want to have in my Puppy, I will want to create my own, so I'll need to learn about remastering then, but I think I'd rather wait a while for that, let my head cool down a bit first ;-)
I've never used that particular puplet but if you're getting that kind of error while trying the cd you better check it's thread in murga-linux (down, for maintainance I guess) or if it was properly burnt.
You can also create a Windows installer (.exe file) for any Puppy. It's straightforward and installs a frugal mode Puppy inside Windows (98, 2k and XP). Its original forum thread is here (down at the moment): http://www.murga-linux.com/puppy/viewtopic.php?t=44098
But there's a Portuguese version (read the original files to understand its functioning in pw32-inst/Read me first/OriginalTutorial.html and pw32-inst/Puppy-Win32-Installer/original-pup-installer.readMe ) at http://www.divshare.com/download/7994602-371
Thanks to both Linus72, (Bryan), and Fyujj for your help and comments.
I'm pretty sure that the burns were successful, even though they were done under Windows, simply because all 4 of them, (different versions of browser and webserver puppy), exhibited exactly the same problem and used exactly the same process as my original Puppy Linux 4.2.1 ISO burn which works fine.
I've downloaded the RecoverPuppy ISO mentioned by Linus72 and I will try that out once I get to work tomorrow and burn another CD.
I ought to have said before that this is aimed at a commercial development, but it will be replacing Windows XP Embedded in order to save about 100 GBP per system and it will be first time this company has used Linux, so it's quite important that I get it right !!
What I need at the end of the day is a nice reliable, all solid state, embedded system, installed on a Wafer Atom 5.25 inch embedded motherboard, running a N270 Atom at 1.6 GHz with 1 GB of RAM and either 4 0r 8 GB of Compact Flash, that I can Dial-Up from a centralised PC to collect data for off-line analysis. So any advice on packages like rsync, ssh, PPP servers etc. would be gratefully appreciated.
Ok, sorry for not having said that earlier. I had this problem with browser puppy too when trying to boot from a frugal install (initrd.gz, vmlinuz and pup_xxx.sfs copied to a directory in a linux / partition). The problem is the file was called PUP_412.sfs and I had put pup_412.sfs in GRUB's menu.lst. So it seems the cd booting (I think its syslinux) is having the same problem.
Maybe you could try isobuster http://www.isobuster.com/isobusterdownload.php (you only need the free version) to rename the file, create a new .iso and burn the cd again.
I know it's not your case, but if it's only to try some puppies, if you create a Windows installer you won't have this problem.
In any case, you may install this frugal Slaxer Pup for Windows (uninstallable through 'Add/Remove Programs') and then you'll have the Puppy's tools if you need them (only for Win 98, 2k and XP) http://www.divshare.com/download/7994250-ae1
at the boot prompt when the cd first boots type in
that is suppose to stop the cd from looking for puppy files. if it boots up you can delete the puppy files of the version you don't want, and redo a fugal install with the version of puppy you want to use. I've had problems before with puppy cds starting up when using versions puppy of different from the version already installed.
Last edited by colorpurple21859; 07-27-2009 at 09:19 PM.
Many thanks to Linus72, fyujj and colorpurple21859, but what all I really need is a Puplet that will run on a remote, embedded PC, that I can dial from a standard PC into and access files on the remote Puppy via FTP.
So I've downloaded Webserver Puppy, but I've had some hardware issues with the Embedded PC so I haven't yet had a chance to test it.