The View-OS concept is defined as allowing each process to have its own view of its execution environment. For example, each process can have its own view for its file system, networking support, devices, userid, system-name, time, etc. A process running in a View-OS machine has its own "namespace" implemented at user level. This approach increases the safety of the system (no need for root access, no need for kernel code), and flexibility (it is possible to support features not included in the kernel). Umview and kmview are two implementations of the View-OS concept. Technically, umview and kmview are user-level, system-call based, partial, modular, virtual machine monitors. They virtualize a subset of the kernel requests (system calls) depending upon which modules have been loaded and upon which kind of virtualization the user configured. Most of the features of chroot/schroot/fakeroot(ng)/fuse/net-namespaces (and many other tools) have been implemented in View-OS modules. The talk includes a public demo of some View-OS features (if Murphy permits).