Re: Quagga Installation Questions

2004-04-03 Thread Peter E. Abresch Jr. - at Pepco
I finally completed my quagga .spec file. I had to make additional 
adjustments. I created a quagga-0.96.4-3.s390.rpm. I used rpm to 
uninstall zebra and then used my new quagga rpm to install quagga. I then 
customized my zebra and ospfd conf files and all seems to be working fine.

This was my first .spec file. I want to thank everyone for their 
assistance and patience. I am now working on a .spec file for Net-Telnet 
perl package so I can check out mrlg.cgi.

Peter

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Quagga Installation Questions

2004-03-31 Thread Peter E. Abresch Jr. - at Pepco
I am getting all so close, I have completed my .spec file and successfully 
tested it. Some last minute questions.

I am ready to do the rpm ?bb quagga-0.96.4.spec. There was a method to 
redirect the output to the terminal and to a file so I can review it. It 
was a redirection command and for the life of me, I cannot get my syntax 
correct. Can someone provide me the syntax?

Once the rpm binary is built, is there anything I can do to test/verify 
that everything is ok before actually installing it?

Thanks much.

Peter

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Quagga Installation Questions

2004-03-31 Thread Daniel Jarboe
 I am ready to do the rpm ?bb quagga-0.96.4.spec. There was a method
to
 redirect the output to the terminal and to a file so I can review it.
It
 was a redirection command and for the life of me, I cannot get my
syntax
 correct. Can someone provide me the syntax?

Something like rpm -bb quagga-0.96.4.spec 
/usr/src/packages/BUILD/quagga-build.log 21  should work.  This will
redirect your stdout and stderr, and run the build in the background.

 Once the rpm binary is built, is there anything I can do to
test/verify
 that everything is ok before actually installing it?

If rpm -bb gets far enough to write rpm files, you are well on your way.
Only thing I can think to check are the standard queries you do on rpm's
but with a -p option and specify the filename that was written.  For
example, you can run rpm -qpl quagga-0.96.4.s390.rpm (or whatever the
filename) and make sure all the files you think should be there are...

Other biggees are rpm -qp --scripts and rpm -qpR, etc.  There's a
bunch of query options listed in the man pages.  There's also rpm
--checksig too, I suppose, but of course that should succeed.

~ Daniel









---

This message is the property of Time Inc. or its affiliates. It may be
legally privileged and/or confidential and is intended only for the use
of the addressee(s). No addressee should forward, print, copy, or
otherwise reproduce this message in any manner that would allow it to be
viewed by any individual not originally listed as a recipient. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorized disclosure, dissemination, distribution,
copying or the taking of any action in reliance on the information
herein is strictly prohibited. If you have received this communication
in error, please immediately notify the sender and delete this message.
Thank you.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Quagga Installation Questions

2004-03-31 Thread Post, Mark K
If you want to have the output come to your terminal _and_ sent to a file,
use the tee command:
rpm -bb quagga-0.96.4.spec | tee /path/to/output/file


Mark Post

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Peter
E. Abresch Jr. - at Pepco
Sent: Wednesday, March 31, 2004 9:01 AM
To: [EMAIL PROTECTED]
Subject: Re: Quagga Installation Questions


I am getting all so close, I have completed my .spec file and successfully
tested it. Some last minute questions.

I am ready to do the rpm ?bb quagga-0.96.4.spec. There was a method to
redirect the output to the terminal and to a file so I can review it. It
was a redirection command and for the life of me, I cannot get my syntax
correct. Can someone provide me the syntax?
-snip-

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Quagga Installation Questions

2004-03-31 Thread Peter E. Abresch Jr. - at Pepco
OK, I am getting excited now. I just built my first rpm and it looks good, 
at least to a Linux newbe like myself. I think I am ready to install it, 
but?.

The following command reveals rpm -ihv --test quagga-0.96.4-3.s390.rpm

error: failed dependencies:
ucd-snmp   is needed by quagga-0.96.4-3
initscripts = 5.60 is needed by quagga-0.96.4-3


I have package ucdsnmp-4.2.5-83 installed. Do I need to go back and change 
the .spec file:

%if %with_snmp
Prereq: ucd-snmp
%endif

to

%if %with_snmp
Prereq: ucdsnmp
%endif

and rebuild?

What about initscripts? I do not understand what initscripts is and if it 
is really required under SuSE. Can any one shed any additional light on 
this?

When it come down to do the actual install, Should I uninstall zebra using 
rpm ?e zebra-0.93b-83 before installing quagga using rpm -ihv 
quagga-0.96.4-3.s390.rpm? It looks like there are duplicate files.

Thanks very much.

Peter

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Quagga Installation Questions

2004-03-31 Thread Post, Mark K
Cool.  Feeling like that is one reason why I like working with Linux.

Changing the prereq for ucdsnmp should get you past that hurdle.  The
initscripts prereq is the same thing, just another package on the system.
When I do a rpm -ql initscripts on a Red Hat system, I get a list of
files, some of which include what I expected to see:
/etc/rc
/etc/rc.d
/etc/rc.d/init.d
/etc/rc.d/init.d/functions
/etc/rc.d/init.d/halt
/etc/rc.d/init.d/halt.s390init
/etc/rc.d/init.d/killall
/etc/rc.d/init.d/netfs
/etc/rc.d/init.d/network
/etc/rc.d/init.d/random
/etc/rc.d/init.d/rawdevices
/etc/rc.d/init.d/single
/etc/rc.d/rc
/etc/rc.d/rc.local

If I find the corresponding files on a SLES8 system, and do an  rpm -qf
/etc/rc.d/rc0.d I get this:
filesystem-2002.9.2-32

The other one I checked, /etc/rc.d/rc gave this:
aaa_base-2002.11.5-1

I would suspect that aaa_base is the package you need, since it provides the
directory framework for all the initscripts.  But, what I would do is look
at the SUSE SRPM for zebra, and see what it calls out.  Substitute that for
initscripts.

And yes, I would remove zebra before installing quagga.  You could add a
--replacefiles switch, but that's something I prefer to avoid.


Mark Post


-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Peter
E. Abresch Jr. - at Pepco
Sent: Wednesday, March 31, 2004 11:53 AM
To: [EMAIL PROTECTED]
Subject: Re: Quagga Installation Questions


OK, I am getting excited now. I just built my first rpm and it looks good,
at least to a Linux newbe like myself. I think I am ready to install it,
but?.

The following command reveals rpm -ihv --test quagga-0.96.4-3.s390.rpm

error: failed dependencies:
ucd-snmp   is needed by quagga-0.96.4-3
initscripts = 5.60 is needed by quagga-0.96.4-3


I have package ucdsnmp-4.2.5-83 installed. Do I need to go back and change
the .spec file:

%if %with_snmp
Prereq: ucd-snmp
%endif

to

%if %with_snmp
Prereq: ucdsnmp
%endif

and rebuild?

What about initscripts? I do not understand what initscripts is and if it
is really required under SuSE. Can any one shed any additional light on
this?

When it come down to do the actual install, Should I uninstall zebra using
rpm ?e zebra-0.93b-83 before installing quagga using rpm -ihv
quagga-0.96.4-3.s390.rpm? It looks like there are duplicate files.

Thanks very much.

Peter

--
For LINUX-390 subscribe / signoff / archive access instructions, send email
to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Quagga Installation Questions

2004-03-31 Thread Rob van der Heij
Peter E. Abresch Jr. - at Pepco wrote:

error: failed dependencies:
   ucd-snmp   is needed by quagga-0.96.4-3
   initscripts = 5.60 is needed by quagga-0.96.4-3


I think this is because your Red Hat spec file specifies pre-required
package names that are used for Red Hat packages, and not the SuSE ones.
Some of the things that Red Hat ship in initscripts come in sysconfig on
SuSE.
If you're brave you remove those dependencies from the spec file and
build again. Provided you have AutoReq on, many of the prereqs of the
package will be done already. If you can find which additional prereqs
you have it may save you time in the future.
Some will encourage to install with --nodeps but I hate that because APT
will complain about that later.
Rob

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Quagga Installation Questions

2004-03-31 Thread Peter E. Abresch Jr. - at Pepco
I replaced ucc-snmp with ucdsnmp and replaced initscripts with aaa_base 
and rebuilt. As Mark pointed out, this was in the original src.rpm for 
Zebra. I ran the rpm -ihv --test quagga-0.96.4-3.s390.rpm and it failed 
with many conflicts such as the following:

file /usr/sbin/zebra from install of quagga-0.96.4-3 conflicts with file 
from package zebra-0.93b-83

