Date   

Re: [WIC] Wic creates spurious partition

Rudolf J Streif
 

Ok, I found the answer to my own question. It's the typical extended partition issue.

:rjs

On 4/30/20 4:36 PM, Rudolf J Streif via lists.yoctoproject.org wrote:
I seem to be running into wic problems today...

I have the following wks file:


              
part SPL --source rawcopy --sourceparams="file=SPL" --ondisk mmcblk
--no-table --align 1
part u-boot --source rawcopy --sourceparams="file=${UBOOT_BINARY}"
--ondisk mmcblk --no-table --align 69
part /boot --source bootimg-partition --ondisk mmcblk1 --fstype=vfat
--label boot --active --align 4096 --fixed-size 16

part /mnt/persistent --ondisk mmcblk1 --fstype=ext4 --label persistent
--fixed-size 10
part / --source rootfs --ondisk mmcblk1 --fstype=ext4 --label rootfs1
--size 500
part /mnt/rootfs2 --source rootfs --ondisk mmcblk1 --fstype=ext4 --label
rootfs2 --size 500
part /mnt/internal_storage --ondisk mmcblk1 --fstype=ext4 --label data
--size 1000

bootloader --ptable msdos

              
That should create 7 partitions of which 5 have a file system. However,
when I flash the emmc with it and boot the device:

# fdisk /dev/mmcblk1

Disk /dev/mmcblk1: 3.62 GiB, 3867148288 bytes, 7553024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0813790a

Device         Boot   Start     End Sectors  Size Id Type
/dev/mmcblk1p1 *       8192   40959   32768   16M  c W95 FAT32 (LBA)
/dev/mmcblk1p2        40960   61439   20480   10M 83 Linux
/dev/mmcblk1p3        61440 1392639 1331200  650M 83 Linux
/dev/mmcblk1p4      1392640 4771841 3379202  1.6G  f W95 Ext'd (LBA)
/dev/mmcblk1p5      1392641 2723840 1331200  650M 83 Linux
/dev/mmcblk1p6      2723842 4771841 2048000 1000M 83 Linux

There is another partition that essentially overlaps the last two. That
makes no sense.

Thanks,
Rudi




    

  


Re: [WIC] Wic creates spurious partition

Scott Murray
 

On Thu, 30 Apr 2020, Rudolf J Streif wrote:

I seem to be running into wic problems today...

I have the following wks file:

part SPL --source rawcopy --sourceparams="file=SPL" --ondisk mmcblk
--no-table --align 1
part u-boot --source rawcopy --sourceparams="file=${UBOOT_BINARY}"
--ondisk mmcblk --no-table --align 69
part /boot --source bootimg-partition --ondisk mmcblk1 --fstype=vfat
--label boot --active --align 4096 --fixed-size 16

part /mnt/persistent --ondisk mmcblk1 --fstype=ext4 --label persistent
--fixed-size 10
part / --source rootfs --ondisk mmcblk1 --fstype=ext4 --label rootfs1
--size 500
part /mnt/rootfs2 --source rootfs --ondisk mmcblk1 --fstype=ext4 --label
rootfs2 --size 500
part /mnt/internal_storage --ondisk mmcblk1 --fstype=ext4 --label data
--size 1000

bootloader --ptable msdos
That should create 7 partitions of which 5 have a file system. However,
when I flash the emmc with it and boot the device:

# fdisk /dev/mmcblk1

Disk /dev/mmcblk1: 3.62 GiB, 3867148288 bytes, 7553024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0813790a

Device         Boot   Start     End Sectors  Size Id Type
/dev/mmcblk1p1 *       8192   40959   32768   16M  c W95 FAT32 (LBA)
/dev/mmcblk1p2        40960   61439   20480   10M 83 Linux
/dev/mmcblk1p3        61440 1392639 1331200  650M 83 Linux
/dev/mmcblk1p4      1392640 4771841 3379202  1.6G  f W95 Ext'd (LBA)
/dev/mmcblk1p5      1392641 2723840 1331200  650M 83 Linux
/dev/mmcblk1p6      2723842 4771841 2048000 1000M 83 Linux

There is another partition that essentially overlaps the last two. That
makes no sense.
That makes sense for DOS partitioning; there can only be 4 primary
partitions, so number 4 is marked as an extended partition with the
total space of the further logical partitions.

Scott


Re: [WIC] Wic creates spurious partition

Sergey Bostandzhyan
 

Hi Rudi,

On Thu, Apr 30, 2020 at 04:36:39PM -0700, Rudolf J Streif wrote:
bootloader --ptable msdos


That should create 7 partitions of which 5 have a file system. However,
when I flash the emmc with it and boot the device:

did you mean --ptable gpt?

/dev/mmcblk1p4      1392640 4771841 3379202  1.6G  f W95 Ext'd (LBA)
/dev/mmcblk1p5      1392641 2723840 1331200  650M 83 Linux
/dev/mmcblk1p6      2723842 4771841 2048000 1000M 83 Linux
In msdos layout you can only have a limited number of primary partitions,
anything exceeding that will go into extended partitions which you see
as "overlapping" here, in the above paste p5 and p6 are actually within the
extended p4 (hinted by W95 Ext'd)

Kind regards,
Jin






[WIC] Wic creates spurious partition

Rudolf J Streif
 

I seem to be running into wic problems today...

I have the following wks file:

part SPL --source rawcopy --sourceparams="file=SPL" --ondisk mmcblk
--no-table --align 1
part u-boot --source rawcopy --sourceparams="file=${UBOOT_BINARY}"
--ondisk mmcblk --no-table --align 69
part /boot --source bootimg-partition --ondisk mmcblk1 --fstype=vfat
--label boot --active --align 4096 --fixed-size 16

part /mnt/persistent --ondisk mmcblk1 --fstype=ext4 --label persistent
--fixed-size 10
part / --source rootfs --ondisk mmcblk1 --fstype=ext4 --label rootfs1
--size 500
part /mnt/rootfs2 --source rootfs --ondisk mmcblk1 --fstype=ext4 --label
rootfs2 --size 500
part /mnt/internal_storage --ondisk mmcblk1 --fstype=ext4 --label data
--size 1000

bootloader --ptable msdos
That should create 7 partitions of which 5 have a file system. However,
when I flash the emmc with it and boot the device:

# fdisk /dev/mmcblk1

Disk /dev/mmcblk1: 3.62 GiB, 3867148288 bytes, 7553024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0813790a

Device         Boot   Start     End Sectors  Size Id Type
/dev/mmcblk1p1 *       8192   40959   32768   16M  c W95 FAT32 (LBA)
/dev/mmcblk1p2        40960   61439   20480   10M 83 Linux
/dev/mmcblk1p3        61440 1392639 1331200  650M 83 Linux
/dev/mmcblk1p4      1392640 4771841 3379202  1.6G  f W95 Ext'd (LBA)
/dev/mmcblk1p5      1392641 2723840 1331200  650M 83 Linux
/dev/mmcblk1p6      2723842 4771841 2048000 1000M 83 Linux

There is another partition that essentially overlaps the last two. That
makes no sense.

Thanks,
Rudi


Re: [WIC] Grow last partition up to disk size

Khem Raj
 

On 4/30/20 4:11 PM, Rudolf J Streif wrote:
Thanks, guys, I appreciate it.
Doing it dynamically on first boot would probably work as it is a data partition and not the rootfs partition.
I will give it a try.
96boards-tools also has a script which works regardless of init systems

https://github.com/96boards/meta-96boards/blob/master/recipes-bsp/96boards-tools/96boards-tools_0.12.bb

:rjs
On 4/30/20 12:13 PM, Michael Nazzareno Trimarchi wrote:
Hi

On Thu, Apr 30, 2020 at 9:10 PM Michael Nazzareno Trimarchi via
lists.yoctoproject.org
<michael=amarulasolutions.com@...> wrote:
Hi

Well I have write something like this

[Unit]
Description=Increases rootfs image size to fit partition
Requires=dev-disk-by\x2dpartlabel-rootfs.device
After=dev-disk-by\x2dpartlabel-rootfs.device

[Service]
Type=oneshot
ExecStart=/usr/sbin/sgdisk /dev/disk/by-path/platform-ff0f0000.dwmmc -e
This resize gpt up to disk size

ExecStart=/usr/sbin/parted /dev/disk/by-path/platform-ff0f0000.dwmmc
-s "resizepart 4 -1" quit
This resize partition number 4 up to the max

Michael

ExecStart=/sbin/resize2fs /dev/disk/by-partlabel/rootfs
ExecStart=/bin/systemctl disable resize-rootfs.service

StandardOutput=journal+console

[Install]
WantedBy=default.target


On Thu, Apr 30, 2020 at 8:30 PM Marek Belisko<marek.belisko@...> wrote:
On Thu, Apr 30, 2020 at 8:27 PM Khem Raj<raj.khem@...> wrote:

On 4/30/20 11:25 AM, Marek Belisko wrote:
On Thu, Apr 30, 2020 at 8:23 PM Khem Raj<raj.khem@...> wrote:

On 4/30/20 11:16 AM, Marek Belisko wrote:
Hi Rudolf,

On Thu, Apr 30, 2020 at 7:39 PM Rudolf J Streif
<rudolf.streif@...> wrote:
I was looking for a way in a wks file to have wic grow the last
partition to fill up the remainder of the disk. Of course wic does not
know how large the disk is but that could be a parameter.

The alternative way is to use fixed-size and do the math manually but
that would not allow wic to grow a partition based on content.
You can usehttps://manpages.debian.org/testing/systemd/systemd-growfs.8.en.html
which grow partition to the end.
can it grow a mounted partition ? since that will be the case when
growing rootfs partition.
It will grow last partition in first boot only.
my question was will it grow a mounted rootfs parition if that happens
tobe the last partition, I understand it will grow last partion and do
it as firstboot service.
I usually use it in case when have dual rootfs (A, B) and data
partition which is expanded to then end of disk.
I don't have experience with growing rootfs (I think it can grow only
not mounted partitions)
:rjs


