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] [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] [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 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 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] 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

[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] 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

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

[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] 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] [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

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] [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] 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

[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] 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

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] 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

[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] [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] 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: [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 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: 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 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

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: [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: [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] 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] 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] 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] 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] 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] [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] [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 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

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][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 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 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] 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] 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] 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] 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

[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] 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

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] 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 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] 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] 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]

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]

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] [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

[OpenWrt-Devel] new hotplug-radiobutton package

[Edgar Soldin]

Attached you will find a new admin package, which contains a hotplug script for 
switching wifi on/off if the router has a ses button. This is
readymade and tested for wrt54g(s,l) and wl500w models. Makefile is provided.
Youre welcome to integrate it in the packages feed, as it is very openwrt 
specific.

kind regards ede



hotplug-radiobutton.tgz
Description: Binary data
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] hotplug radiobutton

[edgar . soldin]

Hi all,

https://dev.openwrt.org/ticket/5256
is still open and waiting for check in.

thanks ede


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

[OpenWrt-Devel] new package hotplug radiobutton script

[edgar . soldin]

Hi all,

2 months ago I created the following ticket.
https://dev.openwrt.org/attachment/ticket/5256/
It announces a new ses button wifi switch script.

I assume it was not added because of the inappropriate format. Today I 
added a patch to the ticket which holds the new package changes against 
the current packages repository. You will find it here

https://dev.openwrt.org/attachment/ticket/5256/radiobutton.patch

thank you very much... ede

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

Re: [OpenWrt-Devel] IXP4XX , LUCI can't work. Browser can't open WEB.

[edgar . soldin]

in case you used the luci trunk. There was a missing dependency which 
prevented luci from starting properly. You can try


$ /etc/init.d/lucid restart
lucid[1022]: Failed to initialize daemon https: 
/usr/lib/lua/luci/sys.lua:33: mo

dule 'iwinfo' not found:
no field package.preload['iwinfo']
no file './iwinfo.lua'
no file '/usr/share/lua/iwinfo.lua'
no file '/usr/share/lua/iwinfo/init.lua'
no file '/usr/lib/lua/iwinfo.lua'
no file '/usr/lib/lua/iwinfo/init.lua'
no file './iwinfo.so'
no file '/usr/lib/lua/iwinfo.so'
no file '/usr/lib/lua/loadall.so'

This is fixed in rev 5249 (49h ago).

regards ede

On 11.08.2009 10:28, linux_pro wrote:

SVN 17202-17223   , LUCI can't work。
Browser can't open web。

GCC 4.1.2  UCLIBC 0.30.1

I user  MI424-wr


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

Re: [OpenWrt-Devel] IXP4XX , LUCI can't work. Browser can't open WEB.

[edgar . soldin]

did you install the luci theme?
anything in logread or dmesg?

 ... ede

On 11.08.2009 10:49, linux_pro wrote:

i user luci svn ： 5252

ps w  display
lua -lluci.lucid -e luci.lucid.start()

i not know what's wrong,
Looks is all right

2009/8/11 linux_pro:

i try it
but display:
stopping lucid superserver：lucid
starting lucid supersrever: lucid


Still unable to open WEB

2009/8/11 linux_pro:

thanks，i try it.

2009/8/11:

in case you used the luci trunk. There was a missing dependency which
prevented luci from starting properly. You can try

$ /etc/init.d/lucid restart
lucid[1022]: Failed to initialize daemon https:
/usr/lib/lua/luci/sys.lua:33: mo
dule 'iwinfo' not found:
no field package.preload['iwinfo']
no file './iwinfo.lua'
no file '/usr/share/lua/iwinfo.lua'
no file '/usr/share/lua/iwinfo/init.lua'
no file '/usr/lib/lua/iwinfo.lua'
no file '/usr/lib/lua/iwinfo/init.lua'
no file './iwinfo.so'
no file '/usr/lib/lua/iwinfo.so'
no file '/usr/lib/lua/loadall.so'

This is fixed in rev 5249 (49h ago).

regards ede

On 11.08.2009 10:28, linux_pro wrote:


SVN 17202-17223   , LUCI can't work。
Browser can't open web。

GCC 4.1.2  UCLIBC 0.30.1

I user  MI424-wr


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

Re: [OpenWrt-Devel] IXP4XX , LUCI can't work. Browser can't open WEB.

[edgar . soldin]

then something else is wrong and luci not working only a symptom .. 
smells as if your networking has problems .. ede


On 11.08.2009 11:03, linux_pro wrote:

y, default is install luci theme. I checked.

on the ttyS0, top or dmesg is work.
but user telnet ,top or dmesg is"Freeze"

2009/8/11:

did you install the luci theme?
anything in logread or dmesg?

  ... ede

On 11.08.2009 10:49, linux_pro wrote:


i user luci svn ： 5252

ps w  display
lua -lluci.lucid -e luci.lucid.start()

i not know what's wrong,
Looks is all right

2009/8/11 linux_pro:


i try it
but display:
stopping lucid superserver：lucid
starting lucid supersrever: lucid


Still unable to open WEB

2009/8/11 linux_pro:


thanks，i try it.

2009/8/11:


in case you used the luci trunk. There was a missing dependency which
prevented luci from starting properly. You can try

$ /etc/init.d/lucid restart
lucid[1022]: Failed to initialize daemon https:
/usr/lib/lua/luci/sys.lua:33: mo
dule 'iwinfo' not found:
no field package.preload['iwinfo']
no file './iwinfo.lua'
no file '/usr/share/lua/iwinfo.lua'
no file '/usr/share/lua/iwinfo/init.lua'
no file '/usr/lib/lua/iwinfo.lua'
no file '/usr/lib/lua/iwinfo/init.lua'
no file './iwinfo.so'
no file '/usr/lib/lua/iwinfo.so'
no file '/usr/lib/lua/loadall.so'

This is fixed in rev 5249 (49h ago).

regards ede

On 11.08.2009 10:28, linux_pro wrote:


SVN 17202-17223   , LUCI can't work。
Browser can't open web。

GCC 4.1.2  UCLIBC 0.30.1

I user  MI424-wr


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

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

Re: [OpenWrt-Devel] IXP4XX , LUCI can't work. Browser can't open WEB.

[edgar . soldin]

you can try to narrow down the changeset that causes the problem by 
checking out revisions, buildroot them and flash them on the device .. ede


On 12.08.2009 04:27, linux_pro wrote:

I very sure , SVN 17220  LUCI can't work.
i backup SVN 15XXX, is ok.
so,my mi424(ixp425) hardware is OK.

HI, Mark Kelly,i user BIG ENDIAN is OK.

2009/8/11 Mark Kelly:

Luci is working fine on r17207 on my IXP4xx board, but it was broken due to
a Big Endian issue on the IXP4xx a couple of weeks ago.


On Tue, 2009-08-11 at 05:06 -0400, edgar.sol...@web.de wrote:

then something else is wrong and luci not working only a symptom ..
smells as if your networking has problems .. ede

On 11.08.2009 11:03, linux_pro wrote:

y, default is install luci theme. I checked.

on the ttyS0, top or dmesg is work.
but user telnet ,top or dmesg is"Freeze"

2009/8/11:

did you install the luci theme?
anything in logread or dmesg?

   ... ede

On 11.08.2009 10:49, linux_pro wrote:


i user luci svn ： 5252

ps w  display
lua -lluci.lucid -e luci.lucid.start()

i not know what's wrong,
Looks is all right

2009/8/11 linux_pro:


i try it
but display:
stopping lucid superserver：lucid
starting lucid supersrever: lucid


Still unable to open WEB

2009/8/11 linux_pro:


thanks，i try it.

2009/8/11:


in case you used the luci trunk. There was a missing dependency which
prevented luci from starting properly. You can try

$ /etc/init.d/lucid restart
lucid[1022]: Failed to initialize daemon https:
/usr/lib/lua/luci/sys.lua:33: mo
dule 'iwinfo' not found:
 no field package.preload['iwinfo']
 no file './iwinfo.lua'
 no file '/usr/share/lua/iwinfo.lua'
 no file '/usr/share/lua/iwinfo/init.lua'
 no file '/usr/lib/lua/iwinfo.lua'
 no file '/usr/lib/lua/iwinfo/init.lua'
 no file './iwinfo.so'
 no file '/usr/lib/lua/iwinfo.so'
 no file '/usr/lib/lua/loadall.so'

