Linked by Thom Holwerda on Mon 6th Feb 2006 22:21 UTC
General Development "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."
Permalink for comment 93373
To read all comments associated with this story, please click here.
RE: ifup
by bhearsum on Tue 7th Feb 2006 00:16 UTC in reply to "ifup"
Member since:

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.

Reply Parent Score: 3