[OpenWrt-Devel] redis server

2014-01-31 Thread John Lauro
Has anyone ported redis server to openwrt?  Tried a simple build and it 
failed...  just checking before I spend time tracking down the problem(s) why a 
simple make didn't work.

If not, I'll figure it out next week, and if anyone else is interested in a 
port let me know.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] Keep settings broken on NetGear WNDR3800

2012-12-05 Thread John Lauro
Unfortunately that (sqush/jffs difference) wasn't it.  I tried double upgrade 
through squshfs, and still no good for keeping the settings.

One possible clue...  under backup / flash firmware, and pick Generate 
archive it creates a 0 byte tar.gz file.
I don't have CONFIG_BUSYBOX_CONFIG_FEATURE_SEAMLESS_GZ=y in my .config file, 
so I must of done something to make that option go away...


As to the kernel upgrade...  I would expect that not to be possible with 
squash, but seems like it should be possible with jffs.  Just too used to 
desktops/servers I guess and it may require an extra boot loader to allow that 
to be changed after generation.



- Original Message -
From: Paul Fertser fercer...@gmail.com
To: John Lauro la...@covenanteyes.com
Cc: OpenWrt Development List openwrt-devel@lists.openwrt.org
Sent: Wednesday, December 5, 2012 1:38:38 AM
Subject: Re: Keep settings broken on NetGear WNDR3800

Hi,

John Lauro la...@covenanteyes.com writes:
 One of the larger differences is I use jffs2 and you have squashfs.
 Any chance that is related to my issue with loosing settings when
 doing a full image upgrade?

Yes, it might affect how the configs are restored. Probably it's
broken for jffs2 since most users are using squashfs + jffs2 overlay
and so nobody noticed.

It looks like in both squashfs and jffs2 cases it just hands mtd the
file with the configs, and it search for the JFFS2 EOF marker (which
is appended to squashfs images as well) and then places the configs
overwriting it. Probably that's not a valid way to really overwrite
the files already present in a jffs2 image.

 On the subject of images...  and upgrades...  When the kernel jumped
 from 3.3 to 3.6 I had to do a whole firmware upgrade instead of just
 opkg upgrade on all the packages

That's to be expected. But do you want to say it's a bug that opkg
agreed to upgrade the kernel instead of telling you it just can't do
it (and then refusing to upgrade all the modules of course)?

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] Keep settings broken on NetGear WNDR3800

2012-12-05 Thread John Lauro
It works now.  Found the option, did a couple of full upgrades, squash - 
squash (after updating the packages), and then squash - jffs and it kept the 
settings each time.

The fix was selecting 
base - busybox - archival - Make tar, rpm, modprobe etc understand .gz data

Not sure how that became unset as I don't recall ever changing it (at least not 
directly).

Might make sense to have luci upgrade force that as a dependency to prevent 
others from making the same build mistake?


Thanks everyone for all the help.


- Original Message -
From: John Lauro john.la...@covenanteyes.com
To: Paul Fertser fercer...@gmail.com
Cc: OpenWrt Development List openwrt-devel@lists.openwrt.org
Sent: Wednesday, December 5, 2012 7:05:21 PM
Subject: Re: [OpenWrt-Devel] Keep settings broken on NetGear WNDR3800

Unfortunately that (sqush/jffs difference) wasn't it.  I tried double upgrade 
through squshfs, and still no good for keeping the settings.

One possible clue...  under backup / flash firmware, and pick Generate 
archive it creates a 0 byte tar.gz file.
I don't have CONFIG_BUSYBOX_CONFIG_FEATURE_SEAMLESS_GZ=y in my .config file, 
so I must of done something to make that option go away...


As to the kernel upgrade...  I would expect that not to be possible with 
squash, but seems like it should be possible with jffs.  Just too used to 
desktops/servers I guess and it may require an extra boot loader to allow that 
to be changed after generation.



- Original Message -
From: Paul Fertser fercer...@gmail.com
To: John Lauro la...@covenanteyes.com
Cc: OpenWrt Development List openwrt-devel@lists.openwrt.org
Sent: Wednesday, December 5, 2012 1:38:38 AM
Subject: Re: Keep settings broken on NetGear WNDR3800

