public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: "Schmidl, Tobias (T CED SES-DE)" <tobiasschmidl@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"MacDonald, Joe (DI SW CAS ES EPT)" <joe.macdonald@siemens.com>
Subject: Re: [PATCH v2 1/1] expand-on-first-boot: Switch from resize2fs to systemd-growfs
Date: Thu, 2 Jun 2022 20:37:31 +0200	[thread overview]
Message-ID: <20220602203731.1e64a8d2@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <960aaede1657fd4c039582add4dfdb750cc82f9f.camel@siemens.com>

Am Thu, 2 Jun 2022 18:26:05 +0200
schrieb "Schmidl, Tobias (T CED SES-DE)" <tobiasschmidl@siemens.com>:

> Hi all,
> >   
> 
> > > 
> > >  .../expand-on-first-boot/expand-on-first-boot_1.1.bb   |  5 +++--
> > >  .../files/expand-last-partition.sh                     | 10
> > > ++++++++-- 2 files changed, 11 insertions(+), 4 deletions(-)
> > > 
> > > diff --git
> > > a/meta/recipes-support/expand-on-first-boot/expand-on-first-
> > > boot_1.1.bb
> > > b/meta/recipes-support/expand-on-first-boot/expand-on-first-
> > > boot_1.1.bb
> > > index 1703a64..09ff234 100644 ---
> > > a/meta/recipes-support/expand-on-first-boot/expand-on-first-
> > > boot_1.1.bb
> > > +++
> > > b/meta/recipes-support/expand-on-first-boot/expand-on-first-
> > > boot_1.1.bb
> > > @@ -1,15 +1,16 @@ # Resize last partition to full medium size on
> > > fist boot # # This software is a part of ISAR. -# Copyright (c)
> > > Siemens AG, 2018 +# Copyright (c) Siemens AG, 2018-2022
> > >  #
> > >  # SPDX-License-Identifier: MIT
> > >  
> > >  inherit dpkg-raw
> > >  
> > >  DESCRIPTION = "This service grows the last partition to the full
> > > medium during first boot" +MAINTAINER = "isar-users
> > > <isar-users@googlegroups.com>" 
> > > -DEBIAN_DEPENDS = "systemd, sed, grep, coreutils, mount,
> > > e2fsprogs,  
> > 
> > Maybe e2fsprogs can be dropped now? If not ... maybe we need to add
> > something here to really enable btrfs?
> > 
> >   
> 
> 
> while I'm on it, should I also do a version bump for the package to
> 1.2, since there a lot of new stuff in it?

Very good point, yes please bump when you touch. Version is up to you
but 1.2 sounds good.

Henning

> Kind regards,
> 
> Tobias


      reply	other threads:[~2022-06-02 18:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 11:37 [PATCH v2 0/1] " Tobias Schmidl
2022-05-30 11:37 ` [PATCH v2 1/1] " Tobias Schmidl
2022-06-02 14:47   ` Henning Schild
2022-06-02 16:26     ` Schmidl, Tobias
2022-06-02 18:37       ` Henning Schild [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220602203731.1e64a8d2@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=joe.macdonald@siemens.com \
    --cc=tobiasschmidl@siemens.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox