On 2018-04-11 16:09, Luiz Angelo Daros de Luca wrote:
You can also expand the overlay partition directly on img file or after the
installation.
First expand this physical partition. I like to do it with parted (script
friendly) but it is not available
as OpenWrt tool:
$ /usr/sbin/parted OpenWr
On 2018-04-11 14:50, Tomasz Maciej Nowak wrote:
W dniu 11.04.2018 o 14:35, Mikael Bak pisze:
[snip]
I'm using the Image Builder to create custom images. I can't find any
option how to specify the size of the rootfs and/or the overlay.
Is it possible with Image Builder or must I build the wh
Hi txt.file,
On 2018-04-11 14:48, txt.file wrote:
There is no need to create a bigger squashfs as squashfs is read-only.
With squashfs you get two file systems. squashfs for the files in the
image and jffs2 for changed/added files. During the first boot the jffs2
is created. It starts after the
On 11.04.2018 14:48, txt.file wrote:
There is no need to create a bigger squashfs as squashfs is read-only.
With squashfs you get two file systems. squashfs for the files in the
image and jffs2 for changed/added files. During the first boot the jffs2
is created. It starts after the end of the squ
> >
> > I didn't know a way to expand squashfs, so decided to compile the image
> > and adjusted /root size as per the size of the disk.
> >
> I'm using the Image Builder to create custom images. I can't find any
> option how to specify the size of the rootfs and/or the overlay.
> Is it possible
W dniu 11.04.2018 o 14:35, Mikael Bak pisze:
On 2018-04-11 14:11, Nishant Sharma wrote:
[snip]
I didn't know a way to expand squashfs, so decided to compile the
image and adjusted /root size as per the size of the disk.
I'm using the Image Builder to create custom images. I can't find any
There is no need to create a bigger squashfs as squashfs is read-only.
With squashfs you get two file systems. squashfs for the files in the
image and jffs2 for changed/added files. During the first boot the jffs2
is created. It starts after the end of the squashfs until the end of
device. The good
Hi Mikael,
On Wednesday 11 April 2018 06:05 PM, Mikael Bak wrote:
Is it possible with Image Builder or must I build the whole thing from
source?
That's the exact point where I was stuck. I chose the harder way, but
may be someone on the list could assist us.
Regards,
Nishant
__
On 2018-04-11 14:11, Nishant Sharma wrote:
[snip]
I didn't know a way to expand squashfs, so decided to compile the image
and adjusted /root size as per the size of the disk.
I'm using the Image Builder to create custom images. I can't find any
option how to specify the size of the rootfs
On Wednesday 11 April 2018 05:02 PM, Mikael Bak wrote:
Both are fine, squashfs is recommended. No significant performance
penalty either way.
And added benefit of no RO filesystem mounts on dirty reboots with ext2/3/4.
Do I have to expand the fs after flashing in order to make use of my 1GB
C
On 2018-04-11 11:30, Felix Fietkau wrote:
On 2018-04-11 10:59, Mikael Bak wrote:
[snip]
What is the recommended filesystem to use on a CF card in this case?
[snip]
Both are fine, squashfs is recommended. No significant performance
penalty either way.
- Felix
Thanks Felix,
I will give sq
On 2018-04-11 10:59, Mikael Bak wrote:
> Hi,
>
> I am playing around with an old PC Engines Alix board and I want to put
> OpenWRT on it.
>
> For the x86 platform I see that there are two options: ext4 and squashfs.
>
> What is the recommended filesystem to use on a CF card in this case?
>
> I
12 matches
Mail list logo
