The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of...

72
The MINIX3 Service Layer Recent Past, Current Status, and Near-Term Future MINIXCon 2016 David van Moolenbroek [email protected]

Transcript of The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of...

Page 1: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

The MINIX3 Service LayerRecent Past, Current Status, and Near-Term Future

MINIXCon 2016

David van [email protected]

Page 2: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Talk outline

● Terminology● Service layer evolution● Recent and ongoing projects

– A new information service

– Library-based file systems

– Network stack redesign

● Conclusion● How to contribute

Page 3: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Terminology

Page 4: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Terminology

Page 5: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Terminology

Page 6: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Terminology

Page 7: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Terminology

Page 8: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Terminology

Page 9: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Terminology

Page 10: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Service layer evolution

Page 11: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Service layer evolution

Page 12: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Service layer evolution

Page 13: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Service layer evolution

Page 14: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

A new information service

1

Page 15: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

System information

● How to get system info and adjust settings?– Largely (inherently) not portable

1

Page 16: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

System information

● How to get system info and adjust settings?– Largely (inherently) not portable

● Use case: the ps utility– Show a list of current processes

1

Page 17: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

System information

● How to get system info and adjust settings?– Largely (inherently) not portable

● Use case: the ps utility– Show a list of current processes

● In MINIX, ps needs info from process tables– Distributed across PM, VFS, and the kernel

1

Page 18: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

System information

● How to get system info and adjust settings?– Largely (inherently) not portable

● Use case: the ps utility– Show a list of current processes

● In MINIX, ps needs info from process tables– Distributed across PM, VFS, and the kernel

● Traditional ps: get tables directly from services– Every system change requires ps recompilation

1

Page 19: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

First attempt: ProcFS

● Expose information through /proc file system– Google Summer of Code 2009 project

– Loosely based on Linux procfs, sysfs

1

Page 20: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

First attempt: ProcFS

● Expose information through /proc file system– Google Summer of Code 2009 project

– Loosely based on Linux procfs, sysfs

● ps was changed accordingly – problem solved!

1

Page 21: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

First attempt: ProcFS

● Expose information through /proc file system– Google Summer of Code 2009 project

– Loosely based on Linux procfs, sysfs

● ps was changed accordingly – problem solved!● That is, until we wanted to import NetBSD ps...

1

Page 22: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

The sysctl interface 1

int sysctl(int mib[], u_int miblen, void *oldp, size_t *oldlenp, void *newp, size_t newlen);

Page 23: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

The sysctl interface

● Access to a hierarchical key-value store● Key: an array of numbers, one per tree level

– Management Information Base style

– For example: 1.4.2.13.5

– Symbolic names: “kern.hostname” instead of “1.10”

● Value: integer, string, or structure● Not persistent; most keys managed by system

1

int sysctl(int mib[], u_int miblen, void *oldp, size_t *oldlenp, void *newp, size_t newlen);

Page 24: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Importing NetBSD ps 1

libkvm

libc

ps

userland

system

service

change to use procfs?

replace with custom library?

emulate sysctl using procfs?

add sysctl to procfs?

create new sysctl service?

Page 25: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Importing NetBSD ps 1

libkvm

libc

ps

userland

system

service

change to use procfs?

replace with custom library?

emulate sysctl using procfs?

add sysctl to procfs?

create new sysctl service?

Page 26: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Importing NetBSD ps 1

libkvm

libc

ps

userland

system

service

change to use procfs?

replace with custom library?

emulate sysctl using procfs?

add sysctl to procfs?

create new sysctl service?

✕

Page 27: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Importing NetBSD ps 1

libkvm

libc

ps

userland

system

service

change to use procfs?

replace with custom library?

emulate sysctl using procfs?

add sysctl to procfs?

create new sysctl service?

✕

Page 28: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Importing NetBSD ps 1

libkvm

libc

ps

userland

system

service

change to use procfs?

replace with custom library?

emulate sysctl using procfs?

add sysctl to procfs?

create new sysctl service?

✕

✕

Page 29: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Importing NetBSD ps 1

libkvm

libc

ps

userland

system

service

change to use procfs?

replace with custom library?

emulate sysctl using procfs?

add sysctl to procfs?

create new sysctl service?

✕

✕

Page 30: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Importing NetBSD ps 1

libkvm

libc

ps

userland

system

service

change to use procfs?

replace with custom library?

emulate sysctl using procfs?

add sysctl to procfs?

create new sysctl service?

✕

✕

✕

Page 31: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Importing NetBSD ps 1

libkvm

libc

ps

userland

system

service

change to use procfs?

replace with custom library?

emulate sysctl using procfs?

add sysctl to procfs?

create new sysctl service?

✕

✕

✕

Page 32: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Importing NetBSD ps 1

libkvm

libc

ps

userland

system

service

change to use procfs?

replace with custom library?

emulate sysctl using procfs?

add sysctl to procfs?

create new sysctl service?

✕

✕

✕

✕

Page 33: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Importing NetBSD ps 1

libkvm

libc

ps

userland

system

service

change to use procfs?

replace with custom library?

emulate sysctl using procfs?

add sysctl to procfs?

create new sysctl service?

✕

✕

✕

✕

Page 34: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Importing NetBSD ps 1

libkvm

libc

ps

userland

system

service

change to use procfs?

replace with custom library?

emulate sysctl using procfs?

add sysctl to procfs?

create new sysctl service?

✕

✕

✕

✕

✓

Page 35: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Current status and future

● Management Information Base (MIB) service– Merged, available in 3.4.0!

– About 85 of NetBSD's ~800 keys implemented

– 4,146 LoC (Lines of Code)

– ProcFS now calls into the MIB service

– Imported userland: ps, sysctl, top, ipcs, ipcrm

1

Page 36: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Current status and future

● Management Information Base (MIB) service– Merged, available in 3.4.0!

– About 85 of NetBSD's ~800 keys implemented

– 4,146 LoC (Lines of Code)

– ProcFS now calls into the MIB service

– Imported userland: ps, sysctl, top, ipcs, ipcrm

● A path forward for importing other NetBSD tools

1

Page 37: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Try it: sysctl -a 1

Page 38: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Library-based file systems

2

Page 39: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Disk-backed file systems

● Not much progress– 2006: “FS” service split into VFS and MFS

– 2016: two more disk-backed FSes (ext2, isofs)

2

Page 40: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Disk-backed file systems

● Not much progress– 2006: “FS” service split into VFS and MFS

– 2016: two more disk-backed FSes (ext2, isofs)

● It is pretty hard to write a file system service– Implementing e.g. rename is seriously difficult

– ext2 and isofs started as copies of MFS

– Maintenance nightmare!

2

Page 41: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Disk-backed file systems

● Not much progress– 2006: “FS” service split into VFS and MFS

– 2016: two more disk-backed FSes (ext2, isofs)

● It is pretty hard to write a file system service– Implementing e.g. rename is seriously difficult

– ext2 and isofs started as copies of MFS

– Maintenance nightmare!

● What can we do to improve on this?

2

Page 42: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Some first steps 2

Page 43: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Some first steps 2

Page 44: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Some first steps 2

Page 45: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Some first steps 2

Page 46: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Towards decomposition

● File systems are graphs

2

Page 47: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Towards decomposition

● File systems are graphs● Most file system layouts have UNIX origins

– The graph nodes are inodes

– The graph edges are directory entries

– FS operations: series of node and edge operations

2

Page 48: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Towards decomposition

● File systems are graphs● Most file system layouts have UNIX origins

– The graph nodes are inodes

– The graph edges are directory entries

– FS operations: series of node and edge operations

● To create a file, one needs to..– Allocate a new inode

– Create a directory entry for that inode

2

Page 49: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Towards decomposition

● File systems are graphs● Most file system layouts have UNIX origins

– The graph nodes are inodes

– The graph edges are directory entries

– FS operations: series of node and edge operations

● To create a file, one needs to..– Allocate a new inode

– Create a directory entry for that inode

● This graph-level logic is (mostly) generic!– That means we can reuse that part

2

Page 50: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Splitting up the file system 2

Page 51: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Splitting up the file system 2

Page 52: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Splitting up the file system 2

Page 53: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Splitting up the file system 2

Page 54: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Current status and future

● TwinFS– A new crash-consistent file system layout

2

Page 55: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Current status and future

● TwinFS– A new crash-consistent file system layout

● Prototype– Graph layer: 2,847 LoC (reusable!)

– Edge layer: 678 LoC

– Node layer: 3,010 LoC

2

Page 56: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Current status and future

● TwinFS– A new crash-consistent file system layout

● Prototype– Graph layer: 2,847 LoC (reusable!)

– Edge layer: 678 LoC

– Node layer: 3,010 LoC

● Not merged yet – needs testing

2

Page 57: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Current status and future

● TwinFS– A new crash-consistent file system layout

● Prototype– Graph layer: 2,847 LoC (reusable!)

– Edge layer: 678 LoC

– Node layer: 3,010 LoC

● Not merged yet – needs testing

● A way forward to simplify writing FS services

2

Page 58: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Network stack redesign

3

Page 59: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

A tale of scope creep

● Original goal: IPv6 support

3

Page 60: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

A tale of scope creep

● Original goal: IPv6 support

● “Hmm, while I'm here..”

3

Page 61: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

A tale of scope creep

● Original goal: IPv6 support

● “Hmm, while I'm here..”

● Now: three subprojects– Native BSD socket API

– Replacing the TCP/IP stack

– Revisiting the packet level

3

Page 62: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Native BSD socket API

● INET and UDS are character drivers– BSD socket API (socket, bind, connect..) in libc

– This approach has several problems

3

Page 63: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Native BSD socket API

● INET and UDS are character drivers– BSD socket API (socket, bind, connect..) in libc

– This approach has several problems

● Solution: turn BSD socket calls into syscalls– Turn INET and UDS into “socket drivers”

– VFS forwards socket calls to right socket drivers

3

Page 64: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Native BSD socket API

● INET and UDS are character drivers– BSD socket API (socket, bind, connect..) in libc

– This approach has several problems

● Solution: turn BSD socket calls into syscalls– Turn INET and UDS into “socket drivers”

– VFS forwards socket calls to right socket drivers

● Current status– All infrastructure complete (but untested)

– Almost done converting UDS to socket driver

3

Page 65: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Replacing the TCP/IP stack

● Requirements for a new TCP/IP stack:– Comes with IPv6 support

– Interface-compatible with NetBSD

– Maintainable

3

Page 66: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Replacing the TCP/IP stack

● Requirements for a new TCP/IP stack:– Comes with IPv6 support

– Interface-compatible with NetBSD

– Maintainable

● Internal discussions yielded three options:1.Import a more recent INET from minix-vmd

2.Reimplement the wrapper around lwIP

3.Use RUMP to extract NetBSD's TCP/IP stack

3

Page 67: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Replacing the TCP/IP stack

● Requirements for a new TCP/IP stack:– Comes with IPv6 support

– Interface-compatible with NetBSD

– Maintainable

● Internal discussions yielded three options:1.Import a more recent INET from minix-vmd

2.Reimplement the wrapper around lwIP

3.Use RUMP to extract NetBSD's TCP/IP stack

● Leaning heavily towards option 2

3

Page 68: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Revisiting the packet level

● Preparing for the future– Support for other protocol families?

– Support for non-ethernet devices?

– Support for a firewall?

3

ETH

TCP/IP ???

???

???

Page 69: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

Conclusion

● The service layer is evolving rapidly– MINIX is growing up and catching up

● That calls for proper software engineering– Not just adding functionality

– But also restructuring what is already there

– And reducing redundancy

● The main concern is maintenance!

Page 70: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

How to contribute (1)

● We could use your help!● Code development...

– Porting more of NetBSD userland

– Writing a device driver

– Filling in missing functionality

● ...and other activities– Documentation

– PR work

– Testing

Page 71: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

How to contribute (2)

● Information and wishlists– Wiki: http://wiki.minix3.org

● Source code, bug reports, submitting code– GitHub: https://github.com/Stichting-MINIX-

Research-Foundation/minix

● Getting support– Newsgroup: http://groups.google.com/group/minix3

– IRC: FreeNode #minix-dev

Page 72: The MINIX3 Service Layer sysctl interface Access to a hierarchical key-value store Key: an array of numbers, one per tree level – Management Information Base style

End of talk

[email protected]


MODEL: G7100gscs-b2c.lge.com/downloadFile?fileId=KROWM000340340.pdf · Star Key Microphone Soft Right Key Camera Key End/Power Key Clear/Cancel Key Numeric Keys Hash Key Message key.

MODEL: G7100gscs-b2c.lge.com/downloadFile?fileId=KROWM000340340.pdf · Star Key Microphone Soft Right Key Camera Key End/Power Key Clear/Cancel Key Numeric Keys Hash Key Message key.

Really large scale systems configuration large scale systems configuration Config Management @ Facebook Phil Dibowitz. Configuration Management Experience ... • Optimal sysctl settings

Really large scale systems configuration large scale systems configuration Config Management @ Facebook Phil Dibowitz. Configuration Management Experience ... • Optimal sysctl settings

Key and key control

Key and key control

Key 1 Key 2 Key 3 Key 4 Key 5 Key 6 Key 7 Key 8 Key 9 Key ...rnamedical.com/files/inserts/11/648516.pdf · Key 1 Key 2 Key 3 Key 4 Key 5 Key 6 Key 7 Key 8 ... relazioni statistiche