This is fixed in rev 5249 (49h ago).

regards ede

On 11.08.2009 10:28, linux_pro wrote:


SVN 17202-17223   , LUCI can't work。
Browser can't open web。

GCC 4.1.2  UCLIBC 0.30.1

I user  MI424-wr


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

___
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] IXP4XX , LUCI can't work. Browser can't open WEB.

[edgar . soldin]

seems like the route back is not properly set .. ede

On 12.08.2009 10:31, linux_pro wrote:

O!
i user ttyS0 on the mi424, ping my PC IP 192.168.1.26,
display time out
but on the my PC, ping MI424 192.168.1.1, is OK
i iptables -F
iptables -Z

not diff


2009/8/12 linux_pro:

thanks ede

i try to do.


2009/8/12:

you can try to narrow down the changeset that causes the problem by checking
out revisions, buildroot them and flash them on the device .. ede

On 12.08.2009 04:27, linux_pro wrote:


I very sure , SVN 17220  LUCI can't work.
i backup SVN 15XXX, is ok.
so,my mi424(ixp425) hardware is OK.

HI, Mark Kelly,i user BIG ENDIAN is OK.

2009/8/11 Mark Kelly:


Luci is working fine on r17207 on my IXP4xx board, but it was broken due
to
a Big Endian issue on the IXP4xx a couple of weeks ago.


On Tue, 2009-08-11 at 05:06 -0400, edgar.sol...@web.de wrote:

then something else is wrong and luci not working only a symptom ..
smells as if your networking has problems .. ede

On 11.08.2009 11:03, linux_pro wrote:


y, default is install luci theme. I checked.

on the ttyS0, top or dmesg is work.
but user telnet ,top or dmesg is"Freeze"

2009/8/11:


did you install the luci theme?
anything in logread or dmesg?

   ... ede

On 11.08.2009 10:49, linux_pro wrote:


i user luci svn ： 5252

ps w  display
lua -lluci.lucid -e luci.lucid.start()

i not know what's wrong,
Looks is all right

2009/8/11 linux_pro:


i try it
but display:
stopping lucid superserver：lucid
starting lucid supersrever: lucid


Still unable to open WEB

2009/8/11 linux_pro:


thanks，i try it.

2009/8/11:


in case you used the luci trunk. There was a missing dependency
which
prevented luci from starting properly. You can try

$ /etc/init.d/lucid restart
lucid[1022]: Failed to initialize daemon https:
/usr/lib/lua/luci/sys.lua:33: mo
dule 'iwinfo' not found:
 no field package.preload['iwinfo']
 no file './iwinfo.lua'
 no file '/usr/share/lua/iwinfo.lua'
 no file '/usr/share/lua/iwinfo/init.lua'
 no file '/usr/lib/lua/iwinfo.lua'
 no file '/usr/lib/lua/iwinfo/init.lua'
 no file './iwinfo.so'
 no file '/usr/lib/lua/iwinfo.so'
 no file '/usr/lib/lua/loadall.so'

This is fixed in rev 5249 (49h ago).

regards ede

On 11.08.2009 10:28, linux_pro wrote:


SVN 17202-17223   , LUCI can't work。
Browser can't open web。

GCC 4.1.2  UCLIBC 0.30.1

I user  MI424-wr


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


___
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

[OpenWrt-Devel] hotplug radiobutton package

[edgar . soldin]

Hello Jow and Felix and all developers.

Is there any reason that this new package
https://dev.openwrt.org/ticket/5256
is whether commented nor committed to trunk?
I also announced it 2 times on this list.

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

[OpenWrt-Devel] PING .. hotplug radiobutton package - please check in

[edgar . soldin]

Hello Jow and Felix and all developers.

Is there any reason that this new package
https://dev.openwrt.org/ticket/5256
is whether commented nor committed to trunk?

This is the 4th submission on this topic. Please somebody answer.

Thanks ede

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

Re: [OpenWrt-Devel] WiFi on Linksys WRT54GL

[edgar . soldin]

You have the proprietary _and_ the open source driver under 2.4.
Do both show this issue?

... ede


On 21.09.2009 10:05, Vladimir Voronkov wrote:

Hi,

I tried 2.4 kernel and the problem of the driver is the same as why it was 
removed in 2.5 kernels, I suppose. WiFi stops working if the router is burdened 
with some task for some time (for example if PC in LAN is downloading something 
and the router is busy with transferring data during about 5 minutes). Also I 
couldn't manage with openl2tp thing started under 2.4.

Is there some work doing about this issue?

Thank,
Vladimir


-Original Message-
From: openwrt-devel-boun...@lists.openwrt.org [mailto:openwrt-devel-
boun...@lists.openwrt.org] On Behalf Of Jo-Philipp Wich
Sent: Friday, September 18, 2009 6:23 PM
To: OpenWrt Development List
Subject: Re: [OpenWrt-Devel] WiFi on Linksys WRT54GL

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi.


As far as I understand, in release 8.09 b43 driver is removed.


Right.


So the question is - when these drives be fixed or replaced with the
working ones?


Working drivers are in the brcm-2.4 builds of OpenWrt.
Also b43 support is available in bcm47xx trunk builds.


Regards,
JoW
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqzl7IACgkQdputYINPTPNyzgCgoHcsDMSRxDj7McBf26JEvweB
L3YAoKOYe8RGRUHq5/BlbGTVs+cjabqy
=5kAe
-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 mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Packages were found, but none compatible with the architectures configured

[edgar . soldin]

I recall having similar issues when using a recent trunk compiled image 
(after the kernel upgrade) and trying to use a kmod package from the 
8.09.1 repository ... I guess it's the kernel version.


ede

On 20.10.2009 12:33, ZioPRoTo (Saverio Proto) wrote:

# opkg install kmod-sched
Collected errors:
  * Packages were found, but none compatible with the architectures configured


I had the same problem with weekend upgrading some packages on same
devices running 8.09.1 tag, and packages were compiled using the trunk
toolchain.

I don't know exactly if this is your case, but for example the Atheros
target changed architecture name from "mips" to
"atheros_uClibc-0.9.30.1".

So if your firmware was compiled before the target name change, and
you are now compiling the packages with a recent toolchain, the opkg
will fail its check because it thinks you are installing a package for
a wrong target.

I have no idea if this only applies for the Atheros target or also for
other targets.

Saverio
___
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] [OpenWrt] #6081: Wifi toggle package propose

[edgar . soldin]

I checked the trunk version of "wifi" and calling "wifi up" or just
"wifi" is the same. This means that this script can't enable
connection that have the wifi disabled at the config file. Also that
is impossible to use a default off on power up.


true .. that can only be achieved by toggling the uci config variables.
hotplug-radiobutton was never meant to switch the default. A router 
should switch to a default on reboot. What if nobody is around to push 
the button but wireless is needed but it was disabled before it was 
rebooted?



I use the following script:


SNIP


So it iterates over every wifi-device at /etc/config/wireless and
disable/enable it.
So I think it's also generic for whatever you want.


it is ..


So the question is: is possible to have more than on wifi-device?


yes it is..


If so all solutions that I see have...more issues.


question is what do you want. A simple switch on/off of wireless 
(meaning all wireless devices) or a more complicated configurable script 
switching just some devices..



... best regards ede


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

Re: [OpenWrt-Devel] building trunk stuck at scripts/kconfig/conf trying to read from stdin

[edgar . soldin]

probably the question if you want to enable kernel float emulation.

QUESTIONs:
Is there a way to disable this prompt?
How do I enable a softfloat in the toolchain?

Thanks ede


Hi Timo,

Am 22.11.2009 12:11, schrieb Timo Juhani Lindfors:

and "strace -p ..." confirmed that the last process was blocked in
reading from stdin. After I hit enter the build continued -- is this a
bug in the build scripts?


Probably something missing in the kernels .config. A 'make V=99' would 
have showed it.



 - jan
___
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] Upgrade the babel package, renaming it to babeld

[edgar . soldin]

You manage the openwrt svn by a git interface?

