On 29/09/09 16:26, phanisvara das wrote:

"this program" refers to openSUSE, right? instead of "ipconfig" the program is called "ifconfig" here. you call it from a command prompt, as root.

ifconfig should not be used. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 29/09/09 16:42, phanisvara das wrote:

please excuse my ignorance, but why? i'm quite happy with it: finding out what's going on with my network configuration, shutting up & down devices. what's wrong with that?

It will go away at some point in the future, is deprecated. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 29/09/09 16:55, James D. Parra wrote:

What command will take its place?

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

Just hate to see an efficient tool be dropped.

why not write a script that translates the result? Most of the info is available in the output of ip, and the rest can probably be gotten elsewhere.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

If you have tool that works and delivers relevant info, why abandon it just write scripts to do what has already been done? Why reinvent the wheel?

Anyhow, I don't want this be a flame war. I only hope 'ifconfig' sticks around for a while. A long while.

I asked earlier if ifconfig uses depricated APIs. Nobody knows, or nobody has answered. If it does, then when the depricated APIs are finally actually removed from the kernel, then ifconfig will break. Why reinvent the wheel? Because the wheel no longer functions. (in this case) If it doesn't use depricated APIs, then there is nothing to stop you from grabbing the source and compiling it yourself once it is removed from the distribution. ifconfig (part of net-tools) hasn't been actively developed since 2001, ip (from iproute2) has been available since the 2.4.x series kernels, so I'd suspect that ifconfig does make use of depricated APIs. So, my suggestion: in your new scripts, make use of the output of ip, and for your old scripts, either update them, or write that translation script that I mentioned earlier. Just trying to help. I'd even actually write it for you if I weren't at work forced to use a winblows box.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wed, 2009-09-30 at 11:57 +1300, Philip Dowie wrote:

...

If you have tool that works and delivers relevant info, why abandon it just write scripts to do what has already been done? Why reinvent the wheel?

An attitude that would freeze progress. And ifconfig, ip, et al... are reading their information from /proc or /sys anyway. If you want to write solid utilities, or scripts, you don't frog around trying to parse the [variable] output of some utility you just go straight to the source.

...

Anyhow, I don't want this be a flame war. I only hope 'ifconfig' sticks around for a while. A long while. I asked earlier if ifconfig uses depricated APIs. Nobody knows, or nobody has answered. If it does, then when the depricated APIs are finally actually removed from the kernel, then ifconfig will break.

I don't know about "deprecated" I know what I've been told, and read, but people more knowledgeable than me.

If it doesn't use depricated APIs, then there is nothing to stop you from grabbing the source and compiling it yourself

Somehow that is easier than just using/learning the newer tool?

once it is removed from the distribution. ifconfig (part of net-tools) hasn't been actively developed since 2001, ip (from iproute2) has been available since the 2.4.x series kernels, so I'd suspect that ifconfig does make use of depricated APIs.

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

On Wednesday 30 September 2009 12:43:37 pm kanenas@hawaii.rr.com wrote:

Actually the question should be reversed. If ip was to do one better (it is, no?) than ifconfig, why doesn't it?

far as i understand, ip can do much more than ifconfig, re, configuring the interfaces. (didn't get into ip yet, have to do that eventually.)

why is someone encouraged to reinvent the wheel if the current level of functionality is desired?

not reinvent the wheel; make a wheel with gear shift. would probably not be too difficult to add an option that displays info the same way ifconfig does, for backwards compatibility. would have to talk to the ip developers about that.

is the kde4 mentality taking over everything?

or is the "don't move from KDE 3" mentality coming up again? seems like anything new is drawing flak these days... -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wednesday 30 September 2009 01:57:42 pm Peter Nikolic wrote:

No it's the why put up with crap that clearly does not work when the previous stuff worked perfectly

i don't have the time now, but will get into ip as soon as i can. i haven't read anywhere that it "clearly does not work." what i've seen so far is that it displays information a little different. what i've heard is that you can do more with it than with ifconfig. until i find out otherwise, i assume that is correct. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wednesday 30 September 2009 09:53:09 am Philip Dowie wrote:

If we keep maintaining old stuff, then pretty soon Linux will be like Windows: Having code that is 20+ years old because people simply don't want to change.

NOBODY said ANYTHING like that. The *one* thing that pisses us oldtimers off is that almost anything coming out as *new* AND as a *replacement* of something we are used to ALWAYS seems to have about half the features the *old* goat has. why is this so hard to understand? why can't a *replacement* come out with *all* of the old features AND ONLY AFTER THAT add whatever new whatchamacallit the developer wants? in real world engineering this is a given. why do coders (or whoever pushes forth *new* crap) think this is immaterial? d. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thu, 2009-10-01 at 09:36 +0200, Anders Johansson wrote:

On Thursday 01 October 2009 09:25:03 kanenas@hawaii.rr.com wrote:

...

why can't a *replacement* come out with *all* of the old features AND ONLY AFTER THAT add whatever new whatchamacallit the developer wants? in real world engineering this is a given. Ah yes, that's why on all new cars you always have the option to start them with a hand crank - after all, that was a feature that was ubiquitous in older cars, and in real world engineering, features are never dropped

I own a 1919 Model-T Ford depot hack - and I have the steel rod in my wrist to prove it. Some technologies need to die. But it does give me something in common with Wolverine. While ifconfig has never tossed me ten feet and broken my arm... I don't get the argument about less features - "ip" is *way* for featureful [word?] than ifconfig.

...

why do coders (or whoever pushes forth *new* crap) think this is immaterial? What is it you can do in ifconfig that you can't do in ip?

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

On Thursday 01 October 2009 22:10:54 Mike McMullin wrote:

Nifty, however in piston driven automobiles, there still exists the crankshaft, the hand crank was replaced by an electric crank (Starter motor?). ;)

