Hi,All:

     I think this is a bug of vt_ioctl, who can give me a confirm?

     In the man page of consolechars(v 0.3.3), we can see the describe 
as follow:

---------------------------------------------------------------------
        --tty=device
               Use  device as console device for ioctls, instead of 
guessing which one to use, which usually chooses the current
               tty.  This can be useful for testing when under X, in 
conjunction with --no-act - actual ioctls are  refused  for
               some reason then.

--------------------------------------------------------------------

But when i use the command as follow,:
consolechars --sfm=/dir/name --tty=/dev/tty5  under tty1. The change 
happen on tty1, not on tty5! So i read the source code of consolechars 
and find the command as above use ioctl cmd PIO_UNIMAPCLR and 
PIO_UNIMAP. The source code of kernel 2.6.8.1 as follow:
(drivers/char/vt_ioctl.c)

         ...
         case PIO_UNIMAPCLR:
               { struct unimapinit ui;
                 if (!perm)
                         return -EPERM;
                 i = copy_from_user(&ui, (void *)arg, sizeof(struct 
unimapinit));
                 if (i) return -EFAULT;
                 con_clear_unimap(fg_console, &ui);
                 return 0;
               }

         case PIO_UNIMAP:
         case GIO_UNIMAP:
                 return do_unimap_ioctl(cmd, (struct unimapdesc *)arg, 
perm);
         ...


we can see in the case PIO_UNIMAPCLR, One parameter of con_clear_unimp 
is  "fg_console"! it's current tty!  In the implement of 
do_unimap_ioctl(), use "fg_console" too! Use "console" will be right!


The attachment is a patch against 2.6.8.1. If what i said is right, 
there also should do some other modify, such as in the case of 
GIO_SCRNMAP!