Any way to make cryptsetup smaller? I have a small 32M NOR flash and 11M SquashFS rootfs.

Any way to make cryptsetup smaller? I have a small 32M NOR flash and 11M SquashFS rootfs.

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 470 bytes --]

Hi,

I have a 32M NOR that I boot from and it uses a 11M SquashFS rootfs made
from core-image-minimal.  I'd like to add cryptsetup but doing so blows my
SquashFS up to 35M.

I've looked at the recipe and package config and I see things like
--enable-static and other settings that look doubtful that I can build
cryptsetup package and get it to fit my size constraints.

All I'm wanting to do is encrypt a filesytem and mount it as ext4.

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 1275 bytes --]

Re: [oe] Any way to make cryptsetup smaller? I have a small 32M NOR flash and 11M SquashFS rootfs.

[Khem Raj]

On 8/2/21 11:07 AM, Brian Hutchinson wrote:
> Hi,
> 
> I have a 32M NOR that I boot from and it uses a 11M SquashFS rootfs made 
> from core-image-minimal.  I'd like to add cryptsetup but doing so blows 
> my SquashFS up to 35M.
> 
> I've looked at the recipe and package config and I see things like 
> --enable-static and other settings that look doubtful that I can build 
> cryptsetup package and get it to fit my size constraints.
> 
> All I'm wanting to do is encrypt a filesytem and mount it as ext4.
> 

Can you list all the direct/indirect dependencies that cryptsetup is 
bringing in ? perhaps buildhistory will be handy to get that information

> Regards,
> 
> Brian
> 
> 
> 
> 

Re: [oe] Any way to make cryptsetup smaller? I have a small 32M NOR flash and 11M SquashFS rootfs.

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 2841 bytes --]

Hey Khem,

On Mon, Aug 2, 2021 at 4:05 PM Khem Raj <raj.khem@gmail.com> wrote:

>
>
> On 8/2/21 11:07 AM, Brian Hutchinson wrote:
> > Hi,
> >
> > I have a 32M NOR that I boot from and it uses a 11M SquashFS rootfs made
> > from core-image-minimal.  I'd like to add cryptsetup but doing so blows
> > my SquashFS up to 35M.
> >
> > I've looked at the recipe and package config and I see things like
> > --enable-static and other settings that look doubtful that I can build
> > cryptsetup package and get it to fit my size constraints.
> >
> > All I'm wanting to do is encrypt a filesytem and mount it as ext4.
> >
>
> Can you list all the direct/indirect dependencies that cryptsetup is
> bringing in ? perhaps buildhistory will be handy to get that information
>
> You mean something like this:

bitbake -g cryptsetup && cat pn-buildlist | grep -ve "native" | sort | uniq
WARNING: You have included the meta-virtualization layer, but
'virtualization' has not been enabled in your DISTRO_FEATURES. Some
bbappend files may not take effect. See the meta-virtualization README for
details on enabling virtualization support.
Loading cache: 100%
|###############################################################################################################################################################################################################################################|
Time: 0:00:00
Loaded 5177 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
NOTE: PN build list saved to 'pn-buildlist'
NOTE: Task dependencies saved to 'task-depends.dot'

Summary: There was 1 WARNING message shown.
acl
attr
autoconf
autoconf-archive
automake
base-files
base-passwd
bash
bash-completion
bc
binutils
binutils-cross-aarch64
bison
boost
btrfs-tools
bzip2
ca-certificates
coreutils
cryptsetup
db
dbus
dbus-test
depmodwrapper-cross
diffutils
e2fsprogs
elfutils
eudev
expat
findutils
flex
gawk
gcc
gcc-cross-aarch64
gcc-runtime
gcc-source-9.3.0
gdbm
gettext
glib-2.0
glibc
glibc-locale
gmp
gnome-desktop-testing
gnu-config
grep
icu
initscripts
iproute2
iptables
json-c
kmod
libaio
libcap
libcap-ng
libcroco
libdevmapper
liberror-perl
libffi
libgcc
libgcc-initial
libmnl
libmodule-build-perl
libmpc
libnsl2
libpcre
libtirpc
libtool
libtool-cross
libxcrypt
libxml2
linux-fslc-imx
linux-libc-headers
lvm2
lzo
m4
make
mdadm
mpfr
ncurses
openssl
opkg-utils
packagegroup-core-buildessential
perl
pkgconfig
popt
procps
ptest-runner
python3
readline
sed
shadow
shadow-securetty
shadow-sysroot
shared-mime-info
socat
sqlite3
tcp-wrappers
thin-provisioning-tools
tzdata
unzip
update-rc.d
util-linux
which
xz
zlib

