Searched hist:202274 (Results 1 - 5 of 5) sorted by relevance
| /freebsd-10.1-release/lib/libc/gen/ | ||
| H A D | ttyslot.c | diff 202274 Thu Jan 14 03:40:05 MST 2010 ed Phase out ttyslot(3). The ttyslot() function was originally part for SUSv1, marked LEGACY in SUSv2 and removed later on. This function only makes sense when using utmp(5), because it was used to determine the offset of the record for the controlling TTY. It makes little sense to keep it here, because the new utmpx file format doesn't index based on TTY slots. |
| H A D | ttyname.3 | diff 202274 Thu Jan 14 03:40:05 MST 2010 ed Phase out ttyslot(3). The ttyslot() function was originally part for SUSv1, marked LEGACY in SUSv2 and removed later on. This function only makes sense when using utmp(5), because it was used to determine the offset of the record for the controlling TTY. It makes little sense to keep it here, because the new utmpx file format doesn't index based on TTY slots. |
| H A D | Symbol.map | diff 202274 Thu Jan 14 03:40:05 MST 2010 ed Phase out ttyslot(3). The ttyslot() function was originally part for SUSv1, marked LEGACY in SUSv2 and removed later on. This function only makes sense when using utmp(5), because it was used to determine the offset of the record for the controlling TTY. It makes little sense to keep it here, because the new utmpx file format doesn't index based on TTY slots. |
| /freebsd-10.1-release/libexec/getty/ | ||
| H A D | ttys.5 | diff 202274 Thu Jan 14 03:40:05 MST 2010 ed Phase out ttyslot(3). The ttyslot() function was originally part for SUSv1, marked LEGACY in SUSv2 and removed later on. This function only makes sense when using utmp(5), because it was used to determine the offset of the record for the controlling TTY. It makes little sense to keep it here, because the new utmpx file format doesn't index based on TTY slots. |
| /freebsd-10.1-release/include/ | ||
| H A D | unistd.h | diff 202274 Thu Jan 14 03:40:05 MST 2010 ed Phase out ttyslot(3). The ttyslot() function was originally part for SUSv1, marked LEGACY in SUSv2 and removed later on. This function only makes sense when using utmp(5), because it was used to determine the offset of the record for the controlling TTY. It makes little sense to keep it here, because the new utmpx file format doesn't index based on TTY slots. |
Completed in 193 milliseconds