Put this in reach of a type 2 hdd install (I have put them on CD-R; so /mnt/cdrom/<tgzfile> for this howto)

boot Puppy Linux from hdd install. Open a terminal (rxvt). You should be in /root.

Save /etc because slackware files will destroy this?! I have not investigated this any further!
So here I will just repair it afterwards...

tar czvf etc.tgz /etc/*

Now install the 3 tgz files from above:
# change working dir to / ; must be in / !!
cd /
tar zxvf <tgzfile>
# important to run the slackware doinst script!
sh install/doinst.sh
# do this for all 3 tgz file
# now restore destroyed /etc files
tar zxvf /root/etc.tgz

--- DONE ---

This is enough to compile simple C apps. One would like to also install make; g++ etc. from slackware the same way...
Then probably X11 libs, GTK libs etc.

Here is a hardcopy: [img]http://www.geocities.com/petersieg/gcc50m102.jpg
[/img]
Attached is a c.zip file containing some simple c apps and splot, a tiny c+tcl/tk app. that is using tcl/tk as the frontend (by Matt Welsch).

- then I thought
You are too young and inexperienced in the ways of the Puppy 'Force'
(I wanted a print out ) but could not . . .

So what I am gonna do, as a half way house, is fire up the olde
Vector Linux 5.00 beta and try some compiling in there
Then If I am able, will try out your stuff - I did have a look at tinycc
('av a look at the How to section)
which is VERY cool and easy - but I can not find sufficient info on
C programming with it
and C is pretty hard for me - "ellow Whirled" is about my limit . . .

bash scripts often will not work quite right with the busybox replacements for the gnu utils

i symlinked /bin/sh to bash so bash runs whether it's called by /bin/bash or /bin/sh

i set SHELL=/bin/bash so it is the default shell that rxvt uses

i symlinked /bin/ash to busybox so i still have busybox's ash if i want it (i mostly use it to see if a script will work in ash as well as bash)

bash could be put in /usr (or could even be on the hard drive) ... if you symlink /bin/sh to a drive that will be unmounted when Puppy shuts down, /bin/sh needs to be symlinked to busybox before the drive is unmounted

I managed to get Puppy on the HD (previously holding Vector 4.6) using the John Murga Opera Puplet (by using a selection 2 boot - no reading or saving from HD) Thus it was easy to do a Number 2 Install and Grub install (I found installing to hda1 rather than MBR worked OK)

bash scripts often will not work quite right with the busybox replacements for the gnu utils

i symlinked /bin/sh to bash so bash runs whether it's called by /bin/bash or /bin/sh

i set SHELL=/bin/bash so it is the default shell that rxvt uses

i symlinked /bin/ash to busybox so i still have busybox's ash if i want it (i mostly use it to see if a script will work in ash as well as bash)

bash could be put in /usr (or could even be on the hard drive) ... if you symlink /bin/sh to a drive that will be unmounted when Puppy shuts down, /bin/sh needs to be symlinked to busybox before the drive is unmounted

bash scripts often will not work quite right with the busybox replacements for the gnu utils

i symlinked /bin/sh to bash so bash runs whether it's called by /bin/bash or /bin/sh

i set SHELL=/bin/bash so it is the default shell that rxvt uses

i symlinked /bin/ash to busybox so i still have busybox's ash if i want it (i mostly use it to see if a script will work in ash as well as bash)

bash could be put in /usr (or could even be on the hard drive) ... if you symlink /bin/sh to a drive that will be unmounted when Puppy shuts down, /bin/sh needs to be symlinked to busybox before the drive is unmounted

The way I have my "1.0.3beta" setup right now is bash is in /usr/bin so as not to add to the size of the initial ramdisk, and /bin/bash is a link to it.
The initial ramdisk has /bin/sh pointing to busybox.

I have had problems with the busybox versions of mkdir, cp and mv -- well, Puppy already has cp-FULL, but now cp is the full version, also mkdir and mv are full versions.

probably ultimately should look at compiling busybox without ash, just have bash.
And, what you suggest about SHELL, yes, in /etc/profile i guess, would be good.

i have /bin/ash symlinked to busybox, but the only time i use ash is to see if a script i wrote will also run in ash

if you put SHELL=/bin/bash in /etc/profile, then rxvt and aterm will use bash

if you have bash in /usr/bin (that's the way i did it, for the same reason, to not make image.gz bigger ... except i have bash in /root now) ... you can symlink bash to /bin/sh, and bash will completely replace busybox's sh (scripts starting #!/bin/sh will use bash instead of busybox) ... i've been running Puppy like that for a long time, and have not had problems with it

what i do is basically this:

i have a script (/usr/bin/bash-on) to enable bash (note that it executes /usr/bin/bash not /bin/sh):

#!/usr/bin/bash
ln -sf /bin/sh /bin/busybox
# fix /bin/bash if rc.reboot is likely to run a script that runs /bin/bash

bash-on would probably execute from rc.sysinit or maybe rc.local0 and bash-off would execute from rc.reboot (you need this or you lose the shell when /usr unmounts ... if you copy bash to /bin/bash then bash-off isn't needed ... i don't know whether this really uses more ram or not, with the way the kernel caches stuff)

when bash is symlinked to /bin/sh, a script that runs /bin/sh will really be running bash ... but bash will behave as though it was sh ... so it will use /etc/profile like sh would ... it will not use .bashrc ... you might find that if you kill X and restart X, that the environment variables in /etc/profile have been lost ... it might be necessary to source /etc/profile in $HOME/.bash_profile

anyway, the way i did it was to completely replace busybox with bash ... and Puppy seems to run with little or no problems that way

Now that I'm using 1.0.2 (off CD) and I have it set up to use tinycc, I could tar up my /root/.usr directory so that you could easilly have tcc for your computer.
If I bz2 it the file is about 2.2MB. There are lots of C header files in it. Installing would be as easy as downloading and untaring once.

`What the MasterPups are up to is all very well (I am just jealous - 'coz I can't do it) but a tcc with a Gui interface IDE type environment would be one of the (yet more things) that makes puppy unique

. . . now all I have to do is learn C
gosh you sure have to be smart to be penguinated

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