Widgeteye wrote:
>
> 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 that you don't have any CDROMs mounted or they will get cpied
too!

jamess

James wrote:

> Widgeteye wrote:
>>
>> 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 that you don't have any CDROMs mounted or they will get cpied
> too!

I've heard that it can have problems copying /dev/* and /proc/*; at least
they won't be correct at the target.

And I think cp gets confused when it starts trying to copy /newdrive onto
itself.

Have Fun!
Rich

> D. Phanwrote:
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

If you use slackware's package management, you can take the contents
of /var/log/packages replicate the packages you have installed onto
the new disk (whether on the same machine or another). When the new
disk is installed and mounted to say /new_disk, you set
ROOT=/new_disk and use pkgtools to install each package listed in the
original boxes /var/log/packages.

I use this all to the time to build usermode linux filesystems with
slapt-get:

ls /var/log/packages/|ROOT=/new_disk xargs -r slapt-get --install

Message posted via:
=====================
www.linuxpackages.net/forum
www.linuxpackages.net
Expanding the world of Slackware
=====================

Rich Grise wrote:
>
>
> I've heard that it can have problems copying /dev/* and /proc/*; at least
> they won't be correct at the target.
>
> And I think cp gets confused when it starts trying to copy /newdrive onto
> itself.

Before I installed Slack 10 I cpied everything to the #$@@$ IDE HDD. It
copied /dev just fine. One time not to long ago I was installing some
software and the docs told me to run a chmod command on a program in
/dev. I actually copied and pasted the command into the terminal so I
wouldn't screw it up. It turned out that I didn't have the dev file that
was supposed to be chmoded and it corrupted the *whole* /dev directory.
If I tried to log on as anybody but root I would get an error message
about not enough pttys being available. I just mved /dev to dev.old and
reinstalled /dev from the Slack install CD. It worked out quite well. So
much for RTFM and actually doing what it says!

Keep on Slackin'

jamess

On 2004-08-13, Rich Grise <null@example.net> wrote:
> James wrote:
>
>> Widgeteye wrote:
>>>
>>> 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 that you don't have any CDROMs mounted or they will get cpied
>> too!

Well ya do have to use a little common sense.


>
> I've heard that it can have problems copying /dev/* and /proc/*; at least
> they won't be correct at the target.
>
> And I think cp gets confused when it starts trying to copy /newdrive onto
> itself.

Never ran into a problem. And have been doing it this way since
the early 90's.
Nothing has ever been broken by the process. Maybe I m just damned lucky.
For years.

>
> Have Fun!
> Rich
>


--
--------------------------------------------
[Thou] rump-fed ronyon!
-William Shakespeare, Macbeth