BR,

marek



BR,

marek



marek


--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web:http://open-nandra.com
--
| Michael Nazzareno Trimarchi Amarula Solutions BV |
| COO - Founder Cruquiuskade 47 |
| +31(0)851119172 Amsterdam 1018 AM NL |
| [`as]http://www.amarulasolutions.com |
--
-----
Rudolf J Streif
CEO/CTO ibeeto
+1.855.442.3386 x700


Re: [WIC] Grow last partition up to disk size

Rudolf J Streif
 

Thanks, guys, I appreciate it.

Doing it dynamically on first boot would probably work as it is a data partition and not the rootfs partition.

I will give it a try.

:rjs

On 4/30/20 12:13 PM, Michael Nazzareno Trimarchi wrote:
Hi

On Thu, Apr 30, 2020 at 9:10 PM Michael Nazzareno Trimarchi via
lists.yoctoproject.org
<michael=amarulasolutions.com@...> wrote:
Hi

Well I have write something like this

[Unit]
Description=Increases rootfs image size to fit partition
Requires=dev-disk-by\x2dpartlabel-rootfs.device
After=dev-disk-by\x2dpartlabel-rootfs.device

[Service]
Type=oneshot
ExecStart=/usr/sbin/sgdisk /dev/disk/by-path/platform-ff0f0000.dwmmc -e
This resize gpt up to disk size

ExecStart=/usr/sbin/parted /dev/disk/by-path/platform-ff0f0000.dwmmc
-s "resizepart 4 -1" quit
This resize partition number 4 up to the max

Michael

ExecStart=/sbin/resize2fs /dev/disk/by-partlabel/rootfs
ExecStart=/bin/systemctl disable resize-rootfs.service

StandardOutput=journal+console

[Install]
WantedBy=default.target


On Thu, Apr 30, 2020 at 8:30 PM Marek Belisko <marek.belisko@...> wrote:
On Thu, Apr 30, 2020 at 8:27 PM Khem Raj <raj.khem@...> wrote:


On 4/30/20 11:25 AM, Marek Belisko wrote:
On Thu, Apr 30, 2020 at 8:23 PM Khem Raj <raj.khem@...> wrote:


On 4/30/20 11:16 AM, Marek Belisko wrote:
Hi Rudolf,

On Thu, Apr 30, 2020 at 7:39 PM Rudolf J Streif
<rudolf.streif@...> wrote:
I was looking for a way in a wks file to have wic grow the last
partition to fill up the remainder of the disk. Of course wic does not
know how large the disk is but that could be a parameter.

The alternative way is to use fixed-size and do the math manually but
that would not allow wic to grow a partition based on content.
You can use https://manpages.debian.org/testing/systemd/systemd-growfs.8.en.html
which grow partition to the end.
can it grow a mounted partition ? since that will be the case when
growing rootfs partition.
It will grow last partition in first boot only.
my question was will it grow a mounted rootfs parition if that happens
tobe the last partition, I understand it will grow last partion and do
it as firstboot service.
I usually use it in case when have dual rootfs (A, B) and data
partition which is expanded to then end of disk.
I don't have experience with growing rootfs (I think it can grow only
not mounted partitions)

            

                
:rjs



BR,

marek





              
BR,

marek





          
marek


--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com



--
| Michael Nazzareno Trimarchi                     Amarula Solutions BV |
| COO  -  Founder                                      Cruquiuskade 47 |
| +31(0)851119172                                 Amsterdam 1018 AM NL |
|                  [`as] http://www.amarulasolutions.com               |





    
-- 
-----
Rudolf J Streif
CEO/CTO ibeeto
+1.855.442.3386 x700


Re: [PATCH] openssl: Fix dependency loop with PACKAGECONFIG cryptodev-linux

Denys Dmytriyenko
 

On Thu, Apr 30, 2020 at 08:23:11PM +0000, Scott Ellis wrote:

Hi, Scott,

Sorry, I'm not trying to discourage you from submitting patches, but there are
few issues with your patch here - see below and inline.

First of all, patches for OE-core should be sent to:
openembedded-core@...
https://lists.openembedded.org/g/openembedded-core

Looks like you are building poky-zeus - Poky, as a distro, is composed from
multiple components/layers, such as bitbake, oe-core/meta, meta-poky and
meta-yocto-bsp. Most of them have own git repos with corresponding mailing
lists - usually mentioned in corresponding README files, please check those.


Applies to both zeus and dunfell
The process to get your change backported to older branches/releases is to
submit it against master, and once accepted, re-send and ask to backport to
other branches, such as zeus and dunfell with the name of the branch in the
subject. That is because different branches/versions are usually maintained
by different people.


ERROR: Nothing RPROVIDES 'cryptodev-module-native' (but virtual:native:/home/scott/poky-zeus/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb RDEPENDS on or otherwise requires it)
ERROR: Required build target 'openssl' has no buildable providers.
Missing or unbuildable dependency chain was: ['openssl', 'rpm-native', 'python3-native', 'openssl-native', 'cryptodev-module-native']
Not sure how you were able to set the wrong PACKAGECONFIG for openssl-native,
when it gets explicitly emptied in the recipe below.


