Lines Matching +full:system +full:- +full:wide
32 .Sh 1 "Upgrading a \*(Ps system"
35 system to \*(4B. This procedure may vary according to the version of
36 the system running before conversion.
38 System V system, some of this section will still apply (in particular,
39 the filesystem conversion). However, many of the system configuration
44 a \*(Ps HP300 system.
51 It is largely a \*(Ps system with Sun's NFS 3.0 filesystem code and
52 some \*(Ps-Tahoe features (e.g. networking code).
58 This is a \*(Ps-Tahoe vintage system with Sun's NFS 4.0 filesystem code
60 The instructions for \*(Ps-Tahoe should largely apply.
62 \*(Ps-Reno from CSRG.
81 If you are running \*(Ps, upgrading your system
82 involves replacing your kernel and system utilities.
87 (2) use an existing \*(Ps or later system to extract the root and
90 boot from the new system, then merge or restore existing
92 (3) extract the sources from the distribution tape onto an existing system,
93 and use that system to cross-compile and install \*(4B.
98 for getting the system running.
99 Ideally, the new system binaries (root and
102 then site-specific files should be merged into them.
103 Once the new system is up and fully merged, the previous root and
118 Most systems will need to provide a new filesystem for system use
124 filesystem can be an MFS virtual-memory-resident filesystem,
137 Extract kernel and/or user-level sources from the distribution tape
141 Configure and boot a kernel for the local system.
150 Merge site-dependent configuration files from
171 Merge and update local software to reflect the system changes.
177 Section 3.4 discusses the merger of the saved files back into the new system.
185 save and suggests directories in which site-specific files should be present.
186 This list will likely be augmented with non-standard files you
187 have added to your system.
216 /etc/rc.local * site specific system startup commands
217 /etc/remote \(dg auto-dialer configuration
220 /etc/syslog.conf * system logger configuration
232 /usr/lib/mail.rc \(dg system-wide mail(1) initialization (moves to \f(CW/etc/mail.rc\fP)
250 The next step is to build a working \*(4B system.
275 There should be a per-architecture centrally-shareable read-only
279 Variable per-machine directories should be concentrated below
283 Site-wide machine independent shareable text files should be separated
293 /bin (user binaries needed when single-user)
294 /sbin (root binaries needed when single-user)
299 /var (mount point for per-machine variable directories)
315 /usr/local (locally added binaries used site-wide)
318 /usr/share (mount point for site-wide shared text)
347 /var/backups (backups of system files)
349 /var/db (system-wide databases, e.g. tags)
363 /var/tmp (disk-based temporary directory)
364 /var/users (root of per-machine user home directories)
391 Once you have extracted the \*(4B system and booted from it,
440 (\fIfsck \-b32\fP),
441 in which case it will re-zero these fields.
443 if fsck has not done so; again, the \fI\-b32\fP option may be
454 with the \fI\-c 2\fP option.
455 The sequence \fIfsck \-p \-c 2\fP will update them all,
458 expand maximum uid's and gid's to 32-bits,
464 \fIfsck \-c 1\fP.
467 When your system is booting reliably and you have the \*(4B root and
471 merging your old files into the new system.
484 may be used without change from the previous system.
497 of the system filesystems.
502 that now contains only system configuration files;
504 a new filesystem containing per-system spool and log files; and
508 System administration programs formerly in
576 directory now contains nearly all the host-specific configuration
606 New in \*(Ps-Tahoe \*(4B Comments
619 /etc/amd-home location database of home directories
620 /etc/amd-vol location database of exported filesystems
622 /etc/csh.cshrc system-wide csh(1) initialization file
623 /etc/csh.login system-wide csh(1) login file
624 /etc/csh.logout system-wide csh(1) logout file
631 /etc/pwd.db non-secure hashed user data base file
633 /etc/security daily system security checker
636 System security changes require adding several new ``well-known'' groups to
638 The groups that are needed by the system as distributed are:
649 bin 7 group for system binaries
653 staff 20 system staff
654 guest 31 system guests
664 now run set-group-id to ``daemon'' so that users cannot
671 Standard system programs that require this access are
672 made set-group-id to that group.
682 now run set-group-id to ``tty''.
687 can access the filesystem information without being set-user-id to ``root''.
692 the system without root access.
697 programs now run set-user-id ``root'' instead of ``daemon.''
706 \fB#\fP \fIchown \-R root /var/spool/at\fP
707 \fB#\fP \fIchown \-R uucp:daemon /var/spool/uucp\fP
708 \fB#\fP \fIchmod \-R o\-w /var/spool/uucp\fP
713 has been changed to specify the user-id that should be used to run a process.
714 The userid ``nobody'' is frequently useful for non-privileged programs.
733 and that host names are now fully specified as domain-style names
742 to do nightly security checks on the system.
747 each night, and mails the output to the super-user.
768 Finally, the system binaries are checksummed and their permissions
774 The C-library and system binaries on the distribution tape
805 has also been changed to add certain well-known addresses.
821 functions will no longer return an encrypted password string to non-root
823 An old-style passwd file is created in
833 Several new users have also been added to the group of ``well-known'' users in
852 The ``operator'' user-id is used as an account for dumpers
857 and is noted here just to provide a common user-id.
859 the user with least privilege. The ``games'' user is a pseudo-user
874 use the `\-p' option to
878 an existing system into a new
893 cd $SRC; tar cf - msgs preserve | (cd /var && tar xpf -)
899 tar cf - at mail rwho | (cd /var && tar xpf -)
900 tar cf - ftp mqueue news secretmail uucp uucppublic | \e
901 (cd /var/spool && tar xpf -)
908 tar cf - * | (cd /var/spool/output && tar xpf -)
929 tar cf - . | (cd /var/account && tar xpf -)
931 rm -f msgbuf
932 mv messages messages.[0-9] ../log
933 mv wtmp wtmp.[0-9] ../log
939 a new virtual memory system,
943 a log-structured filesystem,
946 enhanced security and system management support,
951 The kernel sources have been reorganized to collect all machine-dependent
953 and most of the machine-independent code is now free of code
956 to eliminate the statically-mapped user structure and to make most
958 The system and include files have been converted to be compatible
961 There are numerous other changes throughout the system.
965 The kernel uses a new internal system call convention;
966 the use of global (``u-dot'') variables for parameters and error returns
968 and interrupted system calls no longer abort using non-local goto's (longjmp's).
970 returning characteristic errors to abort or restart the current system call.
973 The old sleep interface can be used only for non-interruptible sleeps.
1001 .IP \-1
1002 Permanently insecure mode \- always run system in level 0 mode.
1004 Insecure mode \- immutable and append-only flags may be turned off.
1007 Secure mode \- immutable and append-only flags may not be cleared;
1012 are read-only.
1014 Highly secure mode \- same as secure mode, plus disks are always
1015 read-only whether mounted or not.
1019 while the system is multi-user.
1022 and the \-\fBo\fP option to
1024 for information on setting and displaying the immutable and append-only
1027 Normally, the system runs in level 0 mode while single user
1034 If it is desired to run the system in level 0 mode while multiuser,
1039 initialized to \-1.
1043 operating system developed at Carnegie-Mellon,
1050 efficient memory utilization using copy-on-write
1051 and other lazy-evaluation techniques,
1055 The Mach virtual memory system call interface has been replaced with the
1056 ``mmap''-based interface described in the ``Berkeley Software
1069 short-comings of the current Mach virtual memory system.
1075 Swap space is allocated on-demand rather than up front and no
1076 allocation checks are performed so it is possible to over-commit
1081 system call are slightly different.
1090 transport class 4 (TP-4),
1092 and 802.3-based link-level support (hardware-compatible with Ethernet\**).
1096 We also include support for ISO Connection-Oriented Network Service,
1097 X.25, TP-0.
1117 The OSI equivalent to ARP is ESIS (End System to Intermediate System Routing
1145 address family and family-specific data)
1147 as have the address family-specific versions of this structure.
1154 System calls that pass a
1164 field for those system calls.
1165 System calls that pass a
1171 receive a completely filled-in
1175 the new library uses a different system call number.
1203 (this variance in length is nearly guaranteed by the presence of link-layer
1208 specified in the IEEE Std1003.1 system interface standard.
1210 byte-range file locking, and saved user and group identifiers.
1225 is used to mount a sub-tree of an existing filesystem
1226 that uses a different set of uids and gids than the local system.
1250 the root filesystem is initially mounted read-only
1255 The root filesystem may be made writable while in single-user mode
1259 mount \-uw /
1262 including the ability to upgrade a filesystem from read-only to read-write
1263 or downgrade it from read-write to read-only.
1273 However, it can be configured on a per-mount basis to run over TCP.
1275 gateways and over long-haul networks.
1295 to a blank-separated format to allow colons in pathnames.
1297 A new local filesystem, the log-structured filesystem (LFS),
1298 has been added to the system.
1299 It provides near disk-speed output and fast crash recovery.
1301 for the Sprite operating system at Berkeley.
1312 For an in-depth description of the implementation and performance
1313 characteristics of log-structured filesystems in general,
1317 We have also added a memory-based filesystem that runs in
1327 The quota system has been rewritten to support both
1334 The system security has been greatly enhanced by the
1337 Once set, these flags can only be cleared by the super-user
1338 when the system is running in insecure mode (normally, single-user).
1339 In addition to the immutable and append-only flags,
1340 the filesystem supports a new user-settable flag ``nodump''.
1348 See the ``-h'' flag to
1352 system crash dumps, and object files generated by the compiler.
1373 so a user-level application is unaware of their special treatment.
1374 Unlike pre-\*(4B systems, symbolic links do
1382 An implementation of an auto-mounter daemon,
1384 was contributed by Jan-Simon Pendry of the
1386 See the document ``AMD \- The 4.4BSD Automounter'' (SMM:13)
1409 The \*(4B system uses the IEEE P1003.1 (POSIX.1) terminal interface
1411 The terminal driver is similar to the System V terminal driver
1426 A new system call,
1428 creates a job-control session consisting of a single process
1438 Programs that allocate controlling terminals (or pseudo-terminals)
1444 pseudo-terminals and other terminals as controlling terminal; see
1454 with the new system.
1459 .Sh 4 "Native operating system compatibility"
1462 built for the native operating system (HP-UX or SunOS) by emulating
1463 their system calls.
1467 Though this native operating system compatibility was provided by the
1469 it is complete enough to run several non-trivial applications including
1470 those that require HP-UX or SunOS shared libraries.
1482 However, by using system call tracing and
1508 but supports traditional C as a command-line option.
1509 The system libraries and utilities all compile
1561 is for historic reasons only, and the system make configuration files in
1568 hierarchy on the local system, and another on each
1569 system that shares the source filesystem.
1581 (that may be mounted read-only).
1584 The Kerberos authentication system designed by MIT (version 5)
1590 at the system administrator's discretion.
1600 Each system needs the file
1613 Note that the password-changing program
1618 .Li \-l
1627 timezone for the system should be copied to
1691 gain, often of four or five to one in system time.
1702 a flat-file interface for fixed or variable length records
1715 have been added to the system.
1718 function is optimized for data with pre-existing order,
1723 functions are variants of most-significant-byte radix sorting.
1745 ANSI C multibyte and wide character support has been integrated.
1746 The rune functionality from the Bell Labs' Plan 9 system is provided
1769 An application front-end editing library, named libedit, has been
1770 added to the system.
1773 libkvm, has been integrated into the system.
1782 programs that display system status information, implementations of
1796 amd An auto-mounter implementation.
1800 calendar Addition of an interface for system calendars.
1803 chflags A utility for setting the per-file user and system flags.
1810 csh Freely redistributable and 8-bit clean.
1816 fstat Utility displaying information on files open on the system.
1822 kdump A system-call tracing facility.
1823 ktrace A system-call tracing facility.
1827 locate A database of the system files, by name, constructed weekly.
1842 sysctl MIB-style interface to system state.
1843 tcopy Fast tape-to-tape copying and verification.
1847 uname The POSIX 1003.2 system identification utility.
1848 vis A filter for converting and displaying non-printable characters.
1858 cross-compile \*(4B on another system.
1882 Since the stat st_size field is now 64-bits instead of 32,
1971 Locally-written debuggers that try to check the magic number
1977 This is primarily to protect users' files in publicly-writable directories
1982 All publicly-writable directories should have their ``sticky'' bits set