From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 From: "James A. Robinson" Date: Thu, 29 Sep 2016 07:15:00 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11423ca6ff77a7053da03cf0 Subject: [9fans] Question re source trees Topicbox-Message-UUID: a1114454-ead9-11e9-9d60-3106f5b1d025 --001a11423ca6ff77a7053da03cf0 Content-Type: text/plain; charset=UTF-8 Hi folks, I notice that http://plan9.bell-labs.com/plan9/download/plan9.iso.bz2 is from 2015-01-10, whereas Richard Miller's http://plan9.bell-labs.com/sources/contrib/miller/9pi.img.gz was built on 2016-05-30. I was wondering whether the changes made by Mr. Miller for supporting the Raspberry Pi were getting folded back into a source tree available via means other than those with an active plan9 system (I see references to /n/sources/contrib/miller which I assume is a 9fs mount). I was specifically curious because I wanted to poke around to get sense of what kind of support is available for the Raspberry Pi 3 vs. the Raspberry Pi 2. There were some early emails indicating a few small changes Mr. Miller needed to make for booting the system, but I couldn't find anything discussing whether other hardware was supported (e.g., the built-in wifi on the Pi 3). Jim --001a11423ca6ff77a7053da03cf0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi folks,

I notice that=C2= =A0http= ://plan9.bell-labs.com/plan9/download/plan9.iso.bz2
is from 2= 015-01-10, whereas Richard Miller's
http://plan9.bell-labs.com/= sources/contrib/miller/9pi.img.gz

was built on= 2016-05-30.=C2=A0 I was wondering whether the changes made
by Mr= . Miller for supporting the Raspberry Pi were getting folded
back= into a source tree available via means other than those with
an = active plan9 system (I see references to =C2=A0/n/sources/contrib/miller
which I assume is a 9fs mount).

I was spec= ifically curious because I wanted to poke around to get
sense of = what kind of support is available for the Raspberry Pi 3
vs. the = Raspberry Pi 2.=C2=A0 There were some early emails indicating
a f= ew small changes Mr. Miller needed to make for booting the
system= , but I couldn't find anything discussing whether other
hardw= are was supported (e.g., the built-in wifi on the Pi 3).

Jim

--001a11423ca6ff77a7053da03cf0-- From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@9fans.net From: Richard Miller <9fans@hamnavoe.com> Date: Thu, 29 Sep 2016 09:08:27 +0100 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Question re source trees Topicbox-Message-UUID: a12a3978-ead9-11e9-9d60-3106f5b1d025 > I was wondering whether the changes made > by Mr. Miller for supporting the Raspberry Pi were getting folded > back into a source tree available via means other than those with > an active plan9 system (I see references to /n/sources/contrib/miller > which I assume is a 9fs mount). You can also use a web browser to access /n/sources; it's mapped to http://plan9.bell-labs.com/sources (when the server isn't down). Source for all the raspberry pi kernel changes is kept up to date in http://plan9.bell-labs.com/sources/contrib/miller/9/bcm > ... I couldn't find anything discussing whether other > hardware was supported (e.g., the built-in wifi on the Pi 3). The Broadcom 43430 wifi chip on the pi3 turns out to be functionally almost the same as the 4330, for which I had written a driver some time ago for another platform. The client who commissioned that work has generously agreed to its release, so 9piwifi support will appear shortly. (The driver is working but WPA authentication needs a few tweaks.) I can also supply bluetooth code for the pi3 if anyone is interested. From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 29 Sep 2016 01:12:27 -0700 From: Kurt H Maier To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20160929081227.GD70826@wopr> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [9fans] Question re source trees Topicbox-Message-UUID: a12fa688-ead9-11e9-9d60-3106f5b1d025 On Thu, Sep 29, 2016 at 09:08:27AM +0100, Richard Miller wrote: > > I can also supply bluetooth code for the pi3 if anyone is interested. > I am interested. Will it be part of your next pi release? khm From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20160929081227.GD70826@wopr> References: <20160929081227.GD70826@wopr> From: Richard Miller <9fans@hamnavoe.com> Date: Thu, 29 Sep 2016 11:54:03 +0100 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=94eb2c0b7c96d09b37053da34b84 Subject: [9fans] Question re source trees Topicbox-Message-UUID: a1350de4-ead9-11e9-9d60-3106f5b1d025 --94eb2c0b7c96d09b37053da34b84 Content-Type: text/plain; charset=UTF-8 > > > I can also supply bluetooth code for the pi3 if anyone is interested. > > > > I am interested. Will it be part of your next pi release? > > Probably not for a while. I would have to write some man pages first. --94eb2c0b7c96d09b37053da34b84 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
> I can also supply bluetooth code for th= e pi3 if anyone is interested.
>

