diff --git a/README.txt b/README.txt index b6144aca710..9a4775c77b7 100644 --- a/README.txt +++ b/README.txt @@ -197,8 +197,25 @@ Ubuntu Bash under Windows 10 C:\Users\Username\AppData\Local\lxss\rootfs - However, I am unable to see my files under the rootfs/home directory - so this is not very useful. + However, I am unable to see my files under the rootfs\home directory. + After some looking around, I find the home directory + %localappdata%\lxss\home. + + With that trick access to the /home directory, you should actually be + able to use Windows tools outside of the Ubuntu sandbox with versions of + NuttX built within the sandbox using that path. + + You can also execute Windows tools from within the Ubuntu sandbox: + + $ /mnt/c/Program\ Files\ \(x86\)/Microchip/xc32/v1.43/bin/xc32-gcc.exe --version + Unable to translate current working directory. Using C:\WINDOWS\System32 + xc32-gcc.exe (Microchip Technology) 4.8.3 MPLAB XC32 Compiler v1.43 Build date: Mar 1 2017 + ... + + The error message indicates that there are more issues: You cannot mix + Windows tools that use Windows style paths in an environment that uses + POSIX paths. I think you would have to use Linux tools only from within + the Ubuntu sandbox. Install Linux Software. ----------------------- diff --git a/TODO b/TODO index fe969060bf2..2cf4fdcaaae 100644 --- a/TODO +++ b/TODO @@ -196,7 +196,7 @@ o Task/Scheduler (sched/) OS can cause non-cancellation point interfaces to behave strangely. There was a change recently in pthread_cond_wait() and pthread_cond_timedwait() recently to effectively disable - the cancellation point behavior of sem_init(). This was + the cancellation point behavior of sem_wait(). This was accomplished with two functions: pthread_disable_cancel() and pthread_enable_cancel() diff --git a/mm/shm/shmctl.c b/mm/shm/shmctl.c index 0c468b36af7..2421dea09e5 100644 --- a/mm/shm/shmctl.c +++ b/mm/shm/shmctl.c @@ -171,7 +171,9 @@ int shmctl(int shmid, int cmd, struct shmid_ds *buf) if (region->sr_ds.shm_nattch > 0) { - /* Yes.. just set the UNLINKED flag. The region will be removed when there are no longer any processes attached to it. + /* Yes.. just set the UNLINKED flag. The region will be + * removed when there are no longer any processes attached to + * it. */ region->sr_flags |= SRFLAG_UNLINKED;