From: Evgeniy Polyakov [EMAIL PROTECTED]
Date: Sun, 28 May 2006 19:33:21 +0400
Does SELinux have security handlers for each type of possible ioctls
over the world? Each ioctl number is like each netlink type of message,
but instead there is only one check per ioctl syscall as long as lsm
hook
Here is part of the dmesg on my 3c59x test machine.
This happend first time and I'm quite sure after module reloading things
will be ok again, so it is not bug report but probably some meat for brain...
Hmm... I can not login using neither serial console, nor direct access,
it looks like
On Sun, 2006-28-05 at 23:36 -0700, David Miller wrote:
[..]
More to the point I think that none of this will be handled
transparently unless the onus is put on new netlink module users.
Ie. make the register of a netlink subsystem user (either direct
netlink or via generic netlink) fail if
Hi,
I made a small update on this patch, only a small compile fix
and small bugfix.
The thing I would like to know now, is if the current approach
is the desired situation.
- Should only 1 input device be created, or multiple devices?
- Should instead of KEY_RADIO new keys be created
Hi James,
On Monday, 29. May 2006 19:48, James Courtier-Dutton wrote:
I can concur that the forcedeth is unreliable on nvidia based motherboards.
I have a ethernet device that works with forcedeth.
:00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3)
:00:0a.0 0680:
Hi gurus,
I am not sure if there is a problem in the additive increment (AI)
parameter of tcp_highspeed.c:
When snd_cwnd is smaller than 38 and the connection is in
congestion avoidance phase (snd_cwnd snd_ssthresh), the snd_cwnd
seems to stop growing. I guess the problem is in the
