On Sat Jul 25 23:09:49 EDT 2009, co...@bitworthy.net wrote: > > > Why is sysname= not documented in plan9.ini(8)? Just an oversight? > > > > because it's not set there. ndb/cs sets sysname. > > see comments in /rc/bin/cpurc. > > > > I got the notion that you can set sysname via plan9.ini from this doc: > > http://www.9grid.fr/wiki/plan9/Configuring_a_Standalone_CPU_Server/ > > About half way down the page, under the 'NETWORK DATABASE' section: >
however, doing it this way will cause ndb/cs to be confused. this can cause subtle problems. it's best to follow the convention. > in my terminal's plan9.ini, and after I reboot, /dev/sysname and $sysname > end up being set accordingly... I guess because anything put into plan9.ini > ends up as an env variable? yes. actually everything in plan9.ini will be in #ec. #ec is a subset of #e. > I realize it's totally "against the point" to have a _single_ plan 9 box; but > I doubt it's all that rare when you step outside the lab or the corporate > environment and peer into the domiciles of everyday people using plan 9 > at home for personal experimentation and educational purposes. i hope this isn't condecending, but if faced with that constraint, i would do as i suggested before. run a cpu/auth/fs and use drawterm to access it. when i really had one machine, i ran it as a terminal. but that wasn't much fun. i was pretty motivated to get a fs working. my home network consists of a ken's fs, a cpu server and a terminal. i also have a secondary fast cpu server and a secondary slow cpu server, that's generally in various states of disrepair as i break^wwork on things. a big system, can be a little more elaborate. coraid has a stand-alone auth server, and four other cpu servers and a stand alone fs. there are also a few dozen terminals. - erik
