Changeset 89acbff for postlfs/config/logon.xml
- Timestamp:
- 05/12/2005 08:23:24 PM (19 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 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, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 07ac9895
- Parents:
- c594bf3
- File:
-
- 1 edited
-
postlfs/config/logon.xml (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
postlfs/config/logon.xml
rc594bf3 r89acbff 7 7 8 8 <sect1 id="postlfs-config-logon" xreflabel="Customizing your Logon with /etc/issue"> 9 <sect1info> 10 <othername>$LastChangedBy$</othername> 11 <date>$Date$</date> 12 </sect1info> 13 <?dbhtml filename="logon.html"?> 14 <title>Customizing your Logon with /etc/issue</title> 15 <indexterm zone="postlfs-config-logon"> 16 <primary sortas="e-etc-issue">/etc/issue</primary></indexterm> 9 <?dbhtml filename="logon.html"?> 17 10 18 <para>When you first boot up your new <acronym>LFS</acronym> system, the logon 19 screen will be nice and plain (as it should be in a bare-bones system). Many 20 people however, will want their system to display some information in the logon 21 message. This can be accomplished using the 22 file <filename>/etc/issue</filename>.</para> 11 <sect1info> 12 <othername>$LastChangedBy$</othername> 13 <date>$Date$</date> 14 </sect1info> 23 15 24 <para>The <filename>/etc/issue</filename> file is a plain text file 25 which will also accept certain Escape sequences (see below) in order to 26 insert information about the system. There is also the file 27 <filename>issue.net</filename> which can be used when logging on remotely. 28 <command>ssh</command> however, will only use it if you set the option in the 29 configuration file and will also <emphasis>not</emphasis> interpret the 30 escape sequences shown below.</para> 16 <title>Customizing your Logon with /etc/issue</title> 31 17 32 <para>One of the most common things which people want to do is to clear 33 the screen at each logon. The easiest way of doing that is to put a 34 "clear" escape-sequence into <filename>/etc/issue</filename>. A simple way of 35 doing this is to do <userinput><command>clear > 36 /etc/issue</command></userinput>. 37 This will insert the relevant escape code into the start of the 38 <filename>/etc/issue</filename> file. Note that if you do this, when 39 you edit the file, you should leave the ^[c character on 40 the first line alone.</para> 18 <indexterm zone="postlfs-config-logon"> 19 <primary sortas="e-etc-issue">/etc/issue</primary> 20 </indexterm> 41 21 42 <para>The following escapes are recognized by agetty (the program which 43 usually parses <filename>/etc/issue</filename>). This information is from 44 <command>man agetty</command> where you can find extra information 45 about the logon process.</para> 22 <para>When you first boot up your new LFS system, the logon screen will 23 be nice and plain (as it should be in a bare-bones system). Many people 24 however, will want their system to display some information in the logon 25 message. This can be accomplished using the 26 file <filename>/etc/issue</filename>.</para> 46 27 47 <para>The <filename>issue</filename> file can contain certain escape codes to 48 display various information. All escape codes consist of a backslash 49 (\) immediately followed by one of the letters explained 50 below (so <option>\d</option> in <filename>/etc/issue</filename> would 51 insert the current date).</para> 28 <para>The <filename>/etc/issue</filename> file is a plain text file 29 which will also accept certain Escape sequences (see below) in order to 30 insert information about the system. There is also the file 31 <filename>issue.net</filename> which can be used when logging on remotely. 32 <command>ssh</command> however, will only use it if you set the option in the 33 configuration file and will also <emphasis>not</emphasis> interpret the 34 escape sequences shown below.</para> 52 35 53 <screen>b Insert the baudrate of the current line. 36 <para>One of the most common things which people want to do is to clear 37 the screen at each logon. The easiest way of doing that is to put a "clear" 38 escape-sequence into <filename>/etc/issue</filename>. A simple way of 39 doing this is to do <command>clear > /etc/issue</command>. 40 This will insert the relevant escape code into the start of the 41 <filename>/etc/issue</filename> file. Note that if you do this, when you 42 edit the file, you should leave the ^[c character on the first line alone.</para> 43 44 <para>The following escapes are recognized by <command>agetty</command> 45 (the program which usually parses <filename>/etc/issue</filename>). This 46 information is from <command>man agetty</command> where you can find 47 extra information about the logon process.</para> 48 49 <para>The <filename>issue</filename> file can contain certain escape codes to 50 display various information. All escape codes consist of a backslash (\) 51 immediately followed by one of the letters explained below (so 52 <option>\d</option> in <filename>/etc/issue</filename> would 53 insert the current date).</para> 54 55 <screen><literal>b Insert the baudrate of the current line. 54 56 d Insert the current date. 55 57 s Insert the system name, the name of the operating system. … … 63 65 U Insert the string "1 user" or "<n> users" where <n> is the 64 66 number of current users logged in. 65 v Insert the version of the <acronym>OS</acronym>, e.g., the build-date etc.</screen>67 v Insert the version of the OS, e.g., the build-date etc.</literal></screen> 66 68 67 69 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.
