On Wed, Nov 18, 2009 at 6:13 PM, Ray Haque wrote:
> On Wed, Nov 18, 2009 at 11:51 AM, Mark Eichin wrote:
>> nning linux on there, or some other OS? It sounds like the
>> usual "remount-readonly on filesystem corruption, instead of panicking"
>> linux behaviour, which (pretty much by definition)
Ray Haque writes:
> Hello everyone,
>
> I have built screen to use on an embedded ARM platform (Zipit Z2
> instant messenger). I am having a problem where if I run multiple
> screens I end up with a "read only file system" and can no longer save
> anything. If I exit screen completely, the erro
Hi there,
Besides my main computer, I use an old Lear Sigler ADM-3A terminal.
It lacks function or cursor keys. Cursor-left is Ctrl-H, Cursor-up is
Ctrl-K an so on...
Jstar works fine but when using it inside screen, the trouble starts:
Ctrl-K is now "cursor up" and not interpreted by jstar.
B
Hi there,
Besides my main computer, I use an old Lear Sigler ADM-3A terminal.
It lacks function or cursor keys. Cursor-left is Ctrl-H, Cursor-up is
Ctrl-K an so on...
Jstar works fine but when using it inside screen, the trouble starts:
Ctrl-K is now "cursor up" and not interpreted by jstar.
Hello,
I have built screen for an embedded ARM device. Everything works okay
- but after moving through a couple of screened windows I keep finding
myself with a "read only file system". Even after I exit all screens,
the problem persists until I reboot.
Would anyone have any clues as to what i
Hello everyone,
I have built screen to use on an embedded ARM platform (Zipit Z2
instant messenger). I am having a problem where if I run multiple
screens I end up with a "read only file system" and can no longer save
anything. If I exit screen completely, the error still exists. It
takes a reb
