Re: [PATCH master,23.05] ramips: fix ZyXEL NR7101 bricking typo

[edgar . soldin]

On 15.10.2023 21:59, Paul D wrote:

This needs to be applied to 23.05 and master ASAP.  It is already
bricking devices.


how about quickly
 removing the erroneous image from 
https://downloads.openwrt.org/releases/23.05.0/
plus
 adding a prominent red NOTE on https://openwrt.org/toh/zyxel/nr7101 not to 
flash 23.05
?

preventing head aches is the best way to treat 'em ..ede

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: Override MAC address for interface?

[edgar . soldin]

On 23.02.2023 13:49, Peter Naulls wrote:

On 2/23/23 01:43, Rafał Miłecki wrote:

On 22.02.2023 21:02, Peter Naulls wrote:





config device
 option 'lan1'


This line is clearly wrong. See how you specify device name in above section.


Perhaps it is "clear" but there's much in OpenWrt that isn't obvious up front,
until you know, and then it is. But thanks for the correction.

However, what I really want to do is this:


config interface 'wan'
     option auto '0'
     option proto 'dhcp'
     #option device 'wan'
     option name 'wan'
     option metric '0'

config device 'wan'
     option name 'wan'
     option macaddr '34:BA:9A:CC:DD:BB'

But uci doesn't allow this. I guess I'll have to rename the wan device in the 
DTS to wan0 or something.


this is how it worked in 21.x , can't try on 22.x just now
 
https://forum.openwrt.org/t/solved-how-to-clone-mac-address-for-21-02-0/108690/3

..ede

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: sysupgrade broken on imx nand targets (and maybe others too)

[edgar . soldin]

On 24.01.2023 17:13, Lanchon wrote:

the problem lies elsewhere: on your platform something is rebooting the system 
asynchronously while it is updating. this is very dangerous and must be fixed 
elsewhere in code.


just a wild guess. faulty power supplies sometimes lead to reboots if the power 
supplied does not suffice. maybe a direction to investigate? ..sunny regards ede

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [PATCH v2 6/7] coreutils: Import from packages feed

[edgar . soldin]

On 08.01.2023 00:02, Thibaut wrote:




Le 7 janv. 2023 à 22:41, Robert Marko  a écrit :

On Sat, 7 Jan 2023 at 16:26, Thibaut VARÈNE  wrote:





Le 7 janv. 2023 à 15:06, Christian Marangi  a écrit :

On Fri, Jan 06, 2023 at 11:49:44PM -0800, Brian Norris wrote:

I need to express a per-target dependency on the 'base64' utility, and
that's seemingly impossible to do for busybox. Pull in coreutils to make
that easier.

Signed-off-by: Brian Norris 


We still need to think of a correct solution for this... coreutils is an
option but wonder if a better one is openssl... Actually we have a small
tool to handle specific decryption of some stuff... Wonder if that can
be expanded for this task and just use wolfssl or openssl api to decode
base64 stuff?


Using one or the other would impose (i.e. (en)force) that SSL library on this 
particular target. Do we want this, especially considering the ongoing 
conversation about mbedTLS?

Also pulling an entire SSL implementation just to decode base64 seems a tad 
overkill too.


I agree on this one, forcing usage of OpenSSL isn't ideal, coreutils
is a better option for sure.


There might be an even easier/lighter way (short of enabling base64 in 
busybox), AWK to the rescue:
https://github.com/shane-kerr/AWK-base64decode

The code is clean and judging by the comment line 97, works with busybox awk.


how is luci doing base64 en/decoding? that should be available in default 
images. if it's using lua, that should be available in every image even without 
web-interface or?

..ede

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [sdwalker/sdwalker.github.io] 2bdb42: This week's update

[edgar . soldin]

is the below weekly message of any informational value to _all_? can someone 
maybe block this if it's not? ..thanks ede

On 08.05.2022 23:05, Stephen Walker via openwrt-devel wrote:

The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.

To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [PATCH 2/4] base-files/functions.sh: do not iterate over ls

[edgar . soldin]

