Hi Alan,

I've created the GitHub issue for the NanoX project:
https://github.com/apache/nuttx/issues/18496

I tried to add the gsoc2026 label but it seems I don't have permissions to
add labels in the repository. Could you or someone from the team add the
gsoc2026 label when you get a chance?

Thanks,
Siddhi

On Thu, Mar 5, 2026 at 3:40 PM Siddhi Tripathi <[email protected]>
wrote:

> Hi Alan,
> Thanks for the helpful reply! I looked into both projects and here's what I'm 
> thinking:
>
> **Multi-user project** - I saw someone already created a GitHub issue for 
> this with the gsoc2026 label. I'm still interested, but I understand there 
> might be competition now.Should I show interest in the existing issue??
>
> **NanoX project** - Since you mentioned this doesn't have candidates yet, I'm 
> really excited about this too! Graphics and GUI stuff sounds fun, and running 
> a web browser on NuttX would be pretty cool to see.
>
> I'm planning to submit proposals for both projects during the application 
> window.
>
> Quick question about NanoX - does this project require any specific hardware 
> for testing? Like a board with a display? I have the simulator running on my 
> Mac, but not sure if that's enough for graphics work. If hardware is needed, 
> what would you recommend?
>
> Thanks,
> Siddhi
>
>
> On Thu, Mar 5, 2026 at 2:04 AM Alan C. Assis <[email protected]> wrote:
>
>> Hi Siddhi,
>>
>> Nice to know you are interested in participating in the GSoC 2026.
>>
>> There is also another user interested in adding support to multi-user on
>> NuttX.
>> I suggest all candidates interested to work on some project to open an
>> issue in the Github to list it and make it easy to track:
>>
>> https://github.com/apache/nuttx/issues?q=state%3Aopen%20label%3A%22gsoc2026%22
>>
>> The steps you listed here are mostly right, please note that NuttX already
>> have login authentication in place, you can test it enabling in sim:nsh
>> these options:
>>
>> CONFIG_NSH_LOGIN=y
>> CONFIG_NSH_CONSOLE_LOGIN=y
>> CONFIG_NSH_LOGIN_FIXED=y
>>
>> Also keep in mind that we have 10 projects participating in the GSoC, so
>> projects like porting NanoX to NuttX don't have candidates yet.
>>
>> BR,
>>
>> Alan
>>
>> On Wed, Mar 4, 2026 at 4:31 PM Siddhi Tripathi <
>> [email protected]>
>> wrote:
>>
>> > Hello Everyone,
>> > I am interested in working on the multi-user support project for GSoC
>> > 2026.I've
>> > been poking around the codebase for a while now and managed to get the
>> > simulator running on my Mac (took some effort, but it works!).
>> >
>> > ## What I've Found So Far
>> > Looking through the code, I noticed there's already some groundwork
>> done:
>> > - Commit 903e87a added UID/GID support to BINFS
>> > - Commit 896f34f added effective UID/GID interfaces
>> >
>> > But from what I can tell, multi-user support isn't fully there yet:
>> > - Most filesystems (FAT, ROMFS, TMPFS, PROCFS) don't have UID/GID
>> support
>> > - No file permission checks yet
>> > - No way to add users or manage passwords
>> > - Commands like `ls -l` don't show owners
>> >
>> > ## What I'm Thinking of Working On
>> > I'd like to take this further and make multi-user support a reality. My
>> > rough plan:
>> > 1. **Start small** - get UID/GID working in TMPFS first (seems simpler
>> than
>> > others)
>> > 2. **Then move to other filesystems** - FAT, ROMFS, PROCFS one by one
>> > 3. **Add the missing system calls** - chown, chmod, etc.
>> > 4. **Build user tools** - useradd, passwd, id, and make ls show owners
>> > 5. **Finally add authentication** - /etc/passwd and login
>> > I'm planning to do all development and testing in the simulator since I
>> > don't have various hardware boards.
>> >
>> > ## A Few Questions
>> > - Does this sound like the right approach?
>> > - Any filesystem I should prioritize over others?
>> > - Is there any other work I missed that I should know about?
>> > - Does this fit within a 350-hour GSoC project?
>> >
>> > I already have the simulator running and I'm comfortable with the
>> codebase.
>> > Would love to hear your thoughts before I dive deeper.
>> >
>> > Thanks,
>> > Siddhi
>> >
>>
>

Reply via email to