From mboxrd@z Thu Jan  1 00:00:00 1970
From: dexen deVries <dexen.devries@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Date: Mon,  2 Sep 2013 12:38:26 +0200
Message-ID: <1909624.IyeLYgNJ9F@coil>
User-Agent: KMail/4.10.5 (Linux/3.11.0-rc3-l52; KDE/4.10.5; x86_64; ; )
In-Reply-To: <CAPavXpDf5UkYt-otEhxuW1ahh3XOFLuwduKAvn5TV5bHzB2mdg@mail.gmail.com>
References: <CAPd04b6STJ-uzv_XJixzH6zdr0hw0aJbtP9WNMYP9uif3jEfxw@mail.gmail.com>
	<CAPd04b6bQSUHKMsMrdhieJfYGTzEQdLn9Pje5wEsuojfiBT9sQ@mail.gmail.com>
	<CAPavXpDf5UkYt-otEhxuW1ahh3XOFLuwduKAvn5TV5bHzB2mdg@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
Subject: Re: [9fans] reading addr always returns #0,#0?
Topicbox-Message-UUID: 78c5da88-ead8-11e9-9d60-3106f5b1d025

On Monday 02 of September 2013 14:13:56 Alexander Sychev wrote:
> The problem is the "addr" file is closed between your calls. When you=
 open
> the "addr" file next time, an internal address is set to 0,0.
> But after the writing the address is actual and if you read "data" fi=
le you
> will see the text according to your address.
>=20
> I you write the code on C or Go without a closing a descriptor of "ad=
dr"
> file, everything will be ok :-)


or use 9p rdwr:


echo -n , | 9p write acme/2/addr
echo 'dot=3Daddr' | 9p rdwr acme/2/ctl=20

--=20
dexen deVries

[[[=E2=86=93][=E2=86=92]]]

Take care of the luxuries and the necessities will take care of themsel=
ves.
                -- L. Long