Re: [Linux-decnet-user] dnprogs installation on Red Hat 8.0 (success!)

[Larry B. <ba...@us...>]

I installed my Red Hat 8.0 Linux system as a Server, i.e., I selected =
the Server installation option.  I did not have to do anything special =
with Red Hat after that, except for "MACADDR=3D..." and "depmod -a", as =
I wrote.  Before I installed DECnet, I read in the linux-decnet FAQ that =
the 2.4 kernels had DECnet built in.  I found that the =
/boot/config-2.4.* files on my system already had the DECNET parameters =
defined, so I assumed I'd be OK.  Take a look at your /boot/config* =
files.  As far as loading the decnet.o module, I think that happens =
automatically on-demand, provided the kernel can find it (hence, the =
necessity for the "depmod -a" command).

Larry Baker
US Geological Survey

  ----- Original Message -----=20
  From: McVeagh, John=20
  To: 'Larry Baker' ; lin...@li...=20
  Sent: Wednesday, May 21, 2003 6:10 AM
  Subject: RE: [Linux-decnet-user] dnprogs installation on Red Hat 8.0 =
(success!)


  Larry,

  Thanks for posting the step by step process for Redhat.  I have a =
related question.=20
  Did you find that DECnet support was enabled (active) in the kernel or =
did you have to load a module (decnet.o)?

  John McVeagh
  CSX Technology



    -----Original Message-----
    From: Larry Baker [mailto:ba...@us...]
    Sent: Tuesday, May 20, 2003 6:57 PM
    To: lin...@li...
    Subject: [Linux-decnet-user] dnprogs installation on Red Hat 8.0 =
(success!)


    My Red Hat 8.0 Linux DECnet installation seems to work now (with one =
minor annoyance, see below).  I used the information in the online HTML =
man pages and FAQs as a reference.  The steps I followed were:

    Download dnprogs-2.23-1.i386.rpm to /usr/local/src

    Install the dnprogs RPM:

        # cd /usr/local/src
        # rpm -Uvh dnprogs-2.23-1.i386.rpm

        Ignore the messages about not being user patrick

        Answer the questions to define the DECnet network

    Optionally configure the DECnet hosts file:

        # vi /etc/decnet.conf

        Add more hosts, etc.

    Optionally configure the DECnet objects file:

        # vi /etc/dnetd.conf

        Comment out unneeded objects, etc.

    Optionally configure the DECnet proxy file:

        # vi /etc/decnet.proxy

        Add DECnet->Linux userid mappings, etc.

    Configure the DECnet startup/shutdown script:

        # vi /etc/init.d/decnet

        Change "prefix=3D/usr/local" to "prefix=3D/usr" (the rpm =
installation
        puts the executables in /usr..., not /usr/local...)

    Configure the Ethernet MAC address:

        16-bit DECnet address =3D ( area-no. * 1024 ) + node-no.
        Convert 16-bit DECnet address to hex
        Swap hex bytes and append to AA:00:04:00

        For example, 63.171 =3D ( 63 * 1024 ) + 171 =3D 64683 =3D FCAB
        MAC address for 63.171 =3D AA:00:04:00:AB:FC

        # vi /etc/sysconfig/network-scripts/ifcfg-eth0

        Add a line specifying the MAC address using the MACADDR keyword

        # DECnet host address 63.171
        MACADDR=3DAA:00:04:00:AB:FC

        On my system, I also made ifcfg-eth0 executable

        # chmod +x /etc/sysconfig/network-scripts/ifcfg-eth0

    Update the kernel module database:

        # depmod -a

    Enable the DECnet service:

        # chkconfig --level 345 decnet on

    Reboot

        # reboot

    Try something

        # dnping local-host
        # dnping remote-host


    On my Red Hat 8.0 system, after DECnet is enabled, "ifconfig" no =
longer works without an explicit interface argument.  This is a minor =
annoyance, which I ignore.

    Larry Baker
    US Geological Survey