Stan, I like the idea of piping tar to tar. I think that will preserve timestamps, permissions, and the owner, right? About a symlink: A symbolic link seems much easier than remembering the vfstab file during an upgrade, but for me doing: cd /usr/local cd .. and ending up in /opt is a little too weird. I know I have some recursive makefiles that would go nuts if they ran into that sort of thing. > > Here is what I did to make my /usr/local bigger. Will someone please > > comment on the validity of this procedure before I get so far into this > > hole that I can never dig myself out? > > > > Retarget /usr/local to /opt/ulocal > > a) cp -r /usr/local/* /opt/ulocal #Probably should have > done "cp -R ..." > > I'd sugest the following instead hee: > > mkdir /usr/ulocal > cd /usr/local > tar cvf . | ( cd /opt/ulocal ; tar xf -) > > > b) Added line to /etc/vfstab --> "/opt/ulocal/ - > /usr/local lofs - yes -" > > c) renamed /usr/local to /usr/local.orig > > d) mkdir /usr/local > > e) reboot > > > > The idea is to make /usr/local really refer to /opt/ulocal (where I have > > lots of space) > > > >How about a symlink? Winston Jenks Technical Director, Cape Software, Inc. _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave