From d304a53f0bf5e12206ac95078c92ab6008d7eab5 Mon Sep 17 00:00:00 2001 From: Mikhail Gusarov Date: Sat, 14 Mar 2009 19:59:47 +0600 Subject: [PATCH] Explained difference between /etc/iftab and /etc/net/iftab. --- etcnet/docs/etcnet.8 | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/etcnet/docs/etcnet.8 b/etcnet/docs/etcnet.8 index bfadb39..75c9df1 100644 --- a/etcnet/docs/etcnet.8 +++ b/etcnet/docs/etcnet.8 @@ -25,7 +25,7 @@ ip rules startup table ('ip \-4 rule add' args) .IP /etc/net/vlantab VLAN mass\-configuration table. If you need to configure lots of simple VLAN interfaces, this is the right place. See VLANTAB SYNTAX for details. .IP /etc/net/iftab -Interface mappings table, optional, but strictly advised to have. This file is used by ifrename. iftab file format is described in iftab manpage. Please note that we don't use /etc/iftab, but keep our own /etc/net/iftab. This difference allows to keep /etc/net\-specific filenames with profile and host suffixes under a single directory without creating additional mess in /etc. Additionally it prevents the system from accidental interface name change after ifrename invocation. +Interface mappings table, optional, but strictly advised to have. iftab file format is described in iftab manpage. Please note that /etc/iftab is a separate entity, processed by the ifrename ran by udev. /etc/net/iftab works properly with etcnet profiles and host suffixes, but it's not possible to rename interface using /etc/net/iftab if it the target name is already occupied. Additionally it prevents the system from accidental interface name change after ifrename invocation. Hence, in simple configurations it's easier to use /etc/iftab (e.g. for assigning permanent eth0/eth1/... interfaces), and in complex environments it is advisable to use /etc/net/iftab and custom interface names. .IP /etc/net/hosttab This optional file can be used during MULTIHOST CONFIGURATION. .IP /etc/net/ifup\-pre -- 1.6.2