(Added the list to CC:)

From: John Cowan <xxxxxx@ccil.org>

Date: Saturday, August 10, 2019 12:46 PM

I agree with all of these. What is more, I think the priority procedures should be flushed altogether. By the time you have asked for the priority, it has changed, and you really should never set the priority unless you are running real-time processes.

So leave nice in this one for the process SRFI's use, and don't implement priority or set-priority for it/them?

Furthermore, system-name is gethostname(), but it turns out that (at least on glibc systems) gethostname() is a lie: it just returns what uname -n returns, which is not a value you can rely on for opening network connections. So I think it should be flushed as well.

Ditto? I'm still working on the list of removals, and uname is in it.

- Harold

On Sat, Aug 10, 2019 at 12:29 PM <xxxxxx@ancell-ent.com> wrote:

In 3.2 I/O, dup->fdes

Everything in 3.4 Processes, including sub-headings

In 3.5 Process state:

parent-pid

process-group
set-process-group

priority
set-priority

Which leaves nice for priority setting.

In 3.8 System parameters, system-name, which belongs in a networking SRFI for talking to other processes not necessarily on the system

All of 3.9 Signal system:

signal-process
signal-process-group

In 3.12 Terminal device control:

open-control-tty

become-session-leader

tty-process-group
set-tty-process-group

control-tty-file-name

- Harold