From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Wed, 21 Mar 2012 03:03:55 -0400 To: 9fans@9fans.net Message-ID: <475f07a0fb303033089ac070f1b4817c@brasstown.quanstro.net> In-Reply-To: <2579c7.ca2f8562.rxRt.mx@tumtum.plumbweb.net> References: <2579c7.a4dbcdb6.srLn.mx@tumtum.plumbweb.net> <2579c7.b6c4656c.fWVN.mx@tumtum.plumbweb.net> <293b9c3a5125e6d4510209ebe02df801@brasstown.quanstro.net> <2579c7.ca2f8562.rxRt.mx@tumtum.plumbweb.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] wifi interface Topicbox-Message-UUID: 6ca9c742-ead7-11e9-9d60-3106f5b1d025 On Wed Mar 21 03:02:26 EDT 2012, 9p-st@imu.li wrote: > > echo mtu 9000>/net/ether0/clone > interesting, i didn't realise clone had been overloaded like that, i just > knew about the ctl file in the connection directory. it's not overloaded. when you open the clone file, the fid gets changed to be that of $nextconv/ctl. since the operations tend to be one shot, the idom is to "operate directly on the clone file". - erik