|
|
Don't reboot...
Rather than rebooting just to change an IP, why don't you use ifconfig?
On most Macs, en0 is your default ethernet interface. If you're using another interface, specify that instead. This will go away, of course, the next time you reboot, but if you do whatever you like from your instructions above, the next reboot will catch the new IP, too.
Don't reboot...
I would agree that a reboot is optional. But I would suggest that it's probably a good idea to reboot now, during configuration. If you have to reboot at a later date when the system is "in production", and your system does not come up on the expected IP, or there's a typo in the default route or something, that could cause a bigger problem.
Don't reboot...
Just because ifconfig, although it's a legacy tool, doesn't respect Mac OS X procedure when changing things, for example configd is not aware of your changes and preferences.plist (located in "/Library/Preferences/SystemConfiguration") is not updated.
Don't reboot...
You touched a nerve and I had to respond.
Don't reboot...
Evedience of ifconfig usefulness is of all people MSFT.
Don't reboot...
Not to get too far off topic here, but
ipconfig has been around forever. It's been around at least as long as Windows NT 3.5, which was released in 1994, and I'm pretty sure it existed before that in Windows for Workgroups/DOS.Anyway, it can't really be compared to ifconfig on Unix, as you can't use it to actually do anything other than release/renew DHCP leases. It's mostly just for displaying network information, where ifconfig does all the real work of modifying interface configuration (hence the name!).
Don't reboot...
You may consider whatever you want but using ifconfig only is not recommended by Apple as it doesn't inform all the frameworks of the changes made. If it was the good tool why would Apple develop tools that you can find in Mac OS X Server to change network configuration ?
Don't reboot...
It's called high-level vs low-level. ifconfig is a low-level tool - pretty much all it does it tell you the current state of a network device or change the state of the device. It doesn't send out notifications, update configd, or do anything else, because it doesn't need to.
Don't reboot...
Reading this : |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.05 seconds |
|