I am thinking this is a very good thing and is one of the very benefits of 
using rpm to begin with. I will remove zebra and install quagga later this 
week. I will post my final results.

Thank to everyone that contributed and cross your fingers for me.

Peter

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Quagga Installation Questions

2004-03-31 Thread Rob van der Heij
Peter E. Abresch Jr. - at Pepco wrote:

file /usr/sbin/zebra from install of quagga-0.96.4-3 conflicts with file
from package zebra-0.93b-83

One of the things your package probably should say is 'Conflicts:
zebra'  so that RPM will force you to take zebra out before you install
quagga.
Rob

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Quagga Installation Questions

2004-03-30 Thread Peter E. Abresch Jr. - at Pepco
I have downloaded Quagga 96.4. In the tarball directory I found the
following under subdirectory redhat containing quagga-0.96.4.spec. I used
this as a template to create a spec for SuSE SLES8. I am seeing a build
requirement for package tetex. This is not part of the SuSe SLES8
distribution. I have been unable to determine if tetex is really necessary
or not. Should I install tetex as well? Any ideas and opinions are
welcomed. Thanks.

Peter


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Quagga Installation Questions

2004-03-30 Thread Adam Thornton
On Tue, 2004-03-30 at 09:48, Peter E. Abresch Jr. - at Pepco wrote:
 I have downloaded Quagga 96.4. In the tarball directory I found the
 following under subdirectory redhat containing quagga-0.96.4.spec. I used
 this as a template to create a spec for SuSE SLES8. I am seeing a build
 requirement for package tetex. This is not part of the SuSe SLES8
 distribution. I have been unable to determine if tetex is really necessary
 or not. Should I install tetex as well? Any ideas and opinions are
 welcomed. Thanks.

I would be vastly surprised if tetex were needed except to produce
pretty documentation.

See, this is what I have against SuSE: everything is built with all the
features turned on, and everything has huge and surprising dependencies,
so it's impossible to build a minimal system.

Adam

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Quagga Installation Questions

2004-03-30 Thread Post, Mark K
Adam,

Except I don't think that SUSE is the one introducing the tetex requirement.
The .spec file did come from someone building it on a Red Hat system of some
kind (most likely Intel).


Mark Post

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Adam
Thornton
Sent: Tuesday, March 30, 2004 10:54 AM
To: [EMAIL PROTECTED]
Subject: Re: Quagga Installation Questions


On Tue, 2004-03-30 at 09:48, Peter E. Abresch Jr. - at Pepco wrote:
 I have downloaded Quagga 96.4. In the tarball directory I found the
 following under subdirectory redhat containing quagga-0.96.4.spec. I
 used this as a template to create a spec for SuSE SLES8. I am seeing a
 build requirement for package tetex. This is not part of the SuSe
 SLES8 distribution. I have been unable to determine if tetex is really
 necessary or not. Should I install tetex as well? Any ideas and
 opinions are welcomed. Thanks.

I would be vastly surprised if tetex were needed except to produce pretty
documentation.

See, this is what I have against SuSE: everything is built with all the
features turned on, and everything has huge and surprising dependencies, so
it's impossible to build a minimal system.

Adam

--
For LINUX-390 subscribe / signoff / archive access instructions, send email
to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Quagga Installation Questions

2004-03-30 Thread Adam Thornton
On Tue, 2004-03-30 at 10:28, Post, Mark K wrote:
 Adam,

 Except I don't think that SUSE is the one introducing the tetex requirement.
 The .spec file did come from someone building it on a Red Hat system of some
 kind (most likely Intel).

Fair enough.  Then it's why I dislike Red Hat *too*.

Hey, I just want a system that doesn't think it has to install X, TeX,
and audio libraries to, say, handle e-mail.

Adam

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Quagga Installation Questions

2004-03-30 Thread Daniel Jarboe
 I am seeing a build requirement for package tetex. This is not part
 of the SuSe SLES8 distribution. I have been unable to determine if
 tetex is really necessary or not. Should I install tetex as well?
 Any ideas and opinions are welcomed. Thanks.

There are te... and ...tex type packages available on your
supplementary cd, including tetex-beta.20020207-93.  After it's
installed, you should probably go through the motions of YaST2's SuSE
config.  I don't remember if it was one of the te/tex type packages or
just docbook, but even after installing them for a build, the doc
portion still failed with errors.  Later after SuSE config ran, however,
everything just worked.

At any rate, the tetex would only be required to build the src.rpm into
the appropriate arch.rpms.  It won't be a run-time/install dependency.
Meaning if you have one big image that you do your building on, once the
rpm is built you can install it on other images without tetex without
any problem.  An alternative is to look at how the .spec is constructed.
The author might have been nice enough to let you easily disable
building the documentation that relies on tetex.  If not, it gets more
complicated, and is usually easier to just install the package than
hunting through the configure/Makefile etc.

~ Daniel







---

This message is the property of Time Inc. or its affiliates. It may be
legally privileged and/or confidential and is intended only for the use
of the addressee(s). No addressee should forward, print, copy, or
otherwise reproduce this message in any manner that would allow it to be
viewed by any individual not originally listed as a recipient. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorized disclosure, dissemination, distribution,
copying or the taking of any action in reliance on the information
herein is strictly prohibited. If you have received this communication
in error, please immediately notify the sender and delete this message.
Thank you.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Quagga Installation Questions

2004-03-30 Thread Rob van der Heij
On Tue, 2004-03-30 at 18:37, Adam Thornton wrote:

 Fair enough.  Then it's why I dislike Red Hat *too*.

 Hey, I just want a system that doesn't think it has to install X, TeX,
 and audio libraries to, say, handle e-mail.

And since some of the packages are named differently, the build
requirements for SuSE and Red Hat are not the same. That's why I
suggested to take a src.rpm package for SuSE on Intel when you can find
it, rather than Red Hat on Intel.
When I recall correctly the quagga build required texinfo, automake and
readline-devel. I don't have TeX installed.

Rob

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Quagga Installation Questions

2004-03-30 Thread Gregg C Levine
Hello from Gregg C Levine
I'm not planning on launching an argument over distributions, but what
about mine? I use Slackware? It's not completely dependant on all the
funny stuff that you commented on. In fact, its even easier to work
with then the current Red release, for Intel. Debian, I can't seem to
get to work, with my normal system, the installer complains about my
network card choice. 

Remember, I'm an Intel person watching the fun inside the mainframe
community.
---
Gregg C Levine [EMAIL PROTECTED]

The Force will be with you...Always. Obi-Wan Kenobi
Use the Force, Luke.  Obi-Wan Kenobi

 -Original Message-
 From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf
Of
 Adam Thornton
 Sent: Tuesday, March 30, 2004 11:37 AM
 To: [EMAIL PROTECTED]
 Subject: Re: [LINUX-390] Quagga Installation Questions
 
 On Tue, 2004-03-30 at 10:28, Post, Mark K wrote:
  Adam,
 
  Except I don't think that SUSE is the one introducing the tetex
requirement.
  The .spec file did come from someone building it on a Red Hat
system of some
  kind (most likely Intel).
 
 Fair enough.  Then it's why I dislike Red Hat *too*.
 
 Hey, I just want a system that doesn't think it has to install X,
TeX,
 and audio libraries to, say, handle e-mail.
 
 Adam
 

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Quagga Installation Questions

2004-03-28 Thread Rob van der Heij
Peter E. Abresch Jr. - at Pepco wrote:

I did not see any Quagga source for SuSE SLES8. Can I use the source RPM
for the Fedora distribution and if so, what if anything do I need to
change?
You mention the i386 version and build my s390.rpm package. What do I need
to change in the i386 package?

Ideally, nothing... In the early days we had to pick up the proper
versions of config.sub and config.guess but these days they are normally
up-to-date.
Just to try, I picked up the source package for SuSE 9
ftp://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/suse/i386/9.0/suse/src/quagga-0.96.2-22.src.rpm
and then something like this:
rpm -i quagga-0.96.2-22.src.rpm
cd /usr/src/packages/SPECS
rpm -bb quagga.spec
And when all works fine you find the rpm packages in ../RPMS/s390. In
this case I noticed that we miss a macro so I had to comment out line 29
in the spec file (and remember that my package is missing some
dependencies). That seemed enough to make it build (after I installed
automake, texinfo and libread-devel - wouldn't it be nice if SuSE
packages would have proper build requirements listed). Whether the thing
works is another issue. The fact that SuSE provide it with the Intel
version but not with s390 make one wonder.
I see S390 and S390x. What is the difference?


The s390 is meant for a 32-bit distribution, and s390x is the 64-bit one.

