On 31 January 2018 at 03:45, Manjukumar Harthikote Matha <manju...@xilinx.com> wrote: > Hi Nathan, > >> -----Original Message----- >> From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx- >> boun...@yoctoproject.org] On Behalf Of Nathan Rossi >> Sent: Tuesday, January 30, 2018 9:01 AM >> To: Bishop, Mark (STRT) <mbis...@smithsinterconnectinc.com> >> Cc: meta-xilinx@yoctoproject.org >> Subject: Re: [meta-xilinx] read-only-fs >> >> On 31 January 2018 at 02:31, Bishop, Mark (STRT) >> <mbis...@smithsinterconnectinc.com> wrote: >> > Changing the that file gets me a good build but I'm concerned with changing >> anything in a directory that is called 'generated' for when I move this to a >> build >> server. Looking for the 'right' way to fix it. >> >> You can forcibly override it in local.conf or any conf really, with >> something like: >> >> SERIAL_CONSOLES_CHECK_<machine-name> = "" >> >> or completely override: >> >> SERIAL_CONSOLES_CHECK_forcevariable = "" >> > > Is there a way in OE-Core to disable such tasks when read-only fs is enabled? > If not, that is something should be handled in some easy manner >
Its a bit tricky since read-only-rootfs is a image feature which means its not generally available knowledge at the time which sysvinit-inittab would be able to disable its postinst. Though you could have sysvinit-initab split its serial check into a separate package, and have it excluded somehow. But since its not a commonly needed feature it might be easier to transition to systemd for its features? Though another option would be to implement a feature in getty to lets its process wait for the device if they don't exist or something. Regards, Nathan -- _______________________________________________ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