Hi,

John Lauro la...@covenanteyes.com writes:
 One of the larger differences is I use jffs2 and you have squashfs.
 Any chance that is related to my issue with loosing settings when
 doing a full image upgrade?

Yes, it might affect how the configs are restored. Probably it's
broken for jffs2 since most users are using squashfs + jffs2 overlay
and so nobody noticed.

It looks like in both squashfs and jffs2 cases it just hands mtd the
file with the configs, and it search for the JFFS2 EOF marker (which
is appended to squashfs images as well) and then places the configs
overwriting it. Probably that's not a valid way to really overwrite
the files already present in a jffs2 image.

 On the subject of images...  and upgrades...  When the kernel jumped
 from 3.3 to 3.6 I had to do a whole firmware upgrade instead of just
 opkg upgrade on all the packages

That's to be expected. But do you want to say it's a bug that opkg
agreed to upgrade the kernel instead of telling you it just can't do
it (and then refusing to upgrade all the modules of course)?

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


[OpenWrt-Devel] Keep settings broken on NetGear WNDR3800

2012-12-04 Thread John Lauro
Whenever I try to upgrade the firmware (using trunk), I loose all settings.  
Everything from root password, to wifi settings such as the SID, etc...

Can someone reproduce?  (ie: maybe I did something wrong with my configuration 
and broke it, any suggestions what to make sure I didn't disable?)  I assume 
it's not broke for all platforms.


Unless someone else wants to fix, I'll try to track down what's wrong and fix 
as it's particularly annoying to me...  but any pointers as to how it should 
work and confirmation it works on other platforms would be great.  (or if 
someone can reproduce or deny the problem on the WNDR3800 would be great).
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] Keep settings broken on NetGear WNDR3800

2012-12-04 Thread John Lauro
I am using luci, but could try sysupgrade if you think it would make a 
difference. Haven't checked those areas before. I have checked 
/lib/upgrade/keep.d. (Hmm... thought /etc/shadow was in keep.d, but it isn't, 
but there is more than what's in luci.flash_keep). 

root@OpenWrt:~# uci show luci.flash_keep 
luci.flash_keep=extern 
luci.flash_keep.uci=/etc/config/ 
luci.flash_keep.dropbear=/etc/dropbear/ 
luci.flash_keep.openvpn=/etc/openvpn/ 
luci.flash_keep.passwd=/etc/passwd 
luci.flash_keep.opkg=/etc/opkg.conf 
luci.flash_keep.firewall=/etc/firewall.user 
luci.flash_keep.uploads=/lib/uci/upload/ 


root@OpenWrt:~# cat /etc/sysupgrade.conf 
## This file contains files and directories that should 
## be preserved during an upgrade. 

# /etc/example.conf 
# /etc/openvpn/ 

- Original Message -

From: camden lindsay camden.lindsay+open...@gmail.com 
To: OpenWrt Development List openwrt-devel@lists.openwrt.org 
Sent: Tuesday, December 4, 2012 10:41:44 AM 
Subject: Re: [OpenWrt-Devel] Keep settings broken on NetGear WNDR3800 

Hello, John 


I'm no expert, but think there should be some additional information, if you 
could include it. 


--Are you upgrading using luci, or using sysupgrade? 


If using luci, could you show the output of: 
uci show luci.flash_keep 


If using sysupgrade, could you show output of: 
cat /etc/sysupgrade.conf 


You may have already checked these files, but without posting the information 
in your intial email, its hard to know. 


take care-- 
c 








___ 
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] Keep settings broken on NetGear WNDR3800

2012-12-04 Thread John Lauro
That's good to know.  I must of broke it with my config.  :)

Can you send me your .config file so I can try to determine what is different 
in mine that could be causing the problem.

- Original Message -
From: Hannu Nyman hannu.ny...@iki.fi
To: OpenWrt Development List openwrt-devel@lists.openwrt.org
Sent: Tuesday, December 4, 2012 11:04:35 AM
Subject: Re: [OpenWrt-Devel] Keep settings broken on NetGear WNDR3800

I can update my WNDR3800 (and 3700v2 and 3700) just fine with all settings 
intact. Last updates: yesterday WNDR3800 from trunk 34440 to trunk 34469, 
(and also 3700v2 from trunk 344xx to AA 34469).  No problem with keeping 
settings. So, it is probably something specific for you.

I am using LuCI for the update, but I believe it is just a wrapper around the 
sysupgrade script, so the update method should not have much effect.


On 4.12.2012 17:24, John Lauro wrote:
 Whenever I try to upgrade the firmware (using trunk), I loose all settings.  
 Everything from root password, to wifi settings such as the SID, etc...

 Can someone reproduce?  (ie: maybe I did something wrong with my 
 configuration and broke it, any suggestions what to make sure I didn't 
 disable?)  I assume it's not broke for all platforms.


 Unless someone else wants to fix, I'll try to track down what's wrong and fix 
 as it's particularly annoying to me...  but any pointers as to how it should 
 work and confirmation it works on other platforms would be great.  (or if 
 someone can reproduce or deny the problem on the WNDR3800 would be great).


___
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] Keep settings broken on NetGear WNDR3800

2012-12-04 Thread John Lauro
Many differences, but wouldn't expect most of them to matter.

One of the larger differences is I use jffs2 and you have squashfs.  Any chance 
that is related to my issue with loosing settings when doing a full image 
upgrade? 


On the subject of images...  and upgrades...  When the kernel jumped from 3.3 
to 3.6 I had to do a whole firmware upgrade instead of just opkg upgrade on all 
the packages (although opkg acted like it could update, but still rebooted with 
the old kernel, which obviously then broke several kernel modules that did 
upgrade for the new kernel).


Thanks.

- Original Message -
From: Hannu Nyman hannu.ny...@iki.fi
To: openwrt-devel@lists.openwrt.org
Sent: Tuesday, December 4, 2012 11:24:06 AM
Subject: Re: [OpenWrt-Devel] Keep settings broken on NetGear WNDR3800

My .config?

Publicly available from: http://koti.welho.com/hnyman1/Openwrt/
More info at: https://forum.openwrt.org/viewtopic.php?id=28392


___
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] Looking for Openwrt programmers to customize Open-Mesh router code

2012-12-03 Thread John Lauro
That's how I read it too.

You are assuming you would catch it, and know what is causing it...  Might be 
subtle enough that it just looks like an google ranked ad.  (I would probably 
not notice, as I tend to always vpn back to home servers and vpn back for even 
general internet traffic despite the extra delay...)

Not to mention, google tends to switch most searching to https if you ever used 
any sort of google account on the computer before.  Of course ssl can be 
disabled for google searches, as many schools started blocking google because 
of incompatibility with content filters...  and child protection laws trump 
privacy issues, so google had to put in a disable option or be completely 
blocked...  Still, google displays a pretty clear note when that happens.

Personally, I wouldn't mind my searches being slightly modified if it meant 
free internet instead of the $5+/night they might otherwise charge per room.  
If there was a room charge for internet, they best not be messing with it in 
such a way...




- Original Message -
From: Aaron Z aar...@pls-net.org
To: OpenWrt Development List openwrt-devel@lists.openwrt.org
Sent: Monday, December 3, 2012 11:56:46 AM
Subject: Re: [OpenWrt-Devel] Looking for Openwrt programmers to customize   
Open-Mesh router code

Paul Fertser fercer...@gmail.com wrote:
 Brian Epstein br...@deepbluecommunications.com writes:
  Assuming Gold’s Gym is now the official Gym sponsor for all Wyndham
  hotels.  Now for example when anyone searches for the word “Gym” or
  “step class” on Google.com at any Super8 from behind our equipment,
  the search is modified prior to being sent to Google.com such that
  the search now says “step class golds gym”.
 
 Am I reading that right that when somebody wants to send a search
 query to Google you hijack it and modify however you want? Seriously?

That's how I read it. If that happened to me on a free hotel internet 
connection (which I am paying for with my room charge), I would NOT stay at 
that hotel again (I would leave after that night if possible) and (at minimum) 
the following people would be informed why I left: The hotel manager, corporate 
headquarters (if the hotel was part of a chain), my friends who keep up with me 
on various social media sites, Google Maps and any other place that I could 
find online that did reviews on that hotel, anyone who asked me about my trip.
If I am on a public network, most anything important is running back home over 
a OpenVPN or connecting via HTTPS, but messing with guests searches will only 
lose you goodwill...

Aaron Z
___
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] Change Default IP?

2012-11-29 Thread John Lauro
I tried preinit and also
.../trunk/package/base-files/files/etc/config/network
.../trunk/target/linux/ar7/base-files/etc/config/network

and it still comes out as 192.168.1.1.   (building for a wndr3800)

Seems to be lots of network files.  I guess I could have the wrong one?  The 
bin comes out under ar711x.


- Original Message -
From: Weedy weedy2...@gmail.com
To: openwrt-devel@lists.openwrt.org
Sent: Wednesday, November 28, 2012 7:21:25 PM
Subject: Re: [OpenWrt-Devel] Change Default IP?

On 28/11/12 06:38 PM, John Lauro wrote:
 Is there a place to change the default IP for a firmware build?
 
 I tried setting under Image configuration - Preinit configuration options - 
 IP address for preinit network messages, but that  doesn't seem to work (not 
 that I expected to, but it's the only config options I could find related to 
 an IP address).  Doing a search of my build tree, 192.168.1.1 seems to be 
 embedded in several spots.
 
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel
 

Preinit configuration has always worked for me. You can use the more
heavy handed $TOPDIR/files/etc/config/network if it is not working.
___
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] Change Default IP?

2012-11-29 Thread John Lauro
Not certain which config option for uci-defaults you are referring to, so 
perhaps I am not using the right one for it not to matter?

Not sure, but looks like network gets established from 
target/linux/ar71xx/base-files/etc/defconfig/wndr3700/network in the base 
filesystem (or not? it at least appears to be closer to my running 
/etc/config/network than most of the other copies of network) and this line is 
in /etc/uci-defaults/network:
[ -e /etc/config/network ]  exit 0
(and that would cause uci-defaults/network not to run)
(or is that not what runs at first boot that you were referring to?)

so I think that would keep the defaults from loading on first boot?

If nothing else, I have a few things to try.  Will try the 
target/linux/ar71xx/base-files/etc/defconfig/wndr3700/network first as I think 
that sounds most promissing.  Might be a few days before I gen a new firmware 
and test it.  The flow of all these files/configurations is a bit hard to 
follow from build system to running system, etc...  At least most of it just 
works, and adding to it is easy enough...  just altering some of the defaults 
can be a bit hard to follow...


- Original Message -
From: Daniel Dickinson dan...@powercloudsystems.com
To: OpenWrt Development List openwrt-devel@lists.openwrt.org
Cc: Hannu Nyman hannu.ny...@iki.fi
Sent: Thursday, November 29, 2012 5:42:10 PM
Subject: Re: [OpenWrt-Devel] Change Default IP?

Actually shouldn't matter.  If using right config option (under Image
options IRC) then there will be an uci-defaults file that runs on
firstboot to set the ipaddr, which should occur after the defconfig
configuration.  At least that's the intended design; if the order of
scripts is wrong then that's a bug.

Regards,

Daniel

On 29/11/2012 5:21 PM, Hannu Nyman wrote:
 You mentioned later in the thread that you are building for wndr3800.
 That is the key info here.

 Due to complex switch port LED defintions, WNDR3700/3800 has a
 dedicated network file template that will be used:
 https://dev.openwrt.org/browser/trunk/target/linux/ar71xx/base-files/etc/defconfig/wndr3700/network


 It has the section:
 config interface lan
 option ifname   eth0.1
 option type bridge
 option protostatic
 option ipaddr   192.168.1.1
 option netmask  255.255.255.0


 On 29.11.2012 1:38, John Lauro wrote:
 Is there a place to change the default IP for a firmware build?

 I tried setting under Image configuration - Preinit configuration
 options - IP address for preinit network messages, but that  doesn't
 seem to work (not that I expected to, but it's the only config
 options I could find related to an IP address).  Doing a search of my
 build tree, 192.168.1.1 seems to be embedded in several spots.



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

