This is a discussion on migrating slackwareOS to a new hard drive? within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> In news:Xns953AD15B1D605jbuserspc9org@205.200.16.73, Jem Berkes bitched and moaned: >> GNU tar does. I've done complete network transfers of disk contents ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| In news:Xns953AD15B1D605jbuserspc9org@205.200.16.73, Jem Berkes bitched and moaned: >> GNU tar does. I've done complete network transfers of disk contents >> using tar and netcat. > > Aren't there also some other things that could be happening with > /proc and /dev, like dynamic content creation? I can't remember the > details but I thought I'd throw that out there. tar cannot read the entire /proc tree, but that is mostly the pid's |
| |||
| |> GNU tar does. I've done complete network transfers of disk contents |> using tar and netcat. | |Aren't there also some other things that could be happening with /proc and |/dev, like dynamic content creation? I can't remember the details but I |thought I'd throw that out there. I normally exclude /proc from the tar since its contents are virtual. /dev is ok to tar, GNU tar knows what to do with device files. -- |
| |||
| Jem Berkes wrote: > Aren't there also some other things that could be happening with /proc > and /dev, like dynamic content creation? I can't remember the details > but I thought I'd throw that out there. With /proc, just creating the directory should be sufficient since it's dynamically created and altered as Linux runs. /dev can change, however unless udev is being used, the individual devices can be copied and used quite easily. |
| |||
| D. Phan wrote: > hello there > > My old hard drive in which is running slackware 10.0 is now so noisy > with high frequency. I now wanna move whole contents in the old to a new > harddisk. Please tell me your experience about that > much appreciated, > regards > d.phan > my system: slackware 10 (ker-2.4.26/cpu 450mhz - 128MB ram) with no X > and X apps, and managed by puTTY (ssh) from XP clients Thanks for all information and help this weekends would be relaxed right at the box to move data to the new one. cheers |
| |||
| On Wed, 4 Aug 2004 qyswmhk@ojdmyw.com wrote: > |> GNU tar does. I've done complete network transfers of disk contents > |> using tar and netcat. > | > |Aren't there also some other things that could be happening with /proc and > |/dev, like dynamic content creation? I can't remember the details but I > |thought I'd throw that out there. > > I normally exclude /proc from the tar since its contents are virtual. > /dev is ok to tar, GNU tar knows what to do with device files. /proc is a seperate filesystem. if you give tar the --one-file-system, it will be excluded. tarring it up is kind of pointless anyway, since only a snapshot of it's outputs is preserved, and restoring it does not producce a functional proc filesystem. note, just for giggles, that you can mount a proc filesystem anywhere. eg., mkdir /tmp/foo && mount -t proc none /tmp/foo. but above /dev, i just did a fast test, tar -cpf /tmp/dev.tgz /dev/, and tar did bitch about socket /dev/log ... not sure if that's a problem or not. but i've never notied any negative results from using the technique in practice. -- Fire the Liars - Impeach Bush and Cheney! Prosecute the criminals - Indict Rumsfeld and Ashcroft! Corruption starts at the top. William Hunt, Portland Oregon USA |
| |||
| On Tue, 3 Aug 2004, Stanislaw Flatto wrote: > William Hunt wrote: > >> verify everything is working. >> fill new drive up with lots of new stuff until full. >> buy bigger drive. >> goto (1). >> >> > :-D > > Should be published as Mini-HOWTO for *every* OS. > Having fun > Stanislaw > Slack user from Ulladulla. but of course - what is the point of newer, bigger, and faster if not to fill it up, tear it up, and wear it out ? > -- Fire the Liars - Impeach Bush and Cheney! Prosecute the criminals - Indict Rumsfeld and Ashcroft! Corruption starts at the top. William Hunt, Portland Oregon USA |
| |||
| |> I normally exclude /proc from the tar since its contents are virtual. |> /dev is ok to tar, GNU tar knows what to do with device files. | |but above /dev, i just did a fast test, tar -cpf /tmp/dev.tgz /dev/, |and tar did bitch about socket /dev/log ... not sure if that's a |problem or not. but i've never notied any negative results from |using the technique in practice. Yes, that's the other little detail, tar doesn't grab Unix sockets but that's ok since those will be created by the app that needs them on the other side. -- |
| |||
| William Hunt <wjh@huntbros.net> writes: > (5) use tar to copy live data from old mountpoints to new mountpoints. > for example: > > OLDMNT=/ > NEWMNT=hdb2 > cd ${OLDMNT} > tar --one-file-system -cpvf - . | ( cd ${NEWMNT} ; tar -xpf - ) > I think its advisable to replace (cd ${NEWMNT} ; tar -xpf - ) with (cd ${NEWMNT} && tar -xpf - ) so that in the case of making some typo in ${NEWMNT} you don't end up messing your files... -- Sami |
| |||
| On Wed, 4 Aug 2004, Sami Nuuttila wrote: > William Hunt <wjh@huntbros.net> writes: >> (5) use tar to copy live data from old mountpoints to new mountpoints. >> for example: >> OLDMNT=/ >> NEWMNT=hdb2 >> cd ${OLDMNT} >> tar --one-file-system -cpvf - . | ( cd ${NEWMNT} ; tar -xpf - ) > > I think its advisable to replace (cd ${NEWMNT} ; tar -xpf - ) with > (cd ${NEWMNT} && tar -xpf - ) so that in the case of making some typo > in ${NEWMNT} you don't end up messing your files... yes, you're right, very good point. -- Fire the Liars - Impeach Bush and Cheney! Prosecute the criminals - Indict Rumsfeld and Ashcroft! Corruption starts at the top. William Hunt, Portland Oregon USA |
| ||||
| On 2004-08-04, W <still@none.com> wrote: > In news:Pine.LNX.4.58.0408031001140.11811@worker.hunt bros.net, William > Hunt bitched and moaned: >> (5) use tar to copy live data from old mountpoints to new mountpoints. >> for example: >> >> OLDMNT=/ >> NEWMNT=hdb2 >> cd ${OLDMNT} >> tar --one-file-system -cpvf - . | ( cd ${NEWMNT} ; tar -xpf - ) > > `tar` does not recreate /dev properly, the last time I looked. > > Maybe I do stuff wrong but I just go into the root directory of the old drive and do this, which works everytime BTW. In fact just did it last week. cd / cp -a * /newdrive Make sure and do all the necessary fstab stuff and yer done. pretty simple, but then I'm a simple minded kinda guy. PS, yeah I know about dot files but I have never had any in my / directory and the dot files in all the other directories copy just fine. Widgeteye -- -------------------------------------------- [Thou] rump-fed ronyon! -William Shakespeare, Macbeth |