I am interested.=C2=A0 Will it be part of your next pi release?

Probably not for a while. I would have to write some man = pages first.
=C2=A0
--94eb2c0b7c96d09b37053da34b84-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: From: Ole-Hjalmar Kristensen Date: Thu, 29 Sep 2016 13:55:00 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7bacb134c00e25053da425c2 Subject: Re: [9fans] Question re source trees Topicbox-Message-UUID: a140d6f6-ead9-11e9-9d60-3106f5b1d025 --047d7bacb134c00e25053da425c2 Content-Type: text/plain; charset=UTF-8 This is great news. I am thinking of using the Pi3 to control a mobile platform, and having wifi support without using an external wireless router would simplify the hardware. On Thu, Sep 29, 2016 at 10:08 AM, Richard Miller <9fans@hamnavoe.com> wrote: > > I was wondering whether the changes made > > by Mr. Miller for supporting the Raspberry Pi were getting folded > > back into a source tree available via means other than those with > > an active plan9 system (I see references to /n/sources/contrib/miller > > which I assume is a 9fs mount). > > You can also use a web browser to access /n/sources; it's mapped to > http://plan9.bell-labs.com/sources (when the server isn't down). > > Source for all the raspberry pi kernel changes is kept up to date in > http://plan9.bell-labs.com/sources/contrib/miller/9/bcm > > > ... I couldn't find anything discussing whether other > > hardware was supported (e.g., the built-in wifi on the Pi 3). > > The Broadcom 43430 wifi chip on the pi3 turns out to be functionally > almost the same as the 4330, for which I had written a driver some > time ago for another platform. The client who commissioned that work > has generously agreed to its release, so 9piwifi support will appear > shortly. (The driver is working but WPA authentication needs a few > tweaks.) > > I can also supply bluetooth code for the pi3 if anyone is interested. > > > --047d7bacb134c00e25053da425c2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
This is great news. I am thinking of using the Pi3 to cont= rol a mobile platform, and having wifi support without using an external wi= reless router would simplify the hardware.

On Thu, Sep 29, 2016 at 10:08 AM, Richar= d Miller <9fans@hamnavoe.com> wrote:
> I was wondering whether the changes mad= e
> by Mr. Miller for supporting the Raspberry Pi were getting folded
> back into a source tree available via means other than those with
> an active plan9 system (I see references to=C2=A0 /n/sources/contrib/m= iller
> which I assume is a 9fs mount).

You can also use a web browser to access /n/sources; it's mapped= to
http://plan9.bell-labs.com/sources (when the server isn&#= 39;t down).

Source for all the raspberry pi kernel changes is kept up to date in
http://plan9.bell-labs.com/sources/contr= ib/miller/9/bcm

> ... I couldn't find anything discussing whether other
> hardware was supported (e.g., the built-in wifi on th= e Pi 3).

The Broadcom 43430 wifi chip on the pi3 turns out to be functionally=
almost the same as the 4330, for which I had written a driver some
time ago for another platform.=C2=A0 The client who commissioned that work<= br> has generously agreed to its release, so 9piwifi support will appear
shortly.=C2=A0 (The driver is working but WPA authentication needs a few tweaks.)

I can also supply bluetooth code for the pi3 if anyone is interested.