.. ede

I don't know how you can force svn to generate proper patches - I use
git and it's better at handling such things.

- Felix
   


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

[OpenWrt-Devel] category patches for libpar2 & rdiff-backup

[edgar . soldin]

Hi all,

find attached two patches that fix a wrong categorizations for the 
mentioned packages.


libpar2 belongs in libraries
rdiff-backup in utilities

Thanks ede

Index: feeds/packages/libs/libpar2/Makefile
===
--- feeds/packages/libs/libpar2/Makefile	(Revision 18610)
+++ feeds/packages/libs/libpar2/Makefile	(Arbeitskopie)
@@ -20,8 +20,8 @@
 include $(INCLUDE_DIR)/package.mk
 
 define Package/libpar2
-  SECTION:=net
-  CATEGORY:=Network
+  SECTION:=libs
+  CATEGORY:=Libraries
   DEPENDS:=+libsigcxx
   TITLE:=A library for performing common tasks related to PAR recovery sets
 endef
Index: feeds/packages/utils/rdiff-backup/Makefile
===
--- feeds/packages/utils/rdiff-backup/Makefile	(Revision 18610)
+++ feeds/packages/utils/rdiff-backup/Makefile	(Arbeitskopie)
@@ -21,9 +21,9 @@
 -include $(if $(DUMP),,$(STAGING_DIR)/mk/python-package.mk)
 
 define Package/rdiff-backup
-  SUBMENU:=Python
-  SECTION:=lang
-  CATEGORY:=Languages
+  SUBMENU:=backup
+  SECTION:=utils
+  CATEGORY:=Utilities
   TITLE:=Incremental backup utility
   URL:=http://www.nongnu.org/rdiff-backup
   DEPENDS:=+python-mini +librsync +libpopt +openssl-util
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] bump and fix strongswan 2.8

[edgar . soldin]

Hi all,

the attached patch bumps strongswan 2.8 for 2.4 kernels to latest 
version 2.8.11 and fixes a compile error because of the missing circleq 
implementation in uclibc.


regards ede

PS: can somebody point me to a good guide to set up strongswan with 
pptpd on openwrt? Thanks.
Index: feeds/packages/net/strongswan/patches/400-pluto-fix_CIRCLEQ.patch
===
--- feeds/packages/net/strongswan/patches/400-pluto-fix_CIRCLEQ.patch	(Revision 0)
+++ feeds/packages/net/strongswan/patches/400-pluto-fix_CIRCLEQ.patch	(Revision 0)
@@ -0,0 +1,149 @@
+diff -Nurp strongswan-2.8.11.orig/linux/include/circ-queue.h strongswan-2.8.11.queue/linux/include/circ-queue.h
+--- strongswan-2.8.11.orig/linux/include/circ-queue.h	1970-01-01 01:00:00.0 +0100
 strongswan-2.8.11.queue/linux/include/circ-queue.h	2009-12-02 19:11:31.414549616 +0100
+@@ -0,0 +1,131 @@
++/*
++ * Copyright (c) 1991, 1993
++ *	The Regents of the University of California.  All rights reserved.
++ *
++ * Redistribution and use in source and binary forms, with or without
++ * modification, are permitted provided that the following conditions
++ * are met:
++ * 1. Redistributions of source code must retain the above copyright
++ *notice, this list of conditions and the following disclaimer.
++ * 2. Redistributions in binary form must reproduce the above copyright
++ *notice, this list of conditions and the following disclaimer in the
++ *documentation and/or other materials provided with the distribution.
++ * 3. All advertising materials mentioning features or use of this software
++ *must display the following acknowledgement:
++ *	This product includes software developed by the University of
++ *	California, Berkeley and its contributors.
++ * 4. Neither the name of the University nor the names of its contributors
++ *may be used to endorse or promote products derived from this software
++ *without specific prior written permission.
++ *
++ * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
++ * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
++ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
++ * ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
++ * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
++ * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
++ * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
++ * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
++ * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
++ * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
++ * SUCH DAMAGE.
++ *
++ *	@(#)queue.h	8.5 (Berkeley) 8/20/94
++ * $FreeBSD: ports/misc/44bsd-more/files/queue.h,v 1.1 2001/01/06 03:41:36 hoek Exp $
++ */
++
++/*
++ * Circular queue definitions.
++ */
++#define CIRCLEQ_HEAD(name, type)	\
++struct name {\
++	struct type *cqh_first;		/* first element */		\
++	struct type *cqh_last;		/* last element */		\
++}
++
++#define CIRCLEQ_ENTRY(type)		\
++struct {\
++	struct type *cqe_next;		/* next element */		\
++	struct type *cqe_prev;		/* previous element */		\
++}
++
++/*
++ * Circular queue functions.
++ */
++#define CIRCLEQ_EMPTY(head) ((head)->cqh_first == (void *)(head))
++
++#define CIRCLEQ_FIRST(head) ((head)->cqh_first)
++
++#define CIRCLEQ_FOREACH(var, head, field)\
++	for((var) = (head)->cqh_first;	\
++	(var) != (void *)(head);	\
++	(var) = (var)->field.cqe_next)
++
++#define CIRCLEQ_FOREACH_REVERSE(var, head, field)			\
++	for((var) = (head)->cqh_last;	\
++	(var) != (void *)(head);	\
++	(var) = (var)->field.cqe_prev)
++
++#define	CIRCLEQ_INIT(head) do {		\
++	(head)->cqh_first = (void *)(head);\
++	(head)->cqh_last = (void *)(head);\
++} while (0)
++
++#define CIRCLEQ_INSERT_AFTER(head, listelm, elm, field) do {		\
++	(elm)->field.cqe_next = (listelm)->field.cqe_next;		\
++	(elm)->field.cqe_prev = (listelm);\
++	if ((listelm)->field.cqe_next == (void *)(head))		\
++		(head)->cqh_last = (elm);\
++	else\
++		(listelm)->field.cqe_next->field.cqe_prev = (elm);	\
++	(listelm)->field.cqe_next = (elm);\
++} while (0)
++
++#define CIRCLEQ_INSERT_BEFORE(head, listelm, elm, field) do {		\
++	(elm)->field.cqe_next = (listelm);\
++	(elm)->field.cqe_prev = (listelm)->field.cqe_prev;		\
++	if ((listelm)->field.cqe_prev == (void *)(head))		\
++		(head)->cqh_first = (elm);\
++	else\
++		(listelm)->field.cqe_prev->field.cqe_next = (elm);	\
++	(listelm)->field.cqe_prev = (elm);\
++} while (0)
++
++#define CIRCLEQ_INSERT_HEAD(head, elm, field) do {			\
++	(elm)->field.cqe_next = (head)->cqh_first;			\
++	(elm)->field.cqe_prev = (void *)(head);\
++	if ((head)->cqh_last == (void *)(head))\
++		(head)->cqh_last 

[OpenWrt-Devel] add vars for uci firewall include scripts

[edgar . soldin]

the change to uci_firewall.sh omitted the necessary variables for the 
/etc/firewall.user script and the like. This patch adds them again.


regards ede
Index: package/firewall/files/uci_firewall.sh
===
--- package/firewall/files/uci_firewall.sh	(Revision 18608)
+++ package/firewall/files/uci_firewall.sh	(Arbeitskopie)
@@ -397,6 +397,9 @@
 }
 
 fw_include() {
+	config_get WAN wan ifname
+	config_get WANDEV wan device
+	config_get LAN lan ifname
 	local path
 	config_get path $1 path
 	[ -e $path ] && . $path
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] add vars for uci firewall include scripts

[edgar . soldin]

I copied it over from 7.09's /etc/init.d/firewall init script ... and it 
worked for my script.. LAV doesn't seem to be set there. Would you like 
me to add LANDEV?


.. ede

On 09.12.2009 19:15, Jo-Philipp Wich wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Shouldn't you add "LANDEV" too?

~ JoW
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAksf6SMACgkQdputYINPTPMhhgCfcmk9JpBiBRd+gH/vD0kVmRil
5mEAoJkk68q7FeUwIAIcqKFbvWq/dGeL
=EPwH
-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

Re: [OpenWrt-Devel] add vars for uci firewall include scripts

