source: postlfs/config/logon.xml@ 1dad4a4

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 v5_1 xry111/git-date xry111/git-date-for-trunk xry111/git-date-test
Last change on this file since 1dad4a4 was bae6e15, checked in by Larry Lawrence <larry@…>, 18 years ago

fix xsl chunk error in PostLFS section

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

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