Bug#632970: cannot set keyboard layout for vserver
Harald Dunkel, le Fri 22 Jul 2011 15:28:30 +0200, a écrit :
> On 07/22/11 01:13, Samuel Thibault wrote:
> > Err, it looks plain wrong to me to configure the keyboard on the server
> > side.
> This bug report is not about configuring the keyboard-configuration
> package on a remote machine, but on the client, i.e. the host with
> the keyboard attached.
Ah, ok. Since you said "for a vserver", I thought you were talking about
> > If I want to connect to the same server from another machine
> > which has another keyboard layout, the layout is bogus. So it should be
> > configured on the client side, since that's where the keyboard is. And
> > you can do it, e.g.
> > Xephyr -keybd ephyr,,,xkbmodel=evdev,xkblayout=de :3 -screen 1280x1024 -query vserver1 -terminate
> I completely agree, but actually I just want to tell the local(!)
> keyboard-configuration package which keyboard is connected. X, Xnest,
> Xephyr and all other local XWindow servers could use this information,
> which would disburden the user from remembering complex command
> line options like
> -keybd ephyr,,,xkbmodel=evdev,xkblayout=de
So it'd be a matter of xserver-xephyr defaulting to the underlying X
server layout, or reading /etc/default/keyboard.
> Xephyr is not X, and uses us by default.
Why should it be cast into stone? us seems to me a bad default for most
(that is, no-us) people, compared to simply inheriting the underlying X
server layout or reading /etc/default/keyboarD.