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
for execution by a suitably authorized person. Therefore,
information beyond the code itself is necessary to determine malice.
Note, too, that there is nothing Lua-specific in the above argument.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents
record-keeping data space, and the code to do 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
not
be a problem. The more consistently the limits work, the better off
we are in the long run.
I've got the change implemented and the result builds. I'll be
experimenting to see whether it really does have the effect I want and
will report back here.
/~\ The ASCII Mouse
()?
/~\ 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 new
behaviour (and, of course, similar changes in the other places SIGXFSZ
is generated).
Comments or other thoughts?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1
Sorry for replying to the list, but Mouse refuses to accept mails
from .de domains.
Yeah, I should train myself to stop responding to list mail from .de
addresses, or at least use something like my netbsd.org address, until
and unless .de...no *smack* bad Mouse! No ranting onlist!
If you
; if a directory can have
multiple parents, walking parents until you get to the root becomes a
much less obviously possible thing to do.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39
in thinking 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
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
like any
other PPS support until you test the resulting time carefully.
/~\ 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
is unavoidable without special-purpose hardware,
simply because of interrupt latency. I'm worried that USB will make
that a lot worse, and most people will not be competent to expect that.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents
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
? Heavens! Didn't you know that's not the NetBSD way?
Seriously, this - or something of the sort - actually makes a lot of
sense to me as a resolution, here.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email
. Either
that or I'd use bidirectional buffer logic, so there is nothing like a
direct electrical connection between the SCA pins and the SCSI bus.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61
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
is basically the same all the way from 1.4T
through 5.x, so it seems to me it's _probably_ the same post-5.x.
/~\ 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
?
There certainly shouldn't be. (Well, assuming you mean
dump/newfs/restore, not dump/rm -rf */restore.)
But, of course, depending on what made things weird to begin with, it
could potentially happen again, which amounts to much the same thing in
practice.
/~\ The ASCII Mouse
to catch just such 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
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
already, that you don't have two partitions
overlapping.
/~\ 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
larger blocks, those two inodes fall into the same block; otherwise,
not. If they do, it might be interesting to look at the rest of that
block, in case its contents look recognizable.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo
[...] If all of this is true, maybe [EdgeBSD i]s a more suitable
place for your stuff now?
Possibly. They're welcome to my changes if they want them too. I'll
send a ping thataway.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo
? WSEMUL_MTERM?
tun(4)-for-IPv6? v6-capable SLIP? netstat -T? touch -d and -i?
In short...
NetBSD-current the main development branch for things that we know we
want, and that we are prepared to support for a long time, and that
mostly work.
...that.
/~\ The ASCII Mouse
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
like ucom0, not ttyU0.
/~\ 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
, that anyone has to agree with me, or care what I
think
/~\ 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
assuming you don't mind being slightly incompatible
with the rest of the world.
/~\ 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.
/~\ 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
I'd expect: write--flush dependency _is_ a DAG,
with barriers being chokepoints (I forget the graph-theory term for
them) in the DAG.
Mouse
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
that got to do with filehandles? Is st_ino now
generated from a filehandle somehow rather than being the filesystem's
responsibility?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7
required for all filesystems?
/~\ 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
something?
/~\ 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
for 4.0.1's raidctl -s output. They may need
fixing if yours looks different.
/~\ 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
#! /bin/sh
# Public domain
-size
directory entries.)
/~\ 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
VOP_READDIR(), etc.
Perhaps, but the type _is_ stored on the disk in recent
implementations. See src/sys/ufs/ufs/dir.h in 5.2, for example.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52
than I do could probably do a better job.
/~\ 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
bothered. (It's not something to do casually. According to
the doc, the device shall not accept an attempt to change the hard
limit if a previous change to the hard limit has been made since the
last power-on reset.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
anything useful with it;
at a stab-in-the-dark guess, I'd guess that it would depend heavily on
the particular BIOS in question - which at that point I'm no longer
sure deserves the B part of the name.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
Protected Area...and this thing,
whether an ld instance or something else, is not a normal disk drive;
for example, it usually will not be partitioned further.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email
-checked-out working tree), and
the patience to wait for git to fetch it, you can get it by cloning
git://git.rodents-montreal.org/Mouse/netbsd-fork/4.0.1/src.
Here are the one-line summaries. Except for 53fe079, the commit
messages are only one line long; 53fe079's explains how the interface
a little greater than the IDENTIFY-reported capacity. So
I assume I'm doing something wrong, and the obvious question is, what?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E
it, it will stay stuck at zero.
/~\ 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
.
I'm sure there are lots of other possible designs.
It may be better to do it with special-purpose opcodes (eg the SPARC's
ld*a and st*a instructions), but it is by no means necessary.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents
try experiments, if anyone has anything to suggest.
I also still have the pcap capture files, in case they might contain
anything of value. For now, I'm just using MTU 1500.
Any thoughts?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo
things. That's
why I snooped on both hosts.
If you haven't yet, try using tcp mounts as that tends to avoid
exercising some of those cases.
I've been wondering how TCP mounts would compare. Perhaps I'll try
them some one of these days.
Mouse
is straight or crossover.
(I also don't know whether that's relevant; I don't know enough about
how gigabit auto-x negotation works.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D
the stack trace is that
it's trying to page something out and finds itself wanting to page
something in to do so.
Is this a case of don't do that, then, or should this work and I just
need to track down a bug?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
!
/~\ 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
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.
/~\ 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
carefully compare prototypes, is a good thing.
Not, of course, that it's the only such offender. Consider enodev()
and its relatives (unless of course that botch has been eliminated in
modern versions, though this suggestion makes me suspect not).
/~\ The ASCII Mouse
- in the presence of
a flood of writes.
Thank you, people, for pointing me in such helpful directions!
/~\ 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
man page, ideally referring to the memory barrier specs.
I agree.
/~\ 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
is really satisfactory.
Of course, userland is not immune to the undocumented-interface problem
either. But I haven't seen it nearly as much there.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61
to use storage exported via iSCSI.
Did I miss something, or is the support just not 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
. Am I missing something?
/~\ 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
, though the latter I may be able to figure out
(mostly meaning, if I can find and identify the relevant kernel code).
Did I miss something, or is this just not documented?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents
Like mouse@ I am unaware of what makes ksem mandatory, [...]
Whatever is 'mandatory'.
Well, it was said to be...as jnemeth put it, it was made unconditional
on the basis that it is essential.
But if you use programs that require POSIX shared memory, you should
also offer POSIX semaphores
of users need it or a
large majority of systems need it are justification for this; examples
of optional things which I think should remain optional despite being
very popular are options INET and pseudo-device pty.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
[...] P1003_1B_SEMAPHORE [...]
The feature was condiational in the past, but made unconditional on
the basis that it is essential.
This leads me to ask, what is it essential to? I'm moderately sure
I've never used POSIX semaphores for anything.
/~\ The ASCII Mouse
PRU_DETACH handler calls, doesn't do this as far as I can see.
So I clearly am missing something. But what? What locking do I need
here, beyond of course the locking my AF code needs internally?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
, or is the Wikipedia page wrong, or what?
/~\ 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 interested.
An assembler comment - from something like:
asm volatile(; STR(__LINE__))
How is that any more effective in a macro than in an inline function?
What am I missing here?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents
char *, int, const char *);
I see a #define lurking !
Exactly. It's a #define that I don't think can be got rid of by using
a function, even an inline function, instead.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
both -- which
it won't, if you use macros...
Huh?
Okay, what's the static inline version of log() here?
#define log(msg) log_(__FILE__,__LINE__,(msg))
extern void log_(const char *, int, const char *);
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
is better.
/~\ 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
that
haven't been true since the days of the m68k, and the existence and
use of machines of that ilk is why.
/~\ 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
= new_thing1();
if (...failure...) bail(can't do it: %d %d (from %s),...);
...
}
(Okay, that's not quite true. Using always_inline doesn't necessarily
mean committing to gcc. But _depending on_ always_inline does, ISTM.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against
the how to sanely write error handling routines issue is
spurious. Such code always has, de-facto if not intended, some kind of
catchall behaviour.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D
of
read/write, not time of open. kill(2) checks UIDs at time of calling
kill(), not time of your getting the PID of the target. To name just
three examples.
Indeed, I think file descriptors are the odd ones out here, not the
other way around.
/~\ The ASCII Mouse
\ / Ribbon
whatever NetBSD
eventually decides on.
/~\ 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
-
of those points is impossible, nor that there are no other right
answers. However, since we've already got an implementation of (i),
the costs are heavily skewed in favour of retaining the status quo.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo
and should be treated as such,
which in NetBSD's case I would say means a quirk entry, documented as
being a workaround for broken hardware, for it.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8
authors? filesystem authors?
midlayer (eg scsipi) authors?)
/~\ 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
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
their sector size. (Yes, I consider it broken
for a disk to lie about its sector size.)
/~\ 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
important.
...in general, I agree, but in the case of DHCP, I'm not so sure. It
needs to send and receive packets to and from unusual IPs (0.0.0.0, I
think it is), if nothing else.
Mouse
files with little churn.)
/~\ 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
a stripe size that's a multiple of three.
/~\ 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
to
_require_ that the implementation error out if O_EXEC is combined with
one of the other three. (I would expect that to just be an application
error, which an implementation may choose to assign meaning to.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
help such a person.
I have them in the form of commits in a git repo. I can, of course,
generate diffs as desired; also, anyone who cares to (and has some
1.2gig to hold the result) is welcome to git clone
git://git.rodents-montreal.org/Mouse/netbsd-fork/5.1/src and look at
commits d9c27c0
these are good things to be able to
do is open to debate, of course.)
/~\ 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
for. (If, as is probably the case
in many such uses, that user is root, I have trouble seeing _any_ issue
here - anyone who can overwrite root-owned files pretty much pwnz0rz
the system already.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
.
/~\ 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
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 chrooted process either way.
/~\ 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 slightest bit of difference to them
what fexecve() does?
/~\ 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 supports?
I think treating the versions with a misleading f as standards
compatability goop is the right way to go here.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E
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
. :)
Mouse
and deletes but lots of I/O to the big files).
So far I've had no problems. But I also haven't been using WAPBL or
even softdep, nor 6.x. I don't know if that helps localize the problem
any
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo
If those two modules have bugs, the bugs should be fixed. [...]
Is it a bug to use pthreads?
In the case of security-critical software, yes, I believe it is.
In case it's not clear, I'm with Thor et al on this one.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X
must run as root. To pick another, the class of
machines on which apache is unnecessary is much, much larger than the
class of machines on which login and su (and, more generally, programs
which by default are built with PAM) are unnecessary.
/~\ The ASCII Mouse
show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386--netbsdelf...
(gdb) run
Starting program: /home/mouse/gdbtest
at which point nothing I've tried will wake it up, except for
SIGKILLing gdb from another
.
The program I'm using is up for ftp from ftp.rodents-montreal.org in
/mouse/misc/video-mmap.c. It's not long, 107 lines. The underlying
hardware in my case is i386 with a uvideo:
uvideo0 at uhub3 port 1 configuration 1 interface 0: Vimicro Corp. Venus USB2.0
Camera, rev 2.00/1.02, addr 2
with a
stupid mistake that could have been corrected with a careful reading of
the manpage and the code.
/~\ 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
) did I/O async, with sync calls just starting the operation
async and immediately blocking until it finishes. Indeed, the very
name of the operation (QIO) meant queue I/O. (This was fairly old
VMS by now; I don't know how close it is to modern VMS.)
/~\ The ASCII Mouse
on different assumptions and
thus talking past one 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
501 - 600 of 800 matches
Mail list logo
