Posted: Thu 17 Feb 2011, 09:31
anyone knows, how to make nfs client run at initrd.gz, so can look at pup.sfs on virtual drive?
READ-ONLY Archive
https://oldforum.puppylinux.com/
I'm not sure if I understand your question> Are you using the PXE approach mentioned here and finding that it is inadequate for your needs?mhanifpriatama wrote:anyone knows, how to make nfs client run at initrd.gz, so can look at pup.sfs on virtual drive?
So maybe samba is better?sunburnt wrote:I think Barry has added PXE booting of Puppy-2.16.
In our discussion he mentioned NFS, so maybe it's part of Puppy-2.16.
Otherwise.. I think that there's a DotPup or something for installing NFS.
Note: NFS doesn't seem to be used so much anymore.
Samba is much more popular & is easier to setup (I've read & my personal experiance).
Samba is about as fast as NFS & much more secure, it's size is a little larger.
Puppy already has good Samba client tools, it just needs Samba server.
There's a Samba server DotPup at MU's site: http://puppyfiles.org
I suggested to Barry that he might include it so Puppy would be just like Win.
Good, now I have a better understanding. I CANNOT solve either the NFS issue you raise NOR the changing boot structure that a LiveCD (or PXE) gives you. But, I will try to help by showing you 2 things.mhanifpriatama wrote:thanks gc.martin,
I want my server run nfs server. I think that kernel module.
So, my server can offer drive-sharing (like virtual hard drive).
I want my client run nfs-client. I think that kernel module too.
So, my client can see the virtual drive.
If nfs-client can run before loading my lupu_520.sfs, I can place it at virtual drive, then the init script can mount it.
I think this will solve the old computer client with very low ram. ....
So ... after booting to desktop.. hmmm ...My PXE clients, after booting to desktop of course, can read and write to that SAMBA server using either the GUI tools provide in the PXE's PUP or using the "mount" feature of the system.
Code: Select all
mount -t nfs server_ip_address:/sharename /mnt/mountpoint
Code: Select all
mount -o loop /mnt/mountpoint/pup.sfs /initrd/pup_ro2
i already compile them1. NFS server - relatively easy - if your puppy version doesn't support in-kernel nfs server, you can always get this http://unfs3.sourceforge.net/ and compile yourself a server.
sorry, but noone also need to have portmapper running to be able to use it. If you could compile it for other puppies it would be very helpful.
if you see the script you will understand.Quote:
-p
Do not register with the portmapper. This will prevent other hosts from finding out the port numbers used for the MOUNT and NFS services by querying the portmap daemon. Clients will need to manually specify the port numbers to use (on Linux clients, use the mountport and port mount options).
Code: Select all
##############END MODULE LOADING TO ACCESS DRIVES####################
mkdir /mnt/try
mount -o port=4711,mountport=4711,mountvers=3,nfsvers=3,nolock,tcp 169.254.33.219:/root /mnt/try
#######################FINDING PUPPY FILES###########################
Code: Select all
#mount -o port=4711,mountport=4711,mountvers=3,nfsvers=3,nolock,tcp 169.254.33.219:/root /mnt/try
mount: mounting 169.254.33.219:root on /mnt/try failed
alsoprompt 1
default linux
timeout 100
label linux
kernel bzImage
append init=/sbin/init root=/dev/nfs rw nfsroot=192.168.0.1:/nfsroot ip=192.168.0.254:192.168.0.1:192.168.0.1:255.255.255.0:llama0::off noapic acpi=off
Yes, I booted Fatdog over nfs. There are two ways of doing it:Master_wrong wrote:@jamesbond
is that teaser means you can boot with pxe and nfs already ?
thats awesome...
Can I get your "puppy modified"? That just init script?a) running puppy modified to load its pup.sfs from nfs [my first screenshot] - this is like running frugal install but the "harddisk" where the pup.sfs is stored is nfs
maybe nfs need to be unmounted first... ?Note: those steps above are working but aren't clean, they're used for proof-of-concept only that it works. They won't shutdown cleanly, I think there's some shutdown code which mucks with the network. I did the test with Fatdog, but it should work with all puppies.