diff --git a/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb b/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb
index aa4ef6f48a..a952fae728 100644
--- a/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb
+++ b/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb
@@ -32,7 +32,7 @@ PACKAGECONFIG ?= ""
PACKAGECONFIG_class-native = ""
PACKAGECONFIG_class-nativesdk = ""
Here, ^^^ PACKAGECONFIG should all be empty for native and nativesdk versions
of openssl.


-PACKAGECONFIG[cryptodev-linux] = "enable-devcryptoeng,disable-devcryptoeng,cryptodev-linux,,cryptodev-module"
+PACKAGECONFIG[cryptodev-linux] = "enable-devcryptoeng,disable-devcryptoeng,cryptodev-linux"
This is not a fix, but rather a workaround for a bad setup. Moreover, it
actually reverts my recent fix to RDEPENDS on cryptodev-module, which is
needed to properly support devcryptoeng in openssl.

Maybe if you share with us how you set your environment, we would be able to
help you resolve it properly. Thank you!

--
Denys


B = "${WORKDIR}/build"
do_configure[cleandirs] = "${B}"
--
2.17.1


How to include initrd.cpio to image

Gmane Admin
 

I am generating core-image-minimal-initramfs-edison.cpio.gz which is found in the deploy-core-image-minimal-initramfs-image-complete/ directory.

When I build my image edison-image initrd gets included and deployed in edison-image-edison.hddimg. But I am not using that.

I also generate edison-image-edison.ext4 which has bzImage kernel in /boot. But by Zeus, I have no idea how to get edison-image to install a file from the other recipe's deploy.

To me it doesn't make sense to include bzImage without initrd, kernel will not be able to load the rootfs without.

I know I can bundle the initramfs, and that has worked fine before. Until kernel + initrd grew above 15MB, now U-Boot won't load it. I have now kernel = 10MB + initrd = 10MB which boot fine when I copy initrd to /boot manually.


[PATCH] openssl: Fix dependency loop with PACKAGECONFIG cryptodev-linux

Scott Ellis
 

Applies to both zeus and dunfell

ERROR: Nothing RPROVIDES 'cryptodev-module-native' (but virtual:native:/home/scott/poky-zeus/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb RDEPENDS on or otherwise requires it)
ERROR: Required build target 'openssl' has no buildable providers.
Missing or unbuildable dependency chain was: ['openssl', 'rpm-native', 'python3-native', 'openssl-native', 'cryptodev-module-native']

Signed-off-by: Scott Ellis <scott@...>
---
meta/recipes-connectivity/openssl/openssl_1.1.1f.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb b/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb
index aa4ef6f48a..a952fae728 100644
--- a/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb
+++ b/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb
@@ -32,7 +32,7 @@ PACKAGECONFIG ?= ""
PACKAGECONFIG_class-native = ""
PACKAGECONFIG_class-nativesdk = ""

-PACKAGECONFIG[cryptodev-linux] = "enable-devcryptoeng,disable-devcryptoeng,cryptodev-linux,,cryptodev-module"
+PACKAGECONFIG[cryptodev-linux] = "enable-devcryptoeng,disable-devcryptoeng,cryptodev-linux"

B = "${WORKDIR}/build"
do_configure[cleandirs] = "${B}"
--
2.17.1


Re: [WIC] Grow last partition up to disk size

Michael Nazzareno Trimarchi
 

Hi

On Thu, Apr 30, 2020 at 9:10 PM Michael Nazzareno Trimarchi via
lists.yoctoproject.org
<michael=amarulasolutions.com@...> wrote:

Hi

Well I have write something like this

[Unit]
Description=Increases rootfs image size to fit partition
Requires=dev-disk-by\x2dpartlabel-rootfs.device
After=dev-disk-by\x2dpartlabel-rootfs.device

[Service]
Type=oneshot
ExecStart=/usr/sbin/sgdisk /dev/disk/by-path/platform-ff0f0000.dwmmc -e
This resize gpt up to disk size

ExecStart=/usr/sbin/parted /dev/disk/by-path/platform-ff0f0000.dwmmc
-s "resizepart 4 -1" quit
This resize partition number 4 up to the max

Michael

ExecStart=/sbin/resize2fs /dev/disk/by-partlabel/rootfs
ExecStart=/bin/systemctl disable resize-rootfs.service

StandardOutput=journal+console

[Install]
WantedBy=default.target


On Thu, Apr 30, 2020 at 8:30 PM Marek Belisko <marek.belisko@...> wrote:

On Thu, Apr 30, 2020 at 8:27 PM Khem Raj <raj.khem@...> wrote:



On 4/30/20 11:25 AM, Marek Belisko wrote:
On Thu, Apr 30, 2020 at 8:23 PM Khem Raj <raj.khem@...> wrote:



On 4/30/20 11:16 AM, Marek Belisko wrote:
Hi Rudolf,

On Thu, Apr 30, 2020 at 7:39 PM Rudolf J Streif
<rudolf.streif@...> wrote:

I was looking for a way in a wks file to have wic grow the last
partition to fill up the remainder of the disk. Of course wic does not
know how large the disk is but that could be a parameter.

The alternative way is to use fixed-size and do the math manually but
that would not allow wic to grow a partition based on content.
You can use https://manpages.debian.org/testing/systemd/systemd-growfs.8.en.html
which grow partition to the end.
can it grow a mounted partition ? since that will be the case when
growing rootfs partition.
It will grow last partition in first boot only.
my question was will it grow a mounted rootfs parition if that happens
tobe the last partition, I understand it will grow last partion and do
it as firstboot service.
I usually use it in case when have dual rootfs (A, B) and data
partition which is expanded to then end of disk.
I don't have experience with growing rootfs (I think it can grow only
not mounted partitions)



:rjs


BR,

marek



BR,

marek



marek


--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com


--
| Michael Nazzareno Trimarchi Amarula Solutions BV |
| COO - Founder Cruquiuskade 47 |
| +31(0)851119172 Amsterdam 1018 AM NL |
| [`as] http://www.amarulasolutions.com |


--
| Michael Nazzareno Trimarchi Amarula Solutions BV |
| COO - Founder Cruquiuskade 47 |
| +31(0)851119172 Amsterdam 1018 AM NL |
| [`as] http://www.amarulasolutions.com |


Re: [WIC] Grow last partition up to disk size

Michael Nazzareno Trimarchi
 

Hi

Well I have write something like this

[Unit]
Description=Increases rootfs image size to fit partition
Requires=dev-disk-by\x2dpartlabel-rootfs.device
After=dev-disk-by\x2dpartlabel-rootfs.device

[Service]
Type=oneshot
ExecStart=/usr/sbin/sgdisk /dev/disk/by-path/platform-ff0f0000.dwmmc -e
ExecStart=/usr/sbin/parted /dev/disk/by-path/platform-ff0f0000.dwmmc
-s "resizepart 4 -1" quit
ExecStart=/sbin/resize2fs /dev/disk/by-partlabel/rootfs
ExecStart=/bin/systemctl disable resize-rootfs.service

StandardOutput=journal+console

[Install]
WantedBy=default.target

On Thu, Apr 30, 2020 at 8:30 PM Marek Belisko <marek.belisko@...> wrote:

On Thu, Apr 30, 2020 at 8:27 PM Khem Raj <raj.khem@...> wrote:



On 4/30/20 11:25 AM, Marek Belisko wrote:
On Thu, Apr 30, 2020 at 8:23 PM Khem Raj <raj.khem@...> wrote:



On 4/30/20 11:16 AM, Marek Belisko wrote:
Hi Rudolf,

On Thu, Apr 30, 2020 at 7:39 PM Rudolf J Streif
<rudolf.streif@...> wrote:

I was looking for a way in a wks file to have wic grow the last
partition to fill up the remainder of the disk. Of course wic does not
know how large the disk is but that could be a parameter.

