Hi folks,
I'm wondering a bit why the OpenWrt toolchains rely on a set STAGING_DIR
environment variable. I haven't found any documentation on this except "You
have to set it". Examining the source tree of gcc didn't show me any
STAGING_DIR occurrence. It seems to be used only in the specs file.
Hi Jow,
thank you for that information.
> If the password option is specified like "$p$" then the password hash
> for is validated against /etc/shadow.
>
> If the password option is specified like "$1$" then the client supplied
> login password is hashed through crypt() and compared against the
Hi!
I've seen that there is an ACL concept for the ubus available [1], which fits
very nice to my plan making our system services available as ubus calls instead
of maintaining a REST API structure in parallel. However, I was not able to
figure out how to add additional users to the ubus. There
> what kind of changes are we talking about ? just config file stuff or
> big changes to how stuff is built and installed ?
>From what I've seen so far, it is about half in the package Makefiles, so how
>stuff is built and installed. The other half is shared between changes in the
>code and chan
Hello,
I'm quite new to OpenWrt and being faced with an existing build tree here.
After reading nearly everything I could force Google to bubble it up to the top
result pages, I'm still struggling with a simple question.
Our build tree is full of custom patches to different packages, mainly in
