source: postlfs/config/logon.xml@ 64d97b7c

10.0 10.1 11.0 6.0 6.1 6.2 6.2.0 6.2.0-rc1 6.2.0-rc2 6.3 6.3-rc1 6.3-rc2 6.3-rc3 7.10 7.4 7.5 7.6 7.6-blfs 7.6-systemd 7.7 7.8 7.9 8.0 8.1 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind gnome kde5-13430 kde5-14269 kde5-14686 ken/refactor-virt krejzi/svn lazarus nosym perl-modules qt5new systemd-11177 systemd-13485 trunk v1_0 v5_0 v5_0-pre1 v5_1 v5_1-pre1 xry111/git-date xry111/git-date-for-trunk xry111/git-date-test
Last change on this file since 64d97b7c was 64d97b7c, checked in by Larry Lawrence <larry@…>, 19 years ago

update to sawfish-1.3, librep-0.16.2 and first round spell check

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@792 af4574ff-66df-0310-9fd7-8a98e5e911e0

  • Property mode set to 100644
File size: 2.5 KB
Line 
1<sect1 id="postlfs-config-logon">
2<?dbhtml filename="logon.html" dir="postlfs"?>
3<title>/etc/issue (Customizing your logon)</title>
4
5<para>When you first boot up your new LFS system, the logon screen will
6be nice and plain (as it should be in a bare-bones system). Many people
7however, will want their system to display some information in the logon
8message. This can be accomplished using the
9file <filename>/etc/issue</filename>.</para>
10
11<para>The <filename>/etc/issue</filename> file is a plain text file
12which will also accept certain Escape sequences (see below) in order to
13insert information about the system. There is also the file
14<filename>issue.net</filename> which can be used when logging on remotely.
15SSH however, will only use it if you set the option in the
16configuration file and will also <emphasis>not</emphasis> interpret the
17escape sequences as shown below.</para>
18
19<para>One of the most common things which people want to do is to clear
20the screen at each logon. The easiest way of doing that is to put a
21"clear" escape into /etc/issue. A simple way of doing this is to do
22<userinput>clear > /etc/issue</userinput>. This will insert the
23relevant escape code into the start of the
24<filename>/etc/issue</filename> file. Note that if you do this, when
25you edit the file, you should leave the ^[c character on the first line
26alone.</para>
27
28<para>The following escapes are recognized by agetty (the program which
29usually parses <filename>/etc/issue</filename>). This information is from
30<userinput>man agetty</userinput> where you can find extra information
31about the logon process.</para>
32
33<para>The issue-file can contain certain escape codes to display various
34information. All escape codes consist of a backslash (\) immediately followed
35by one of the letters explained below (so \d in
36<filename>/etc/issue</filename> would insert the current date).</para>
37
38<para><screen>b Insert the baudrate of the current line.
39d Insert the current date.
40s Insert the system name, the name of the operating system.
41l Insert the name of the current tty line.
42m Insert the architecture identifier of the machine, eg. i486
43n Insert the nodename of the machine, also known as the hostname.
44o Insert the domainname of the machine.
45r Insert the release number of the kernel, eg. 2.4.16.
46t Insert the current time.
47u Insert the number of current users logged in.
48U Insert the string "1 user" or "&lt;n&gt; users" where &lt;n&gt; is the
49 number of current users logged in.
50v Insert the version of the OS, eg. the build-date etc.</screen></para>
51
52</sect1>
53
Note: See TracBrowser for help on using the repository browser.