>> Can anyone give me a clue, how one can ``stop'' system from
accessing RAM, and then allow it again?
>
> I think this has no aim, RAM tests should be done during booting, but
> u could try to disable interrupts while in kernel mode 'cli' which
> will prevent any further context switching, then tr
You can play with adding system calls to FreeBSD. This is
not something that people need to do very often, but it is a
good way to give yourself some experience writing code that
runs in kernel mode. The following OnLamp tutorial is intended
for OpenBSD, but I think most of it applies to FreeBSD a
I think i've seen somewhere but i don't remember that floating point
arithmetic is not allowed in kernel space, if that's right, can anyone
please tell why ???
and why not not emulate the floating point in kernel space ???
That's nonsense! Floating point arithmetic is absolutely allowed in
kerne
I have a usb keyboard (Genius slimstar pro) and am having
the same problems as others are experiencing. When the kb
is first loaded, the two modifiers ctrl and shift are
"stuck" on. This results in keys like d exiting your
terminal. If you hit ctrl and shift on another kb (I have
an at kb hooked u
Josh Carroll wrote:
I included a limitation on the maximum length of a proto (mostly to
avoid buffer overflows) and 20 is probably way too large, so I can
lower that if need be.
I'm not sure buffer overflows are prevented:
static int
parse_protos(const char *protospec)
{
...
char
5 matches
Mail list logo
