Lines Matching +full:files +full:- +full:based
40 files are different, and the executable file formats are completely
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.
78 but files will still need to be moved around.
85 onto empty disks, and then merge or restore any existing configuration files
91 configuration files and filesystems; or
93 and use that system to cross-compile and install \*(4B.
102 then site-specific files should be merged into them.
124 filesystem can be an MFS virtual-memory-resident filesystem,
137 Extract kernel and/or user-level sources from the distribution tape
150 Merge site-dependent configuration files from
160 Copy or merge files from
175 Section 3.2 lists the files to be saved as part of the conversion process.
177 Section 3.4 discusses the merger of the saved files back into the new system.
182 .Sh 2 "Files to save"
184 The following list enumerates the standard set of files you will want to
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
191 image of the following files before the new filesystems are created.
192 The rest of this subsection describes where theses files
209 /etc/named* \(dg named configuration files
217 /etc/remote \(dg auto-dialer configuration
232 /usr/lib/mail.rc \(dg system-wide mail(1) initialization (moves to \f(CW/etc/mail.rc\fP)
235 /usr/lib/uucp/* \(dg for local uucp configuration files
237 /usr/spool/* \(dg for current mail, news, uucp files, etc. (moves to \f(CW/var/spool\fP)
240 /sys/conf/files.HOST \(dg list of special files in your kernel (moves to \f(CW/sys/<arch>/conf\fP)
241 /*/quotas * filesystem quota files (moves to \f(CW/*/quotas.user\fP)
244 \(dg\|Files that can be used from \*(Ps without change.
245 \(dd\|Files that need local changes merged into \*(4B files.
246 *\|Files that require special work to merge and are discussed in section 3.4.
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
284 from architecture specific binary files and should be concentrated below
292 /etc (config files)
293 /bin (user binaries needed when single-user)
294 /sbin (root binaries needed when single-user)
296 /tmp (mount point for memory based filesystem)
299 /var (mount point for per-machine variable directories)
300 /usr (mount point for multiuser binaries and files)
310 /usr/games (binaries for games, score files in \f(CW/var\fP)
311 /usr/include (standard include files)
315 /usr/local (locally added binaries used site-wide)
318 /usr/share (mount point for site-wide shared text)
327 /usr/share/calendar (various useful calendar files)
330 /usr/share/games (games text files)
333 /usr/share/misc (dumping ground for random text files)
335 /usr/share/skel (template user home directory files)
345 /var/account (accounting files, formerly \f(CW/usr/adm\fP)
347 /var/backups (backups of system files)
349 /var/db (system-wide databases, e.g. tags)
350 /var/games (score files)
351 /var/log (log files)
355 /var/quotas (directory to store quota files)
356 /var/run (directory to store *.pid files)
363 /var/tmp (disk-based temporary directory)
364 /var/users (root of per-machine user home directories)
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.
465 .Sh 2 "Merging your files from \*(Ps into \*(4B"
471 merging your old files into the new system.
473 If you saved the files on a
483 The data files marked in the previous table with a dagger (\(dg)
485 Those data files marked with a double dagger (\(dd) have syntax
492 The files marked with an asterisk (*) require
502 that now contains only system configuration files;
504 a new filesystem containing per-system spool and log files; and
506 that contains most of the text files shareable across architectures
514 Various programs and data files formerly in
521 Administrative files formerly in
525 and, similarly, log files are now in
576 directory now contains nearly all the host-specific configuration
577 files.
579 and those configuration files containing pathnames are nearly all affected
586 The following table lists some of the local configuration files
596 /etc/syslog.conf /etc/syslog.conf pathnames of log files changed
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
621 /etc/changelist \f(CW/etc/security\fP files to back up
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
629 /etc/mtree directory for local mtree files; see mtree(8)
631 /etc/pwd.db non-secure hashed user data base file
636 System security changes require adding several new ``well-known'' groups to
656 utmp 45 access to utmp files
664 now run set-group-id to ``daemon'' so that users cannot
665 directly access the files in the spool directories.
666 The special files that access kernel memory,
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''.
697 programs now run set-user-id ``root'' instead of ``daemon.''
701 reverts to privileged status to remove its lock files.
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.
727 You should look closely at the prototype version of these files
733 and that host names are now fully specified as domain-style names
747 each night, and mails the output to the super-user.
752 \(bu Syntax errors in the password and group files.
755 \(bu Dangerous values in various initialization files.
756 \(bu Dangerous .rhosts files.
761 In addition, it reports any changes to setuid and setgid files, special
762 devices, or the files in
766 Backup copies of the files are saved in
774 The C-library and system binaries on the distribution tape
789 For instructions on how to set up the necessary configuration files,
801 configuration files in
805 has also been changed to add certain well-known addresses.
806 .Sh 3 "Shadow password files"
813 The hashed dbm password files do not contain encrypted passwords,
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
876 so that files are recreated with the same file modes.
877 The following commands provide a guide for copying spool and log files from
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
943 a log-structured filesystem,
945 files and filesystems that are up to 2^63 bytes in size,
951 The kernel sources have been reorganized to collect all machine-dependent
952 files for each architecture under one directory,
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
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).
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
1039 initialized to \-1.
1043 operating system developed at Carnegie-Mellon,
1045 It is based on the 2.0 release of Mach
1050 efficient memory utilization using copy-on-write
1051 and other lazy-evaluation techniques,
1056 ``mmap''-based interface described in the ``Berkeley Software
1067 Since the code is based on the 2.0 release of Mach,
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
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.
1145 address family and family-specific data)
1147 as have the address family-specific versions of this structure.
1171 receive a completely filled-in
1203 (this variance in length is nearly guaranteed by the presence of link-layer
1210 byte-range file locking, and saved user and group identifiers.
1225 is used to mount a sub-tree of an existing filesystem
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),
1299 It provides near disk-speed output and fast crash recovery.
1300 This work is based, in part, on the LFS filesystem created
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
1322 clustering that allows large pieces of files to be
1326 files and filesystems to grow to 2^63 bytes in size.
1329 Quota expiration is based on time rather than
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.
1353 Note that the flag is not preserved when files are copied
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)
1391 contains special files
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
1462 built for the native operating system (HP-UX or SunOS) by emulating
1469 it is complete enough to run several non-trivial applications including
1470 those that require HP-UX or SunOS shared libraries.
1478 to auxiliary files that do not exist under \*(4B (e.g.
1495 based on draft 12 of the POSIX.2 Shell and Utilities document.
1505 Most of the libraries and header files have been converted
1508 but supports traditional C as a command-line option.
1525 The standard include files for
1541 descends into that directory and creates all object and other files there.
1561 is for historic reasons only, and the system make configuration files in
1581 (that may be mounted read-only).
1613 Note that the password-changing program
1618 .Li \-l
1624 The timezone conversion code in the C library uses data files installed in
1631 The data files initially installed in
1643 to rebuild the timezone data files so that leap seconds are not counted.
1648 The data files without leap second information
1666 It is possible to install both sets of timezone data files. This results
1671 Each contain a complete set of zone files.
1702 a flat-file interface for fixed or variable length records
1718 function is optimized for data with pre-existing order,
1723 functions are variants of most-significant-byte radix sorting.
1730 based on
1769 An application front-end editing library, named libedit, has been
1796 amd An auto-mounter implementation.
1803 chflags A utility for setting the per-file user and system flags.
1804 chfn An editor based replacement for changing user information.
1805 chpass An editor based replacement for changing user information.
1806 chsh An editor based replacement for changing user information.
1809 cp POSIX 1003.2 compatible, able to copy special files.
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.
1830 make Replaced with a new, more powerful make, supporting include files.
1842 sysctl MIB-style interface to system state.
1843 tcopy Fast tape-to-tape copying and verification.
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,
1934 The kernel's limit on the number of open files has been
1945 Memory allocation does not occur until after 20 files have been opened
1965 Old core files will not be intelligible by the current debuggers
1971 Locally-written debuggers that try to check the magic number
1974 Files may not be deleted from directories having the ``sticky'' (ISVTX) bit
1977 This is primarily to protect users' files in publicly-writable directories
1982 All publicly-writable directories should have their ``sticky'' bits set
1986 changes in \*(4B that affect the installation of local files;