Re: [LEDE-DEV] Advice on filesystem for x86 (CF card)

2018-04-11 Thread txt.file 
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 point is that you have some failsafe mode where you
ignore the jffs2 and only load the squashfs. Then your device has the
same behavior as directly after flashing.

With ext4 you get a single read-write file system (which makes failsafe
difficult).

This is how ar71xx works and I expect x86 does the same. If I am wrong
correct me, please.

kind regards
txt.file

Mikael Bak:
> 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 and/or the overlay.
> 
> Is it possible with Image Builder or must I build the whole thing from
> source?
> 
> TIA,
> Mikael
> 
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH] brcm47xx: proper region code in image name

2017-12-11 Thread txt.file 
Didn't you want to use 'us' as image identifier? In your patch it is
still north america just shortened to 2 letters.

kind regards
txt.file

Moritz Warning:
> Replace 'north-america' by 'us' and remove 'other-regions' in image files for 
> Netgear WGR614 v10.
> 
> Signed-off-by: Moritz Warning <moritzwarn...@web.de>
> ---
>  target/linux/brcm47xx/image/Makefile | 18 +-
>  1 file changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/target/linux/brcm47xx/image/Makefile 
> b/target/linux/brcm47xx/image/Makefile
> index 8c681ac345..ccd6f4dc44 100644
> --- a/target/linux/brcm47xx/image/Makefile
> +++ b/target/linux/brcm47xx/image/Makefile
> @@ -806,21 +806,21 @@ define Device/linksys-e4200-v1
>  endef
>  TARGET_DEVICES += linksys-e4200-v1
>  
> -define Device/netgear-wgr614-v10_north-america
> +define Device/netgear-wgr614-v10-na
>DEVICE_TITLE := Netgear WGR614 v10 North America
>$(Device/netgear)
>NETGEAR_BOARD_ID := U12H139T01_NETGEAR
>NETGEAR_REGION := 2
>  endef
> -TARGET_DEVICES += netgear-wgr614-v10_north-america
> +TARGET_DEVICES += netgear-wgr614-v10-na
>  
> -define Device/netgear-wgr614-v10_other-regions
> -  DEVICE_TITLE := Netgear WGR614 v10 Other Regions
> +define Device/netgear-wgr614-v10
> +  DEVICE_TITLE := Netgear WGR614 v10
>$(Device/netgear)
>NETGEAR_BOARD_ID := U12H139T01_NETGEAR
>NETGEAR_REGION := 1
>  endef
> -TARGET_DEVICES += netgear-wgr614-v10_other-regions
> +TARGET_DEVICES += netgear-wgr614-v10
>  
>  define Device/netgear-wn2500rp-v1
>DEVICE_TITLE := Netgear WN2500RP v1
> @@ -910,23 +910,23 @@ define Device/netgear-wnr2000v2
>  endef
>  TARGET_DEVICES += netgear-wnr2000v2
>  
> -define Device/netgear-wnr3500l-v1-north-america
> +define Device/netgear-wnr3500l-v1-na
>DEVICE_TITLE := Netgear WNR3500L v1 North America
>DEVICE_PACKAGES := kmod-b43 $(USB2_PACKAGES)
>$(Device/netgear)
>NETGEAR_BOARD_ID := U12H136T99_NETGEAR
>NETGEAR_REGION := 2
>  endef
> -TARGET_DEVICES += netgear-wnr3500l-v1-north-america
> +TARGET_DEVICES += netgear-wnr3500l-v1-na
>  
> -define Device/netgear-wnr3500l-v1-other-regions
> +define Device/netgear-wnr3500l-v1
>DEVICE_TITLE := Netgear WNR3500L v1 Other Regions
>DEVICE_PACKAGES := kmod-b43 $(USB2_PACKAGES)
>$(Device/netgear)
>NETGEAR_BOARD_ID := U12H136T99_NETGEAR
>NETGEAR_REGION := 1
>  endef
> -TARGET_DEVICES += netgear-wnr3500l-v1-other-regions
> +TARGET_DEVICES += netgear-wnr3500l-v1
>  
>  define Device/netgear-wnr3500l-v2
>DEVICE_TITLE := Netgear WNR3500L v2
> 



