Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller

I used Ka/Kb/Kc (upper case) for my Fairchild Clipper port, but that doesn't work on case-insensitive file systems. I did once make the changes for unicode, but again there can be problems with non-Plan9 file systems, even now. On Tue, 30 Oct 2018 at 12:43, Ethan Gardener wrote: > On Tue, Oct

Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller

, 6l amd64 .7 7a, 7c, 7l arm64 .8 8a, 8c, 8l 386 .9 p9p, 9[acl] power64 On Tue, 30 Oct 2018 at 09:35, Anthony Martin wrote: > Charles Forsyth once said: > > I had a chart somewhere with the available non-unicode letters. > > I made one a few years ago. It's at http://pbrane

Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller

It's z because the Atmel AVR is the last thing you'd want to use. (As usual, once you've got C going, it's ok, except for the design bugs.) They were in the Berkeley mote, which we worked on years ago, later on custom hardware, but always with completely different software from Berkeley's. I had li

Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller

He wants something I think that generates code that will run on unixy systems, and there isn't one, except in specialised ways. On Sun, 28 Oct 2018 at 14:20, Skip Tavakkolian wrote: > Inferno sources include kencc that build on the target os/arch. > > On Sun, Oct 28, 2018, 5:41 AM wrote: > >> R

Re: [9fans] zero copy & 9p (was Re: PDP11 (Was: Re: what heavy negativity!)

> I'll see if I wrote up some of it. I think there were manual pages for the >> Messages replacing Blocks. > > Here are the three manual pages https://goo.gl/Qykprf It's not obvious from them, but internally a Fragment can represent a slice of a Segment*

Re: [9fans] zero copy & 9p (was Re: PDP11 (Was: Re: what heavy negativity!)

They are machines designed to run programs most people do not write! On Mon, 15 Oct 2018 at 19:20, hiro <23h...@gmail.com> wrote: > > Also, NUMA effects are more important in practice on big multicores. Some > > of the off-chip delays are brutal. > > yeah, we've been talking about this on #cat-v.

Re: [9fans] zero copy & 9p (was Re: PDP11 (Was: Re: what heavy negativity!)

rom others. > >>> But some experiments in nix and in a thing I wrote for leanxcale show > >>> that > >>> some things can be much faster. > >>> It’s fun either way. > >>> > >>>> El 13 oct 2018, a las 23:11, hiro <23h...@

Re: [9fans] zero copy & 9p (was Re: PDP11 (Was: Re: what heavy negativity!)

I did several versions of one part of zero copy, inspired by several things in x-kernel, replacing Blocks by another structure throughout the network stacks and kernel, then made messages visible to user level. Nemo did another part, on his way to Clive On Fri, 12 Oct 2018, 07:05 Ori Bernstein, w

Re: [9fans] PDP11 (Was: Re: what heavy negativity!)

Ideally, anyway. On Mon, 8 Oct 2018 at 11:20, hiro <23h...@gmail.com> wrote: > saving every bit of memory has costs in coding, the pressure wasn't as > strong any more. > the earned flexibility can be used for more elegant design. > >

Re: [9fans] Is Plan 9 C "Less Dangerous?"

Plan 9 C implements C by attempting to follow the programmer's instructions, which is surprisingly useful in systems programming. The big fat compilers work hard to find grounds to interpret those instructions as "undefined behaviour". On Sun, 2 Sep 2018 at 17:32, Chris McGee wrote: > Hi All, >

Re: [9fans] Is Plan 9 C "Less Dangerous?"

The Plan 9 C compiler doesn't take an insane view of the meaning of "undefined behaviour", which makes a big difference. It also assumes you know how to write loops if they need to be fast (which frankly hasn't really mattered at the O/S level, esp on modern hardware), so it won't "optimise" essent

Re: [9fans] A compiler bug

I've fixed the immediate problem I think in a local copy but I want to eliminate another difference between targets before publishing the change. On Thu, 2 Aug 2018 at 15:20, wrote: > > Fwiw, the bugs in 6c and 8c where the cast fails was fixed in 9front > > with https://code.9front.org/hg/plan9

Re: [9fans] A compiler bug

Oh. I meant that I'd fix it. On Thu, 2 Aug 2018 at 01:29, Bakul Shah wrote: > On Aug 1, 2018, at 4:35 PM, Charles Forsyth > wrote: > > > even so, the format and intention of the example seems practical (with > the correct cast to uintptr) and "An implementation

Re: [9fans] A compiler bug

"6.6 Constant expressions" doesn't allow a cast from a non-arithmetic type to an arithmetic one generally, and a cast in an address constant can only cast from an integer constant to a pointer type (eg, char *reg = (char*)0x123450); the one example with 8c escaped with a warning ("initialize point

Re: [9fans] Acme create new file

Type B filename in the tag of an existing frame in the directory and execute it with button 2; or type B filename as a command in that directory in a win frame or rio window. On 13 May 2018 at 02:22, Chris McGee wrote: > Hi All, > > I’ve been using acme for a while and really enjoying the capab

Re: [9fans] Spectre and Meltdown

If Intel sells you lemons, make lemonade (ok, ok, at least a whiskey sour). I myself welcome our new speculative overlords, and look forward to new interesting predictions, and perhaps even a renewed interest in single-address space systems, since that's what we've got. On 10 January 2018 at 21:43

Re: [9fans] R.I.P cs.bell-labs.com

"we never know when plan9.bell-labs.com will be back." Yes, yes we do. Not. On 5 January 2018 at 16:35, David du Colombier <0in...@gmail.com> wrote: > > How about contrib? It would be nice to have something to fall back on > > when the plug is finally pulled. > > We could use the /n/sources/cont

Re: [9fans] R.I.P cs.bell-labs.com

0in...@gmail.com> wrote: > > Didn't Charles Forsyth have a github or similar such repository with a > copy > > of the Labs sources? That was even seeing sporadic updates? I'm sure I > > browsed it last fall, but I can't find it now. > > Few years

Re: [9fans] Why Plan 9 uses $ifs instead of $IFS?

WAT! or should that be "wat!" On 17 October 2017 at 22:49, Jules Merit wrote: > Gun Control UTF8, sgi 0xfbc bowling for columbine > > On Tue, Oct 17, 2017 at 2:45 PM, Jules Merit > wrote: > > E4M1 Charles, dm > > E3M8 Dis 9/11 > > > > On Tue, Oct 17, 2017 at 2:12 PM, Jules Merit > > wrote:

Re: [9fans] Why Plan 9 uses $ifs instead of $IFS?

> > since for example the original Rc paper still referred to $IFS. really? the only references to IFS I can find are in comparisons of $ifs to the Bourne shell's $IFS On 17 October 2017 at 16:05, Giacomo Tesio wrote: > Really? Just aesthetics? :-o > I supposed it had some practical goal I was

Re: [9fans] Killing another user's process

lower case kill restricts the list to processes of the invoking user initial cap Kill doesn't do that. for lower case kill, you can @{rfork n; echo -n none >/tmp/none && bind /tmp/none /dev/user && kill tftpd} you wouldn't normally of course but aspects of that command might be instructive On 25 J

Re: [9fans] equality sign in Rc

On 15 May 2017 at 17:44, trebol wrote: > > = is part of rc syntax, like {} and (), and it interprets it, not the i'd forgotten about the = in >[2=1], so you'd need another exception ... rc would interpret that, but then in [a-b=] it presumably wouldn't again...

Re: [9fans] equality sign in Rc

On 15 May 2017 at 19:33, trebol wrote: > $-fu must be equivalent to $^-fu, $^x is a syntax error, and not $x. $^x would be "whatever $ is" concatenated with literal "x" but "$" by itself is a syntax error

Re: [9fans] equality sign in Rc

On 15 May 2017 at 17:44, trebol wrote: > I suppose this is the perfect answer to my silly question: why not permit = > after the start of a command? > do that, but make it behave like = before the start of the command. rc provides the outer syntax for all commands, as it does for file matching a

Re: [9fans] equality sign in Rc

On 15 May 2017 at 17:30, Giacomo Tesio wrote: > % echo "$--fu" > rc: null list in concatenation > wrong quotes. try echo $'--fu' h% --x=hello h% echo $'--x' hello

Re: [9fans] Blocking on write

On 15 May 2017 at 16:46, Giacomo Tesio wrote: > Shouldn't the waserror code check that the queue has been actually closed? Either that or check errstr against Ehungup, since that's the exact error it incurred. The latter has the advantage of not obscuring a different error if the pipe is closed

Re: [9fans] equality sign in Rc

On 15 May 2017 at 16:54, Erik Quanstrom wrote: > if we implement the right thing, then arguments like --fu=bar will be > 'eaten silently' from the perspective of the (human) operator. sure gigo, > but this seems extra hard o get right in a Unix environment. It would be better then to leave thi

Re: [9fans] equality sign in Rc

On 15 May 2017 at 16:37, Erik Quanstrom wrote: > I implemented the Unix mistake as this hack is for p9p. I'm not sure I > like it. it's interesting to note that = is still not allowed in a list. Great. So now there are two different rc conventions. perhaps {} should be treated specially after

Re: [9fans] equality sign in Rc

On 15 May 2017 at 12:54, Charles Forsyth wrote: > and = would be handled by rc uniformly. It also wouldn't break anything, because nothing currently can use unquoted =, and things that used quoted = would work just as before.

Re: [9fans] equality sign in Rc

On 15 May 2017 at 12:54, Charles Forsyth wrote: > = would be handled by rc uniformly. Just as file name patterns are handled by the shell for all commands.

Re: [9fans] equality sign in Rc

The original aim was to implement named parameters that the shell would parse and pass to the command. That was frustrated in UNIX because there was one command (dd) that used = in its syntax. There are no such commands in Plan 9, except mk, but mk is interesting because mk treats those as entries

Re: [9fans] Blocking on write

On 15 May 2017 at 11:05, Giacomo Tesio wrote: > Is there any fs/device in Plan9 that can easily provide such behaviour? Bind #| to a name and fill up one of the data files (blocks at 256k on my system, might be 32k on small ones).

Re: [9fans] equality sign in Rc

Given > broken! one=1 two=2 echo $one $two > 1 2 > What should the following do? one=1 echo two=2 $one $two Disregarding a UNIX historical mistake, I'd expect 1 2 > broken! echo one=1 > one=1 >

Re: [9fans] equality sign in Rc

On 13 May 2017 at 13:36, trebol wrote: > You can force rc to setting a variable only if = is surrounded by spaces, > like in sh, but then you'll have a lot of problems in plan9/p9p. That isn't sh's rule. x=y is fine as an assignment without spaces. Shell/environment variable assignments appear

Re: [9fans] equality sign in Rc

On 13 May 2017 at 15:21, trebol wrote: > No with hyphenation, my friend! ahh! that's a little more specific. I usually switch it off so I wouldn't have noticed.

Re: [9fans] equality sign in Rc

On 13 May 2017 at 13:36, trebol wrote: > Then I used troff to write a paper, and surprise!, there is no utf8 > support. I'm fairly sure there is in troff.

Re: [9fans] Starting rio on combined CPU, file and auth

On 5 May 2017 at 02:22, Alex Musolino wrote: > > "CPU servers typically don't have any reason to run rio on a local draw > device." > I don't even bother including the draw device and hangers-on in cpu servers.

Re: [9fans] pipe: bug or feature?

On 28 March 2017 at 01:05, arisawa wrote: > the program reads a file and writes it to one end of pipe and then reads > it from another end of pipe. > the buffer for writing pipe is named buf0, and for reading pipe is named > buf. > The general problem with this is that a pipe is a full-duplex co

Re: [9fans] coherence function in kernel (especially in raspberry pi port)

On 28 March 2017 at 19:21, yoann padioleau wrote: > but I fail to understand the meaning of S and B. Synchronisation Barrier

Re: [9fans] coherence function in kernel (especially in raspberry pi port)

On 28 March 2017 at 19:21, yoann padioleau wrote: > For example I see this code in bcm/taslock.c > > coherence(); > l->key = 0; > coherence(); > > bcm/taslock.c seems actually mostly a copy paste of port/taslock.c > with an extra call to coherence before the assignment abo

Re: [9fans] SHA-1 collision and venti

lies on that > behavior. > As for venti, I wouldn't say 'no point' to an algorithm update, but > I'd rather have fossil updated to manage to deal with collisions > better first. > > > On Mon, Feb 27, 2017 at 8:14 PM, Bakul Shah wrote: > > On Mon, 27

Re: [9fans] SHA-1 collision and venti

On 27 February 2017 at 18:30, Charles Forsyth wrote: > that's a separate argument that venti would never work for you, regardless > of the hash algorithm used. since venti returns the resulting score from each write, and it knows whether there's been a collision, it appears i

Re: [9fans] SHA-1 collision and venti

On 27 February 2017 at 17:28, Bakul Shah wrote: > My argument is that an archival system that can't store some files, no > matter how they were generated, is not good enough. A hash collision > researcher may have a legitimate reason to store such files. > that's a separate argument that venti

Re: [9fans] SHA-1 collision and venti

On 27 February 2017 at 16:47, Charles Forsyth wrote: > On 27 February 2017 at 15:46, Dave MacFarlane wrote: > >> Why not skip sha-256 and go directly to Sha3? > > > blake2 has also been suggested also, it's not clear it's urgent for venti. the scam is to mak

Re: [9fans] SHA-1 collision and venti

On 27 February 2017 at 15:46, Dave MacFarlane wrote: > Why not skip sha-256 and go directly to Sha3? blake2 has also been suggested

Re: [9fans] SHA-1 collision and venti

On Sun, 26 Feb 2017, 18:49 Bakul Shah, wrote: > The links are to different files. > Not on Gmail at least look to see where each link points. Both are to -2 in the message I see on Gmail. Unless it cleverly optimised the"identical" content!

Re: [9fans] SHA-1 collision and venti

On 26 February 2017 at 17:30, Jules Merit wrote: > there is a backdoor when a score of 4, what data produces it i have no > idea. > where is that? I had a quick look but couldn't find it.

Re: [9fans] SHA-1 collision and venti

It's curious that svn "corrupts" the repository, if that's really what they mean, when two leaf files collide. An index or directory colliding with a file would be more understandable. On 26 February 2017 at 18:16, Charles Forsyth wrote: > > On 26 February 2017 a

Re: [9fans] SHA-1 collision and venti

On 26 February 2017 at 17:25, Bakul Shah wrote: > Venti is similarly corruptible, right? Since the checksum is over just the > content. If you downloaded https://shattered.io/static/shattered-1.pdf > and > https://shattered.io/static/shattered-2.pdf,

Re: [9fans] Upspin - a respin of 9p?

I see it as being orthogonal or complementary to various other existing facilities, including 9P, ix, 9Pcloud, CliveTalk, etc, not competing or replacing as such, although it obviously owes something to earlier projects; and I think it can be immediately useful to me in various contexts.

Re: [9fans] Upspin - a respin of 9p?

On 23 February 2017 at 17:44, Aram Hăvărneanu wrote: > Upspin does not currently work on Windows, but if you need Go on > Windows you don't need to use the Go installer, unzipping the zip file > will suffice (and works in any directory) > That's useful for the future, thanks. I wanted it on a bi

Re: [9fans] Upspin - a respin of 9p?

To install this distributed file system software on my Windows machine, I need to install Go, which is too big for what remains on the built-in drive, so I pointed it at a removable one, and the installer gives the diagnostic "Installation directory must be on a local hard drive", which is slightly

Re: [9fans] Upspin - a respin of 9p?

On 23 February 2017 at 09:34, Bakul Shah wrote: > What seems to be missing is the namespace splicing (no bind or mount). That's a function of the operating system (or not), even with 9P, so nothing here rules that out. There are some interesting possibilities.

Re: [9fans] Upspin - a respin of 9p?

On 23 February 2017 at 09:00, Charles Forsyth wrote: > (That isn't a criticism: both this and 9P-like things have their place.) And you can point the name server at other services, and store public keys in the key server, which has possibilities.

Re: [9fans] Upspin - a respin of 9p?

I don't think it's a reworking of 9P. It's closer to an older style of distributed file system, closer to Amoeba's or the Cambridge Distributed System, and using full-content storage operations on content accessed through a separate and global name service. 9P (and relatives) allow a huge assortmen

Re: [9fans] Update APE

On 21 February 2017 at 04:12, Kurt H Maier wrote: > with the possible > exception of Forsyth's 9k repository [1], which doesn't appear to have > got much updating recently. > Yes, I've been busy with things other than Plan 9 to try to make ends meet.

Re: [9fans] adding TCP half-duplex close

On 5 February 2017 at 18:13, Bakul Shah wrote: > If they implement close correctly, they should be able to implement > close-read correctly, it being a pure subset. In theory :-) > > but they didn't, so it's useless. > As for SYN+data+FIN you had to have both sides properly implement rfc1644 >

Re: [9fans] adding TCP half-duplex close

It's a similar story with SYN+data+FIN to provide a basic reliable datagram. You can't rely on a consistent implementation (unless it's to defeat your purpose). On 5 February 2017 at 15:51, Charles Forsyth wrote: > > On 5 February 2017 at 05:23, Bakul Shah wrote: >

Re: [9fans] adding TCP half-duplex close

On 5 February 2017 at 05:23, Bakul Shah wrote: > I think shutdown(sock, SHU_RD) is mainly to let the sender generate an > SIGPIPE signal in case it has sent data on a closed direction of a > connection. But I think this is only for completeness. Almost always you’d > use close(sock). At least I h

Re: [9fans] adding TCP half-duplex close

it's also funny that the rationale seems to be to pass the same conformance test for Go that once had it added to Inferno so it would pass a Java test but it was never otherwise used for reasons already given, so I took it out again. On 4 February 2017 at 10:11, Charles Forsyth wrote: &g

Re: [9fans] adding TCP half-duplex close

at 09:58, Charles Forsyth wrote: > > On 4 February 2017 at 01:56, Skip Tavakkolian > wrote: > >> Shutting down the write-end (i.e. 'shut_wr'), should send FIN, and >> transition to Finwait1. > > > i'd make it a "read" or "write"

Re: [9fans] adding TCP half-duplex close

On 4 February 2017 at 01:56, Skip Tavakkolian wrote: > Shutting down the write-end (i.e. 'shut_wr'), should send FIN, and > transition to Finwait1. i'd make it a "read" or "write" parameter to the existing "hangup" message. older implementations that don't accept the parameter will give an erro

Re: [9fans] QIC-80

a qic-120 drive or better and the symbios scsi card, but i've also used an adaptec 1542(?). first i copied them onto zip drives(!) and later onto sata, and later still onto sd On 31 January 2017 at 19:24, Anthony Sorace wrote: > This is a bit of personal archeology, but has anyone read QIC-80 ta

Re: [9fans] Why getenv replaces \0 with spaces in the returned value?

p and I can't see any issue. > > > Giacomo > > > 2017-01-18 21:13 GMT+01:00 Charles Forsyth : > > Yes, it's the lists. Nothing will cope with \0 in a C string, so it's a > good > > choice as list of string element separator. > > > >

Re: [9fans] Why getenv replaces \0 with spaces in the returned value?

Yes, it's the lists. Nothing will cope with \0 in a C string, so it's a good choice as list of string element separator. On 18 January 2017 at 19:21, Fran. J Ballesteros wrote: > rc lists? > > > El 18 ene 2017, a las 17:45, Giacomo Tesio escribió: > > > > Hi, last night I noticed this strange p

Re: [9fans] create/create race

On 30 November 2016 at 21:51, Charles Forsyth wrote: > that the whole path name is re-evaluated 3 times That doesn't happen with the current implementation, because it walks to the parent directory, does the create/open etc at that point with a reference held.

Re: [9fans] create/create race

On 30 November 2016 at 16:16, Giacomo Tesio wrote: > Also I'm looking for "instances that *want* the existing effect", as > Charles perfectly described them, something that break without it, so that > I can dive deeper into the matter. cat >x x: already exists rm x cat >x # different race mk x

Re: [9fans] create/create race

On 30 November 2016 at 15:28, Giacomo Tesio wrote: > I will use the new create syscall (without OEXCL support) when I need such > level of control and use ocreate with OEXCL Perhaps I'm confused. I thought OEXCL was just the same as the 9P create, which is what you were trying to get. With OEXC

Re: [9fans] create/create race

On 30 November 2016 at 15:02, Giacomo Tesio wrote: > > But reading that thread I can't actually see why the OEXCL path has been > taken instead of eliminating the race mapping the syscall to the 9p message. > I mean except backward compatibility. > I suppose you'll find out, but I'd expect that

Re: [9fans] create/create race

On 30 November 2016 at 13:32, wrote: > interesting, the thread starts here: > > http://marc.info/?l=9fans&m=111558704718788&w=2 > I suspect the discussion predated 9P2000 and the introduction of the OEXCL option.

Re: [9fans] Job interview questions

On 10 November 2016 at 06:03, Andrew Simmons wrote: > 9) What is the difference between Javascript and jQuery It's funny about JavaScript. (Never mind jQuery.) Given the heart-thumping power of even modern little devices, there's no reason whatsoever why they couldn't implement proper

Re: [9fans] Job interview questions

On 10 November 2016 at 06:03, Andrew Simmons wrote: > 6) Can you explain the request Flow in Asp.Net MVC > The correct answer is "Is that an African or an English MVC flow?" (the point being that it changed significantly between ASP.NET MVC 5 and the replacement ASP.NET Core MVC)

Re: [9fans] Purism laptops

On 11 November 2016 at 18:51, James A. Robinson wrote: > Have folks seen https://puri.sm/ ? Their description of how they are > trying > t > They look quite nice

Re: [9fans] Job interview questions

On 10 November 2016 at 06:59, Kurt H Maier wrote: > > 7) Explain Dependency Injection > > This is what we call passing arguments. > In the newer ASP.NET Core, they've ramped it up by extensive use of reflection, so your program ends up trapped in a hall of mirrors, and you've no idea w

Re: [9fans] arm platform with sata and multiple nics

On 4 October 2016 at 09:04, hiro <23h...@gmail.com> wrote: > what's a sata+ NIC? Some of the Pi Hats/Shields are odd: I've got one that's got both a SATA interface of some sort and a separate NIC interface.

Re: [9fans] arm platform with sata and multiple nics

There are several Rpi Hats with sata and sata+ NICs, for use with SSDs, although I haven't had time yet to look at driving the ones I've got. On Tue, 4 Oct 2016, 03:35 michaelian ennis, wrote: > are two features I've seen sought after on this list. This just popped up > on Kickstarter. > > https

Re: [9fans] More about /dev/draw

On 29 May 2016 at 13:44, Dave MacFarlane wrote: > Why would the alpha channel work differently with the same image from the > same code with the same hardware > depending on the driver? > Because there might be a difference in the way the components inside the pixel word are being interpreted or

Re: [9fans] More about /dev/draw

On 28 May 2016 at 18:23, Dave MacFarlane wrote: > Does anyone have any pointers? I'd check that the image you're drawing with S over D isn't filled with a completely transparent value if the image has got an alpha channel.

Re: [9fans] bug in authdial()

On 20 May 2016 at 23:04, Skip Tavakkolian <9...@9netics.com> wrote: > i'm a little confused by the discussion of il + tcp on authdial > causing the delay. if ndb/cs returns multiple dial strings, dialmulti > function (/sys/src/libc/9sys/dial.c) dials them all in parallel > (rfork) and the first o

Re: [9fans] problem with acme on 9front

On 19 May 2016 at 21:11, stanley lieber wrote: > at the cost of stepping all over the rest of the (Plan 9) system ?

Re: [9fans] problem with acme on 9front

On 19 May 2016 at 19:40, Siarhei Zirukin wrote: > Please consider upgrading to sam instead. > Any experienced acme user will quickly start banging the desk in frustration if thrown back into sam. Incredibly clumsy by comparison; not fluid. sam -d is useful for certain types of scripting.

Re: [9fans] bug in authdial()

It's not just il. There are other networks, other protocols, other than tcp and IP. It's one of the advantages of plan 9 that it's easy to try and use new ones. cs could present a different search list when there's only one way to get somewhere. as a quick fix for everything, if you're not using il

Re: [9fans] bug in authdial()

On 18 May 2016 at 01:43, arisawa wrote: > - p = netmkaddr(nt->val, netroot, "ticket"); > rv = dial(p, 0, 0, 0); > if(rv >= 0) > break; > > + p = netmkaddr(nt->val, “tcp", "t

Re: [9fans] Inferno in a browser window

On 13 May 2016 at 01:03, Skip Tavakkolian wrote: > There is (was) a browser plugin The original one ran in Internet Explorer. I think the bits are still included in emu/Nt, but I'd be surprised it if still worked. It was a response to the contemporary "browser as operating system" discussion. W

Re: [9fans] cpu command latency

On 11 May 2016 at 14:44, Kenny Lasse Hoff Levinsen wrote: > Delete the channel from /srv in the loop to test a full remote mount > dance, including the initial dial. It shouldn't take 3s to dial, though. There's something initially slow in connecting to grid.nyx.link with cpu, and setting up,

Re: [9fans] cpu command latency

On 11 May 2016 at 10:04, arisawa wrote: > latency data between japan and other country will be enough. > > I want to have those times: > for(i in 1 2 3){ > time cpu -h HOST -k ‘dom=DOM’ -c pwd > sleep 3 > } > they are c > It takes ages to get throu

Re: [9fans] A couple questions about /dev/draw and /dev/kbmap

On 5 May 2016 at 14:56, wrote: > libdraw determines the iounit in initdraw() and sizes > its write buffer accordingly. uploading pixels into a image > will split the y/Y operation in multiple ones so they fit > into the buffer. > Yes, and the data doesn't go through rio (unlike an older system),

Re: [9fans] Go on Plan 9?

On 13 April 2016 at 15:42, Charles Forsyth wrote: > On 13 April 2016 at 15:39, Richard Miller <9f...@hamnavoe.com> wrote: > >> If you want to get to the satisfying ALL TESTS PASSED message at the end >> of the go install+test process, you will need a swap file, >

Re: [9fans] Go on Plan 9?

On 13 April 2016 at 15:39, Richard Miller <9f...@hamnavoe.com> wrote: > If you want to get to the satisfying ALL TESTS PASSED message at the end > of the go install+test process, you will need a swap file, > That's insane. Really.

Re: [9fans] Go on Plan 9?

On 13 April 2016 at 14:08, Chris McGee wrote: > I believe that my rpi only has the 512MB of RAM so I’ll add swap. It should be enough to increase the available virtual space by changing that #define. It won't need a swap file unless the program forces all that to be allocated, which it shouldn'

Re: [9fans] Libc locks documentation

If you look for "condition variables" for event notification, you'll find relevant material, such as this paper https://www.cs.berkeley.edu/~brewer/cs262/Mesa.pdf which has a few references in it too. There's a little evolutionary history of them somewhere. On 24 March 2016 at 19:56, Giacomo Tesio

Re: [9fans] Inferno hosted on Plan 9 for Raspberry Pi?

On 5 March 2016 at 17:36, Brian Vito wrote: > I'm hoping to be able to get Inferno > running hosted on Plan 9 (which runs very well for me on the Raspberry Pi). > It looks as though I did that last July. It needs an update to asm-arm.s to save and restore floating-point status, if you're using f

Re: [9fans] Plan 9 port to Raspberry Pi 3 Model B (ARM64)?

The 32-bit subset of ARMv8 is (supposedly) better specified at the system level than ARMv7 (ie, by the v8 architecture itself). There are some cores that do just the 32-bit subset of v8, but apparently Cortex-A53 will do 64 as well, which I hadn't realised from the Rpi3 announcement I saw. On 3 M

Re: [9fans] Fwd: Multiplexing Styx/9P2000 over TCP connections

so at each end there's a 9P client and server, but part of the same logical conversation (the flipside of the original conversation). As sometimes happens, the need for it went away, so I never did write it, but I thought it might be fun. > > So, do Plan 9 or Inferno already do anything li

Re: [9fans] Fwd: Multiplexing Styx/9P2000 over TCP connections

On 3 March 2016 at 02:09, wrote: > I recently posted the following to the Inferno mailing list (but > received no response). I'm re-posting here, as this applies to Plan 9 > just as much as to Inferno, anyway... > Sorry. You asked some interesting questions but I was busy with something else wh

Re: [9fans] Plan 9 port to Raspberry Pi 3 Model B (ARM64)?

On 3 March 2016 at 14:50, Richard Miller <9f...@hamnavoe.com> wrote: > cpu0: 1200MHz ARM Cortex-A53 r0p4 it's ARMv8-A!

Re: [9fans] Plan 9 port to Raspberry Pi 3 Model B (ARM64)?

On 3 March 2016 at 14:50, Richard Miller <9f...@hamnavoe.com> wrote: > requires three new > instructions that 5a doesn't know about ... > Possibly. I added some of the control instructions where there was consistency in definition and they were needed more than once.

Re: [9fans] bug in exportfs

On 15 February 2016 at 01:05, arisawa wrote: > filtering of exportfs is handy if it works well. > ... The whole short discussion was useful, thanks. It gave me a few ideas, prompted by exportfs, including about filtering.

Re: [9fans] startboot signature

On 17 February 2016 at 08:19, Giacomo Tesio wrote: > Out of curiosity, why the startboot function in port/initcode.c is `void > startboot(char *argv0, char **argv)` given the argv0 is ignored? > > I see that this simplify various main() in init9.s but I wonder why not > simply use `void startboot

Re: [9fans] file descriptor leak

On 16 February 2016 at 15:52, arisawa wrote: > > I have observed warning messages from dns server: > dns 30792: warning process exceeded 100 file descriptors > dns 30888: warning process exceeded 200 file descriptors > It's worth noting that this message doesn't necessarily mean you've got a fil

<    1   2   3   4   5   6   7   8   9   10   >