On 04/02/15 15:17, Christoph Lameter wrote:
On Wed, 4 Feb 2015, Markku Savela wrote:
Just a note... We had inheritable capabilities in the linux of Nokia N9 phone.
Could we review the patch please?
Unfortunately, I don't have it and with quick search only found "N9 MER"
kern
On 04/02/15 15:17, Christoph Lameter wrote:
On Wed, 4 Feb 2015, Markku Savela wrote:
Just a note... We had inheritable capabilities in the linux of Nokia N9 phone.
Could we review the patch please?
Unfortunately, I don't have it and with quick search only found N9 MER
kernels, where
Just a note... We had inheritable capabilities in the linux of Nokia N9
phone.
If a program needed some capabilities, they had to be requested by the
manifest file inside the debian package. Of course, request is only
granted if the package origin had permission to grant them.
--
To
Just a note... We had inheritable capabilities in the linux of Nokia N9
phone.
If a program needed some capabilities, they had to be requested by the
manifest file inside the debian package. Of course, request is only
granted if the package origin had permission to grant them.
--
To
Imho, the patch doesn't go far enough actually. What should be done:
- get rid of the union
- use IPv6 format only
- store IPv4 addresses in IPv4 mapped format
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
Imho, the patch doesn't go far enough actually. What should be done:
- get rid of the union
- use IPv6 format only
- store IPv4 addresses in IPv4 mapped format
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More
On 12/05/2012 09:32 PM, Andy Lutomirski wrote:
>Anyway, implementing the features you want in a new module is encouraged,
>so long as the behavior of existing module stays the same.
I'll think about it some more and do it possibly using a sysctl.
Adding this kind of stuff in a module is asking
On 12/05/2012 09:32 PM, Andy Lutomirski wrote:
Anyway, implementing the features you want in a new module is encouraged,
so long as the behavior of existing module stays the same.
I'll think about it some more and do it possibly using a sysctl.
Adding this kind of stuff in a module is asking
Does this filesystem capability "feature" also include the equivalent
of "nosuid" option for a mount?
(google gives gobblegook of hits with "linux file system
capabilities", can't figure out which of them is the "definitive" one
-- pointers?)
--
To unsubscribe from this list: send the line
Does this filesystem capability feature also include the equivalent
of nosuid option for a mount?
(google gives gobblegook of hits with linux file system
capabilities, can't figure out which of them is the definitive one
-- pointers?)
--
To unsubscribe from this list: send the line unsubscribe
How about just simple solution? Make it possible that "malloc" works
as it was originally intended: return NULL, if memory not available,
non-NULL only if allocation truly succeeded and is guaranteed..
Make kernel configuration option? (e.g. disable "over commit"
mis-fea
How about just simple solution? Make it possible that malloc works
as it was originally intended: return NULL, if memory not available,
non-NULL only if allocation truly succeeded and is guaranteed..
Make kernel configuration option? (e.g. disable over commit
mis-feature :-)
--
Markku Savela
>
> > This is a pity, because it would be so easy to make the both stacks
> > totally independent of the actual link layers. It only needs one (or
> > two) new function pointer in net_device. This function should do the
> > conversion from IPv4/IPv6 address into corresponding hardware
> >
This is a pity, because it would be so easy to make the both stacks
totally independent of the actual link layers. It only needs one (or
two) new function pointer in net_device. This function should do the
conversion from IPv4/IPv6 address into corresponding hardware
would give defaults for
the functions.
[I run into this while trying to do a netdev to a device is not known
by the stacks, and IPv6 even refuses to start on it (because of the
ivp6_generate_eui64 fails?). IPv4 ARP seems to fall back to broadcast,
so it sort of starts]
--
Markku Savela
would give defaults for
the functions.
[I run into this while trying to do a netdev to a device is not known
by the stacks, and IPv6 even refuses to start on it (because of the
ivp6_generate_eui64 fails?). IPv4 ARP seems to fall back to broadcast,
so it sort of starts]
--
Markku Savela
Oops!
The error exits are not right in foo_init (need to release anything
succesfully created, if later operations fail). Probably need to make
the current foo_exit into foo_cleanup and call it in real foo_exit and
in any errors at foo_init.
But, again thanks for the help. I consider the "case
Solution found!
> On Thu, Jan 25, 2007 at 09:35:07AM +0200, Markku Savela wrote:
> > If want to write a loadable module which "implements" a char device
> > ("virtual", no real device present). How do I get the correct
> > "/dev/foo" to app
Solution found!
On Thu, Jan 25, 2007 at 09:35:07AM +0200, Markku Savela wrote:
If want to write a loadable module which implements a char device
(virtual, no real device present). How do I get the correct
/dev/foo to appear automaticly?
From: Greg KH [EMAIL PROTECTED]
If you look
Oops!
The error exits are not right in foo_init (need to release anything
succesfully created, if later operations fail). Probably need to make
the current foo_exit into foo_cleanup and call it in real foo_exit and
in any errors at foo_init.
But, again thanks for the help. I consider the case
If want to write a loadable module which "implements" a char device
("virtual", no real device present). How do I get the correct
"/dev/foo" to appear automaticly? What is the current recommended
solution (kernel 2.6.17 in Ubuntu and later).
static int major;
static int __init foo_init(void)
If want to write a loadable module which implements a char device
(virtual, no real device present). How do I get the correct
/dev/foo to appear automaticly? What is the current recommended
solution (kernel 2.6.17 in Ubuntu and later).
static int major;
static int __init foo_init(void)
{
22 matches
Mail list logo
