Comments on: Cross-silo consistency @ Sun http://blogs.digitar.com/jjww/2006/06/cross-silo-consistency-at-sun/ thoughts & musings Sat, 24 Jul 2010 02:26:30 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Steven http://blogs.digitar.com/jjww/2006/06/cross-silo-consistency-at-sun/comment-page-1/#comment-358 Steven Fri, 01 Feb 2008 14:42:57 +0000 #comment-358 I would assume you need different break sequences. Assume you are on a alom console to a server and you need to look at a zone. You wouldn't want it to send you back to the alom prompt when you just needed to disconnect from the zone. I would assume you need different break sequences. Assume you are on a alom console to a server and you need to look at a zone. You wouldn't want it to send you back to the alom prompt when you just needed to disconnect from the zone.

]]> By: Joe Moore http://blogs.digitar.com/jjww/2006/06/cross-silo-consistency-at-sun/comment-page-1/#comment-357 Joe Moore Wed, 03 Oct 2007 08:11:01 +0000 #comment-357 It's even worse on the x86 LOM front... try remembering that to break out of the console application on an x4500 you have to hit "ESC+(" instead of the other combinations.<br /> <br /> To be fair, though, ~ is the traditional rlogin escape character (and ~. therefore terminates the connection), and # is the traditional escape for the "tip" serial interface command (hence #. for the ALOM terminate sequence) The silos are assuming different traditional users. It's even worse on the x86 LOM front… try remembering that to break out of the console application on an x4500 you have to hit "ESC+(" instead of the other combinations.

To be fair, though, ~ is the traditional rlogin escape character (and ~. therefore terminates the connection), and # is the traditional escape for the "tip" serial interface command (hence #. for the ALOM terminate sequence) The silos are assuming different traditional users.

]]>