Exactly my point. HOW DARE THEY!!!"§!"§!"!!!!!!! Don't they realize that IF MY BATTERY DIES I WON'T BE ABLE TO START MY CAR This is a simple operation that used to work in EVERY CAR, and now they expect you to PUSH your car until you get somewhere where they MIGHT have a new BATTERY. THIS IS SO OBVIOUS PEOPLE!!!!!!! Why do engineers have to CHANGE WHAT WORKS! Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thursday 01 October 2009 22:45:01 Mike McMullin wrote:

...

Don't they realize that IF MY BATTERY DIES I WON'T BE ABLE TO START MY CAR

Only true if you have an automatic transmission, you can actually push start a manual, automatic as well, but not by hand, unlike the manual.

..not push start by hand....what do you push with then?

Because they liked "New Coke"?

New coke was marketing, not engineering. Coke itself was engineering, when they wanted the same taste but without the cocaine

Which is to say, not all change actually makes sense, or dollars in that case.

How about understanding my point: functionality improves, and sometimes it's worth throwing out the old way of doing things In the case of ifconfig/ip, the comment about inexperienced users just makes me laugh. Those users don't use command lines at all, so it's just a non- argument. In fact, linux frequently gets made fun of by users of MS and Apple for forcing people to use the command line (which of course is not true - there are GUI applications that present the exact same info) The semi-experienced people who do at times use the command line, well, they will have to learn something new. It happens from time to time, it's not the first time and it won't be the last. The experienced people appreciate ip, because it allows them to do much more. Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Fri, 2009-10-02 at 10:05 +1300, Philip Dowie wrote:

...

On Thu, 2009-10-01 at 22:23 +0200, Anders Johansson wrote:

...

On Thursday 01 October 2009 22:10:54 Mike McMullin wrote:

...

Nifty, however in piston driven automobiles, there still exists the crankshaft, the hand crank was replaced by an electric crank (Starter motor?). ;) Exactly my point. HOW DARE THEY!!!"§!"§!"!!!!!!! Don't they realize that IF MY BATTERY DIES I WON'T BE ABLE TO START MY CAR Only true if you have an automatic transmission, you can actually push start a manual, automatic as well, but not by hand, unlike the manual. how fast do you gotta get an automatic before you can push start it?

And if your battery is really dead and you have electronic ignition and computer controlled fuel injection... good luck push starting that thing, automatic or manual. Or if it is a hybrid... Also - as someone who owns a crank start car - crank starting a modern high-compression engine, assuming you physically could crank it, would probably qualify as a suicide attempt. So it is a pretty good metaphor; new techniques and technologies sometimes really do mean the old ones should go away [doesn't mean some masochist can't still emulate them]. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Also - as someone who owns a crank start car - crank starting a modern high-compression engine, assuming you physically could crank it, would probably qualify as a suicide attempt.

surely any hand crank would freewheel in the same way motorcycle kickstarters do... (acknolwedged old ones didn't, but......) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Anders Johansson wrote:

On Thursday 01 October 2009 22:10:54 Mike McMullin wrote:

...

Nifty, however in piston driven automobiles, there still exists the crankshaft, the hand crank was replaced by an electric crank (Starter motor?). ;)

Exactly my point. HOW DARE THEY!!!"§!"§!"!!!!!!!

Don't they realize that IF MY BATTERY DIES I WON'T BE ABLE TO START MY CAR

This is a simple operation that used to work in EVERY CAR, and now they expect you to PUSH your car until you get somewhere where they MIGHT have a new BATTERY.

THIS IS SO OBVIOUS PEOPLE!!!!!!! Why do engineers have to CHANGE WHAT WORKS!

Anders

Actually, I can start all of my vehicles without the starter. I do need a tiny amount of battery juice to feed the alternator, or else no sparkies, but I don't need the starter nor a tiny fraction of the battery power needed to operate a starter. As common as automatic transmissions are, they are in no way mandatory nor desirable in all situations. So, I don't have any. Sure, internal combustion itself is probably going away eventually. So what? At that time so will transmissions, both automatic and standard , and starters of any form, so it will be moot and I will not have any reason to want to keep my manual transmission on a device that doesn't even need any such thing as a transmission. The point is we are dealing within a given context, that being unix-like-systems. There are any number of ways to get computing tasks done and linux and other unix-like systems are by far just the beginning, The first charming retarded baby steps. And on a unix-like system, for better or for worse, it has been long established that one will find ifconfig. You dont' have to like it, you just have to realize it. Progress? Yeah ok. ip is nice. But in the world of supporting a lot of servers doing actual work for companies that rightly have no patience for dinking around, common denominators are nicer. Common denominators mean your staff spends more time producing and less time reading up and performing experiments on the latest replacement for some command, or reading up and performing experiments on this *nix's equivalent of some command that that other *nix has. Common denominators mean fewer mistakes, and in IT as with many other fields, mistakes can be company-killing expensive. ifconfig exists in almost exactly the same form on probably every single unix-like os. It's on all the old commercial versions of unix that didn't ship with compilers by default and ran so reliably that they are still in production long after the manufacturers have gone away, all the way up to it's on my new Palm Pre. Many of those other systems do not have either ip, nor a compiler to compile it, nor any such thing as /proc or /sys, and some have /proc but it has none of the extra and poorly thought-out stuff that linux has in /proc, which linux is now finally realizing and trying to move into /sys... But they all have ifconfig, and ifconfig works almost exactly the same way on all of them at least for common and simple things like simply reading the status of the interfaces. It's nice that new systems have ip. It's nice that ip may be a better designed way of doing things. It's true that, if you happen to have the luxury of only having to deal with new systems, and only linux, and you will be off on some other adventure and unimpeachable when your lack of foresight hurts your customer in a couple of years, it's probably better to use the newer better tools across the board. None of that grants the moral position to say that therefore no one could possibly have a need for, or be better served by, ifconfig, or any other traditional utility that has been in use a long time and is common across a wide range of platforms. Anyone who says "oh well any server that old should just be replaced with a new one running linux!" (without knowing anything about such servers or what they do or why or for whom etc... or even if the server is old at all instead of say, a brand new and superior freebsd system) automatically and immediately removes themselves from the discussion on grounds of ignorance, incompetency and lack of basic wisdom or plain sense. -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thursday 01 October 2009 13:45:54 Philipp Thomas wrote:

* Anders Johansson (ajohansson@suse.de) [20091001 09:37]:

...

As far as I can see, ip has all the features of ifconfig, and quite a bit more.

Yes, but ip's documentation is mediocre at best.

The man page is a bit BNF heavy, and light on descriptions and explanations, yes Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Anders Johansson wrote:

What is it you can do in ifconfig that you can't do in ip? As far as I can see, ip has all the features of ifconfig, and quite a bit more.

Running the ifconfig command with no parameters shows a lot of info about the various interfaces. I don't see something similar with ip. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thu, 2009-10-01 at 08:30 -0400, James Knott wrote:

Anders Johansson wrote:

...

What is it you can do in ifconfig that you can't do in ip? As far as I can see, ip has all the features of ifconfig, and quite a bit more.

Running the ifconfig command with no parameters shows a lot of info about the various interfaces. I don't see something similar with ip.

? ip addr ip -statistics link You must specify an option to ip ifconfig ip addr and "ip addr" is still one character less typing! :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wednesday 30 September 2009 09:36:49 pm Anders Johansson wrote:

On Thursday 01 October 2009 09:25:03 kanenas@hawaii.rr.com wrote:

...

why can't a *replacement* come out with *all* of the old features AND ONLY AFTER THAT add whatever new whatchamacallit the developer wants?

in real world engineering this is a given.

Ah yes, that's why on all new cars you always have the option to start them with a hand crank - after all, that was a feature that was ubiquitous in older cars, and in real world engineering, features are never dropped

my '74 850 Norton Commando and my '67 750 G15 both have a kickstarter *only*. (ok, not exactly a hand crank, but close enough:)) Yes, they are dinosaurs, but they still go around cornrers better than 95% of the bikes on the road. I do hope it does not take 40+ years for 5% of the software to surpass the "hand cranked" versions first punched on paper tape...

...

why do coders (or whoever pushes forth *new* crap) think this is immaterial?

What is it you can do in ifconfig that you can't do in ip? As far as I can see, ip has all the features of ifconfig, and quite a bit more.

I think you're ranting against the wrong software here

Anders

I do admit it is a bit of a rant, but *not* at ip. my comments were a response to a general complaint about resistance to "new" software. And I *do* maintain that too much of new software considers too many features of existing software as handcranks, drops them and comes out incomplete. Let's take ip for example. I would hazard a guess that only about a third of the readers of this forum can write a script in a couple of minutes to add the missing functionality as compared to the ifconfig output . I put myself on the other third, the one where the script would take a number of false starts and a couple of days to complete. And finally there is the third that has not a clue about scripts...linucs has evolved.... In this case it would take very little effort from one of the gurus to make the grumpy third or two thirds smile if ip outputs at least the same info as ifconfig on a simple call. Probably it would take less time than arguing about it. d. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

...

In this case it would take very little effort from one of the gurus to make the grumpy third or two thirds smile

Grumpy, and vocal, 2 - 5%

if ip outputs at least the same info as

...

ifconfig on a simple call. Probably it would take less time than arguing about it.

Do not script around ifconfig. It has been deprecated - right there in the man page - for almost a decade. In fact, don't script around any utilities at all. If you need to script just read /sys - those are just files, way easier to script with. Want the number of collisions from eth0 - cat /sys/class/net/eth0/statistics/collisions 0

In fact, since ip does nothing without parameters, simply having it default to ifconfig output (character for character identical) would make sense.

"ip" is not "ifconfig"

The backbone of 'Nix systems is small fast command line utilities that can be aggregated, built upon, and invoked from everywhere.

I just don't except that "small fast command line utilities" is the backbone of anything. A very solid argument could be made that UNIX is great despite being burdened with a shattered train wreck of inconsistent utilities. $ ls /usr/bin | wc -l 3,350 For crying out loud! Just cause you know it doesn't make is smart, efficient, or elegant. There is nothing what-so-ever "elegant" about the UNIX shell; you can do a lot of cool stuff, that doesn't mean it isn't a mess.

When people start replacing these with "new and improved" utilities with not so much as a thought to backward compatibility they break things in places they don't even know about.

ifconfig still works! Even after people have been warned for almost a decade.

The vast majority of use of ifconfig (and ipconfig in windows) is just to get a fast snapshot of the interfaces, their state, IPs Gateways, etc.

The great majority of users will just right-click on Network Manager. If you know to go run /sbin/ifconfig then you are plenty smart enough to go run "ip addr" instead.

The naked command should do this rather than showing not enough help to be helpful.

I go back to my if-you-already-know-enough... this doesn't matter. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Adam Tauno Williams wrote:

Do not script around ifconfig. It has been deprecated - right there in the man page - for almost a decade. In fact, don't script around any utilities at all.

The real problem is something often termed the "QWERTY" effect (after the keyboard layout that was specifically designed to slow keyboard input down because the original mechanical typewriter kept jamming because the operators typed too fast for the mechanism). Something is not adopted (even though it may be better), because the cost of changing to it outweighs the perceived benefits of the change. There is fairly large amount of training material, old scripts etc which would need to modified to remove ifconfig and replace with the ip equivalents and many do not see the point or are unwilling to make the effort to make the changes... (this does not just apply in this case, e.g. there is still a large amount of old Cobol out there still being used for similar reasons). Simplest solution would probably be for someone offer as a project to some masochistic trainee programmer or undergrad the task of writing a script to map between ifconfig and ip. (If nothing else they would learn an awful lot about *NIX networking :-) ). While ip remains poorly documented, and ifconfig is well known the number of things that depend on the latter will tend to increase. - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkrFvpAACgkQasN0sSnLmgI/BgCdHbMt7Y4Iyh7z8agmwhJviMLm tSUAoPE3mArWeiRNwmjzeF2gndYU9euU =YU0c -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hans Witvliet wrote:

