SLUG Mailing List Archives
Re: [SLUG] re-partitioning HD and re-arranging mount points...
- To: ken@xxxxxxxxxx
- Subject: Re: [SLUG] re-partitioning HD and re-arranging mount points...
- From: Daniel Freedman <freedman@xxxxxxxxxxxxxxxx>
- Date: Fri Nov 17 02:57:55 2000
- Cc: slug@xxxxxxxxxxx, freedman@xxxxxxxxxxxxxxxx
Thanks so much for clarifying these differences.
Was my earlier description of the transfer method pretty much the
standard way of doing it? (Repeated below.)
Thanks so much for your response,
1. Make a new partition on the HD using previously un-partitioned sectors.
2. Build a filesystem on the new partition
3. Mount the new partition (maybe /mnt/temp)
4. Copy the data from /usr/local to /mnt/temp
5. Run md5sum on original data in /usr/local; compare with 'md5sum -c <file>'
to new data on /mnt/temp ***
6. Unmount the old partition from /usr/local
7. Unmount the new partition from /mnt/temp
8. Update /etc/fstab to tell it about new partition for /usr/local
9. Re-mount the new partition over the old mount point
10.Ready to do re-installation
Ken Yap wrote:
> >*** Side question on md5sum: my understanding of ext2fs is that when
> >copying or moving files within a partition, the files are not actually
> >moved or copied, only the inode table is updated (and thus no md5sum
> >is necessary as there is no risk of incorrect I/O related to move);
> >however, when moving between partitions, the files actually have to be
> >copied or moved, and thus an md5sum check would be prudent. Is this
> >correct thinking, please? Thanks so much.
> When you are moving a file within a filesystem, no copying of the data
> blocks is done, only the links are altered. When you are copying a file,
> the data blocks are replicated. When you move a file outside the
> filesystem, it behaves like a copy and unlink.
Daniel A. Freedman
Laboratory for Atomic and Solid State Physics
Department of Physics