Re: Network cards changed after kernel upgrade in Etch
On Wed, Sep 05, 2007 at 20:25:12 -0300, Eriberto wrote: Hi! I am having problems when I upgrade the Etch in my servers. The NICs designations are changing. For example, in a machine the NIC was eth0 with 2.6.18-4-686 kernel. After the first upgrade, the NIC was renamed to eth1. The same fact occurs with 2.6.21-2 kernel (Etch-backports). What is the cause of this problem? Changed module load order in the new kernels and/or a problem with your /etc/udev/rules.d/z25_persistent-net.rules. You have to make sure that this file has exactly one entry for each NIC in your computer and that the correct MAC address is associated with the each eth* name. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Network Cards
On Fri, Oct 05, 2001 at 08:11:08PM -0400, Wayne Topa wrote: Matthew Sackman([EMAIL PROTECTED]) is reported to have said: Weird! Both of you that replied talk of putting eth0 in /etc/modutils/ I've never done that at all - I just put in /etc/network/interfaces, and it gets loaded and works. Do you really need it in aliases? If so why? Only if you compiled the NIC driver as a module. You probably have it compiled into the kernel. I (we) assumed he had 'not' compiled it into the kernel. My only excuse for that is that is how I do it and he didn't say which method he used. :-( I assumed again, darn it. It's a module. The natsemi module. It loads fine without there being anything relating to eth0 anywhere under /etc/modutils. Weird - I simply never knew this should be there. In fact, come to think of it, on all the boxes I've set up I've never put eth0 in there and I've never had a problem. Any ideas? Matthew -- Matthew Sackman Nottingham, ENGLAND - The contents of this email are intended for the indicated recipient(s) only. This may or may not be indicated in the above email as it is enormously easy to fake email addresses (see the relevant RFCs). For security reasons this email is likely to be gnupg signed. On the other hand it may not be if I forgot to do so. In any case, if you are reading this on a Windows based computer then there was no point in me doing so (provided that I remembered) as your computer is most likely being used by yourself and 2.8 other people at the same time (normally without your consent). No responsibility will be accepted by anyone for any of the contents of this email. So tough. If in doubt, go compile Mozilla.
Re: Network Cards
On Sat, Oct 06, 2001 at 11:00:22AM +0100, Matthew Sackman wrote: | On Fri, Oct 05, 2001 at 08:11:08PM -0400, Wayne Topa wrote: | Matthew Sackman([EMAIL PROTECTED]) is reported to have said: | Weird! Both of you that replied talk of putting eth0 in /etc/modutils/ | | I've never done that at all - I just put in /etc/network/interfaces, | and it gets loaded and works. Do you really need it in aliases? | If so why? | | | Only if you compiled the NIC driver as a module. You probably have it | compiled into the kernel. I (we) assumed he had 'not' compiled it | into the kernel. My only excuse for that is that is how I do it and | he didn't say which method he used. :-( I assumed again, darn it. Yeah, I figured he had a pre-packaged kernel which includes everything as modules so as to minimize the _need_ for recompiling. | It's a module. The natsemi module. It loads fine without there being | anything relating to eth0 anywhere under /etc/modutils. | | Weird - I simply never knew this should be there. In fact, come to | think of it, on all the boxes I've set up I've never put eth0 in there | and I've never had a problem. | | Any ideas? Maybe the kernel is better at identifying the module automagically? If you run 'lsmod' does it show the natsemi module? -D
Re: Network Cards
On Sat, 2001-10-06 at 10:48, dman wrote: On Sat, Oct 06, 2001 at 11:00:22AM +0100, Matthew Sackman wrote: | On Fri, Oct 05, 2001 at 08:11:08PM -0400, Wayne Topa wrote: | Matthew Sackman([EMAIL PROTECTED]) is reported to have said: | Weird! Both of you that replied talk of putting eth0 in /etc/modutils/ | | I've never done that at all - I just put in /etc/network/interfaces, | and it gets loaded and works. Do you really need it in aliases? | If so why? | | | Only if you compiled the NIC driver as a module. You probably have it | compiled into the kernel. I (we) assumed he had 'not' compiled it | into the kernel. My only excuse for that is that is how I do it and | he didn't say which method he used. :-( I assumed again, darn it. Yeah, I figured he had a pre-packaged kernel which includes everything as modules so as to minimize the _need_ for recompiling. | It's a module. The natsemi module. It loads fine without there being | anything relating to eth0 anywhere under /etc/modutils. | | Weird - I simply never knew this should be there. In fact, come to | think of it, on all the boxes I've set up I've never put eth0 in there | and I've never had a problem. | | Any ideas? Maybe the kernel is better at identifying the module automagically? If you run 'lsmod' does it show the natsemi module? Just a guess, but perhaps the module is listed in /etc/modules to load at run time on other machine, therefore not needing an alias in the aliases file. Putting it in the aliases file allows it to be autoloaded when the net is needed IIRC. --mike
Re: Network Cards
Matthew Sackman wrote: --snip-- It's a module. The natsemi module. It loads fine without there being anything relating to eth0 anywhere under /etc/modutils. Weird - I simply never knew this should be there. In fact, come to think of it, on all the boxes I've set up I've never put eth0 in there and I've never had a problem. Any ideas? Matthew I have been following this thread with a modest amount of interest, and it spurred me to do some investigation. Here is what I have found so-far: I have two computers running Debian testing. One has a checkered past, starting off with Stormix, upgraded to Progeny, then upgraded to its current testing status using the apt-get dist-upgrade route. In poking around the /etc/init.d/ directory, I ran across a program called discover, that even has a MAN page! It is an interesting little program that is designed to do some automatic hardware detection at bootup! It even shows up as a separate package in the Debian testing and unstable archives, but is not in the stable archives. The second computer is one that I have just installed a fresh copy of Debian testing upon using the new boot-floppies (the idepci variety), and it DOESN'T have this discover package installed. Evidently, this is not a part of the standard install! Now here comes the interesting part. On the fresh install, I had to use the alias trick to get my NIC to install properly...actually I used the modconf program. On the other (upgraded) computer I never had to add anything, BUT I cannot say when this particular package was introduced. I do have a third computer running Progeny Newton, and it is on there. I strongly suspect it was introduced to my upgraded system when I had Progeny on it. The bottom-line conclusion for me is that the discover package is probably doing some automatic hardware detection and setup for those who have NOT had to use the alias trick to get their cards working! I would appreciate some verification of this conclusion from others. Check out the discover package...it looks interesting, and I haven't heard much ballyhoo about it. This is the first time I have ever noticed its presence on my system(s). Cheers, -Don Spoon-
Re: Network Cards
On Sat, Oct 06, 2001 at 12:58:35PM -0500, Michael Heldebrant wrote: On Sat, 2001-10-06 at 10:48, dman wrote: On Sat, Oct 06, 2001 at 11:00:22AM +0100, Matthew Sackman wrote: | It's a module. The natsemi module. It loads fine without there being | anything relating to eth0 anywhere under /etc/modutils. | | Weird - I simply never knew this should be there. In fact, come to | think of it, on all the boxes I've set up I've never put eth0 in there | and I've never had a problem. | | Any ideas? Maybe the kernel is better at identifying the module automagically? If you run 'lsmod' does it show the natsemi module? Yes, it's shown. Just a guess, but perhaps the module is listed in /etc/modules to load at run time on other machine, therefore not needing an alias in the aliases file. Putting it in the aliases file allows it to be autoloaded when the net is needed IIRC. That would make sense - it is forced loaded at boot from /etc/modules. I generally force load any module that I judge to be crucial (like all the iptables modules and the network cards - I don't leave it up to the kernel autoloader (although that is enabled and works for various FS modules that I occasionally use). Well I guess that's cleared that up then! Cheers, Matthew -- Matthew Sackman Nottingham, ENGLAND - The contents of this email are intended for the indicated recipient(s) only. This may or may not be indicated in the above email as it is enormously easy to fake email addresses (see the relevant RFCs). For security reasons this email is likely to be gnupg signed. On the other hand it may not be if I forgot to do so. In any case, if you are reading this on a Windows based computer then there was no point in me doing so (provided that I remembered) as your computer is most likely being used by yourself and 2.8 other people at the same time (normally without your consent). No responsibility will be accepted by anyone for any of the contents of this email. So tough. If in doubt, go compile Mozilla. pgpaayvm3G6is.pgp Description: PGP signature
Re: Network Cards
On Fri, Oct 05, 2001 at 08:37:48AM -0500, Mike Grover wrote: | Hi all, | I am new to using debian. | I have just finished installing ver 2.2 r3 and was wondering how I | go about setting up network cards? | | I have a ne2000 in the machine, but when I type ifconfig, All | I see is the local loop back interface. It the card PCI or ISA? If it is ISA then add alias eth0 ne to some file in /etc/modutils/ (pick a name that you will remember is your custom stuff, not packaged stuff) and run 'update-modules'. Then edit /etc/network/interfaces and include the config for the interface (ie, ip addres, etc or specify using dhcp). If it is a PCI card, then I don't know the module name but the procedure is the same except for the name of the module. HTH, -D
Re: Network Cards
Mike Grover([EMAIL PROTECTED]) is reported to have said: Hi all, I am new to using debian. I have just finished installing ver 2.2 r3 and was wondering how I go about setting up network cards? I have a ne2000 in the machine, but when I type ifconfig, All I see is the local loop back interface. Add the card to /etc/modultils/aliases If it is a pci card alias eth0 ne2k-pci otherwise alias eth0 ne Edit /etc/network/interfaces to look something like this # automatically added when upgrading auto eth0 iface eth0 inet static address 192.168.1.1 network 192.168.1.0 netmask 255.255.255.0 broadcast 192.168.1.255 Then run /etc/init.d/modutils Truthfully I don't remember if you have to reboot. Its been so long since I have done the above I just don't recall. HTH=Hope This Helps, YMMV=Your Mileage May Vary, HAND=Have A Nice Day -- DOS Tip #2: Add BUGS=OFF to your CONFIG.SYS ___
Re: Network Cards
Weird! Both of you that replied talk of putting eth0 in /etc/modutils/ I've never done that at all - I just put in /etc/network/interfaces, and it gets loaded and works. Do you really need it in aliases? If so why? Thanks, Matthew On Fri, Oct 05, 2001 at 12:16:41PM -0400, dman wrote: On Fri, Oct 05, 2001 at 08:37:48AM -0500, Mike Grover wrote: | Hi all, | I am new to using debian. | I have just finished installing ver 2.2 r3 and was wondering how I | go about setting up network cards? | | I have a ne2000 in the machine, but when I type ifconfig, All | I see is the local loop back interface. It the card PCI or ISA? If it is ISA then add alias eth0 ne to some file in /etc/modutils/ (pick a name that you will remember is your custom stuff, not packaged stuff) and run 'update-modules'. Then edit /etc/network/interfaces and include the config for the interface (ie, ip addres, etc or specify using dhcp). If it is a PCI card, then I don't know the module name but the procedure is the same except for the name of the module. HTH, -D -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Matthew Sackman Nottingham, ENGLAND - The contents of this email are intended for the indicated recipient(s) only. This may or may not be indicated in the above email as it is enormously easy to fake email addresses (see the relevant RFCs). For security reasons this email is likely to be gnupg signed. On the other hand it may not be if I forgot to do so. In any case, if you are reading this on a Windows based computer then there was no point in me doing so (provided that I remembered) as your computer is most likely being used by yourself and 2.8 other people at the same time (normally without your consent). No responsibility will be accepted by anyone for any of the contents of this email. So tough. If in doubt, go compile Mozilla.
Re: Network Cards
On Fri, Oct 05, 2001 at 11:27:38PM +0100, Matthew Sackman wrote: Weird! Both of you that replied talk of putting eth0 in /etc/modutils/ I've never done that at all - I just put in /etc/network/interfaces, and it gets loaded and works. Do you really need it in aliases? If so why? Is the driver compiled into the kernel or as a module? -- Within the limits of equity, everything is to be accomplished through the free and perfectible initiative of man; nothing is to be achieved by law or by force save universal justice. -- Frédéric Bastiat (1801-1850) Rick Pasotto[EMAIL PROTECTED]http://www.niof.net
Re: Network Cards
Matthew Sackman([EMAIL PROTECTED]) is reported to have said: Weird! Both of you that replied talk of putting eth0 in /etc/modutils/ I've never done that at all - I just put in /etc/network/interfaces, and it gets loaded and works. Do you really need it in aliases? If so why? Only if you compiled the NIC driver as a module. You probably have it compiled into the kernel. I (we) assumed he had 'not' compiled it into the kernel. My only excuse for that is that is how I do it and he didn't say which method he used. :-( I assumed again, darn it. -- Build a system that even a fool can use, and only a fool will use it. ___
RE: Network cards
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Saturday, July 29, 2000 1:53 PM To: debian-user@lists.debian.org Subject: Network cards Hello all, I was wondering if someone out there can tell me if there is a difference between the D-Link DE-530 Don't know anything about this one. D-Link DFE-530TX Has a Via Rhine II chipset, works with the via-rhine kernel module. WARNING! The driver does not seem to be SMP-safe! On my dual machine it floods all consoles with errors, on the single CPU ones it works fine. D-Link DFE-530TX+ Uses a _different_ chipset, Realtek I believe. Consequently the module is different, too. Christian -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE5guQxtxWmQklOL8URAiXxAJ0X0dGdzIBTTYWbld9n8WDSfZDYFwCePPKT J4LuXV8JHzbjFh79DbECNsw= =dE6S -END PGP SIGNATURE-
Re: Network Cards
Jay Kelly wrote: I have a quick qestion, I want my nic cards (eth0 and eth1) to keep the setting I configure such as ip, netmask after rebooting. Each time I reboot eth1 dumps all the information I put in the ifconfig setup. How can I get it to store and keep the information for both nic cards? I find on my frozen (potato) installation on a sparc the file /etc/network/interfaces, described in `man interfaces`.
Re: Network Cards
On Fri, May 26, 2000 at 01:42:35PM -0500, Bolan Meek wrote
Jay Kelly wrote:
I have a quick qestion, I want my nic cards (eth0 and eth1) to keep the
setting I configure such as ip, netmask after rebooting. Each time I reboot
eth1 dumps all the information I put in the ifconfig setup. How can I get it
to store and keep the information for both nic cards?
I find on my frozen (potato) installation on a sparc the file
/etc/network/interfaces, described in `man interfaces`.
On slink it's /etc/init.d/network, which is set up nicely
IFF you identify and configure your network card during
installation. A fairly standard example is attached;
if you don't have one customise this one then place it
in /etc/init.d and run
# chmod a+rx /etc/init.d/network
# update-rc.d network start 40 S .
John P.
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.mdt.net.au/~john Debian Linux admin support:technical services
#! /bin/sh
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
IPADDR=192.168.113.106
NETMASK=255.255.255.0
NETWORK=192.168.113.0
BROADCAST=192.168.113.255
GATEWAY=192.168.113.110
ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
route add -net ${NETWORK}
[ ${GATEWAY} ] route add default gw ${GATEWAY} metric 1
RE: Network Cards
If I have my ip addresses set in the /etc/init.d/network (for slink), then upgrade to potato, do I need to redo the ifconfig but in /etc/network/interface. I use to run slink I configures my cards in the /etc/init.d/network then I upgraded to potato. Now if I look in the /etc/network/interfaces file its empty. But when I do a ifconfig I can see both card. Will I need to transfer all the ip information over? Jay -Original Message- From: John Pearson [mailto:[EMAIL PROTECTED] Sent: Friday, May 26, 2000 5:35 PM To: debian-user@lists.debian.org Subject: Re: Network Cards On Fri, May 26, 2000 at 01:42:35PM -0500, Bolan Meek wrote Jay Kelly wrote: I have a quick qestion, I want my nic cards (eth0 and eth1) to keep the setting I configure such as ip, netmask after rebooting. Each time I reboot eth1 dumps all the information I put in the ifconfig setup. How can I get it to store and keep the information for both nic cards? I find on my frozen (potato) installation on a sparc the file /etc/network/interfaces, described in `man interfaces`. On slink it's /etc/init.d/network, which is set up nicely IFF you identify and configure your network card during installation. A fairly standard example is attached; if you don't have one customise this one then place it in /etc/init.d and run # chmod a+rx /etc/init.d/network # update-rc.d network start 40 S . John P. -- [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.mdt.net.au/~john Debian Linux admin support:technical services
Re: Network Cards
* Jay Kelly in RE: Network Cards dated 2000/05/26 17:52 wrote: If I have my ip addresses set in the /etc/init.d/network (for slink), then upgrade to potato, do I need to redo the ifconfig but in /etc/network/interface. I use to run slink I configures my cards in the /etc/init.d/network then I upgraded to potato. Now if I look in the /etc/network/interfaces file its empty. But when I do a ifconfig I can see both card. Will I need to transfer all the ip information over? No you don't need to redo your network settings in /etc/network/interfaces. Everything will work as it did before but when you are feeling up to it there is nothing stopping you from changing to the new setup. -- Ashley Clark pgpAndzaG4Lg6.pgp Description: PGP signature
Re: Network cards.
Just go for an Adaptec. You will have problems that you never dreamt of. The topic was about ethernet cards! paul
Re: Network cards.
On Sun, 13 Dec 1998, wb2oyc wrote: : : Just go for an Adaptec. You will have problems that you never dreamt : of. : The topic was about ethernet cards! http://www.adaptec.com/products/index.html#fastethernet -- Nathan Norman MidcoNet 410 South Phillips Avenue Sioux Falls, SD mailto:[EMAIL PROTECTED] http://www.midco.net finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9)
Re: Network cards.
http://www.adaptec.com/products/index.html#fastethernet Nathan, oopps, guess I missed that myself! paul
Re: Network cards.
On 12 Dec 1998 13:38:56 -0800, you wrote: I believe Donald Becker [EMAIL PROTECTED] said that he believes that every 10/100 Mbps ethernet card on the market is now supported for Linux. :-) He believes. Though he knows that later Adaptec ANA6911A cards don't work. You have to be pretty unlucky to find a card that doesn't work Just go for an Adaptec. You will have problems that you never dreamt of. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber |Questions are the | Mailadresse im Header Karlsruhe, Germany | Beginning of Wisdom | Fon: *49 721 966 32 15 Nordisch by Nature | Lt. Worf, TNG Rightful Heir | Fax: *49 721 966 31 29
Re: Network cards.
Some PCI NICs may be troublesome, but you can count on most older 3Com's or Intel. Personally, I have several 3Com cards, and a few LinkSys that are NE2000 clones, and none of them have failed to work with any Linux. I'd check out the source of your rumor. Sounds like crap to me! Paul
Re: Network cards.
Brent McMillan [EMAIL PROTECTED] writes: I'll be setting up a network between my linux box and 2 other machines for a cable modem. I hear that there are some network cards that just don't work for linux. Crazy I know, but that's the rumour. Does any one know off any cards I should avoid or any they would recomend? Thanks. I believe Donald Becker [EMAIL PROTECTED] said that he believes that every 10/100 Mbps ethernet card on the market is now supported for Linux. :-) You have to be pretty unlucky to find a card that doesn't work. I usually just buy cheap 10 Mbps NE2000 clones. It depends on your application. Cheers, - Jim
Re: Network cards.
3c501 cards should not be used anywhere, of course. I've heard some bad things about ne2000 clones, but have used several from different manufacturers and never had a problem. Performance isn't great, but considering the price, they aren't all that bad for a small network. Of course, if you get some recently-introduced cards, there might be a wait until somebody writes a driver. The Ethernet-HOWTO has some good advice in this area. Bob On Fri, 11 Dec 1998, Brent McMillan wrote: I'll be setting up a network between my linux box and 2 other machines for a cable modem. I hear that there are some network cards that just don't work for linux. Crazy I know, but that's the rumour. Does any one know off any cards I should avoid or any they would recomend? Thanks. Brent. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null Bob Nielsen Internet: [EMAIL PROTECTED] Tucson, AZ AMPRnet: [EMAIL PROTECTED] DM42nh http://www.primenet.com/~nielsen
RE: Network cards.
On 11-Dec-98 Brent McMillan wrote: I'll be setting up a network between my linux box and 2 other machines for a cable modem. I hear that there are some network cards that just don't work for linux. Crazy I know, but that's the rumour. Does any one know off any cards I should avoid or any they would recomend? Thanks. Brent. I am a big fan of the dec tulip (100mbit) chipset. The soho network in a box never worked for me -- I took it back.
Re: Network cards.
Just make sure you don't buy a WinNIC! - just kidding, couldn't resist, sorry. http://metalab.unc.edu/LDP/HOWTO/Hardware-HOWTO.html will tell you what (not) to get. HTH, G.S. ---Brent McMillan [EMAIL PROTECTED] wrote: I'll be setting up a network between my linux box and 2 other machines for a cable modem. I hear that there are some network cards that just don't work for linux. Crazy I know, but that's the rumour. Does any one know off any cards I should avoid or any they would recomend? Thanks. Brent. == -BEGIN GEEK CODE BLOCK- Version: 3.1 GCM/IT d-(+) s:++: a30 C++$ UL++$ P+ L++ E- W++ N++ o+ K? w--(---) O- M- V- PS PE(+) Y+ PGP(-) t+ 5 X+ R- tv(+) b+ DI++(+++) D(++) G e++ h r+++ y+++ --END GEEK CODE BLOCK-- _ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com
It could happen to you (was Re: network cards and POST failures)
Hello everyone, at last, the strange problems I was having with my Linux box at reboot time is solved. I followed Donald Becker's recommendation about putting /sbin/ifconfig eth0 down at the very end of the reboot script and this fixes everything. Now everything is crystal-clear to me. I agree with Bruce that the Debian distribution should take care of shutting down Ethernet devices before rebooting. As an example, I was getting this error in my desktop machine everytime I rebooted the Linux box: eth0: Bus master arbitration failure, status 88f2 Since my desktop machine is not a production machine (I am the only one that uses it) and that I first saw this error after a kernel upgrade, I did not waste much time finding the cause. Each time I got that error I just cycled power to the computer and everything worked fine after that. Well, the Ethernet card here is also a NE2100 compatible (it's a BocaLAN Card, using the lance.c driver) and it does DMA. After I put /sbin/ifconfig eth0 down at the bottom of /etc/init.d/reboot the problem went away. Beware!!! This problem could happen to you and you'll waste hours trying to find what's wrong. Regards, Eloy.- P.S. Somebody may want to post this to debian-devel@lists.debian.org because I have no posting priviledges there. At 12:46 PM 12/2/96 PST, Bruce Perens wrote: Here's what Donald Becker had to say about Eloy Paris' problem in which a network card caused RAM POST failures. This is perhaps something that we should take care of in the shutdown scripts after NFS partitions are unmounted and daemons are killed. We can use the output of netstat -i to figure out what interfaces to shut down. From: Donald Becker [EMAIL PROTECTED] On Sat, 30 Nov 1996, Bruce Perens wrote: Eloy Paris [EMAIL PROTECTED] has a DEC PC that fails the RAM POST only when the Boca PCnet32 card is present and a recent Linux kernel has just shut down. My uninformed speculation is that the card could be doing wild DMA, and I'm wondering if there's any special step that should be taken to shut down this card before rebooting. That's a common BIOS bug. The warm boot code should disable the bus-master capability on all cards. What is happening is that the card is continuing to receive and store packets into memory. The work-around, which we must use here as well, is to put /sbin/ifconfig eth0 down /sbin/ifconfig eth1 down /sbin/ifconfig eth2 down /sbin/ifconfig eth3 down in you shutdown script. (Usually /etc/rc.d/rc.6, but Redhat is different.) This will disable the cards. -- Eloy A. Paris Information Technology Rockwell Automation de Venezuela Telephone: +58-2-9432311 Fax: +58-2-9430323 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