Looks like everything but the kitchen sink.

Thanks,

Brian

[-- Attachment #2: Type: text/html, Size: 4998 bytes --]

Re: [oe] Any way to make cryptsetup smaller? I have a small 32M NOR flash and 11M SquashFS rootfs.

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 3494 bytes --]

I meant build an image like you do and then add cryptsetup and do a build
again this all after enabling build history then check build history repo
and it will have the information on top commit about what changed and which
all packages got added and how much are they adding to size

On Mon, Aug 2, 2021 at 3:17 PM Brian Hutchinson <b.hutchman@gmail.com>
wrote:

> Hey Khem,
>
> On Mon, Aug 2, 2021 at 4:05 PM Khem Raj <raj.khem@gmail.com> wrote:
>
>>
>>
>> On 8/2/21 11:07 AM, Brian Hutchinson wrote:
>> > Hi,
>> >
>> > I have a 32M NOR that I boot from and it uses a 11M SquashFS rootfs
>> made
>> > from core-image-minimal.  I'd like to add cryptsetup but doing so blows
>> > my SquashFS up to 35M.
>> >
>> > I've looked at the recipe and package config and I see things like
>> > --enable-static and other settings that look doubtful that I can build
>> > cryptsetup package and get it to fit my size constraints.
>> >
>> > All I'm wanting to do is encrypt a filesytem and mount it as ext4.
>> >
>>
>> Can you list all the direct/indirect dependencies that cryptsetup is
>> bringing in ? perhaps buildhistory will be handy to get that information
>>
>> You mean something like this:
>
> bitbake -g cryptsetup && cat pn-buildlist | grep -ve "native" | sort |
> uniq
> WARNING: You have included the meta-virtualization layer, but
> 'virtualization' has not been enabled in your DISTRO_FEATURES. Some
> bbappend files may not take effect. See the meta-virtualization README for
> details on enabling virtualization support.
> Loading cache: 100%
> |###############################################################################################################################################################################################################################################|
> Time: 0:00:00
> Loaded 5177 entries from dependency cache.
> NOTE: Resolving any missing task queue dependencies
> NOTE: PN build list saved to 'pn-buildlist'
> NOTE: Task dependencies saved to 'task-depends.dot'
>
> Summary: There was 1 WARNING message shown.
> acl
> attr
> autoconf
> autoconf-archive
> automake
> base-files
> base-passwd
> bash
> bash-completion
> bc
> binutils
> binutils-cross-aarch64
> bison
> boost
> btrfs-tools
> bzip2
> ca-certificates
> coreutils
> cryptsetup
> db
> dbus
> dbus-test
> depmodwrapper-cross
> diffutils
> e2fsprogs
> elfutils
> eudev
> expat
> findutils
> flex
> gawk
> gcc
> gcc-cross-aarch64
> gcc-runtime
> gcc-source-9.3.0
> gdbm
> gettext
> glib-2.0
> glibc
> glibc-locale
> gmp
> gnome-desktop-testing
> gnu-config
> grep
> icu
> initscripts
> iproute2
> iptables
> json-c
> kmod
> libaio
> libcap
> libcap-ng
> libcroco
> libdevmapper
> liberror-perl
> libffi
> libgcc
> libgcc-initial
> libmnl
> libmodule-build-perl
> libmpc
> libnsl2
> libpcre
> libtirpc
> libtool
> libtool-cross
> libxcrypt
> libxml2
> linux-fslc-imx
> linux-libc-headers
> lvm2
> lzo
> m4
> make
> mdadm
> mpfr
> ncurses
> openssl
> opkg-utils
> packagegroup-core-buildessential
> perl
> pkgconfig
> popt
> procps
> ptest-runner
> python3
> readline
> sed
> shadow
> shadow-securetty
> shadow-sysroot
> shared-mime-info
> socat
> sqlite3
> tcp-wrappers
> thin-provisioning-tools
> tzdata
> unzip
> update-rc.d
> util-linux
> which
> xz
> zlib
>
> Looks like everything but the kitchen sink.
>
> Thanks,
>
> Brian
>