--047d7bacb134c00e25053da425c2-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: From: "James A. Robinson" Date: Thu, 29 Sep 2016 06:22:58 -0700 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11461deac05d58053da56252 Subject: Re: [9fans] Question re source trees Topicbox-Message-UUID: a14f71c0-ead9-11e9-9d60-3106f5b1d025 --001a11461deac05d58053da56252 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable =E2=80=8BThank you for the answer, that's very generous of =E2=80=8Byou and= your client! (I had thought the http://plan9.bell-labs.com/sources site was having trouble, looks like maybe it's just Chrome getting aggressive about HTTPS and failing, I can open the page w/ lynx). Jim --001a11461deac05d58053da56252 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
=E2=80=8BThank you for the answer, that= 's very generous of =E2=80=8Byou and your client!
(I had thought the http:/= /plan9.bell-labs.com/sources site was having
tr= ouble, looks like maybe it's just Chrome getting aggressive about
=
HTTPS and failing, I can open the page w/ lynx).


= Jim
--001a11461deac05d58053da56252-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: In-Reply-To: From: "James A. Robinson" Date: Sun, 2 Oct 2016 17:42:14 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11481626acdece053de5591a Subject: [9fans] plan9.bell-labs.com hates AppleWebKit? Topicbox-Message-UUID: a2bc4754-ead9-11e9-9d60-3106f5b1d025 --001a11481626acdece053de5591a Content-Type: text/plain; charset=UTF-8 So... Does Alcatel-Lucent have a problem with AppleWebKit users on principle? It looks to me as though my problem with browsing around under http://plan9.bell-labs.com/sources/ (and other subpages) is because the server doesn't like the User-Agent string: $ telnet plan9.bell-labs.com 80 Trying 135.104.24.16... Connected to plan9.bell-labs.com. Escape character is '^]'. GET /sources/contrib/ HTTP/1.1 Host: plan9.bell-labs.com Connection: keep-alive Cache-Control: max-age=0 Upgrade-Insecure-Requests: 1 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 DNT: 1 Accept-Encoding: gzip, deflate, sdch Accept-Language: en-US,en;q=0.8 HTTP/1.1 200 OK Connection closed by foreign host. And here it is again w/o the User-Agent string: $ telnet plan9.bell-labs.com 80 Trying 135.104.24.16... Connected to plan9.bell-labs.com. Escape character is '^]'. GET /sources/contrib/ HTTP/1.1 Host: plan9.bell-labs.com Connection: keep-alive Cache-Control: max-age=0 Upgrade-Insecure-Requests: 1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 DNT: 1 Accept-Encoding: gzip, deflate, sdch Accept-Language: en-US,en;q=0.8 HTTP/1.1 200 OK Server: Plan9 Date: Sun, 02 Oct 2016 17:29:09 GMT Connection: close Last-Modified: Fri, 14 Mar 2014 22:14:11 GMT Content-Type: text/html [... proper body returned...] I tried playing around with the UA value and found that if I change AppleWebKit to something else such as AppleWebKis I get a response... Jim --001a11481626acdece053de5591a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
So... Does Alcatel-Lucent have a problem with AppleWebKit=
users on principle?

It looks to me as though my problem with br= owsing around
under http://plan9.bell-labs.com/sources/ (and other subpages)
i= s because the server doesn't like the User-Agent string:

