Topics

#yocto "zeus" #yocto


Monsees, Steven C (US)
 

 

This is probably a simple question, but since I am new to yocto there is a lot to learn…

 

How do I establish kernel access permissions for the “zeus” kernel so that when my application is up and running, (or an application startup script), can create read/write files for access/updating in the ”/etc” and “/dev” directories ?

 

In the few cases I do this I am seeing unable to open errors…

Note the same code appears to work correctly under “rocko”…

 

Thanks,

Steve


Khem Raj
 

On 11/12/20 4:03 AM, Monsees, Steven C (US) via lists.yoctoproject.org wrote:
This is probably a simple question, but since I am new to yocto there is a lot to learn…
How do I establish kernel access permissions for the “zeus” kernel so that when my application is up and running, (or an application startup script), can create read/write files for access/updating in the ”/etc” and “/dev” directories ?
In the few cases I do this I am seeing unable to open errors…
Note the same code appears to work correctly under “rocko”…
you have to provide more context to help you more, but usually /dev is populated with devtmpfs during kernel boot. and similarly /etc is mounted early on. So access permissions could be mounting issues perhaps.

Thanks,
Steve


Monsees, Steven C (US)
 

All things being equal, would you know why I might see

"NFS: bad mount option value specified: minorversion=1"

when running app under "zeus" but not under "rocko" ?

-----Original Message-----
From: Khem Raj [mailto:raj.khem@gmail.com]
Sent: Thursday, November 12, 2020 1:40 PM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>; yocto@lists.yoctoproject.org
Subject: Re: [yocto] #yocto "zeus"

*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.



On 11/12/20 4:03 AM, Monsees, Steven C (US) via lists.yoctoproject.org
wrote:
This is probably a simple question, but since I am new to yocto there
is a lot to learn...

How do I establish kernel access permissions for the "zeus" kernel so
that when my application is up and running, (or an application startup
script), can create read/write files for access/updating in the "/etc"
and "/dev" directories ?

In the few cases I do this I am seeing unable to open errors...

Note the same code appears to work correctly under "rocko"...
you have to provide more context to help you more, but usually /dev is populated with devtmpfs during kernel boot. and similarly /etc is mounted early on. So access permissions could be mounting issues perhaps.


Thanks,

Steve





Khem Raj
 

are you using nfsvers= in /etc/fstab

On Thu, Nov 12, 2020 at 10:44 AM Monsees, Steven C (US) via
lists.yoctoproject.org
<steven.monsees=baesystems.com@lists.yoctoproject.org> wrote:



All things being equal, would you know why I might see

"NFS: bad mount option value specified: minorversion=1"

when running app under "zeus" but not under "rocko" ?

-----Original Message-----
From: Khem Raj [mailto:raj.khem@gmail.com]
Sent: Thursday, November 12, 2020 1:40 PM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>; yocto@lists.yoctoproject.org
Subject: Re: [yocto] #yocto "zeus"

*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.



On 11/12/20 4:03 AM, Monsees, Steven C (US) via lists.yoctoproject.org
wrote:
This is probably a simple question, but since I am new to yocto there
is a lot to learn...

How do I establish kernel access permissions for the "zeus" kernel so
that when my application is up and running, (or an application startup
script), can create read/write files for access/updating in the "/etc"
and "/dev" directories ?

In the few cases I do this I am seeing unable to open errors...

Note the same code appears to work correctly under "rocko"...
you have to provide more context to help you more, but usually /dev is populated with devtmpfs during kernel boot. and similarly /etc is mounted early on. So access permissions could be mounting issues perhaps.


Thanks,

Steve