Re: [Hardhats-members] GTM prompt weirdness with FreeBSD

2006-10-10 Thread K.S. Bhaskar
If GT.M works at all on OS X, I would expect it the compiler to run 
unchanged.  This is because while GT.M generates object files in a 
standard format, it uses its own dynamic loader.

In Ismet's case, I suspect that the 1h is coming from some mismatch 
having to do with terminal characteristics on the server side (e.g., 
libncurses).  I wonder if something like stty sane before going into 
GT.M might make a difference.

GNU screen (http://www.gnu.org/software/screen/) may be a way to deal 
with the occasional connection freezing or dropping.

Regards
-- Bhaskar


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


Re: [Hardhats-members] GTM prompt weirdness with FreeBSD

2006-10-10 Thread Greg Woodhouse


--- K.S. Bhaskar [EMAIL PROTECTED] wrote:

 If GT.M works at all on OS X, I would expect it the compiler to run 
 unchanged.  This is because while GT.M generates object files in a 
 standard format, it uses its own dynamic loader.

Maybe.  Obviously, habing your own linker makes a big difference, but
what is not obvious to me (due to my ignorance of Mach) is that the
operating system interfaces will be compatible, even if the
high-level system calls (fork, dup, sbrk, etc.) I'll have to check
the developer documentation when I get a chance and see what I can
learn. My guess, though, is that if your run BSD over Mach, the fact
that schuduling (say) is handled by the microkernel would not be
visible at the VM level, and if thazt's the case Bhaskar may well be
right here. (I'm certainly no expert.)

 
 In Ismet's case, I suspect that the 1h is coming from some mismatch 
 having to do with terminal characteristics on the server side (e.g., 
 libncurses).  I wonder if something like stty sane before going
 into 
 GT.M might make a difference.
 

I'm sure you're right. The thread forked but there's been no exec (new
subject line) as yet. :-)

===
Gregory Woodhouse  [EMAIL PROTECTED]

Mathematics is the science of patterns.
--Lynn Arthur Steen, 1988

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


Re: [Hardhats-members] GTM prompt weirdness with FreeBSD

2006-10-10 Thread Ismet Kursunoglu
 
 In Ismet's case, I suspect that the 1h is coming from some mismatch 
 having to do with terminal characteristics on the server side (e.g., 
 libncurses).  I wonder if something like stty sane before going into 
 GT.M might make a difference.

