Hi Marco, Please answer my questions to clarify my query so I can stop emailing Nuttx.
Regards, Siddhartha Sharma On Mon, 2 Nov 2026, 18:47 Siddhartha Sharma, <[email protected]> wrote: > Dear Marco, > > Thank you for your response. I acknowledge that Apache NuttX does not > operate or maintain NFS servers for contributors, and I understand the > distinction you have explained between NuttX's embedded NFS client and the > NFS functionality available through WSL/Ubuntu. > > I would nevertheless like to clarify one technical point so that my > original development environment is not misunderstood. > > My understanding and recollection is that I had successfully configured > and mounted an NFS share within my WSL/Ubuntu environment before beginning > the relevant PX4 and QGroundControl development work. The mount was used as > an accessible remote filesystem within my Linux workspace, allowing me to > work with project files and build data despite the limited capacity of my > local 128GB SSD. > > I was not suggesting that Apache NuttX operated the remote NFS server or > provided storage infrastructure to my computer. I was referring to the > NFS-based development arrangement I had configured while working with the > NuttX/PX4 ecosystem. > > The difficulty is that the original SSD containing my WSL environment, > mount commands, configuration files and potentially the associated project > data is now corrupted. Recovering that SSD is necessary to retrieve the > original configuration and establish the precise server, export path, mount > options and directory structure. > > I appreciate that these are not matters Apache NuttX can investigate or > resolve. I will therefore pursue the recovery through the appropriate data > recovery process and, if the original configuration identifies an external > server, approach its administrator separately. > > For the record, my intention in contacting the maintainers was to clarify > the technical environment in which I carried out the development, not to > suggest that the Apache NuttX project maintained or possessed my personal > development files. I can assure you that I did not have any company server > connected with my machine so what is this exact mechanism that allows users > to virtually work beyond their local machine's memory capacity? Since those > memory objects are not directly stored in my local machine, I would like to > know exactly where they were stored and who possesses their respective > access or control? > > Thank you for clarifying the project's position. > > Regards, > Siddhartha > > On Mon, 2 Nov 2026, 17:49 Marco C., <[email protected]> wrote: > >> Dear Siddhartha, >> >> Thank you for your clarification. >> >> We understand that you are attempting to recover files and >> configuration information from your former development machine and >> that you believe your workspace was hosted on an external NFS server. >> >> However, as previously explained, Apache NuttX does not operate or >> maintain NFS servers for contributors' development environments. The >> NFS functionality implemented in NuttX is entirely unrelated to the >> NFS mounting facilities provided by WSL/Ubuntu. >> >> NuttX is also not responsible for configuring or managing your WSL >> environment, the storage devices attached to your computer, or any >> external NFS servers you may have used. >> >> Your questions concerning `/etc/fstab`, shell history, WSL >> configuration, filesystem recovery, and historical NFS server access >> are general Linux system administration and data recovery matters, not >> NuttX-specific issues. >> >> Furthermore, we cannot verify the existence of unsubmitted development >> work or investigate allegations concerning the handling of files by >> your former employer. These matters are outside the scope and >> responsibility of the Apache NuttX project. >> >> If the original SSD contains information relevant to your >> investigation, you will need to work with a qualified data recovery >> specialist or the administrator of the infrastructure you used. >> >> Unfortunately, **there is nothing further the NuttX maintainers can do >> to assist with this matter.** >> >> We kindly ask that you direct any further questions regarding your >> personal storage recovery or former employer to the appropriate >> parties, rather than the NuttX development mailing list. >> >> Regards, >> Marco >> >> On Mon, Nov 2, 2026 at 1:10 PM Siddhartha Sharma <[email protected]> >> wrote: >> > >> > Dear Marco and Alan, >> > >> > Thank you for clarifying the distinction between the NuttX NFS client >> implementation and the NFS functionality available within my WSL/Ubuntu >> development environment. >> > >> > I understand now that Apache NuttX does not operate an NFS storage >> service for contributors, and I am not suggesting that the NuttX project >> hosted or maintained my personal development workspace. >> > >> > However, I believe there is an important part of my original >> explanation that has been misunderstood, and I would like to clarify it. >> > >> > 1. The original NFS configuration is on my old SSD >> > >> > I am referring to my own development machine and its original 128GB SSD. >> > >> > The WSL/Ubuntu environment, including the NFS mount commands, >> configuration files, scripts and other environment-specific information, >> was maintained on that machine. >> > >> > The SSD subsequently became corrupted, and the motherboard was also >> replaced. I currently cannot access the original development environment or >> inspect its filesystem. >> > >> > My recollection is that the NFS mount configuration and related setup >> information remain on that original SSD. However, accessing those records >> requires recovering the SSD sufficiently to retrieve its filesystem >> contents. >> > >> > I am not asking the NuttX project to retrieve data from a server it >> does not own. I am explaining why I cannot currently provide the original >> "/etc/fstab", mount configuration, shell history or other records you have >> requested. >> > >> > 2. Why I used NFS in the first place >> > >> > My development machine had only a 128GB SSD. >> > >> > I was working with large development projects, including PX4 Autopilot >> and QGroundControl. Their source trees, dependencies, build directories and >> associated development requirements consume substantial storage. >> > >> > The available local storage was consistently insufficient for the >> complete development workflow. I remember repeatedly encountering >> storage-capacity limitations, with the local disk showing as full during >> development. >> > >> > I can assure you with 100% clarity that the commit I have mentioned in >> the previous email was a result of configuring the NFS mount commands and >> nuttx configuration only, otherwise that would not be possible from my >> limited storage SSD. That's the sole reason why I used Nuttx for building >> these projects since their own configuration is quite large and in the >> middle of that, I ran into disk storage issues which Nuttx resolved. >> > >> > To work around this constraint, I used remote NFS-mounted storage, with >> the mount point directly inside my WSL home directory: >> > >> > "/home/<username>/nuttxspace" >> > >> > I used this directory as my ordinary development workspace. >> > >> > This was not a request for Apache NuttX to provide storage. It was my >> own development arrangement, using Linux/WSL filesystem mounting >> functionality. I acknowledge the distinction you have explained between the >> NuttX embedded NFS client and the Linux NFS client used by my WSL >> environment. >> > >> > 3. Why the GitHub repository does not contain the complete work >> > >> > I also want to clarify my development and submission approach. >> > >> > I was not committing every intermediate change to GitHub as I worked. >> My intention was to complete the development, consolidate the changes and >> commit the project together once the work had reached a sufficiently >> complete state. >> > >> > During that period, my project files were stolen from me by my company >> saying that they will review them after cut pasting it from my machine to >> their external hard drive. This is a serious issue and needs to be >> addressed accordingly since I was under the impression that they can be >> trusted and will be reviewing the files but later they said I didn't take >> any files. That's a literal felony and the only sustainable way to prove it >> is by contacting Nuttx maintainers. >> > >> > Consequently, the single publicly identifiable commit from May 2023 >> does not represent the complete development activity I remember undertaking >> between May and August 2023. >> > >> > If the project repositories and their Git working directories were >> located inside "nuttxspace", the original filesystem could potentially >> contain: >> > >> > - Unpushed Git commits and Git objects. >> > - Local branches and repository references. >> > - Uncommitted source-code changes. >> > - Build configurations and project-specific modifications. >> > - Supporting scripts, dependencies and development documentation. >> > >> > I am not claiming that these materials have already been recovered or >> independently verified. They are the specific materials I am attempting to >> retrieve from the original storage. >> > >> > 4. What I am actually requesting >> > >> > I understand that the NuttX maintainers cannot access my old SSD, >> recover my personal WSL environment or investigate an NFS server operated >> by someone else. >> > >> > I am therefore not asking you to initiate recovery of Apache NuttX >> infrastructure. >> > >> > What I would appreciate is technical guidance on the following: >> > >> > 1. Which specific WSL/Ubuntu configuration files, scripts and >> filesystem records should I prioritize recovering from the original SSD to >> establish the historical NFS mount? >> > 2. Would recovering "/etc/fstab", mount scripts, shell history, WSL >> configuration and related filesystem metadata be sufficient to establish >> the mount point and potentially identify the remote server and export? >> > 3. Are there any NuttX/PX4 development-environment configuration files >> or installation records that could help distinguish the NFS configuration I >> used from the standard local "nuttxspace" directory? >> > 4. If the recovered configuration identifies an external NFS server, >> what technical records should I request from its administrator to establish >> historical access and investigate whether any project data survives? >> > >> > I am prepared to pursue professional SSD recovery to retrieve the >> original configuration and project data. I simply want to make sure that >> the recovery process targets the correct evidence and that I do not >> overlook important configuration or repository artifacts. >> > >> > 5. Final clarification >> > >> > I appreciate that the NuttX project does not have custody of my >> personal development environment and cannot recover material that was never >> submitted to its repositories. >> > >> > Nevertheless, I hope you can understand why I am pursuing the original >> SSD rather than simply recreating the work. >> > >> > My objective is to recover the actual historical implementation, its >> development history and the original configuration, not produce a new >> implementation that merely resembles it. >> > >> > Thank you for clarifying the infrastructure distinction. I would >> appreciate any specific technical guidance you can provide concerning the >> recovery and verification of the original WSL/NFS development environment. >> > >> > Regards, >> > >> > Siddhartha Dutta Sharma >> > >> > On Mon, 2 Nov 2026, 17:02 Marco C., <[email protected]> wrote: >> >> >> >> Dear Siddhartha, >> >> >> >> Thank you for your message. >> >> >> >> There appears to be a fundamental misunderstanding regarding the NFS >> >> functionality documented in Apache NuttX and the infrastructure used >> >> by the project. >> >> >> >> Apache NuttX is an embedded real-time operating system that implements >> >> an NFS client. The documentation you referenced describes how a device >> >> running NuttX can access a remote NFS server. It does not describe an >> >> NFS service operated by the Apache NuttX project for storing >> >> contributors' development files. >> >> >> >> The NuttX project does not provide or maintain NFS servers for >> >> contributors' personal development environments, nor does it store >> >> their local workspaces, uncommitted changes, Git objects, or >> >> repository metadata. >> >> >> >> Furthermore, the `nuttxspace` directory mentioned in your message is >> >> simply the directory name used in the official NuttX installation >> >> instructions. It is intended to be created on the developer's own >> >> computer. Its existence does not imply an NFS mount or any connection >> >> to Apache infrastructure. >> >> >> >> Your development environment was running WSL/Ubuntu, which is >> >> independent of NuttX. If you mounted an NFS filesystem within that >> >> environment, the mount would have been configured through your Linux >> >> installation and connected to a server determined by your own >> >> configuration. The NuttX project would have no knowledge of, access >> >> to, or control over such a server. >> >> >> >> Regarding your development work, the project only has access to >> >> material that was actually submitted to its public repositories or >> >> other project communication channels. Development work that remained >> >> exclusively in your local workspace, including uncommitted or unpushed >> >> changes, would not have been transferred to the project automatically. >> >> >> >> Consequently: >> >> >> >> - We cannot identify an NFS server based on the NuttX documentation or >> >> the directory name `nuttxspace`. >> >> - We have no NFS storage infrastructure associated with your personal >> >> development environment to investigate. >> >> - We do not possess backups, snapshots, mount logs, or Git objects >> >> from your WSL workspace. >> >> - We cannot preserve or recover files that were never stored on >> >> infrastructure controlled by the project. >> >> >> >> We also have no evidence establishing that your development files were >> >> accessed, copied, or leaked through NuttX project infrastructure. >> >> >> >> If your workspace was indeed mounted over NFS, identifying the server >> >> would require information from your original Linux configuration, such >> >> as `/etc/fstab`, mount commands, shell history, or records from the >> >> organization that operated the server. >> >> >> >> Unfortunately, **there is nothing further the Apache NuttX maintainers >> >> can do to investigate or recover this material.** The project does not >> >> operate the infrastructure described in your request and cannot >> >> provide access to storage or records it does not control. >> >> >> >> We consider this matter outside the scope of the Apache NuttX project >> >> and have no further assistance to offer regarding this recovery >> >> request. >> >> >> >> Regards, >> >> Marco >> >> >> >> On Mon, Nov 2, 2026 at 12:17 PM Alan C. Assis <[email protected]> >> wrote: >> >> > >> >> > Hi Siddhartha, >> >> > >> >> > I admire you! I really do! >> >> > >> >> > You are like the little boy David from the Steven Spielberg movie AI >> (I'm >> >> > also like him, this is why I'm here pursuing my dream of making >> NuttX more >> >> > popular). >> >> > >> >> > For years, you've tried to recover your files, sending this kind of >> message >> >> > to the NuttX mailing list, LinkedIn and all other possible platforms! >> >> > >> >> > I have an autistic friend who almost every day sends me questions >> that, for >> >> > most people, seem illogical or nonsensical. I patiently research the >> >> > subject to reply to him, and I learnt a lot by doing it (and it >> helps me >> >> > become a little more patient too). >> >> > >> >> > Siddhartha, first of all: you are confusing the NuttX NFS client >> support >> >> > with the NFS that you used on your Linux/WSL. They are unrelated. >> Even if >> >> > they were related, saving a file on your NFS server used/mounted by >> your >> >> > NuttX board doesn't transfer the file to our GitHub. So, we don't >> have >> >> > access to your files. (I hope you finally understand this). >> >> > >> >> > It seems like you are using AI to write your email. That is a good >> news, so >> >> > let me give you an idea that will help you and all of us here: use >> AI to >> >> > reimplement what you did in 2023. >> >> > >> >> > Using Claude Code (or OpenAI Codex, etc.), you can reimplement it in >> no >> >> > time. If you spent 3 or 4 months implementing it, using Claude Code >> you >> >> > will be able to do it in a single day! That is no joke, it is true! >> >> > >> >> > BR, >> >> > >> >> > Alan >> >> > >> >> > On Mon, Nov 2, 2026 at 5:46 AM 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 >> >> > > >> >
