Dear Girish Ji,
Why do you always need to be so sarcastic ?
I love linux, and would even want to live with it, most of the time
(99.99%) it gives me everything and even the community people are very good
mannered and well cultured.
There are many times that even a simple reply can be made into a top-class
solution to the OP. When dont you answer from Linux point of view !!!!
Do, turn in your charm face when you are replying.
I always liked those sessions when we met for spam cheetah at chennai
(Frontier & others).
Looking to see your charming friendly reply (instead of hard-task-master
type).
regards,
s.sivakumar
chennai
On Tue, Dec 11, 2012 at 6:22 PM, Girish Venkatachalam <
girishvenkatachalam at gmail.com> wrote:
These are the problems you will never face in OpenBSD.
Aana other than my throat getting dry nothing is going to change in LUG. ;)
On Tue, Dec 11, 2012 at 5:53 PM, Balasubramaniam Natarajan
<bala150985 at gmail.com> wrote:
On Wed, Dec 5, 2012 at 11:33 AM, Arun Khan <knura9 at gmail.com> wrote:replace
The trouble is I did not pull out the nic card on this server and
ranthe nic after installation for me to face this problem.
I don't understand what you are saying above.
I ment that if I had replaced the NIC card on the server then it is okay
for the OS to have named my nic card in that increasing order, however it
this case all I did was to reboot the machine and eth0 became eth5.
Please state your problem clearly. What you kind of hardware you are
dealing with, what are you doing with that hardware.I am using Dell Rack based server, which has four ethernet card. While
installing the system I configure eth0 to be my mgmt interface. Then I
apt-get update and apt-get upgrade, then rebooted the system when I facedOS
this problem of eth0 never came up :-(
Brute force solution - empty the persistent net rules file and reboot.
udev will recreate the entries in the file and assign device eth*
names in the order it sees them. Edit the file to your liking i.e.
which NIC (aka mac address) you want to assign to respective eth*
names.
This worked on an instance, thanks. However how do I make sure that the
does not rename the interface automatically and cause this confusion ?
--
Regards,
Balasubramaniam Natarajan
www.blog.etutorshop.com
_______________________________________________
ILUGC Mailing List:
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
--
Gayatri Hitech
http://gayatri-hitech.com
_______________________________________________
ILUGC Mailing List:
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
