Hi Donald,

Donald Russell <russell....@gmail.com> writes:

> This Message Is From an Untrusted Sender 
> You have not previously corresponded with this sender. 
>  
> Thanks Sven,
>
> Where do I find the source code? Maybe I can contribute to a
> solution. 😀

It's in the linux kernel source, file drivers/s390/char/raw3270.c, line
580:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/s390/char/raw3270.c?h=v6.1-rc5#n580

As a quick test i changed:

        } else if (MACHINE_IS_VM) {
                raw3270_size_device_vm(rp);
                raw3270_size_device_done(rp);
        } else
                raw3270_writesf_readpart(rp);

to:
        } else if (0 && MACHINE_IS_VM) {
                raw3270_size_device_vm(rp);
                raw3270_size_device_done(rp);
        } else
                raw3270_writesf_readpart(rp);

so it always uses WSFQ to get the geometry.

> When you changed to code to use “LPAR mode” instead of diag 120, did
> the console work properly with different geometries?

It did, but i haven't tested whether dynamic resizing works. And it's
diag210, the 'diag 120' was a typo from me.

> That’s the first problem, when the system first comes up, if the
> screen isn’t 24X80 the wheels fall off the wagon.
>
> But the other problem occurs when the console is
> disconnected/reconnected and the geometry is different. (A very likely
> scenario as everybody has their favorite settings. I generally use 60
> X 140)

Let me try this here. I'm normally running c3270 in tmux, so i'm not
disconnecting and reconnecting to my session. But i realize that my
workflow is likely different compared to running production systems.

> I can detect when a reconnect event happens, but there needs to be a
> way to tell the kernel/driver “check the geometry
> and adjust accordingly”. 
>
> I’d like to use 3270 mode, but this is a showstopper for me. Without
> it working for any geometry allowed by 3270 data
> stream specification, it’s not something I want to implement. 🙁
>
> Why do I want to to use it? It solves two annoying problems:
> 1 - it supports “dark” fields so passwords are not visible (ssh to
> another system etc)
> 2 - it supports the Linux “progress bars” as created by fsck and
> others. On the 3215, every update is written to a new
> line; with the 3270 mode, those lines are just overwritten as
> intended.

It can even show different foreground colors if you set $TERM to ansi.

Regards
Sven

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to