nfs questions?

[Jason W]

compiletc.tce as well as filesystems-2.6.26 are not PPI compatible and need to be loaded each boot.

[cannonfodder]

I tend to gravitate towards small foot print / minimalist distros (Arch, Slitaz are favorites), hence my interest in Tiny Core.

I like that I can build TC with only the extensions that I want, as opposed to DSL or Puppy, which come with software I do not need or use.

I also like that TC runs on my Compaq laptop (Pentium MMX @ 133MHz with 48MB of RAM). My goal is to use this machine as an always on webserver on a small LAN. I'd like to be able to access the HTML files hosted on it from another PC on the LAN via NFS.

That said, I understand that running on older hardware is NOT one of TC's primary goals.

All of which brings me to the following questions:

1. What is the technical nature of PPI incompatibilities with extensions like "compiletc.tce" and "filesystems-2.6.26" ? Very little information seems to be available on this topic (on the Core Concepts page, for example).

2. Does there exist a work-around, short of using a different mode of operation?

In closing, I'd like to say that I am a just an average Linux enthusiast - i.e., not a developer with a degree in Computer Sciences - but I am willing to learn and I commend the Tiny Core developers on an EXCELLENT distro.

[Jason W]

cannonfodder-
I share your interest in older hardware as that is mostly what I use. 
Many who wish to use TC as an nfs server will be using old hardware, so
I will make an nfsd module extension that is PPI compatible so that only
the nfsd kernel module will be installed for those using the nfs-utils package.
It will be in TCZ and TCE format, supporting all modes.

[Juanito]

1. What is the technical nature of PPI incompatibilities with extensions like "compiletc.tce" and "filesystems-2.6.26" ? Very little information seems to be available on this topic (on the Core Concepts page, for example).

Basically to be PPI compatible, all the files in an extension need to be in /usr/local as it is this directory that is made permanent - files outside /usr/local will be lost on boot. The files in compiletc are in /usr, /lib, etc and thus are lost on reboot in a PPI system

[curaga]

Note that in TC 2.x the module extensions are PPI compatible. There one would only need to load the nfs extension on boot.

[Jason W]

In that case, would it be ok to make the filesystems-2.6.26
extension PPI compatible as an nfs server machine will always have
hard drive space for tclocal/PPI.  No need then for an nfsd extension.

[curaga]

Sure

[cannonfodder]

Thank you Jason W, Juanito and curaga for your prompt and complete replies.

I don't usually post in forums - either my posts have gone unanswered or unresolved. The support here so far has been outstanding.

[Jason W]

filesystems-2.6.26 in TC 1.x is now PPI compatible.  For minimal ram usage without PPI the tcz format is recommended.