From: joann@ariadne.SLAC.Stanford.EDU (Jo Ann Malina)
Newsgroups: bit.listserv.aix-l
Subject: Re:      Re: choosing mount points, expanding files
Date: 4 Nov 92 06:25:45 GMT
Reply-To: joann@unixhub.slac.stanford.edu
Organization: SLAC (Stanford Linear Accelerator Center)

In article <AIX-L%92110317420355@PUCC.PRINCETON.EDU>,         Bruce Posey <POSEY@OHSTPHRM.BITNET> writes:

|> >1. We will be installing a number of third-party products. What is the most
|> > sensible mount point? One of the products is INGRES database (100Mb). Our
|> > machine will have about 1.8 gig when we finish. We are condidering /usr as
|> > the mount point.

I don't know anything about INGRES -- if it's a single command that learns
where its home directory is when you install it, you can put those files
just about anywhere. /usr/local/INGRES or /usr/apps/INGRES are possibilities.
If there's a possibility INGRES will expand (from growing log files, database,
etc), put it in its own partition.

|> On Tue, 3 Nov 1992 14:38:00 EST Leo McCarthy said:
|> >2. /usr shows as 98% used. I am going to need to expand it soon. There does not
|> >   appear to be any on-the-fly way of doing so. Do I absolutely have to backup
|> >   /usr, delete it, recreate/re-size it, and restore it?
|> 
|> /usr can be expanded on the fly but it cannot be shrunk.  Do an extendlv
|> command with the appropriate switches and parameters followed by a chfs command
|> with the appropriate number of 512 byte blocks for the whole /usr filesystem.
|> Make sure you specify the number of blocks for the whole filesystem and not
|> just the newly added partitions.  That will leave you in big trouble.

Nah, just expand the file system. That expands the logical volume underneath it:
SMIT -- Physical & Logical Storage -- File Systems -- Add/Change/Show/Delete
File Systems -- Journaled File Systems -- Change/Show Characteristics of a
Journaled File System.  Select /usr.  If you add 1 to the number of blocks, it
will be rounded up to the next physical partition, 4Mb unless you've changed it.

|> > 3. We are concerned with security on the machine. We are disabling TFTP, and
|> > taking numerous other measures. Are there any favorite things to look out
|> > for?

One thing you can do to keep up on discoveries is to subscribe to the CIAC
(Computer Incident Advisory Capability) Information Bulletin. Contact David
Brown, ciac@llnl.gov (510/423-9878). Old bulletins are available via anonymous
ftp from irbis.llnl.gov (128.115.19.60).

Directory of the CIAC archives

/pub/ciac/archives/ciac      CIAC documents
/pub/ciac/archives/cert      CERT documents
/pub/ciac/archives/nist      NIST documents
/pub/ciac/archives/ddn       DDN documents
/pub/ciac/archives/nasa-span NASA/SPAN documents

/pub/ciac/virus/virus-l      Virus-L Moderated News
/pub/ciac/virus/msdos        MS-DOS/PC-DOS anti-virus software and utilities.
/pub/ciac/virus/mac          Macintosh anti-virus software and utilities.
/pub/ciac/virus/atari        Atari anti-virus software and utilities.
/pub/ciac/virus/books        Virus bibliography
/pub/ciac/virus/docs         More virus documents
/pub/ciac/virus/reviews      Published reviews of anti-virus software

/pub/ciac/docs               Incident handling guidelines

*) *) *) *) *) *) *) *) *) *) *)!(* (* (* (* (* (* (* (* (* (* (* (* (*
Jo Ann Malina, Stanford Linear Accelerator Center
joann@unixhub.slac.stanford.edu  -or-  415/926-2846
Neither Stanford nor the DOE would be caught dead with these opinions.
Nor do they consult me when formulating theirs.
Newsgroups: bit.listserv.aix-l