(old)Puppy Linux Discussion Forum

Posted: **Thu 18 Feb 2010, 16:55**

Has anyone got

pUPnGO_V412_XVESA_JWM.iso

running as a GUI yet?

I downloaded, installed with puppy pfix=ram, got a cmd prompt okay.
If I type

Xvesa

I get a graphics screen but blank except for the mouse cursor so what else to type to get a gui?
Also doing

Code: Select all

lynx

at cmd line gives me a basic browser but it doesn't seem to be connected to the net as get

unable to connect to remote host.

and

Code: Select all

ifconfig eth0

returns

device not found.

I was hoping this would be a bit easier to start off.

Any help appreciated.

Thanks

Posted: **Thu 18 Feb 2010, 17:01**

dave,

Code: Select all

startx

Posted: **Thu 18 Feb 2010, 17:14**

sinc:
Yes of course. How stupid of me. Thanks my friend.
I'm having one of those days

Now any idea about why I can't get my internet connection.
ifconfig -a only brings up the local loopback.
Tried dhclient eth0.....not found
ifup eth0 ...can't open /etc/network/interfaces

Driver issue..wonder how I fix that?

Cheers

Posted: **Thu 18 Feb 2010, 17:19**

i haven't tried to connect to the internet yet bc I am not near an ethernet cable, I'm almost always wireless. But what might be helpful would be to use the build script instead of the iso and include ttuuxxx's file manager pet. That will help to be able to search files, but be aware that you have to be in 4.12 in order to use the build script.

Posted: **Thu 18 Feb 2010, 18:19**

davesurrey wrote:....at cmd line gives me a basic browser but it doesn't seem to be connected to the net as get
unable to connect to remote host.
and
Code: Select all
ifconfig eth0
returns
device not found.
I was hoping this would be a bit easier to start off.

Hi davesurrey
Are you running in qemu or on a real machine? pUPnGO only provide drivers for vmware and qemu as is...
Try command route at command line...
Kim

Posted: **Thu 18 Feb 2010, 18:26**

Update: New build with latest BusyBox snapshot (v.1.17.0.git). A more intensive use of BusyBox used to reduce size (-700K) and complexity. Build script, BusyBox bin and new grub/bootmanager scripts included on iso.

Overview:
Kernel (original) 1,6Mb
initrd.gz (original) 1,3Mb
pup_412pUPnGO.sfs 2,0Mb (3,7Mb with GUI)
zdrv_412.sfs 700 Kb (Lynx)

Basic still boots (in virtual machine) with 16Mb whereas GUI-version needs approx. 24 MB to get to a GUI...

Posted: **Thu 18 Feb 2010, 19:21**

Kim,
Thanks for your reply.

Are you running in qemu or on a real machine? pUPnGO only provide drivers for vmware and qemu as is...

Running as a frugal install in a real machine. So I guess I need to add the lan driver. Not sure how to do that from cmd line so it'll be a learning experience.

Try command route at command line...

#route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
127.0.0.0 * 255.0.0.0 U 0 0 0 lo

Not sure what that tells me that I didn't know.

Code: Select all

ifconfig -a

told me the loopback is okay and that eth0 isn't working.

Thanks anyway.
Dave

Posted: **Thu 18 Feb 2010, 19:40**

davesurrey
Try to view in a normal p412 which modules are loaded (lsmod) and build them into pUPnGO - then it should work...
kim

Posted: **Thu 18 Feb 2010, 21:05**

Am I right or wrong?

These micro versions of puppy can be used together with all the sfs files that allow it to start up programs without being fat due to only adding one program at a time?

http://www.murga-linux.com/puppy/viewtopic.php?t=52620 and this one

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

SFS's
ch4-AdobeReader-8.0.sfs
ch4-alsa-streamtuner-3.sfs
ch4-fbreader-0.10.7.sfs
ch4-firefox-3.5.3.sfs
ch4-FirePup-0.04.3-ln.sfs
ch4-FoxitReader1.0.sfs
ch4-frostwire-4.17.0-jre.sfs
ch4-geany-0.16.sfs
ch4-gimphoto-1.4.3.sfs
ch4-GoogleEarth-4.3-ln.sfs
ch4-gxine-0.5.9b.sfs
ch4-jre1.6.0_11.sfs
ch4-K-Office-1.6.3.sfs
ch4-Mplayer1rc2.sfs
ch4-mtpaint-3.30.sfs
ch4-mtpaint-3.31.1-i486.sfs
ch4-OpenOffice-3.0-ln.sfs
ch4-OpenOffice-3.1.1.sfs
ch4-Opera10final-4585.sfs
ch4-pwidgets-2.0.8.sfs
ch4-samba-3.0.26.sfs
ch4-seamonkey-1.1.18-full.sfs
ch4-vlc_nogui-0.8.6.sfs
ch4-winelite-1.1.14.sfs
ch4-winelite-1.1.30.sfs
_________________
ChoicePup4.1.2 As You Like It. puppylinux.ca/members/choicepup/ (usr=puppy passwd=linux)

Last edited by jrb on Tue Oct 20, 2009 1:24 am; edited 5 times in total

some posts down in that thread. I guess they are made for Choice pup. How is that one different from the pupngo?

Posted: **Thu 18 Feb 2010, 23:50**

nooby wrote:Am I right or wrong?

some posts down in that thread. I guess they are made for Choice pup. How is that one different from the pupngo?

pUPnGO is for advanced linux users, its the extreme lightweight version, It hardly has enough in it to actually run in gui. Its a building a base tool, Where as Choicepup has a solid base, and works well out of the box, pUPnGO you have to configure things to work etc, but it you have the time you'll learn a lot from using it, but you'll need patience and google

ttuuxxx

Posted: **Fri 19 Feb 2010, 05:40**

Choicepup could be next step learning linux for me then. I tested to start anew with Stardust last night and managed to do both codecs to mplayer and to find and take down Firefox 3.57 so that was an adventure.

Choicepup look interesting if one have not the latest hardware then. only use what you need when you need it. But Stardust works very good on my HP/Compaq 5622 with 2 or 3 GB RAM not sure.

oh, are all puppies adjusted to be used on USB flash? Does all puppie by default write only when one tell them to?

Posted: **Fri 26 Feb 2010, 04:27**

Sounds like a great base for a browser only puplet... something I would like to get back to eventually - probably with Midori. I would try a fully static build but since flash is a necessity I would likely pull in the shared libs that flash 9 depends on and do the rest static. Figuring out required libraries is easy using ldd, but does anyone know how you find the other required files (images, fonts, config files etc..) short of parsing a strace output?

Posted: **Fri 26 Feb 2010, 05:52**

technosaurus wrote:...but does anyone know how you find the other required files (images, fonts, config files etc..) short of parsing a strace output?

Do not know if this is an answer to your question...but pUPnGO build script has some limited ability to include ordinary PET-files in the build. Place them in /data/pets-folder and at least the files will be in the build...

Posted: **Fri 26 Feb 2010, 14:45**

@goingnuts
Although that works it also brings in (sometimes many) unnecessary files.
Actually I was refering to programs that segfault if missing some random file (not a library) that is hardcoded in. This could be a config file or even something as simple as an image file.

When you compile with debugging enabled, programs often output these problems to the command line (which you can log with [program] [-options] 2>programerror.log)... but debugging makes the program significantly larger and would require a full rebuild

Without debugging enabled, you can use strace, but you get too much info:
strace [program] [-options] &>program.log

I seem to recall a program called filewatch or something that would just tell you what files were accessed by a program... so that one could pull in only the files that are absolutely required.

Posted: **Fri 26 Feb 2010, 17:39**

technosaurus wrote:Sounds like a great base for a browser only puplet... something I would like to get back to eventually - probably with Midori. I would try a fully static build but since flash is a necessity I would likely pull in the shared libs that flash 9 depends on and do the rest static. Figuring out required libraries is easy using ldd, but does anyone know how you find the other required files (images, fonts, config files etc..) short of parsing a strace output?

Run 'strings' on the binary?

Lsof can help too.

Posted: **Wed 03 Mar 2010, 19:07**

New build script and builds (build script included in ISO) uploaded. A more user-friendly menu driven build configuration can be used. Also an application menu included.
Basically now ALSA is working (but not in builds), GUI-build with low or full font, use BusyBox intensively or a more safe build. Not quite sure if save to CD works...
Build with Geany, Lynx, Links, Abiword, Gxine, Gparted or Hiawatha+php+mysql-server now available. The applications will run but you might miss some of the features as fine-tuning and size reductions have not been made to its full extent.

Basic build iso (with and with out GUI) is more or less the same as previous build - the main purpose have been to make the build script easier to use - and to give an appetizer of what the pUPnGO-build script can be used for...

The new script fetch PETs from ftp://distro.ibiblio.org/pub/linux/dist ... packages-4 and community PETS.

Examples of builds possible ("QuickPUPs"...?):

Hiawatha based Web server with php+mysql (needs RAM!) (20MB)
A lightweight web-browser with GUI and the Links-browser (13MB)
Plain writer edition, GUI and Abiword. (17MB)
Tiny GUI build with XFE, Links and Gparted (16MB)
Multimedia GUI version with Gxine only. (16MB) NB: remember to include ALSA in the build!

I will not claim the build script to be bug free (its probably not) but I have tested most of the combinations possible. ex. Gxine can play mp3/mpg-files but haven't tested other formats...

Still: To have a proper build you need to install used PETs to the host system - and you need disc-space...(save-file 512->1024 needed)
Have fun...
Kim
Below screen shot of 16MB build with Gparted, Links and XFE-filemanager running in qemu 32MB RAM...

Posted: **Wed 03 Mar 2010, 22:24**

If anyone would like to setup a kiosk using only jwm this link could help for setting a background and application start buttons
http://www.murga-linux.com/puppy/viewtopic.php?t=51200

On recent X to disable ctrl+alt+backspace - edit the xorg.conf template for:
Section “ServerFlags

Posted: **Fri 05 Mar 2010, 17:34**

I am trying to make some hardware dependent build with pUPnGO. This means that using a virtual machine do not work - I have to burn each build to CD and boot on the specific machine the build is for. This is definitely a slow approach as I want to only build in the needed drivers for the specific hardware the target machine have.

One approach is to boot target machine with a full P412 CD, after boot do a lsmod and note what was found. Then afterwards try to figure out where that specific module is in P412 and include it in the build.

A more automatic approach would be nice - maybe do the boot with full P412 - and save the result of lsmod to a file. This file could maybe be used afterwards to pick the modules and put it in the pUPnGO build?

I cannot find a translation between the output of lsmod and the actual place on drive where the module file is - so if someone could give a pointer I would be grateful.

Posted: **Fri 05 Mar 2010, 20:58**

I made a zdrv cutter script a while back - its in cutting edge - latest version 0.0.4 added xorg drivers (not currently on zdrv yet, but I think they should be eventually) so you will probably do best with 0.0.3 for now. Please feel free to make any improvements you need, it is public domain.

http://www.murga-linux.com/puppy/viewtopic.php?t=51450
http://www.murga-linux.com/puppy/viewtopic.php?t=51552

Posted: **Fri 05 Mar 2010, 21:25**

THANKS technosaurus!

Excellent - just what I needed! What a time saver!
First test looks great (reduced my driver "load" to 3MB) and it seems everything is found and included. Just had to comment out the inclusion of "/etc/DISTRO_SPECS" as I have no such file.

If its ok with you I will try to include it as a function in pUPnGO build script?

Kim

(old)Puppy Linux Discussion Forum

pUPnGO - 6Mb ISO - Basic Building Block Puplet

Update...