On 20.09.2020 07:31, Rosen Penev wrote:
> - for file in $(ls $1/*.sh 2>/dev/null); do
> - . $file
> + for file in "$1"/*.sh; do
> + [ -e "$file" ] || break
> + . "$file"

the existence check is probably meant to catch "../*.sh" entry found if no 
files match. as files will likely not vanish during the loop this will probably 
work.
still it'll break the loop completely without any need. using 'continue' 
instead of 'break' would not break the loop and be safer here.

..ede

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] time for OJ 1.15 everyone?

[edgar . soldin]

new year, new OJ.

start of the year is OJ release time traditionally by now. are we in agreement?

a snappy new NY to one and all ..ede

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [JPP-Devel] Fwd: SVN: [6214] core/trunk

[edgar . soldin]

On 06.01.2020 12:37, Michaël Michaud wrote:
> Hi Ede,
>
> I did a quick try and it seems to work fine.
> Seems that the change you did is rather big. I'll try to go deeper into your 
> change to try to understand.

go ahead :)

> What about the SO remark 
> (https://stackoverflow.com/questions/1884230/httpurlconnection-doesnt-follow-redirect-from-http-to-https)
> Did you decide to follow the link anyway without warning ?

as current browsers follow redirects regardless as well, i assume that it's 
established and expected behaviour.

> Indeed, I did not understand what the problem is exactly, and it's OK for me 
> to go on. Just want to know your idea about the SO warning.

personally feel that warning on every redirect is overengineering. securitywise 
it might make sense to warn on leaving the host or switching from https though. 
alas i'm lacking the time to implement it.

..ede

> Michaël
>
> Le 04/01/2020 à 20:00, edgar.sol...@web.de a écrit :
>> Mike,
>>
>> could you please check the fix and close the ticket if it works as 
>> expected?.. thanks ede
>>
>>
>>  Forwarded Message 
>> Subject: [JPP-Devel] SVN: [6214] core/trunk
>> Date: Sat, 04 Jan 2020 18:58:23 +
>> From: jump-pilot-svn--- via Jump-pilot-devel 
>> 
>> Reply-To: OpenJump develop and use 
>> To: jump-pilot-de...@lists.sourceforge.net
>> CC: jump-pilot-...@lists.sourceforge.net
>>
>> Revision: 6214
>>    http://sourceforge.net/p/jump-pilot/code/6214
>> Author:   edso
>> Date: 2020-01-04 18:58:23 + (Sat, 04 Jan 2020)
>> Log Message:
>> ---
>> bugfix #489 "Veneto Region (Italy) WMS service does not work on OpenJump"
>> wms now follows http redirections by default
>> also
>> some better error handling/reporting
>> Edit WMS resets connection now on manual url editing
>>
>> Modified Paths:
>> --
>>  core/trunk/ChangeLog
>>  
>> core/trunk/src/com/vividsolutions/jump/workbench/ui/plugin/wms/EditWMSQueryPanel.java
>>  
>> core/trunk/src/com/vividsolutions/jump/workbench/ui/plugin/wms/MapLayerPanel.java
>>  core/trunk/src/com/vividsolutions/wms/AbstractWMSRequest.java
>>  core/trunk/src/com/vividsolutions/wms/BasicRequest.java
>>  core/trunk/src/com/vividsolutions/wms/FeatureInfoRequest.java
>>  core/trunk/src/com/vividsolutions/wms/MapRequest.java
>>  core/trunk/src/com/vividsolutions/wms/WMService.java
>>  core/trunk/src/org/openjump/util/URLConnectionProvider.java
>>
>> Modified: core/trunk/ChangeLog
>> ===
>> --- core/trunk/ChangeLog    2020-01-01 09:21:44 UTC (rev 6213)
>> +++ core/trunk/ChangeLog    2020-01-04 18:58:23 UTC (rev 6214)
>> @@ -3,6 +3,10 @@
>>   # 2. make sure that lines break at 80 chars for constricted display 
>> situations
>>   #< 80 chars 
>> -->#
>>
>> +2020-01-04 ede
>> +  * bugfix #489 "Veneto Region (Italy) WMS service does not work on 
>> OpenJump"
>> +    wms now follows http redirections by default
>> +
>>   2020-01-01 mmichaud 
>>     * Clean and improve ExtractLayersByAttribute
>>     * Implements FR #262 : copy info to clipboard (patch from Rashad)
>>
>> Modified: 
>> core/trunk/src/com/vividsolutions/jump/workbench/ui/plugin/wms/EditWMSQueryPanel.java
>> ===
>> --- 
>> core/trunk/src/com/vividsolutions/jump/workbench/ui/plugin/wms/EditWMSQueryPanel.java
>>     2020-01-01 09:21:44 UTC (rev 6213)
>> +++ 
>> core/trunk/src/com/vividsolutions/jump/workbench/ui/plugin/wms/EditWMSQueryPanel.java
>>     2020-01-04 18:58:23 UTC (rev 6214)
>> @@ -57,6 +57,7 @@
>>   import javax.swing.border.Border;
>>   import javax.swing.event.DocumentEvent;
>>   import javax.swing.event.DocumentListener;
>> +import javax.swing.text.JTextComponent;
>>
>>   import org.apache.commons.lang3.ArrayUtils;
>>   import org.openjump.core.ui.plugin.wms.AddWmsLayerWizard;
>> @@ -63,6 +64,7 @@
>>   import org.openjump.util.UriUtil;
>>
>>   import com.vividsolutions.jump.I18N;
>> +import com.vividsolutions.jump.workbench.JUMPWorkbench;
>>   import com.vividsolutions.jump.workbench.model.WMSLayer;
>>   import com.vividsolutions.jump.workbench.plugin.EnableCheck;
>>   import com.vividsolutions.jump.workbench.ui.InputChangedListener;
>> @@ -303,7 +305,6 @@
>>     private void reset(DocumentEvent e) {
>>   System.out.println(e);
>>   resetConnection();
>> -    ;
>>     }
>>   };
>>
>> @@ -329,13 +330,19 @@
>>   SwingUtilities.invokeLater(new Runnable() {
>>     public void run() {
>>   for (final Component c : cs) {
>> -  // System.out.println(c);
>> +  //System.out.println(c);
>>     if (c instanceof AbstractButton)
>>   ((AbstractButton) c).addActionListener(ali);
>>     else if (c instanceof JTextField)
>>   ((JTextField) c).getDocument().addDocumentListener(doli);
>> - 

[OpenWrt-Devel] test

[Edgar Soldin]

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH v1 1/1] openssh: disable passwords for openssh server

[edgar . soldin]

hey All,

On 2/15/2018 20:50, Magnus Kroken wrote:
>>> This is just about the default configuration, it's not a choice between 
>>> conflicting compile time options with varying security implications. While 
>>> key authentication may be best practice, allowing SSH password logins isn't 
>>> on the level of reimplementing LuCI in PHP 4. The change is *literally* a 
>>> handful of sed commands, why can't advanced users take care of that 
>>> themselves? Why do we want to make it easier to build a soft-bricking image 
>>> than it is today?
>>
>>
>> Conversely, why can’t advanced users have a clear, standardized way of doing 
>> this?  That they’re “advanced” doesn’t mean they don’t also appreciate 
>> convenience, an easy way to save and export/import configurations, etc.
> 
> I'm not against general development, improvement or standardization of config 
> handling. I'm against the default state of the patch that started this mail 
> thread. The convenience of this patch opens up a new way to break the 
> convenience of failsafe on a lot of devices, and I don't think many people 
> would expect the particular package selection to cause such a behavior. I 
> consider failsafe to be more important. You've already addressed that in your 
> pull request, and I'm in favor of "this should be configurable at build time, 
> but the default behavior should not change". How that is implemented is a 
> different matter, which so far I haven't thought much about.

i am following this PR since the start and hold the same reservations. how 
about a menuconfig option that allows you to activate this feature and allows 
to define a path to an 'authorized_keys' file.
implemented for all sshd packages this would squash all requirements into one 
solution, or not?

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] international keyboard layout support

[edgar . soldin]

hey All,

while tinkering with Gluon the Openwrt based Freifunk firmware (currently on 
CC) on a x86 based thin client box i needed support for a german keyboard 
layout. i managed to realize that manually as i didn't find any prepared 
packages for this purpose.

is there any interest in a keyboardmaps package, holding busybox compatible 
binary kmaps and activating the needed busybox utilities? i imagine some 
devs/users especially on platforms with proper keyboard interfaces (usb/ps2) 
would appreciate that.

thanks ..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] uclient-fetch & SSL WAS:Re: DD: CONFIG_BUSYBOX_DEFAULT_WGET is not set

[edgar . soldin]

thx John! neat.. that should do the trick. finally a small ssl capable wget, 
jippee! ..ede

On 22.01.2016 22:32, John Clark wrote:
> There is a symbolic link:
> 
> lrwxrwxrwx1 root root13 Jan 22 20:04 wget -> 
> uclient-fetch*
> 
> 
> On 1/22/16 4:29 PM, edgar.sol...@web.de wrote:
>> On 22.01.2016 16:20, Felix Fietkau wrote:
>>> On 2016-01-22 16:03, edgar.sol...@web.de wrote:
 On 22.01.2016 14:32, Weedy wrote:
>> Question: The busybox binary (for me) goes from 366,401 bytes to 300,327
> with the removal of wget from it.  Therefore, the uclient-fetch binary
> swapout causes a 46,379 byte increase in size. I assume the desire to move
> to uclient-fetch from busybox is for the SSL support?  If so, it still 
> does
> not support SSL without also building ustream-ssl.
 yeah. an ssl capable wget (whatever it's called) out of the box would be 
 greatly appreciated.

 @Felix: is that on the table?
>>> It's already done. With uclient-fetch, you can simply install any
>>> ustream-ssl variant (along with ca-certificates if you want to have
>>> proper validation), and it'll immediately be SSL capable. That was my
>>> main motivation behind replacing wget with ustream-ssl.
>>>
>>> The aforementioned size increase is probably either a bug or a
>>> measurement error (see my other mail regarding that subject).
>>>
>> nice! is there a possibility to create a wget wrapper? i assume not everyone 
>> is familiar with uclient-fetch, so at least a stub noting to use 
>> uclient-fetch might probably help when users are confused that wget isn't 
>> there.
>>
>> ..ede
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> 
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] uclient-fetch & SSL WAS:Re: DD: CONFIG_BUSYBOX_DEFAULT_WGET is not set

[edgar . soldin]

On 22.01.2016 16:20, Felix Fietkau wrote:
> On 2016-01-22 16:03, edgar.sol...@web.de wrote:
>> On 22.01.2016 14:32, Weedy wrote:
 Question: The busybox binary (for me) goes from 366,401 bytes to 300,327
>>> with the removal of wget from it.  Therefore, the uclient-fetch binary
>>> swapout causes a 46,379 byte increase in size. I assume the desire to move
>>> to uclient-fetch from busybox is for the SSL support?  If so, it still does
>>> not support SSL without also building ustream-ssl.
>>
>> yeah. an ssl capable wget (whatever it's called) out of the box would be 
>> greatly appreciated.
>>
>> @Felix: is that on the table?
> It's already done. With uclient-fetch, you can simply install any
> ustream-ssl variant (along with ca-certificates if you want to have
> proper validation), and it'll immediately be SSL capable. That was my
> main motivation behind replacing wget with ustream-ssl.
> 
> The aforementioned size increase is probably either a bug or a
> measurement error (see my other mail regarding that subject).
> 

nice! is there a possibility to create a wget wrapper? i assume not everyone is 
familiar with uclient-fetch, so at least a stub noting to use uclient-fetch 
might probably help when users are confused that wget isn't there.

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] uclient-fetch & SSL WAS:Re: DD: CONFIG_BUSYBOX_DEFAULT_WGET is not set

[edgar . soldin]

On 22.01.2016 14:32, Weedy wrote:
>> Question: The busybox binary (for me) goes from 366,401 bytes to 300,327
> with the removal of wget from it.  Therefore, the uclient-fetch binary
> swapout causes a 46,379 byte increase in size. I assume the desire to move
> to uclient-fetch from busybox is for the SSL support?  If so, it still does
> not support SSL without also building ustream-ssl.

yeah. an ssl capable wget (whatever it's called) out of the box would be 
greatly appreciated.

@Felix: is that on the table?

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] SVN to GIT transition / paid patch-checking

[edgar . soldin]

On 13.10.2015 12:44, Imre Kaloz wrote:
> On Tue, 13 Oct 2015 12:33:35 +0200, Bastian Bittorf
>  wrote:
> 
> 
> 
>> It should be easy possible to get funding from all the companies which
>> work with OpenWrt. Is this in option?
> 
> Not until we have a nonprofit organization as companies can't have tax 
> deduction in exchange.. This is pretty much the main issue people from said 
> companies brought up at the summit as well.
> 
> 

how about said companies simply employ(part time even)/pay core devs for 
working on openwrt? 

if they really want to give back tax deductability shouldn't be an issue. there 
are costs of business that are not deductible. why should openwrt people be 
forced into forming/maintaining organizational infrastructure, when they could 
spend that time enhancing openwrt instead.

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Renaming trunk to Dxx Dxx ? Or seperate name for Trunk?

[edgar . soldin]

How about Trusty Trunk.. no cocktail though.. so far.. ede


On 10.09.2015 22:08, Tobias Welz wrote:
> Just following up with the T... T... idea - I found some T T Cocktails:
> 
> Tahitian Tea
> Tahitian Treat
> Tanqueray Tonic
> Tanzanian Tonic
> 
> 
> 
> Am 09.09.2015 um 19:57 schrieb Hannu Nyman:
>> Tobias Welz wrote at Wed Sep 9 17:24:14 CEST 2015:
>> > So I absolutely vote for some clear consistent naming of the trunk and 
>> > seperate names for the releases. (What about some Cocktail with a letter 
>> > from the end of the alphabet like Z Z or X X in case there 
>> > exists one)
>>
>> On that idea, the possible permanent name for the trunk could be something 
>> Txx Trunk. There are over 20 releases until TT is reached, so not for soon. 
>> I didn't find any really suitable drink names, but below are some ideas:
>> Trekking Trunk
>> Tasty Trunk
>> Tricky Trunk
>> Tempting Trunk
>> Twisty Trunk
>> Trunk Thrill
>> Thrilling Trunk
>>
>> But until that, renaming trunk to something Dxxx Dxxx would be enough to 
>> decrease confusion.
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> 
> 
> 
> 
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> 
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH v4] base-files: add /etc/profile.d support

[edgar . soldin]

On 04.09.2015 13:55, Karl Palsson wrote:
> Jo-Philipp Wich  wrote:
>> Hi.
> 
>>> Why the -e?  You only got existing files in the glob above right? 
> 
>> Almost. If the directory does not exist or is empty then the glob
>> pattern is returned literally, e.g. "echo /tmp/*" will expand to a list
>> of files but "echo /does_not_exist/*" will return "/does_not_exist/*"
>> literaly so the for-in loop will run once with the literal glob pattern
>> as argument, therefore the "-e" test is required.
> 
> So let's -d test the directory instead of -e testing every file just in
> case the directory didn't exist?
> 

On 04.09.2015 13:55, Karl Palsson wrote:
> Jo-Philipp Wich  wrote:
>> Hi.
>
>>> Why the -e? You only got existing files in the glob above right?
>
>> Almost. If the directory does not exist or is empty then the glob
>> pattern is returned literally, e.g. "echo /tmp/*" will expand to a list
>> of files but "echo /does_not_exist/*" will return "/does_not_exist/*"
>> literaly so the for-in loop will run once with the literal glob pattern
>> as argument, therefore the "-e" test is required.
>
> So let's -d test the directory instead of -e testing every file just in
> case the directory didn't exist?
>

http://mywiki.wooledge.org/BashPitfalls#for_i_in_.24.28ls_.2A.mp3.29
also explains why you need to test the availability of the found file. 
essentially shell globbing will return *.sh if no match is found. to circumvent 
that case you need test -e.

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH v4] base-files: add /etc/profile.d support

[edgar . soldin]

On 04.09.2015 12:36, Bastian Bittorf wrote:
> * edgar.sol...@web.de  [04.09.2015 12:30]:
>> note from a bystander. this looks wrong - path/file names containing spaces 
>> will be delimited by for. probably better use
>
> for the sent patch this works:
>
> root@box:~ touch "A 1"
> root@box:~ touch "A 2"
> root@box:~ for FILE in A*; do ls -l "$FILE"; done
> -rw-r--r-- 1 root root 0 Sep 4 12:22 A 1
> -rw-r--r-- 1 root root 0 Sep 4 12:22 A 2
>

right your patch is fine. this was wrt. karlp's example code that resides in 
functions.sh include() function.

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH v4] base-files: add /etc/profile.d support

[edgar . soldin]

On 04.09.2015 11:51, karlp wrote:
> include() {  
> local file 
> 
> for file in $(ls $1/*.sh 2>/dev/null); do 
> . $file  
> done 
> } 

note from a bystander. this looks wrong - path/file names containing spaces 
will be delimited by for. probably better use

for i in "$1/*.sh"; do
[ -e "$i" ] || continue
some command "$i"
done

as explained on
 http://mywiki.wooledge.org/BashPitfalls#for_i_in_.24.28ls_.2A.mp3.29

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] Combine CA-certificates in one file

[edgar . soldin]

On 12.06.2015 21:20, micke.p...@telldus.se wrote:> 2015-06-12 09:39 skrev 
Cristian Morales Vega:
> 
>> On 12 June 2015 at 08:30,  wrote:
>>
>>> Some packages or libraries cannot use split ca cetificates in a folder.
>>> This adds a config to combine all certificates into one file.
>>
>> I have nothing against this patch. But do you have a list of such
>> packages? I may be interested in patching them.
> 
> In python 2.7.9 there is a new class SSLContext that can load the system 
> certificates. This was not available previously. OpenWRT currently ships 
> 2.7.10. I have modified our code to use this instead.
> 
> My patch can be discarded, I think.

devices are getting bigger and your patch offers additional functionality. i'd 
vote to keep it, as it does not hurt (disabled by default) but may be useful to 
others.

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] wrong configured spam-filter for openwrt-dev

[edgar . soldin]

On 30.04.2015 12:48, Bastian Bittorf wrote:
> while sending a mail to openwrt-dev,
> i got this answer, which doesnt make any sense,
> because the list only accepts "registered" users anyway:
> 
> : host mail.openwrt.org[78.24.191.176]
> said: 554 5.7.1 Service unavailable; Client host [176.9.57.138] blocked
> using bl.spamcop.net; Blocked - see 
> http://www.spamcop.net/bl.shtml?176.9.57.138
> (in reply to RCPT TO command)
> 
> so: first check, if the user is 'registered', if not ask do spamchecking.
> who feels responsible for that?
> 

inconvenient, true. but comprehensible as email has no sender verification, so 
anybody could write an email to the list and use your address in the FROM: 
field.

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Dark Destroyer

[edgar . soldin]

On 08.04.2015 00:45, David Lang wrote:
> On Wed, 8 Apr 2015, Peter Lawler wrote:
> 
>> On 08/04/15 05:47, Hartmut Knaack wrote:
>>
>>> Give your +1 answer on this mail if you prefer "Dark Destroyer".
>> How does that even work? You're not giving an option to vote for
>> anything else.
> 
> There are three different subthreads, each looking for answers on that thread

right.. ignore my previous mail wrt. given choices ..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Dark Destroyer

[edgar . soldin]

On 08.04.2015 00:33, Peter Lawler wrote:
> On 08/04/15 05:47, Hartmut Knaack wrote:
> 
>> Give your +1 answer on this mail if you prefer "Dark Destroyer".
> How does that even work? You're not giving an option to vote for
> anything else.
> 

simply write your vote in the subject and have a mail body that says '+1', 
easy. if you are following the list you should know the options by now. 
if you want to introduce a new one, speak up and don't forget to point it out 
to Hartmut, so he doesn't miss it on counting.

i am really wondering if the core devs are following this or even give a damn. 
didn't read anything after John's last mail declaring Dirty Diamond the winner. 
Felix, John, anybody?

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Designated Driver

[edgar . soldin]

hmm.. seems like all doodle polls, incl. the original one suffer from this 
weakness. hereby i declare defeat and hope you Hartmut will count the votes 
properly, manually as seems necessary.

+1 for Designated Driver

..ede

PS: i will deactivate the flawed doodle poll now

> On Tue, Apr 7, 2015 at 12:47 PM, Hartmut Knaack  wrote:
> 
>> That Doodle poll turned out to be spamed/trolled, and everyone could even
>> change or delete other votes. Since this was just communicated over this
>> mailing list, and subscribers are at least basically verified, why not
>> have a
>> good old fashioned poll?
>>
>> Give your +1 answer on this mail if you prefer "Designated Driver".
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>>
> 
> 
> 
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> 
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] OpenWrt DD release name v2

[edgar . soldin]

ok, took the freedom to set up another vote, incl. the third option. let's see 
what the numbers say in a few days. 
http://doodle.com/9d262b569bh4r7kv

it'd make sense that everybody retakes the vote to have the truest election 
result.

regards ..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] OpenWrt release name

[edgar . soldin]

On 06.04.2015 09:35, John Crispin wrote:
> i think we have a winner with 96 vs 50 votes.
> 
>> == Dirty Diamond ==
>> 2 cl Rum
>> 2 cl Vodka
>> 2 cl Tequila Silver
>> 2 cl Campari
>> 2 cl Curaçao Blue
>> 2 cl Lime syrup
>> 2 1/2 cl Orange juice
>>  Coca Cola


i also liked 

== Designated Driver ==
1 part cranberry juice cocktail
1 part grapefruit juice
1 part orange juice
1 part pineapple juice

, which would also be a nice pun on router functionality. 
is it really to late to consider this additional entry?

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] [packages] dnsmasq: add option --quiet-dhcp

[edgar . soldin]

On 07.01.2015 23:50, Lars Kruse wrote:
> 
> The --quiet-dhcp setting increases privacy by omitting DHCP lease logs
> including MAC addresses.
> 
> Signed-off-by: Lars Kruse 
> 
> --- a/package/network/services/dnsmasq/files/dnsmasq.init
> +++ b/package/network/services/dnsmasq/files/dnsmasq.init
> @@ -123,6 +123,7 @@ dnsmasq() {
>   append_bool "$cfg" nonwildcard "--bind-interfaces"
>   append_bool "$cfg" fqdn "--dhcp-fqdn"
>   append_bool "$cfg" proxydnssec "--proxy-dnssec"
> + append_bool "$cfg" quiet_dhcp "--quiet-dhcp"
>  
>   append_parm "$cfg" dhcpscript "--dhcp-script"
>   append_parm "$cfg" cachesize "--cache-size"

would make sense to use 'quietdhcp' instead of 'quiet_dhcp', as the other 
options seem to ommit the dashes too.

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Help, how to troubleshoot openwrt crash(reboot)

[edgar . soldin]

On 11.10.2014 20:40, document wrote:
> hi,
> 
> how to troubleshoot openwrt crash(reboot) ?
> 
> i have openvpn-2.3.2 installed from opkg but when i manually start it about 
> 1min passed, router (openwrt-12.09) will reboot.
> 
> when i enabled openvpn service on startup, router will auto reboot forever.
> 
> i have a little linux skill, but output of logread at openwrt-12.09 will not 
> help and will be empty when there is a new boot.
> 
> even both openvpn client (my router) and server (linux vps) debug level logs 
> not help.
> 
> the same configure files for client on both other platform like windows7 
> (home) and fedora20 (office) work normally.
> 
> all packages from opkg at tp-link wr703n.
> 
> --- may be useless above, blah blah...
> 
> Any ideas of how to troubleshoot normal software or process booboo on 
> openwrt-12.09 ?
> 
> update: i update firmware to openwrt-14.09, router get the same issure.
> 

try 
http://wiki.openwrt.org/doc/howto/generic.failsafe

disable openvpn auto start up. try to start it manually after the box booted up 
normally.

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH 0/4] dnsmasq: DNSSEC support

[edgar . soldin]

On 16.06.2014 11:56, Nikos Mavrogiannopoulos wrote:
> On Mon, Jun 16, 2014 at 10:53 AM,   wrote:
>>> On the contrary I'd prefer if it doesn't. Nettle is an open project
>>> under LGPL that anyone can contribute and can be reused by a variety
>>> of software; polarssl is closed commercial project under a commercial
>>> license with a GPLv2 exception.
>> according to
>>  https://polarssl.org/how-to-get
>> you can use the polarssl library properly under copyleft GPL2. if they offer 
>> additional licenses does not matter.
> 
> That's what I already mentioned. The difference with open-source
> software is the missing "how to contribute page" (I consider the
> presence of a developer community a vital part of being open source).
> Otherwise, tomorrow you could be left with a GPLv2 codebase that is
> outdated an unmaintained if the X company desires that the GPLv2
> codebase they release is no longer a good marketing approach.
> Another risk is to wait for years (or eternity) to get features that
> paying customers get (see matrixssl).
> 

well, i guess our open-source definition differs here ;) i tend to use the 
definition of the open source initiative
 http://opensource.org/osd

understandably you'd prefer maintained code. but in reality even big oss 
projects die or are split up or forked or, or, or.. so what is left is that you 
can take a past and current maintenance status as a variable in your decision 
making only, no more, no less.

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH 0/4] dnsmasq: DNSSEC support

[edgar . soldin]

On 16.06.2014 10:40, Nikos Mavrogiannopoulos wrote:
> On Mon, Jun 16, 2014 at 10:31 AM, Steven Barth  wrote:
>> > Hi Nikos,
>> > Is there a reason for not having dnssec by default? If there is a way
>> > to disable it, I believe it will only be beneficial to have it in.
>> > The main problem here is that this increase the default image size
>> > significantly plus we can't even reuse all the added crypto code because
>> > none of the core or important services use nettle. It would be nice to see
>> > dnsmasq interacting with a more mainstream embedded crypto library like
>> > polarssl or so.
> On the contrary I'd prefer if it doesn't. Nettle is an open project
> under LGPL that anyone can contribute and can be reused by a variety
> of software; polarssl is closed commercial project under a commercial
> license with a GPLv2 exception.
> 

according to 
 https://polarssl.org/how-to-get

you can use the polarssl library properly under copyleft GPL2. if they offer 
additional licenses does not matter.

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] how to set busybox's some options now ?

[edgar . soldin]

On 17.12.2013 16:14, Yousong Zhou wrote:
> On 17 December 2013 22:13, openwrt-de...@couprie.net
>  wrote:
>> Hi yousong,
>>
>> Can you give a example how to call menuconfig for busybox ?
> 
> I am doing menuconfig for busybox in OpenWrt build environment in
> which busybox tarball has already been extracted. Your situation may
> vary. Busybox itself provide menuconfig just like those for
> OpenWrt/Buildroot/Kernel.
> 
> $ make -C build_dir/target-mips_34kc_uClibc-0.9.33.2/busybox-1.19.4/
> menuconfig
> 
> Does it deserve a "busybox_menuconfig" just like "kernel_menuconfig"?

there should be at least one graphical way. so either busybox's menu_config or 
at least the old options presumably missing currently in trunk's menu_config.

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Question on UCI Lua license

[edgar . soldin]

On 13.08.2013 21:54, Jeff Remy wrote:
> Hi,
> I have a question regarding the UCI Lua bindings license.
> libuci itself is LGPLv2.1, the cli utility is GPLv2 and the Lua
> bindings are GPLv2.
> I was wondering if this was on purpose?
> It does not seem to be in line with the library but again, there might
> be other reasons.

i am not associated to the UCI authors/project. so i cannot tell you why they 
did it.

however, usually licensing like this is done because GPL is restrictive when it 
comes to linking. see
http://en.wikipedia.org/wiki/GNU_General_Public_License#Linking_and_derived_works

because of that lots of projects choose to provide libraries on LGPL or other 
licenses that do not enforce an OS license on the code the library is linked 
against to make the library more attractive for commercial usage. other 
components that do not need to be linked stay under GPL though.

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Iozone openwrt package

[edgar . soldin]

On 31.05.2013 13:48, devendra.aaru wrote:
> On Fri, May 31, 2013 at 5:18 PM, Bastian Bittorf  
> wrote:
>> * devendra.aaru  [31.05.2013 13:44]:
>>> The patch i generated spans upto 1M as since it contains the source
>>> code of iozone and i bit modified it since it doesn't compile (aio.h
>>> and async io operations are missing in the current toolchain base).
>>
>> your patch should be a "Makefile" and a folder "/patches".
>> the makefile should point to e.g.  
>> http://www.iozone.org/src/current/iozone3_414.tar
>>
> 
> Well then it must be going to take lot of time for me to do that!
> 

take a package of your choice and check it's contents, especially the Makefile. 
it's pretty obvious how they work. there is also information on the openwrt 
wiki on how to create packages.

wrt. creating the patch - you could go the easy route and simply 'diff' your 
current source against a matching src tree and place the result into the patch/ 
folder of your package.

..good luck, ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] TP-Link TL-WR841ND to replace WRT54GL?

[edgar . soldin]

On 06.03.2013 19:40, Gert Doering wrote:
> Hi,
> 
> On Wed, Mar 06, 2013 at 07:33:44PM +0100, a...@mykolab.com wrote:
>> The TL-WR841ND may very well be a good choice. You can also consider 
>> the TL-WR1043ND, it has solid support (I have had about four of them and 
>> tested rather heavily over time). It is probably the best tested OpenWrt 
>> supported router today. It also fits you budget with a margin:
>> http://www.amazon.com/TP-LINK-TL-WR1043ND-Ultimate-Wireless-Detachable/dp/B002YLAUU8
> 
> +1 on the 1043ND.
> 
> If you do not need 5GHz WiFi, this is a really good buy.  Using them with
> various versions of OpenWRT as 1wire hub, OpenVPN client, server, 3G router
> (using an USB UMTS dongle, with OpenVPN and IPv6 over OpenVPN), ...
> 

out of interest. what would be a good 5ghz alternative?

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Maintainer address not reachable [Was: [PATCH] net/freeswitch: Make upstream-defaults package installable]

[edgar . soldin]

On 27.02.2013 15:33, Florian Fainelli wrote:
> Hello,
> 
> On 01/31/2013 09:11 PM, Uwe Kleine-König wrote:
>> Hello,
>>
>> I just got a mailer daemon notice that open...@slickdeals.endjunk.com
>> didn't get this mail because the mail server for its domain couldn't be
>> connected by mine.
>>
>> Who cares for the patch then?
> 
> Can you try to reach mazilo over IRC to see if he can provide you with an 
> alternate email address to contact him?
> 
> By the way, this specific patch seems to be obsolete with r35465, can you 
> confirm?

mazilo@ seems to exist
http://marc.info/?a=128509841500012&r=1&w=2

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Compiling custom kernel for latest trunk

[edgar . soldin]

On 15.01.2013 16:41, Emmanuel Deloget wrote:
> Le 12/01/2013 16:08, darius a écrit :
>> Hello,
>>
>> Simple question for those who know. I do 'make kernel_menuconfig' then 
>> select some needed features in kernel and then do 'make -j3' in topdir. 
>> After image is done, I install it on the router, but my kernel features are 
>> still not available. So I suppose I've done something wrong with kernel 
>> compilation. Could someone guide my about compiling custom kernel ?
>>

do not forget to

 make target/linux/{clean,compile} V=99

after you changed your kernel settings. you might leave out the cleaning if you 
just switched something on/off.

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] Initial support for Mikrotik RB751G-2HnD and RB751U-2HnD

[edgar . soldin]

this is different from client to client. if unsure or unable to fix it simply 
attach the patch to the email. this way it will survive whatever comes. people 
on this mailing list like the patches inline for commenting, but heck.. if it 
does not work out for you, simply attach it (for usage) *and* send it inline 
(for commenting).

generally mail programs have options to disable automatic line breaks and html 
composition. look for those.

..ede

On 05.04.2012 23:36, Hanno Schupp wrote:
> I am at a loss then what to do. I even went to the length of installing 
> alpine on my pc just for the purpose of sending one email. 
> 
> Why is this so hard? This makes porting openwrt to a new router model look 
> easy in comparison. I sent it to myself as a copy and it looked completely 
> normal to me. Where and how can I check it got mangled and how can I avoid it 
> getting it mangled. I followed the instructions in kernel.org for 
> email-clients and apparently the patch still gets mangled. Argh.
> 
> Kind Regards
> 
> Hanno 
> 
> 
> On 6/04/2012, at 9:24 AM, Jo-Philipp Wich  wrote:
> 
> It got line wrapped.
> 
> ~ Jow
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] lighttpd-nossl

[edgar . soldin]

hadn't seen it. yes, different build dir should work.

thanks ..ede

On 19.03.2012 15:05, Peter Wagner wrote:
> both packaes are build in a sepreate folders
> so yes - you can select both packages.
> 
> But you can also building both and testing it ;)
> 
> /Peter
> On Monday 19 March 2012 13:24:24 edgar.sol...@web.de wrote:
>> had a look at irssi. does this actually work when both packages are
>> selected? don't you end up with two packages both containing whatever was
>> build first?
>>
>> ..ede
>>
>> On 19.03.2012 13:18, Peter Wagner wrote:
>>> Hi,
>>>
>>> look at the ctorrent or irssi Makefile. There you can see how to
>>> implement the nossl stuff in one Makefile.
>>>
>>> Regards,
>>> Peter
>>>
>>> On Monday 19 March 2012 12:05:31 Christiane Ruetten wrote:
 Hi Edgar,

  just to be explicit: the idea is to have lighttpd-nossl in the

 official repo so I can get away with distributing a single
 platform-independent opkg. So I was hoping that the current
 maintainer could simply add a -nossl build instead of me having
 to reproduce the complete build effort.

 What I could do, though, is provide for a package/lighttpd-nossl/
 Makefile and company and someone else adds it to the official
 build system, but chances are that testing my changes, and generally
 making sure I didn't screw up might surpass the effort that
 a knowledgable maintainer requires for a copy/modify operation
 on the current package repo.

 I might be wrong there, and am grateful for any advice on
 how to proceed.

 Cheers,
 Christiane

 Am 19.03.12 11:30, schrieb edgar.sol...@web.de:
> On 19.03.2012 10:52, Christiane Ruetten wrote:
>> Hi,
>>
>>  would you be able to easily add a variant of the lighttpd
>>
>> package without the massive libopenssl dependency? It is almost
>> completely filling up the flash in 4 MByte routers, leaving
>> almost no headroom for further functionality, and https is not
>> always required.
>>
>>  I am currently in the process of rewriting the PirateBox
>>
>> wifi deaddrop service in an OpenWRT-friendly way. The current
>> target router chosen by the PirateBox community is the
>> TL-MR3020 which unfortunately only has 4 MByte flash.
>> Installing just lighttpd with rewrite and cgi and minimal
>> modules for USB storage takes the system from 1.4M to under
>> 100K of free flash.
>
> hi christiane,
>
> take a look at the lighttpd makefile
>
>  https://dev.openwrt.org/browser/packages/net/lighttpd/Makefile
>
> how webdav is build in as selectable package.
>
> you could do something similar to the currently hard coded openssl
> support.
>
> ..ede
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel

 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>>
>>> ___
>>> openwrt-devel mailing list
>>> openwrt-devel@lists.openwrt.org
>>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] lighttpd-nossl

[edgar . soldin]

had a look at irssi. does this actually work when both packages are selected? 
don't you end up with two packages both containing whatever was build first?

..ede

On 19.03.2012 13:18, Peter Wagner wrote:
> Hi,
> 
> look at the ctorrent or irssi Makefile. There you can see how to implement 
> the 
> nossl stuff in one Makefile.
> 
> Regards,
> Peter
> On Monday 19 March 2012 12:05:31 Christiane Ruetten wrote:
>> Hi Edgar,
>>
>>  just to be explicit: the idea is to have lighttpd-nossl in the
>> official repo so I can get away with distributing a single
>> platform-independent opkg. So I was hoping that the current
>> maintainer could simply add a -nossl build instead of me having
>> to reproduce the complete build effort.
>>
>> What I could do, though, is provide for a package/lighttpd-nossl/
>> Makefile and company and someone else adds it to the official
>> build system, but chances are that testing my changes, and generally
>> making sure I didn't screw up might surpass the effort that
>> a knowledgable maintainer requires for a copy/modify operation
>> on the current package repo.
>>
>> I might be wrong there, and am grateful for any advice on
>> how to proceed.
>>
>> Cheers,
>> Christiane
>>
>> Am 19.03.12 11:30, schrieb edgar.sol...@web.de:
>>> On 19.03.2012 10:52, Christiane Ruetten wrote:
 Hi,

  would you be able to easily add a variant of the lighttpd

 package without the massive libopenssl dependency? It is almost
 completely filling up the flash in 4 MByte routers, leaving
 almost no headroom for further functionality, and https is not
 always required.

  I am currently in the process of rewriting the PirateBox

 wifi deaddrop service in an OpenWRT-friendly way. The current
 target router chosen by the PirateBox community is the
 TL-MR3020 which unfortunately only has 4 MByte flash.
 Installing just lighttpd with rewrite and cgi and minimal
 modules for USB storage takes the system from 1.4M to under
 100K of free flash.
>>>
>>> hi christiane,
>>>
>>> take a look at the lighttpd makefile
>>>
>>>  https://dev.openwrt.org/browser/packages/net/lighttpd/Makefile
>>>
>>> how webdav is build in as selectable package.
>>>
>>> you could do something similar to the currently hard coded openssl
>>> support.
>>>
>>> ..ede
>>> ___
>>> openwrt-devel mailing list
>>> openwrt-devel@lists.openwrt.org
>>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] lighttpd-nossl

[edgar . soldin]

Maybe you are lucky and someone steps up. You are probably better of finding 
the maintainer (if there's one) directly by looking at the revision log or 
asking in the openwrt irc channel. The mailing list is often slow in this 
regard. If it all does not happen in time frame you planned in then you still 
have the do-it-yourself option.

..ede

On 19.03.2012 12:05, Christiane Ruetten wrote:
> Hi Edgar,
> 
>  just to be explicit: the idea is to have lighttpd-nossl in the
> official repo so I can get away with distributing a single
> platform-independent opkg. So I was hoping that the current
> maintainer could simply add a -nossl build instead of me having
> to reproduce the complete build effort.
> 
> What I could do, though, is provide for a package/lighttpd-nossl/
> Makefile and company and someone else adds it to the official
> build system, but chances are that testing my changes, and generally
> making sure I didn't screw up might surpass the effort that
> a knowledgable maintainer requires for a copy/modify operation
> on the current package repo.
> 
> I might be wrong there, and am grateful for any advice on
> how to proceed.
> 
> Cheers,
> Christiane
> 
> 
> Am 19.03.12 11:30, schrieb edgar.sol...@web.de:
>> On 19.03.2012 10:52, Christiane Ruetten wrote:
>>> Hi,
>>>
>>>  would you be able to easily add a variant of the lighttpd
>>> package without the massive libopenssl dependency? It is almost
>>> completely filling up the flash in 4 MByte routers, leaving
>>> almost no headroom for further functionality, and https is not
>>> always required.
>>>
>>>  I am currently in the process of rewriting the PirateBox
>>> wifi deaddrop service in an OpenWRT-friendly way. The current
>>> target router chosen by the PirateBox community is the
>>> TL-MR3020 which unfortunately only has 4 MByte flash.
>>> Installing just lighttpd with rewrite and cgi and minimal
>>> modules for USB storage takes the system from 1.4M to under
>>> 100K of free flash.
>>>
>>
>> hi christiane,
>>
>> take a look at the lighttpd makefile
>>  https://dev.openwrt.org/browser/packages/net/lighttpd/Makefile
>> how webdav is build in as selectable package.
>>
>> you could do something similar to the currently hard coded openssl support.
>>
>> ..ede
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] lighttpd-nossl

[edgar . soldin]

On 19.03.2012 10:52, Christiane Ruetten wrote:
> Hi,
> 
>  would you be able to easily add a variant of the lighttpd
> package without the massive libopenssl dependency? It is almost
> completely filling up the flash in 4 MByte routers, leaving
> almost no headroom for further functionality, and https is not
> always required.
> 
>  I am currently in the process of rewriting the PirateBox
> wifi deaddrop service in an OpenWRT-friendly way. The current
> target router chosen by the PirateBox community is the
> TL-MR3020 which unfortunately only has 4 MByte flash.
> Installing just lighttpd with rewrite and cgi and minimal
> modules for USB storage takes the system from 1.4M to under
> 100K of free flash.
> 

hi christiane,

take a look at the lighttpd makefile
 https://dev.openwrt.org/browser/packages/net/lighttpd/Makefile
how webdav is build in as selectable package.

you could do something similar to the currently hard coded openssl support.

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] parted and EFI_PARTITION=y

[edgar . soldin]

On 29.02.2012 14:16, cl...@bit63.org wrote:
> Quoting edgar.sol...@web.de:
> ...
>> more along the lines of
>>
>> ...
>>
>> define Package/parted
>>  SECTION:=utils
>>  CATEGORY:=Utilities
>>  SUBMENU:=disc
>>  DEFAULT:=n
>>  TITLE:=GNU Parted manipulates partition tables
>>  URL:=http://www.gnu.org/software/parted/
>>  DEPENDS:= +libuuid +libreadline +libncurses
>> endef
>>
>> # enable kernel module if package selected
>> ifdef CONFIG_PACKAGE_parted
>>   CONFIG_KERNEL_EFI_PARTITION:=y
>> endif
> 
> This makes sense. Thanks.
> 
>>
>> ...
>>
>>
>> but adding a proper kernel module package wouldn't probably hurt either ..ede
> 
> A kernel module seems like the best plan, however, since this config 
> parameter can't be configured as a module AFAICT I am unclear how to 
> accomplish this.
> 

if this really is no module, but just a symbol it would be probably most 
elegant to include a config file in the package Makefile to allow the user to 
switch on off partition schemes via menuconfig.

actually this should probably be dealt with in the buildroot kernel Makefile 
definition, shouldn't it, so that packages do not override each other.

see how madwifi includes Config.in for configuration parameters
https://dev.openwrt.org/browser/trunk/package/madwifi/Makefile

be aware the var names get the leading CONFIG_ automatically in this case e.g. 
defs would be like 

...
config KERNEL_EFI_PARTITION
default y
...


..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] parted and EFI_PARTITION=y

[edgar . soldin]

> Quoting edgar.sol...@web.de:
> 
>> On 29.02.2012 12:24, cl...@bit63.org wrote:
>>> In this case I am not sure what the best course of action is.
>>> What is the OpenWRT way to enable kernel options that aren't kernel modules?
>>
>> you can add a simple config var to your Makefile, like
>>  CONFIG_KERNEL_*=y
> 
> I couldn't find an example in the OpenWRT tree.
> If you know of one please point me in the right direction.
> 
> Are you suggesting something like the following?
> 
> include $(TOPDIR)/rules.mk
> 
> PKG_NAME:=parted
> PKG_VERSION:=2.4
> PKG_RELEASE:=1
> 
> PKG_BUILD_DIR:=$(BUILD_DIR)/parted-$(PKG_VERSION)
> PKG_SOURCE:=parted-$(PKG_VERSION).tar.gz
> PKG_SOURCE_URL:=@GNU/parted
> PKG_MD5SUM:=76a6457ea88447d79d50ca331069b19c
> PKG_CAT:=zcat
> CONFIG_KERNEL_EFI_PARTITION=y
> 
> include $(INCLUDE_DIR)/package.mk
> 
> define Package/parted
> SECTION:=utils
> CATEGORY:=Utilities
> SUBMENU:=disc
> DEFAULT:=n
> TITLE:=GNU Parted manipulates partition tables
> URL:=http://www.gnu.org/software/parted/
> DEPENDS:= +libuuid +libreadline +libncurses
> endef
> 
> define Package/parted/description
> GNU Parted manipulates partition tables. This is useful for creating
> space for new operating systems, reorganizing disk usage, copying data
> on hard disks and disk imaging. The package contains a library,
> libparted, as well as well as a command-line frontend, parted,
> which can also be used in scripts.
> endef
> 
> define Build/Configure
> $(call Build/Configure/Default, \
> --enable-static \
> )
> endef
> 
> define Package/parted/install
> $(INSTALL_DIR) $(1)/usr/sbin
> $(INSTALL_BIN) $(PKG_BUILD_DIR)/parted/parted $(1)/usr/sbin/
> endef
> 
> $(eval $(call BuildPackage,parted))
> 
> 
> 
> 
> This message was sent using IMP, the Internet Messaging Program.
> 
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
 

more along the lines of 

...

define Package/parted
 SECTION:=utils
 CATEGORY:=Utilities
 SUBMENU:=disc
 DEFAULT:=n
 TITLE:=GNU Parted manipulates partition tables
 URL:=http://www.gnu.org/software/parted/
 DEPENDS:= +libuuid +libreadline +libncurses
endef

# enable kernel module if package selected
ifdef CONFIG_PACKAGE_parted
  CONFIG_KERNEL_EFI_PARTITION:=y
endif

...


but adding a proper kernel module package wouldn't probably hurt either ..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] parted and EFI_PARTITION=y

[edgar . soldin]

On 29.02.2012 12:24, cl...@bit63.org wrote:
> In this case I am not sure what the best course of action is.
> What is the OpenWRT way to enable kernel options that aren't kernel modules?

you can add a simple config var to your Makefile, like
 CONFIG_KERNEL_*=y

these are automatically translated to CONFIG_* defs in the generated 
kernelconfig. it's generated on every run, but you will have to explicitely 
rebuild your kernel with
 make target/linux/{clean,compile} V=99
to have the module built in obviously.

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] WBMR-HP-G300H flash image for flashing from original FW?

[edgar . soldin]

On 23.02.2012 19:21, John Crispin wrote:
> dd-wrt webif

on openwrt? ..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] reaver-wps package Makefile available

[edgar . soldin]

for the unaware
http://code.google.com/p/reaver-wps/

somebody created a package Makefile for reaver in the forum
https://forum.openwrt.org/viewtopic.php?pid=152639

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Help -- Noob Question -- Driving Me Crazy

[edgar . soldin]

On 11.11.2011 20:51, Mike Brady wrote:

Can someone tell be or direct me to an example of how to put a linux version 
conditional into an OpenWrt package Makefile please?

What I want to do is say "if this is and version of Linux 2.4 then do stufft". 
I've tried something like

ifeq ($(CONFIG_LINUX_2_4),1)

endif

but no joy.



use
ifeq ($(KERNEL),2.4)
e.g. see here
https://dev.openwrt.org/browser/trunk/package/fuse/Makefile?rev=21300

be aware 2.4 is not supported anymore in trunk.. ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] OpenWrt GPL compliance

[edgar . soldin]

On 20.09.2011 13:56, bifferos wrote:
> 
> I'd like to provide a binary build of OpenWrt packages, however I want to 
> comply with the terms of the GPL.  I figured the most obvious thing to do 
> would be to copy the way OpenWrt does things.  I'm not convinced that OpenWrt 
> complies with the GPL with regard to section 3, as I have no idea how to 
> generate the packages in the snapshot from the files in the 'sources' area, 
> and I haven't seen this documented anywhere.
> 
> Can someone shed some light on this?
> 

Did you see the first sentences of e.g.
http://downloads.openwrt.org/backfire/10.03.1-rc5/README

? ede

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] OpenWrt GPL compliance

[edgar . soldin]

On 20.09.2011 14:33, bifferos wrote:
> So how do I know what version of packages was pulled in at the time of 
> building?  I can assume the package source itself ends up in the 'dl' 
> directory, so I can back that up so I have the pristine package source, but 
> what about the patch set that was applied at that time, and where is the 
> build config for that release?
> 

this is topic once in a while here on the list. search the archives. there is 
one revision for packages and trunk per release, as they come out of the same 
svn.

> Put in simple terms, where is the build script for a given snapshot?

ordinary buildroot. just find out the correct revision and download that 
instead of latest.


ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] replace CONFIG_PREEMPT_NONE with CONFIG_PREEMPT

[edgar . soldin]

On 02.09.2011 12:39, Luka Perkov wrote:
> Hi,
> 
> On Fri, Sep 02, 2011 at 10:46:37AM +0200, Florian Fainelli wrote:
>> On Friday 02 September 2011 00:55:54 Luka Perkov wrote:
>>> Also in linux-2.6.39.4/kernel/Kconfig.preempt you will see for
>>> CONFIG_PREEMPT:
>>>
>>> Select this if you are building a kernel for a desktop or
>>> embedded system with latency requirements in the milliseconds
>>> range
> 
> Please look at the kernel config file above. You will see that
> CONFIG_PREEMPT should be used on embedded systems...
>  

actually it says 

"system with latency requirements in the milliseconds range"

;9 .. but that's no reason not to use it if it might fix issues.

ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH][PACKAGE] upgrade openvpn package

[edgar . soldin]

On 29.08.2011 18:17, Luka Perkov wrote:
> On Mon, Aug 29, 2011 at 05:32:10PM +0200, Jan Willies wrote:
>> 2011/8/29 
>>> right missed that. and yes reversing would be most elegant. ede
> 
> I don't see why reversing would be most elegant. Now you can fully tweak
> your openvpn package.
> 

you missed the reference

> which incidentially shows that the option names are misleading and
> they should be renamed or their effect reversed, so that they enable,
> not disable (I'd prefer the latter).

OPENVPN_LZO is not only shorter than OPENVPN_DISABLE_LZO , it also reads better 
if it is reversed !OPENVPN_LZO . But for that the values in Config.in would 
have been to be reversed too.

The solution now works. All is well.. ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH][PACKAGE] upgrade openvpn package

[edgar . soldin]

On 29.08.2011 17:14, Jonas Gorski wrote:
> On 29 August 2011 17:04,   wrote:
>> On 29.08.2011 16:44, Jan Willies wrote:
>>> 2011/8/29 mailto:edgar.sol...@web.de>>
>>>
>>> On 29.08.2011 16 :14, Jan Willies wrote:
>>> > Hi Luka,
>>> >
>>> > 2011/8/21 Luka Perkov >>  >> >>
>>> >
>>> >  define Package/openvpn
>>> >   SECTION:=net
>>> >   CATEGORY:=Network
>>> > +  SUBMENU:=VPN
>>> >   DEPENDS:=+kmod-tun +libopenssl +PACKAGE_openvpn_complzo:liblzo
>>> >
>>> >
>>> > The lzo dependency doesn't seem to work. It's not selected here.
>>>
>>> as openvpn_complzo obviously is a package definition why isn't the 
>>> liblzo dependency defined there? that would definitely select it then.
>>>
>>>
>>> It's just a configuration option (Config.in), not a full featured package. 
>>> Depending on it there makes it unavailable in menuconfig unless lzo is 
>>> selected. This is not desired IMO.
>>>
>>>
>>
>> i see, but there is only a OPENVPN_LZO there in Config.in . So wouldn't it be
>>
>> +OPENVPN_LZO:liblzo
> 
> OPENVPN_LZO /disables/ lzo, so it should be:
> 
> +!OPENVPN_LZO:liblzo
> 
> 
> which incidentially shows that the option names are misleading and
> they should be renamed or their effect reversed, so that they enable,
> not disable (I'd prefer the latter).
> 
> 

right missed that. and yes reversing would be most elegant. ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH][PACKAGE] upgrade openvpn package

[edgar . soldin]

On 29.08.2011 16:44, Jan Willies wrote:
> 2011/8/29 mailto:edgar.sol...@web.de>>
> 
> On 29.08.2011 16 :14, Jan Willies wrote:
> > Hi Luka,
> >
> > 2011/8/21 Luka Perkov    >>
> >
> >  define Package/openvpn
> >   SECTION:=net
> >   CATEGORY:=Network
> > +  SUBMENU:=VPN
> >   DEPENDS:=+kmod-tun +libopenssl +PACKAGE_openvpn_complzo:liblzo
> >
> >
> > The lzo dependency doesn't seem to work. It's not selected here.
> 
> as openvpn_complzo obviously is a package definition why isn't the liblzo 
> dependency defined there? that would definitely select it then.
> 
> 
> It's just a configuration option (Config.in), not a full featured package. 
> Depending on it there makes it unavailable in menuconfig unless lzo is 
> selected. This is not desired IMO.
> 
> 

i see, but there is only a OPENVPN_LZO there in Config.in . So wouldn't it be

+OPENVPN_LZO:liblzo

then?

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH][PACKAGE] upgrade openvpn package

[edgar . soldin]

On 29.08.2011 16:14, Jan Willies wrote:
> Hi Luka,
> 
> 2011/8/21 Luka Perkov mailto:open...@lukaperkov.net>>
> 
>  define Package/openvpn
>   SECTION:=net
>   CATEGORY:=Network
> +  SUBMENU:=VPN
>   DEPENDS:=+kmod-tun +libopenssl +PACKAGE_openvpn_complzo:liblzo
> 
> 
> The lzo dependency doesn't seem to work. It's not selected here.

as openvpn_complzo obviously is a package definition why isn't the liblzo 
dependency defined there? that would definitely select it then.

ede

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH 1/1] kmod-input-xxx: missing dependency on kmod-input-core

[edgar . soldin]

On 27.07.2011 17:57, Philip Prindeville wrote:
> On 7/27/11 4:19 AM, Jo-Philipp Wich wrote:
>> Hi.
>>
>>> -  KCONFIG:=CONFIG_INPUT_EVDEV
>>> +  KCONFIG:=CONFIG_INPUT_EVDEV +kmod-input-core
>>
>> This looks wrong.
>>
>> ~ Jow
> 
> Specifically?
> 

wouldn't it be

DEPENDS:=+kmod-input-core

? ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Please ignore: cts 0.2 stable & geomconv 0.3rc2 released

[edgar . soldin]

... sorry again ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] cts 0.2 stable & geomconv 0.3rc2 released

[edgar . soldin]

continuing my daily release cycle here comes

CTS (coordinate transfomation services) Extension, stable until proven 
otherwise, translated into english, german, spanish, italian

Geometry Converter Extension 0.3rc2 fixing a bug where it simply did nothing if 
an older version of my other extensions was installed. to tell the user the 
language properties file has an added string for that case.
Fork maintainers please see GCPlugin:initialize for convenience installation 
methods.

both as always available on
https://sourceforge.net/projects/jump-pilot/files/p_GPS%2CCTS%20Extensions/

Geometry Converter in this current state applies again for inclusion into oj 
for the 1.4.2 release. anybody willing please send me translations.


kind regards ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Make package foo conflict with /replace package bar

[edgar . soldin]

On 12.06.2011 10:59, edgar.sol...@web.de wrote:
> On 10.06.2011 08:43, harish badrinath wrote:
>> Hello,
>> If i have a package called foo, How do it specify in its Makefile
>> (package/foo/Makefile) that it conflicts with / replaces a package
>> called bar. When that happens the compilation is aborted until package
>> bar is deselected.
>>
>>
> 
> try what phillip suggested, but know that the result wont be a compilation 
> error. instead the package will not be available in menuconfig (as long as 
> the conflicting package is selected) or deselected during build because of 
> that rule and hence skipped.
> 
> conflicting packages usually do the same differently. did you consider 
> creating a package with options?
> 

check
http://wiki.openwrt.org/doc/devel/packages#adding.configuration.options

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Make package foo conflict with /replace package bar

[edgar . soldin]

On 10.06.2011 08:43, harish badrinath wrote:
> Hello,
> If i have a package called foo, How do it specify in its Makefile
> (package/foo/Makefile) that it conflicts with / replaces a package
> called bar. When that happens the compilation is aborted until package
> bar is deselected.
> 
> 

try what phillip suggested, but know that the result wont be a compilation 
error. instead the package will not be available in menuconfig (as long as the 
conflicting package is selected) or deselected during build because of that 
rule and hence skipped.

conflicting packages usually do the same differently. did you consider creating 
a package with options?

ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] initial 2.6.39 support for brcm47xx

[edgar . soldin]

works for me on a asus wl-500w.

thanks, ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] initial 2.6.39 support for brcm47xx

[edgar . soldin]

On 24.05.2011 21:12, Peter Wagner wrote:
> i think its more about - he asks me in a polite way not to toppost :)
> and if someone asks in a nice way - you can see what you can get ;)

he did indeed. probably i just overreact on this. it's like somebody is telling 
how to talk (in which order)... i should leave the issue to you guys, it just 
got to me. all i wanted to say was, feel free to choose.

sorry&peace ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] initial 2.6.39 support for brcm47xx

[edgar . soldin]

On 24.05.2011 21:03, Rafał Miłecki wrote:
> 2011/5/24  :
>> On 24.05.2011 20:03, Rafał Miłecki wrote:
>>> P.S.
>>> Please, don't top post :)
>>
>> why shouldn't he? it's not like you couldn't understand his message, is it?
> 
> That's posting style that was decided to be used for most open-source
> related ML.
> 
> Short and great explanation:
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
> 

don't we have other issues to deal with? 
i see your point, hope you see mine too.. there are mailing list archives that 
put threads in order, regardless who posted where. at least i (doing this in my 
own private time) do not need anybody to tell me where to post in an answer. 
next time somebody insists on proper capitalization. how about mandatory spell 
checking?

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] initial 2.6.39 support for brcm47xx

[edgar . soldin]

On 24.05.2011 20:03, Rafał Miłecki wrote:
> P.S.
> Please, don't top post :)

why shouldn't he? it's not like you couldn't understand his message, is it?

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] How does one build just one KLM?

[edgar . soldin]

welcome.. you could also manually remove builddir. buildroot is putting files 
in builddir (.prepared and the like). this is to circumvent to 
prepare,rebuild,install something again (e.g. when recompile an image with one 
added pkg added in menuconfig). 

keep that in mind and you are set for your kernel mod development ..

good luck ede

On 12.05.2011 17:00, John Zavgren wrote:
> Thank you SO much for your help. I've identified my problem. It seems that I 
> need to make the clean target before I make the compile target, otherwise, 
> the KLM isn't generated.
> This recipe works:
> 
> make package/vislinkRcv/clean V=99
> make package/vislinkRcv/compile V=99
> 
> 
> 
> On Thu, May 12, 2011 at 10:23 AM,  > wrote:
> 
> so where does a (in buildroot root)
> 
> $> make package//{clean,compile} V=99
> 
> leave you?... attach the output or pastebin it .. also check if the new 
> binary is created in builddir
> 
> ..ede
> 
> 
> 
> On 12.05.2011 16:08, John Zavgren wrote:
> > It get's  built and staged when I do a "global" make.
> >
> > I want a technique for making just this one KLM, so that I don't need 
> to build the entire enchilada, every time I make a change to  it's source 
> code. I don't care where the .ko file lands, because I'm moving it to my 
> target (via scp) anyway. (I'm not replacing the entire file system with each 
> incremental build.)
> >
> > All I'm looking for, at this point, is a simple hack that will save me 
> a huge amount of development time.
> >
> >
> >
> > On Thu, May 12, 2011 at 9:37 AM,    >> wrote:
> >
> > isn't it build in the build_dir or just not installed? i see no 
> install definition in your makefile. as jow wrote
> >
> > > f you can you should consider packaging your source as an 
> out-of-tree
> > > module, see for example the KernelPackage / kmod defintions in
> > > package/wprobe/Makefile .
> >
> > ede
> >
> > On 12.05.2011 15:24, John Zavgren wrote:
> > > Here's the Makefile. Thanks, John
> > > --
> > >
> > > #
> > > # Copyright (C) 2006 OpenWrt.org
> > > #
> > > # This is free software, licensed under the GNU General 
> Public License v2.
> > > # See /LICENSE for more information.
> > > #
> > > # $Id: Makefile 10203 2008-01-15 03:25:11Z matteo $
> > >
> > > include $(TOPDIR)/rules.mk  
>  
> > > include $(INCLUDE_DIR)/kernel.mk  
>  
> > >
> > > PKG_NAME:=vislinkRcv
> > > PKG_VERSION:=1.1
> > >
> > > include $(INCLUDE_DIR)/package.mk  
>  
> > >
> > > define KernelPackage/vislinkRcv
> > >   SUBMENU:=Network Devices
> > >   TITLE:=Vislink tunnel receiver.
> > >   FILES:=$(PKG_BUILD_DIR)/vislinkRcv.$(LINUX_KMOD_SUFFIX)
> > >   AUTOLOAD:=$(call AutoLoad,50,vislinkRcv)
> > > endef
> > >
> > > define KernelPackage/vislinkRcv/description
> > > This module receives and processes frames that have 
> been
> > > created by vislink encpasulation.
> > > endef
> > >
> > > define Build/Prepare
> > > mkdir -p $(PKG_BUILD_DIR)
> > > cp src/Makefile src/vislink.h src/vislinkRcv.c 
> $(PKG_BUILD_DIR)/
> > > endef
> > >
> > > define Build/Compile
> > > $(MAKE) -C $(LINUX_DIR) \
> > > CROSS_COMPILE="$(TARGET_CROSS)" \
> > > ARCH="$(LINUX_KARCH)" \
> > > SUBDIRS="$(PKG_BUILD_DIR)" \
> > > KERNELDIR=$(LINUX_DIR) \
> > > CC="$(TARGET_CC)" \
> > > modules
> > > endef
> > >
> > > $(eval $(call KernelPackage,vislinkRcv))
> > >
> > >
> > >
> > > On Thu, May 12, 2011 at 9:09 AM,    >     > >
> > > Could you post your makefile here?..  ede
> > >
> > > On 12.05.2011 02:02, John Zavgren wrote:
> > > > Thanks, Christian:
> > > >
> > > > I read the article on the wiki and then I tried "make 
> package/vislinkRcv/compile" from th

Re: [OpenWrt-Devel] How does one build just one KLM?

[edgar . soldin]

so where does a (in buildroot root) 

$> make package//{clean,compile} V=99

leave you?... attach the output or pastebin it .. also check if the new binary 
is created in builddir

..ede



On 12.05.2011 16:08, John Zavgren wrote:
> It get's  built and staged when I do a "global" make.
> 
> I want a technique for making just this one KLM, so that I don't need to 
> build the entire enchilada, every time I make a change to  it's source code. 
> I don't care where the .ko file lands, because I'm moving it to my target 
> (via scp) anyway. (I'm not replacing the entire file system with each 
> incremental build.)
> 
> All I'm looking for, at this point, is a simple hack that will save me a huge 
> amount of development time.
> 
> 
> 
> On Thu, May 12, 2011 at 9:37 AM,  > wrote:
> 
> isn't it build in the build_dir or just not installed? i see no install 
> definition in your makefile. as jow wrote
> 
> > f you can you should consider packaging your source as an out-of-tree
> > module, see for example the KernelPackage / kmod defintions in
> > package/wprobe/Makefile .
> 
> ede
> 
> On 12.05.2011 15:24, John Zavgren wrote:
> > Here's the Makefile. Thanks, John
> > --
> >
> > #
> > # Copyright (C) 2006 OpenWrt.org
> > #
> > # This is free software, licensed under the GNU General Public 
> License v2.
> > # See /LICENSE for more information.
> > #
> > # $Id: Makefile 10203 2008-01-15 03:25:11Z matteo $
> >
> > include $(TOPDIR)/rules.mk  
> > include $(INCLUDE_DIR)/kernel.mk  
> 
> >
> > PKG_NAME:=vislinkRcv
> > PKG_VERSION:=1.1
> >
> > include $(INCLUDE_DIR)/package.mk  
> 
> >
> > define KernelPackage/vislinkRcv
> >   SUBMENU:=Network Devices
> >   TITLE:=Vislink tunnel receiver.
> >   FILES:=$(PKG_BUILD_DIR)/vislinkRcv.$(LINUX_KMOD_SUFFIX)
> >   AUTOLOAD:=$(call AutoLoad,50,vislinkRcv)
> > endef
> >
> > define KernelPackage/vislinkRcv/description
> > This module receives and processes frames that have been
> > created by vislink encpasulation.
> > endef
> >
> > define Build/Prepare
> > mkdir -p $(PKG_BUILD_DIR)
> > cp src/Makefile src/vislink.h src/vislinkRcv.c 
> $(PKG_BUILD_DIR)/
> > endef
> >
> > define Build/Compile
> > $(MAKE) -C $(LINUX_DIR) \
> > CROSS_COMPILE="$(TARGET_CROSS)" \
> > ARCH="$(LINUX_KARCH)" \
> > SUBDIRS="$(PKG_BUILD_DIR)" \
> > KERNELDIR=$(LINUX_DIR) \
> > CC="$(TARGET_CC)" \
> > modules
> > endef
> >
> > $(eval $(call KernelPackage,vislinkRcv))
> >
> >
> >
> > On Thu, May 12, 2011 at 9:09 AM,    >> wrote:
> >
> > Could you post your makefile here?..  ede
> >
> > On 12.05.2011 02:02, John Zavgren wrote:
> > > Thanks, Christian:
> > >
> > > I read the article on the wiki and then I tried "make 
> package/vislinkRcv/compile" from the TOPDIR (vislinkRcv is the stuff that I'm 
> developing) and no KLM was actually built. When I do the general purpose 
> "make" operation from the same context, it is built.
> > >
> > > Confused.
> > >
> > > On Wed, May 11, 2011 at 6:53 PM, Christian Sobkowski 
> mailto:insan...@gmx.ch>  >  
>  > >
> > > The Wiki basically answers it:
> > > http://wiki.openwrt.org/doc/howto/build
> > >
> > > A 'make path/to/package/compile' (i.e. 'make 
> package/busybox/compile') in the TOPDIR with an optional V=99 switch will do 
> the trick.
> > >
> > > Cheers,
> > > Christian
> > >
> > > On May 12, 2011, at 12:40 AM, John Zavgren wrote:
> > >
> > >> If I wish to build just one KLM (or application, or 
> library), is there a way I can target my build to just that one thing? At 
> this time, I'm executing a make command at the top level of the openWRT 
> source tree, every time I wish to cross compile something. And, ... , that's 
> awfully slow.
> > >>
> > >> Thanks,
> > >> John
> > >>
> > >>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/

Re: [OpenWrt-Devel] How does one build just one KLM?

[edgar . soldin]

isn't it build in the build_dir or just not installed? i see no install 
definition in your makefile. as jow wrote

> f you can you should consider packaging your source as an out-of-tree
> module, see for example the KernelPackage / kmod defintions in
> package/wprobe/Makefile .

ede

On 12.05.2011 15:24, John Zavgren wrote:
> Here's the Makefile. Thanks, John
> --
> 
> #
> # Copyright (C) 2006 OpenWrt.org
> #
> # This is free software, licensed under the GNU General Public License v2.
> # See /LICENSE for more information.
> #
> # $Id: Makefile 10203 2008-01-15 03:25:11Z matteo $
> 
> include $(TOPDIR)/rules.mk 
> include $(INCLUDE_DIR)/kernel.mk 
> 
> PKG_NAME:=vislinkRcv
> PKG_VERSION:=1.1
> 
> include $(INCLUDE_DIR)/package.mk 
> 
> define KernelPackage/vislinkRcv
>   SUBMENU:=Network Devices
>   TITLE:=Vislink tunnel receiver.
>   FILES:=$(PKG_BUILD_DIR)/vislinkRcv.$(LINUX_KMOD_SUFFIX)
>   AUTOLOAD:=$(call AutoLoad,50,vislinkRcv)
> endef
> 
> define KernelPackage/vislinkRcv/description
> This module receives and processes frames that have been
> created by vislink encpasulation.
> endef
> 
> define Build/Prepare
> mkdir -p $(PKG_BUILD_DIR)
> cp src/Makefile src/vislink.h src/vislinkRcv.c $(PKG_BUILD_DIR)/
> endef
> 
> define Build/Compile
> $(MAKE) -C $(LINUX_DIR) \
> CROSS_COMPILE="$(TARGET_CROSS)" \
> ARCH="$(LINUX_KARCH)" \
> SUBDIRS="$(PKG_BUILD_DIR)" \
> KERNELDIR=$(LINUX_DIR) \
> CC="$(TARGET_CC)" \
> modules
> endef
> 
> $(eval $(call KernelPackage,vislinkRcv))
> 
> 
> 
> On Thu, May 12, 2011 at 9:09 AM,  > wrote:
> 
> Could you post your makefile here?..  ede
> 
> On 12.05.2011 02:02, John Zavgren wrote:
> > Thanks, Christian:
> >
> > I read the article on the wiki and then I tried "make 
> package/vislinkRcv/compile" from the TOPDIR (vislinkRcv is the stuff that I'm 
> developing) and no KLM was actually built. When I do the general purpose 
> "make" operation from the same context, it is built.
> >
> > Confused.
> >
> > On Wed, May 11, 2011 at 6:53 PM, Christian Sobkowski   >> 
> wrote:
> >
> > The Wiki basically answers it:
> > http://wiki.openwrt.org/doc/howto/build
> >
> > A 'make path/to/package/compile' (i.e. 'make 
> package/busybox/compile') in the TOPDIR with an optional V=99 switch will do 
> the trick.
> >
> > Cheers,
> > Christian
> >
> > On May 12, 2011, at 12:40 AM, John Zavgren wrote:
> >
> >> If I wish to build just one KLM (or application, or library), is 
> there a way I can target my build to just that one thing? At this time, I'm 
> executing a make command at the top level of the openWRT source tree, every 
> time I wish to cross compile something. And, ... , that's awfully slow.
> >>
> >> Thanks,
> >> John
> >>
> >>
> >> --
> >> Remember when teachers, public employees, Planned Parenthood, NPR 
> and PBS crashed the stock market, wiped out half of our 401Ks, took trillions 
> in TARP money, spilled oil in the Gulf of Mexico, gave themselves billions in 
> bonuses, and paid no taxes? Yeah, me neither.
> >>
> >> John Zavgren
> >> 603-371-0513   > (home)
> >> 603-801-2094   > (cell)
> >> johnzavgren (skype)
> >> 603-821-0904   > (skype)
> >> j...@zavgren.com  
> >
> >>
> >> ___
> >> openwrt-devel mailing list
> >> openwrt-devel@lists.openwrt.org 
>  
>  >
> >> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> >
> >
> > ___
> > openwrt-devel mailing list
> > openwrt-devel@lists.openwrt.org 
>  
>  >
> > https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> >
> >
> >
> >
> > --
> > Remember when teachers, public employees, Planned Parenthood, NPR and 
> PBS crashed the stock market, wiped out half of our 401Ks, took trillions in 
> TARP money, spilled oil in the Gulf of Mexico, gave themselves billions in 
> bonuses, and paid no taxes? Yeah, me neither.
> >
> > John Zavgren
> > 603-371-0513  (home)
> > 

Re: [OpenWrt-Devel] How does one build just one KLM?

[edgar . soldin]

Could you post your makefile here?..  ede

On 12.05.2011 02:02, John Zavgren wrote:
> Thanks, Christian:
> 
> I read the article on the wiki and then I tried "make 
> package/vislinkRcv/compile" from the TOPDIR (vislinkRcv is the stuff that I'm 
> developing) and no KLM was actually built. When I do the general purpose 
> "make" operation from the same context, it is built.
> 
> Confused.
> 
> On Wed, May 11, 2011 at 6:53 PM, Christian Sobkowski  > wrote:
> 
> The Wiki basically answers it:
> http://wiki.openwrt.org/doc/howto/build
> 
> A 'make path/to/package/compile' (i.e. 'make package/busybox/compile') in 
> the TOPDIR with an optional V=99 switch will do the trick.
> 
> Cheers,
> Christian
> 
> On May 12, 2011, at 12:40 AM, John Zavgren wrote:
> 
>> If I wish to build just one KLM (or application, or library), is there a 
>> way I can target my build to just that one thing? At this time, I'm 
>> executing a make command at the top level of the openWRT source tree, every 
>> time I wish to cross compile something. And, ... , that's awfully slow.
>>
>> Thanks, 
>> John
>>
>>
>> -- 
>> Remember when teachers, public employees, Planned Parenthood, NPR and 
>> PBS crashed the stock market, wiped out half of our 401Ks, took trillions in 
>> TARP money, spilled oil in the Gulf of Mexico, gave themselves billions in 
>> bonuses, and paid no taxes? Yeah, me neither.
>>
>> John Zavgren
>> 603-371-0513  (home)
>> 603-801-2094  (cell)
>> johnzavgren (skype)
>> 603-821-0904  (skype)
>> j...@zavgren.com 
>>
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org 
>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> 
> 
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org 
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> 
> 
> 
> 
> -- 
> Remember when teachers, public employees, Planned Parenthood, NPR and PBS 
> crashed the stock market, wiped out half of our 401Ks, took trillions in TARP 
> money, spilled oil in the Gulf of Mexico, gave themselves billions in 
> bonuses, and paid no taxes? Yeah, me neither.
> 
> John Zavgren
> 603-371-0513 (home)
> 603-801-2094 (cell)
> johnzavgren (skype)
> 603-821-0904 (skype)
> j...@zavgren.com 
> 
> 
> 
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Retaining WAN IP addresses across reboots

[edgar . soldin]

On 13.04.2011 19:18, Philip Prindeville wrote:
> All of the platforms I have use a CMOS NVRAM with RTC built-in.
> 
> 

do they have names? ;)

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Status of outstanding patches

[edgar . soldin]

write to Travis Kemen  about the maintainer issue.. in 
case he didn't read your mail to the end.. regards ede

On 25.03.2011 22:46, W. Michael Petullo wrote:
> vips-7.24.1.patch, upgrade VIPS to 7.24.1
> 
>   https://dev.openwrt.org/ticket/8467
> 
>   I'd be happy to take over the maintenance of the VIPS package

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] lantiq: various fixes to the extract.sh script

[edgar . soldin]

On 28.02.2011 18:26, Luca Olivetti wrote:
> [ ! -f ${DIR}decode_ifx_fw -a -f ${DIR}ifxmips_fw_decodev2.tar.bz2 ]

These will break if the path contains spaces. Always enclose pathes in double 
quotes if you can't be sure that they never will include spaces. This is also 
true for the other places where you used the $DIR variable.

peace ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] dnsmasq leasefile fix

[edgar . soldin]

i see to reflect the date change the file is copied to jffs.. makes sense, so 
the touch alone is more expensive due to the nature of the overlaying fs :) .. 
thanks ede

On 15.02.2011 12:50, Peter Wagner wrote:
> no its not about what is more expensive but someone in the development 
> channel 
> ment, that a touch on a squashfs with jffs overlay will create a new file on 
> the jffs overlay even when the file existed on the squashfs partition...
> 
> Am Dienstag, 15. Februar 2011, 11:20:47 schrieb edgar.sol...@web.de:
>> On 15.02.2011 11:13, Ferenc Wagner wrote:
>>> Peter Wagner  writes:
 -   [ -n "$leasefile" ] && [ -e "$leasefile" ] || touch "$leasefile"
 +   [ -n "$leasefile" ] && ( [ -e "$leasefile" ] || touch
 "$leasefile" )
>>>
>>> Looks like this is fixed already by commit 15fba44a (but see point 6 of
>>> http://mywiki.wooledge.org/BashPitfalls and the rest for an interesting
>>> read) so the following is academic, but I typed it before checking...
>>>
>>> It's cheeper to use braces in such cases to avoid subshell creation:
>>>   [ -n "$leasefile" ] && { [ -e "$leasefile" ] || touch
>>>   "$leasefile"; }
>>
>> command grouping is the way to go, right
>>
>>> Btw. is the -e test really necessary?  Why not simply
>>>
>>>   [ -n "$leasefile" ] && touch "$leasefile"
>>>
>>> ?
>>
>> depends on what is more expensive .. the test or the touch, but i doubt the
>> research is worth the effective result.
>>
>> ede
>>
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> 
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] dnsmasq leasefile fix

[edgar . soldin]

On 15.02.2011 11:13, Ferenc Wagner wrote:
> Peter Wagner  writes:
> 
>> -   [ -n "$leasefile" ] && [ -e "$leasefile" ] || touch "$leasefile"
>> +   [ -n "$leasefile" ] && ( [ -e "$leasefile" ] || touch "$leasefile" )
> 
> Looks like this is fixed already by commit 15fba44a (but see point 6 of
> http://mywiki.wooledge.org/BashPitfalls and the rest for an interesting
> read) so the following is academic, but I typed it before checking...
> 
> It's cheeper to use braces in such cases to avoid subshell creation:
> 
>   [ -n "$leasefile" ] && { [ -e "$leasefile" ] || touch "$leasefile"; 
> }
> 

command grouping is the way to go, right

> Btw. is the -e test really necessary?  Why not simply
> 
>   [ -n "$leasefile" ] && touch "$leasefile"
> ?

depends on what is more expensive .. the test or the touch, but i doubt the 
research is worth the effective result.

ede

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] build brcm-24 image with trunk

[edgar . soldin]

Is there a way to build a kernel 2.4 image for brcm47xx platform with the 
current buildroot in trunk? The target brcm-2.4 was removed a while ago. How 
would I do so, except of going back in svn history?

thanks ede

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] base-files/hotplug: refactoring ifup/netstate V2

[edgar . soldin]

On 20.01.2011 13:40, John Crispin wrote:
>> > without having stomach ache, when base breaks.
> i dont get the "when base breaks" bit

he means in case the modifications (in the 'alternative' base package) 
introduce a show stopping bug.

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] base-files: refactoring load_modules()

[edgar . soldin]

On 20.01.2011 06:50, Scott Nicholas wrote:
> I like Bastian's refactorings using only ash builtins. if ever a micro
> image is needed, sed/awk can go away. yes? 

for micro images usually busybox is used and awk/sed are available busybox 
applets. i really doubt that the size increase is in proportion to the rework 
(including bugfixing) the already working code.

ede

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] gawk package

[edgar . soldin]

Could you please add

http://projects.qi-hardware.com/index.php/p/openwrt-packages/source/tree/release_2010-11-17/gawk/Makefile

to the package repository.

Thanks ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] sextante loading mystery solved

[edgar . soldin]

I do .. these open* projects all look the same in thunderbirds address 
suggestions .. I will have to find a solution for that.

thanks & sorry, again, ede

On 03.11.2010 20:10, Jo-Philipp Wich wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

You keep writing to the wrong list ;)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkzRs6gACgkQdputYINPTPMN2ACfTp3ENuEulzMOBMRJVnIdsKp6
S3cAn3x4HsBxQn4fysjNXH66117ZKO86
=0TCd
-END PGP SIGNATURE-
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] sextante loading mystery solved

[edgar . soldin]

phew, that was something. As it turns out.

es.unex.sextante.openjump.extensions.SextanteToolboxPlugin

detects the path to the extension dir as follows

String sPath = System.getProperty("user.dir") + "/lib/ext";

'user.dir' despite it's name holds the current working dir of the java vm. The 
old oj_linux.sh didn't switch to the oj home dir, but used pathes for all 
parameters. This gave problems with spaces in the path, so I decided to chdir 
to oj home, like we do under windows. Funny coincidence, this way the problem 
was solved in parallel to occurring.

Still we should fix SextanteToolboxPlugin.java. Using the home_dir is unclean, 
there are better ways to reflect where a specific file is located in the 
filesystem. I'd patch it if I'd know where Stefan hosts the scm for the 
sextante binding. If it is on an scm at all. Anybody has a clue? I found the 
source in the 'ojsextantebinding_oct2010.jar' but I don't know if that is 
really the cutting edge code.


.. regards ede

PS: Stefan, please check also the mail to the mailing list about the logo on 
sf.net  .
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] oj icon on sourceforge

[edgar . soldin]

Stefan,

could you please upload the attached icon to the sourceforge web? Login there 
and click on
https://sourceforge.net/projects/jump-pilot/
on the sf-folder icon left to the title 'The JUMP Pilot Project'.

I'd do it. But you know, I can't :). If there is nobody else currently 
administering the sf.net account, I'd volunteer to do so, as your standby when 
you are away.

.. thanks, ede


<>___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] font for oj logo needed

[edgar . soldin]

sorry wrong list again, please ignore .. ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] Package dnsmasq init-file

[edgar . soldin]

On 27.10.2010 14:13, Bastian Bittorf wrote:

If an already running DHCP-server is found on
the configured interface, the init-script refuses
to start, but does not give a hint why. It took us
some days to track down this behavior in our MANET,
where every wifi/adhoc-node runs it own DHCP-server.
Now syslog is more verbose on this.

Signed-off-by: Bastian Bittorf


dnsmasq.init.patch


Index: package/dnsmasq/files/dnsmasq.init
===
--- package/dnsmasq/files/dnsmasq.init  (Revision 23650)
+++ package/dnsmasq/files/dnsmasq.init  (Arbeitskopie)
@@ -283,7 +283,12 @@
#check for an already active dhcp server on the interface, unless 
'force' is set
config_get_bool force "$cfg" force 0
[ $force -gt 0 ] || {
-   udhcpc -n -q -s /bin/true -t 1 -i $ifname>&-&&  return 0
+   udhcpc -n -q -s /bin/true -t 1 -i $ifname>&-&&  {
+   logger -t dnsmasq \
+   "found already running DHCP-server on interface 
'$ifname'" \
+   "refusing to start, use 'option force 1' to 
override"
+   return 0


shouldn't it return something else than 0 in case of an error?

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [openjump-users] openjump.exe with ini

[edgar . soldin]

The reasons for a unified java launcher would be

- java, which most contributors should understand
- one ini file for all architectures
- one routine to replace them all ;) (set classpath, build cmd line)

sounds worth it to me.

..ede

On 01.09.2010 17:34, Larry Becker wrote:

It doesn't seem like the windows launcher would be improved by calling a java 
launcher.  I don't know about other OSs/distros.

regards,
Larry

On Wed, Sep 1, 2010 at 9:31 AM, mailto:edgar.sol...@web.de>> wrote:

On 01.09.2010 15:46, Larry Becker wrote:

BTW, I have nothing against retiring the bin directory, but it might 
break the startup scripts.


true, I can check and modify the windows and linux scripts, if we agree on 
retiring '/bin'.

And again I want to lobby for a one for all solution.Let me summarize:

- we try to be 'cross-platform'
- but can't support different distributions for each operating system
- user must be able to change the java runtime parameters (e.g. memory 
settings)
- runtime parameters cannot be changed inside the running environment, but 
have to be given as parameters

Only solution I see is a unified launcher (java) run by native launchers 
for the different os's. I like the simplicity of startup scripts, but am pretty 
sure that end users are more confused than supported by them (which should i 
use, how can i configure ...).


regards ede



___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [openjump-users] Trojan in OJ.exe: Positive false message

[edgar . soldin]

Wrong list .. sorry, please ignore .. ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [openjump-users] Trojan in OJ.exe: Positive false message

[edgar . soldin]

I am tired of antivirus detecting viruses in the oj.exe windows starter. We 
can't send to each and every of them that it is a false positive every time.

Solution:
We have a working batch file starter. Having a second starter is a) confusing 
and b) unfortunately unsettling users with virus alerts. Let's abandon the idea 
of oj.exe until we come up with a better solution.

For a while I am thinking of a java based starter. A jar file which does the 
job of the script files on every platform. Usually jar files are linked with 
the runtime.
As a minimal version it could build only the command line and run 
http://mindprod.com/jgloss/exec.html
the java runtime for the platform.

.. regards ede

On 28.08.2010 08:35, Arnd Kielhorn wrote:
> Hi, 
> 
> under Windows XP with Anti virus software AVIRA and with daily actual virus 
> information I just downloaded the official OJ release from Sourceforge and I 
> got the message that in OJ.exe the trojan TR/Crypt.ULPM.Gen was found.
> In my opinion it is a false positive message by could be checked from one of 
> the developers? Thanks
> 
> Arnd
> 

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] svn access

[edgar . soldin]

ups .. wrong projects mailing list .. sorry, please ignore... ede

On 21.07.2010 05:10, Weedy wrote:

On Tue, Jul 20, 2010 at 4:59 AM, mailto:edgar.sol...@web.de>> wrote:

In connection to the work on the gps extension I'd like to request access to the 
sourceforge svn. I think it'd make sense to store the plugin sources there for others 
to see and work with. My sourceforge id is e...@users.sourceforge.net 
 .

Thanks ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org 
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


I don't believe we use SF at all.



___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] svn access

[edgar . soldin]

In connection to the work on the gps extension I'd like to request access to 
the sourceforge svn. I think it'd make sense to store the plugin sources there 
for others to see and work with. My sourceforge id is 
e...@users.sourceforge.net .

Thanks ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] dnsmasq bogus nxdomains

[edgar . soldin]

sweet, simple and effective. You should put the example configuration on
the wiki as well for others suffering the symptoms.

thanks ede

On 16.07.2010 21:57, mickey wrote:
> Hello,
> 
> this patch extends the dnsmasq initscript with an option for bogus-nxdomain.
> 
> From the manpage:
> 
> -B, --bogus-nxdomain=
> Transform replies which contain the IP address given into "No such 
> domain" replies. This is intended to counteract a devious move made by 
> Verisign in September 2003 when they started returning the address of an 
> advertising web page in response to queries for unregistered names, instead 
> of the correct NXDOMAIN response. This option tells dnsmasq to fake the 
> correct response when it sees this behaviour. As at Sept 2003 the IP address 
> being returned by Verisign is 64.94.110.11 
> 
> 
> Example configuration blocking German ISPs Alice and Kabel Deutschland:
> 
> config 'dnsmasq'
> list 'bogusnxdomain' '66.150.2.179'
> list 'bogusnxdomain' '64.236.172.120'
> 
> Signed-Off-By: Mickey Knox 
> 
> 
> --- package/dnsmasq/files/dnsmasq.init(Revision 22184)
> +++ package/dnsmasq/files/dnsmasq.init(Arbeitskopie)
> @@ -53,6 +53,10 @@
>   append args "-H $1"
>  }
>  
> +append_bogusnxdomain() {
> +   append args "-B $1"
> +}
> +
>  dnsmasq() {
>   local cfg="$1"
>   append_bool "$cfg" authoritative "-K"
> @@ -83,6 +87,7 @@
>   config_list_foreach "$cfg" "interface" append_interface
>   config_list_foreach "$cfg" "notinterface" append_notinterface
>   config_list_foreach "$cfg" "addnhosts" append_addnhosts
> + config_list_foreach "$cfg" "bogusnxdomain" append_bogusnxdomain
>   append_parm "$cfg" "leasefile" "-l"
>   append_parm "$cfg" "resolvfile" "-r"
>   append_parm "$cfg" "tftp_root" "--tftp-root"
> 
> 
> 
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [openjump-users] Re: VS: Off-list: Mobile GPS solution in OJ

[edgar . soldin]

On 10.06.2010 16:33, Arnd Kielhorn wrote:

Hi Ede,

as I just checked that it would be possible to help out with a gps mouse again. 
But we need a raw plan in which time frame You will need the gps mouse.


I just now target the week from 12-16.7.  Is it possible this soon? Do 
you still have my address. I'll send it anyway off-list.




So we need to have a concrete task plan for calculating the time You need to 
develope. My suggestion (your screenshot show the most things) is to get a tool 
which...

...work with different projections (e.g. WGS84 from GPS with map underlay in 
UTM; does have geotools nice libraries or tools for coordinate transformations?)


I'll primarily try to reanimate the gps extension. If the cts extension 
is installed and working properly it does what Jukka answered:


On 11.06.2010 09:22, Jukka Rahkonen wrote:

For the GPS connector project it might be enough to have a working example
about how to reproject from native GPS output to some other projection
on-the-fly, and instructions about how to add new supported projections.
Screen capture suggests that this is already mostly implemented.



...connecting a gps via serial port (allow different settings for the COM port, 
baud rate etc.)(I think bluetooth gps receivers work with virtual serial COM 
ports)
...optionally have automated panning by actual gps position
...allow to have any zoom levels


the above should be working already. Also adding points from gps is.


...allow to draw point from the actual GPS position (perhaps with an option to 
let the tool claculate an average position from the last XY gps positions)
...allow to draw a border polygon or line from gps positions by running or 
driving with the gps receiver
...perhaps for later enhancements: simple navigation to specific coordinates



These are not implemented. I do not intend to do this for now.


Another thing is that I can suggest to pay a part of the needed money if I can 
get a official invoice. For me it is easier than make a donation.
What are other interested people in the community think about it. Who is 
willing to take another part?


Jukka came forward to pay the amount today. Maybe you (or your 
companies) want to share the amount equally? I'd suggest that the first 
half should be paid in advance, just to be sure of the commitment. The 
second can be paid after it is done. And I repeat. All I am going to do 
is to reanimate the gps extension for the current release of openjump. I 
am not planning to feature enhance it for now. The features are


- serial gps mouse support (possibly gpsd also), protocols as supported 
by gpsylon (nmea,garmin,sirf?)
- track viewport (view menu) with the possibility to switch on/off and 
select the task to track, if several are opened

- statusbar output of current coordinate if any
- the point add from gps (edit menu), as far as i remember undoable

Regards ede



Kindyl regards
Arnd


You probably need to consult your companies (tax) accountant.

My guess would be, that it is called donation it has to go go to a non
profit organisation (ngo), which I obviously am not ;)
I am happy on writing invoices to several parties, with and without vat,
depending if they are german or not.

If I'd really do it I'd also need a gps mouse again. Arnd could you help
out again then?

.. ede


On 10.06.2010 09:22, Arnd Kielhorn wrote:

Hello,

it sounds great if Ede would make this tool and Stefan and Larry would

help and evaluate.

But I have a question about the good idea financing the work by

donation.

To pay a part of it, it is important to get an official quittance or

invoice as a verication for the financial (tax) adminstration. Is it possible
when doing it via donation or should we find another way?


Kindly regards
Arnd


well.. If I would know about that stuff I would help.. but having Larry
on board is already a good step :)

and then w.r.t. funding i) I would feel bad if Jukka pays that out of
his own pocket, ii) I am not sure, but Sourceforge should have some
donation tools - need to check that.
The things here is that we would start with a complete new page full of
issues... i.e. we probably would need to form a legal entity?

stefan

Larry Becker wrote:

I'm interested in seeing GPS capability in OpenJUMP so I could

certainly

give some assistance to Edgar if needed in the area of moving map
performance, although there may be others who have more experience

with

this topic.  I don't have a use for GPS at work yet, but I do have a
personal GPS-enabled android phone that I would like to use with OJ,

so

I'm also very interested in Joe's idea, and I might be able to work on
the android wifi/GPS service at some point.

regards,
Larry Becker

On Wed, Jun 9, 2010 at 10:57 AM, Jukka Rahkonen
mailto:jukka.rahko...@latuviitta.fi>>

wrote:


  Edgar Soldin wrote:

   >   On 08.06.2010 16:48, Larry Becker wrote:
   >>   Seems like GPSylon is a lar

Re: [OpenWrt-Devel] failed to install feed oprofile

[edgar . soldin]

You need to use kernel 2.6.
Enable
menuconfig->Global build settings->Compile the kernel with profiling enabled
then enable
menuconfig->Development->oprofile

Don't forget to recompile the kernel.

ede


On 24.05.2010 11:13, oii...@aol.com wrote:



thank you, I couldn't find the oprofile option in menuconfig, I tried.


-Original Message-
From: Bernhard Loos 
To: OpenWrt Development List 
Sent: Mon, May 24, 2010 5:08 pm
Subject: Re: [OpenWrt-Devel] failed to install feed oprofile

You also have to enable it in menuconfig.



2010/5/24mailto:oii...@aol.com>>:






 $ find packages/ -name"oprofile"



 package/feeds/packages/oprofile







 I don't quite understant that but there's no opcontrol related programs



 after the system is running.



 am I doing anything incorrectly?











 -Original Message-



 From: oiioeumailto:oii...@aol.com>>



 To: openwrt-develmailto:openwrt-devel@lists.openwrt.org>>



 Sent: Mon, May 24, 2010 4:27 pm



 Subject: [OpenWrt-Devel] failed to install feed oprofile











 in r21560 I couldn't find oprofile option in menuconfig, what I did was







 $ ./scripts/feeds update



 $ ./scripts/feeds install -d y oprofile







 anyone ever successfully installed oprofile?







 Thanks!







 ___







 openwrt-devel mailing list







 openwrt-devel@lists.openwrt.org  







 https://lists.openwrt.org/mailman/listinfo/openwrt-devel



















 ___



 openwrt-devel mailing list



 openwrt-devel@lists.openwrt.org  



 https://lists.openwrt.org/mailman/listinfo/openwrt-devel










___

openwrt-devel mailing list

openwrt-devel@lists.openwrt.org  

https://lists.openwrt.org/mailman/listinfo/openwrt-devel





___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [backfire] WRT54G flash space problem

[edgar . soldin]

On 11.05.2010 17:25, Stefan Monnier wrote:

but wouldn't the increase in the kernel image actually equal the
decrease in the squash image and therefore the size of the rootfs_data
stay the same? Both are lzma compressed.


I expect that a kernel with some modules built-in will be smaller
(both in terms of flash space and in terms of RAM use) than the same
kernel plus the same modules compiled as modules.
Whether the difference is significant or negligible, I don't know.



why do you think so? .. especially the ram usage part. ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [backfire] WRT54G flash space problem

[edgar . soldin]

On 10.05.2010 23:47, Bernhard Loos wrote:
> 2010/5/10 Bernhard Loos :
>> 2010/5/10 Matthias Buecher / Germany :
>>> The "linux" partition spans over the kernel and the complete rootfs for
>>> flashing.
>>> The maximum kernel size is 0x000bc000 (begin of "rootfs") minus
>>> 0x0004 (begin of "linux") equals 0x0007c000 (496KB).
>>>
>>> Maddes
>>
>> This is not the maximum kernel size, it's only the current kernel size.
>> You could probably get a few kb more flash space (32 at average) by
>> changing the aligment of the rootfs, squashfs is read only, so it
>> doesn't have to start at an erase block boundary.
> 
> To clarify myself, the size is calculated dynamically, so compiling
> stuff into the kernel doesn't gain much.
> 

at least for sqashfs images. All others would profit from it. Are there
other space sensitive platforms?

..ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [backfire] WRT54G flash space problem

[edgar . soldin]

Then it'd make total sense to stuff in whatever fits there .. thanks for
the enlightenment, ede

On 10.05.2010 23:38, Matthias Buecher / Germany wrote:
> The "linux" partition spans over the kernel and the complete rootfs for
> flashing.
> The maximum kernel size is 0x000bc000 (begin of "rootfs") minus
> 0x0004 (begin of "linux") equals 0x0007c000 (496KB).
> 
> Maddes
> 
> On 10.05.2010 23:34, edgar.sol...@web.de wrote:
>> are these sizes fixed or calculated according the space requirement?
>> Looks like the linux size is fixed, what is the maximum size for a
>> kernel on wrt54g?
>>
>> .. ede
>>
>> On 10.05.2010 23:28, Matthias Buecher / Germany wrote:
>>> Kernel and rootfs are in two different mtd partitions on the WRT54G:
>>>
>>> # dmesg
>>> ...
>>> Creating 5 MTD partitions on "Physically mapped flash":
>>> 0x-0x0004 : "cfe"
>>> 0x0004-0x003f : "linux"
>>> 0x000bc000-0x0021 : "rootfs"
>>> mtd: partition "rootfs" doesn't start on an erase block boundary --
>>> force read-only
>>> 0x003f-0x0040 : "nvram"
>>> 0x0021-0x003f : "rootfs_data"
>>> ...
>>>
>>> So it is moved from "rootfs" to "linux" in this case.
>>>
>>> Maddes
>>>
>>> On 10.05.2010 22:53, edgar.sol...@web.de wrote:
 but wouldn't the increase in the kernel image actually equal the
 decrease in the squash image and therefore the size of the rootfs_data
 stay the same? Both are lzma compressed.

 ..ede


 On 10.05.2010 19:16, Matthias Buecher / Germany wrote:
> It may not downsize the packages themselves, but moving kernel mods from
> rootfs to the kernel image will reduce the rootfs size. Leaving more
> space for JFFS2 rootfs_data.
>
> Having a "K" setting for kernel options would be great.
> Will try to have a look at it during the next weeks.
>
> Thanks for all your help
> Maddes
>
> On 10.05.2010 17:20, edgar.sol...@web.de wrote:
>> there is partly in
>> https://dev.openwrt.org/browser/trunk/include/kernel-defaults.mk
>> line 101
>>
>> you can actually add
>> CONFIG_KERNEL_*
>> entries to your .config and they are copied over as CONFIG_* to the
>> kernel config. All that's missing is a menuconfig interface for that.
>>
>> But at least for routers using lzma squashfs for the initial image this
>> will probably not downsize anything.
>>
>> .. ede
>>
>>
>> On 10.05.2010 16:19, Stefan Monnier wrote:
 In 'make menuconfig' I included them with 'Y' instead of 'M'.
 According to my (newbie) knowledge that adds them to the kernel image.
 Can somebody please confirm my understanding? Or at least prove me
 wrong? :D
>>> Damn! I thought you had found a clever way to get them compiled into
>>> the kernel.
>>> I still hope some day someone will write the extra code needed so that
>>> "make menuconfig" can be told to build some modules right into
>>> the kernel.
>>>
>>>
>>>  Stefan
>>>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>> ___
>>> openwrt-devel mailing list
>>> openwrt-devel@lists.openwrt.org
>>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [backfire] WRT54G flash space problem

[edgar . soldin]

are these sizes fixed or calculated according the space requirement?
Looks like the linux size is fixed, what is the maximum size for a
kernel on wrt54g?

.. ede

On 10.05.2010 23:28, Matthias Buecher / Germany wrote:
> Kernel and rootfs are in two different mtd partitions on the WRT54G:
> 
> # dmesg
> ...
> Creating 5 MTD partitions on "Physically mapped flash":
> 0x-0x0004 : "cfe"
> 0x0004-0x003f : "linux"
> 0x000bc000-0x0021 : "rootfs"
> mtd: partition "rootfs" doesn't start on an erase block boundary --
> force read-only
> 0x003f-0x0040 : "nvram"
> 0x0021-0x003f : "rootfs_data"
> ...
> 
> So it is moved from "rootfs" to "linux" in this case.
> 
> Maddes
> 
> On 10.05.2010 22:53, edgar.sol...@web.de wrote:
>> but wouldn't the increase in the kernel image actually equal the
>> decrease in the squash image and therefore the size of the rootfs_data
>> stay the same? Both are lzma compressed.
>>
>> ..ede
>>
>>
>> On 10.05.2010 19:16, Matthias Buecher / Germany wrote:
>>> It may not downsize the packages themselves, but moving kernel mods from
>>> rootfs to the kernel image will reduce the rootfs size. Leaving more
>>> space for JFFS2 rootfs_data.
>>>
>>> Having a "K" setting for kernel options would be great.
>>> Will try to have a look at it during the next weeks.
>>>
>>> Thanks for all your help
>>> Maddes
>>>
>>> On 10.05.2010 17:20, edgar.sol...@web.de wrote:
 there is partly in
 https://dev.openwrt.org/browser/trunk/include/kernel-defaults.mk
 line 101

 you can actually add
 CONFIG_KERNEL_*
 entries to your .config and they are copied over as CONFIG_* to the
 kernel config. All that's missing is a menuconfig interface for that.

 But at least for routers using lzma squashfs for the initial image this
 will probably not downsize anything.

 .. ede


 On 10.05.2010 16:19, Stefan Monnier wrote:
>> In 'make menuconfig' I included them with 'Y' instead of 'M'.
>> According to my (newbie) knowledge that adds them to the kernel image.
>> Can somebody please confirm my understanding? Or at least prove me
>> wrong? :D
> Damn! I thought you had found a clever way to get them compiled into
> the kernel.
> I still hope some day someone will write the extra code needed so that
> "make menuconfig" can be told to build some modules right into
> the kernel.
>
>
>  Stefan
>
>>> ___
>>> openwrt-devel mailing list
>>> openwrt-devel@lists.openwrt.org
>>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [backfire] WRT54G flash space problem

[edgar . soldin]

but wouldn't the increase in the kernel image actually equal the
decrease in the squash image and therefore the size of the rootfs_data
stay the same? Both are lzma compressed.

..ede


On 10.05.2010 19:16, Matthias Buecher / Germany wrote:
> It may not downsize the packages themselves, but moving kernel mods from
> rootfs to the kernel image will reduce the rootfs size. Leaving more
> space for JFFS2 rootfs_data.
> 
> Having a "K" setting for kernel options would be great.
> Will try to have a look at it during the next weeks.
> 
> Thanks for all your help
> Maddes
> 
> On 10.05.2010 17:20, edgar.sol...@web.de wrote:
>> there is partly in
>> https://dev.openwrt.org/browser/trunk/include/kernel-defaults.mk
>> line 101
>>
>> you can actually add
>> CONFIG_KERNEL_*
>> entries to your .config and they are copied over as CONFIG_* to the
>> kernel config. All that's missing is a menuconfig interface for that.
>>
>> But at least for routers using lzma squashfs for the initial image this
>> will probably not downsize anything.
>>
>> .. ede
>>
>>
>> On 10.05.2010 16:19, Stefan Monnier wrote:
 In 'make menuconfig' I included them with 'Y' instead of 'M'.
 According to my (newbie) knowledge that adds them to the kernel image.
 Can somebody please confirm my understanding? Or at least prove me
 wrong? :D
>>>
>>> Damn! I thought you had found a clever way to get them compiled into
>>> the kernel.
>>> I still hope some day someone will write the extra code needed so that
>>> "make menuconfig" can be told to build some modules right into
>>> the kernel.
>>>
>>>
>>>  Stefan
>>>
> 
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [backfire] WRT54G flash space problem

[edgar . soldin]

there is partly in
https://dev.openwrt.org/browser/trunk/include/kernel-defaults.mk
line 101

you can actually add
CONFIG_KERNEL_*
entries to your .config and they are copied over as CONFIG_* to the 
kernel config. All that's missing is a menuconfig interface for that.


But at least for routers using lzma squashfs for the initial image this 
will probably not downsize anything.


.. ede


On 10.05.2010 16:19, Stefan Monnier wrote:

In 'make menuconfig' I included them with 'Y' instead of 'M'.
According to my (newbie) knowledge that adds them to the kernel image.
Can somebody please confirm my understanding? Or at least prove me wrong? :D


Damn! I thought you had found a clever way to get them compiled into
the kernel.
I still hope some day someone will write the extra code needed so that
"make menuconfig" can be told to build some modules right into
the kernel.


 Stefan

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [backfire] WRT54G flash space problem

[edgar . soldin]

true, my bad, actually one can see it in the end of a make run, how the
packages (incl. kmods) are installed to the image filesystem.

thanks ede

On 09.05.2010 18:19, Bernhard Loos wrote:
> Actually, Y in menuconfig doesn't add the modules into the kernel,
> they will still be kernel modules. It only places the modules directly
> in the image and is in no way different from Y for programs. M creates
> packages for the modules/program without placing it in the image.
> If you want to compile a module into the kernel, you have to choose Y
> in kernel_menuconfig.
> 
>   Bernhard
> 
> 2010/5/9  :
>> That's how it works. Y adds kernel modules to the kernel, and programs
>> to the image.
>>
>> ..ede
>>
>> On 09.05.2010 18:10, Matthias Buecher / Germany wrote:
>>> In 'make menuconfig' I included them with 'Y' instead of 'M'.
>>> According to my (newbie) knowledge that adds them to the kernel image.
>>> Can somebody please confirm my understanding? Or at least prove me wrong? :D
>>>
>>> Maddes
>>>
>>> On 09.05.2010 17:56, Stefan Monnier wrote:
> Put all kmods (2) I needed into the kernel.

 How?


 Stefan

>>>
>>> ___
>>> openwrt-devel mailing list
>>> openwrt-devel@lists.openwrt.org
>>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [backfire] WRT54G flash space problem

[edgar . soldin]

That's how it works. Y adds kernel modules to the kernel, and programs
to the image.

..ede

On 09.05.2010 18:10, Matthias Buecher / Germany wrote:
> In 'make menuconfig' I included them with 'Y' instead of 'M'.
> According to my (newbie) knowledge that adds them to the kernel image.
> Can somebody please confirm my understanding? Or at least prove me wrong? :D
> 
> Maddes
> 
> On 09.05.2010 17:56, Stefan Monnier wrote:
>>> Put all kmods (2) I needed into the kernel.
>>
>> How?
>>
>>
>> Stefan
>>
> 
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] Stopping watchdog

[edgar . soldin]

On 03.05.2010 15:59, Yury Polyanskiy wrote:

On Mon, 3 May 2010 09:35:59 +
Vasilis Tsiligiannis  wrote:


+   [ -c /dev/watchdog ]&&  echo "V">  /dev/watchdog


Why is this needed? busybox watchdog applet writes the magic on shutdown.




What is magic? In this context .. thanks ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [backfire][bug] setting LAN mac address, makes router inaccessible from LAN

[edgar . soldin]

On 29.04.2010 20:38, Matthias Buecher / Germany wrote:
> 
> On 29.04.2010 10:34, edgar.sol...@web.de wrote:
>>
>>> So for others without serial access or JTAG, this issue is like a
>>> bricked router.
>>> This issue should definitely be on the known problems page [1] and
>>> verified on other devices.
>>>
>>
>> Wouldn't it still be possible to tftp flash the router? Looks like it ..
>> ede
> 
> Yes, it is possible under special circumstances.
> Still, mentioning and fixing the issue is the correct solution.
> 

jepp .. totally right. Just wanted to mention another way to reanimate
the router pretending to be bricked. thanks for looking into it.


.. ede
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [backfire][bug] setting LAN mac address, makes router inaccessible from LAN

[edgar . soldin]

So for others without serial access or JTAG, this issue is like a
bricked router.
This issue should definitely be on the known problems page [1] and
verified on other devices.



Wouldn't it still be possible to tftp flash the router? Looks like it .. ede


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel