All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Alkoff <labradley@mindspring.com>
To: nfs@lists.sourceforge.net
Subject: Exportfs does not accept Knoppix /ramdisk/home
Date: Mon, 13 Jun 2005 18:19:42 -0500	[thread overview]
Message-ID: <42AE148E.80904@mindspring.com> (raw)

Please forgive me for bothering you but I and other Knoppix users have a
vexing problem trying to export the Knoppix home directory which is on a
ram disk.

Each time I try to issue
exportfs -rav
an "invalid argument" error message is produced.
However the root / directory is exported without error.

Some background on Knoppix:
Knoppix boots entirely from a cdrom and, in my case, does not use a hard
disk at all.  In fact, there is no hard disk in the Knoppix machine I'm
using now.

Knoppix creates a ram disk when it boots with soft links to the cdrom.
You can delete a soft line to a file and write your own.   In this case
I deleted the soft link to /etc/exports and wrote one for my exports.

Once everything is running satisfactorily you can save the entire /etc
and subdirectories to a thumb drive.

Knoppix boots with a user "knoppix" and its home is mounted as
/ramdisk/home/knoppix
with a symlink
/home -> /ramdisk/home

Tried several variations on below but keep getting an error message.
I suspect that /ramdisk is not considered a file system by exportfs.

This is a portion of /etc/exports:
/       knoppix(sync,rw,no_root_squash)
/ramdisk/home/knoppix   knoppix(sync,rw,no_root_squash)
#/home  knoppix(sync,rw,no_root_squash)

This is the result of exportfs:

root@Knoppix etc # exportfs -rav
exporting knoppix:/ramdisk/home/knoppix
exporting knoppix:/
exporting knoppix:/ramdisk/home/knoppix to kernel
knoppix:/ramdisk/home/knoppix: Invalid argument
reexporting knoppix:/ to kernel

In searching the Knoppix mailing list it appears that others are having
the same trouble trying to mount the Knoppix home directory for NFS.
Some have said that the owner of Knoppix is not interested in NFS, only
Samba.

If I cannot mount using NFS I'll have to go to Samba but am not sure yet
how to go about mounting a Linux share on Samba or whether Samba would
accept the ramdisk part.

Can you tell me why exportfs isn't working with the home ramdisk and
suggest any workarounds?

I have experience with NFS on several Linux machines and have portmap,
nfsd and rpc.mountd running.

I hope the knowledgable people on this list can help solve this puzzle.
Thank you.


-- 
Larry Alkoff N2LA - Austin TX
Using Thunderbird on Slackware Linux


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2005-06-13 23:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-13 23:19 Larry Alkoff [this message]
2005-06-13 23:28 ` Exportfs does not accept Knoppix /ramdisk/home Neil Brown
2005-06-14  5:07   ` Larry Alkoff
2005-06-14  5:29     ` Neil Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42AE148E.80904@mindspring.com \
    --to=labradley@mindspring.com \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.