On Fri, Nov 01, 2013 at 01:17:50PM -0400, Mouse wrote:
> > As zero-length symlinks aren't sensible, this should probably be
> > prohibited. Does anyone see any reason they shouldn't be?
>
> I think "not sensible" is not a good enough reason to prohibit
> something.
Yeah yeah, but still nowad
On 2 Nov, 2013, at 03:33 , Alan Barrett wrote:
> On Fri, 01 Nov 2013, Greg Troxel wrote:
>>> But if NetBSD enables PPS on ucom, there's going to be an expectation that
>>> it is good enough for stratum-1 timekeeping, like PPS on real serial ports.
>>
>> I don't think there's any such expectatio
> Does anyone see any reason they shouldn't be?
If it ain't broken don't fix it?
Hubert
smime.p7s
Description: S/MIME cryptographic signature
On Fri, 01 Nov 2013, David Holland wrote:
rmind@ points out that it's possible to create zero-length
symlinks. As zero-length symlinks aren't sensible, this
should probably be prohibited. Does anyone see any reason they
shouldn't be?
Symlink names should satisfy all the rules for file system
On Fri, 1 Nov 2013 14:48:51 -0400
"Terry Moore" wrote:
> But using a serial port handshaking line over an emulated com port over USB
> is not likely to be terribly wonderful. Long-term accuracy (tick count)
> probably no problem, but jitter it will depend on how that's filtered.
That's the ke
On Fri, 01 Nov 2013, paul_kon...@dell.com wrote:
I don't know this API. But my first reaction when I saw the
designation "PPS" is to think of GPS timekeeping boxes and other
precision frequency sources that have a PPS output. On those
devices, the PPS output is divided down from the main osci
On Fri, 01 Nov 2013, Greg Troxel wrote:
But if NetBSD enables PPS on ucom, there's going to be an
expectation that it is good enough for stratum-1 timekeeping,
like PPS on real serial ports.
I don't think there's any such expectation created.
[...]
People who expect the same as serial PPS are