$ telne= t plan9.bell-labs.com 80
Tryi= ng 135.104.24.16...
Connected to = plan9.bell-labs.com.
Escape character is '^]'.
GET /sourc= es/contrib/ HTTP/1.1
Host: plan9.= bell-labs.com
Connection: keep-alive
Cache-Control: max-age=3D0Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Macintosh; Intel= Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.= 116 Safari/537.36
Accept: text/html,application/xhtml+xml,application/xm= l;q=3D0.9,image/webp,*/*;q=3D0.8
DNT: 1
Accept-Encoding: gzip, deflat= e, sdch
Accept-Language: en-US,en;q=3D0.8

HTTP/1.1 200 OK
Conn= ection closed by foreign host.

And here it is again w/o the User-Age= nt string:

$ telnet plan9.bel= l-labs.com 80
Trying 135.104.24.16...
Connected to plan9.bell-labs.com.
Escape character is &#= 39;^]'.
GET /sources/contrib/ HTTP/1.1
Host: plan9.bell-labs.com
Connection: keep-alive
Cac= he-Control: max-age=3D0
Upgrade-Insecure-Requests: 1
Accept: text/htm= l,application/xhtml+xml,application/xml;q=3D0.9,image/webp,*/*;q=3D0.8
D= NT: 1
Accept-Encoding: gzip, deflate, sdch
Accept-Language: en-US,en;= q=3D0.8

HTTP/1.1 200 OK
Server: Plan9
Date: Sun, 02 Oct 2016 1= 7:29:09 GMT
Connection: close
Last-Modified: Fri, 14 Mar 2014 22:14:1= 1 GMT
Content-Type: text/html

[... proper body returned...]
I tried playing around with the UA value and found that if I change
A= ppleWebKit to something else such as AppleWebKis I get a
response...
=
Jim

--001a11481626acdece053de5591a-- From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sun, 2 Oct 2016 22:01:21 -0400 From: sl@9front.org To: 9fans@9fans.net Message-ID: <339dd66b0a603a422b5037b357a47d4d@mirv.inri.net> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] plan9.bell-labs.com hates AppleWebKit? Topicbox-Message-UUID: a2c5e5ac-ead9-11e9-9d60-3106f5b1d025 > So... Does Alcatel-Lucent have a problem with AppleWebKit > users on principle? Interesting reversal. sl From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) From: arisawa In-Reply-To: Date: Tue, 4 Oct 2016 21:59:40 +0900 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] plan9.bell-labs.com hates AppleWebKit? Topicbox-Message-UUID: a39ccbda-ead9-11e9-9d60-3106f5b1d025 I can get proper response from http://plan9.bell-labs.com/sources/ by = using mac/osx safari. > 2016/10/03 2:42=E3=80=81James A. Robinson = =E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=EF=BC=9A >=20 > So... Does Alcatel-Lucent have a problem with AppleWebKit > users on principle? >=20 > It looks to me as though my problem with browsing around > under http://plan9.bell-labs.com/sources/ (and other subpages) > is because the server doesn't like the User-Agent string: >=20 > $ telnet plan9.bell-labs.com 80 > Trying 135.104.24.16... > Connected to plan9.bell-labs.com. > Escape character is '^]'. > GET /sources/contrib/ HTTP/1.1 > Host: plan9.bell-labs.com > Connection: keep-alive > Cache-Control: max-age=3D0 > Upgrade-Insecure-Requests: 1 > User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) = AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 = Safari/537.36 > Accept: = text/html,application/xhtml+xml,application/xml;q=3D0.9,image/webp,*/*;q=3D= 0.8 > DNT: 1 > Accept-Encoding: gzip, deflate, sdch > Accept-Language: en-US,en;q=3D0.8 >=20 > HTTP/1.1 200 OK > Connection closed by foreign host. >=20 > And here it is again w/o the User-Agent string: >=20 > $ telnet plan9.bell-labs.com 80 > Trying 135.104.24.16... > Connected to plan9.bell-labs.com. > Escape character is '^]'. > GET /sources/contrib/ HTTP/1.1 > Host: plan9.bell-labs.com > Connection: keep-alive > Cache-Control: max-age=3D0 > Upgrade-Insecure-Requests: 1 > Accept: = text/html,application/xhtml+xml,application/xml;q=3D0.9,image/webp,*/*;q=3D= 0.8 > DNT: 1 > Accept-Encoding: gzip, deflate, sdch > Accept-Language: en-US,en;q=3D0.8 >=20 > HTTP/1.1 200 OK > Server: Plan9 > Date: Sun, 02 Oct 2016 17:29:09 GMT > Connection: close > Last-Modified: Fri, 14 Mar 2014 22:14:11 GMT > Content-Type: text/html >=20 > [... proper body returned...] >=20 > I tried playing around with the UA value and found that if I change=20 > AppleWebKit to something else such as AppleWebKis I get a > response... >=20 > Jim >=20 From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: From: Sergey Zhilkin Date: Wed, 5 Oct 2016 22:01:34 +0300 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=e89a8fb1f99e8572fa053e22cf19 Subject: Re: [9fans] plan9.bell-labs.com hates AppleWebKit? Topicbox-Message-UUID: a3c58a02-ead9-11e9-9d60-3106f5b1d025 --e89a8fb1f99e8572fa053e22cf19 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi all ! Get right response from server, with macOS Sierra beta 10.12.1 (16B2338c) and Safari 10.0.1 (12602.2.14.0.1) 2016-10-04 15:59 GMT+03:00 arisawa : > I can get proper response from http://plan9.bell-labs.com/sources/ by > using mac/osx safari. > > > > 2016/10/03 2:42=E3=80=81James A. Robinson =E3=81=AE= =E3=83=A1=E3=83=BC=E3=83=AB=EF=BC=9A > > > > So... Does Alcatel-Lucent have a problem with AppleWebKit > > users on principle? > > > > It looks to me as though my problem with browsing around > > under http://plan9.bell-labs.com/sources/ (and other subpages) > > is because the server doesn't like the User-Agent string: > > > > $ telnet plan9.bell-labs.com 80 > > Trying 135.104.24.16... > > Connected to plan9.bell-labs.com. > > Escape character is '^]'. > > GET /sources/contrib/ HTTP/1.1 > > Host: plan9.bell-labs.com > > Connection: keep-alive > > Cache-Control: max-age=3D0 > > Upgrade-Insecure-Requests: 1 > > User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) > AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 > > Accept: text/html,application/xhtml+xml,application/xml;q=3D0.9, > image/webp,*/*;q=3D0.8 > > DNT: 1 > > Accept-Encoding: gzip, deflate, sdch > > Accept-Language: en-US,en;q=3D0.8 > > > > HTTP/1.1 200 OK > > Connection closed by foreign host. > > > > And here it is again w/o the User-Agent string: > > > > $ telnet plan9.bell-labs.com 80 > > Trying 135.104.24.16... > > Connected to plan9.bell-labs.com. > > Escape character is '^]'. > > GET /sources/contrib/ HTTP/1.1 > > Host: plan9.bell-labs.com > > Connection: keep-alive > > Cache-Control: max-age=3D0 > > Upgrade-Insecure-Requests: 1 > > Accept: text/html,application/xhtml+xml,application/xml;q=3D0.9, > image/webp,*/*;q=3D0.8 > > DNT: 1 > > Accept-Encoding: gzip, deflate, sdch > > Accept-Language: en-US,en;q=3D0.8 > > > > HTTP/1.1 200 OK > > Server: Plan9 > > Date: Sun, 02 Oct 2016 17:29:09 GMT > > Connection: close > > Last-Modified: Fri, 14 Mar 2014 22:14:11 GMT > > Content-Type: text/html > > > > [... proper body returned...] > > > > I tried playing around with the UA value and found that if I change > > AppleWebKit to something else such as AppleWebKis I get a > > response... > > > > Jim > > > > > --=20 =D0=A1 =D0=BD=D0=B0=D0=B8=D0=BB=D1=83=D1=87=D1=88=D0=B8=D0=BC=D0=B8 =D0=BF= =D0=BE=D0=B6=D0=B5=D0=BB=D0=B0=D0=BD=D0=B8=D1=8F=D0=BC=D0=B8 =D0=96=D0=B8=D0=BB=D0=BA=D0=B8=D0=BD =D0=A1=D0=B5=D1=80=D0=B3=D0=B5=D0=B9 With best regards Zhilkin Sergey --e89a8fb1f99e8572fa053e22cf19 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi all !=C2=A0
Get right response from server, with ma= cOS Sierra beta 10.12.1 (16B2338c) and=C2=A0Safari 10.0.1 (12602.2.14.0.1)<= /div>

