Re: [OE-core] [PATCH 6/6] systemd: remove unnecessary code

2016-02-09 Thread Maciek Borzecki
On wto, 2016-02-09 at 07:19 -0800, Khem Raj wrote: > On Mon, Feb 8, 2016 at 2:09 AM, Maciej Borzecki > wrote: > > Remove unnecessary chown on journal file. > > > > Signed-off-by: Maciej Borzecki > > --- > >  meta/recipes-core/systemd/systemd_228.bb | 2 +- > >  1 file changed, 1 insertion(+), 1 d

Re: [OE-core] [PATCH 3/6] systemd: extend PACKAGECONFIG flags

2016-02-08 Thread Maciek Borzecki
On pon, 2016-02-08 at 12:07 +0100, Andreas Müller wrote: > On Mon, Feb 8, 2016 at 11:44 AM, Maciek Borzecki > wrote: > > On pon, 2016-02-08 at 11:21 +0100, Andreas Müller wrote: > > > On Mon, Feb 8, 2016 at 11:09 AM, Maciej Borzecki > > > wrote: > > >

Re: [OE-core] [PATCH 3/6] systemd: extend PACKAGECONFIG flags

2016-02-08 Thread Maciek Borzecki
On pon, 2016-02-08 at 11:21 +0100, Andreas Müller wrote: > On Mon, Feb 8, 2016 at 11:09 AM, Maciej Borzecki > wrote: > > We currently ship a rather full-blown setup of system. Very few > > configuration knobs are actually exposed through PACKAGECONFIG > > flags. This patch adds new PACKAGECONFIG f

Re: [OE-core] [PATCH 1/6] systemd: move bash completion into separate package

2016-02-08 Thread Maciek Borzecki
On pon, 2016-02-08 at 12:20 +0200, Tanu Kaskinen wrote: > On Mon, 2016-02-08 at 11:09 +0100, Maciej Borzecki wrote: > > Add systemd-bash package that ships bash completion files > > > > Signed-off-by: Maciej Borzecki > > --- > >  meta/recipes-core/systemd/systemd_228.bb | 9 ++--- > >  1 file

Re: [OE-core] issues encountered using wic

2014-10-31 Thread Maciek Borzecki
On pią, 2014-10-31 at 11:47 -0500, Tom Zanussi wrote: > Hi, > > On Fri, 2014-10-31 at 10:36 -0500, Peter A. Bigot wrote: > > I've started to transition to wic (in master) in hopes it reduces the > > amount of host passwd contamination resulting from creating SD images by > > untarring the rootfs on

Re: [OE-core] [OE-code][PATCH] wic: include partition label in fs image file name

2014-08-11 Thread Maciek Borzecki
Right, the empty-partition case somehow missed the label - good catch. > > Acked-by: Tom Zanussi Saul, I think that the patch was missed by due to malformed subject line. Would you be able to push it to master? > > > Signed-off-by: Maciej Borzecki > > Signed-off-b

Re: [OE-core] [OE-code][PATCH] wic: include partition label in fs image file name

2014-07-27 Thread Maciek Borzecki
21 lip 2014 23:23 Tom Zanussi napisał(a): > > On Mon, 2014-07-21 at 13:01 +0200, Maciej Borzecki wrote: > > Not including the label image but having multiple partitions of the same > > type, the image file of one partition would overwrite the other. > > > > Right, the empty-partition case som

Re: [OE-core] [PATCH v2] wic: do not overwrite autogenerated /etc/fstab with original too early

2014-07-25 Thread Maciek Borzecki
25 lip 2014 18:30 Richard Purdie napisał(a): > > On Fri, 2014-07-25 at 10:57 -0500, Tom Zanussi wrote: > > On Fri, 2014-07-25 at 17:48 +0200, Maciek Borzecki wrote: > > > One question though. How do I get the patches into master? I'm not > > > @intel

Re: [OE-core] [PATCH v2] wic: do not overwrite autogenerated /etc/fstab with original too early

2014-07-25 Thread Maciek Borzecki
25 lip 2014 17:00 Tom Zanussi napisał(a): > > On Thu, 2014-07-24 at 19:49 -0500, Tom Zanussi wrote: > > On Thu, 2014-07-24 at 14:27 +0200, Maciej Borzecki wrote: > > > DirectImageCreator.__write_fstab() generates new /etc/fstab in sysroot > > > with rootfs contents. The fstab entries are gener

Re: [OE-core] [PATCH] wic: squashfs partition support

2014-07-23 Thread Maciek Borzecki
On śro, 2014-07-23 at 15:21 -0500, Tom Zanussi wrote: > Hi, please include a description for this. Ok, will update with the rest of the patches. > > Also, it looks like this is missing the empty_partition() part? That's intentional. Squashfs, being read-only, is not really useful for a partition

Re: [OE-core] [PATCH 1/2] wic: original fstab restored too early

2014-07-23 Thread Maciek Borzecki
On śro, 2014-07-23 at 14:21 -0500, Tom Zanussi wrote: > Sorry, I'm not seeing how this fixes the problem (best would be to > explain that in the patch description too), or for that matter, how to > reproduce the problem. Could you elaborate? Right, the wording might be unfortunate and not reflect