Template talk:Cmd

2013-12-30T22:27:46Z

Theo: Equal sign

What was the reason that this template was changed? Now it look not much different than the standard mediawiki format for a line with a prefixed whitespace.<br />

<nowiki>{{Cmd|test command}}</nowiki>
{{Cmd|test command}}
test command
--[[User:Fab|Fab]] 04:10, 7 March 2012 (UTC)

<div style="margin-left:4em">
Probably I should have proposed the change first rather than just pushing it. I was trying to get visual consistency between the two block formats you exhibited above, and some new templates I was introducing, primarily [[Template:Cat]]. See [[User:Dubiousjim/Cheatsheet#Block_elements]] for some samples. As I informally browsed this wiki, it seemed like many pages just used the second, space-prefixed format for giving commands to enter---that is, the usage of [[Template:Cmd]] across this wiki seemed very incomplete. So I thought it might work best to have a presentation that was somewhat distinct but not jarringly so. That way, habituation to the [[Template:Cmd]] format needn't make it stand out so much when reading a page that says:

type these commands

(I can appreciate the merits of the other argument, though, that says it should stand out more when a wiki page doesn't use the [[Template:Cmd]], so that someone can more easily notice it and perhaps change it to do so.)

What do you think might work better? Using a darker background, like the template had formerly? Using a different border? Just don't worry about the considerations I cite, and go back to the original?

-- [[User:Dubiousjim|Dubiousjim]] 19:14, 7 March 2012 (UTC)
</div>

: Made the background darker, as in the original. -- [[User:Dubiousjim|Dubiousjim]] 06:45, 8 March 2012 (UTC)

=Equal sign=
Is it normal that I can't use "=" within this template? With <pre>{{cmd|=}}</pre> I get <pre>{{{1}}}</pre> I have to write <pre>{{cmd|&#61;}}</pre> to get <pre>=</pre>--[[User:Theo|Theo]] ([[User talk:Theo|talk]]) 22:27, 30 December 2013 (UTC)

Serial mouse

2013-12-30T22:26:53Z

Theo: how to make use of a serial mouse

[[Category:Installation]]

=Introduction=

A mouse connected to the serial port will not be recognized by an X.Org server automatically. In <code>/var/log/Xorg.0.log</code> there will be a message:
<pre>
(II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
</pre>
An existing <code>/etc/X11/xorg.conf</code> with <code>AutoAddDevices</code> enabled will result in
<pre>
(WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
</pre>

We will describe two ways of getting an usable serial mouse under X.org. In our example we have a Logitec serial mouse of the model M/N: M-M30 associated to the device <code>/dev/ttyS0</code>.

=Getting information about the mouse=

If the protocol for the serial mouse is unkown, the command {{cmd|mouse-test /dev/ttyS0}} from the package <code>gpm</code> can be used to get the necessary information. The program is interactive and will print at the end a message like:
<pre>
Your mouse seems to be a 'mman' one on "/dev/ttyS0" (24 matches)
</pre>
The <code>man</code> page <code>gpm-types</code> contain a list of the protocols. In our case the lines
<pre>
mman Mouseman
The protocol used by the new Logitech devices with three but-
tons. It is backward compatible with the Microsoft protocol, so
if your mouse has three buttons and works with -t ms or similar
decoders you may try -t mman instead to use the middle button.
This mouse decoder accepts standard serial options, although
they should not be needed.
</pre>
gives us more information about the protocol. We can test the mouse in a virtual console by running:
{{cmd|gpm -m /dev/ttyS0 -t mman}}

=Solution: Inform the Linux input subsystem=

The serial port should already be known to udev:
{{Cmd|udevadm info --name=/dev/ttyS0 --query=path}}
<pre>/devices/platform/serial8250/tty/ttyS0</pre>
But in the output of {{cmd|cat /proc/bus/input/devices}} there is no hint of its existence. Installing the package <code>linuxconsoletools</code> from the testing repository and executing
{{cmd|inputattach --mouseman /dev/ttyS0}}
should give us a working mouse for the X server.
The command
{{cmd|inputattach --help}} prints a list of the available protocols. In our case the line
<pre> --mouseman -mman 3-button Logitech / Genius mouse</pre>
tells us which one to use. Now the output of {{cmd|cat /proc/bus/input/devices}} should contain a section like:
<pre>
I: Bus=0013 Vendor=0004 Product=0001 Version=0100
N: Name="Logitech M+ Mouse"
P: Phys=ttyS0/serio0/input0
S: Sysfs=/devices/platform/serial8250/tty/ttyS0/serio8/input/input9
U: Uniq=
H: Handlers=event2 mouse0
B: PROP=0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3
</pre>

To start the <code>inputattach</code> command automatically create a file <code>/etc/local.d/sermouse.start</code> with the content:
<pre>
#!/bin/sh
inputattach --daemon --mouseman /dev/ttyS0
</pre>
Make it executable and add the service <code>local</code> to the <code>default</code> runlevel:
{{cmd|rc-update add local default}}
Then the command
{{cmd|rc}} should start the new service. If you want to stop <code>inputattach</code> when stopping the <code>local</code> service, create an executable file <code>/etc/local.d/sermouse.stop</code> with content
<pre>
#!/bin/sh
killall inputattach
</pre>
Alternatively you can create a script in <code>/etc/init.d</code> to define a service for the serial mouse.

=Solution: Configure the X.org server=

If you don't have a <code>/etc/X11/xorg.conf</code>, then generate one with the command
{{cmd|Xorg -configure}}
and modify (and move) the resulting file <code>/root/xorg.conf.new</code> to get a running X server. For instance you might have to know the correct driver for the <code>"InputDevice"</code> section for your graphics card. Include the section
<pre>
Section "ServerFlags"
Option "AutoAddDevices" "False"
EndSection
</pre>
to disable hotplugging and set the <code>"Device"</code> and <code>"Protocol"</code> options in the <code>"InputDevice"</code> section for your mouse. In our case we have:
<pre>
Option "Protocol" "MouseMan"
Option "Device" "/dev/ttyS0"
</pre>
Then restart the X server. For instance:
{{cmd|rc-service lxdm restart}}

=References=

*[http://wiki.archlinux.org/index.php/serial_input_device_to_kernel_input Serial input device to kernel input - ArchWiki]
*[http://bugs.alpinelinux.org/issues/2532 Feature #2532: Request for package: linuxconsoletools]
*[http://lists.alpinelinux.org/alpine-devel/1891.html How to run script at startup (alpine-devel Archives)]
*[http://wiki.gentoo.org/wiki/Local.d local.d GEntoo Wiki]

Alpine Linux - User contributions [en]

Template talk:Cmd

Serial mouse