gt; not work with DDB, though.
It also would not work for output. (Would it be possible to do the
same in the other direction? I would guess so, but I don't really know
enough to know.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
Sixel, Tektronix, ship it over the network, whatever.
Do we have the infrastructure for hot-plugging wsdisplays?
Virtualization, virtualization, all is virtualization
Mouse
t least for that one - there must be some other
explanation. Thank you!
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
g with anything else sending
something I don't recognize in the position of an HTTP verb.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
slightly different) NetBSD source trees.
Makes me wonder what the relevant difference is. Border router blocks?
Lack of HTTPS support? They don't recognize the interface I present?
They just haven't noticed me yet?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X
kernel just to
shut up each and every complaint is, IMO, misguided. (I don't know
which case this particular instance is. It's just that mrg's text
makes me feel it's a case of trying to contort the code to shut up the
tool for the sake of shutting up the tool, not for the sake of
ful?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
vice's
device-specific version; while I'm sure someone better at researching
such things could do better, it will be one thing needing doing.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
tter.
When applied to plain file, yes.
When applied to a device special pseudo-file, other semantics apply.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
ace in a filesystem file.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
abuse contacts, and those which don't respond,
or which support the misbehaviour, stay blocked; those which clean up
their act get unblocked. But I don't know how well that matches up
with NetBSD's tradeoffs.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Agai
octet of its
link-layer address. It returns char * (IMO it should be unsigned char
*, but they didn't ask me). There's also CLLADDR, which is the same
except it returns a const char * instead of a char *. I can't easily
check -current, because HTTP access to cvsweb has been broken; it n
ples I know of are sockets in transit in
SCM_RIGHTS messages, when the sender has closed its descriptor and the
receiver hasn't received it yet, and a few kernel-internal uses such as
the NFS client.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
AF_INET socket that is passed in this way?
Whatever the configuration calls for, of course.
That can't be done with per-packet filtering. That's why I think
per-packet filtering is a wrong place to try to satisfy this desire.
/~\ The ASCII Mouse
\ / Ribbon
d, and/or SCM_RIGHTS. Maybe sosend() and
sorecv().
But not, I would say, per-packet filtering.
And, of course, I'm armchair quarterbacking here. Whatever is
implemented here, it won't be by me.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
unchanged) contents need re-pushing. But, here,
we have _changed_ contents, changed by the client without anything else
changing the display, needing pushing.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
, well, people like kre know a lot
about what _should be_ fastest, but nothing beats actually measuring
performance with various values to see what truly _is_ fastest, on
_your_ particular hardware, with _your_ particular workload.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X
ning rust supports non-MSI
interrupts: it's a matter for the interface glue rather than for the
storage technology.
Admittedly, my understanding of nvme is hazy. Have I misunderstood?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodent
000;
}
bcopy(tvp, &lasttime, sizeof(struct timeval));
Obviously, this depends on the system not sustaining as many as a
million fetches of the time (gettimeofday() being only one of variousp
things which can call microtime()) per second for any significant
period.
/~\ The ASC
s good, bad, or just ugly, it looks to me as though
it's exposed a bug.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
l()
operations, either with more than three arguments or with the third arg
being a pointer to a struct.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
lls on NetBSD as
far as I can see.
Am I doing something wrong?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
the simple thing to do is to just grep for
PFIL_IFNET_ATTACH and PFIL_IFNET_DETACH and look at the surrounding
code to see what circumstances they're used in.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email!
1.kmod]: linker error: global symbol
> `MyFunctionName' redefined
Well, I don't use kernel modules, so this is just a guess. But maybe
create module_3 which defines MyFunctionName and make module_1 and
module_2 each depend on it?
/~\ The ASCII Mouse
\ / Ribb
o leave any part of the struct uio unchanged.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
SD ports use all-bits-0
for nil pointers, I think it is a bad idea to get used to assuming
that; sooner or later it will come back to bite you.
> Cannot be problem that I am using separate kernel thread for
> receiving data on socket ?
It seems unlikely to me, though I don't know 10.1 ne
ll, at first, you don't - and, indeed, under 5.2
there is no uio_segflg; if I were trying to do something like this in
5.2 I'd have to go digging to figure out where 5.2 records the
difference between userland and kernel when doing I/O.
/~\ The ASCII Mouse
\ / R
se. In most cases, when I've been working in the kernel, I've
either just run giantlocked or depended on running uniprocessor. (Even
uniprocessor kernels have _some_ locking issues, but they are greatly
reduced as compared to multiprocessor kernels.)
/~\ The ASCII
../diff/89a4f0d-8938bc4, instead of the path I gave last mail, to get
the fix.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
ff is available
from ftp.rodents-montreal.org, in
/pub/mouse/git-unpacked/Mouse/netbsd-fork/5.2/src/diff/89a4f0d-a744955
(also available over HTTP, though when I look at that view it renders
somewhat brokenly - I *think* this is just a rendering issue), in case
anyone is interested. And, as always, the
et *so;
[...]
if ((error = fd_getsock(fd, &so)) != 0)
return error;
It would make the most sense, I would say, for you to look at what the
kernel you care about does in such calls when it wants to map a
userland-provided socket fd to its internal data struct
le instead of
a namei walk. There is the case of having two things mounted on the
same path, but that shouldn't be unsolvable.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
into my older
versions or invented it and pushed it upstream.
> That still gives me EIO.
Figures. :-( Oh well. I suppose it was worth trying
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email!
lt;30 ticks
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
be write a tiny
program to just call unmount(2) with "/foo/bar" and maybe MNT_FORCE?
(I'm assuming the client system is NetBSD.) Might not work, but it
sounds to me as though you don't have much to lose by trying it.
/~\ The ASCII Mouse
\ / Ribbon C
als may be useful as part of it; the same is true of socketpairs
and probably various other things.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
even be using the result. But it _is_ another
example of something that already showed up decades ago (the uV2 dates
from...the mid-'80s, I think, certainly pre-1990), and it seems to me
it is unlikely to be the last example.
/~\ The ASCII Mouse
\ / Ribbon Cam
mmer/winter time ("DST")
moves civil day boundaries as expressed in UTC.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
has other hackery in the kernel, none of which I have
tried to push upstream because I think it doesn't belong in NetBSD.
If I want a kitchen-sink kernel I know where to find Linux.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@
and as far as I know it
was never rolled forward into any other version. But you're welcome to
look at the 1.4T code.
It's present in my mutant 1.4T tree. My primary distribution mechanism
for that is a world-clonable git repo
(git://git.rodents-montreal.org/Mou
uses
/dev/kmem to fetch it. (This one is unidirectional; I don't think
I've ever quite dared to use /dev/kmem to write into the kernel for
anything but debugging hackery.)
I'm sure there are plenty of other possibilities. These are just the
ones I offhand recall usi
out of space, so presumably there's some use case
I'm missing where that's useful.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
But I'd also say that this failure is clearly a bug
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
routine, freeaddrinfo().
asprintf() is a harder case, because freeing is up to the caller.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
t that effect?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
hat renders strncpy() (not strlcpy - that was my mistake)
incapable of upholding its interface contract is, IMO, not suitable for
general-purpose use such as building - or working under - NetBSD.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
e kernel.
(As a personal example, I find the macros a substantial
impediment to understanding code - while admittedly I don't know
whether they are shared with other OS projects, in my limited
experience they are NetBSD-specific.)
/~\ The ASCII Mouse
\ / Ribbo
ely be rejected given this prototype, no?
No, char * in the prototype should be compatible with char * restrict
in the definition, especially in view of what restrict actually means.
(It should also be compatible with char * const and the like; don't
confuse char * X with X char *.)
/~\ The
he ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
of(bar.prop)
...
else
...
trusting dead code elimination to remove the unused arm (which
therefore likely will not get tested and thus can harbour a latent bug
until ported to a machine with unusual foo.name and/or bar.prop sizes).
/~\ The ASCII
> strncpy() has the advantage of working nicely and predictably
> regardless of whether the known buffer's length is that of the source
> or that of the destination. I.e. one can use it to copy a known
> number of possibly (or definitely) unterminated chars from an array
> of a given length into a
what they think is a correct copy using whatever you pick instead while
still getting it wrong one way or another.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
It's not just that the monitor can't handle
1280x1024, though; a much older application release runs under DOS at
1280x1024 and works fine.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
ENT and -ENOMEM and the like, also a Linux signature).
Unfortunately the issue manifests for only one customer, on the far
side of the planet, so the change-test-debug cycle time is on the order
of days. And the monitor that provokes the issue is expen$ive enough
that getting another one for tes
> At work, we just tried to build a 9.1 kernel with the i915drm line
> uncommented [...]
Doh! amd64. My apologies for forgetting to say.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D
both GENERIC and ALL, but it's commented
in both (yes, even in ALL). Is it expected to work, or is this
something that should have been deleted entirely?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email!
e...low.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
volved disappearing from USB).
I may investigate more someday, but probably not soon, since, as I
think I said upthread, I've found a more effective workaround (ignore
the filesystem entirely).
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
gt; into generating what the Pico wants.)
> Or just install this package?
> cross-arm-none-eabi-gcc-8.3.0nb5 GCC for bare metal ARM EABI
8.3.0? Much too recent for me. (Besides, pkgsrc isn't interested in
supporting me.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
I haven't tried to chase it down, since, as
thorpej said, there is actually no filesystem in the usual sense there.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
wn code for it, probably including writing an ARM assembler.
(I think I have a DNARD somewhere, but I suspect I will find writing my
own assembler easier than bludgeoning the NetBSD/arm toolchain into
generating what the Pico wants.)
/~\ The ASCII Mouse
\ / Ribbon Campai
fields.
I'll be experimenting more, but if anyone has any thoughts I'd welcome
them.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
eboot again (from single user).
That...surprises me. I'd have to dig through the FFS support to have
any idea what's behind that.
> I still wonder how /etc/rc.d/resize_root handles this.
So do I!
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
ystem mounted read-only,
it doesn't much matter how you got to that state. But I _think_ you
can't convert a read/write mount to read-only without an unmount, which
for the root filesystem means a reboot.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
ple, on i386 or amd64, a and c often begin at
the same place, with c bigger, so if a is mounted read-only you can
mount c read/write for this kind of trick.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
;not working at all",
but, obviously, that's not relevant to the existing hardware.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
nly the Q1900M *looks* like a
newer design.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
are just too cheap.
I may have to do some such. I'll see what Vantec has to say. (In
particular, I don't want to do anything permanent to this card while
there's still some chance I may need to RMA it.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
or ASRock
has done something odd or my particular Q1900M has a duff "x16" slot,
because it doesn't work. I think my quad wm is a x1 card; if I can
find the silly thing I'll try it in the ASRock to see if the slot
itself works.
/~\ The ASCII Mo
8102 0x00092810 0x0041a023
0xd0: 0x00220040 0x 0x 0x
0xe0: 0x 0x00140392 0x 0x000e
0xf0: 0x00010003 0x 0x 0x
I hope the above includes whatever you'd be looking for!
/~\ The ASCII
97b product 0x0585.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
ry slightly broken, returning the right vendor/product numbers
but trash in other fields? I'll have to investigate.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
hinks GUI glitz is more important than functionality. But
I *think* I didn't get any additional drives listed (not surprising in
view of the above).
I'll experiment a bit more. I think I have another machine with a PCIe
slot (I once had a quad wm in there, but I can't recall whether
r something needs configuring to run the
x16 slot at more than x1. The card does say it needs a x4 or higher
slot to work, so if the x16 slot is running x1 (is that even possible?)
that might be responsible.
Any thoughts? Any pointers to where I might usefully look?
/~\ The ASCII
ormally the buses they want to actually have.
Of course, then you have people wondering why the new device attachment
line they added isn't working. But you'll have that potential for
_any_ design with a "silently drop this line" semantic.
/~\ The ASCII
#x27;s what I'd want (to my limited understanding, this is close
to what "no virtio" does at present).
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
er than copying all the bytes.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
'fuse-sparsetest' that makes metadata
> available for inspection later about the writes it sees. But that's
> hard to write.
You could get much of that information by ktracing and looking for the
relevant calls - {,p}write{,v} and lseek seem to me to be the most
likely cand
ic, I actually think you will have trouble even
_defining_ what "100% right" is for this test, since everything about
sparseness, right down to whether it's even a thing, is
filesystem-dependent.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
se, that depends on you having the resources (disk space,
time, and energy/motivation) to do that.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
building it. (If trying to build a new kernel SEGVs, maybe
cross-build it?)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
nderlying machines? I'm wondering
if perhaps something is broken in a subtle way such that it manifests
on only certain hardware (I'm talking about something along the lines
of "this tickles erratum #2188 in stepping 478 of Intel CPUs from the
Forest Lawn family").
/~\ Th
nly don't mind losing it for
long enough to find everything using TCP "OOB".
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
't so badly broken, but I doubt I'd
actually find any use for the latter. I might rip out the OOB stuff
just to find and fix anything trying to use it, though.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Em
's case, it is defined to drop data while sarching for the IAC DM
that makes up part of a synch; ignoring the urgent bit means that
dropping won't happen. (Does that matter in practice? Probably not,
especially given how little TELNET is used outside walled gardens. But
it still is a correctnes
terface that exposes the
urgent popinter _properly_?), and provided your and the peer's
implementations agree on which sequence number goes in the urgent
field.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
quot;The distinction between
some of the fields in the events and revents bitmasks is really not
useful without STREAMS.").
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
priority levels to data?
That's part of what I was wondering.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
> Also, I suspect mouse was thinking of the TCP URG concept, and not
> PUSH when he wrote what he did, but I don't know for sure.
Ouch. Yes, you are entirely correct in that regard. Total braino on
my part. My apologies.
/~\ The ASCII Mouse
\ / Ribbon
not, but I figured it was still workt asking.
>> ... I'd still be curious where it came from.
> Those answers are CVS:
Not where it came from in the sense of who committed it or what it
looked like at the time, but rather where that person got the various
distinctions from.
/~
historical accident that should be fixed, but, even
if that reading is correct, I'd still be curious where it came from.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
needs are relatively simple, but still.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
> Thanks Mouse and Martin. I got past that error. But now I'm running
> into another problem - unable to determine when write op occurs (to
> be able to return ENOSPC error).
> I want to return ENOSPC error whenever write occurs. Which variable
> contains this info? I'
l, actually, I'd start by rereading the code, but I assume you've
already done that.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
and 44 long). So I think it's fair to
say that, in the right context (an important caveat!), a time
difference as short as (1602-802)/44.1=18.14+ milliseconds is clearly
discernible to me.
This is, of course, a situation designed to perceive a very small
difference. I'm sure there
er quick tests, but trying
to figure out an issue on a version I don't use except at work is
something I am unmotivated to do on my own time, and using work time to
dig after an issue that doesn't affect work's use case isn't an
appropriate use of work resources.
/~\ The ASCII
get repeated signals.
But then, so is every other ITIMER_REAL I've ever used.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
do that, I'm not sure
> correct POSIX periodic timers can attain a target _average_ interval
> between expirations [...]
I would argue that it's misleading, to the point I would call it
incorrect, to call such a thing "periodic".
/~\ The ASCII
1 - 100 of 1008 matches
Mail list logo