Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Mon 01 Sep 2014, 22:36
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
How to set up a Puppy Linux Cybercafe
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 5 of 9 [132 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8, 9 Next
Author Message
ecomoney


Joined: 25 Nov 2005
Posts: 2183
Location: Lincolnshire, England

PostPosted: Mon 16 Mar 2009, 20:57    Post subject:  

Im such a newb Wink

The atftpd-swe3-1.0a.tgz is a zipped up file. The install procedure is to transfer it to the /tmp folder on the smoothwall (Smoothwall is basically a security hardened Red Hat install with no xwindows I believe), and uncompress it. One of the files inside the main atftpd-swe3-1.0a.tgz file is one called /tmp/udpcast-files.tgz . This file contains a directory "/home/tftpboot" where Ive put all of the files to make puppy boot. An install script is then run that makes all of the additions to Smoothwall, and finally just "unzips" the udpcast-files.tgz files to make an unconfigured "/root" directory.

Basically to modify the "mod", all I would have to do is to somehow modify the udpcast-files.tgz file to contain all of the files needed to boot puppy linux in their correct places. (pxelinux.o, initrd.gz, vmlinuz, default etc etc)

What I need to know is, how would I make a new gzip archive of /root and its subdirs and insert it in the right place, so that when I installed this mod on a smoothwall box everything would end up in the right places and it would "just work" lol? Ive also managed to make a "tar" archive of the /root folder on the smoothwall from its working configuration, and even managed to "gzip" it, so Ive now got a .tar.gz. Is the the same as a .tgz? With a different name?

Ive managed to get my websites and mirrors backup, so Ive loaded the original mod .tgz here

origional tftp addon for Smoothwall 3.0

Compressed .tar.gz of /root directory with puppy files inside from working system

Basically, if I can get these merged, then I will have modified the origional MOD to boot puppy. There doesnt seem to be anyone answering on the Smoothwall forums, or I would ask them....its a pretty basic command line zip problem common to all linux I have anyway.

Would really appreciate some help with this......Its going to have to be part of the instructions in any case.

Cheers

_________________
Puppy Linux's Mission

Sorry, my server is down atm!
Back to top
View user's profile Send private message Visit poster's website MSN Messenger 
ecomoney


Joined: 25 Nov 2005
Posts: 2183
Location: Lincolnshire, England

PostPosted: Tue 17 Mar 2009, 14:40    Post subject:  

Just an update, Ive had a pm back via the smoothwall forum from Nanouk, the author of the smoothwall tftp mod, offering to package the cutdown 3.1.2 files along with the mod, and provide me with instructions on how to go about repackaging the mod for future releases of puppy.

I have tried today to repackage a "humungous initrd" with the latest 4.2 RC3 files....and failed! Im going to do a bit more research into this, and hopefully produce a setup that will netboot the latest puppy.

When nanouk gets back to me I will post a link to it here, and provide hosting on our public software mirror.

What would be really handy is a script that will automatically remaster a pup420.sfs, pup_save.2fs, and an initrd.gz file into a new "humongous initrd.gz" file. It would then just be a case of ssh'ing the new file over to the smoothwall box in Immingham and Hull. Once I have the commands down I will try and write one.

_________________
Puppy Linux's Mission

Sorry, my server is down atm!
Back to top
View user's profile Send private message Visit poster's website MSN Messenger 
Aitch


Joined: 04 Apr 2007
Posts: 6825
Location: Chatham, Kent, UK

PostPosted: Tue 17 Mar 2009, 15:42    Post subject:  

Rob

Another use for what you are doing maybe to provide Netbootability for the few folks who have hardware with an existing OS with a network connection, but no working CD or Floppy to boot from, or a bios that's locked & won't allow booting from existing hardware?
[It may need a floppy to get started in some circumstances, as I've seen this done with debian at some of our LUG's installfests
http://linux-boot.net/Boot/FD/]

This could be included on the download pages
& that could have far wider appeal & PRnewsworthiness, IMHO

Maybe, other useful links

http://www.linuxhq.com/ldp/howto/Bootdisk-HOWTO/index.html

http://www.linuxhq.com/ldp/howto/Network-boot-HOWTO/index.html

http://www.linuxhq.com/ldp/howto/Clone-HOWTO/index.html

Aitch Smile
Back to top
View user's profile Send private message 
ecomoney


Joined: 25 Nov 2005
Posts: 2183
Location: Lincolnshire, England

PostPosted: Tue 17 Mar 2009, 23:25    Post subject:  

Yes, it would probably be wise for me to prepare some netboot floppy or cd images for my next visit, just in case. All of the computers there look fairly modern (under four years old) but if there is something Ive learnt about this industry its never assume anything!

Im going to have a go now at making a new humongous initrd.gz for puppy 4.2. See you in a few weeks Cool

_________________
Puppy Linux's Mission

Sorry, my server is down atm!
Back to top
View user's profile Send private message Visit poster's website MSN Messenger 
MagicZaurus

Joined: 05 Jan 2009
Posts: 88

PostPosted: Tue 17 Mar 2009, 23:36    Post subject:  

Hi ecomoney!

Once 4.2 is released and WhoDo provides the Unleashed tree it should be a matter of a few hours to built the humongous initrd.gz from Puppy Unleashed.

So far I didn't try the other methods, but building it with the script provided in Unleashed is pretty easy.

Your tftpboot folder should only need 4 files from my experience.

pxelinux.0 (PXE-Bootloader)
default (PXE-Bootloader config file)
vmlinuz
initrd.gz

Have fun with exploring neetbooting. I only booted 3 different machines so far and no major problems. You have the chance to try more hardware variations at the cybercafes.
Back to top
View user's profile Send private message 
ecomoney


Joined: 25 Nov 2005
Posts: 2183
Location: Lincolnshire, England

PostPosted: Wed 18 Mar 2009, 00:27    Post subject:  

Ok, the story so far, I have managed to get the 55mb minimal install netboot 4.12 install to netboot from the smoothwall server...the next step, figure out how to make a netbooting 4.20!

I took the initrd.gz and pup_420.sfs from the puppy 4.2 rc3 iso. The idea was to combine them to make a new "humungous initrd.gz" to put into the root/tftpboot folder of the smoothwall, replacing the initrd.gz file that is there which boots the cutdown 4.1.2.

The initrd.gz for 4 series puppys appears to contain just one file when un-gzipped (gunzip?) or opened with pupzip (i.e. clicked on), its actually compressed with a thing called cpio to squeeze a few more megs of compression.

I made a mnt/home/hinit folder and placed the initrd.gz and pup_420.sfs files from the 4.2 iso in it, and then made a new subdirectory called "/mnt/home/hinit/tmp" and changed directory to it

Code:
mkdir ./tmp
cd tmp


The next step was to extract the initrd.gz file from the folder below into the current folder (i.e. from /mnt/home/hinit/initrd.gz)

Code:
zcat ../initrd.gz | cpio -idv


After chugging for a bit, a familiar linux directory tree appeared in /mnt/home/hinit/tmp. The next step was for me to copy the pup_420.sfs file from the directory below (i.e. /mnt/home/hinit) into the uncompressed directory tree.

Code:
cp ../pup_420.sfs ./


Then to remove the origional initrd.gz in /mnt/home/hinit

Code:
rm ../initrd.gz


and to zip up the contents of the current folder (/mnt/home/hinit/tmp) into a new "humungous initrd.gz"

Code:
find . | cpio -o -H newc | gzip -9 > ../initrd.gz


after much thrashing around of the hard disk and a spike in processor usage, I found a new /mnt/home/hinit/initrd.gz file, of around 98mb....so I copied it over the top of the working initrd.gz (about 55mb) on the smoothwall

Code:
cd ../
scp -pvC -P 222 ./initrd.gz root@smoothwall:/home/tftpboot/initrd.gz


Marveling at my newfound ability to enter completely unintelligible code on the command line, I rebooted the laptop, which was set to "netboot" in the bios

Code:
could not find ramdisk image: initrd.gz


WHY!!! the initrd.gz file was in exactly the same place as the one that worked, with exactly the same name....how come it wasnt found?

Im at a loss, and I know soon I will be called over to demonstrate my work so far. The cutdown 4.1.2 is fine, but it doesnt actually contain any applications and will do little to run a cybercafe. I need 4.2 (with PWidgets!) if Im going to keep this contract.

Can anyone shed any light?

_________________
Puppy Linux's Mission

Sorry, my server is down atm!

Last edited by ecomoney on Tue 05 Jan 2010, 01:16; edited 2 times in total
Back to top
View user's profile Send private message Visit poster's website MSN Messenger 
MagicZaurus

Joined: 05 Jan 2009
Posts: 88

PostPosted: Wed 18 Mar 2009, 00:50    Post subject:  

Hi!

Here you also can find the full version 4.1.2 initrd.gz and vmlinuz.

ftp://puppy@ftp.servage.net/humongous412/

Maybe you can buy WhoDo a beer and ask him to build the humongous initrd.gz from 4.2 RC3 for you. If he thinks your project is important for Puppy promotion he might spent a few of his PCs CPU cycles for it.

Don't be frustrated. Breaking new grounds is always not an easy thing.

What about access permission for your new initrd.gz on the SmoothWall? Readable for everyone?

Cheers!
Back to top
View user's profile Send private message 
ecomoney


Joined: 25 Nov 2005
Posts: 2183
Location: Lincolnshire, England

PostPosted: Wed 18 Mar 2009, 01:35    Post subject:  

Hi MZ, thanks for getting back to me so quickly. Im sure WhoDo has quite enough on his plate to be spending time packaging netboot files.

. I did check the permissions while the two different initrd.gz files were still on puppy, and they had both had three ticks next to the "world" access. I tried a "ls -l >> dir.txt", transferred it back up to the laptop, then onto my internet connected computer via a pendrive (I know...not a good setup to work from) and got this

Code:
total 101629
-rw-r--r-- 1 root   root           0 Mar 18 08:18 dir.txt
-rw-r--r-- 1 root   root   102013039 Mar 17 19:33 initrd.gz
-rw-r--r-- 1 root   root       13156 Apr  8  2009 pxelinux.0
drwxr-xr-x 2 nobody nobody      1024 Mar 17 22:05 pxelinux.cfg/
-rw-r--r-- 1 root   root     1627180 Apr  9  2009 vmlinuz


I dont know a lot about file permissions (I dont have to, I use puppy!) but from deciphering this and comparing it, the initrd.gz seems to have precisely the same file permissions as when it was on the puppy machine, and the same as the other files which can be read at netboot...I dont think its a permissions problem.

Speaking of permissions, I would have liked to have tried the full 4.1.2 file you posted a link too, but I get asked for a password...none of the usual seem to work. Perhaps you would pm? If I can get hold of the file I will send a link over to Pascal who is packaging a new smoothwall mod, so he can produce a full and a cutdown version of the Smoothwall Puppy Boot mod. This would be an excellent spinoff project from the whole excercise.

_________________
Puppy Linux's Mission

Sorry, my server is down atm!

Last edited by ecomoney on Wed 18 Mar 2009, 01:48; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website MSN Messenger 
raffy

Joined: 25 May 2005
Posts: 4765
Location: Manila

PostPosted: Wed 18 Mar 2009, 01:40    Post subject: ramdisk_size  

Ah, I thought I saw somewhere that ownership of TFTP files in Smoothwall has to be by nobody? I guess you posted it early on - do this in terminal opened inside the folder you were using above:
Code:
chown -R nobody:nobody *

(The -R is supposed to affect files inside lower-level folders like pxelinux.cfg.)

Also, in /pxelinux.cfg/default, ramdisk_size should be sufficient to hold your new initrd.gz. The arithmetic of this is to divide the bytes with 1,024 to come up with KB of memory. Or, to make it fool-proof, copy the KB numbers of initrd.gz that you see in Rox (File Manager).

Using information from the file window you just posted, the number can be anywhere from 99700 to 102000 (all such possibilities should work).

EDIT: You have funny dates there in your files: April 9, 2009???

_________________
Puppy user since Oct 2004. Want FreeOffice? Get the sfs (English only).
Back to top
View user's profile Send private message 
MagicZaurus

Joined: 05 Jan 2009
Posts: 88

PostPosted: Wed 18 Mar 2009, 02:32    Post subject:  

Sorry! When I copy&paste the link, the password was lost.

ftp://puppy:puppylinux@ftp.servage.net/humongous412/

I think it's a kind of public. Raffy provided me with the location to upload the files last time.

Indeed permissions seem to be ok.
Back to top
View user's profile Send private message 
ecomoney


Joined: 25 Nov 2005
Posts: 2183
Location: Lincolnshire, England

PostPosted: Wed 18 Mar 2009, 03:40    Post subject:  

Hi Raffy, I did as you suggested with the chown command, all of the files in the folder are no owned by nobody, but I was still getting the same message from the boot prompt on the client computer.

smoothwall has the "joe" text editor, using that I opened the /home/tftpboot/tftpboot.cfg/default file and changed it to read
Code:

DEFAULT Puppy
PROMPT 0
NOESCAPE 0
ALLOWOPTIONS 0
TIMEOUT 100

MENU TITLE Puppy Network Booting!

# Puppy Linux Loader
LABEL Puppy
MENU Puppy Net-Booting
KERNEL vmlinuz
APPEND initrd=initrd.gz ramdisk_size=[b]102013040[/b]

EOF


this was one number bigger than the file size reported in the directory isting above...still no joy. Then I looked at your instructions and saw the nuber you had suggested was much smaller...I think I got my bytes and my megabytes mixed up. Embarassed

I edited the /home/tftpboot/pxelinux.cfg/default file again, and changed it to 102000, the larger of the range you suggested, but still no luck.

Ive found the problem with the dates, the bios date on the machine I compiled the files with was incorrect, I have corrected this now. Will this make any difference?

Im have just finished downloading the file you sent MZ, thank you for that. If the netboot then works with the file you sent me (which I assume has been tested before), I think I can summize that it must be in my packaging of the new 4.2 initrd.gz that the error has crept in, and the message about the initrd.gz file not being found is somehow erronious.

Good news is, I have finally (after about four years of trying) managed to get internet connection sharing to work. In the room where my workshop is, I dont have internet connectivity via an ethernet cable, and smoothwalls dont do wireless! I should be able to use another old laptop I have in for repair to "collect" a net connection, input it into the smoothwall, then out of the smoothwall into my test machine..perhaps via a router? I have a spare router but it has a dhcp server in it too...perhaps I can turn this off? This will finally give me something approximating the actual setup of the cybercafe.

Many thanks again for your quick responses.

P.S. I have uploaded my "failed" 4.2 humongous initrd.gz (the one giving these messages when I use it to replace the previous cutdown one which works) to my webserver here. Would it be easy for someone knowledgeable to do a "post-mortem" and see why it doesnt work?

http://ecomoney.eu/smoothwall/puppytftp/fails/initrd.gz

[/code]

_________________
Puppy Linux's Mission

Sorry, my server is down atm!
Back to top
View user's profile Send private message Visit poster's website MSN Messenger 
ecomoney


Joined: 25 Nov 2005
Posts: 2183
Location: Lincolnshire, England

PostPosted: Wed 18 Mar 2009, 04:24    Post subject:  

Right, I transferred the latest initrd.gz that you sent the link to MZ to the smoothwall, and I even did a directory listing to make sure that it had transferred.

Code:
total 94586
-rw-r--r-- 1 nobody nobody      314 Mar 18 08:18 dir.txt
-rw-r--r-- 1 root   root          0 Mar 18 10:45 dir2.txt
-rw-r--r-- 1 nobody nobody [b]94829431[/b] Mar 17 23:02 initrd.gz
-rw-r--r-- 1 nobody nobody    13156 Apr  8  2009 pxelinux.0
drwxr-xr-x 2 nobody nobody     1024 Mar 18 10:39 pxelinux.cfg/
-rw-r--r-- 1 nobody nobody  1627180 Apr  9  2009 vmlinuz


You can see from the filesize that I have *tried to* highlight in bold above that the correct file was transferred.....still the same error message!!!!

cannot find initrd.gz

So just as a double check, I retransferred the smaller (58mb) cutdown 4.1.2 version back to the /home/tftpboot folder, and tried it again, and it worked!!!! Evil or Very Mad Confused

So....

Out of the three humungous initrd.gz files I tried only the smallest one was "found"vand worked, despite them all being called the same thing and being in the same place.

This jogged my memory of something I skim read about size limits of 100mb or similar...just I cannot remember where..

Im going to need to do some more research. MZ, can you confirm that you have booted from the file you just sent e before, and from what platform? It may be that the tftp server in smoothwall has some kind of size restriction.

Many thanks for your continued help...I must be off to sleep at some time.

_________________
Puppy Linux's Mission

Sorry, my server is down atm!
Back to top
View user's profile Send private message Visit poster's website MSN Messenger 
ecomoney


Joined: 25 Nov 2005
Posts: 2183
Location: Lincolnshire, England

PostPosted: Wed 18 Mar 2009, 05:13    Post subject:  

Aha! have tracked down something, I looked in /var/log on the smoothwall and found a file "atftpd.log", this was 130k big text file, so I knew it must contain the results of all my long trials and tribulations. I looked inside. Remember from above, the last thing I did was to retry the smaller initrd.gz from the cutdown 4.1.2. Heres the last section.

Code:
Mar 18 11:41:45 seafarers atftpd[2460.16384]: Advanced Trivial FTP server started (0.7)
Mar 18 11:41:45 seafarers atftpd[2461.16384]: pid file already exist, overwriting
Mar 18 11:41:57 seafarers atftpd[2461.16384]: SIGTERM received, stopping threads and exiting.
Mar 18 11:41:57 seafarers atftpd[2461.16384]: atftpd terminating
Mar 18 11:41:57 seafarers atftpd[2461.16384]: unlink: Permission denied
Mar 18 11:41:57 seafarers atftpd[2461.16384]: Main thread exiting
Mar 18 11:41:57 seafarers atftpd[2492.16384]: Advanced Trivial FTP server started (0.7)
Mar 18 11:41:57 seafarers atftpd[2493.16384]: pid file already exist, overwriting
Mar 18 11:44:21 seafarers atftpd[2523.16386]: Serving /pxelinux.0 to 192.168.0.248:2070
Mar 18 11:44:21 seafarers atftpd[2524.32770]: Serving /pxelinux.0 to 192.168.0.248:2071
Mar 18 11:44:21 seafarers atftpd[2525.49154]: Serving /pxelinux.cfg/01-00-08-02-15-d2-df to 192.168.0.248:57089
Mar 18 11:44:21 seafarers atftpd[2526.65538]: Serving /pxelinux.cfg/C0A800F8 to 192.168.0.248:57090
Mar 18 11:44:21 seafarers atftpd[2527.81922]: Serving /pxelinux.cfg/C0A800F to 192.168.0.248:57091
Mar 18 11:44:21 seafarers atftpd[2528.98306]: Serving /pxelinux.cfg/C0A800 to 192.168.0.248:57092
Mar 18 11:44:21 seafarers atftpd[2529.114690]: Serving /pxelinux.cfg/C0A80 to 192.168.0.248:57093
Mar 18 11:44:21 seafarers atftpd[2530.131074]: Serving /pxelinux.cfg/C0A8 to 192.168.0.248:57094
Mar 18 11:44:21 seafarers atftpd[2531.147458]: Serving /pxelinux.cfg/C0A to 192.168.0.248:57095
Mar 18 11:44:21 seafarers atftpd[2532.163842]: Serving /pxelinux.cfg/C0 to 192.168.0.248:57096
Mar 18 11:44:21 seafarers atftpd[2533.180226]: Serving /pxelinux.cfg/C to 192.168.0.248:57097
Mar 18 11:44:21 seafarers atftpd[2534.196610]: Serving /pxelinux.cfg/default to 192.168.0.248:57098
Mar 18 11:44:21 seafarers atftpd[2535.212994]: Serving /vmlinuz to 192.168.0.248:57099
Mar 18 11:44:22 seafarers atftpd[2536.229378]: Serving /initrd.gz to 192.168.0.248:57100
Mar 18 11:44:22 seafarers atftpd[2536.229378]: Requested file to big, increase BLKSIZE
Mar 18 11:44:26 seafarers atftpd[2537.245762]: Serving /vmlinuz to 192.168.0.248:57101
Mar 18 11:44:27 seafarers atftpd[2538.262146]: Serving /initrd.gz to 192.168.0.248:57102
Mar 18 11:44:27 seafarers atftpd[2538.262146]: Requested file to big, increase BLKSIZE
Mar 18 11:44:28 seafarers atftpd[2539.278530]: Serving /vmlinuz to 192.168.0.248:57103
Mar 18 11:44:29 seafarers atftpd[2540.294914]: Serving /initrd.gz to 192.168.0.248:57104
Mar 18 11:44:29 seafarers atftpd[2540.294914]: Requested file to big, increase BLKSIZE


Here is the difference between it working with the smaller file, and not working with the larger. Apparently its down to "BLKSIZE".

Off for some more research to find out how to increase it...whatever it is Rolling Eyes

_________________
Puppy Linux's Mission

Sorry, my server is down atm!
Back to top
View user's profile Send private message Visit poster's website MSN Messenger 
Aitch


Joined: 04 Apr 2007
Posts: 6825
Location: Chatham, Kent, UK

PostPosted: Wed 18 Mar 2009, 05:18    Post subject:  

Rob, continuing good luck with your project

Your "I tried to highlight comment"

I don't think you can embolden inside a code box

However it DOES highlight it


also RE: wifi from the smoothwall;

It looks possible to add a wrt54 in reverse mode [at least I think they have a wifi version] - see Dennis's comment

http://murga-linux.com/puppy/viewtopic.php?t=39667

However, I wouldn't be surprised if someone like tempestuous didn't know a way to add some code to the smoothwall to add wifi to it, maybe....

Aitch Smile
Back to top
View user's profile Send private message 
MagicZaurus

Joined: 05 Jan 2009
Posts: 88

PostPosted: Wed 18 Mar 2009, 07:53    Post subject:  

Quote:
pascal what do you know about blksize in relation to this mod, it is limiting transfer's over pxe to a max size of 90Mb's!

anything that can be done here?
i have emailed the author of atftpd but am still awaiting reply

i need to increase this to serve a live image of winxp live which i would like to be 200 - 300mb ideally. my current image of 90mb is really to small i need to make the ramdrive bigger !


This is from the Smoothwall forum. So there is a limit of 90MB for the initrd.gz on Smoothwall. So this might be the root cause of your problem.

I used Puppy as my TFTP server and was able to boot that initrd.gz which you downloaded. So if that limit on Smoothwall cannot be changed, then you need to make a smaller Puppy initrd.gz by leaving some unnecessary packages out.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 5 of 9 [132 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8, 9 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

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


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1499s ][ Queries: 12 (0.0274s) ][ GZIP on ]