Re: build.sh install to a remote machine with sshfs

["Dr. Nicola Mingotti" <nmingotti%gmail.com@localhost>]

Thank you Chris,

for this week i will stick with moving the *.tgz sets as you do,
i just finished and it works.

Still, there are a few drawbacks:
- some important files are overwritten : rc.conf, /etc/passwd ...
  once [a few hours ago] i lost /etc/fstab (but i was copying one set 
at a time and
  rebooting to see what happens)
- it is really slow to un-tar all to the block (~ 20min), ./build.sh 
XXXX install=YYY was
  super quick [unfair comparison, that was on a bigger machine ]
+ at least /home/FOO directories are not overwritten so that is a safe place
   to keep config files between the changes

bye
Nicola




On Wed-09-Oct-2024 18:28, Christoph Badura wrote:
> I have no clue about sshfs and this particular pax error message.
>
> You could give mount_psshfs(8) a try.  Maybe you have better luck with that.
> I've briefly used that a couple of years ago.  But not with build.sh.
>
> What I usuall do is build sets and extract them on the remote system.
> I.e.:
>
> ssh root@remote tar -xzp -C /somehere
>
> --chris