Re: [9fans] telnet to port (and webfs debug)
I did already tried this, but without success, but I tried it again just to be sure, still without success. I tried to telnet the proxy with telnet tcp!host!port and it worked as expected (GET http://www.google.com; printed its bloated html). This limit the issue boundaries to webfs (since, as far as I can see, hget is just a wrapper of it), since both squid and the tcp stack proved to work properly. The problem is, I can't figure out how to debug webfs. Any tip? Note that it worked once, a few days ago, when I managed to sysupdate (setting http_proxy.host in /usr/glenda/.hgrc). Giacomo 2015-02-12 17:27 GMT+01:00 cinap_len...@felloff.net: the httpproxy variable is read by webfs on startup only. webfs is usually started in your $home/lib/profile to provide http client service. just setting httpproxy before running hget or mothra has no effect on the proxy setting unless you start a new webfs instance. so try: httpproxy=http://proxy:port webfs hget http://www.google.com/ when that works, set the httpproxy variable at the top of your $home/lib/profile before webfs is started to make it permanent. -- cinap
Re: [9fans] telnet to port (and webfs debug))
hg is using ape port of python which comes with its own http library. wrote a hg extentsion that makes it use webfs instead, so i can keep my credentials in factotum/secstore: [extensions] hgwebfs= in your $home/lib/hgrc -- cinap
Re: [9fans] telnet to port (and webfs debug))
yes, patch would be welcome :-) -- cinap
Re: [9fans] telnet to port (and webfs debug)
On 13 February 2015 at 14:13, erik quanstrom quans...@quanstro.net wrote: does anybody remember what the hardware that inspired this was? and why proper marshalling code couldn't be written. It wasn't hardware: it was a large package of existing protocol code that needed to run but made too many assumptions about structure and structure member alignments, prompting the pragma.
Re: [9fans] telnet to port (and webfs debug)
User-Agent: Mozilla/5.0 (compatible; hjdicks) does anybody remember what the hardware that inspired this was? and why proper marshalling code couldn't be written. c structures can't really be trusted with memory layout. - erik
Re: [9fans] telnet to port (and webfs debug))
No webfs required! There's a factotum extension I wrote a while back that is bundled with Mercurial version 2.2+: http://mercurial.selenic.com/wiki/FactotumExtension. If you're using the mercurial contrib package from either jas or myself, it should be enabled by default. thanks to both you and jas for the work on hg. - erik
Re: [9fans] telnet to port (and webfs debug))
On Fri, Feb 13, 2015 at 5:59 AM, cinap_len...@felloff.net wrote: yes, patch would be welcome :-) No webfs required! There's a factotum extension I wrote a while back that is bundled with Mercurial version 2.2+: http://mercurial.selenic.com/wiki/FactotumExtension. If you're using the mercurial contrib package from either jas or myself, it should be enabled by default. Steve
Re: [9fans] telnet to port (and webfs debug))
On Fri, Feb 13, 2015 at 5:30 AM, Giacomo Tesio giac...@tesio.it wrote: Note that, strangely enough, hg ignores the .hgrc in your home directory. The hgrc(8) speak about Unix (and Windows) but since GNU is Not U... ehm... Plan9 is not Unix (:-D), I can't say where to write it. Hi Giacomo, This might explain some of what you are seeing: http://mercurial.selenic.com/wiki/Plan9FromBellLabs Your hgrc should be placed under $home/lib. Steve
[9fans] 9atom installation report on Acer C710 Chromebook
Hi, I have an Acer C710 Chromebook (http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/acer-c7-chromebook) with chromeos bootloader replaced with seabios+coreboot from John Lewis (https://johnlewis.ie/custom-chromebook-firmware/rom-download/). The machine used to work fairly well with this bootloader (except some glitches like non-working suspend/resume) with Debian GNU/Linux. The one I have has Celeron 1007u processor. This morning, I decided to install 9atom. The installation went quite well but towards the end, while it is compiling amd64 executables, I got a panic and a freeze. panic: cpu0: cclose 0xf01c45f8 dumpstack: disabled cpu0: exiting cpu1: exiting Will be be happy to help debug and get 9atom to run fine on this machine. It has got a 16GB SSD and 2GB RAM. I chose fossil+venti while formatting the disk. The installation process was the very smooth except for the above errors. Ramakrishnan