signature.asc
Description: OpenPGP digital signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] Tools prerequisites: should python2 requirement be upgraded to python3?

2017-10-21 Thread txt.file 
In my humble opinion moving to python3 is a good idea. Debian has also
python3 as default since stretch. The bigger question is what will break
by switching to python3.

Hannu Nyman:
> I upgraded my buildhost to new Ubuntu 17.10 and noticed that Ubuntu has
> dropped python 2.7 from the packages installed by default, and only
> python3 is installed. There is no symlink for "python", so LEDE
> prerequisite check fails.
> 
> LEDE prerequisite check looks for Python2:
> 
> https://github.com/lede-project/source/blob/master/include/prereq-build.mk#L141
> 
> 
>  $(eval $(call SetupHostCommand,python,Please install Python 2.x, \
>     python2.7 -V 2>&1 | grep Python, \
>     python2 -V 2>&1 | grep Python, \
>     python -V 2>&1 | grep Python))
> 
> Ubuntu 17.10 does not provide a symlink for plain "python", likely
> because they want to keep users aware that python3 is the version in
> use. So the prerequisite check fails. That will hurt users with build
> systems that are python3-only by default.
> 
> Installing the old python 2.7 naturally helped, but I started to wonder
> if there is a really good reason why LEDE buildhost does not use python3
> and python2 is required?
> 
> rules.mk seems to define python as  PYTHON:=python
> 
> I wonder if that could be enhanced to use python3 if available.
> 
> Of the build tools, "scons" seems to use/check for python2 (in
> tools/scons/files/pywrap.sh ), but based on internet resources, scons
> itself works ok also with python3.
> 
> I have not tested how well the build would go with python symlinked to
> python3, but just wanted raise the issue that some popular Linux distros
> are moving towards python3 now.
> 
> Python2 has EOL set for 2020, so there is still time to move on, but we
> might be ahead of the deadline.
> 
> 
> 
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev



signature.asc
Description: OpenPGP digital signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] update Tor to 0.2.9.11

2017-09-07 Thread txt.file 
Please apply
https://github.com/openwrt/packages/commit/71bd5ac2bf6cd53effe9a78ea17833dedd42a20d
to the "for-17.01" branch, too. I compile tested and runtime tested it
on ramips-mt7628 (VoCore2).

kind regards
txt.file



signature.asc
Description: OpenPGP digital signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] dependency to compile Apache2

2017-05-30 Thread txt.file 
Setting CONFIG_PACKAGE_zlib=y did not resolv the problem. Still the same
error message.

txt.file
--
This message is signed.

Alberto Bursi:
> 
> 
> On 05/22/2017 11:30 PM, Vieno Foo wrote:
>> I tried to compile Apache2 for a VoCore2 (mt7628). Sadly it does not
>> compile but returns an error.
>>
>> "Package apache is missing dependencies for the following libraries:
>> libz.so.1"
>>
>> I attached my lede config file.
>>
>> Kind regards
>> txt.file
>>
> 
> 
> I think that library is in zlib package. From the log it seems zlib is 
> not selected.
> 
> # CONFIG_PACKAGE_zlib is not set
> 
> Try selecting it. If it fixes the issue, add it to the list of dependencies 
> in the apache2 makefile.
> (and send a PR to fix that if it is a package from the repositories)
> 
> -Alberto
> 
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev
> 



signature.asc
Description: OpenPGP digital signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH] ar71xx: change image version for ubiquiti devices

2017-05-16 Thread txt.file 
I have changed the patch to only change the version name. Ubiquiti is
currently at AirMAX firmware version 6.0.4. So version 6.0.0 for us is
IMHO a good/current version number.

I also checked if 0.0.0 would have worked. It resulted in an error on
the device I had.


txt.file
--
This message is signed.

Felix Fietkau:
> On 2017-05-02 10:18, txt.file wrote:
>> Felix Fietkau:
>>>> -  -B $(UBNT_BOARD) -v 
>>>> $(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-OpenWrt-$(REVISION) \
>>>> +  -B $(UBNT_BOARD) -v 
>>>> $(UBNT_TYPE).$(UBNT_CHIP).v0.0.0-$(VERSION_DIST)-$(REVISION) \
>>> The Ubiquiti firmware web interface parses the version number, right?
>>> Did you do any tests to check how it reacts to the 0.0.0 version number?
>> Not yet. Is now on my TODO for this week.
>>
>> txt.file
> I thought about this some more. Even if it works, I'd prefer changing
> the version to match a recent AirOS version. The 0.0.0 just looks weird.
> Also, the version should probably be changed in a separate commit.
> 
> - Felix
> 



signature.asc
Description: OpenPGP digital signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH] ar71xx: change image version for ubiquiti devices

2017-05-02 Thread txt.file 
Not yet. Is now on my TODO for this week.

txt.file

Felix Fietkau:
> On 2017-04-05 23:44, Matthias Fritzsche wrote:
>> changes the image version from hardcoded OpenWrt to
>> $VERSION_DIST. AirOS shows a notification with the image version
>> during a firmware upgrade.
>>
>> fixes #582
>>
>> Signed-off-by: Matthias Fritzsche <txt.f...@txtfile.eu>
>> ---
>>  target/linux/ar71xx/image/ubnt.mk | 6 +++---
>>  1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/target/linux/ar71xx/image/ubnt.mk 
>> b/target/linux/ar71xx/image/ubnt.mk
>> index b203d6a..056dced 100644
>> --- a/target/linux/ar71xx/image/ubnt.mk
>> +++ b/target/linux/ar71xx/image/ubnt.mk
>> @@ -6,7 +6,7 @@
>>  # routerboard creates partitions out of the ubnt header
>>  define Build/mkubntimage
>>  -$(STAGING_DIR_HOST)/bin/mkfwimage \
>> --B $(UBNT_BOARD) -v 
>> $(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-OpenWrt-$(REVISION) \
>> +-B $(UBNT_BOARD) -v 
>> $(UBNT_TYPE).$(UBNT_CHIP).v0.0.0-$(VERSION_DIST)-$(REVISION) \
> The Ubiquiti firmware web interface parses the version number, right?
> Did you do any tests to check how it reacts to the 0.0.0 version number?
> 
> - Felix
> 
> 



signature.asc
Description: OpenPGP digital signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] Planning v17.01.1

2017-04-11 Thread txt.file 
NACK for a RC. For reasons see what Hannu said.



kind regards
txt.file
--
This message is signed.

Hannu Nyman:
> On 9.4.2017 17.14, Jo-Philipp Wich wrote:
>> I'd like to start preparing the v17.01.1 release during the upcoming
>> week with the goal to release final binaries during the easter holidays
>> (~14.04. - 17.04.).
>> ...
>> Also, please reply with a quick ACK / NACK on whether you'd like to see
>> an -RC build before 17.01.1 final.
> 
> 
> The proposed timing for 17.01.1 sounds good.
> 
> NACK for rc.
> I see no need for rc1 as long as there is no last-minute rush to
> backport things on large scale. 17.01 builds have been so stable that
> there should be no major problems.
> 
> 
> 
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev



signature.asc
Description: OpenPGP digital signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH] ar71xx: change image version for ubiquiti devices

2017-03-14 Thread txt.file 
Good point. But if we change it to v7.0.0 now we have the same problem
sooner or later. On TP-Link devices i have often seen v0.0.0-… or similar.