I tried that but you still see the GTM1h displayed under stock FreeBSD 6.1, 
i386. 

 GNU screen (http://www.gnu.org/software/screen/) may be a way to deal 
 with the occasional connection freezing or dropping.

That is a great idea! Then I could just resume the session later on a
different terminal. 

Of course I would still like to know if this behavior, i.e. the ssh
lockups that I see from console sessions, is hardware (switch-network
adapter-cabling, bus, heat etc..) or software related. (send or recv issues 
or the myriad of possible adjustments to the application or network layers)
As time allows I will try to figure it out and report back. 

Overall I really like to use Debian-Stable as much as possible (the
rapidity and package management of security updates being the star feature) 
however
when it comes to networking features and internals and overall system 
documentation
and cohesiveness FreeBSD wins. To really understand something about
networks or security I often I will read the FreeBSD manual or better yet the 
FreeBSD and OpenBSD man pages, which are an invaluable resource. 

http://www.freebsd.org/cgi/man.cgi
http://www.openbsd.org/cgi-bin/man.cgi

-- 
Ismet B. Kursunoglu, MD, FCCP

 Medical Director
 Alaska Clinic, LLC
 3750 E. Country Field Circle, STE B
 Wasilla, Alaska 99654-6659
 [EMAIL PROTECTED]
 voice (907)357-7240

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


Re: [Hardhats-members] GTM prompt weirdness with FreeBSD

2006-10-09 Thread Norman Dodd
We have been using Putty for our remote sites with no problems

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ismet
Kursunoglu
Sent: Monday, October 09, 2006 9:32 AM
To: Hardhats
Subject: [Hardhats-members] GTM prompt weirdness with FreeBSD

I see a '1h' displayed immediately following the GTM prompt when I run
HUI OpenVistA 4.1 with the Linux compatibility layer under FreeBSD 6.1
for x86. No windowing system is running - i.e. just from the plain
console screen via an ssh session I see this;

GTM1h

I tried various shells with no change in the behavior. I also noticed
the same thing when I ssh into and log into our HUI/Debian/GTM/VistA 
server from a FreeBSD terminal. The '1h' will disappear after commands
such as 'D ^XUP' are run and then recalled using the history facility. 
(i.e. up-arrow). 

This doesn't happen under Debian/Sarge, NetBSD or OpenBSD. I don't 
have a Mac around to check OS X. However under Debian/Sarge the
history facility doesn't work. 

The reason I am interested in using FreeBSD is that I have noticed
rare lock ups over ssh-terminal sessions with stock Debian/Sarge
terminals. And so far in testing this doesn't appear to be the case
under FreeBSD. I admire and like the engineering, cohesiveness and
rock solid stability that FreeBSD offers so that is why I started
testing it for possible production. 

I like the idea of using just plain terminals for many reasons but the
system lock ups as mentioned above are going to be troublesome.  

I haven't experienced any frozen screens/lock-ups over ssh under KDE
using Konsole or xterms with Debian/Sarge - which is also perfectly
stable but much more resource intensive. We could certainly run
lightweight window managers as an alternative, but for some users I
would prefer that all they see is the plain old terminal.  

Thanks. 

-- 
Ismet B. Kursunoglu, MD, FCCP

 Medical Director
 Alaska Clinic, LLC
 3750 E. Country Field Circle, STE B
 Wasilla, Alaska 99654-6659
 [EMAIL PROTECTED]
 voice (907)357-7240

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


Re: [Hardhats-members] GTM prompt weirdness with FreeBSD

2006-10-09 Thread Kevin Toppenberg
Could that be part of an escape code sending a terminal control
sequence?  Have you tried putty?  Does it do the same thing?

Can you tell us more about the linux compatibility layer for FreeBSD?
I wonder how that would work with OS X?

Kevin


On 10/9/06, Ismet Kursunoglu [EMAIL PROTECTED] wrote:
 I see a '1h' displayed immediately following the GTM prompt when I run
 HUI OpenVistA 4.1 with the Linux compatibility layer under FreeBSD 6.1
 for x86. No windowing system is running - i.e. just from the plain
 console screen via an ssh session I see this;

 GTM1h

...

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


Re: [Hardhats-members] GTM prompt weirdness with FreeBSD

2006-10-09 Thread Ismet Kursunoglu
 Could that be part of an escape code sending a terminal control
 sequence?  Have you tried putty?  Does it do the same thing?

If it is related to the terminal then why the different behavior with
C-VT100 series of terminal emulation from Debian to FreeBSD? 

My understanding that putty is a terminal emulator for MS Windows
only. I have not seen this with putty.

 Can you tell us more about the linux compatibility layer for FreeBSD?
 I wonder how that would work with OS X?

My very limited understanding is that it works as a loadable kernel
module (called the linux KLD for Kernel LoaDable object) which then
allows you to access various Linux libraries and applications and run
them. You might have to manually link some libraries for things to work
but in general it claims to be able to run over 90% of Linux
applications. 
 
 On 10/9/06, Ismet Kursunoglu [EMAIL PROTECTED] wrote:
  I see a '1h' displayed immediately following the GTM prompt when I run
  HUI OpenVistA 4.1 with the Linux compatibility layer under FreeBSD 6.1
  for x86. No windowing system is running - i.e. just from the plain
  console screen via an ssh session I see this;
 
  GTM1h
 
 ...
-- 
Ismet B. Kursunoglu, MD, FCCP

 Medical Director
 Alaska Clinic, LLC
 3750 E. Country Field Circle, STE B
 Wasilla, Alaska 99654-6659
 [EMAIL PROTECTED]
 voice (907)357-7240

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members