On Nov 10, 2008, at 3:27 PM, erik quanstrom wrote:
At least in case of cpu(1) the magic is a bit perverse and quite
unlike the rest of the system. The way notes are managed make
a local end of a cpu(1) jump through considerable hoops in order
for the notes to be properly delivered. That was a sad
On Mon, Nov 10, 2008 at 5:04 PM, andrey mirtchovski
<[EMAIL PROTECTED]> wrote:
> I don't remember if the solution for note sending across machines was
> novel. I seem to remember that in this case processes were addressed
> by node/pid.
>
>
I've got it somewhere, will rummage around.
ron
> I would like to be able to import the /proc (or similar) filesystem from
> the remote machine and bind it over the files that my local kernel uses
> to send notes to the proxy process. That's how my "ideal world" model
> would work. Observe how that was also the first suggestion on the "notes
> t
On Mon, 2008-11-10 at 16:42 -0700, andrey mirtchovski wrote:
> > ... would you really honestly say that rolling out your
> > own notes forwarder is a *neat* trick? As opposed to
> > be able to use basic system's FS functionality?
>
> ok, how would you implement it, then? how would you deliver a no
> ... would you really honestly say that rolling out your
> own notes forwarder is a *neat* trick? As opposed to
> be able to use basic system's FS functionality?
ok, how would you implement it, then? how would you deliver a note to
a process that's running on a remote machine? would you be introd
> At least in case of cpu(1) the magic is a bit perverse and quite
> unlike the rest of the system. The way notes are managed make
> a local end of a cpu(1) jump through considerable hoops in order
> for the notes to be properly delivered. That was a sad discovery.
>
> Another discovery was that
cpu is just great tutorial.
notes forwarder, well, I am stil unsure.
ron
On Mon, 2008-11-10 at 14:49 -0800, ron minnich wrote:
> On Mon, Nov 10, 2008 at 2:24 PM, Roman V. Shaposhnik <[EMAIL PROTECTED]>
> wrote:
>
> > At least in case of cpu(1) the magic is a bit perverse and quite
> > unlike the rest of the system. The way notes are managed make
> > a local end of a c
On Mon, Nov 10, 2008 at 2:24 PM, Roman V. Shaposhnik <[EMAIL PROTECTED]> wrote:
> At least in case of cpu(1) the magic is a bit perverse and quite
> unlike the rest of the system. The way notes are managed make
> a local end of a cpu(1) jump through considerable hoops in order
> for the notes to b
On Mon, 2008-11-10 at 01:55 +0900, sqweek wrote:
> On Thu, Oct 23, 2008 at 8:43 AM, Roman V. Shaposhnik <[EMAIL PROTECTED]>
> wrote:
> > The only question is -- where such a note
> > is supposed to be sent to?
> >
> > Can someone, please, educate me on the moral equivalent of process
> > groups, s
>I'm not really sure what magic is involved in the DEL interrupt.
rio (or ip/telnetd, or ... some other user program).
On Thu, Oct 23, 2008 at 8:43 AM, Roman V. Shaposhnik <[EMAIL PROTECTED]> wrote:
> The only question is -- where such a note
> is supposed to be sent to?
>
> Can someone, please, educate me on the moral equivalent of process
> groups, sessions and their relationships with #c/cons ?
Maybe you worke
On Wed, 2008-10-22 at 10:54 -0600, andrey mirtchovski wrote:
> > This has one or two complications. There is no way to interrupt or kill
> > the foreground process. Instead, ctrl-c interrupts 9vx itself.
>
> chris,
>
> one of the nice things about the Plan 9 graphics system is that rio is
> in
I was playing around with the modified "win" program and I realized
it's not going to work due to the propensity of acme to redirect
standard error to a separate window. This environment has no way of
notifying anyone that a new window has opened without being requested
except visually.
A better s
> you have to type 'scroll' and middle-click it with the mouse (is there
> a way to issue this as a command from the terminal, anybody?). also,
one would think that
; echo noscroll>/dev/wctl
would work, but it does not.
- erik
my previous message was meant to include a small addition which I
omitted by accident and which turned out to be wrong anyway. here is
the rest of the picture.
I presume that there is no program to read the text on the graphical
9vx terminal (which would be required in order to "visualize" rio), s
> This has one or two complications. There is no way to interrupt or kill
> the foreground process. Instead, ctrl-c interrupts 9vx itself.
chris,
one of the nice things about the Plan 9 graphics system is that rio is
in no way different than any other graphical program. it reads and
writes file
On Wed, 2008-10-22 at 12:28 -0400, erik quanstrom wrote:
> rio does provide most everything one would need for a "text-mode"
> interface. unfortunately, you can't currently "tail -f" /dev/text. perhaps
> such a change would be easier and more general
That's a very good point! It hadn't occurred
> >> > Hello,
> >> >
> >> > Rio is the responsible for killing a process using the Del key, AFAIK
> >> > there is no way to terminate a program running in console. May be with
> >> > some magic combination of the keys ctrl-t ctrl-t X.
> >>
> >> Why not write a simple 'shell' shell (heh) that co
>> * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [081022 11:16]:
>> > Hello,
>> >
>> > Rio is the responsible for killing a process using the Del key, AFAIK
>> > there is no way to terminate a program running in console. May be with
>> > some magic combination of the keys ctrl-t ctrl-t X.
>>
>> Why n
On Wed, Oct 22, 2008 at 12:42 PM, erik quanstrom <[EMAIL PROTECTED]> wrote:
> you mean like, uh, rio or acme? ☺
i can't see why it would be a bad idea to do something like
this for text-only mode. it'd be a nice exercise, if nothing else.
it should be possible to do without writing a file server,
* erik quanstrom <[EMAIL PROTECTED]> [081022 13:51]:
> > * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [081022 11:16]:
> > > Hello,
> > >
> > > Rio is the responsible for killing a process using the Del key, AFAIK
> > > there is no way to terminate a program running in console. May be with
> > > some
> * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [081022 11:16]:
> > Hello,
> >
> > Rio is the responsible for killing a process using the Del key, AFAIK there
> > is no way to terminate a program running in console. May be with some magic
> > combination of the keys ctrl-t ctrl-t X.
>
> Why not write
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [081022 11:16]:
> Hello,
>
> Rio is the responsible for killing a process using the Del key, AFAIK there
> is no way to terminate a program running in console. May be with some magic
> combination of the keys ctrl-t ctrl-t X.
Why not write a simple 'shell
Hello,
Rio is the responsible for killing a process using the Del key, AFAIK there is
no way to terminate a program running in console. May be with some magic
combination of the keys ctrl-t ctrl-t X.
gabi
-- [EMAIL PROTECTED] wrote:
>
>Last night I downloaded 9vx. It works fine from a termi
Last night I downloaded 9vx. It works fine from a terminal, using
the following invocation:
../9vx.Linux -g -u glenda
where -g is the option to run sans GUI.
This has one or two complications. There is no way to interrupt or kill
the foreground process. Instead, ctrl-c interrupts 9vx itself.
Any
26 matches
Mail list logo
