Hi All,
I'm running squeak headless on a Raspberry Pi with -vm-display-null. Normally there is no monitor connected. Sometimes for testing I can connect a monitor. How can/should I write some text to the monitor so I can see what is going on? Thanks in advance for any and all help.
Lou
On 10-08-2017, at 9:05 AM, Louis LaBrunda Lou@Keystone-Software.com wrote:
Hi All,
I'm running squeak headless on a Raspberry Pi with -vm-display-null. Normally there is no monitor connected. Sometimes for testing I can connect a monitor. How can/should I write some text to the monitor so I can see what is going on? Thanks in advance for any and all help.
Other than doing magic to open a display window etc - which ought to be possible but I’ve never looked at it - the simplest thing is to use the stdio stream. As in
FileStream stdio nextPutAll: ‘Hello, World’; flush.
Your words of deathless prose should appear in whatever place stdout would appear, typically the terminal window from which you fired up Squeak. I have to admit I have no idea where that might be if you started Squeak from some login or startup script. Maybe it would require some added > mylogfile magic?
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim It is easier to change the specification to fit the program than vice versa.
And don't forget to put a #cr or #lf (I forget which) before the #flush.
I usually have OSProcess loaded, in which case a handy logging trick is OSProcess class>>trace:
Dave
On 10-08-2017, at 9:05 AM, Louis LaBrunda Lou@Keystone-Software.com wrote:
Hi All,
I'm running squeak headless on a Raspberry Pi with -vm-display-null. Normally there is no monitor connected. Sometimes for testing I can connect a monitor. How can/should I write some text to the monitor so I can see what is going on? Thanks in advance for any and all help.
Other than doing magic to open a display window etc - which ought to be possible but Iâve never looked at it - the simplest thing is to use the stdio stream. As in
FileStream stdio nextPutAll: âHello, Worldâ; flush.
Your words of deathless prose should appear in whatever place stdout would appear, typically the terminal window from which you fired up Squeak. I have to admit I have no idea where that might be if you started Squeak from some login or startup script. Maybe it would require some added > mylogfile magic?
tim
tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim It is easier to change the specification to fit the program than vice versa.
On Thu, Aug 10, 2017 at 9:41 AM, tim Rowledge tim@rowledge.org wrote:
On 10-08-2017, at 9:05 AM, Louis LaBrunda Lou@Keystone-Software.com
wrote:
Hi All,
I'm running squeak headless on a Raspberry Pi with -vm-display-null.
Normally there is no
monitor connected. Sometimes for testing I can connect a monitor. How
can/should I write some
text to the monitor so I can see what is going on? Thanks in advance
for any and all help.
Other than doing magic to open a display window etc - which ought to be possible but I’ve never looked at it - the simplest thing is to use the stdio stream. As in
FileStream stdio nextPutAll: ‘Hello, World’; flush.
That should be
FileStream stdout nextPutAll: ‘Hello, World’; cr; flush.
or
FileStream stderr nextPutAll: ‘Hello, World’; cr; flush.
Your words of deathless prose should appear in whatever place stdout would appear, typically the terminal window from which you fired up Squeak. I have to admit I have no idea where that might be if you started Squeak from some login or startup script. Maybe it would require some added > mylogfile magic?
tim
tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim It is easier to change the specification to fit the program than vice versa.
A common technique for servers is to have an RFB server running in the image, and to connect to it using a VNC client when needed. That way you don't even need a monitor, just a network connection.
- Bert -
On Thu, Aug 10, 2017 at 6:05 PM, Louis LaBrunda Lou@keystone-software.com wrote:
Hi All,
I'm running squeak headless on a Raspberry Pi with -vm-display-null. Normally there is no monitor connected. Sometimes for testing I can connect a monitor. How can/should I write some text to the monitor so I can see what is going on? Thanks in advance for any and all help.
Lou
Louis LaBrunda Keystone Software Corp. SkypeMe callto://PhotonDemon
Hi Guys,
Thanks for all the suggestions. I ended up with creating a simple/small log file. It was the easiest thing to do and it helped solve my most recent problem.
Lou
squeak-dev@lists.squeakfoundation.org
-
Bert Freudenberg -
David T. Lewis -
Eliot Miranda -
Louis LaBrunda -
tim Rowledge