[edgar . soldin]

well, it wouldn't hurt and maybe somebody might need it in the future. 
Also maybe some other variables for wireless and the like. But, I have 
problems to figure out where the scripts gets the network values from. 
It's not in the general nvram vars available by 'uci show'.


... ede

On 09.12.2009 22:28, Jo-Philipp Wich wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


I copied it over from 7.09's /etc/init.d/firewall init script ... and it
worked for my script.. LAV doesn't seem to be set there. Would you like
me to add LANDEV?


No, I was just curious. But it seems to make sense :)

~ JoW


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

[OpenWrt-Devel] bump pptpd to 1.3.4, minor fixes

[edgar . soldin]

attached is a patch that bumps pptpd to the latest version. It contains 
patches to fix two compile issues & removes the obsolete 
pptpgre_use_debug_option patch. Also pptpd is now depending package ppp, 
as pppd is needed to run pptpd.


kind regards ede
Index: feeds/packages/net/pptpd/patches/002-makefile_fix.patch
===
--- feeds/packages/net/pptpd/patches/002-makefile_fix.patch (Revision 0)
+++ feeds/packages/net/pptpd/patches/002-makefile_fix.patch (Revision 0)
@@ -0,0 +1,11 @@
+--- pptpd-1.3.4.orig/plugins/Makefile  2006-08-03 04:02:01.0 +0200
 pptpd-1.3.4/plugins/Makefile   2009-12-03 21:18:09.678467590 +0100
+@@ -18,7 +18,7 @@ all: $(PLUGINS)
+ %.so: %.c
+   $(CC) -o $@ $(LDFLAGS) $(CFLAGS) $^ $(LDADD)
+ 
+-LIBDIR?= $(DESTDIR)$(prefix)/lib/pptpd
++LIBDIR= $(DESTDIR)$(prefix)/lib/pptpd
+ 
+ install: $(PLUGINS)
+   $(INSTALL) -d $(LIBDIR)
Index: feeds/packages/net/pptpd/patches/002-pptpgre_use_debug_option.patch
===
--- feeds/packages/net/pptpd/patches/002-pptpgre_use_debug_option.patch 
(Revision 18610)
+++ feeds/packages/net/pptpd/patches/002-pptpgre_use_debug_option.patch 
(Arbeitskopie)
@@ -1,35 +0,0 @@
-diff -Nur pptpd-1.3.0/pptpgre.c.orig pptpd-1.3.0/pptpgre.c
 pptpd-1.3.0/pptpgre.c.orig 2006-04-18 02:13:10.0 -0400
-+++ pptpd-1.3.0/pptpgre.c  2006-04-18 02:14:19.0 -0400
-@@ -46,6 +46,9 @@
- 
- #define PACKET_MAX 8196
- 
-+/* Command Line Variable Args */
-+extern int pptpctrl_debug;
-+
- typedef int (*callback_t)(int cl, void *pack, unsigned int len);
- 
- /* test for a 32 bit counter overflow */
-@@ -319,7 +322,9 @@
-   stats.rx_lost += head->seq - gre.seq_recv - 1;
-   syslog(LOG_DEBUG, "GRE: timeout waiting for %d 
packets", head->seq - gre.seq_recv - 1);
-   }
--  syslog(LOG_DEBUG, "GRE: accepting #%d from queue", head->seq);
-+  if (pptpctrl_debug) {
-+  syslog(LOG_DEBUG, "GRE: accepting #%d from queue", 
head->seq);
-+  }
-   gre.seq_recv = head->seq;
-   status = callback(cl, head->packet, head->packlen);
-   pqueue_del(head);
-@@ -399,7 +404,9 @@
-   }
-   /* check for out-of-order sequence number */
-   if (seq_greater(seq, gre.seq_recv)) {
--  syslog(LOG_DEBUG, "GRE: accepting packet #%d", seq);
-+  if (pptpctrl_debug) {
-+  syslog(LOG_DEBUG, "GRE: accepting packet #%d", 
seq);
-+  }
-   stats.rx_accepted++;
-   gre.seq_recv = seq;
-   return cb(cl, buffer + ip_len + headersize, 
payload_len);
Index: feeds/packages/net/pptpd/patches/001-bad_pqueue_debug.patch
===
--- feeds/packages/net/pptpd/patches/001-bad_pqueue_debug.patch (Revision 18766)
+++ feeds/packages/net/pptpd/patches/001-bad_pqueue_debug.patch (Arbeitskopie)
@@ -1,7 +1,6 @@
-diff -urN pptpd-1.3.0/pqueue.c.orig pptpd-1.3.0/pqueue.c
 pptpd-1.3.0/pqueue.c.orig  2006-04-17 20:44:28.0 -0400
-+++ pptpd-1.3.0/pqueue.c   2006-04-17 20:44:58.0 -0400
-@@ -6,14 +6,11 @@
+--- pptpd-1.3.4.orig/pqueue.c  2005-08-03 10:53:22.0 +0200
 pptpd-1.3.4/pqueue.c   2009-12-03 17:47:26.976174000 +0100
+@@ -7,13 +7,11 @@
  #include "pqueue.h"
  
  #ifdef DEBUG_PQUEUE
@@ -14,7 +13,6 @@
  
 -#define DEBUG_CMD(_a) if (DEBUG_ON) { _a }
 -
--
  #define MIN_CAPACITY 128 /* min allocated buffer for a packet */
  
  static int pqueue_alloc (int seq, unsigned char *packet, int packlen, 
pqueue_t **new);
Index: feeds/packages/net/pptpd/Makefile
===
--- feeds/packages/net/pptpd/Makefile   (Revision 18610)
+++ feeds/packages/net/pptpd/Makefile   (Arbeitskopie)
@@ -8,19 +8,19 @@
 include $(TOPDIR)/rules.mk
 
 PKG_NAME:=pptpd
-PKG_VERSION:=1.3.0
+PKG_VERSION:=1.3.4
 PKG_RELEASE:=1
 
 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
 PKG_SOURCE_URL:=...@sf/poptop
-PKG_MD5SUM:=75d494e881f7027f4e60b114163f6b67
+#PKG_MD5SUM:=75d494e881f7027f4e60b114163f6b67 #1.3.0
 
 include $(INCLUDE_DIR)/package.mk
 
 define Package/pptpd
   SECTION:=net
   CATEGORY:=Network
-  DEPENDS:=+kmod-ppp +kmod-gre
+  DEPENDS:=+kmod-ppp +kmod-gre +ppp
   TITLE:=PopTop pptp server
   URL:=http://www.poptop.org/
   SUBMENU:=VPN
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] syslog-ng should log kernel messages as well

[edgar . soldin]

you are right vasilis .. I just tried it with syslog-ng3 ..

the syslog-ng manual also states

page 38
"On Linux, the klogd daemon can be used in addition to syslog-ng to read 
kernel messages and forward them to syslog-ng.
klogd used to preprocess kernel messages to resolve symbols etc., but as 
this is deprecated by ksymoops there is really
no point in running both klogd and syslog-ng in parallel. Also note that 
running two processes reading /proc/kmsg at

the same time might result in dead-locks.
When using syslog-ng to read messages from the /proc/kmsg file, 
syslog-ng automatically disables the follow_freq()

parameter to avoid blocking the file."

and about the use of pipe on Page 39
"Pipe is very similar to the file() driver, but there are a few 
differences, for example pipe() opens its argument
in read-write mode, therefore it is not recommended to be used on 
special files like /proc/kmsg."


therefore I am not sure if enabling logging kernel messages without 
disabling klogd is a good idea. Also you should use file() and of course 
add it to the log declaration.


... ede


On 14.12.2009 09:41, Vasilis Tsiligiannis wrote:

Hello Brian,


-log { source(src); destination(messages); };
+log { source(src); source(kernel); destination(syslog_server); };


Correct me if I am wrong: shouldn't there be a "destination syslog_server
{...};" also present in the config? Or just send them to messages destination
which already exists?

Best Regards,
Vasilis Tsiligiannis




___
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] syslog-ng should log kernel messages as well

[edgar . soldin]

But then the FAQ contradicts this with it's "expanded
syslog-ng.conf" (http://www.campin.net/syslog-ng/expanded-syslog-ng.conf) where 
it uses:



dunno what that site is but
http://www.balabit.com/network-security/syslog-ng/
is where syslog-ng comes from


source s_kernel
{ pipe("/proc/kmsg" log_prefix("kernel: ")); };


well that's plain wrong (see manual on balabit.com)



 source src { file("/proc/kmsg"); unix-stream("/dev/log"); internal(); 
};

in http://www.campin.net/syslog-ng/faq.html#klogd


as it should be...


therefore I am not sure if enabling logging kernel messages without
disabling klogd is a good idea.


Of course.  I don't use klogd here.  Perhaps the packaging of syslog-ng
should be such that it's mutually exclusive of whatever provides klogd,
although I am not sure which package that is given that I don't use it
here.  :-)  I'm also unsure if the ipk format allows the specification
of "conflicts".


I just found it is run by /etc/init.d/boot .. maybe it should be 
conditionally started only if some uci config of syslog-ng is not set.. 
or else ...





Also you should use file() and of course
add it to the log declaration.


Well, the package authors themselves seem to use file and pipe
with /proc/kmsg quite interchangeably.  I think I'd like to see more
clarification before I change what I think has been the historical use
case.


do whatever you like, for me the reasoning (locking and rw accessing a 
non writeable handler) in the official syslog-ng manual makes perfect sense




Of course, you can go ahead and submit a patch to change it yourself if
you like, but using pipe() is working plenty fine here and I log plenty
of kernel messages (i.e. every firewall exception and there are tons).


good for you ... still the patch is lacking the part where you actually 
log the source


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

[OpenWrt-Devel] bump iptables to 1.4.6

[edgar . soldin]

find attached a patch that updates iptables to recent version 1.4.6. 
Modified are the imq patch and the Makefile to resemble changes in 
iptables. I moved the patches back into the ./patches folder as there is 
no reason anymore to keep them in ./patches/


although I used git to create the patch, it'll probably leave an empty 
folder .\patches\1.4.4 . git rm even won't delete me the folder. Anybody 
knows how?


thanks ede
diff --git a/package/iptables/Makefile b/package/iptables/Makefile
index b4e2554..22bf453 100644
--- a/package/iptables/Makefile
+++ b/package/iptables/Makefile
@@ -9,18 +9,16 @@ include $(TOPDIR)/rules.mk
 include $(INCLUDE_DIR)/kernel.mk
 
 PKG_NAME:=iptables
-PKG_VERSION:=1.4.4
-PKG_RELEASE:=3
+PKG_VERSION:=1.4.6
+PKG_RELEASE:=1
 
-PKG_MD5SUM:=08cd9196881657ea0615d926334cb7e9
+PKG_MD5SUM:=c67cf30e281a924def6426be0973df56
 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2
 PKG_SOURCE_URL:=http://www.netfilter.org/projects/iptables/files \
ftp://ftp.be.netfilter.org/pub/netfilter/iptables/ \
ftp://ftp.de.netfilter.org/pub/netfilter/iptables/ \
ftp://ftp.no.netfilter.org/pub/netfilter/iptables/
 
-PATCH_DIR:=./patches/$(PKG_VERSION)
-
 PKG_FIXUP = libtool
 
 include $(INCLUDE_DIR)/package.mk
@@ -325,6 +323,7 @@ endef
 define Package/libiptc/install
$(INSTALL_DIR) $(1)/usr/lib
$(CP) $(PKG_INSTALL_DIR)/usr/lib/libiptc.so* $(1)/usr/lib/
+   $(CP) $(PKG_INSTALL_DIR)/usr/lib/libip?tc.so* $(1)/usr/lib/
 endef
 
 define Package/libxtables/install
diff --git a/package/iptables/patches/002-layer7_2.17.patch 
b/package/iptables/patches/002-layer7_2.17.patch
new file mode 100644
index 000..a62d87f
--- /dev/null
+++ b/package/iptables/patches/002-layer7_2.17.patch
@@ -0,0 +1,390 @@
+diff -Nur a/libxt_layer7.c b/libxt_layer7.c
+--- a/extensions/libxt_layer7.c1970-01-01 01:00:00.0 +0100
 b/extensions/libxt_layer7.c2008-08-22 16:00:52.0 +0200
+@@ -0,0 +1,368 @@
++/* 
++   Shared library add-on to iptables for layer 7 matching support. 
++  
++   By Matthew Strait , Oct 2003-Aug 2008.
++
++   http://l7-filter.sf.net 
++
++   This program is free software; you can redistribute it and/or
++   modify it under the terms of the GNU General Public License
++   as published by the Free Software Foundation; either version
++   2 of the License, or (at your option) any later version.
++   http://www.gnu.org/licenses/gpl.txt
++*/
++
++#define _GNU_SOURCE
++#include 
++#include 
++#include 
++#include 
++#include 
++#include 
++#include 
++
++#include 
++#include 
++
++#define MAX_FN_LEN 256
++
++static char l7dir[MAX_FN_LEN] = "\0";
++
++/* Function which prints out usage message. */
++static void help(void)
++{
++  printf(
++  "layer7 match options:\n"
++  "--l7dir  : Look for patterns here instead of 
/etc/l7-protocols/\n"
++  "  (--l7dir must be specified before --l7proto 
if used)\n"
++  "[!] --l7proto : Match named protocol using 
/etc/l7-protocols/.../name.pat\n");
++}
++
++static const struct option opts[] = {
++  { .name = "l7proto", .has_arg = 1, .val = 'p' },
++  { .name = "l7dir",   .has_arg = 1, .val = 'd' },
++  { .name = NULL }
++};
++
++/* reads filename, puts protocol info into layer7_protocol_info, number of 
protocols to numprotos */
++static int parse_protocol_file(char * filename, const char * protoname, 
struct xt_layer7_info *info)
++{
++  FILE * f;
++  char * line = NULL;
++  size_t len = 0;
++
++  enum { protocol, pattern, done } datatype = protocol;
++
++  f = fopen(filename, "r");
++
++  if(!f)
++  return 0;
++
++  while(getline(&line, &len, f) != -1)
++  {
++  if(strlen(line) < 2 || line[0] == '#')
++  continue;
++
++  /* strip the pesky newline... */
++  if(line[strlen(line) - 1] == '\n')
++  line[strlen(line) - 1] = '\0';
++
++  if(datatype == protocol)
++  {
++  /* Ignore everything on the line beginning with the 
++  first space or tab . For instance, this allows the 
++  protocol line in http.pat to be "http " (or 
++  "http I am so cool") instead of just "http". */
++  if(strchr(line, ' ')){
++  char * space = strchr(line, ' ');
++  space[0] = '\0';
++  }
++  if(strchr(line, '\t')){
++  char * space = strchr(line, '\t');
++  space[0] = '\0';
++  }
++
++  /* sanity check.  First non-comment non-blank 
++  line must be the same as the file name. */
++  if(strcmp(line, protoname))
++  xtables_error(OTHER_PROBLEM, 
++ 

[OpenWrt-Devel] ping on patches for pptpd and iptables

[edgar . soldin]

these patches are unanswered/pending

bump pptpd to 1.3.4, minor fixes
https://lists.openwrt.org/pipermail/openwrt-devel/2009-December/005409.html

bump iptables to 1.4.6
https://lists.openwrt.org/pipermail/openwrt-devel/2009-December/005423.html


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

Re: [OpenWrt-Devel] [PATCH] syslog-ng should log kernel messages as well

[edgar . soldin]

I still object to the inclusion of this patch. At least for syslog-ng3.

The developers of syslog-ng clearly state in their
http://www.balabit.com/dl/guides/syslog-ng-v3.0-guide-admin-en.pdf
that
/proc/kmsg should not be opened with pipe driver, but with file() instead
and also
log_prefix is deprecated and should be replaced by program_override()

regards ede


On 03.01.2010 22:37, Brian J. Murrell wrote:

[ Second try as the first was not committed ]

If you want to use syslog-ng, likely you want to also log the kernel
messages with it.  This patch adds that.

Signed-off-by: Brian J. Murrell

---

Index: files/syslog-ng.conf
===
--- files/syslog-ng.conf(revision 18617)
+++ files/syslog-ng.conf(working copy)
@@ -10,7 +10,8 @@
  };

  source src { unix-stream("/dev/log"); internal(); };
+source kernel { pipe("/proc/kmsg" log_prefix("kernel: ")); };

  destination messages { file("/var/log/messages"); };

-log { source(src); destination(messages); };
+log { source(src); source(kernel); destination(messages); };






___
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] and again, ping on patches for pptpd and iptables

[edgar . soldin]

 Original Message 
Subject: [OpenWrt-Devel] ping on patches for pptpd and iptables
Date: Sat, 26 Dec 2009 16:49:55 +0100
From: edgar.sol...@web.de
Reply-To: OpenWrt Development List 
To: OpenWrt Development List 

these patches are unanswered/pending

bump pptpd to 1.3.4, minor fixes
https://lists.openwrt.org/pipermail/openwrt-devel/2009-December/005409.html

bump iptables to 1.4.6
https://lists.openwrt.org/pipermail/openwrt-devel/2009-December/005423.html


regards 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

Re: [OpenWrt-Devel] More preinit fixes

[edgar . soldin]

On 26.01.2010 09:29, Daniel Dickinson wrote:
> Ticket #6575: Patch for brcm47xx, hopefully it will boot again.  Working

The patch is for brcm-2.4 ?

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

Re: [OpenWrt-Devel] [PATCH] Hotplug automount fixes/enhancements

[edgar . soldin]

(stability)
Quite a chunk of code. Did you write it from scratch?
How thoroughly is this tested by now?
Does this work with kernel 2.4? Lot's of users are stuck to these kernels.

(packaging)
I don't mean to be picky, but wouldn't it make sense to keep code that
depends on specific package with that package? This could result in

/lib/functions/mount.sh
... mount.ext2.sh
... mount.xfs.sh
... mount.swap.sh
... fsck.sh
... fsck.ext2.sh
... fsck.xfs.sh
... and so on

This would make the initial space used smaller and it grows with the
needed functionality. It will get rid of all the if/elif redundant code
and hence easier to maintain.

(usability)
I like that you are putting infos to the logs. But there could be more.
Especially when e.g. fsck'ing is enabled but the software missing. Or in
every similar case, the user should see a statement to install the
package or disable the request.

(fix)
As I will surely add a file based swapping, swap should be disabled
before unmounting the file systems.


So far for now, good work .. ede


On 30.01.2010 02:13, Daniel Dickinson wrote:
> The attached patch replaces the current /etc/hotplug.d/block/10-mount
> and adds a shared shell script 'library' that, with this patch, is used
> by hotplug automount and fstab, and will be used by the rootfs on
> external storage package that I am working on as well.
> 
> You can turn automount completely off.
> You can set it to do only mounts from fstab
> You can set it to do only 'anonymous' mounts (mounted under /mnt/device)
> Ditto swap (if swap-utils is installed)
> You can mix and match
> You can control whether anonymous mounts get their filesystem checked
> You can control fstab filesystem checks on a per mount point basis
> (fsck depends on the appropriate package being installed)
> You can mount via uuid or label if blkid is installed
> 
> I will document on the wiki if it gets accepted.
> 
> Regards,
> 
> Daniel
> 
> 
> 
> 
> ___
> 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] remount /dev/root readonly for shutdown

[edgar . soldin]

Is there a sync command before the unmount?

Maybe the system does not reach the umount call, and therefor it is
never cleanly unmounted? You could debug that.

Maybe the controller is caching and needs specific commands to write the
cache to disc? Did you search the web?

good luck, ede


On 30.01.2010 00:11, Gerlando Falauto wrote:
> Hi all,
> 
> I am (slowly) experimenting with my LaCie Ethernet Disk Mini v2 NAS.
> In order to maintain compatibility with Lacie's software, I did not change
> the disk layout (yet).
> I can run my own OpenWRT without disrupting the original firmware
> by putting the kernel's uImage on [sda9]/snaps/00/boot and the root filesystem
> on [sda2] which is an xfs partition (it's the 300GB user partition)
> mounted as read/write.
> 
> Now every time I shutdown the box, my xfs filesystem gets corrupted
> and at the next reboot
> kernel ends up panicking because it can't mount the root filesystem to
> find an init file.
> 
> I figured the shutdown sequence did not correctly unmount my filesystem;
> I found the executed command was "umount -a -r", so I tried doing it manually:
> 
> r...@openwrt:~# umount -a -r
> umount: devpts busy - remounted read-only
> umount: tmpfs busy - remounted read-only
> umount: tmpfs busy - remounted read-only
> umount: can't remount /dev/root read-only
> umount: can't remount rootfs read-only
> 
> r...@openwrt:~# mount -t proc proc /proc
> r...@openwrt:~# umount -r /
> umount: can't remount /dev/root read-only
> 
> I know that mounting the initial root filesystem as read-write is not
> a very nice thing to do,
> but could someone please point out why it's, like, forbidden by law,
> so that I even get punished for doing it?
> 
> Thanks a lot!
> Gerlando
> ___
> 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] usb storage performance

[edgar . soldin]

On 07.02.2010 08:38, Damian Lesiuk wrote:
> I think something is wrong with usb-storage kernel driver on wl-500g premium 
> v1.

brcm-2.4?

> When I am copying something between partition I have 100 kB/s - 300
> kB/s, the same action on wl500g.googlecode.com firmware, I have 10
> mB/s.
> In addition, terribly load increases. Router gets slow. On
> wl500g.googlecode.com firmware I have load 1.2 when copying.

which filesystem are these?

> 
> I am using newest snapshot (3 february or something).
> 

openwrt snapshot?

> Another question
> 
> Why is the kernel consumes so much CPU?

it shouldn't, something is wrong

> 10% when the router does nothing, 25% When I am downloading something by wget.
> Kernel 2.4 when the router is not doing nothing at all worn out and
> the CPU load was approximately 0. Here, load does not fall below 0.30.
> ___
> 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] Automount enhanced/fixed, also fstab

[edgar . soldin]

At a quick glance it looks promising. I understand the need of the
copyright notice. I am no core developer but I guess you would have to
license the files under GPL2 by adding the appropriate notice.
Any file including existing GPL2 code would have to be licensed GPL2 anyway.

Will try it out these days .. ede

On 07.02.2010 06:58, Daniel Dickinson wrote:
> Hi all,
> 
> Here is the automount patch I've been promising with the modularization
> and logging suggested by ede.
> 
> You can turn automount completely off.
> You can set it to do only mounts from fstab
> You can set it to do only 'anonymous' mounts (mounted under /mnt/device)
> Ditto swap (if swap-utils is installed)
> You can mix and match
> You can control whether anonymous mounts get their filesystem checked
> You can control fstab filesystem checks on a per mount point basis
> (fsck depends on the appropriate package being installed)
> You can mount via uuid or label if blkid is installed
> 
> 
> 
> 
> ___
> 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] Automount enhanced/fixed, also fstab

[edgar . soldin]

What do you think of packaging hotplug automount separately? Now that
it's that sophisticated it takes several kilobytes of space. Space that
is valuable to users without non-usb-routers.

We could start a 'Base System / Hotplug Scripts' submuenu. A perfect
place also for the wifi toggle script, if it will eventally end up in
trunk anyway.

I'd volunteer to package hotplugd-automount.

.. ede

On 07.02.2010 07:00, Daniel Dickinson wrote:
> This time with the patch
> 
> On Sun, 2010-02-07 at 00:58 -0500, Daniel Dickinson wrote:
>> Hi all,
>>
>> Here is the automount patch I've been promising with the modularization
>> and logging suggested by ede.
>>
>> You can turn automount completely off.
>> You can set it to do only mounts from fstab
>> You can set it to do only 'anonymous' mounts (mounted under /mnt/device)
>> Ditto swap (if swap-utils is installed)
>> You can mix and match
>> You can control whether anonymous mounts get their filesystem checked
>> You can control fstab filesystem checks on a per mount point basis
>> (fsck depends on the appropriate package being installed)
>> You can mount via uuid or label if blkid is installed
>>
>> ___
>> 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] compression mode of jffs2

[edgar . soldin]

I discovered a currently not used option of jffs2. It allows the setting
of a compression mode. Because size matters on embedded devices I wonder
why this is not enabled. Attached a patch that does that. I tried it and
it works.

More info on the available switches also here
http://mhonarc.axis.se/jffs-dev/msg01683.html
and the mkfs.jffs2 man page

regards ede
Index: include/image.mk
===
--- include/image.mk(Revision 19505)
+++ include/image.mk(Arbeitskopie)
@@ -16,10 +16,10 @@
 KDIR=$(KERNEL_BUILD_DIR)
 
 ifneq ($(CONFIG_BIG_ENDIAN),y)
-JFFS2OPTS :=  --pad --little-endian --squash
+JFFS2OPTS :=  --pad --little-endian --squash --compression-mode=size
 SQUASHFS_OPTS :=  -le
 else
-JFFS2OPTS :=  --pad --big-endian --squash
+JFFS2OPTS :=  --pad --big-endian --squash --compression-mode=size
 SQUASHFS_OPTS :=  -be
 endif
 
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] compression mode of jffs2

[edgar . soldin]

This is kind of difficult as the internal flashes are usually very
small. A dd read write of 2MB is not really a test. But generally I
guess the probably very little speed difference is worth the space
saved. I guess it is little because there is no optimization switch for
speed.

ede

On 07.02.2010 18:00, Matthias Buecher / Germany wrote:
> How will this affect performance (the opposite side of compression)?
> If it does, then it would be great if this would be selectable and not
> hardcoded.
> 
> Just my two cents
> Maddes
> 
> On 07.02.2010 17:44, edgar.sol...@web.de wrote:
>> I discovered a currently not used option of jffs2. It allows the setting
>> of a compression mode. Because size matters on embedded devices I wonder
>> why this is not enabled. Attached a patch that does that. I tried it and
>> it works.
>>
>> More info on the available switches also here
>> http://mhonarc.axis.se/jffs-dev/msg01683.html
>> and the mkfs.jffs2 man page
>>
>> regards 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

Re: [OpenWrt-Devel] [PATCH] Automount enhanced/fixed, also fstab

[edgar . soldin]

The swap parts should be part of base files. The needed swapon/off could
come from util-linux or busybox.

.. ede

On 07.02.2010 07:00, Daniel Dickinson wrote:
> This time with the patch
> 
> On Sun, 2010-02-07 at 00:58 -0500, Daniel Dickinson wrote:
>> Hi all,
>>
>> Here is the automount patch I've been promising with the modularization
>> and logging suggested by ede.
>>
>> You can turn automount completely off.
>> You can set it to do only mounts from fstab
>> You can set it to do only 'anonymous' mounts (mounted under /mnt/device)
>> Ditto swap (if swap-utils is installed)
>> You can mix and match
>> You can control whether anonymous mounts get their filesystem checked
>> You can control fstab filesystem checks on a per mount point basis
>> (fsck depends on the appropriate package being installed)
>> You can mount via uuid or label if blkid is installed
>>
>> ___
>> 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] compression mode of jffs2

[edgar . soldin]

Any idea how to measure boot time? I don't have serial console access. ede

On 08.02.2010 11:14, Bas Mevissen wrote:

On Sun, 2010-02-07 at 18:00 +0100, Matthias Buecher / Germany wrote:

How will this affect performance (the opposite side of compression)?
If it does, then it would be great if this would be selectable and not
hardcoded.

Just my two cents
Maddes

On 07.02.2010 17:44, edgar.sol...@web.de wrote:

I discovered a currently not used option of jffs2. It allows the setting
of a compression mode. Because size matters on embedded devices I wonder
why this is not enabled. Attached a patch that does that. I tried it and
it works.



My 2 cents: compare the boot time between the jffs2 with and without the
patch. Can you also give an example in the actual flash space saved by
the patch?

Bas.


___
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] compression mode of jffs2

[edgar . soldin]

On second thought I actually think it would make sense to clarify the 
following points before taking any action. Not that I expected  anything 
to happen soon ;)


1. How is the compression evaluated. On per file or per file system 
basis. I couldn't really find docs telling this. Any hint appreciated.
2. Jffs2 compression seems to be in kernel from 2.6.15 on. Therefor it 
will probably not work on 2.4 ... I actually don't remember to have this 
tested. Hence I will have to.


Will dig a little more and come back with results.

regards ede



On 08.02.2010 11:32, Bastian Bittorf wrote:

* Bas Mevissen  [08.02.2010 11:20]:


My 2 cents: compare the boot time between the jffs2 with and without the
patch. Can you also give an example in the actual flash space saved by
the patch?


boottime should'nt be affected, because bootpartition is squashfs,
only the writeable partition is jffs2. In theory i vote for default to
size-optimization and make it menuconfig-selectable to switch to old mode.

bye, Bastian



___
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] Automount enhanced/fixed, also fstab

[edgar . soldin]

On 09.02.2010 06:12, Daniel Dickinson wrote:

On Sun, 2010-02-07 at 16:26 +0100, edgar.sol...@web.de wrote:

What do you think of packaging hotplug automount separately? Now that
it's that sophisticated it takes several kilobytes of space. Space that
is valuable to users without non-usb-routers.


I think adding hotplugd-autmount (5K), plus a new package block-common
(for the things used by fstab, hotplug and soon external rootfs) (8K),
is not a good use of time and infrastracture.


I'll offer my time actually to package it.
By the way how far is your usb root work by now? I am looking forward to 
it as well.



It could be done and I'll
do it if the core devs want it, but honestly 13K is pretty miniscule and


it is .. but all the small things take up a lot of space in the end. And 
why should a 2MB router without usb hold these scripts, which are now 
perfectly modularized and therefor easy packable.



it greatly complicates life for the many with USB devices if it
separate.


usb-storage should simply be depending on it .. and then it will be there.

.. thanks ede


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

Re: [OpenWrt-Devel] luci web interface package

[edgar . soldin]

install a theme. For some reason they are not automatically selected. 
Annoying all the time ;)


.. ede

On 10.02.2010 10:59, Iwan Budi Kusnanto wrote:

Hi All,
I managed to compile & install openwrt for avila gateworks.
But, i can't install the luci web interface.
These are what i do :
- In make menuconfig i already choose libuci-lua, lua, & liblua.
- opkg install luci-web luci-admin-mini luci-admin full

The browser redirected to cgi-bin/luci, but nothing shown up.
What should i do ?

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

Re: [OpenWrt-Devel] luci web interface package

[edgar . soldin]

Can you send a 'opkg list_installed' ?
Which platform you are on ?

ede

On 11.02.2010 04:43, Iwan Budi Kusnanto wrote:

edgar.sol...@web.de wrote:

install a theme. For some reason they are not automatically selected.
Annoying all the time ;)


I did. it is automatically selected. I use kamikaze 8.09.2



.. ede

On 10.02.2010 10:59, Iwan Budi Kusnanto wrote:

Hi All,
I managed to compile & install openwrt for avila gateworks.
But, i can't install the luci web interface.
These are what i do :
- In make menuconfig i already choose libuci-lua, lua, & liblua.
- opkg install luci-web luci-admin-mini luci-admin full

The browser redirected to cgi-bin/luci, but nothing shown up.
What should i do ?

Thanks,


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

Re: [OpenWrt-Devel] [PATCH] Automount enhanced/fixed, also fstab

[edgar . soldin]

On 12.02.2010 22:13, Daniel Dickinson wrote:

I think the packaging needs the following properties:
1) scripts for functionality (e.g. uuid and label, using blkid) are
automatically installed if the main block-mount (as I've called) is
installed, and the dependency is satisfied (.e.g if block-mount and
blkid are both installed then block-blkid should automatically be
selected for installation)
   


I'd rather keep them optional, that's why the log tells if it misses blkid.


2) It should be possible to pull in the dependencies for say
block-blkid, from the base system menu (device-dependent submenu),
rather than having to hunt down, say, blkid
   


Sorry, not sure what you mean. Could you explain by example?


4) Scripts for functionality should only be installed if the necessary
dependencies are present (e.g. block-blkid shouldn't be installed
without blkid and block-mount)
   


This will be ensured by dependency definition in the Makefile.


