Lines Matching +full:system +full:- +full:control

28 .\" *troff -ms
34 of Berkeley\s-2\fP
56 update other major components of the system, as well as to offer
68 The fifth is to evaluate alternate access control mechanisms and
69 audit the existing security features of the system, particularly
71 Other areas of work include multi-architecture support, 
87 There have been several changes in the system that were included
90 Multi-architecture support
96 non-VAX processor, the CCI Power 6/32 and 6/32SX.  (This addition also
98 Harris HCX-7 and HCX-9, as well as the Sperry 7000/40 and ICL machines.)
102 The entire source tree, including all kernel and user-level sources,
115 patterns in the UNIX kernel and a hybrid strategy that is time-efficient
116 for small allocations and space-efficient for large allocations.
118 with a single easy-to-program interface,
133 and other user-level programs that use such information now obtain
135 The use of this facility has allowed improvements in the file system's
136 knowledge of irregular disk geometries such as track-to-track skew.
138 Fat Fast File System
140 The 4.2 fast file system [McKusick84]
147 Old kernels will treat the new filesystems as read-only,
173 to integrate these with an OSI transport class 4 (TP-4) implementation.
186 Wisconsin TP-4 to match GOSIP requirements.
192 We will make this TP-4 operate with an OSI IP,
195 A kernel version of the OSI IP and ES-IS protocols must be produced.
219 of the IEEE POSIX P1003.1 system interface standard.
222 P1003.6 (security), P1003.7 (system administration), and P1003.8
226 POSIX related changes to the BSD system have included a new terminal
227 driver, support for POSIX sessions and job control, expanded signal
228 functionality, restructured directory access routines, and new set-user
229 and set-group id facilities.
233 We also have a prototype implementation of the 4.2BSD-based POSIX
234 job control facility.
244 system.
251 The Internet and the Berkeley collection of local-area networks
254 connecting several UC campuses, Stanford and NASA-Ames
266 for TCP that improve throughput on both local and long-haul networks
270 The new algorithms include ``slow-start,''
271 a technique for opening the TCP flow control window slowly
277 In addition, the round-trip timer has been modified to estimate the variance
278 in round-trip time, thus allowing earlier retransmission of lost packets
292 into the TP-4 protocol implementation.
294 Toward a Compatible File System Interface
296 The most critical shortcoming of the 4.3BSD UNIX system was in the
299 there is no single distributed file system
302 file system protocols, just as it is necessary to run several 
306 several stylized interfaces between the file system implementation
308 Among these are Sun Microsystems' Virtual File System interface (VFS)
310 Digital Equipment's Generic File System (GFS) architecture [Rodriguez86],
311 AT&T's File System Switch (FSS) [Rifkin86],
312 the LOCUS distributed file system [Walker85],
313 and Masscomp's extended file system [Cole85].
316 notably the network file system in the Eighth Edition UNIX
317 system [Weinberger84] and two different file systems used at Carnegie Mellon
324 Each design attempts to isolate file system-dependent details
332 and having selected a different set of file system primitive operations.
340 framework.  We have studied the various file system interfaces to determine
342 and are currently working on a file system interface
347 toward convergence on a standard compatible file system interface.
352 System Security
356 safeguards built into the system.
358 weaknesses in the system access mechanisms, rather than actively
360 When we are notified of a problem or loophole in a system utility
369 We will make a complete audit of the system
370 utilities and network servers to find unintended system access mechanisms.
372 As a part of the work to make the system more resistant to attack
374 additional documentation on the configuration and operation of the system.
377 and control of privileged operations such as file system backups.
379 We are investigating the addition of access control lists (ACLs) for
381 ACLs provide a much finer granularity of control over file access permissions
383 discretionary access control mechanism (mode bits).
393 A major shortcoming of the present system is that authentication
397 on a UNIX system,
410 the X window system, and the mail system within an authentication
413 with the network authentication system.
420 \fISoftware\- Practice and Experience\fP, Vol. 12, pp. 1147-1162, 1982.
425 ``An Implementation of an Extended File System for UNIX,''
427 pp. 131-150, June, 1985.
432 ``Trusted Computer System Evaluation Criteria,''
433 \fICSC-STD-001-83\fP,
438 ``Towards a Compatible File System Interface,''
440 Manchester, England, pp. 481-496, September 1986.
444 ``Vnodes: An Architecture for Multiple File System Types in Sun UNIX,''
446 pp. 238-247, June, 1986.
451 \fIUsenix Conference Proceedings\fP, pp. 237-252, June, 1984.
455 ``A Fast File System for UNIX'',
457 pp 181-197, August 1984.
462 \fIUsenix Conference Proceedings\fP, pp. 519-531, June, 1985.
468 Manchester, England, pp. 451-460, September 1986.
474 pp. 295-303, June, 1988.
479 pp. 248-259, June, 1986.
483 ``The Generic File System,''
485 pp. 260-269, June, 1986.
489 ``Design and Implementation of the Sun Network File System,''
491 pp. 119-130, June, 1985.
495 ``The ITC Distributed File System: Principles and Design,''
496 \fIProc. 10th Symposium on Operating Systems Principles\fP, pp. 35-50,
502 \fIUsenix Conference Proceedings\fP, pp. 191-202, February, 1988.
505 Walker, B.J. and S.H. Kiser, ``The LOCUS Distributed File System,''
506 \fIThe LOCUS Distributed System Architecture\fP,
510 Weinberger, P.J., ``The Version 8 Network File System,''