Re: [Sheflug] NFS the hard way

["Barrie Bremner" <nospam [at] barriebremner.com>]

I'm lost here.

What init level are you running at?
Out of interest, which distro?
What does "ifconfig" give on both the source and target machines?
Have you got a working system in the target machine?
Have you done anything funny with /etc/hosts.[allow/deny]

If all the crap I list below doesn't work, or you can't get the target
machine's network up, stick the target drive in a system that is known
to work and use NFS that way, however:

Graham's suggestion of sticking in the drive for the backup/new
machine into the server and dd'ing or my prefered method:

(cd /source/directory && tar cf - . ) | (cd /dest/directory && tar xvfp -)

this one is a little slow, because you will have to cd into all the
directories to be copied, since just cd / && tar... will copy things
like temp, /proc and /dev.
There is also

cp -av /source/directory /dest/directory

 same problems apply.

Still I managed to copy my entire system several times a few weeks
back when I was moving to ReiserFS using the tar method with no
problems...just compare things carefully!

If you must use NFS, move up from single user mode - I'm sure network
behaviour is funny in that mode.

Boot the server to init 3.
If you don't want people logging in:

touch /etc/nologin

Start portmap, nfsd, mountd etc

Check access permissions, exports and the like.

Boot the client machine - have you already got a working system on the
client machine?
If not, I'd rip an HDD from another machine and use that to run the
client machine, and have the empty drive there too - I'd rather use a
full working system instead of a bootdisk - because I'm crazy - but at
least you're gonna have all the programs you're gonna need.

Start portmapper on the client. Mount the server's exported
directories.

Go for it.

I know I'm repeating a few things, but I'm trying to give a complete
check list...





James Wallbank writes:
 > Hi Guennadi,
 > 
 > I like the idea of running the machine as client, not server. The 
 > only problem is I'm running the target machine as a client...
 > 
 > >3) Run this machine as client, not server - the other one as server. In
 > >this case you might be able to boot, say, from a single-floppy Linux
 > >(e.g. tomsrtbt)...
 > 
 > ..using tomsrtbt just as you suggest! The problem is that the target 
 > h/d is completely empty. It's just formatted with hda1 (ext2) and 
 > hda2 (swap) just like the original machine - I want to transfer the 
 > whole of the OS across if I can. Of course, if only tomsrtbt (or 
 > another Linux from floppy) had NFS server capability built in...


-- 
Barrie J. Bremner

email: baz at barriebremner.com | OpenPGP ID: 5164F553

http://barriebremner.com/
[Contact information available at website]

   "Linux? Is that some kind of MacOS?"
      -- BT technical support

---------------------------------------------------------------------
Sheffield Linux User's Group - http://www.sheflug.co.uk
To unsubscribe from this list send mail to
- <sheflug-request [at] vuw.ac.nz> - with the word 
 "unsubscribe" in the body of the message. 

  GNU the choice of a complete generation.