Bill Moffitt:
> I don't know if it makes any difference, but insofar as there is an
> AirOS 6.0 now
> (https://community.ubnt.com/t5/airMAX-Updates-Blog/airOS-6-0-Has-Been-Released/ba-p/1769476)
> should we change the strong to something like "v7.0.0-" etc.?
> 
> 
> On 3/3/2017 7:51 AM, txt.file wrote:
>> changes the image version from hardcoded OpenWrt to
>> $VERSION_DIST. AirOS shows a notification with the image version
>> during a firmware upgrade.
>>
>> fixes #582
>>
>> Signed-off-by: Matthias Fritzsche <txt.f...@txtfile.eu>
>> ---
>>   target/linux/ar71xx/image/ubnt.mk | 6 +++---
>>   1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/target/linux/ar71xx/image/ubnt.mk
>> b/target/linux/ar71xx/image/ubnt.mk
>> index 7a1fc80..c633ca1 100644
>> --- a/target/linux/ar71xx/image/ubnt.mk
>> +++ b/target/linux/ar71xx/image/ubnt.mk
>> @@ -6,7 +6,7 @@
>>   # routerboard creates partitions out of the ubnt header
>>   define Build/mkubntimage
>>  -$(STAGING_DIR_HOST)/bin/mkfwimage \
>> -   -B $(UBNT_BOARD) -v
>> $(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-OpenWrt-$(REVISION) \
>> +   -B $(UBNT_BOARD) -v
>> $(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-$(VERSION_DIST)-$(REVISION) \
>>  -k $(IMAGE_KERNEL) \
>>  -r $@ \
>>  -o $@
>> @@ -19,7 +19,7 @@ define Build/mkubntimage-split
>>  dd if=$@ of=$@.old1 bs=1024k count=1; \
>>  dd if=$@ of=$@.old2 bs=1024k skip=1; \
>>  $(STAGING_DIR_HOST)/bin/mkfwimage \
>> -   -B $(UBNT_BOARD) -v
>> $(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-OpenWrt-$(REVISION) \
>> +   -B $(UBNT_BOARD) -v
>> $(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-$(VERSION_DIST)-$(REVISION) \
>>  -k $@.old1 \
>>  -r $@.old2 \
>>  -o $@; \
>> @@ -28,7 +28,7 @@ endef
>> define Build/mkubntimage2
>>  -$(STAGING_DIR_HOST)/bin/mkfwimage2 -f 0x9f00 \
>> -   -v $(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-OpenWrt-$(REVISION) \
>> +   -v
>> $(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-$(VERSION_DIST)-$(REVISION) \
>>  -p jffs2:0x5:0xf6:0:0:$@ \
>>  -o $@.new
>>  @mv $@.new $@
> 
> 
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev



signature.asc
Description: OpenPGP digital signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH] ar71xx: change image version for ubiquiti devices

2017-03-03 Thread txt.file 
changes the image version from hardcoded OpenWrt to
$VERSION_DIST. AirOS shows a notification with the image version
during a firmware upgrade.

fixes #582

Signed-off-by: Matthias Fritzsche 
---
 target/linux/ar71xx/image/ubnt.mk | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/target/linux/ar71xx/image/ubnt.mk 
b/target/linux/ar71xx/image/ubnt.mk
index 7a1fc80..c633ca1 100644
--- a/target/linux/ar71xx/image/ubnt.mk
+++ b/target/linux/ar71xx/image/ubnt.mk
@@ -6,7 +6,7 @@
 # routerboard creates partitions out of the ubnt header
 define Build/mkubntimage
-$(STAGING_DIR_HOST)/bin/mkfwimage \
-   -B $(UBNT_BOARD) -v 
$(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-OpenWrt-$(REVISION) \
+   -B $(UBNT_BOARD) -v 
$(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-$(VERSION_DIST)-$(REVISION) \
-k $(IMAGE_KERNEL) \
-r $@ \
-o $@
@@ -19,7 +19,7 @@ define Build/mkubntimage-split
dd if=$@ of=$@.old1 bs=1024k count=1; \
dd if=$@ of=$@.old2 bs=1024k skip=1; \
$(STAGING_DIR_HOST)/bin/mkfwimage \
-   -B $(UBNT_BOARD) -v 
$(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-OpenWrt-$(REVISION) \
+   -B $(UBNT_BOARD) -v 
$(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-$(VERSION_DIST)-$(REVISION) \
-k $@.old1 \
-r $@.old2 \
-o $@; \
@@ -28,7 +28,7 @@ endef
 
 define Build/mkubntimage2
-$(STAGING_DIR_HOST)/bin/mkfwimage2 -f 0x9f00 \
-   -v $(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-OpenWrt-$(REVISION) \
+   -v $(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-$(VERSION_DIST)-$(REVISION) 
\
-p jffs2:0x5:0xf6:0:0:$@ \
-o $@.new
@mv $@.new $@
-- 
2.1.4

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [PATCH] ar71xx: change image version to LEDE for ubiquiti devices

2017-03-03 Thread txt.file 
ar71xx: change image version to LEDE for ubiquiti devices

Signed-off-by: txt.file <txt.f...@txtfile.eu>
---
 target/linux/ar71xx/image/ubnt.mk | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/target/linux/ar71xx/image/ubnt.mk 
b/target/linux/ar71xx/image/ubnt.mk
index 7a1fc80..cf6a70c 100644
--- a/target/linux/ar71xx/image/ubnt.mk
+++ b/target/linux/ar71xx/image/ubnt.mk
@@ -6,7 +6,7 @@
 # routerboard creates partitions out of the ubnt header
 define Build/mkubntimage
-$(STAGING_DIR_HOST)/bin/mkfwimage \
-   -B $(UBNT_BOARD) -v 
$(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-OpenWrt-$(REVISION) \
+   -B $(UBNT_BOARD) -v 
$(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-LEDE-$(REVISION) \
-k $(IMAGE_KERNEL) \
-r $@ \
-o $@
@@ -19,7 +19,7 @@ define Build/mkubntimage-split
dd if=$@ of=$@.old1 bs=1024k count=1; \
dd if=$@ of=$@.old2 bs=1024k skip=1; \
$(STAGING_DIR_HOST)/bin/mkfwimage \
-   -B $(UBNT_BOARD) -v 
$(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-OpenWrt-$(REVISION) \
+   -B $(UBNT_BOARD) -v 
$(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-LEDE-$(REVISION) \
-k $@.old1 \
-r $@.old2 \
-o $@; \
@@ -28,7 +28,7 @@ endef
 
 define Build/mkubntimage2
-$(STAGING_DIR_HOST)/bin/mkfwimage2 -f 0x9f00 \
-   -v $(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-OpenWrt-$(REVISION) \
+   -v $(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-LEDE-$(REVISION) \
-p jffs2:0x5:0xf6:0:0:$@ \
-o $@.new
@mv $@.new $@
-- 
2.1.4

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] server resources

2016-05-13 Thread txt.file 
Hey folks

At the battlemesh it was asked if somebody can provide server resources.
I have one physical server which currently does only minor tasks.

Details:
* Intel Atom N2800 (3 cores unused)
* 2GB RAM (~1GB unused)
* up to 300 GB HDD
* officially 100MBit/s
* it runs currently a Tor node (guard, middle), two small web sites for
me and I use it as build server for my own openWRT/libreCMC/gluon/lede
images

I am doing Freifunk in Chemnitz and use (now) LEDE personally. I would
love to give something back to the community. You all do a great job and
I am very thankful.

kind regards
txt.file
-- 
This email is digitally signed.



signature.asc
Description: OpenPGP digital signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev