Re: Removing stale network service entries
Re: Removing stale network service entries
- Subject: Re: Removing stale network service entries
- From: Allan Nathanson <email@hidden>
- Date: Sun, 17 Feb 2008 10:32:14 -0500
- Delivered-to: email@hidden
- Delivered-to: email@hidden
On Feb 16, 2008, at 8:21 AM, Peter Sichel wrote:
On Feb 15, 2008, at 3:54 PM, Allan Nathanson wrote:
But that's essentially what you'd need to do. ... and going a bit
deeper, you'd probably want to remove the adapter-->enX mapping
(something that would best be followed by a reboot).
Can you say more about the adaptor->enX mapping?
How would I remove that, and under what conditions would a reboot
really be necessary?
For the current implementation we keep track of the network interface
adaptors we've seen in the /Library/Preferences/SystemConfiguration/
NetworkInterfaces.plist file. The file is read in by configd's
InterfaceNamer.bundle at startup. When a new interface is detected we
update (write) the file and because we don't check to see if you've
made changes behind our back the only way to have the plugin start
fresh is to reboot (or restart configd which has other implications on
a running system).
---
On Feb 16, 2008, at 4:45 AM, Andreas Fink wrote:
how about a different approach to use always the same USB to
ethernet adaptor. So wherever this person goes, he takes his USB to
ethernet adaptors and only plug an ethernet in instead of plugging
an USB in?
The potential client is a dental lab. The fewer wires they have to
sterilize, the less the chance of cross-contamination and infection
transmission. If having a single point of connection wasn't a
requirement, they could just use Ethernet built-in.
And going wireless isn't an option?
- Allan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden