First you'll need to mount the floppy disk, i think by default the mount point in redhat is /mnt/floppy
So insert the disk, open up a terminal and type "mount /mnt/floppy"
after that cd into the /mnt/floppy directory
then you can do
rpm -ivh blahblah.rpm
to install rpms
'i' tells the rpm command that you want to install a RPM
'v' is for verbose, which basically means it'll give you more information when something happens
'h' is for the hash, you get see a nice little progress bar for the installation
note that you need to do the above as root, so make sure you 'su' beforehand
After the roaring penguin packages are installed invoke "/usr/sbin/adsl-setup"
or "/usr/bin/tkpppoe" if you've installed the GUI package. To be honest with you I havent used rp before so can't help you at this point, but if you're having problems try reading this page:
The .tar.gz or .tar.bz2 files you download from the net are usually source code files, which means you'll need a C compiler in order to build them, I believe majority of people use GCC (GNU C Compiler). It should be available in your redhat CD, under development tools if you use the add/remove software applet.
In most case in order to install software from the source you first extract it with tar command, for .tar.gz use:
tar xvzf file.tar.gz
for tar.bz2 use:
tar xvjf file.tar.bz2
Then it should create a directory, not always but usually same as the filename, with the files inside.
I'm not exactly sure why there are 2 compression methods around and both of them still commonly used, but I tend to think that gzip has faster preformance while bzip2 has better compression rate, though with the power of modern machines you won't see much difference in speed in most cases. The reason why tar is also required is that bzip2 or gzip, unlike winzip/pkzip, is not capable of compressing multi files and put them in one big .zip file. Tar basically glues the files together and put them in one single .tar file, bzip2 of gzip can then do their job and compress the .tar file.
Then in order to compile the software you first cd into the directory, in most cases you then do:
Which sets up parameters(like where the program will be installed, which features to enable etc), checks dependencies, occasionaly does some fancy tricks depending on the software(lol) and generates the Makefile, I usually do a ./configure --help first to see which features can be enabled/disabled etc. If there isn't a configure script read the documentation, usually it will contain instructions on how to compile the software.
then after ./configure completes, type:
Which does the actual compiling.
Which will copy the compiled binaries to where they should be installed. Usually you can do "make uninstall" to uninstall the software but this is not always the case, it is dependant on the author, as a rule of thumb always read the documentation first when you're unsure of something.