“I’ve always assumed that ifup and ifdown were conditional commands that performed their assigned duties only if the interface device in question was up or down, as the command might be. I was dead wrong. I blame my mistake on being a programmer, rather than being stupid, but it’s simply too close to call. The if in ifup, ifdown, and ifstatus is not a programmer’s if – it’s an abbreviation for interface. On the off chance that I’m not the only one who has misunderstood these commands because of their rather iffy names, here’s what they really do and how they are used.”
Odd how the author would confuse an “if” programming statement with an OS command … a command is pretty much a program in itself, so why the confusion?
Maybe it’s because the author knows that unix command shells ARE programmable, and that OS commands ARE programming statements, and that “if” is a valid
conditional statement in the shell. Try it and see.
What really threw me off about this article was the use of the “CLI” acronym.
It’s probably an abbreviation for “click” so it must have something to to with the GUI.
My Debian machine has the commands ifup and ifdown, but no ifstatus. I searched: “apt-cache search ifstatus” and nothing was found. Does anyone know where you obtain this piece of software?
Why does one want to test ifup for example when your browser clearly loads pages?It’s evident your connection is up.
Why does one want to test ifup for example when your browser clearly loads pages?It’s evident your connection is up.
Because not everyone uses a pretty GUI on Linux.
These commands are mostly useful in scripting. You can’t test whether your connection is up and working from a shell script with GUI tools. There’s a lot of other things like this. Ever wonder why there is ‘true’ and ‘false’ commands? That’s why.
Why does one want to test ifup for example when your browser clearly loads pages?It’s evident your connection is up.
In order for a website to load in your browser, it has to be able to resolve the domain name to an IP address, and you have to have your routing table setup properly.
In other words, just because you can’t reach http://google.com via your browser, it doesn’t mean your connection is actually down. The command line tools give you more control over troubleshooting a problem. And, as someone else pointed out, the command line tools are often used in scripting.
ifconfig is my usual toy…
ifyoudidnotknowthis
{
you = newb;
}
Edited 2006-02-07 01:12
ifyoudidnotknowthis
{
you = newb;
}
Classic! What’s up with the moderation, people lost their sense of humor around here ?
What really threw me off about this article was the use of the “CLI” acronym.
Why? Was it too obvious? ๐
Thom, if you thought that was interesting, wait till you hear this next one. man is not a reference to the little people that live inside your computer. It is, in fact, short for manual.
*For those who have no sense of humor, this is a joke not a troll.
# emerge -S ifstatus
Searching…
[ Results for search key : ifstatus ]
[ Applications found : 0 ]
Am I missing something?
As far as I know Gentoo (and Debian?) don’t have ifstatus. They do have ifconfig which offers similar function.
For ifup and ifdown in gentoo see here: http://forums.gentoo.org/viewtopic-t-385555.html
As far as I know Gentoo (and Debian?) don’t have ifstatus. They do have ifconfig which offers similar function.
I’m running Gentoo and searched my ass off for them ๐
For ifup and ifdown in gentoo see here: