From: "Joseph C. Lininger" <jbahm@pcdesk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: moving /var and /home to a new partition
Date: Thu, 31 Mar 2005 19:07:53 -0700 (Mountain Standard Time) [thread overview]
Message-ID: <Pine.WNT.4.62.0503311906570.2556@merlin> (raw)
In-Reply-To: <004a01c53564$b3eca7c0$0d00a8c0@Saidar>
Hi,
mv automatically preserves all owner, group, and permition information.
What you want to do should work just fine.
Equal causes can produce very unequal effects.
Joseph C. Lininger
jbahm@pcdesk.net
Verification: 5eab38a77ac40416e075be8f50607ff7
And so it came to pass that on Wed, 30 Mar 2005, Raul A. Gallegos said
> Hi. I have FC3 installed and currently use the following on one hdd:
>
> /hda1 swap
> /hda2 /
> /hda3 /usr/local
> /hda4 /home
>
> I did this because at time of install I only had one drive. Now I
will be
> installing a second drive for /home only. So what I want to do is
move /home
> to /hdc1 and then move /var to home's current partition /hda4.
>
> I boot into single user mode first and edit fstab.
>
> I know how to edit /etc/fstab but my question is what parameters I
should
> give mv when moving the directories.
>
> I figured I could temporarily mount /hdc1 as /newhome then:
>
> cd /home
> mv * /newhome
>
> Now I can umount /newhome
>
> Now for /var I could do:
>
> cd /var
> mv * /home
>
> So when I reboot all the /var files will be in /home's old partition
/hda4
> and the new /home will be on /hdc1.
>
> What I'm worried about is preserving all permissions, ownerships, etc.
>
> Does this all look right?
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Raul A. Gallegos
` Janina Sajka
` Raul A. Gallegos
` Steve Dawes
` Janina Sajka
` Raul A. Gallegos
` Joseph C. Lininger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.WNT.4.62.0503311906570.2556@merlin \
--to=jbahm@pcdesk.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).