Update README and some C comments
This commit is contained in:
parent
a8708424c2
commit
d9bd5ca05f
21
README.txt
21
README.txt
@ -197,8 +197,25 @@ Ubuntu Bash under Windows 10
|
|||||||
|
|
||||||
C:\Users\Username\AppData\Local\lxss\rootfs
|
C:\Users\Username\AppData\Local\lxss\rootfs
|
||||||
|
|
||||||
However, I am unable to see my files under the rootfs/home directory
|
However, I am unable to see my files under the rootfs\home directory.
|
||||||
so this is not very useful.
|
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.
|
Install Linux Software.
|
||||||
-----------------------
|
-----------------------
|
||||||
|
2
TODO
2
TODO
@ -196,7 +196,7 @@ o Task/Scheduler (sched/)
|
|||||||
OS can cause non-cancellation point interfaces to behave
|
OS can cause non-cancellation point interfaces to behave
|
||||||
strangely. There was a change recently in pthread_cond_wait()
|
strangely. There was a change recently in pthread_cond_wait()
|
||||||
and pthread_cond_timedwait() recently to effectively disable
|
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()
|
accomplished with two functions: pthread_disable_cancel()
|
||||||
and pthread_enable_cancel()
|
and pthread_enable_cancel()
|
||||||
|
|
||||||
|
@ -171,7 +171,9 @@ int shmctl(int shmid, int cmd, struct shmid_ds *buf)
|
|||||||
|
|
||||||
if (region->sr_ds.shm_nattch > 0)
|
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;
|
region->sr_flags |= SRFLAG_UNLINKED;
|
||||||
|
Loading…
Reference in New Issue
Block a user