Key 1 Key 2 Key 3 Key 4 Key 5 Key 6 Key 7 Key 8 Key 9 Key ...rnamedical.com/files/inserts/11/648516.pdf · Key 1 Key 2 Key 3 Key 4 Key 5 Key 6 Key 7 Key 8 ... relazioni statistiche

The Minix3 Notes

The Minix3 Notes

ADSP-2126x SHARC Processor Hardware Reference ADSP-2126x SHARC Processor Hardware Reference Example: Register-to-Memory Moves – External or IOP ... SYSCTL Register Control Bits ...

ADSP-2126x SHARC Processor Hardware Reference ADSP-2126x SHARC Processor Hardware Reference Example: Register-to-Memory Moves – External or IOP ... SYSCTL Register Control Bits ...

Operating Systems Security Linux Fundamentals & Practicesecuresw.dankook.ac.kr/ISS19-2/2019_OS_Se_3_Linux_Overview.pdf-w: use this option when you want to change a sysctl setting The

Operating Systems Security Linux Fundamentals & Practicesecuresw.dankook.ac.kr/ISS19-2/2019_OS_Se_3_Linux_Overview.pdf-w: use this option when you want to change a sysctl setting The

Q.BO KEY Q.BO KEY

Q.BO KEY Q.BO KEY

Supermicro Ethernet Switch Performance Test Ethernet Switch Performance Test ... > Default sysctl net.ipv4.tcp_mem = 3077376 4103168 6154752 > Default sysctl net.core.optmem_max =

Supermicro Ethernet Switch Performance Test Ethernet Switch Performance Test ... > Default sysctl net.ipv4.tcp_mem = 3077376 4103168 6154752 > Default sysctl net.core.optmem_max =

How to write a Device Driver in FreeBSDjmg/drivers/freebsd.device.driver...How to write a Device Driver in FreeBSD John-Mark Gurney. jmg/drivers/ Frameworks ... SYSCTL – read/write

How to write a Device Driver in FreeBSDjmg/drivers/freebsd.device.driver...How to write a Device Driver in FreeBSD John-Mark Gurney. jmg/drivers/ Frameworks ... SYSCTL – read/write

A collection of step-by-step guides for using ... - sysctl.se collection of step-by-step guides for using the IMPEX station SYSCTL AB

A collection of step-by-step guides for using ... - sysctl.se collection of step-by-step guides for using the IMPEX station SYSCTL AB

AIPMT - Studyguideindia€¦ · aipmt final keys 2014 exam date : 04/05/2014 book code : p -----|qno |key|qno |key|qno |key|qno |key| qno |key| qno |key| qno |key| qno |key|

AIPMT - Studyguideindia€¦ · aipmt final keys 2014 exam date : 04/05/2014 book code : p -----|qno |key|qno |key|qno |key|qno |key| qno |key| qno |key| qno |key| qno |key|

color key icon key

color key icon key

10. Key Management. Contents Key Management Public-key distribution Secret-key distribution via public-key cryptography.

10. Key Management. Contents Key Management Public-key distribution Secret-key distribution via public-key cryptography.

The Minix3 Notes - Kambing UI

The Minix3 Notes - Kambing UI

1. Key Thinkers, Key Texts, Key Ideas

1. Key Thinkers, Key Texts, Key Ideas

Examples for using SPTK ver. 3 - Minix3 · SPTK working group December 25, 2011 Contents ... which were converted from “float” format into “wav” format ( 16 kHz sampling,

Examples for using SPTK ver. 3 - Minix3 · SPTK working group December 25, 2011 Contents ... which were converted from “float” format into “wav” format ( 16 kHz sampling,

MINIX3 Processes

MINIX3 Processes

New features and the Spack Roadmapideas-productivity.org/wordpress/wp-content/... · — Detects based on /proc/cpuinfo (Linux), sysctl (Mac) — Allows comparisons for compatibility,

New features and the Spack Roadmapideas-productivity.org/wordpress/wp-content/... · — Detects based on /proc/cpuinfo (Linux), sysctl (Mac) — Allows comparisons for compatibility,

KEY MANAGEMENT; OTHER PUBLIC-KEY CRYPTOSYSTEMS - Chapter 10 KEY MANAGEMENT; OTHER PUBLIC-KEY CRYPTOSYSTEMS - Chapter 10 KEY MANAGEMENT DIFFIE-HELLMAN KEY.

KEY MANAGEMENT; OTHER PUBLIC-KEY CRYPTOSYSTEMS - Chapter 10 KEY MANAGEMENT; OTHER PUBLIC-KEY CRYPTOSYSTEMS - Chapter 10 KEY MANAGEMENT DIFFIE-HELLMAN KEY.