Several questions about Fedora & Qemu

1. NosuchDeviceeth0 error. This is generally because the MAC of the virtual network card has changed during the VM migration process. As a result, the system cannot identify the virtual network card and thus cannot start the network service. This problem occurs in virtual machines (my most basic Fedora14 system .), In/etc/udev/rules. d/70-persistent-net.rules. Delete this file and restart the client system. The system automatically identifies the Mac address of the NIC. 2. About the Fedora 1.No such Device eth0 error.
  This is generally because the MAC of the virtual network card has changed during the VM migration process. As a result, the system cannot identify the virtual network card and thus cannot start the network service.
This problem occurs in virtual machines (my most basic system of Fedora 14 .),
In /Etc/udev/rules. d/70-persistent-net.rulesHere.
Delete this file and restart the client system. The system automatically identifies the Mac address of the NIC.

2. About the network configuration of the most basic system of Fedora 14.
I used to have a graphical interface, so I didn't care about this issue. Besides, debian's system is still using the pppoeconf rp-pppoe package, which is very convenient to use.
But recently I am playing with the Qemu-KVM virtual machine. So I ran Fedora, installed the Fedora 14 graphic desktop on the host (physical machine), installed the most basic fedora system and Debian version 6.0 Test on the client (Guest virtual machine. Most of debian's 6.0 software packages are basically new, so it is worth looking forward. I have never used debian because the software package is too old, and now some server packages are basically as new as Fedora, such as Redis Tokyocabinet Mongodb CouchDB ....... and so on. We hope that Debian will make more efforts to develop a stable version 6.0 early. Hey ~~
-------------------------------------------------------------------
Configure it in/etc/sysconfig/network-script/ Directory.
Ifcfg-lo does not need to be configured. The most basic system is configured.
The main thing is to configure your ifcfg-eth0 file.
[Root @ tpwb network-scripts] #Vi ifcfg-eth0 DEVICE = eth0 port name
BOOTPROTO = static
BROADCAST = 192.168.0.255 BROADCAST address
HWADDR = Nic MAC address IPADDR = 192.168.0.5 IP Address
NETMASK = 255.255.255.0 Subnet Mask
NETWORK = 192.168.0.0 NETWORK segment
GATEWAY = 192.168.0.1 GATEWAY
ONBOOT = yes automatic loading upon startup
TYPE = Ethernet port TYPE
After the configuration is complete, you must
$ Ifup eth0# The command is used to start the network.

DNS is generally automatically allocated. However, we recommend that you.
$/Etc/resolv. conf
Nameserver first DNSnameserver second DNS
Bytes ------------------------------------------------------------------------------------------------

3. About Bash's Yum auto-completion (Tab tabulation key) function.
      Originally, fedora also supported this automatic complementing function, but Gome modified some files, causing this function to be invalid for Yum, so I would like to mention it specially.
        In ~ /. BashrcAdd the above Code to the file.

If [-f/etc/bash_completion]; then

  ./Etc/bash_completion

Fi

Save and execute $ Source/etc/bash_completionThe auto-completion function is added.