Opened 17 years ago
Closed 17 years ago
#2161 closed bug (invalid)
r5 Terminal fails with message BShell: can't open a pty
| Reported by: | kaoutsis | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | - General | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Change History (3)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
While we can certainly introduce this feature to achieve compatibility in the more uglier cases, I don't really see the point for PTYs. At least I can't think of any software I would like to reuse from BeOS that uses it.
comment:3 by , 17 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
OK, closing as "won't fix" then.
Note:
See TracTickets
for help on using tickets.
The R5 Terminal apparently tries to open the slave end without O_NOCTTY (which didn't exist on BeOS) while not being a session leader. We're POSIX compliant in that we let that attempt fail. I don't think we should change this behavior.
We could theoretically let the runtime loader pass the GCC version info to the kernel, which could make it available to everyone interested in emulating R5 behavior, including the tty driver. I can't think of any R5 application using ptys, that we would actually want to use under Haiku, though, so I'm not really inclined to do that.
Opinions?