Hi Gerald
Thanks for your quick reply
On Sat, Sep 13, 2014 at 2:59 PM, Gerald Matzka wrote:
> Take a look at http://wiki.openwrt.org/doc/devel/packages - section
> Package/postinst.
> Seems you forgot the #!/bin/sh
>
Now I update the Makefile like this (there is no indentation)
define Packag
Hi,
there is no need to enable the init script in postinst. The only
thing you need to make it start automatically is to give the executable
bit to the init script.
See below:
define Package/package/install
$(INSTALL_DIR) $(1)/etc/init.d
$(INSTALL_BIN) ./files/package.init $(1)/e
Since clean and world are declared as .PHONY, remove dependencies on
FORCE.
Signed-off-by: Robert P. J. Day
---
as long as i'm reading this correctly, since both clean and world
are declared as .PHONY, there is no need for the older-style FORCE
dependency, is there?
diff --git a/Makefile b/
Hi Jiří,
My init script (puppysplash) is already executable as shown below
root@OpenWrt:~# ls -l /etc/init.d/
-rwxr-xr-x1 root root 1419 Apr 16 17:32 boot
-rwxr-xr-x1 root root 729 Sep 13 07:07 cron
-rwxr-xr-x1 root root 330 Dec 12 2013 defcon
Hi,
imho all replies are superflous. i did fix this in trunk 3 days ago by
adding a generic postinst that will cal the enable and start target
John
On 13/09/2014 10:53, Nguyễn Hồng Quân wrote:
> Hi Jiří,
>
> My init script (puppysplash) is already executable as shown below
>
> root@Op
Presumably this one: https://dev.openwrt.org/changeset/42470
For the mortals among us,
a) does this mean all packages now start as soon as they're installed?
It used to be that packages that were selected and _built in_ to an image were
listed to start automatically, but packages manually inst
As Jiri said, you don't need a postinst function to enable the script. Your
script should start with
#!/bin/sh /etc/rc.common
and include the line:
START=xx
Where 'xx' is the startup position number you want your script executed in
rc.d (Ex: START=95)
See the example init script near the
Hi,
I prepared a new Version of ddns-scripts incl. the LuCI Application.
NEW in scripts:
- IPv6 support
- force communication to IPv4 or IPv6 only
- DNS server support
- using BIND host if installed
- DNS requests via TCP
- Proxy server support
- log file support
- support to run once
NEW in LuC
Hi Ted
On Sat, Sep 13, 2014 at 11:16 PM, Ted Hess wrote:
> As Jiri said, you don't need a postinst function to enable the script.
> Your script should start with
>
> #!/bin/sh /etc/rc.common
>
> and include the line:
>
> START=xx
>
> Where 'xx' is the startup position number you want your scrip
On 07/28/2014 12:37 AM, Ning Ye wrote:
> Hi All,
>
> Hyper-V support for X86 or X86_64 were noticeably missing. There is a
> previous patch for Kernel 3.3 but never maintained or merged into trunk.
> Here's my take on adding the Hyper-V support for the current kernel. No new
> sub targets o
Hi again,
El 13/05/2014 14:24, Ernesto escribió:
I'm compiling trunk r40755. I can add some feeds:
./scripts/feeds update
./scripts/feeds install luci-light alsa-utils bluez-utils
and with menuconfig I can select those packages and compile all right.
But when I add mpd:
./scripts/feeds instal
On 08/09/14 11:53, Steven Barth wrote:
> Yeah, the issue was in the tons of work-arounds needed to deal with
> Linux' onlink-route handling before 3.14. I added another one because
> they are so nice and likeable. This should hopefully do the trick again,
> until next time.
this time, /me not forg
12 matches
Mail list logo
