Re: [9fans] 'wall' messages

[rt@anothy.9srv.net]

// After all rio runs from a rc prompt.

the process, of course, might not be around. see exec in rc(1).

// So track the initial connection and...

*who* tracks the initial connectin? you're adding complexity here,
either directly to rc (which is likely unproductive for the above
reason, among others) or to the OS (some sort of "reporting
mechanism", most likely).

// ...not being a /dev, that's a simple issue of creating a logical
// alias on that initial rc connection into /dev/display/*.

uh, what? i'm going to have something *pretend* to be a graphics
device, just for the purposes of system notices? and how does it
tell other gui apps (or how do they all figure out) that it's not
a *real* graphics device? again, added complexity. part of the
"everything is a file, and *just* a file" model, with plan 9's
namespace system, means that the only way these apps know what's
what is convention. apps *assume* /dev/draw is a graphics device.
you could put your net or audio device there without issue, but
thigs are gonna get fsck'd up.

what hoops are you worried about users jumping through? we (or
the guys at the labs) make a change to /sys/lib/newuser to start
some listener, or /rc/lib/rcmain sources some system-wide
startup, containing reasonable defaults. plumber starts every
time i log in, my apps know how to talk to it, and i get all
these "magical" benifits of things working nicely together, all
without any hoop-jumping.

i have no idea what you're concerned about here.