> > > How do you run VNC if you don't have X installed on your > > > *HEADLESS* servers? For a Java app, you *might* be able > > > to use http://www.developvnc.org/logged-in/jVNC-info.html, > > > since that is installed as an AWT replacement, but for X > > > clients, I believe that you still need to have X installed > > > to use VNC. > > > Having a *HEADLESS* server doesn't equate to not having X installed. > > Then we just have to clarify terms. :-) He used the term > "headless", and > I've always heard the term used to apply to systems without X > installed, > e.g., > > "A headless server is one running in a headless Squeak; > that is, a Squeak that does not have a connection to > an X server." [http://pbl.cc.gatech.edu/myswiki/275 > > "Zinc can be run in a simple headless server mode (i.e. > without a graphical user interface). This allows you > to run a Zinc server on a computer that does not have > a graphical display - a typical UNIX server for example." > [http://zinc.microwavepizza.co.uk/help/headless.html] > > etc. > > In any event, the important context is his, so we should find > out what he > meant. :-)
Well I doubt you will find a definitive definition of *HEADLESS* without chickens involved. My key point is that VNC (and other alternatives) allow remote administration of servers that lack physical input and output devices such as a keyboard, mouse and display. VNC does this cross-platform which is neat as given an Internet connection I can administer any of our servers via our VPN from anywhere. Better still, in times of dire need we can enable vendor tech. support staff to access a test server to assist in problem resolution. Much better than the typical 'send us a test-case that recreates the problem' scenario. > > In fact to run stuff, such as Java AWT rendering on *nix > you must have > > some kind of X-window display buffer, maybe VFB. > > I think that has changed. There were some notes about that recently. As I remember, the notes identified a code based work around for a situation that arose in Vincenzo's code when run in *nix and an observation that JDK 1.4 offers a parameter based work around. The latter we cannot rely on while stating JDK 1.3 compatibility. At the end of the day we are straying from James issues to the fact that there are a thousand and one ways to administer *HEADLESS* clients. Server admin. stuff I think. -- Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