On Fri, 2009-10-02 at 09:49 +0100, G T Smith wrote:

...

While ip remains poorly documented, and ifconfig is well known the number of things that depend on the latter will tend to increase.

Much better job would be to.... Write The F..(ine) Manual! So we can reply with rtfm again

I suspect that WTFM (Writing the Fine Manual) in such way as someone other than the program author or fellow developer can understand it, is considered by many programmers/developers as more difficult (or boring) than writing the program itself :-) In this case things like LNAG would also need to be updated or an equivalent created (AFAIK this has not been done yet). Not really a simple exercise.... - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkrHDacACgkQasN0sSnLmgLLdACgrnpoyj0QUTtAAjUl033XSWwd GbkAoL2UOsWe8igobtgmqq5Foj8KUcLB =OvJp -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thursday 01 October 2009 11:29:32 pm kanenas@hawaii.rr.com wrote:

it would take very little effort from one of the gurus to make the grumpy third or two thirds smile if ip outputs at least the same info as ifconfig

put an alias into ~/.bashrc: <alias ifconfig='ip addr'> if you really want you can pipe it through sed, making it look exactly the same. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 30/09/09 03:13, kanenas@hawaii.rr.com wrote:

Actually the question should be reversed. If ip was to do one better (it is, no?) than ifconfig, why doesn't it? why is someone encouraged to reinvent the wheel if the *current* level of functionality is desired? is the kde4 mentality taking over everything? d.

please read the ifconfig manual "WARNING: Ifconfig is obsolete on system with Linux kernel newer than 2.0. On this system you should use ip. See the ip manual page for details" since 2.0 ..is a long, LONG time ago.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Cristian Rodríguez wrote:

On 29/09/09 16:42, phanisvara das wrote:

...

please excuse my ignorance, but why? i'm quite happy with it: finding out what's going on with my network configuration, shutting up & down devices. what's wrong with that?

It will go away at some point in the future, is deprecated.

Far too many information gathering routines use the output of ifconfig for it to be deprecated, especially since the ability to grab the same info in the same format can't be found easily (if at all) in ip. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wed, 30 Sep 2009, 17:54:26 +0200, David C. Rankin wrote:

[...] But you have hit upon a great point. Think of all the things from plasma widgets to superkaramba themes to just about every network related package that currently uses ifconfig. That is a whole lot of recoding if ifconfig goes away.

FWIW, to be honest, this discussion about ifconfig being deprecated and it will go away is about 7-8 years old now... Due to the fact that ifconfig is still around, I'd wouldn't bet on anyone claiming otherwise. But, as I haven't looked at factory anytime soon, I may be mistaken, and something - shown to us as a disclaimer for almost a decade now - has finally been made reality. I'd say, 7-8 years of a warning period should be enough for _everyone_ to adopt scripts... Cheers. l8er manfred -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

...

be enough for _everyone_ to adopt scripts... ^^^^^ s/o/a :)

are you saying we need an ESB to tell us NIC details ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wednesday 30 September 2009 01:50:47 pm Peter Nikolic wrote:

Well it has to be said that it needs to come back , It is an extremely quick easy tool to use and far out does ANY GUI based replacement

ip is not a gui tool. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

ifconfig should not be used. ~~~~~~~~~~~~~~~~~~~~` That's first I've heard of that. 'ifconfig' is a great tool. Why shouldn't it be used? James -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 29 September 2009 16:08:11 Adam Tauno Williams wrote: ...

"ip" can replace ifconfig / route / netstat / and misc... other scattered utilities.

I have to see how, as I'm used to that misc utilities. And of course, I'm not happy when I have to learn something from scratch, just to have the same ?! -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Simon Roberts wrote:

...

From: Doug McGarrett <dmcgarrett@optonline.net> To: opensuse@opensuse.org Sent: Tuesday, September 29, 2009 2:10:37 PM Subject: [opensuse] ipconfrig--where?

Does this program have ipconfig, and if so, how do you get to it? Ref: 9.3. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Assuming you're looking for ipconfig (there's no "r" in it), the most basic, and most reliable way, albeit not the fastest, to find something in any U**x system would be something on the lines of:

find / -name ipconfig -print

The -print is optional in most systems, but never hurts.

of course there is also the somewhat more useful whereis command :-)... see man whereis AFAIK this only searches the current path.... - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkrDC/QACgkQasN0sSnLmgLKnwCg1PalnBcXH/aM/MGNrmIMCoe6 JggAn2z1YXSRZrIycXck+PRyOFFusdZl =nQFD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org