king a volatile int variable is
more expensive than a syscall into the kernel.)
It is true, though, that that's more-than-zero cost in the loop. But
it might be close enough to zero to be acceptable.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
thers you, make
it long long int instead - there is some risk of value tearing in the
read on many architectures, but, since the kernel's increment is atomic
with respect to userland, the worst it will do is delay noticing the
signal by one trip around the loop.
/~\ The ASCII
umpns_lockdebug_
The tr can be replaced with flags to the following xargs if you have an
xargs with an the ability to fix the whitespace-and-quoting
misfeatures; I don't know whether 9's xargs(1) does.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Aga
e of the console,
you'd also have to figure out what to do with the console if the
hardware goes away.
It's one of the reasons I dislike USB, and closely related to most of
the others.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
> I agree with Mouse, except that I also think it would be very helpful
> and useful to have a serial console on USB only devices.
Oh, sure, it'd be helpful/useful. Lots of difficult things would be.
> I wonder if we could make the console a virtual device which is
> attached
e Foundation's or the Project's.
/~\ 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
x27;ve been working with recent NetBSD at work, for something
for which the presence or absence of good random-seed data makes
absolutely no difference to security.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.or
some more things that have been patched not to use /dev/random.
Sure. And if you don't set the timezone, you'll be stuck in UTC. And
if you don't set up a mailer, mail won't work. If you don't set any
DNS servers, things depending on name resolution won't
or maybe the test is 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
reliable source of entropy.
It's entirely possible one or more of those sources actually does
supply usable entropy, but NetBSD doesn't realize that (and, as I
understand it, provides no way for the sysadmin to fix that, short of
hacking on the source).
/~\ The ASCII
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 it there really was.
/~\ 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
would also want to do all the
relevant processing on CPUs (and, where applicable, other hardware) old
enough to predate the reasons for caring about that level of
unpredictability, because it makes them significantly less likely to
have been trojaned.
/~\ The ASCII Mouse
\
d and" part of the above. (I still think it's
misguided, but I don't expect NetBSD to agree. It's been a long time
since NetBSD and I saw eye to eye on...well, on many points.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo..
to "fully trusted", depending on the site.
/~\ 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 interesting ways for full world builds if you run into a
> problem, cvs up and try an update build again.
I submit that, if that is the case, the build is already broken and you
just haven't yet tripped over a case that makes it unmistakeable.
/~\ The ASCII
d be produced.
Similarly, sets should depend on the main build.
/~\ 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
ror message doesn't report enough information.
/~\ 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
3406 make-2025.02.24. PSIG SIGPIPE SIG_DFL: code=SI_NOINFO
but this is meaningless; ktrace /bin/sh -c 'kill -KILL $$' also shows
kill(2) returning - presumably the ktrace record is written before the
syscall exit path tears down the process due to the signal.
/~\ The ASCII
gt; Perhaps this is fallout from a compiler or binutils upgrade?
I feel fairly sure that's exactly what it is: the old compiler uses the
common model and the new compiler uses lthe def/ref model.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
20 matches
Mail list logo