Rob

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Quagga Installation Questions

2004-03-27 Thread Peter E. Abresch Jr. - at Pepco
I am currently running SuSE Linux SLES8 SP03 in a Linux LPAR. I am
currently running Zebra that was package with SuSE Linux and wish to
upgrade or replace it with the latest release of Quagga. SuSE does not
have a Quagga RPM or SRPM. I am a newbe and have the following questions:

Is their a preferred site for obtaining the latest release of Quagga?

Should I download the source tarball and simply compile it using
configure, make, and make install?

Should I create an SRPM and then RPM from the source tarball? If so, where
do I start?

Any recommendation and opinions are welcome.

Your patience and understanding is appreciated. Thanks.

Peter

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Quagga Installation Questions

2004-03-27 Thread Rob van der Heij
Peter E. Abresch Jr. - at Pepco wrote:

Is their a preferred site for obtaining the latest release of Quagga?

Should I download the source tarball and simply compile it using
configure, make, and make install?

You could, but you will be on your own. You also have  to install a
compiler and all other -devel packages that you need for building it on
each system where you install it. And you will need how to configure.
And you would have no package management for it.
Should I create an SRPM and then RPM from the source tarball? If so, where
do I start?

I like www.rpmseek.com for packages that fit SuSE (and freshmeat.net
appears better for Red Hat). I typically would take the src.rpm that was
used for the i386 version and build my s390.rpm package (once, on a
system that does have all -devel packages that I need).
However, at
http://rpmseek.com/rpm-pl/quagga.html?hl=comcs=quagga:PN:0:0:0:0  I
also see s390.rpm packages, so I think I might even have tried that.
Rob

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Quagga Installation Questions

2004-03-27 Thread Peter E. Abresch Jr. - at Pepco
Thanks for responding. I went to the site and see the source rpm for
Quagga and S390. Some more questions:

I did not see any Quagga source for SuSE SLES8. Can I use the source RPM
for the Fedora distribution and if so, what if anything do I need to
change?

You mention the i386 version and build my s390.rpm package. What do I need
to change in the i386 package?

I see S390 and S390x. What is the difference?

Thanks again.

Peter





Rob van der Heij [EMAIL PROTECTED]
Sent by: Linux on 390 Port [EMAIL PROTECTED]
03/27/2004 11:54 AM
Please respond to Linux on 390 Port


To: [EMAIL PROTECTED]
cc:
Subject:Re: Quagga Installation Questions


Peter E. Abresch Jr. - at Pepco wrote:

Is their a preferred site for obtaining the latest release of Quagga?

Should I download the source tarball and simply compile it using
configure, make, and make install?


You could, but you will be on your own. You also have  to install a
compiler and all other -devel packages that you need for building it on
each system where you install it. And you will need how to configure.
And you would have no package management for it.

Should I create an SRPM and then RPM from the source tarball? If so,
where
do I start?


I like www.rpmseek.com for packages that fit SuSE (and freshmeat.net
appears better for Red Hat). I typically would take the src.rpm that was
used for the i386 version and build my s390.rpm package (once, on a
system that does have all -devel packages that I need).
However, at
http://rpmseek.com/rpm-pl/quagga.html?hl=comcs=quagga:PN:0:0:0:0  I
also see s390.rpm packages, so I think I might even have tried that.

Rob

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390




--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Quagga Installation Questions

2004-03-27 Thread Adam Thornton
On Sat, 2004-03-27 at 10:15, Peter E. Abresch Jr. - at Pepco wrote:
 I am currently running SuSE Linux SLES8 SP03 in a Linux LPAR. I am
 currently running Zebra that was package with SuSE Linux and wish to
 upgrade or replace it with the latest release of Quagga. SuSE does not
 have a Quagga RPM or SRPM. I am a newbe and have the following questions:

 Is their a preferred site for obtaining the latest release of Quagga?

http://www.quagga.net/

 Should I download the source tarball and simply compile it using
 configure, make, and make install?

That's what I'd do.

 Should I create an SRPM and then RPM from the source tarball? If so, where
 do I start?

That would be very nice of you.  You'd start with the Maximum RPM book
at http://www.rpm.org/max-rpm/ but be careful: it's easy to go down this
slope and become the guy that packages Quagga for SLES8 on 390 and
zSeries.  Then you start accepting bug reports and before you know it
you're a project maintainer.

Adam

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390