SMCC. crash(1M). SunOS 5.5 Reference Manual, Section 1M. Sun Microsystems, Incorporated, 25 January 1995.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....the select(2) system call. vop dump dumps the state of the kernel (memory bu ers, tables, variables, registers, etc. to a given vnode, usually a swap device. This is used as the last action performed when a kernel panics and needs to save state for post mortem recovery by tools such as crash [SMCC95]. vop pathconf supports the POSIX path con guration standard. This call returns various con gurable le or directory variables. vop pageio performs I O directly on mapped pages of a le. vop dumpctl works in conjunction with vop dump. It is used to prepare a le system before a dump ....

SMCC. crash(1M). SunOS 5.5 Reference Manual, Section 1M. Sun Microsystems, Incorporated, 25 January 1995.

....such as root vp do not yet exist. This function has to manually create and initialize all of these resources. vfs swapvp returns a vnode speci c to a particular device onto which the system can swap. It is used for example when adding a le as a virtual swap device via the swap a command [SMCC94b]. The VFS operations get invoked transparently via macros that dereference the operations vector s eld for that operation, and pass along the vfs and the arguments it needs. Each VFS operation has a macro associated with it, located in sys vfs.h . Figure 23 shows the de nitions for these ....

SMCC. swap(1M). SunOS 5.5 Reference Manual, Section 1M. Sun Microsystems, Incorporated, 2 March 1994.

....(or kernel) developer would agree that writing a new le system takes a long time, is dicult to test and debug, and has to be constantly maintained as operating systems evolve and change. Every small change takes a long edit compile run debug cycle, with kernel crashes and lack of debugging tools [Golub90, Stallman94, SMCC94a] making the task frustrating. Worse, le system code developed for one operating system is almost never portable to another. After a long period of development for one operating system, the whole process has to be repeated if the le system is to be ported to a new operating system. It should come ....

SMCC. kadb(1M). SunOS 5.4 Reference Manual, Section 1M. Sun Microsystems, Incorporated, 2 June 1994.

....code as described in Section 4.3.1. The translator should also be able to generate runnable user level le system code as described in Section 4.10. The translator should generate kernel modules that can be dynamically loaded into a running kernel using facilities such as modload [SMCC93a], or linked with other kernel objects to produce a static image of a new kernel [SMCC91] The latter can then be copied over to the root directory and run when the machine is next rebooted. The translator should take the worst case approach. Any minor problem with the input le or the code ....

SMCC. modload(1M). SunOS 5.5 Reference Manual, Section 1M. Sun Microsystems, Incorporated, 1 December 1993.

....generate runnable user level le system code as described in Section 4.10. The translator should generate kernel modules that can be dynamically loaded into a running kernel using facilities such as modload [SMCC93a] or linked with other kernel objects to produce a static image of a new kernel [SMCC91]. The latter can then be copied over to the root directory and run when the machine is next rebooted. The translator should take the worst case approach. Any minor problem with the input le or the code generation phase should result in fatal errors. No kernel module should be produced if there ....

SMCC. con g(8). SunOS 4.1 Reference Manual, Section 8. Sun Microsystems, Incorporated, 10 April 1991.

....not to be the functionality itself. Therefore, at the moment, I see no reason to allow Statefs to be directly interposed upon. B.2.4 Snoopfs A le system that will tell you who accessed what les or directories, and when. The le system will record, via direct console messages or syslog [SMCC90], the uid and gid of a process accessing les in this le system, the names of the les or directories, and the time of access. After recording this information, Snoopfs will forward the vnode request to the interposed le system, thus hiding the fact that this le system is being monitored. ....

SMCC. syslogd(8). SunOS 4.1 Reference Manual, Section 8. Sun Microsystems, Incorporated, January, 1990.

....Abstract Programmers often prefer to use existing system security services, such as file system security, rather than implement their own in an application. Traditional Unix security is generally considered inadequate and few operating systems offer enhanced security features such as ACLs[24] or immutable files[12] Additional file system security features are always sought, but implementing them is a difficult task because modifying and porting existing file systems is costly or not possible. We advocate adding new security features using stackable file systems. As a starting point, ....

....of the significant changes that overhauling the file system interface would require, and the impact it would have on performance. A few small enhancements to kernel based file systems were implemented over the years. These include immutable files in 4. 4 BSD s FFS[12] and ACLs in Solaris s UFS[24]. However, none of these features are widely available. Furthermore, making such changes to existing file systems is often a costly proposal: source access is required, and the work involves deep understanding of that operating system s internals. Once the work is accomplished on one platform, a ....

SMCC. acl(2). SunOS 5.6 Reference Manual, Section 2. Sun Microsystems, Incorporated, 18 March 1996.

....words, a collection of TPVM threads that comprise an application are created and execute within the context of a (usually smaller) number of regular processes. These host processes or pods themselves do not contribute to the computation, as is typical with other threads systems e.g. SunOS LWP [15]. The TPVM system therefore requires that host processes are instantiated and established prior to the active computational entities, i.e. the threads, being started. 3 Host processes or pods are initiated via normal native PVM mechanisms, e.g. pvm spawn or a console command. These processes ....

....use with SunOS 4.x, we implemented the thread interface over the Rex [4] thread system. This thread library operates completely in user space and is nonpreemptive. Scheduling is performed only at the request of the user. Next, we implemented the thread interface over the Solaris threads library [15] which provides kernel supported, preemptive threads. Here, the use of semaphores to control scheduling was required. Given these two porting experiences, we were able to determine the necessary services required of two general classes thread systems to implement our portable thread interface. In ....

SunOS 5.3 Reference Manual, Sun Microsystems, Mountain View, CA, 1993.

....[UMIPSV] MIPS I [Kane87] binaries, and the second (Shade V9.V8) runs SunOS 4.x, Version 9 SPARC [SPARC9] binaries. The host system for both is SunOS 4.x, Version 8 SPARC. There are also versions of Shade V8.V8 and Shade V9.V8 where both the host and target operating systems are Solaris 2. x [SunOS5]. All of these Shades are at least complete to the extent that they can run SPEC89 binaries compiled for the respective target systems. 5.1. Shade MIPS.V8 Shade MIPS.V8 was developed to provide the custom tracing capabilities of Shade for MIPS binaries. Given Shade V8.V8 and ready access to ....

SunOS 5.0 Reference Manual, SunSoft, Inc., June 1992.

....[UMIPSV] MIPS I [Kane87] binaries, and the second (Shade V9.V8) runs SunOS 4.x, Version 9 SPARC [SPARC9] binaries. The host system for both is SunOS 4.x, Version 8 SPARC. There are also versions of Shade V8.V8 and ShadeV9. V8 where both the host and target operating systems are Solaris 2. x [SunOS5]. All of these Shades are at least complete to the extent that they can run SPEC89 binaries compiled for the respective target systems. 4.1. Shade MIPS.V8 Shade MIPS.V8 provides Shade s custom tracing capabilities for MIPS binaries. Given Shade V8.V8 and ready access to SPARC systems, SPARC was ....

SunOS 5.0 Reference Manual, SunSoft, Inc., Jun. 1992.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC