Changeset 615b431
- Timestamp:
- 07/22/2005 08:07:57 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:
- 853ae568
- Parents:
- ba0deaad
- Location:
- postlfs/config
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
postlfs/config/logon.xml
rba0deaad r615b431 27 27 28 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 to29 which will also accept certain escape sequences (see below) in order to 30 30 insert information about the system. There is also the file 31 31 <filename>issue.net</filename> which can be used when logging on remotely. 32 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 the33 configuration file and will <emphasis>not</emphasis> interpret the 34 34 escape sequences shown below.</para> 35 35 36 <para>One of the most common things which people want to do is toclear36 <para>One of the most common things which people want to do is clear 37 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 of39 doing this is to do<command>clear > /etc/issue</command>.38 escape sequence into <filename>/etc/issue</filename>. A simple way of 39 doing this is to issue the command <command>clear > /etc/issue</command>. 40 40 This will insert the relevant escape code into the start of the 41 41 <filename>/etc/issue</filename> file. Note that if you do this, when you 42 42 edit the file, you should leave the ^[c character on the first line alone.</para> 43 43 44 <para>The following escape s are recognized by <command>agetty</command>44 <para>The following escape sequences are recognized by <command>agetty</command> 45 45 (the program which usually parses <filename>/etc/issue</filename>). This 46 46 information is from <command>man agetty</command> where you can find … … 57 57 s Insert the system name, the name of the operating system. 58 58 l Insert the name of the current tty line. 59 m Insert the architecture identifier of the machine, e.g., i 48659 m Insert the architecture identifier of the machine, e.g., i686. 60 60 n Insert the nodename of the machine, also known as the hostname. 61 61 o Insert the domainname of the machine. 62 r Insert the release number of the kernel, e.g., 2. 4.16.62 r Insert the release number of the kernel, e.g., 2.6.11.12. 63 63 t Insert the current time. 64 64 u Insert the number of current users logged in. … … 68 68 69 69 </sect1> 70 -
postlfs/config/vimrc.xml
rba0deaad r615b431 25 25 26 26 <para>The LFS book installs <application>Vim</application> 27 as its text editor. At this point we should statethat there are a27 as its text editor. At this point it should be noted that there are a 28 28 <emphasis>lot</emphasis> of different editing applications out there including 29 29 <application>Emacs</application>, <application>nano</application>, … … 33 33 <application>Emacs</application> users!</para> 34 34 35 <para>The LFS book gives a basic <filename>vimrc</filename> file. Here, we 36 attempt to enhance this file. At startup, <command>vim</command> reads 37 <filename>/etc/vimrc</filename> and <filename>~/.vimrc</filename> (i.e., the 38 global <filename>vimrc</filename> and the user-specific one.). Note that this is 39 only true if you compiled <application>vim</application> using LFS-3.1 onwards. 40 Prior to this, the global <filename>vimrc</filename> was 35 <para>The LFS book creates a basic <filename>vimrc</filename> file. In this 36 section you'll find an attempt to enhance this file. At startup, 37 <command>vim</command> reads <filename>/etc/vimrc</filename> and 38 <filename>~/.vimrc</filename> (i.e., the global <filename>vimrc</filename> 39 and the user-specific one). Note that this is only true if you compiled 40 <application>vim</application> using LFS-3.1 onwards. Prior to this, the 41 global <filename>vimrc</filename> was 41 42 <filename>/usr/share/vim/vimrc</filename>.</para> 42 43 … … 46 47 will be made available to users you add to the system later. You can also copy 47 48 the file from <filename>/etc/skel/.vimrc</filename> to the home directory of 48 users already on the system, like root. Be sure to set permissions, owner, and 49 group if you do copy anything directly from 49 users already on the system, such as 50 <systemitem class='username'>root</systemitem>. Be sure to set permissions, 51 owner, and group if you do copy anything directly from 50 52 <filename class="directory">/etc/skel</filename>.</para> 51 53 … … 63 65 <filename>vimrc</filename> is slightly unusual.</para> 64 66 65 <para> We'll run througha quick explanation of what each of the67 <para>Below you'll find a quick explanation of what each of the 66 68 options in this example file means here:</para> 67 69 … … 117 119 118 120 </sect1> 119
Note:
See TracChangeset
for help on using the changeset viewer.