Jan Engelhardt wrote:

On Aug 26 2007 16:54, Zhang Weiwu wrote:

...

[...] Seems the on-board card /was/ eth0, it's getting renamed to eth1 for some reason.

Eh well. What I can think of: you previously had a PCI network card. Since cards on the PCI bus are usually detected before any on-board stuff (rightfully so), eth0 is your PCI card, and eth1 is onboard. SUSE then makes sure this is the case on every boot, even if you remove the PCI one. Does that apply?

By the way: we had the same problem when we upgraded from RHEL4.4 to RHEL4.5. No hardware has been changed during this upgrade. See also [1] for a similar problem. It's a bit more general and not only opensuse related. Th. [1]http://groups.google.com/group/linux.debian.user/browse_thread/thread/653281... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Benji Weber wrote:

[...]

You shouldn't really rely on the ethX numbering remaining the same, they can change at any time.

No, I expect it to be the same when performing an update (as we did) - if an update causes problems like that, something has gone wrong and the distributor did a bad job. An update is not allowed to change any critical system settings. The situation is different when you perform an upgrade, i.e. you install a complete new version of a distribution... Th. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sunday 26 August 2007, Benji Weber wrote:

On 26/08/07, Thomas Hertweck wrote:

...

No, I expect it to be the same when performing an update (as we did) - if an update causes problems like that, something has gone wrong and the distributor did a bad job. An update is not allowed to change any critical system settings. The situation is different when you perform an upgrade, i.e. you install a complete new version of a distribution...

It's not a critical system setting, it may change just on a reboot, if you change nothing...

Not Critical? Who says its not? The bitching about this name change has been loud and long all over the net for every distro that did not add a feature to nail it down. There are a LOT of utilities that depend on static interface names, and not all of them have been fixed to account for this as the OP has quickly found out. This is another of those caviler changes that Linux is so famous for. No warning, no rationale, so solutions until the bitch level gets high. usbfs-->sysfs Screw-you Vmware smfbs-->cifs Screw-you Win98 shares hda-->sda Screw-you 16partitions YOU-->Zmd Screw you entire userbase -- _____________________________________ John Andersen

On Aug 27 2007 23:17, Benji Weber wrote:

There is a feature for static names, just the ethX names are not the static ones.

Says who? There is a __reason__ as to why udev renames it the following way: eth0 renamed to ethxx0 eth1 renamed to ethxx1 ethxx1 renamed to eth0 ethxx0 renamed to eth1 I renames them to ORIGXXN first, so that you _can_ have ethX names the way you want.

I fail to see what your point is, If you want persistent names use the persistent names, if you want non-persistent names use the ethX.

PERSISTENT_NAME in /etc/sysconfig/network/ifcfg-... has been superseded by udev rules in 10.2. Jan -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

If its so so so so critical, you might as well take your time to read /usr/share/doc/packages/sysconfig/README.Persistent_Interface_Names Or hire a system administrator that knows that. Would be important for a system like the one you described. Best regards Marcio On 8/27/07, Thomas Hertweck wrote:

Benji Weber wrote:

...

On 26/08/07, Thomas Hertweck wrote:

...

No, I expect it to be the same when performing an update (as we did) - if an update causes problems like that, something has gone wrong and the distributor did a bad job. An update is not allowed to change any critical system settings.

It's not a critical system setting, it may change just on a reboot, if you change nothing...

You are a funny guy, right? Have you ever worked in an environment where Linux systems are actually used in production (large-scale)? I guess the obvious answer is no, otherwise you would know that these settings are critical. They are not allowed to change during or after a simple update (patch), certainly not in an enterprise version which (by definition) should provide a stable environment. Sorry, but sometimes I can only shake my head when reading these overly naive statements. Geez, it's time to end this thread...

PS: Please do NOT send private copies of list emails. I am reading this mailing list - why do you think I want to receive your emails twice?

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

B) The fact that you get email sent to you as well as the list is to do   with some quirk of the "reply all" system. It means that (perhaps only on   some clients) you have to remember to remove the poster's name from the To   secion and just leave the list address. If you don't notice that or forget, then the sender will get a mail too. Also on some lists (not this list) the list netiquette is to send to both---

On Monday 27 August 2007 17:07, d_garbage wrote: thank goodness most list users don't do that. -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, 27 Aug 2007 23:39:19 +0100, Michael Skiba wrote:

Am Dienstag, 28. August 2007 00:07 schrieb d_garbage:

...

A) Hey, take it easy fella! People only trying to help here, and for free too. If the advice is no good, you could at least say "thanks anyway" and look elsewhere for advice. Uhm.. AFAIK Thomas was someone who gave an advice, not the one who asked a question :)

Greetings Michael

Ah, yes, sorry, bit sleepy here. Yes, read back thought the archive. Heh, anyway, sorry i got that a bit muddled. Wonder what Zhang Weiwu thinks about all this? Are they reading up about static names i wonder? Cheers, David -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Benji Weber wrote:

[...]

My point is this particular setting might just change after a reboot, it might have nothing to do with a patch.

There are persistent names you can rely on, or you can choose to gamble that the ethX names that are transient may remain the same after a reboot or reloading the driver.

You still don't get it. But I don't have time to explain it over and over again. If you don't understand the purpose of an update and why it's important that no settings change during an update, then it's a waste of time anyway. I'll remind you of this thread next time you run YOU and something stops working afterwards... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org