Lars Wirzenius · 2007
network services (sockets) TCP/IP protocol drivers Ethernet card driver Hardware Kernel Normal programs Kernel User level programs Figure 2.1: Some of the more important parts of the Linux kernel. supports: the kernel contains a virtual filesystem (VFS) that contains all the operations for a filesystem, and a filesystem driver for each supported filesystem. When some entity tries to use a filesystem, the request goes via the VFS, which routes the request to the proper filesystem driver. 2.3 Major services in a UNIX system This section describes some of the more important UNIX services, but without much detail. They are described more thorougly in later chapters. 12 Chapter 2. Overview of a Linux System 2.3.1 init The single most important service in a UNIX system is provided by init. init is started as the first process of every UNIX system, as the last thing the kernel does when it boots. When init starts, it continues the boot process by doing various startup chores (checking and m...
Cited by 0
Stephen Michael Oberther · 2007
Modern operating systems appear to allow multiple processes to execute simultaneously creating a need for advanced process management and control. The operating system provides these functions and also grants the user some management and control of the processes. Many UNIX derived operating systems extend the amount of process information given to the user through the proc filesystem. The proc filesystem provides an interface into the operating system data structures related to the individual processes executing on the system. Additional operating system related information is obtained through the proc filesystem as well, depending on the UNIX variant being examined. The group of process utilities implemented in the Sun Microsystems UNIX variant, Solaris, extends the functionality of the proc filesystem to the user. In this paper, an implementation is presented of a subset of the Solaris process utilities for the Linux operating system. The tools are implemented using the existing information in the Linux proc filesystem where possible. Extensions are added to the Linux proc filesystem to extract additional data that not is available through the current Linux proc implementation. The tools are then compared against the Solaris process utilities to evaluate the implementation. ii Contents 1
Cited by 0
Dave Hitz, Bridget Allison, Andrea Borr et al. · 2012
Sharing network data between NT and UNIX systems is becoming increasingly important as NT moves into areas previously serviced entirely by UNIX. One difficulty in sharing data is that the two filesystem security models are quite different. NT file servers use access control lists (ACLs) that allow permissions to be specified for an arbitrary number of users and groups, while UNIX NFS servers use traditional UNIX permissions that provide control only for owner, group, and other. This paper describes an integrated security model in which a single filesystem can contain both files with NT-style ACLs and files with UNIX-style permissions. For native file service requests (NT requests to NT-style files and NFS requests to UNIX-style files) the security model exactly matches an NT or UNIX fileserver. For non-native requests, heuristics allow a reasonable level of access without compromising the security guarantees of the native model. 1
Cited by 0
Hal Stern, Mike Loukides · 2001
From the Publisher:
Managing NFS and NIS is for system administrators who need to set up or manage a network filesystem installation. NFS (Network Filesystem) is probably running at any site that has two or more UNIX systems. NIS (Network Information System) is a distributed database used to manage a network of computers. The only practical book devoted entirely to these subjects, this guide is a must-have for anyone interested in UNIX networking.
Cited by 70
Wang, W. · elib (German Aerospace Center) · 1995
Im diesem Bericht werden folgende Themen behandelt: UNIX-Betriebssystem, -Filesystem und -Shells - UNIX-Netzwerk TCP/IP und NFS - Systemadministration im UNIX-System - Organisation von Festplatten - Dateiverteilung mittels NFS - Benutzerbetreuung - System- und Datensicherung - Software-Installation und -Upgrade - UNIX Anwendungen fuer normale Benutzer. Dabei steht die Benutzung und Verwaltung des zuerst eingefuehrten Verbundes aus DEC stations im Vordergrund.
Cited by 0
Wenya Wang · 1995
Im diesem Bericht werden folgende Themen behandelt: UNIX-Betriebssystem, -Filesystem und -Shells - UNIX-Netzwerk TCP/IP und NFS - Systemadministration im UNIX-System - Organisation von Festplatten - Dateiverteilung mittels NFS - Benutzerbetreuung - System- und Datensicherung - Software-Installation und -Upgrade - UNIX Anwendungen fuer normale Benutzer. Dabei steht die Benutzung und Verwaltung des zuerst eingefuehrten Verbundes aus DEC stations im Vordergrund.
Cited by 0
2008
Linux is a Unix-like operating system, which runs on PC-386 computers. It was implemented first as extension to the Minix operating system [Tanenbaum 1987] and its first versions included support for the Minix filesystem only. The Minix filesystem contains two serious limitations: block addresses are stored in 16 bit integers, thus the maximal filesystem size is restricted to 64 mega bytes, and directories contain
Cited by 0
Zhhuta, V. · ELARTU (Ternopil National Technical University) · 2013
Max OS X stem from Unix: BSD. It contains a lot of things that are common for Unix systems. Kernel, filesystem and base unix utilities as well as it's own package managers. It's not a secret that Mac OS X has a BSD kernel Darwin. The raw Mac OS X won't provide you with all power of Unix but this could be easily fixed: install package manager. There are 3 package manager: MacPorts, Fink and Homebrew.
Cited by 0
Russel Sandberg · 1987
The Sun Network Filesystem (NFS™) provides transparent, remote access to filesystems. Unlike many other remote filesystem implementations under UNIX®, NFS is designed to be easily portable to other operating systems and machine architectures. It uses an External Data Representation (XDR) specification to describe protocols in a machine and system independent way. NFS is implemented on top
Cited by 0
Ryan Elfmaster O'Neill, K. Auerbach · OSTI OAI (U.S. Department of Energy Office of Scientific and Technical Information) · 1986
A UNIX subsystem has been constructed for the Cray Time Sharing System (CTSS). The subsystem provides CTSS users with many System V facilities. UNIX processes are created by sub-partitioning a CTSS user process. The UNIX file system has been extended to permit UNIX data files to be stored in CTSS files or on a mass storage system. Each user of the subsystem has his own copy of the UNIX kernel and UNIX root filesystem. Major directories (/bin, /lib, etc) exist as read-only, mounted file systems, shared by all UNIX users. The addition of a new system call permits the execution of CTSS programs as UNIX processes.
Cited by 0
Stephen Eisenhauer · University of North Texas Digital Library (University of North Texas) · 2014
This Tech Talk presentation gives an introduction to how data is represented on a filesystem, a hands-on demo of DROID, and a discussion of similar tools including 'file' (unix command line) and JHOVE.
Cited by 0Open access
Stephen Eisenhauer · University of North Texas Digital Library (University of North Texas) · 2014
This Tech Talk presentation gives an introduction to how data is represented on a filesystem, a hands-on demo of DROID, and a discussion of similar tools including 'file' (unix command line) and JHOVE.
Cited by 0Open access
Silvano Maffeis · 1993
Traditional UNIX filesystems are not adequate enough for directly supporting database systems, multimedia systems or applications requiring high I/O performance. In this paper we describe the design and implementation of a configurable mixed-media filesystem. The attribute configurable means that a filesystem serving a specific application area can be realized with less effort out of a library of reusable filesystem classes. The attribute mixed-media stands for the filesystem's ability to integrate different media types (RAM, harddisks, WORM optical disks, CDROMs, tape devices, RAIDs etc.) into a virtual storage and making applications unaware of this aggregation. A prototype C++ implementation of the proposed design, called the Vanilla filesystem, is presented and its performance assessed. Raw-write performance is up to 4:5 times higher than in a...
Cited by 0
The RD45 collaboration · 1996
ion........................................................................................................ 6 2.4 Transparent Storage ............................................................................................................. 7 2.5 Proliferation of Computers and Communication ................................................................ 8 2.6 The Sum is Greater than the Parts ....................................................................................... 9 3 Disk predictions .....................................................................................................10 4 Filesystem predictions ...........................................................................................10 4.1 Filesystems for Unix.......................................................................................................... 10 4.2 Filesystems for NT ............................................................................................................ ...
Cited by 0
2015
This chapter discusses the different filesystem options available in the Linux world and shows how to create and manage them from the Linux command line. Linux supports several types of filesystems to manage files and folders. Each filesystem implements the virtual directory structure on storage devices using slightly different features. The chapter discusses the strengths and weaknesses of the more common filesystems used in the Linux environment. The original Linux system used a simple filesystem that mimicked the functionality of the Unix filesystem. The chapter discusses the evolution of that filesystem. It then describes the popular Linux journaling filesystems available. For filesystems, an alternative to journaling is a technique called copy-on-write (COW). The Linux LVM package provides command line commands to create logical volumes across multiple storage devices on which to build filesystems. The chapter explains the commands for interacting with filesystems from a command line environment.
Cited by 0
Jack Cowardin · 1997
The Linux Proc filesystem has precursors in the Process file system of UNIX System V Release 4 and has features in common with the/proc filesystem of the Plan 9 Operating System. Under the Linux Virtual File System, the Proc filesystem is mounted during boot at /proc and provides dynamically updated information about running processes. Although its abstract representation is that of a filesystem, or storage device, data read from /proc are generated on demand by the kernel when a user-level process issues open and read system calls on a file in the /proc directory tree. The data (typically kernel-level system information) are then passed into the address space of the user process. Since the Proc filesystem represents a window on the running kernel, researchers and system administrators (and, by extension, system users) will benefit from a general method of kernel instrumentation whereby statistics of interest may be generated, collected and reported. Because Linux kernel sou...
Cited by 0
Joel Jakubovic · 2025
Unix and Smalltalk are very different in the details, but bear curious similarities in their broad outlines. Prior work has made these comparisons at a high level and sketched a path for retrofitting Smalltalk's advantages onto Unix (without compromising the advantages of the latter). Everybody seems to agree on identifying the Unix file with the Smalltalk object, but this still leaves much unspecified. I argue that we should identify the Unix executable with the Smalltalk method. A Smalltalk VM implementation via the filesystem falls out quite easily from this premise; however, the severe overhead associated with Unix processes casts doubt on its practical realisation. Nevertheless, we can see several ways around this problem. The connection shows promise for realising the benefits of Smalltalk within Unix without sequestering the former in a hermetically sealed image and VM.
Cited by 0Open access
Milan Ďurkov · Digital Repository (National Repository of Grey Literature) · 2012
This bachelor?s thesis gives an overview of the operating system BSD Unix. The theoretical part of the work describes the history, the present and the basic information about the single distributions of this system. It also describes characteristics of the BSD kernel and natively used filesystem UFS which also compares with the Linux filesystem Ext4. The work also comprises description of the BSD license and its comparison with the GNU GPL license. The practical part of the thesis then describes the installation, configuration and practical experience of the work with desktop PC-BSD system.
Cited by 0
Achim D. Brucker, Frank Rittinger, Burkhart Wolff · White Rose Research Online (University of Leeds, The University of Sheffield, University of York) · 2002
We present a secure architecture of a CVS-server, its implementation (i.e. mainly its configuration) and its formal analysis. Our CVS-server is uses cvsauth, that provides protection of passwords and protection of some internal data of the CVS repository. In contrast to other (security oriented) CVS-architectures, our approach allows the CVS-server run on an open filesystem, i.e. a filesystem where users can have direct access both by CVS-commands and by standard UNIX/POSIX commands such as mv. For our secure architecture of the CVS-server, we provide a formal specification and security analysys. The latter is based on a refinement mapping high-level security requirements on the architecture on low-level security mechanisms on the UNIX/POSIX filesystem level. The purpose of the formal analysis of the secure CVS-server architecture is twofold: First, it is the bases for the specification of mutual security properties such as non-repudiation, authentication and access control for this architecture. Second, the mapping of the architecture on standard security implementation technology is described. Thus, our approach can be seen as a method to give a formal underpinning for the usually tricky business of system administrators.
Cited by 5
David Hitz, Guy Harris, James K. Lau et al. · 1990
Auspex builds fast NFS file servers designed to satisfy the I/O demands of large networks and high-performance workstations. The architecture handles NFS operations quickly and efficiently by completely eliminating Unix from the normal path of NFS service. We designed a message passing kernel that allows a slightly modified Unix kernel to execute as a peer processor with Ethernet processors, filesystem processors, and disk storage processors. These non-Unix processors respond efficiently to NFS requests and perform IP packet routing. A separate host processor running SunOS4.0 provides full Unix compatibility by servicing less time critical and less frequent requests such as Yellow Pages. Our message passing kernel is small (15 kbytes of object) and fast (10,000 messages per second into a Motorola 68020) and provides source code debugging for all processors.
Cited by 0