[-- Attachment #2: Type: text/html, Size: 5712 bytes --]

Re: [oe] Any way to make cryptsetup smaller? I have a small 32M NOR flash and 11M SquashFS rootfs.

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 553 bytes --]

On Mon, Aug 2, 2021 at 7:06 PM Khem Raj <raj.khem@gmail.com> wrote:

>
> I meant build an image like you do and then add cryptsetup and do a build
> again this all after enabling build history then check build history repo
> and it will have the information on top commit about what changed and which
> all packages got added and how much are they adding to size
>

Use both:

INHERIT += "buildhistory"

BUILDHISTORY_COMMIT = "1"

???

I've never used it before.

Do I have to smoke /tmp and rebuild everything?

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 1278 bytes --]

Re: [oe] Any way to make cryptsetup smaller? I have a small 32M NOR flash and 11M SquashFS rootfs.

[Khem Raj]

On Mon, Aug 2, 2021 at 4:14 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
>
>
> On Mon, Aug 2, 2021 at 7:06 PM Khem Raj <raj.khem@gmail.com> wrote:
>>
>>
>> I meant build an image like you do and then add cryptsetup and do a build again this all after enabling build history then check build history repo and it will have the information on top commit about what changed and which all packages got added and how much are they adding to size
>
>
> Use both:
>
> INHERIT += "buildhistory"
>
> BUILDHISTORY_COMMIT = "1"

yes see for e.g.
https://github.com/YoeDistro/yoe-distro/blob/master/sources/meta-yoe/conf/distro/yoe.inc#L49
https://github.com/YoeDistro/yoe-distro/blob/master/sources/meta-yoe/conf/distro/yoe.inc#L93


>
> ???
>
> I've never used it before.
>
> Do I have to smoke /tmp and rebuild everything?

No, but perhaps better to do so. You can still reuse sstate

>
> Regards,
>
> Brian

Re: [oe] Any way to make cryptsetup smaller? I have a small 32M NOR flash and 11M SquashFS rootfs.

[Andrea Adami]

Brian,

wow, I think we are the last NOR users here in OE.
I gave the collie to Marcin: let see if another OpenZaurus arises :)

Cheers
A.A.


On Tue, Aug 3, 2021 at 5:16 AM Khem Raj <raj.khem@gmail.com> wrote:
>
> On Mon, Aug 2, 2021 at 4:14 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
> >
> >
> >
> > On Mon, Aug 2, 2021 at 7:06 PM Khem Raj <raj.khem@gmail.com> wrote:
> >>
> >>
> >> I meant build an image like you do and then add cryptsetup and do a build again this all after enabling build history then check build history repo and it will have the information on top commit about what changed and which all packages got added and how much are they adding to size
> >
> >
> > Use both:
> >
> > INHERIT += "buildhistory"
> >
> > BUILDHISTORY_COMMIT = "1"
>
> yes see for e.g.
> https://github.com/YoeDistro/yoe-distro/blob/master/sources/meta-yoe/conf/distro/yoe.inc#L49
> https://github.com/YoeDistro/yoe-distro/blob/master/sources/meta-yoe/conf/distro/yoe.inc#L93
>
>
> >
> > ???
> >
> > I've never used it before.
> >
> > Do I have to smoke /tmp and rebuild everything?
>
> No, but perhaps better to do so. You can still reuse sstate
>
> >
> > Regards,
> >
> > Brian
>
> 
>

Re: [oe] Any way to make cryptsetup smaller? I have a small 32M NOR flash and 11M SquashFS rootfs.

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 577 bytes --]

On Tue, Aug 3, 2021, 10:00 AM Andrea Adami <andrea.adami@gmail.com> wrote:

> Brian,
>
> wow, I think we are the last NOR users here in OE.
> I gave the collie to Marcin: let see if another OpenZaurus arises :)
>
> Cheers
> A.A.
>

Ha, ha,  yes, and I even hardware partitioned my MLC eMMC converting much
of it to SLC (or whatever the soft SLC is called these days).

I still have two Sharp SL-5500's ... don't get much free time to play with
them.  IMX8MM taking up all my time.

Fighting Linux bloat .. getting as bad as Windoze.

Regards,

Brian

>

[-- Attachment #2: Type: text/html, Size: 1247 bytes --]