The alternative way is to use fixed-size and do the math manually but
that would not allow wic to grow a partition based on content.
You can use https://manpages.debian.org/testing/systemd/systemd-growfs.8.en.html
which grow partition to the end.
can it grow a mounted partition ? since that will be the case when
growing rootfs partition.
It will grow last partition in first boot only.
my question was will it grow a mounted rootfs parition if that happens
tobe the last partition, I understand it will grow last partion and do
it as firstboot service.
I usually use it in case when have dual rootfs (A, B) and data
partition which is expanded to then end of disk.
I don't have experience with growing rootfs (I think it can grow only
not mounted partitions)



:rjs


BR,

marek



BR,

marek



marek


--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com
--
| Michael Nazzareno Trimarchi Amarula Solutions BV |
| COO - Founder Cruquiuskade 47 |
| +31(0)851119172 Amsterdam 1018 AM NL |
| [`as] http://www.amarulasolutions.com |


Re: [WIC] Grow last partition up to disk size

Marek Belisko
 

On Thu, Apr 30, 2020 at 8:27 PM Khem Raj <raj.khem@...> wrote:



On 4/30/20 11:25 AM, Marek Belisko wrote:
On Thu, Apr 30, 2020 at 8:23 PM Khem Raj <raj.khem@...> wrote:



On 4/30/20 11:16 AM, Marek Belisko wrote:
Hi Rudolf,

On Thu, Apr 30, 2020 at 7:39 PM Rudolf J Streif
<rudolf.streif@...> wrote:

I was looking for a way in a wks file to have wic grow the last
partition to fill up the remainder of the disk. Of course wic does not
know how large the disk is but that could be a parameter.

The alternative way is to use fixed-size and do the math manually but
that would not allow wic to grow a partition based on content.
You can use https://manpages.debian.org/testing/systemd/systemd-growfs.8.en.html
which grow partition to the end.
can it grow a mounted partition ? since that will be the case when
growing rootfs partition.
It will grow last partition in first boot only.
my question was will it grow a mounted rootfs parition if that happens
tobe the last partition, I understand it will grow last partion and do
it as firstboot service.
I usually use it in case when have dual rootfs (A, B) and data
partition which is expanded to then end of disk.
I don't have experience with growing rootfs (I think it can grow only
not mounted partitions)



:rjs


BR,

marek



BR,

marek



marek


--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com


Re: [WIC] Grow last partition up to disk size

Khem Raj
 

On 4/30/20 11:25 AM, Marek Belisko wrote:
On Thu, Apr 30, 2020 at 8:23 PM Khem Raj <raj.khem@...> wrote:



On 4/30/20 11:16 AM, Marek Belisko wrote:
Hi Rudolf,

On Thu, Apr 30, 2020 at 7:39 PM Rudolf J Streif
<rudolf.streif@...> wrote:

I was looking for a way in a wks file to have wic grow the last
partition to fill up the remainder of the disk. Of course wic does not
know how large the disk is but that could be a parameter.

The alternative way is to use fixed-size and do the math manually but
that would not allow wic to grow a partition based on content.
You can use https://manpages.debian.org/testing/systemd/systemd-growfs.8.en.html
which grow partition to the end.
can it grow a mounted partition ? since that will be the case when
growing rootfs partition.
It will grow last partition in first boot only.
my question was will it grow a mounted rootfs parition if that happens tobe the last partition, I understand it will grow last partion and do it as firstboot service.



:rjs


BR,

marek



BR,
marek


Re: [WIC] Grow last partition up to disk size

Marek Belisko
 

On Thu, Apr 30, 2020 at 8:23 PM Khem Raj <raj.khem@...> wrote:



On 4/30/20 11:16 AM, Marek Belisko wrote:
Hi Rudolf,

On Thu, Apr 30, 2020 at 7:39 PM Rudolf J Streif
<rudolf.streif@...> wrote:

I was looking for a way in a wks file to have wic grow the last
partition to fill up the remainder of the disk. Of course wic does not
know how large the disk is but that could be a parameter.

The alternative way is to use fixed-size and do the math manually but
that would not allow wic to grow a partition based on content.
You can use https://manpages.debian.org/testing/systemd/systemd-growfs.8.en.html
which grow partition to the end.
can it grow a mounted partition ? since that will be the case when
growing rootfs partition.
It will grow last partition in first boot only.


:rjs


BR,

marek



BR,

marek

--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com


Re: [WIC] Grow last partition up to disk size

Khem Raj
 

On 4/30/20 11:16 AM, Marek Belisko wrote:
Hi Rudolf,
On Thu, Apr 30, 2020 at 7:39 PM Rudolf J Streif
<rudolf.streif@...> wrote:

I was looking for a way in a wks file to have wic grow the last
partition to fill up the remainder of the disk. Of course wic does not
know how large the disk is but that could be a parameter.

The alternative way is to use fixed-size and do the math manually but
that would not allow wic to grow a partition based on content.
You can use https://manpages.debian.org/testing/systemd/systemd-growfs.8.en.html
which grow partition to the end.
can it grow a mounted partition ? since that will be the case when growing rootfs partition.


:rjs


BR,
marek


Re: [WIC] Grow last partition up to disk size

Marek Belisko
 

Hi Rudolf,

On Thu, Apr 30, 2020 at 7:39 PM Rudolf J Streif
<rudolf.streif@...> wrote:

I was looking for a way in a wks file to have wic grow the last
partition to fill up the remainder of the disk. Of course wic does not
know how large the disk is but that could be a parameter.

The alternative way is to use fixed-size and do the math manually but
that would not allow wic to grow a partition based on content.
You can use https://manpages.debian.org/testing/systemd/systemd-growfs.8.en.html
which grow partition to the end.

:rjs


BR,

marek

--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com


[WIC] Grow last partition up to disk size

Rudolf J Streif
 

I was looking for a way in a wks file to have wic grow the last
partition to fill up the remainder of the disk. Of course wic does not
know how large the disk is but that could be a parameter.

The alternative way is to use fixed-size and do the math manually but
that would not allow wic to grow a partition based on content.

:rjs


anyone have a recipe for ruby gem nokogiri?

Robert P. J. Day
 

for a gem that is as popular as that is, i was surprised to not find
a recipe for it. any recipe that is compatible as far back as morty
would be fine, thanks.

rday


License files path

Teemu K.
 

Hi,

Is there a way to determine where the license files are stored? It
would help a lot in automatizing build system when you'd know where to
copy licenses from.

They go to build/tmp/deploy/licenses, but then license.manifest
containing list of all the licenses in an image is under that
directory on directory that changes pretty much every time image is
built. Sometimes also the latest directory contains only
image_license.manifest, but license.manifest and package.manifest is
missing. I haven't been able to track down that issue either.

So is there way to determine which path the licenses were stored in?
And how to generate image so that it will always generate
license.manifest and package.manifest as well?

I noticed that in that licenses - directory there is directory with
image name, but it's not link to latest directory so I can't use that.
Seems that it only lists license/version info for image recipe.

-Teemu


Re: Which recipe for Linux tools to run u-boot command inside Linux?

Nicolas Jeker
 

On Thu, 2020-04-30 at 16:34 +1000, JH wrote:
Hi Yann,

Thanks for the tips, I have run to add libubootenv, but got so many
errors, I can build a good Yocto image before adding libubootenv,
what
was it going on? Does that mean I need to add all kernel modules and
to rebuild kernel configure?
Hi JH,

on Zeus it's very likely _not_ libubootenv that you need, you should
try to install u-boot-fw-utils. As Yann wrote, the tools are in
libubootenv since Dunfell, which is newer than Zeus.

8501 - 8520 of 57789