🚀 go-pugleaf

Bovineck@heaven.chess.com (Mikhail Bovineck) wrote:

>
>Well I am nearly there!  I have actually started the installation
>twice now - once I ran out of hardrive space (oops) and the other time
>there was a receive timout error on plip.  The problem is netmask I
>think.  

[snip]

You got me interested in this, so I read the PLIP howto
(/usr/doc/unmaintained/mini/PLIP), and setup PLIP.

(edited) transcript goes something like:

Main# find /usr/doc | grep plip
Main# less /usr/doc/unmaintained/mini/PLIP
Main# ifconfig plip1 192.168.2.1 pointopoint 192.168.2.2 up
Main# route add 192.168.2.2
Main# lynx /mnt/cdrom/doc/rhmanual/manual/index.htm

This is where I decide to use NFS instead of FTP 'cos it needs only the
boot disk.

Main# rpm -qa | grep nfs

I see I only have the NFS clients installed.

Main# ls /mnt/cdrom/RedHat/RPMS/nfs*
Main# rpm -i /mnt/cdrom/RedHat/RPMS/nfs-server-2.2beta29-5.i386.rpm 

Dependancy failure, needs portmapper.

Main# rpm -i /mnt/cdrom/RedHat/RPMS/portmap-4.0-11.i386.rpm 
Main# rpm -i /mnt/cdrom/RedHat/RPMS/nfs-server-2.2beta29-5.i386.rpm 
Main# cd /usr/doc
Main# ls -l nfs*
Main# cd nfs-server-2.2beta29/
Main# ls -l
Main# less README 
Main# man exports
Main# cd ../HOWTO/
Main# ls N*
Main# less NFS-HOWTO 
Main# pico /etc/exports

Added:
---------------------------
/mnt/cdrom
---------------------------

the '---' above is just the start and end of the file. Yes, I left the
export wide open, but I'm on an isolated, trustworthy network... :)
The cdrom is already mounted.

Main# cat /etc/exports

Just to check I saved.

Main# find /usr/doc | grep port
Main# ls -l /usr/doc/portmap-4.0
Main# less /usr/doc/portmap-4.0/README
Main# find /etc -iname port*
Main# /etc/rc.d/init.d/portmap start
Main# /etc/rc.d/init.d/nfs start
Main# rpcinfo -p

Checked that NFS was listed, as per /usr/doc/HOWTO/NFS-HOWTO, which was
open on another Virtual Terminal (Alt-F? keys).

Next, I setup a Pentium 100 testbed that I have Redhat 5.1 on as well,
configured it's PLIP interface, pinged each - Main=19.168.2.1,
P100=192.168.2.2:

P100# ifconfig plip1 192.168.2.2 pointopoint 192.168.2.1 up
P100# route add 192.168.2.1
P100# ping 192.168.2.1

Main# ping 192.168.2.2

Beauty ! Both seem to see each other.

Now, to test the NFS server, I'll mount the NFS exported /mnt/cdrom via
PLIP, to my cd mount point (before I stole the cd drive for something
else), as per NFS-HOWTO:

P100# mount -o rsize=1024,wsize=1024 192.168.2.1:/mnt/cdrom /mnt/cdrom
P100# ls /mnt/cdrom

Hey, it worked.

Now to try this during an install. I created the two RedHat 5.2 (APC -PB
9811, which won't boot off CD) diskettes, although theoretically, I
shouldn't need the supp for an NFS install. 

Main# dd if=/mnt/cdrom/bootimg/boot.img of=/dev/fd0
Main# dd if=/mnt/cdrom/bootimg/supp.img of=/dev/fd0

Make sure you insert, replace and label the diskettes (should I have to
say...)

Now a reboot of the P100, booting on the RedHat 5.2 install diskette
(boot.img). Enter key, for normal install, OK, English, us keyboard, NFS
image, Page Down key (5 times) PLIP, Autoprobe, Static IP address:

  IP address:           192.168.2.2
  Netmask:              255.255.255.255
  Default gateway (IP): 192.168.2.2
  Primary nameserver:   

OK. 

I left the next panel (Domain name, etc) blank, then:

NFS server name:   192.168.2.1
Red Hat directory: /mnt/cdrom

Chugg, chugg, chugg, second stage install, Upgrade or Install, beauty !.
At this point, I stopped, 'cos I didn't want to upgrade the P100 to RedHat
5.2

Now to be honest, the first time I did the install, I accepted the install
programs default netmask of 255.255.255.0. THIS DOES NOT WORK !. I surfed
to DejaNews and Redhat, and eventually found "PLIP tips":
http://www.redhat.com/support/docs/rhl/PLIP-Tips/

Reading DejaNews (Power search, linux & plip & install), I saw this thread,
and a number of others, which had one guy continually touting PLIP install,
but apparently hadn't even tried it, and one guy asking if anybody actually
did it (If your reading this now, please quote the "PLIP tips" site as
well, instead of just the PLIP FAQ for PLIP installs). Anyway, reading PLIP
tips, I saw something in PLIP-Tips-5.html, which twigged me to the problem:

  PLIP is a point-to-point protocol (like PPP), not a broadcast protocol
  (like ethernet); to configure a PLIP interface, you need use the
  pointopoint keyword...

Plus, the next page (PLIP-Tips-6.html), has a netmask of 255.255.255.255.

Anyway, give that a go !


  __   __   _______________________________
 //)) //)) | Richard RUDEK. MicroDek.      | Hey, it's Friday night...
//\\ //\\  | Chatswood, Sydney. Australia. | C:\WORK> CD \  
           `-------------------------------'