Hi, May I ask to revisit this issue? To me ENXIO is not semantically correct in this particular case. It also turns out that doing workaround in userspace may not be that good as we used to think. I propose is to fix VT_WAITACTIVE so it simply wait for bound device activation. For my understanding this change should not have any impact on existing code. I also removed really strange console cleanup bit sticked in a long time ago (see ioctl() part). It will be nice to see this patch
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
| Linus Torvalds | Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series.. |
| Paul Jackson | Re: cpuset-remove-sched-domain-hooks-from-cpusets |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Linus Torvalds | Re: [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [klibc] [patch] import socket defines |
