* Alexander Leidinger wrote:
>> The ideal solution would be to integrate it into vidcontrol, calling
>> some kind of ioctl on the TTY/consolectl, but syscons is too brainless
>> to know anything about hardware specific features.
>
> Here we are back to what was proposed instead of sysctl. I have t
Ed Schouten wrote:
* Alexander Leidinger wrote:
The ideal solution would be to integrate it into vidcontrol, calling
some kind of ioctl on the TTY/consolectl, but syscons is too brainless
to know anything about hardware specific features.
Here we are back to what was proposed instead of sysctl.
Hello Hackers,
I am seeing this message continuously in syslog for every 60 secs. what
could be the possible reasons for this error messages.
Thanks,
Vasanth
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-
Quoting Ed Schouten (from Thu, 29 Jan 2009 15:36:06 +0100):
* Alexander Leidinger wrote:
So you want that either
- a daemon running as root is written which listens to user
requests to set the backlight via sysctl
or
- a SUID root program is written that sets the backlight
via sysctl
Andriy Gapon wrote:
INTR_FILTER - what does it do?
It doesn't seem to be documented anywhere, but seems to affect interrupt
code.
for a bit more information about interrupt filtering, see here:
http://lists.freebsd.org/pipermail/freebsd-hackers/2007-February/019704.html
--
bye,
P.
__
Hi,
I'm trying to port Click modular router to FreeBSD 7.1, but with a
twist. Instead of letting Click run in netisr (as it used to run in
FreeBSD 4), I want to have it running in a kthread. I managed to get
it running this way, but when I turn on INVARIANTS and WITNESS (along
with WITNES
I'm working on BSD 6.x and of course the set of ddb commands is static
to whatever is in the kernel at compile. I see that BSD 7.1 has dynamic
commands using sysinits and sysuninit's to call a new
db_[un]register_cmd.
I see this, though, only after I have spent a day or so adding a
linker_file_[u
Just an addenda:
> I see that BSD 7.1 has dynamic commands using sysinits and sysuninit's to
> call a new
> db_[un]register_cmd.
I was looking at HEAD, not RELENG_7_1. The remainder of my questions as
to why this mechanism are the same, though.
Thanks,
matthew
_
Matthew Fleming wrote:
I'm working on BSD 6.x and of course the set of ddb commands is static
to whatever is in the kernel at compile. I see that BSD 7.1 has dynamic
commands using sysinits and sysuninit's to call a new
db_[un]register_cmd.
I see this, though, only after I have spent a day or s
Hi Warner..
Can the solution become the source tree updates to the same version of my
installed kernel? Sorry for my irregular-time questions and responses but
currently i cannot access to inet.. It's really difficult for me becouse I
don't put instant solution for my systems and my case of study
In message:
Jacky Oh writes:
: Can the solution become the source tree updates to the same version of my
: installed kernel? Sorry for my irregular-time questions and responses but
: currently i cannot access to inet.. It's really difficult for me becouse I
: don't put instant solutio
> If I recall it was painful to find entries in the help listing w/o sorting.
So it's a human reading problem, where ddb spat out the command names in
order that they were in the in-memory struct, and if I wanted to look
over the listing I had to visually scan every one since they weren't in
order
12 matches
Mail list logo