2016-1= 0-04 15:59 GMT+03:00 arisawa <arisawa@ar.aichi-u.ac.jp>:
I can get proper response from http://plan9.bell-labs.com/sources/ by using mac/osx safari.

> 2016/10/03 2:42=E3=80=81James A. Robinson <jimr@highwire.org> =E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB= =EF=BC=9A
>
> So... Does Alcatel-Lucent have a problem with AppleWebKit
> users on principle?
>
> It looks to me as though my problem with browsing around
> under http://plan9.bell-labs.com/sources/ (and othe= r subpages)
> is because the server doesn't like the User-Agent string:
>
> $ telnet plan9.bell-labs.com 80
> Trying 135.104.24.16...
> Connected to plan9.bell-labs.com.
> Escape character is '^]'.
> GET /sources/contrib/ HTTP/1.1
> Host: plan9.bell-labs.com
> Connection: keep-alive
> Cache-Control: max-age=3D0
> Upgrade-Insecure-Requests: 1
> User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKi= t/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36
> Accept: text/html,application/xhtml+xml,application/xml;q=3D0.9,<= wbr>image/webp,*/*;q=3D0.8
> DNT: 1
> Accept-Encoding: gzip, deflate, sdch
> Accept-Language: en-US,en;q=3D0.8
>
> HTTP/1.1 200 OK
> Connection closed by foreign host.
>
> And here it is again w/o the User-Agent string:
>
> $ telnet plan9.bell-labs.com 80
> Trying 135.104.24.16...
> Connected to plan9.bell-labs.com.
> Escape character is '^]'.
> GET /sources/contrib/ HTTP/1.1
> Host: plan9.bell-labs.com
> Connection: keep-alive
> Cache-Control: max-age=3D0
> Upgrade-Insecure-Requests: 1
> Accept: text/html,application/xhtml+xml,application/xml;q=3D0.9,<= wbr>image/webp,*/*;q=3D0.8
> DNT: 1
> Accept-Encoding: gzip, deflate, sdch
> Accept-Language: en-US,en;q=3D0.8
>
> HTTP/1.1 200 OK
> Server: Plan9
> Date: Sun, 02 Oct 2016 17:29:09 GMT
> Connection: close
> Last-Modified: Fri, 14 Mar 2014 22:14:11 GMT
> Content-Type: text/html
>
> [... proper body returned...]
>
> I tried playing around with the UA value and found that if I change > AppleWebKit to something else such as AppleWebKis I get a
> response...
>
> Jim
>





--
=
=D0=A1 = =D0=BD=D0=B0=D0=B8=D0=BB=D1=83=D1=87=D1=88=D0=B8=D0=BC=D0=B8 =D0=BF=D0=BE= =D0=B6=D0=B5=D0=BB=D0=B0=D0=BD=D0=B8=D1=8F=D0=BC=D0=B8
=D0=96=D0=B8=D0= =BB=D0=BA=D0=B8=D0=BD =D0=A1=D0=B5=D1=80=D0=B3=D0=B5=D0=B9
With best reg= ards
Zhilkin Sergey
--e89a8fb1f99e8572fa053e22cf19-- From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 28 Oct 2016 14:30:53 -0700 From: Kurt H Maier To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20161028213053.GA50754@wopr> References: <20160929081227.GD70826@wopr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [9fans] Question re source trees Topicbox-Message-UUID: a7650624-ead9-11e9-9d60-3106f5b1d025 On Thu, Sep 29, 2016 at 11:54:03AM +0100, Richard Miller wrote: > > > > I can also supply bluetooth code for the pi3 if anyone is interested. > > > > > > > I am interested. Will it be part of your next pi release? > > Probably not for a while. I would have to write some man pages first. Is your contrib directory on sources the place this code will turn up when you release it? Or is there another release mechanism I should be monitoring? Thanks, khm