On 14/08/25, Andy Lutomirski wrote:
> On Mon, Aug 25, 2014 at 9:41 AM, Nicolas Dichtel
> wrote:
> > Le 25/08/2014 18:13, Andy Lutomirski a écrit :
> >
> >> On Mon, Aug 25, 2014 at 8:43 AM, Nicolas Dichtel
> >> wrote:
> >>>
> >>> Le 25/08/2014 16:04, Andy Lutomirski a écrit :
> >>>
> On Aug 2
On Mon, Aug 25, 2014 at 9:41 AM, Nicolas Dichtel
wrote:
> Le 25/08/2014 18:13, Andy Lutomirski a écrit :
>
>> On Mon, Aug 25, 2014 at 8:43 AM, Nicolas Dichtel
>> wrote:
>>>
>>> Le 25/08/2014 16:04, Andy Lutomirski a écrit :
>>>
On Aug 25, 2014 6:30 AM, "Nicolas Dichtel"
wrote:
>>
>
Le 25/08/2014 18:13, Andy Lutomirski a écrit :
On Mon, Aug 25, 2014 at 8:43 AM, Nicolas Dichtel
wrote:
Le 25/08/2014 16:04, Andy Lutomirski a écrit :
On Aug 25, 2014 6:30 AM, "Nicolas Dichtel"
wrote:
CRIU wants to save the complete state of a namespace and then restore
it. For that to wor
On Mon, Aug 25, 2014 at 8:43 AM, Nicolas Dichtel
wrote:
> Le 25/08/2014 16:04, Andy Lutomirski a écrit :
>
>> On Aug 25, 2014 6:30 AM, "Nicolas Dichtel"
>> wrote:
CRIU wants to save the complete state of a namespace and then restore
it. For that to work, any information exposed to
Le 25/08/2014 16:04, Andy Lutomirski a écrit :
On Aug 25, 2014 6:30 AM, "Nicolas Dichtel" wrote:
CRIU wants to save the complete state of a namespace and then restore
it. For that to work, any information exposed to things in the
namespace *cannot* be globally unique or unique per boot, since
On Aug 25, 2014 6:30 AM, "Nicolas Dichtel" wrote:
>> CRIU wants to save the complete state of a namespace and then restore
>> it. For that to work, any information exposed to things in the
>> namespace *cannot* be globally unique or unique per boot, since CRIU
>> needs to arrange for that informa
Le 24/08/2014 19:52, Andy Lutomirski a écrit :
On Thu, Aug 21, 2014 at 6:58 PM, Richard Guy Briggs wrote:
On 14/08/21, Andy Lutomirski wrote:
On Aug 20, 2014 8:12 PM, "Richard Guy Briggs" wrote:
Expose the namespace instace serial numbers in the proc filesystem at
/proc//ns/_snum. The link
On 14/08/24, Andy Lutomirski wrote:
> On Thu, Aug 21, 2014 at 6:58 PM, Richard Guy Briggs wrote:
> > On 14/08/21, Andy Lutomirski wrote:
> >> On Aug 20, 2014 8:12 PM, "Richard Guy Briggs" wrote:
> >> > Expose the namespace instace serial numbers in the proc filesystem at
> >> > /proc//ns/_snum.
On Thu, Aug 21, 2014 at 6:58 PM, Richard Guy Briggs wrote:
> On 14/08/21, Andy Lutomirski wrote:
>> On Aug 20, 2014 8:12 PM, "Richard Guy Briggs" wrote:
>> > Expose the namespace instace serial numbers in the proc filesystem at
>> > /proc//ns/_snum. The link text gives the serial number in hex.
On 14/08/21, Andy Lutomirski wrote:
> On Aug 20, 2014 8:12 PM, "Richard Guy Briggs" wrote:
> > Expose the namespace instace serial numbers in the proc filesystem at
> > /proc//ns/_snum. The link text gives the serial number in hex.
>
> What's the use case?
>
> I understand the utility of giving
On Aug 20, 2014 8:12 PM, "Richard Guy Briggs" wrote:
>
> Expose the namespace instace serial numbers in the proc filesystem at
> /proc//ns/_snum. The link text gives the serial number in hex.
What's the use case?
I understand the utility of giving unique numbers to the audit code,
but I don't t
Expose the namespace instace serial numbers in the proc filesystem at
/proc//ns/_snum. The link text gives the serial number in hex.
"snum" was chosen instead of "seq" for consistency with inum and there are a
number of other uses of "seq" in the namespace code.
Suggested-by: Serge E. Hallyn
Si
12 matches
Mail list logo
