Linux-Development-Sys Digest #539, Volume #6 Sat, 27 Mar 99 13:14:05 EST
Contents:
Re: G200 Suport.. (Philipp Lohmann)
Re: Using Linux TCP/IP source for an embedded uP? (James Youngman)
Re: RS485 & Linux: Must toggle DTR quickly (James Youngman)
Re: RS485 & Linux: Must toggle DTR quickly (James Youngman)
Re: Debugging terrible stack corruption problems - tips or tools? (James Youngman)
Re: SIG-PIPE ? (Thibaut Maquet)
Free IDE for developing under Linux (Christoph Lindner)
Re: Idea: Make a seperate "i686" tree for Redhat Linux 6.0 (David Fox)
Re: Kernel NFS: equivalent to userland nfsd -r in kernel NFS (Sid Boyce)
Re: ISA programming (Timothy Wall)
Re: Using Linux TCP/IP source for an embedded uP? ("Bjorn Wesen")
Re: Update Kernel 2.2.3 only seeing 64MB RAM on 128MB RAM PC, 2.0.36 works OK (BUG
?) (Michael Geary)
problem with a PCI device config space (Francesco Giacomini)
Re: how do I uninstall gtk+ (David T. Blake)
SUSE and RH5.1 RPM ?
----------------------------------------------------------------------------
From: Philipp Lohmann <[EMAIL PROTECTED]>
Subject: Re: G200 Suport..
Date: Sat, 27 Mar 1999 11:54:57 GMT
Hi,
this card is well supported by Xfree. Look at www.xfree86.org for the=20
latest drivers.
Regards, pl
>>>>>>>>>>>>>>>>>> Urspr=FCngliche Nachricht <<<<<<<<<<<<<<<<<<
Am 27.03.99, 01:04:40, schrieb "Riacardo" <[EMAIL PROTECTED]> zum =
Thema G200 Suport..:
> I am hanving trouble fiding suport or drivers for my new Matrox G200=
=20
AGP
> on Red Hat 5.2.
> Can anybody help me ????
> Ricardo
------------------------------
From: James Youngman <[EMAIL PROTECTED]>
Subject: Re: Using Linux TCP/IP source for an embedded uP?
Date: 26 Mar 1999 23:32:43 +0000
[EMAIL PROTECTED] (Deton8) writes:
> Hi,
> Would it be possible to use the Linux TCP/IP source to create an embedded
> microprocessor's TCP/IP stack? The commercial ones all seem to be at least
> $5000 with the average about $15000, and I bet that the Linux driver is of
> higher quality anyway.
Yes, but are you planning to comply with the GPL?
--
ACTUALLY reachable as @free-lunch.demon.(whitehouse)co.uk:james+usenet
------------------------------
From: James Youngman <[EMAIL PROTECTED]>
Crossposted-To: comp.arch.embedded
Subject: Re: RS485 & Linux: Must toggle DTR quickly
Date: 26 Mar 1999 23:46:47 +0000
Olav Woelfelschneider <[EMAIL PROTECTED]> writes:
> Keywords: RS485-Network, Linux
>
> I try to run a small RS485 network off the serial port of a PC. The PC polls
> some gadgets with microcontrollers in them.
>
> The PC is coupled via a RS232-RS485 converter which uses DTR to
> switch between transmit and receive. (I use the half-duplex approach with
> only one pair of wires.)
>
> So, to send some data, I turn DTR on, write() the bytes and turn DTR off
> again after the last byte fell out of the UART.
IIRC, you can't tell that. IIRC, the 16{4,5,6}50 will only tell you
when the last byte has passed from the FIFO (or holding register) into
the shift register.
Maybe I'm thinking of the Zilog SCC series or the Motorola MFP,
though. It's been a while...
--
ACTUALLY reachable as @free-lunch.demon.(whitehouse)co.uk:james+usenet
------------------------------
From: James Youngman <[EMAIL PROTECTED]>
Crossposted-To: comp.arch.embedded
Subject: Re: RS485 & Linux: Must toggle DTR quickly
Date: 26 Mar 1999 23:50:51 +0000
[EMAIL PROTECTED] (Matthew T. Linehan) writes:
> More so than you have realized yet. I'm not familiar with the Linux
> implementation, but most serial drivers consider the buffer flushed,
> and done as soon as the last byte to be transmitted as been sent to
> the uart. The problem is, it takes about 1mS (9600 baud) for the uart
> to finish transmitting the character. If your using a buffered uart,
> the problem gets much worse!
Actually, IIRC it's a holding-register versus shift-register problem.
> If you manage to get a fast DTR shut off routine working, you WILL cut
> off the last few bits of your last character. Been there, done that.
Something that just occurred to me is that you may be able to put the
UART into loopback mode and hence know to toggle the DTR when you have
*received* the character. This will only work if the Tx line is not
tri-stated (or otherwise not actually outputting) while in loopback
mode (I can't remember). If you do this, though, you will also have
to turn off the receive FIFO or wait a couple of character-times :-(
> The easiest solution is to not control the 485 transmitter in
> software. Use a one shot circuit in the RS-232 to 485 converter to do
> the dirty work for you.
Actually the easiest solution is to use an extra 2 wires :-)
--
ACTUALLY reachable as @free-lunch.demon.(whitehouse)co.uk:james+usenet
------------------------------
From: James Youngman <[EMAIL PROTECTED]>
Subject: Re: Debugging terrible stack corruption problems - tips or tools?
Date: 26 Mar 1999 23:42:51 +0000
"David Mellor" <[EMAIL PROTECTED]> writes:
> Does any one have any tips or tools for resolving those terrible stack
> corruption problems please?
Checker-GCC?
> I have a problem where function parameters become inaccessible part way
> through a function, as a result of stack corruption - caused by something
> the function has done. I get a segmentation fault when I access
> them.
Split the function, to isolate the problem.
> Unfortunately I can not reproduce the problem under Windows, or I would use
> Purify to try to find the source of the problem.
Try Checker. (q.v.) Ask Pure Software for a Linux port, too.
--
ACTUALLY reachable as @free-lunch.demon.(whitehouse)co.uk:james+usenet
------------------------------
From: Thibaut Maquet <[EMAIL PROTECTED]>
Subject: Re: SIG-PIPE ?
Date: Sat, 27 Mar 1999 14:32:07 +0100
Steve Peltz wrote:
>
> >So, you mean NetScape or TCPD closed the pipe we were using during
> >a NNTP transaction, but I don't see any reason why one of the
> >programs closed it before the end of this transaction. Does it mean
> >there is something wrong in one of the programs ?
>
> Usually that will happen if the user aborts the transaction; either he
> hits stop, requests something else, or quits the program.
Meaning to say, Netscape suddendly left my program; this is a little
bizarre coz I didn't notice any "QUIT" from the NNTP transaction.
So I presume Netscape considers the session has been canceled after
something I haven't found yet (Maybe, a transaction error or something
similar). I am resuming the transaction since I didn't notice any
"QUIT" but in fact, the NNTP transaction has already been terminated
by Netscape and therefore writting to a closed pipe will set the
SIG_PIPE signal. I guess this is what's happening.
>
> >Actually I am not using any pipe in my program; surely tcpd does !
> >But I can't get any control on the pipes of tcpd, there should be
> >something wrong in the NNTP transaction maybe illegal characters
> >or someting else.
>
> tcpd just forks with the socket as stdin/stdout, and your program just
> just reads from them, right? A tcp socket is just a "pipe" as far as the
> system is concerned.
Ok, I suppose tcpd has terminated after "something"; so I have to
determine
now that "something".
Regards
Thibaut Maquet
------------------------------
From: Christoph Lindner <[EMAIL PROTECTED]>
Subject: Free IDE for developing under Linux
Date: Sat, 27 Mar 1999 12:17:47 +0100
I´m just a beginner in programming under linux now.
But I want to start coding under Linux in C or C++
and I´m looking for a free compfortable IDE to do so.
I´ve programmed some very small app. yet by
using xemax, saving the .cc file and starting the gcc
from command line.
What I need is a easy to use tool to generate the makefile
for larger projects by itself, to generate ressources and so on.
How do you guys manage large projects ?
At the moment I use the Code Warrior under NT.
Thank you for your help
Chris
------------------------------
From: d s f o x @ c o g s c i . u c s d . e d u (David Fox)
Crossposted-To:
comp.os.linux.misc,linux.redhat.misc,alt.linux,alt.os.linux,comp.os.linux.hardware
Subject: Re: Idea: Make a seperate "i686" tree for Redhat Linux 6.0
Date: 27 Mar 1999 06:49:35 -0800
"Idea Man" <[EMAIL PROTECTED]> writes:
> Does anyone else think this would be a good idea? Keep the i386 tree, and
> add an i686 tree that is optimized for P-II/Celeron/P-III processors.
>
> This might be a pain in the butt for the mirrors (more hard drive space
> used), but for some mirrors this would be just fine. This would also make
> Linux higher performing for all the people with flashy new Pentium-III
> machines...
How much performance improvement would there be?
--
David Fox http://hci.ucsd.edu/dsf xoF divaD
UCSD HCI Lab baL ICH DSCU
------------------------------
From: Sid Boyce <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: Kernel NFS: equivalent to userland nfsd -r in kernel NFS
Date: Sat, 27 Mar 1999 15:03:15 +0000
Andi Kleen wrote:
>
>
> Knfsd does not support it. If you still need reexporting you have
> to use the usermode nfsd for that.
>
> -Andi
>
Sure it does, "kexportfs -r". It is in knfsd-xxxx/utils/exportfs/, when
you do a make install, the result is that exportfs ends up as
/sbin/kexportfs. I have been using it successfully for quite a time on
both my machines.
Regards
--
... Sid Boyce...Amdahl(Europe)...44-121 422 0375
Any opinions expressed above are mine and do not necessarily represent
the opinions or policies of Amdahl Corporation.
------------------------------
From: Timothy Wall <[EMAIL PROTECTED]>
Subject: Re: ISA programming
Date: Sat, 27 Mar 1999 10:31:28 -0500
just about any i/o port in the 16-bit address range
Antoine FERRAN wrote:
> I'd like to know the memory adresses that could be used by an ISA card.
>
> Please mail me back at :
> [EMAIL PROTECTED]
>
> Thanks!
------------------------------
From: "Bjorn Wesen" <[EMAIL PROTECTED]>
Subject: Re: Using Linux TCP/IP source for an embedded uP?
Date: Sat, 27 Mar 1999 17:24:01 +0100
James Youngman wrote in message ...
>> Would it be possible to use the Linux TCP/IP source to create an embedded
>> microprocessor's TCP/IP stack?
>
>Yes, but are you planning to comply with the GPL?
He would only break GPL if he modifies the stack and refuse giving out the
changes. But why modify it, it's good as it is :)
/Bjorn
------------------------------
From: [EMAIL PROTECTED] (Michael Geary)
Subject: Re: Update Kernel 2.2.3 only seeing 64MB RAM on 128MB RAM PC, 2.0.36 works OK
(BUG ?)
Date: Sat, 27 Mar 1999 15:39:50 GMT
I wrote:
>> Is the kernel mailing list the right place to report this? I'll go
>> look up the archives to get myself familiarized with the list...
[EMAIL PROTECTED] (Peter Samuelson) wrote:
>Yes, report it to them. Also -- as the message that gets appended to
>all list messages says -- read the FAQ at http://www.tux.org/lkml/ .
Thanks. I always like to look at the FAQs and archives before I jump
into a list.
-Mike
p.s. I like to keep newsgroup discussions in the newsgroups,
but if you do want to send email, delete the "X".
------------------------------
From: Francesco Giacomini <[EMAIL PROTECTED]>
Subject: problem with a PCI device config space
Date: Sat, 27 Mar 1999 18:06:32 +0100
Hello.
I have a problem with a PCI card I have installed on my PC, a dual PII: often,
some time after the boot, the PCI confiuration space of the card is "reset",
i.e. almost all the fields, I think all the writable ones, become zero. When it
happens the problem may appear immediately after the boot or later when, for
example, I login using xdm. And this even without loading the driver for that
card.
Since the card works perfectly under WNT I would think the problem is on the
Linux side. I use the 2.0.36 version of the kernel for SMPs. I have never seen
the problem with the UNI-processor version, but I may have not waited enough to
see it.
Following I have included the output of the scanpci command in what I assume is
a normal situation and in an abnormal one. The device in question has vendor id
0x11c8 and device id 0x0658.
=============== normal situation ===========================
PCI says configuration type 1
PCI probing configuration type 1
Probing for devices on PCI bus 0:
pci bus 0x0 cardnum 0x00 function 0x0000: vendor 0x8086 device 0x7180
Intel Device unknown
STATUS 0x2290 COMMAND 0x0106
CLASS 0x06 0x00 0x00 REVISION 0x03
BIST 0x00 HEADER 0x00 LATENCY 0x20 CACHE 0x00
BASE0 0xf8000008 addr 0xf8000000 MEM
pci bus 0x0 cardnum 0x01 function 0x0000: vendor 0x8086 device 0x7181
Intel Device unknown
STATUS 0x02a0 COMMAND 0x000f
CLASS 0x06 0x04 0x00 REVISION 0x03
BIST 0x00 HEADER 0x01 LATENCY 0x60 CACHE 0x00
BASE2 0x40010100 addr 0x40010100 MEM
BASE3 0x22a0e0e0 addr 0x22a0e0e0 MEM
BASE4 0xf6f0f6f0 addr 0xf6f0f6f0 MEM
BASE5 0xf5f0f500 addr 0xf5f0f500 MEM
MAX_LAT 0x00 MIN_GNT 0x0c INT_PIN 0x00 INT_LINE 0x00
pci bus 0x0 cardnum 0x02 function 0x0000: vendor 0x8086 device 0x7110
Intel 82371AB PIIX4 ISA
STATUS 0x0280 COMMAND 0x000f
CLASS 0x06 0x01 0x00 REVISION 0x01
BIST 0x00 HEADER 0x80 LATENCY 0x00 CACHE 0x00
pci bus 0x0 cardnum 0x02 function 0x0001: vendor 0x8086 device 0x7111
Intel 82371AB PIIX4 IDE
STATUS 0x0280 COMMAND 0x0005
CLASS 0x01 0x01 0x80 REVISION 0x01
BIST 0x00 HEADER 0x00 LATENCY 0x40 CACHE 0x00
BASE4 0x0000fcb1 addr 0x0000fcb0 I/O
BYTE_0 0x07 BYTE_1 0xa3 BYTE_2 0x03 BYTE_3 0xa3
pci bus 0x0 cardnum 0x02 function 0x0002: vendor 0x8086 device 0x7112
Intel 82371AB PIIX4 USB
STATUS 0x0280 COMMAND 0x0005
CLASS 0x0c 0x03 0x00 REVISION 0x01
BIST 0x00 HEADER 0x00 LATENCY 0x40 CACHE 0x00
BASE4 0x0000fce1 addr 0x0000fce0 I/O
MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x04 INT_LINE 0x09
pci bus 0x0 cardnum 0x02 function 0x0003: vendor 0x8086 device 0x7113
Intel 82371AB PIIX4 ACPI
STATUS 0x0280 COMMAND 0x0003
CLASS 0x06 0x80 0x00 REVISION 0x01
BYTE_0 0x01 BYTE_1 0x80 BYTE_2 0x00 BYTE_3 0x00
pci bus 0x0 cardnum 0x03 function 0x0000: vendor 0x8086 device 0x1229
Intel 82557 10/100MBit network controller
STATUS 0x0280 COMMAND 0x0007
CLASS 0x02 0x00 0x00 REVISION 0x02
BIST 0x00 HEADER 0x00 LATENCY 0x42 CACHE 0x00
BASE0 0xfecf7008 addr 0xfecf7000 MEM
BASE1 0x0000fcc1 addr 0x0000fcc0 I/O
BASE2 0xfed00000 addr 0xfed00000 MEM
MAX_LAT 0x38 MIN_GNT 0x08 INT_PIN 0x01 INT_LINE 0x09
pci bus 0x0 cardnum 0x0f function 0x0000: vendor 0x11c8 device 0x0658
Device unknown
STATUS 0x02c0 COMMAND 0x0016
CLASS 0x06 0x80 0x00 REVISION 0x03
BIST 0x00 HEADER 0x00 LATENCY 0x40 CACHE 0x08
BASE0 0xfecf8000 addr 0xfecf8000 MEM
BASE1 0xfd000000 addr 0xfd000000 MEM
BASE2 0xf7000008 addr 0xf7000000 MEM
MAX_LAT 0x00 MIN_GNT 0x04 INT_PIN 0x01 INT_LINE 0x09
Probing for devices on PCI bus 1:
pci bus 0x1 cardnum 0x00 function 0x0000: vendor 0x1002 device 0x4742
ATI Mach64 GB
STATUS 0x0290 COMMAND 0x0087
CLASS 0x03 0x00 0x00 REVISION 0x5c
BIST 0x00 HEADER 0x00 LATENCY 0x42 CACHE 0x08
APBASE 0xf5000008 addr 0xf5000000
BLOCKIO 0x0000e801 addr 0x0000e800
MAX_LAT 0x00 MIN_GNT 0x08 INT_PIN 0x00 INT_LINE 0xff
SPARSEIO 0x2ec Block IO enabled Disable 0x46E8
PCI probing configuration type 2
================= abnormal situation ====================
PCI says configuration type 1
PCI probing configuration type 1
Probing for devices on PCI bus 0:
pci bus 0x0 cardnum 0x00 function 0x0000: vendor 0x8086 device 0x7180
Intel Device unknown
STATUS 0x6290 COMMAND 0x0106
CLASS 0x06 0x00 0x00 REVISION 0x03
BIST 0x00 HEADER 0x00 LATENCY 0x20 CACHE 0x00
BASE0 0xf8000008 addr 0xf8000000 MEM
pci bus 0x0 cardnum 0x01 function 0x0000: vendor 0x8086 device 0x7181
Intel Device unknown
STATUS 0x02a0 COMMAND 0x000f
CLASS 0x06 0x04 0x00 REVISION 0x03
BIST 0x00 HEADER 0x01 LATENCY 0x60 CACHE 0x00
BASE2 0x40010100 addr 0x40010100 MEM
BASE3 0x22a0e0e0 addr 0x22a0e0e0 MEM
BASE4 0xf6f0f6f0 addr 0xf6f0f6f0 MEM
BASE5 0xf5f0f500 addr 0xf5f0f500 MEM
MAX_LAT 0x00 MIN_GNT 0x0c INT_PIN 0x00 INT_LINE 0x00
pci bus 0x0 cardnum 0x02 function 0x0000: vendor 0x8086 device 0x7110
Intel 82371AB PIIX4 ISA
STATUS 0x0280 COMMAND 0x000f
CLASS 0x06 0x01 0x00 REVISION 0x01
BIST 0x00 HEADER 0x80 LATENCY 0x00 CACHE 0x00
pci bus 0x0 cardnum 0x02 function 0x0001: vendor 0x8086 device 0x7111
Intel 82371AB PIIX4 IDE
STATUS 0x0280 COMMAND 0x0005
CLASS 0x01 0x01 0x80 REVISION 0x01
BIST 0x00 HEADER 0x00 LATENCY 0x40 CACHE 0x00
BASE4 0x0000fcb1 addr 0x0000fcb0 I/O
BYTE_0 0x07 BYTE_1 0xa3 BYTE_2 0x03 BYTE_3 0xa3
pci bus 0x0 cardnum 0x02 function 0x0002: vendor 0x8086 device 0x7112
Intel 82371AB PIIX4 USB
STATUS 0x0280 COMMAND 0x0005
CLASS 0x0c 0x03 0x00 REVISION 0x01
BIST 0x00 HEADER 0x00 LATENCY 0x40 CACHE 0x00
BASE4 0x0000fce1 addr 0x0000fce0 I/O
MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x04 INT_LINE 0x09
pci bus 0x0 cardnum 0x02 function 0x0003: vendor 0x8086 device 0x7113
Intel 82371AB PIIX4 ACPI
STATUS 0x0280 COMMAND 0x0003
CLASS 0x06 0x80 0x00 REVISION 0x01
BYTE_0 0x01 BYTE_1 0x80 BYTE_2 0x00 BYTE_3 0x00
pci bus 0x0 cardnum 0x03 function 0x0000: vendor 0x8086 device 0x1229
Intel 82557 10/100MBit network controller
STATUS 0x0280 COMMAND 0x0007
CLASS 0x02 0x00 0x00 REVISION 0x02
BIST 0x00 HEADER 0x00 LATENCY 0x42 CACHE 0x00
BASE0 0xfecf7008 addr 0xfecf7000 MEM
BASE1 0x0000fcc1 addr 0x0000fcc0 I/O
BASE2 0xfed00000 addr 0xfed00000 MEM
MAX_LAT 0x38 MIN_GNT 0x08 INT_PIN 0x01 INT_LINE 0x09
pci bus 0x0 cardnum 0x0f function 0x0000: vendor 0x11c8 device 0x0658
Device unknown
STATUS 0x02c0 COMMAND 0x0000
CLASS 0x06 0x80 0x00 REVISION 0x03
BASE2 0x00000008 addr 0x00000000 MEM
MAX_LAT 0x00 MIN_GNT 0x04 INT_PIN 0x01 INT_LINE 0x00
Probing for devices on PCI bus 1:
pci bus 0x1 cardnum 0x00 function 0x0000: vendor 0x1002 device 0x4742
ATI Mach64 GB
STATUS 0x0290 COMMAND 0x0087
CLASS 0x03 0x00 0x00 REVISION 0x5c
BIST 0x00 HEADER 0x00 LATENCY 0x42 CACHE 0x08
APBASE 0xf5000008 addr 0xf5000000
BLOCKIO 0x0000e801 addr 0x0000e800
MAX_LAT 0x00 MIN_GNT 0x08 INT_PIN 0x00 INT_LINE 0xff
SPARSEIO 0x2ec Block IO enabled Disable 0x46E8
PCI probing configuration type 2
======================================================================
And this is the diff between the two:
9c9
< STATUS 0x2290 COMMAND 0x0106
---
> STATUS 0x6290 COMMAND 0x0106
65c65
< STATUS 0x02c0 COMMAND 0x0016
---
> STATUS 0x02c0 COMMAND 0x0000
67,71c67,68
< BIST 0x00 HEADER 0x00 LATENCY 0x40 CACHE 0x08
< BASE0 0xfecf8000 addr 0xfecf8000 MEM
< BASE1 0xfd000000 addr 0xfd000000 MEM
< BASE2 0xf7000008 addr 0xf7000000 MEM
< MAX_LAT 0x00 MIN_GNT 0x04 INT_PIN 0x01 INT_LINE 0x09
---
> BASE2 0x00000008 addr 0x00000000 MEM
> MAX_LAT 0x00 MIN_GNT 0x04 INT_PIN 0x01 INT_LINE 0x00
The only difference not concerning the PCI card in question is on line 9 and
concerns the status of the device:
pci bus 0x0 cardnum 0x00 function 0x0000: vendor 0x8086 device 0x7180
which scanpci does not recognize; but doing cat /proc/pci it corresponds to
Bus 0, device 0, function 0:
Host bridge: Intel 440LX - 82443LX PAC Host (rev 3).
The change in the status, if I read correctly the layout of a PCI config
header, is in bit 14 which flips from 0 to 1. Bit 14 is named "Signaled system
error"; I don't know exactly what it means but it does not sound good to me.
I would appreciate if someone could give me a hint on what's going on and, if
possible, on how to solve the problem. Thanks.
Regards, Francesco.
[EMAIL PROTECTED] CERN EP-ATD
http://wwwinfo.cern.ch/~giacomin Tel. +41 22 76 75022
------------------------------
From: [EMAIL PROTECTED] (David T. Blake)
Subject: Re: how do I uninstall gtk+
Date: 27 Mar 1999 09:42:44 -0800
Mark Leung <[EMAIL PROTECTED]> writes:
>Hi, How do I uninstall GTK+? I am trying to install a new version,
>but no programs will recognise the new GTK+ because of the old
>version. Thanks
cd /usr/lib
unalias rm
rm -f libgtk*
rm -f libgdk*
rm -f libglib*
cd /usr/local/lib
rm -f libgtk*
rm -f libgdk*
rm -f libglib*
And cross your fingers you don't break something in a
way you don't know how to fix.
If you are on a redhat system, and you installed gtk RPMs,
upgrading is as simple as getting the new rpms and doing
rpm -Uvh gtk*rpm glib*rpm
--
Dave Blake
[EMAIL PROTECTED]
------------------------------
From: <[EMAIL PROTECTED]>
Subject: SUSE and RH5.1 RPM ?
Date: Sat, 27 Mar 1999 16:43:09 GMT
Would file.rpm that is made for RH5.1
work on SUSE 6.0 ?
I want to install ADA gnat.rpm made
for RH5.1 on SUSE 6.0.
thanks
bob
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.development.system) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Development-System Digest
******************************
