> -Original Message-
> On Sun, Jan 29, 2006 at 02:27:42PM +0100, Robert Hillen wrote:
> > Thanks Jeff. Your patch seems to fix the problem partly,
> but I still
> > get the "device busy" error because the tun device still remains
> > attached to one process after eth0 is disabled in the
On Monday 30 January 2006 20:26, Jeff Dike wrote:
> On Sun, Jan 29, 2006 at 02:27:42PM +0100, Robert Hillen wrote:
> > Thanks Jeff. Your patch seems to fix the problem partly, but I still get
> > the "device busy" error because the tun device still remains attached to
> > one process after eth0 is
On Sun, Jan 29, 2006 at 02:27:42PM +0100, Robert Hillen wrote:
> Thanks Jeff. Your patch seems to fix the problem partly, but I still get
> the "device busy" error because the tun device still remains attached to
> one process after eth0 is disabled in the uml.
Can you try the attached patch, whic
/dev/net/tun
Many thanks,
Robert
> -Original Message-
> From: Jeff Dike [mailto:[EMAIL PROTECTED]
> Sent: Sunday, January 29, 2006 3:39 AM
> To: Robert Hillen
> Cc: user-mode-linux-user@lists.sourceforge.net
> Subject: Re: [uml-user] Not possible to enable eth0 in UML:
> De
On Sun, Jan 29, 2006 at 12:08:54AM +0100, Robert Hillen wrote:
> This happens when logging in to the uml via a telnet port. The problem
> is that in this case the /dev/net/tun device remains attached to 3
> proceses on the host:
Nice diagnosis - does this patch below help?
Index: linux-2.6.15-mm/
Hi all,
Sometimes following error occurs in an UML when enabling the ethernet
device:
uml:~ # ifconfig eth0 up
SIOCSIFFLAGS: Device or resource busy
This happens when logging in to the uml via a telnet port. The problem
is that in this case the /dev/net/tun device remains attached to 3
proceses
