Source string Read only

(itstool) path: question/para
51/510
Context English State
How do I cut and paste text with a mouse in the text console?
It is not possible to remove data using the mouse. However, it is possible to copy and paste. Once the mouse daemon is running as described in the <link linkend="moused">previous question</link>, hold down button 1 (left button) and move the mouse to select a region of text. Then, press button 2 (middle button) to paste it at the text cursor. Pressing button 3 (right button) will <quote>extend</quote> the selected region of text.
If the mouse does not have a middle button, it is possible to emulate one or remap buttons using mouse daemon options. See the <citerefentry><refentrytitle>moused</refentrytitle><manvolnum>8</manvolnum></citerefentry> manual page for details.
My mouse has a fancy wheel and buttons. Can I use them in FreeBSD?
The answer is, unfortunately, <quote>It depends</quote>. These mice with additional features require specialized driver in most cases. Unless the mouse device driver or the user program has specific support for the mouse, it will act just like a standard two, or three button mouse.
For the possible usage of wheels in the X Window environment, refer to <link linkend="x-and-wheel">that section</link>.
How do I use my delete key in <command>sh</command> and <command>csh</command>?
For the <application>Bourne Shell</application>, add the following lines to <filename>~/.shrc</filename>. See <citerefentry><refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum></citerefentry> and <citerefentry><refentrytitle>editrc</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
bind ^[[3~ ed-delete-next-char # for xterm
For the <application>C Shell</application>, add the following lines to <filename>~/.cshrc</filename>. See <citerefentry><refentrytitle>csh</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
bindkey ^[[3~ delete-char # for xterm
Other Hardware
Workarounds for no sound from my <citerefentry><refentrytitle>pcm</refentrytitle><manvolnum>4</manvolnum></citerefentry> sound card?
Some sound cards set their output volume to 0 at every boot. Run the following command every time the machine boots:
<prompt>#</prompt> <userinput>mixer pcm 100 vol 100 cd 100</userinput>
Does FreeBSD support power management on my laptop?
FreeBSD supports the <acronym>ACPI</acronym> features found in modern hardware. Further information can be found in <citerefentry><refentrytitle>acpi</refentrytitle><manvolnum>4</manvolnum></citerefentry>.
Troubleshooting
Why is FreeBSD finding the wrong amount of memory on <trademark>i386</trademark> hardware?
The most likely reason is the difference between physical memory addresses and virtual addresses.
The convention for most PC hardware is to use the memory area between 3.5 GB and 4 GB for a special purpose (usually for PCI). This address space is used to access PCI hardware. As a result real, physical memory cannot be accessed by that address space.
What happens to the memory that should appear in that location is hardware dependent. Unfortunately, some hardware does nothing and the ability to use that last 500 MB of RAM is entirely lost.
Luckily, most hardware remaps the memory to a higher location so that it can still be used. However, this can cause some confusion when watching the boot messages.
On a 32-bit version of FreeBSD, the memory appears lost, since it will be remapped above 4 GB, which a 32-bit kernel is unable to access. In this case, the solution is to build a PAE enabled kernel. See the entry on memory limits for more information.
On a 64-bit version of FreeBSD, or when running a PAE-enabled kernel, FreeBSD will correctly detect and remap the memory so it is usable. During boot, however, it may seem as if FreeBSD is detecting more memory than the system really has, due to the described remapping. This is normal and the available memory will be corrected as the boot process completes.
Why do my programs occasionally die with <errorname>Signal 11</errorname> errors?
Signal 11 errors are caused when a process has attempted to access memory which the operating system has not granted it access to. If something like this is happening at seemingly random intervals, start investigating the cause.
These problems can usually be attributed to either:
If the problem is occurring only in a specific custom application, it is probably a bug in the code.
If it is a problem with part of the base FreeBSD system, it may also be buggy code, but more often than not these problems are found and fixed long before us general <acronym>FAQ</acronym> readers get to use these bits of code (that is what -CURRENT is for).
It is probably not a FreeBSD bug if the problem occurs compiling a program, but the activity that the compiler is carrying out changes each time.

Loading…

No matching activity found.

Browse all component changes

Glossary

English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: question/para
Flags
read-only
Source string location
book.translate.xml:1700
String age
a year ago
Source string age
a year ago
Translation file
books/faq.pot, string 281