-- 
Daniel Dickinson PowerCloud Systems, Palo Alto, CA Senior Firmware
Engineer (In Canada: Senior Firmware Analyst)


___
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] Change Default IP?

2012-11-29 Thread John Lauro
Not sure, I purposely only have IPv4 enabled at this time though for my build.  
Don't recall the default as that was months ago I went through most of the 
options.

- Original Message -
From: David Woodhouse dw...@infradead.org
To: John Lauro john.la...@covenanteyes.com
Cc: OpenWrt Development List openwrt-devel@lists.openwrt.org
Sent: Thursday, November 29, 2012 6:56:29 PM
Subject: Re: [OpenWrt-Devel] Change Default IP?

On Thu, 2012-11-29 at 15:17 -0500, John Lauro wrote:
 I tried preinit and also
 .../trunk/package/base-files/files/etc/config/network
 .../trunk/target/linux/ar7/base-files/etc/config/network
 
 and it still comes out as 192.168.1.1.   (building for a wndr3800)
 
 Seems to be lots of network files.  I guess I could have the wrong
 one?  The bin comes out under ar711x.

Hm, do we really only have Legacy IP enabled by default? We should
really set an IPv6 address too (ULA or perhaps site-local). That would
be *much* easier to deal with when connecting it to an existing network.

-- 
dwmw2

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


[OpenWrt-Devel] Change Default IP?

2012-11-28 Thread John Lauro
Is there a place to change the default IP for a firmware build?

I tried setting under Image configuration - Preinit configuration options - 
IP address for preinit network messages, but that  doesn't seem to work (not 
that I expected to, but it's the only config options I could find related to an 
IP address).  Doing a search of my build tree, 192.168.1.1 seems to be embedded 
in several spots.

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


Re: [OpenWrt-Devel] Change Default IP?

2012-11-28 Thread John Lauro
Right...  unable to locate a place to set an IP address for the image init 
configuration, only preinit.

- Original Message -
From: Daniel Dickinson dan...@powercloudsystems.com
To: OpenWrt Development List openwrt-devel@lists.openwrt.org
Sent: Wednesday, November 28, 2012 7:41:16 PM
Subject: Re: [OpenWrt-Devel] Change Default IP?

Perhaps you're trying to set image configuration not preinit (i.e. the
default for regular operation)?  If so preinit is the wrong ip address.

Regards,

Daniel

On 28/11/2012 7:21 PM, Weedy wrote:
 On 28/11/12 06:38 PM, John Lauro wrote:
 Is there a place to change the default IP for a firmware build?

 I tried setting under Image configuration - Preinit configuration options 
 - IP address for preinit network messages, but that  doesn't seem to work 
 (not that I expected to, but it's the only config options I could find 
 related to an IP address).  Doing a search of my build tree, 192.168.1.1 
 seems to be embedded in several spots.

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

 Preinit configuration has always worked for me. You can use the more
 heavy handed $TOPDIR/files/etc/config/network if it is not working.
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel

-- 
Daniel Dickinson PowerCloud Systems, Palo Alto, CA Senior Firmware
Engineer (In Canada: Senior Firmware Analyst)


___
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] milliseconds time measurements

2012-11-23 Thread John Lauro
If you want to do multiple commands with time, either put them in a script and 
time the script, or do something like:

echo command 1 ; command 2 | time sh



- Original Message -
From: Gabriel gto...@inti.gob.ar
To: openwrt-devel@lists.openwrt.org
Sent: Friday, November 23, 2012 3:14:09 PM
Subject: Re: [OpenWrt-Devel] milliseconds time measurements

Thank you for your answers!

I've tried with the time command, but I couldn't use it for various 
commands together as in my pc using parentheses like

time (command 1; command 2)

with date +%s I get a seconds count:

root@E10:~# while true; do date; date +%s; sleep 1; done
Fri Nov 23 17:10:11 ART 2012
1353701411
Fri Nov 23 17:10:12 ART 2012
1353701412
Fri Nov 23 17:10:13 ART 2012
1353701413

Regarding /proc/uptime, I didn't know about it, I think will be enough 
for what I wanted!

Best regards

Gabriel


El 23/11/12 13:56, Bastian Bittorf escribió:
 /proc/uptime is much simplier :-)
 and it's even monotonic...and...fast.
 (date +%s can jump into future and past)

 read t1 trash /proc/uptime
 do_something()
 read t2 trash /proc/uptime
 ___
 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] default config for squid, was Autostart of services..

2012-11-10 Thread John Lauro
I think packages can have a postinstall script, and so it should be possible to 
adjust on a per package basis to have things auto start and set themselfs to 
enabled. It might makes sense for some packages, but some people probably 
install everything and so you do want to do that for every possible service 
just because it's installed... 

On a partially related question about packages... 
The default config for squid doesn't work. You have to run a command to init 
it's directory structure when using disk storage (likely every reboot if it's 
ram backed filesystem), and using a disk based cache doesn't make sense (at 
least on my device a WNDR3800 with 128mb of RAM and 16mb flash). I have more 
appropriate config that tells it to use 24MB RAM (process stabilizes at taking 
about 40MB after overhead) instead of a virtual disk that uses RAM less 
efficiently that then causes a reboot when it fills up... Should a usable 
config be the default, or maybe this is device specific and the default is good 
by default for some other platforms? I have a package that requires squid and 
runs it with a different config file instead of the one the comes with the 
squid package, so that works for me. Not sure if it would be useful to fix up 
and submit a change to the deafult squid package, or maybe submit a 
squid-ramcache package for easy install. If I did submit a package, I would 
need to clean up my package as it also adjusts the firewall rules (to force 
transparent caching) in an ugly way that would have to somehow be done more 
friendly/compatibly with the default rules... 


- Original Message -

From: Jan Lukeš johny...@gmail.com 
To: OpenWrt Development List openwrt-devel@lists.openwrt.org 
Sent: Saturday, November 10, 2012 2:55:51 PM 
Subject: Re: [OpenWrt-Devel] Autostart of services.. 

It's a matter of coherence among other services. Some services might be 
harmless, but some can pose a security risk. We need to treat them all the 
same, thus as risk. 


Anyway. Persistence is just matter of explicitly enabling it. 


On Sat, Nov 10, 2012 at 6:16 PM, Michael Markstaller  m...@elabnet.de  wrote: 


-BEGIN PGP SIGNED MESSAGE- 
Hash: SHA1 

Hi, 

first of all: I know this is intentionally unwanted currently; 
still I'd like to start discussing it again: 
If I i.e. install the snmpd-Package (just one example) I'd think it 
should be uprunning, no need to manually enable it again so it really 
starts  runs :o 

This behavior (when i start it afterwards manually, it only persists 
until reboot) is IMHO confusing and not very user-friendly.. 
Whats the real point against something the user selected also runs 
without further fiddling to really enable it (once again)? 


best regards 

Michael 
-BEGIN PGP SIGNATURE- 
Version: GnuPG v1.4.11 (GNU/Linux) 
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ 

iEYEARECAAYFAlCei98ACgkQaWRHV2kMuAI4KACgn3F5uyPnQjl+B01kTA+ey1r6 
mZEAn0PZ5WIVYHy2P/pjyx04tBo1DkFB 
=3MIZ 
-END PGP SIGNATURE- 
___ 
openwrt-devel mailing list 
openwrt-devel@lists.openwrt.org 
https://lists.openwrt.org/mailman/listinfo/openwrt-devel 






-- 



S pozdravem 


Jan Lukeš 

___ 
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