Dear Marco, Thank you for your clarification. I would like to follow up on one important point concerning the NFS infrastructure described in the Apache NuttX documentation.
I understand from your response that Apache NuttX does not operate or maintain NFS servers for contributors' development environments. However, the documented NFS functionality necessarily involves a client accessing a remote NFS server that provides the filesystem being mounted. I would therefore like to understand who is responsible for providing and maintaining the server-side infrastructure used by this documented arrangement. Specifically: 1. If Apache NuttX does not own, operate or maintain the NFS server used by its documented NFS mounting functionality, who provides that server infrastructure? Is it expected to be independently operated by the individual developer, an organization, or a third-party infrastructure provider? 2. Is there a particular organization, infrastructure administrator, service provider or technical contact associated with the NFS server-side implementation that you could direct me to? 3. Regarding the NFS client implementation within NuttX, could you provide the contact details of the developer or maintainer most familiar with its implementation and operation? I would appreciate an opportunity to clarify how the NuttX NFS client establishes connections, mounts remote filesystems and accesses remote storage. 4. Is there a mailing list, technical forum, repository discussion or another official contact channel where I can direct questions specifically concerning the NuttX NFS client and its corresponding server-side requirements? 5. If the NFS server is entirely independent of the NuttX project, could you explain how a developer is expected to identify the appropriate server provider or administrator when following the NuttX NFS documentation? For context, my development environment had a 128GB local SSD, and I had configured an NFS mount in WSL/Ubuntu before beginning the relevant PX4 and QGroundControl development work. My understanding was that the mounted remote filesystem allowed me to work with project files and build data without requiring all of that data to occupy the limited local SSD capacity. The original SSD containing my WSL environment, mount commands and configuration is now corrupted and requires forensic recovery. I am trying to identify the original NFS server and understand the infrastructure with which my development environment was communicating. I am not asking Apache NuttX to recover my personal files or accept responsibility for an independently operated server. I am asking for technical direction to the appropriate people who can explain the NFS architecture documented by the project and, if applicable, help identify the server-side infrastructure relevant to this arrangement. I would be grateful if you could provide an actual technical contact, maintainer or appropriate organization rather than simply redirecting me to general Linux system administration resources. Thank you for your time. Regards, Siddhartha On Mon, 2 Nov 2026, 02:24 Siddhartha Sharma, <[email protected]> wrote: > Dear NuttX Maintainers, > > I am writing to request technical assistance with verifying and recovering > a substantial body of historical development work associated with my > NuttX/PX4 and QGroundControl development environment from approximately May > to August 2023. > > I believe there has been a misunderstanding regarding the NFS > infrastructure documented in the NuttX project and its relevance to my > historical development environment. I would like to clarify the technical > circumstances and request that this matter be referred to someone capable > of investigating the relevant infrastructure and storage records. > > *1. My historical development environment* > > During this period, I worked through WSL/Ubuntu and used a directory named > nuttxspace, created under my WSL home directory: > > /home/<username>/nuttxspace > > My recollection is that I mounted the NFS filesystem directly at this > directory and used it as my ordinary development workspace. My project > operations, including working with source files and Git repositories, were > conducted within this directory. > > Consequently, the files and repository metadata may have resided on the > remote NFS export rather than on my laptop's local SSD. > > I no longer have the original SSD or motherboard from that development > machine. This makes recovery through the original storage infrastructure > particularly important. > > *2. The NuttX documentation establishes the technical basis for > investigation* > > I have examined the historical NuttX NFS documentation introduced through > commit: > > 044028b6066e1bda8180496563df991290ec37a8 > > The documentation describes: > > - > > NuttX's NFS client functionality. > - > > The nfsmount interface and its server-address, mount-point and > remote-path parameters. > - > > The distinction between the NFS client and the Linux NFS server. > - > > Server-side export configuration through /etc/exports. > - > > The network communication required between the client and the server. > > I am not presenting the example IP addresses in that documentation as my > actual historical server addresses. I am identifying the documented > architecture as the technical basis for investigating whether the relevant > infrastructure and associated storage can be identified. > > I would appreciate it if the maintainers could distinguish between the > existence of the documented NFS functionality and the separate question of > whether a particular historical NFS server or export can be identified. > > *3. Why the absence of additional GitHub commits is not conclusive* > > My publicly identifiable commit is: > > 3df3d34e8294d75545241d0be6c4c06f8b488cba > > It is dated 30 May 2023 and is associated with my GitHub identity. > > However, I did not intend to publish every intermediate development change > as an individual GitHub commit. My plan was to complete the work, > consolidate the changes and commit the resulting project together. > > Therefore, the absence of further published commits during May–August 2023 > should not be treated as proof that no additional development work existed. > > If the working repositories were located within the NFS-mounted nuttxspace > directory, the original Git object databases, working files and uncommitted > changes may have been stored on the remote filesystem. > > This is precisely why I am requesting an investigation of the underlying > storage rather than relying exclusively on the public GitHub commit history. > > *4. Concern regarding loss of the original project material* > > I am attempting to recover development work that I can no longer access > through my original machine. > > I have concerns that project material may have been accessed or copied > during the period in question, following assurances that the work would be > reviewed. I do not want to present that concern as an established technical > finding without first examining the available evidence. > > I am therefore requesting preservation and examination of any relevant > records before they are lost through routine log rotation, storage deletion > or backup expiration. > > *5. Specific assistance requested* > > I request that the NuttX project, or the appropriate infrastructure > administrator to whom this request can be referred: > > 1. > > Identify whether any historical NFS server, test environment, > development server or shared export associated with the relevant NuttX/PX4 > development environment can be identified. > 2. > > Determine whether there are historical records identifying the NFS > server address, exported directory, client connections or mount activity > relevant to the May–August 2023 period. > 3. > > Check whether any associated storage volumes, backups, snapshots, > archived exports or repository copies remain available. > 4. > > Preserve relevant records and storage artifacts, where they still > exist, before any further deletion or rotation. > 5. > > Establish whether Git repositories or source directories associated > with my historical nuttxspace workspace can be recovered, including > unpushed commits, Git objects, branches, reflogs and uncommitted working > files where available. > 6. > > If the NFS infrastructure was operated by another organization or > individual, identify the appropriate administrator or responsible party to > whom a formal preservation and recovery request should be directed. > > I am not asking the maintainers to reconstruct my development work from > generic NuttX source code or to infer an actual server address from an > example in the documentation. I am asking for assistance identifying and > investigating the actual historical infrastructure that may have supported > the development environment. > > *6. Requested response* > > Please confirm: > > - > > Whether this request can be investigated by someone familiar with > NuttX NFS infrastructure. > - > > Whether any relevant historical server or storage records can be > identified. > - > > Whether the project can assist with preservation or recovery, or > direct me to the appropriate infrastructure administrator. > - > > What additional technical identifiers or evidence would be required > from me to proceed. > > I am willing to provide the relevant commit hashes, repository details, > historical documentation extracts and any available correspondence that > could help narrow the investigation. > > I would appreciate a substantive technical response addressing the > recovery request rather than a response limited to confirming that NFS > functionality is or is not documented in NuttX. > > My objective is to establish the original storage environment, preserve > any surviving project material and recover the development work wherever > technically possible. > > Regards, > > Siddhartha Dutta Sharma >