NB: All conditions  can't be met via a single package because menuconfig
doesn't like circular dependencies
   


me neither ;) .. but seriously. Circular dependencies only mean that 
somebody did not look deep enough into setting them properly.



Also note that the attached patches are incomplete...I'm having
difficulty getting menuconfig to do what I want, so I'm showing you what
I've got, and letting you try.
   


will do so.


because it it too small.  I think that those wanting 2/8 devices to work
should really think about working on a sister project that makes
   


How did you perceive that openwrt is not targeting 2MB routers?


To reiterate a 2/8 device should really be done with a different
choice-base than OpenWRT because in that case you want less
functionality and smaller size.
   


Currently you have to menuconfig/compile your own image for these 
devices. But I guess this is to keep the number of readymade images to 
build countable.





usb-storage should simply be depending on it .. and then it will be there.
 

It's not only applicable to usb though.   Anyway I think making
block-mount a part of profiles for devices with usb or other block
devices (other than the boot rootfs), would be appropriate.

   


Typically a package would be autoselected by different packages. e.g.

packages that supply block devices: usb-storage, sdcard, ...
autoselect
packages that are needed to use these: e.g. block-mount


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

Re: [OpenWrt-Devel] [PATCH] Automount enhanced/fixed, also fstab

[edgar . soldin]

I'd rather keep them optional, that's why the log tells if it misses blkid.


Actually it doesn't.  And it's only automatically selected if the base
block-mount package is selected, so it is optional, but you don't have
to worry about individual dependencies, and things work as expected
without special effort out of the box.


it does, for a good reason, functions/block.sh issues a log message if 
blkid is missing, but uuid is used. I don't see how to separate a base 
block-mount package, because the majority is replacing old mounting 
routines.


I'd expect the new functionality to split in something like

base-mount (which would be of package base-files because it replaces the 
old fstab mounting and is therefore essential, consisting of the files 
you put in buildroot/package/base-files except of the hotplugd stuff)
menuconfig->Base system->hotplugd-block-automount (automount files, to 
enable automount feature)
menuconfig->Base system->hotplugd-block-fsck (to enable fsck on hotplug 
events)


I'd suggest to put all hotplugd functionality in 
buildroot/package/hotplugd-block. The hotplugd-block Makefile would 
contain the package definitions mentioned above.





2) It should be possible to pull in the dependencies for say
block-blkid, from the base system menu (device-dependent submenu),
rather than having to hunt down, say, blkid



Sorry, not sure what you mean. Could you explain by example?


Base System|Device Dependent

should have packages such
block-meta-blkid, that has the dependencies that pull in blkid and
block-blkid (the package with the blkid mount stuff).


Why is this submenu 'Device Dependent' needed? What does it tell the user?

I see two solutions to this:
If we want to keep it simple and small it might make sense to simply 
activate busybox's blkid per default. Have to doublecheck the size 
increase though.

More elaborate could be, a basefiles subpackage setting

menuconfig->Base system->basefiles
[ ] support mount by uuid or label

. But maybe this is too much. I'd make it depending on the size increase 
above.




me neither ;) .. but seriously. Circular dependencies only mean that
somebody did not look deep enough into setting them properly.


Not true, with the limited dependency language we have.



Show me an example that is not solvable.



packages that supply block devices: usb-storage, sdcard, ...
autoselect
packages that are needed to use these: e.g. block-mount


block-mount is *required* to use usb, it's just nice to have.  That's
why profile selection not autoselect.



What do you mean?

block-mount is *required* to use usb,

or

it's just nice to have

?

In my understanding I distinguish between basefile-block-(mount,fsck( 
and the hotplugd-block-(automount,fsck). The basefile functionality is 
there anyway, the hotplugd is optional. Actually users do not need 
automounting to use usb storage devices. They can use the terminal to 
mount and stuff. But as hotplugd-automounting wasn't optional before on 
second thought I'd vote for activating it by default, but make it not 
depending on anything or anything depending on it.



.. what do you think, ede

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

Re: [OpenWrt-Devel] [PATCH] Automount enhanced/fixed, also fstab

[edgar . soldin]

Lets start here


OpenWrt does not currently run on devices which have 2MB or less of
flash memory. This limitation will probably not be worked around since
those devices are most of the time micro-routers, or Wireless Access
Points, which are not the main OpenWrt target.


This reads to me only as not primary target. Not as in "we do not 
support that". It simply states what was the case at the time of 
writing. Also my understanding of the community project openwrt is not 
to exlude anybody or some purpose. See the list of growing platforms for 
example. It is like a living organism. If there is a need or somebody 
willing it is done. If there is nobody by now, maybe somebody comes 
around later.


What makes openwrt so unique is the vast amount of possibility. There is 
a small set of readymade images. But if you want to buildroot yourself 
the tiniest embedded Linux you need, well it is possible.



Device Dependent is for things like block-* that depend on having
'external' (non-boot rootfs) devices , or on certain wifi devices (like


Device dependent says nothing specific. Even worse, it sounds like 
something that should change according to the chosen device profile. How 
about "additional/external storage support"? This way the user would 
know what to expect in the category.



the toggle you mentioned before).  It's more general than
hotplug-scripts because it includes things other than just hotplug
scripts.


Do you have more packages you want to put in there? Maybe we can come up 
with a less generic name.



I think I'll wait to you've digested the correction on what's essential
and what's not and the total size of the hotplug code.  I also would


And again .. it sums up. Having said sad I am glad to hear that the 
block mount scripts are not that tightly integrated in the boot process 
as I expected. Hence I gladly add it to the optional package list, see 
below.



like you to really think about the issue of badgering the user because
they didn't fill a dependency (that is have scripts that are trying to
execute functions but can't because the programs to do it aren't there).


You got me wrong. Read on.


I think it's fundamentally flawed.  Warning the user if they've
configured things badly is different than failing to fill a dependency
automatically when the promised functionality depends it.


Dependencies reflect absolute requirements. Fs utility packages do not 
require the fsck.sh scripts. E.g. e2fsck works perfectly alone. The same 
with usb storage. This works if the new scripts are installed or not. 
The script merely offer a sophisticated way to deal with it.


What we have here is a dynamic dependency
e.g. blkid. Buildroot does not know if the user is going to configure 
the use of uuid or label mounts. Therefore it is a dependency that 
starts when the user configures the system after flashing. Hence there 
must be a way to tell him/her what is going on.
Same for fs tools. Only because basic addstorage support is installed, 
this doesn't mean that the user is going to use an fsck.* app. This is 
decided later, if he decides to uci config a file check. In that lies 
the real quest.
Easy solution is error log output. Better is putting comments where the 
fsck'ing is configured. Perfect would be a tool that helps to configure 
and checks for pitfalls. I actually opt for Easy+Better.


Circumvent dynamic dependencies is only possible by splitting the 
promised functionality out of the big package to the effect that the 
small package wouldn't run if the dependency is missing. This is extra 
difficult here because of the multiple choice of filesystems. And there 
might be more in the future.



The reason I divided the packages the way I did is so the the scripts
weren't installed unless package that provided the capability to provide
the function was present.  e.g. btrfs fsck script only included when
btrfs-progs is.


Cleanly these fsck scripts should be packaged each as a package that 
depends on the appropriate fs tool and the basic blockmount. But this is 
more hassle than it's worth and therefore putting into their respective 
fs tools package serves the purpose fine.



Initially the core of the block-mount was to be included in base-files
(which is what what you're talking about switching to again, but I might


This was because I was under the impression they weren't optional.


as well have left things the way I had them if we're going to to do
that, because there is 5-8k of scripts that are hotplug only, and that's
it), and the other script functions were to be added along with the
package that provided the program need to use it.  You didn't like that
because it was too big.


Moreover I oppose to the idea to waste space on code that the user does 
not/ can not use.




The thing unless you subdivide to fairly small chunk you can't have a
proper matching of scripts to available functionality.


Agreed see "Circumvent dynamic dependencies..." above.


I am personally
op

Re: [OpenWrt-Devel] [PATCH] sudo: update to 1.7.2p3

[edgar . soldin]

(thanks for http://pastehtml.com/view/5tfitwd.html)



Nice. Where does this come from? .. Is it dynamically updated?

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