[9fans] bundle //GO.SYSIN DD
Hi 9fans, Does anyone know what the meaning/origin of //GO.SYSIN DD in bundle(1) is? I've seen this on other unix-likes as well, but I thought I'd ask here since the awareness of historical context seems to be quite a bit above average on this list. Thanks, Sander.
[9fans] CPU Server Wiki, auth/keyfs, and password for the machine.
In the Wiki on configuring a standalone cpu server, there is a part that says to run auth/keyfs to provide a password for the machine. Assuming a fresh install, this is done while logged in as glenda. Is this really necessary? Is it different from zeroing the nvram and then entering authid, password, etc.? Someday I'll actually understand the authentication pieces here: keyfs, factotum, secstore Thanks. Greg
Re: [9fans] bundle //GO.SYSIN DD
I first saw it used in bundling software created by James Gosling, and liked the (relevant, I might add) joke so much I put it in the Plan 9 version. -rob
Re: [9fans] CPU Server Wiki, auth/keyfs, and password for the machine.
In the Wiki on configuring a standalone cpu server, there is a part that says to run auth/keyfs to provide a password for the machine. Assuming a fresh install, this is done while logged in as glenda. Is this really necessary? Is it different from zeroing the nvram and then entering authid, password, etc.? Yes, and yes. Auth/keyfs is the authentication database. It holds key info for every user in the authentication domain it serves, including whatever user the cpu server itself runs as. Filling out the nvram sets the info that gets used to initialize the cpu server's factotum. Like any other factotum, it needs to have a key that matches the one in authentication database. Auth/keyfs could plausibly preinitialize the entry for the host owner using the nvram key, and that would be fine most of the time, but not always. (It is possible to boot in one auth domain but load an auth/keyfs and be an auth server for a second domain. This is why, for example, users with accounts on the auth server sources.cs.bell-labs.com can mount its fossil but not cpu to the machine.) Russ
Re: [9fans] CPU Server Wiki, auth/keyfs, and password for the machine.
Thanks Russ for the typically thoughtful and informative reply. You are perhaps the most valuable resource on any mailing list anywhere. There ought to be an award or something. The reason I ask is that I missed that step the first time I tried to set up the CPU/Auth server, but I've since gone through it all again carefully more than once, and I stll get connection rejected with my Ken's file server. (Yes I know fossil/venti is the current standard, but what can I say, I'm, perhaps irrationally, or at least non-rationally, attached to the old file server.) The problem is, other than going through the Wiki and 9fans archives, which I've done, I don't have any notion of how to find out where I went wrong. I successfully set this up in the past. I did remember to add IL back to pccpuf, and, as I said, I followed the Wiki. I'm at a loss. Any pointers appreciated. Greg On Jul 26, 2008, at 12:15 PM, Russ Cox wrote: In the Wiki on configuring a standalone cpu server, there is a part that says to run auth/keyfs to provide a password for the machine. Assuming a fresh install, this is done while logged in as glenda. Is this really necessary? Is it different from zeroing the nvram and then entering authid, password, etc.? Yes, and yes. Auth/keyfs is the authentication database. It holds key info for every user in the authentication domain it serves, including whatever user the cpu server itself runs as. Filling out the nvram sets the info that gets used to initialize the cpu server's factotum. Like any other factotum, it needs to have a key that matches the one in authentication database. Auth/keyfs could plausibly preinitialize the entry for the host owner using the nvram key, and that would be fine most of the time, but not always. (It is possible to boot in one auth domain but load an auth/keyfs and be an auth server for a second domain. This is why, for example, users with accounts on the auth server sources.cs.bell-labs.com can mount its fossil but not cpu to the machine.) Russ
Re: [9fans] Plan 9 on Blue Gene
On Sat, Jul 26, 2008 at 1:37 PM, Steven Vormwald [EMAIL PROTECTED] wrote: Is there any (public) information about how plan 9 is/was being used on Blue Gene? The only information I can find seems to be press release-type papers that just say that it runs on Blue Gene, but not what it was used for nor how it was setup and used. The existing BG/L port was a prototype proof of concept. It was not done in a clean-room fashion and so large portions of it are not releasable. The proof of concept was done as part of a proposal to a DOE funded project which just got under way. As part of that project which is funded for the next three years, we'll be doing a clean port to the BG/P (which will be open sourced) along with using Plan 9 to explore large scale (tens of thousands of nodes) distributed systems. High level details are available off of the IBM Research pages: http://domino.research.ibm.com/comm/research_projects.nsf/pages/hare.index.html -- more detailed information to come. -eric
Re: [9fans] CPU Server Wiki, auth/keyfs, and password for the machine.
The reason I ask is that I missed that step the first time I tried to set up the CPU/Auth server, but I've since gone through it all again carefully more than once, and I stll get connection rejected with my Ken's file server. (Yes I know fossil/venti is the current standard, but what can I say, I'm, perhaps irrationally, or at least non-rationally, attached to the old file server.) connection rejected is a message the file server prints in the IL stack. I believe it has nothing to do with authentication, but I also don't know what the criteria are for rejection. You can test connectivity using aux/9pcon: cpu% aux/9pcon -n tcp!web.mit.edu!9fs aux/9pcon: dial: connection refused cpu% If it does connect (which I doubt), you can try starting a 9P session: cpu% aux/9pcon -n tcp!sources.cs.bell-labs.com!9fs Tversion 8192 9P2000 - Tversion tag 65535 msize 8192 version '9P2000' - Rversion tag 65535 msize 8192 version '9P2000' Tattach 1 -1 rsc '' - Tattach tag 3 fid 1 afid -1 uname rsc aname - Rattach tag 3 qid (0002 0 d) cpu% 9pcon has no prompt; I typed the Tversion and Tattach lines. Your server will probably reply to the Tattach with an Rerror; sources is special. Russ
Re: [9fans] odd out-of-memory behavior
If you can make it happen again, you could try to run acid -k -l kernel 1 /386/9pccpu # or your kernel image stacks() it's not immediately obvious what i am doing wrong: akin# acid -k -l kernel 1 /386/9pccpu /386/9pccpu:386 plan 9 boot image /sys/lib/acid/port /sys/lib/acid/386 /sys/lib/acid/kernel acid: include(acid) acid: include(procacid) acid: stacks() = 0xf0312008 1: init dennis pc 0x8984 Await (Wakeme) ut 2 st 2 qpc 0x stdin:5: (error) no stack frame: can't translate address 0xf001bf30 - erik
Re: [9fans] odd out-of-memory behavior
it's not immediately obvious what i am doing wrong: akin# acid -k -l kernel 1 /386/9pccpu /386/9pccpu:386 plan 9 boot image /sys/lib/acid/port /sys/lib/acid/386 /sys/lib/acid/kernel acid: include(acid) acid: include(procacid) acid: stacks() = 0xf0312008 1: init dennis pc 0x8984 Await (Wakeme) ut 2 st 2 qpc 0x stdin:5: (error) no stack frame: can't translate address 0xf001bf30 i forgot to say you should mappc() first. the pc kernel maps some extra data memory below the text segment, which isn't accounted for in the default acid map. russ
