![]() Unless you’ve turned off this option in System Preferences →Desktop & Screen Saver, you can faintly see the background through the menu bar. Apple figures that, in that case, you’re just exploring, reading, or hunting for a certain command. If you click the menu name and hold the mouse button down for a moment, the menu opens, but closes again when you release the button. If you give the menu name a quick click, the menu opens and stays open. Chapter 4 contains complete instructions for using and understanding the Dock.Īctually, menus are even smarter than that. You can change its size, move it to the sides of your screen, hide it entirely, and so on. (Click the window, or the Dock icon, to close Exposé.)īecause the Dock is such a critical component of Mac OS X, Apple has decked it out with enough customization controls to keep you busy experimenting for months. This feature, new in Snow Leopard, is an extension of the Exposé feature described on Exposé: Death to Window Clutter. Hold the mouse button down on a program’s Dock icon to see mini versions of all that program’s open windows. A shortcut menu of useful commands pops right out. To see the menu, Control-click it or right-click it. See Organizing and Removing Dock Icons for details.Įach Dock icon sprouts a pop-up menu. When you click a folder’s icon, you get a pop-up arc of icons, or a grid or list of them, that indicates what’s inside. When you click a program’s icon, a tiny, bright, micro-spotlight dot appears under its icon to let you know it’s open. (You can’t remove the icon of a program that’s currently open, however.)Ĭlick something once to open it. Remove a Dock icon by dragging it away from the Dock, and enjoy the animated puff of smoke that appears when you release the mouse button. ![]() You can add a new icon to the Dock by dragging it there. Everything else goes on the right, including documents, folders, and disks. Our switches are Juniper EX series 32's running JUNOS 10.x releases (10.4R5.5 will be unified on them all soon as we do rolling upgrades).Programs go on the left side. Were it not for the pre/post-thunderbolt firmware update difference, we'd be more focused on our network configuration. This is not a safe configuration for us and definitely suggests a change in behavior on the Mac side. The only way to get them to work is by giving them the same level of dhcp-trust on our switches that the server gets (or disabling our dhcp snooping and safeties vlan-wide). Some machines that were net booting prior to the thunderbolt firmware update (so I'm told) stopped being able to boot under normal conditions once they were updated. Long story short: our pre-thunderbolt-firmware-updated Macs all seem to work perfectly well on the secure network configuration we've had in place for years. At a lower level, if I disable dhcp snooping (which builds the dhcp binding table and implements some related protections) in the VLAN these systems all share, it also works. Enabling dhcp-trust on a port is actually a broad set of behaviors related to dhcp snooping, some arp anti-spoofing tools, etc. but the process ultimately times out and the local OS X is booted.ĥ - Enable dhcp-trust on a thunderbolt Mac's client port (making it the same as the server and, by our definition, very dangerous to our network) and it suddenly will netboot just fine. There are sometimes (?) a series of INFORM messages in the server log. Plug them into any client port in the network and they locate and boot from the server almost immediately.Ĥ - Plug a Mac that has received the recent thunderbolt firmware upgrade into the same (or any other standard) client port and it receives DHCP properly, but never netboots. We've run this for years.ģ - With the previously described conditions in place, any Macs we have that have NOT received (or are not, by age, eligible) for the recent thunderbolt firmware update appear to netboot just fine. It's a Linux server running standard ISC dhcpd. We also have DHCP snooping in our switches that monitors the conversations and provides us with a binding table showing client leases, etc.Ģ - Our DHCP server is standalone and outside of our Netboot server. By default, our client ports are all dhcp UNtrusted (blocks all but DHCP requests and client ACKs, etc). No objections here and we've had it configured this way all along. 1 - Our Netboot server requires dhcp-trust to be enabled on its port in the switch, allowing the switch to pass through dhcp-like messages that are normally blocked to prevent rogue dhcp on client ports.
0 Comments
Leave a Reply. |