home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!udel!apache.dtcc.edu!apache.dtcc.edu!not-for-mail
- From: weave@apache.dtcc.edu (Ken Weaverling)
- Newsgroups: comp.sys.m88k
- Subject: Summary: Making /var a separate partition
- Date: 26 Jan 1993 08:35:25 -0500
- Organization: Delaware Technical & Community College
- Lines: 59
- Message-ID: <1k3emtINN1bk@apache.dtcc.edu>
- References: <1k088uINNft6@apache.dtcc.edu> <1993Jan25.235718.22508@hubcap.clemson.edu>
- NNTP-Posting-Host: apache.dtcc.edu
- Summary: Not too difficult at all
- Keywords: DG Data General AViiON
-
- First of all, thanks to Morris Galloway for his post and his mail to me
- regarding the subject, I followed his method with a few minor changes...
-
- I did the following under single user mode (init 1)
-
- 1) Ran diskman
- Created a logical partition named var
- 2) Ran sysadm and added the file system but DID NOT have sysadmin mount it
-
- 3) Ran the following unix commands to copy the data over
- a) umount /var/spool/news (gotta unmount anything mounted in that directory)
- b) mkdir /var2
- c) find /var -depth -print | cpio -pdlmv /var2
- (this ensures that file modes and ownerships, links, etc are copied)
- (then I verified that everything copied OK)
- d) rm -rf /var
- e) mkdir /var
- f) mkdir /var/tmp
- (this was a paranoia step. I intended to symbolic link /tmp to
- /var/tmp but worried that someone might want to write to /tmp
- when /var was unmounted, so I created /var/tmp under root just
- in case. However, if /var is later mounted, anything in the root
- /var/tmp will be unavailable, so caution is needed there)
- g) umount /var2
- h) mount /var (fstab was edited by sysadm already)
- i) rm -rf /tmp
- j) ln -s /var/tmp /tmp
-
- 4) I did *not* edit any rc scripts.
- 5) I *did* edit /etc/dgux.params to set verbose_FLAG to true so I could
- watch if anything weird happened during reboot
- 6) I then rebooted and watched. It seems that all filesystems are mounted
- before any scripts in /etc/rc3.d are executed, so when S113.update runs
- and cleans up mail and spool and lock directories, /var is already mounted
- and there isn't a problem. I guess S114.mountfs is redundant or is
- needed when you change run levels from a few other states perhaps.
-
- So, my new file system layout looks like below. If anyone notices anything
- weird or dangerous, I'd appreciate a holler. Thanks!
-
- filesystem kbytes used avail capacity mounted on
- /dev/dsk/root 20000 13668 4404 76% /
- /dev/dsk/usr 120000 104367 4068 96% /usr
- /dev/dsk/opt_contrib 297500 200499 82677 71% /usr/opt/contrib
- /dev/dsk/usr_opt_openmac 10000 4569 4467 51% /usr/opt/openmac
- /dev/dsk/usr_opt_pci 2500 1896 369 84% /usr/opt/pci
- /dev/dsk/var 40000 6027 32045 16% /var
- /dev/dsk/news 639861 416150 205194 67% /var/spool/news
- /dev/dsk/local 160000 121353 32462 79% /local
- /dev/dsk/guest 20000 9502 8572 53% /u/guest
- /dev/dsk/staff 160000 98225 46358 68% /u/staff
- /dev/dsk/student 160000 98936 45647 68% /u/student
-
-
- --
- Weave's 10/90 recipe for insanity: Take one programmer, divide into portions:
- 10% programming consisting of equal parts in systems and applications plus
- admin duties broken down into 20% for Unix, 5% PRIMOS, 10% hardware & network,
- 35% DOS/Windows, 10% news, 5% postmaster, and 5% babysitting IRC kiddies.
-