that will be blindingly obvious once I see 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
on whether the comments are accurate). The major
difference I see between what I think you're suggesting and the sparc64
way is the use of a userland utility versus autoconf machinery.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents
with wdc_ofisa
attach wdc at pcmcia with wdc_pcmcia
com is another example. So is le. I'm sure there are plenty of
others. In some cases they don't even need the with stuff, I think.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents
).
But a single node, a single instance of a driver (eg, ne0), always has
at most one parent (exactly one, I think, except for the autoconf root
most ports call mainbus).
To put it another way, the autoconf tree is a tree, not a dag.
/~\ The ASCII Mouse
\ / Ribbon Campaign
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
potentially vary
with the filesystem; this is no different.
What am I missing?
/~\ 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
removal in the filesystem makes sense.
I'm not sure whether I'd prefer to do it with a new and idiosyncratic
syscall, a vfs.something sysctl, some sort of filesystem-level analog
to ioctl, or what.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
about it being
possible to make it safe against hostile users), and (c) get
directories right.
/~\ 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
misinformation.
/~\ 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 off entirely.
/~\ 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
maintenance) of pervasive manual uglification of code to fix
non-errors.
/~\ 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
anyway) or
uglify the code to work around the warning [ok, my phrasing]. I
believe the former is better, because in my experience the mistake the
warning warns about is anything but common.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo
that, but even without threading, there are at least two ways
I can think of offhand that a file descriptor, once opened, can end up
in multiple processes' open file tables: fork() and SCM_RIGHTS. (There
are probably others, too.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X
the implementation of foo(). (If you expect
to use vprintf or relatives to consume the first ... list, this
involves unwarranted chumminess with the stdarg implementation. But if
you walk the first ... list yourself, it's no problem at all.)
/~\ The ASCII Mouse
\ / Ribbon
used it very much and never rolled it forward (it was 1.4T I
added it to). Never even got around to adding it to -Wformat.
As for using nonstandard formats, don't we already do that with %b?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo
of changing if you want to run something else instead
strike me as the biggest ones.
/~\ 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
sure other people have their own uses for long pathname components,
too, though I don't know of any offhand.
/~\ 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
a size that doesn't exist on that port. Is uint32_t
32 bits or at least 32 bits? THe former may well not exist on a
pdp10 port.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39
. Not that I've put all _that_ much effort into
looking; finding needles in haystacks is not exactly my forte - unless
the needles are bugs and the haystacks are code.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email
the damage for purposes of this email.
What about embedded? [...]
What about machines with multiple keyboard/screen heads [...]
I'd argue that embedded is a degenerate case of lights-out, [...]
Certainly defensible.
The multi-bottle+keyboard ( possibly mouse, though last we met
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
properly called FFS, and I think using the ufs
name as part of something that is filesystem-independent is a mistake.
If nothing else, it will confuse humans.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email
cost
is..substantially lower.
/~\ 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
-in-1 test trips, long-lived systems _will_ lose their RNGs. I
think this is suboptimal.
Indeed, a hardware RNG that _didn't_ fail that test once in a while
would be suspect.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents
for a load to reach global visibility?
/~\ 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
implicitly push writes to main RAM, or whatever
else is necessary to make them visible to other CPUs? (A reordering
barrier does not necessarily imply a global visibility barrier.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents
on others) or not - you may
have seen my note to the list asking - but those are needed too; if
they are part of the mutex routines, then your skeleton code is
correct, though your explanation omits part of the reason why.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against
(at
least optionally, and if it's optional then NetBSD runs the hardware in
that mode).
Correct? If so, that completely annuls the hairiest of my worries.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email
filesystem interfaces that represent such things as
strings, I think they are far enough off that it is much too early to
try to design them in here.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61
depth even if there aren't any more Makefiles for it to find.
I think the point still stands.
/~\ 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
broken.
/~\ 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 pulling together multiple mails from tls here. The second-level
quotes are from varying people; I've marked their authors according to
the info I have.]
[Mouse]
Revealed to userland, of course.
Combined with the conservative approach to estimating how much
entropy was put into the pool
bit. (The latter is one reason for
whitening input bits as they are gathered.)
These random number generators are things like the turbulence inside
disk drives and the noise in sound input.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo
whichever NetBSD this ends up in. I've pointed out the
problems; if NetBSD is determined to carry on regardless, that's its
lookout.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7
returns EOPNOTSUPP.
This is not to say that it shouldn't be cleaned up. Just that I don't
think it's actually nonconformant.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39
-governance. So I'll confine myself
to saying my respnse is at
{ftp,http}://ftp.rodents-montreal.org/mouse/ccTLD-thoughts.txt for
anyone interested. (Actually, will be at; as I send this mail, I'm
still writing it - the draft is available at
.../ccTLD-thoughts-draft.txt and I'll move it when I'm done
[...]
The short answer is that Mouse likes tilting at windmills. :-)
Eh. I think that is at least a little of a misstatement. I don't do
such things because I enjoy doing them. Quite the opposite.
I do them because I must.
I'm not entirely sure what I mean by that. It's difficult
a filesystem. I'll take
a filesystem with a nonzero probability of recovering something useful
from over one that guarantees to trash everything any day (other things
being equal, of course).
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents
You can make [your] point, but you won't win against Mouse as he just
doesn't care outside of his wall [...]
Yeah.
I used to. Then I realized that it was sucking away a huge amount of
time, energy, and stress tolerance, for, as far as I could tell, zero
benefit to anyone, including me
will be irreparable. Memory, CPUs, disks, and the
transports between them do fail, occasionally transiently.
/~\ 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
, back in the '80s
when I used it - start a new process to run something. You ran it in
the same process you ran everything else in.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7
. :-)
/~\ 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 a great
way, but it certainly can work.)
/~\ 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 can't
reconstruct raid11, because it has no operational members. I can't
unconfigure it (preparatory to reconfiguring it), because it's held
open by raid0.
What's the right way to do this? Am I stuck needing a reboot?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X
A problem, already, and that's with no more than
a minute or so of thought.)
/~\ 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 machine in question is a production machine and
I'm not in the right city to deal with it personally.)
/~\ 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
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
--;
return(0);
#endif
}
So, yeah, I don't see any way out of this but 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
.
/~\ 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
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
for a
(supposedly-)production OS is not the place to be carrying out research
experiments, not even if another such OS is already doing it.
But my opinions seem to correlate negatively with NetBSD's these days.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
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
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
through
pipes and sockets - pretty much all places where octet strings of any
sort cross the user/kernel boundary.
/~\ 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
Why not use O_DIRECTORY (which is part of -current) and add that to
flags?
Backporting that might be a better alternative. What are its
semantics?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email
and make O_NOACCESS work
only when combined with 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
of those two checks, because
I can't see any reason wby O_DIRECTORY shouldn't be specifiable with,
eg, O_RDONLY.
Am I missing something important there? After how I missed something
pretty blatantly obvious before, I don't trust myself tonight.
/~\ The ASCII Mouse
at the three
commits ending with 5215f8f6551df407d7c87c8e6a80c7b04e9ee844 in the git
repo git://git.rodents-montreal.org/Mouse/netbsd-fork/4.0.1/src.)
The fact that the O_ flags were not intelligently specified aeons ago
so that a conversion is required is regrettable, but at this point
unfixable
access permissions at all. And, indeed, without calling device-level
open() routines and such.
This would also support what Mouse is trying to do,
Actually, I don't think it would, not without creating other problems.
If it addresses my desire, then it must keep a reference to the
underlying
the information in the wrong
place. Is there any way it could be set as an option at mount time?
(That's a serious question; I don't know puffs enough to answer it.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email
filesystems. Perhaps it's
appropriate to add vfsctl(2), with an option which can set a run this
on unmount command? Or maybe a wait for unmount operation?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email
need read access to the executable; whether
you get that access via a path or not is irrelevant.
/proc/curproc/file can address this; so could some kind of
get_RO_fd_on_my_executable().
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents
, it may not
be determinable by the user doing the exec.
$ORIGIN is a poorly conceived interface, unfortunately.
Not as if _that_'s anything new.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D
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
tree with sin_zero and will be adding
prominent comments to it explaining why sin_zero is necessary.
/~\ 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
, at the very least, be
confusing.
Might I suggest BLKMODE instead of BLOCK? At least to my eye, that's a
lot less ambiguous.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39
more the exception than the
rule.
Mouse
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
in the
NetBSD version you're using? (I don't see any indication what version
you're doing this under.)
/~\ 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
EWOULDBLOCK:
#endif
produces a compile-time error. So, my opinion would be to prefer one
of the other alternatives.
/~\ 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
, and, while my Web-fu is admittedly weak, I didn't
find anything the least bit helpful.
/~\ 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 currently at 4.0.1. If this is possible
with a more recent version but not with 4.0.1, I might be able to talk
its admins into switching, but I suspect they'd rather not; it _is_ a
production machine.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo
that will
let me get the info I want I'd prefer 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
there,
though the list of options it shows is longer, so presumably what you
describe won't work before 6.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
, and 1/1073741824 for 8k.)
/~\ 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 source to newfs and/or
fsck; they know a good deal about that stuff, and are much smaller and
more comprehensible than the filesystem kernel code.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61
don't know. I don't know of any such book, but I've never looked; my
own knowledge of such things comes from experimentation and code
reading.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61
Is there an interface for reading (or even writing) another process'
ulimits?
Yes.
Command-line: sysctl proc.$PID.rlimit.$RESOURCE.{soft,hard} (use -w to
change them, of course).
API: sysctl(3) with the analogous MIB.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X
syscall per 256K will be
four times as costly in syscall overhead as doing one syscall per 1M,
even if it is four times as costly in disk transfers.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8
. Unless the host is
unusually slow, writing to the disk will be the limiting factor here,
meaning the buffer cache will have a large number of writes pending, so
coalescing writes is plausible, even likely.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
enough to
prohibit 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
mounted-on
string. But that's definitely an unusual case, and I see nothing wrong
with accessing the topmost mount in that case; that's what normal
filesystem accesses will do, after all.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents
at snapshots, only at the block device level
instead of the filesystem level. (Actually, looking at the existing
snapshot support, it's not clear to me that's not exactly what it
already is.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo
Iis RAIDframe smarter when it has 3 disaks in a RAID 1?
Does RF even support 3-disk RAID 1? It didn't last time I looked, but
that was long enough ago it could very well have changed since then.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
.
I find your discovery about changing a user process's priority making a
difference surprising.
/~\ 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 exempted from quotas without harm (eg, root).
Do you have experience or studies indicating that this is another
respect in which I am an outlier?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61
not distinguish between a sparse
file and a file with long runs of 0x00s, so that's not evidence for
whether it was dumped sparse.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D
is disabled or
limited, the version quoted above will probably be marginally larger
and, assuming larger code doesn't mean more cache line fills,
marginally faster. Which is `more costly' depends on what costs you
care about and to what extent.
/~\ The ASCII Mouse
hello. You can put a wedge on the disk or put the raid on the raw
disk itself.
Can you RAID the raw disk? I thought you had to use partitions of type
RAID for that, which RAW_PART isn't. Am I just confused?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
(or a suitable
porting of it if you're not using the version the patch is for).
/~\ 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
? etc).
/~\ 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
, unless for your
purposes custom bugfixes aren't acceptable, or finding them isn't going
to happen, or some such.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E
issue. (Actually, it's a RAID 15 - a RAID 5 whose members
are RAID 1s.) I can supply full diffs if desired, or anyone with git
installed is welcome to clone the repo and look at the aforementioned
changesets. (For those interested, it's at
git://git.rodents-montreal.org/Mouse/netbsd-fork/4.0.1/src
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
1 - 100 of 800 matches
Mail list logo