i installed solaris 10 11/06 in x86.. The ouput of df command shows that 5.5GB is in /dev/dsk/c1d0s0 which is mounted in / and 38GB in /dev/dsk/c0d0s7 which is mounted in /export/home.. of the 5.5GB in / only 23MB is free... I need modify the partition table such that i need to decrease the size of /export/home and increase the size of /..

Are there unused/unmounted partitions between s0 and s7? You can use format to modify the partition tables, but shrinking one is a totally different story from growing one. I'm not sure you can get away with that. If you had almost nothing in /export/home and were willing to newfs it, then you could do it. Or tar it out to somewhere, make the changes, newfs it, and then tar it back.

I've changed partition tables on live drives and gotten away with it, but I was just changing unused partitions before putting them into use. You have to be absolutely careful, because, if you make a mistake, you could blow the whole thing. Since you are wanting to increase /, I believe you will have to use growfs after changing the tables.

Check all the man pages. Double check everything you do before committing. Do a backup before you start if you want to be extra careful.

Or you could just go through the whole install again and just allocate space appropriately.

I'd recommend starting over and rebuilding the box if you can. If you try to modify the / partition and aren't careful with you start/stop cylinders you'll end up blowing away the partition.

Another option if you can't rebuild is to offload some of the stuff off of root to a different partition and setup sym links to point back. For example you could mv /opt and sym link it to /export/home/opt... Good luck!

Beware that you need to be very careful when selecting directories to offload. Some directories are required to be on / for the boot process to succeed.

Another point: /opt is a good choice to be relocated on a different filesystem. I would however recommend not to use symbolic links for directories containing files belonging to packages. The reason is the symlink would be broken after any patch or further package installation.

Use lofs mounts instead which do not exhibit this issue.

eg. in /etc/vfstab