From: "roland" <devzero@web.de>
To: <yoshfuji@linux-ipv6.org>
Cc: <linux-net@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: unregister_netdevice: waiting for eth0 to become free
Date: Fri, 3 Nov 2006 20:53:09 +0100 [thread overview]
Message-ID: <01d001c6ff81$b4bb5dc0$962e8d52@aldipc> (raw)
In-Reply-To: 20061104.034726.27678443.yoshfuji@linux-ipv6.org
> The ipv6 module cannot be unloaded once it has been
> loaded.
sorry, i thought i could rmmod evey module which was insmod/modprobe'd
before and i didn`t know that there are exceptions
> I'm not sure what is happened with vmware.
i think this is not completely related to vmware - but maybe this is being
triggered more often by vmware ?
http://www.google.de/search?hl=de&q=%22unregister_netdevice%3A+waiting+for+eth0+to+become+free
it`s really strange, but after taking a look, vmware seems to recommend
disabling ipv6 for _every_ linux based guest OS in general:
http://pubs.vmware.com/guestnotes/wwhelp/wwhimpl/common/html/wwhelp.htm?context=gos_ww5_output&file=choose_install_guest_os.html
since there are already running millions of linux based VMs in this world,
i think this isn`t very good "promotion" for ipv6, if vmware recommending
disabling it.
ok, there are not that much people already needing ipv6 NOW, but the later
they are running it and the later outstanding bugs being fixed, the harder
it will be to convert from ipv4 to ipv6....
roland
----- Original Message -----
From: "YOSHIFUJI Hideaki / ????" <yoshfuji@linux-ipv6.org>
To: <devzero@web.de>
Cc: <linux-net@vger.kernel.org>; <linux-kernel@vger.kernel.org>;
<yoshfuji@linux-ipv6.org>
Sent: Friday, November 03, 2006 7:47 PM
Subject: Re: unregister_netdevice: waiting for eth0 to become free
> In article <01a501c6ff74$6fc52c80$962e8d52@aldipc> (at Fri, 3 Nov 2006
> 19:18:17 +0100), "roland" <devzero@web.de> says:
>
>> vserver1:~ # rmmod ipv6
>> ERROR: Module ipv6 is in use by ip6t_REJECT
>> vserver1:~ # rmmod ip6t_REJECT
>> ERROR: Module ip6t_REJECT is in use
>
> The ipv6 module cannot be unloaded once it has been
> loaded.
>
> I'm not sure what is happened with vmware.
>
> --yoshfuji
next prev parent reply other threads:[~2006-11-03 19:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 18:18 unregister_netdevice: waiting for eth0 to become free roland
2006-11-03 18:47 ` YOSHIFUJI Hideaki / 吉藤英明
2006-11-03 19:53 ` roland [this message]
2006-11-03 19:58 ` Stephen Hemminger
2006-11-03 20:13 ` YOSHIFUJI Hideaki / 吉藤英明
-- strict thread matches above, loose matches on Subject: below --
2006-11-03 20:31 devzero
2006-11-03 21:04 ` Stephen Hemminger
2006-11-03 21:43 ` roland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='01d001c6ff81$b4bb5dc0$962e8d52@aldipc' \
--to=devzero@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox