source: postlfs/config/logon.xml@ f8d632a

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 xry111/git-date xry111/git-date-for-trunk xry111/git-date-test
Last change on this file since f8d632a was f8d632a, checked in by Bruce Dubbs <bdubbs@…>, 17 years ago

New XML Chapter 3

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

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