Dell - Internal Use - Confidential
> On Wed, 19 Sep 2018 12:33:37 +0100
> "Burton, Ross" wrote:
>
> > Is anyone actually writing a patch?
>
> I have a tentative fix for this checked into master, I don't know
> whether it actually works because I don't have any inodes over 2^63.
>
> It doesn't
Dell - Internal Use - Confidential
> On Wed, 19 Sep 2018 12:33:37 +0100
> "Burton, Ross" wrote:
>
> > On Tue, 18 Sep 2018 at 22:21, Seebs wrote:
> > > > Are the databases supposed to be shareable between different build
> > > > machines? IIRC, the answer is no. Could you store the native
> > On Wed, 2018-08-22 at 14:54 +, jack.f...@dell.com wrote:
> > > So failure mode is the target filesystem is devoid of SELinux file
> > > contexts, all files are unlabeled_t, which pretty much breaks
> > > everything in enforcing mode. So whatever the corruption
> > > cause/effect in the
> On Wed, 2018-08-22 at 14:54 +, jack.f...@dell.com wrote:
> > So failure mode is the target filesystem is devoid of SELinux file
> > contexts, all files are unlabeled_t, which pretty much breaks
> > everything in enforcing mode. So whatever the corruption cause/effect
> > in the Psuedo
Dell - Internal Use - Confidential
> Dell - Internal Use - Confidential
>
> > 2018-08-20 20:45 GMT+02:00 :
> > > We are encountering a build problem after migrating to Poky 2.3
> > > and Pseudo 1.8.1, and need help to resolve this.
> > > It is hampering our development efforts, forcing us to
Dell - Internal Use - Confidential
> 2018-08-20 20:45 GMT+02:00 :
>> We are encountering a build problem after migrating to Poky 2.3 and Pseudo
>> 1.8.1, and need help to resolve this.
>> It is hampering our development efforts, forcing us to rebuild images
>> frequently.
>>
>> Background:
We are encountering a build problem after migrating to Poky 2.3 and Pseudo
1.8.1, and need help to resolve this.
It is hampering our development efforts, forcing us to rebuild images
frequently.
Background:
Our build applies SELinux file contexts, during build time since our rootfs is
