On Wed, Mar 19, 2014 at 6:47 PM, Cristian Ionescu-Idbohrn
cristian.ionescu-idbo...@axis.com wrote:
On Mon, 17 Mar 2014, Cristian Ionescu-Idbohrn wrote:
I just had a look att commit 109ee5d33694a03cda3424b4846584250832ba8e.
IMO, to imitate bash behaviour isn't the right thing to do. It's a
On Tue, Mar 18, 2014 at 11:37 AM, Laszlo Papp lp...@kde.org wrote:
it seems that the ntpd util currently does not support config files.
Currently, it means that I need to work this around in Yocto for my
purposes, but as I see Zoltan Gyarmati here (*) also tried to do
similar things in
On Thu, Mar 20, 2014 at 10:47 AM, Denys Vlasenko
vda.li...@googlemail.com wrote:
With ntpd configuration file feature, in many cases you are likely
to still need a script such as this to regenerate the config file.
I would not need any script to do that and I am likely not alone. For
the win,
On Thu, Mar 20, 2014 at 11:50 AM, Laszlo Papp lp...@kde.org wrote:
On Thu, Mar 20, 2014 at 10:47 AM, Denys Vlasenko
vda.li...@googlemail.com wrote:
With ntpd configuration file feature, in many cases you are likely
to still need a script such as this to regenerate the config file.
I would
On Thu, Mar 20, 2014 at 10:53 AM, Denys Vlasenko
vda.li...@googlemail.com wrote:
On Thu, Mar 20, 2014 at 11:50 AM, Laszlo Papp lp...@kde.org wrote:
On Thu, Mar 20, 2014 at 10:47 AM, Denys Vlasenko
vda.li...@googlemail.com wrote:
With ntpd configuration file feature, in many cases you are
On Thu, Mar 20, 2014 at 12:02 PM, Laszlo Papp lp...@kde.org wrote:
On Thu, Mar 20, 2014 at 10:53 AM, Denys Vlasenko
vda.li...@googlemail.com wrote:
On Thu, Mar 20, 2014 at 11:50 AM, Laszlo Papp lp...@kde.org wrote:
On Thu, Mar 20, 2014 at 10:47 AM, Denys Vlasenko
vda.li...@googlemail.com
On Thu, Mar 20, 2014 at 12:44 PM, Denys Vlasenko
vda.li...@googlemail.com wrote:
On Thu, Mar 20, 2014 at 12:02 PM, Laszlo Papp lp...@kde.org wrote:
On Thu, Mar 20, 2014 at 10:53 AM, Denys Vlasenko
vda.li...@googlemail.com wrote:
On Thu, Mar 20, 2014 at 11:50 AM, Laszlo Papp lp...@kde.org
Hi Denys !
If you want to add optional support for parsing /etc/ntp.conf
compatible with standard ntpd (perhaps only server
and peer directives), it is acceptable.
If optional compiled in, ok ... but this shouldn't be compiled in
on default binaries. It's just pure bloat without any other
Please I want to unsubscribe.
Hisham Abul Naga
Sent from my iPad
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
You can do that here: http://lists.busybox.net/mailman/listinfo/busybox
On Thu, Mar 20, 2014 at 1:04 PM, Hisham Abul Naga
h_abuln...@hotmail.com wrote:
Please I want to unsubscribe.
Hisham Abul Naga
Sent from my iPad
___
busybox mailing list
On Thu, Mar 20, 2014 at 2:01 PM, Harald Becker ra...@gmx.de wrote:
Hi Denys !
If you want to add optional support for parsing /etc/ntp.conf
compatible with standard ntpd (perhaps only server
and peer directives), it is acceptable.
If optional compiled in, ok ... but this shouldn't be compiled
Hi Denys !
I don't know... I still feel compat is important.
It means growth of user base.
Compatibility with what? Busybox ntpd is not exactly modeled as
upstream ntpd ... and it's the reason why I use BB ntpd, as I
like it's simplicity, and dislike the upstreams complexity for a
minimalistic
Harald,
you would not use the minimal config, so your workflow would not
change anyway, and it is not like the complex use case you suggested
with all the signals and all that. It is a reasonable compromise in my
opinion. Parsing those two variables from a file is trivial, and would
increase the
Harald,
I'm curious. You mentioned earlier that code is never freed from memory.
If you're this concerned with bloat, why don't you fix your problem of
never deallocating the init code instead of worrying about some small
feature like this? The Linux kernel does this; that's why you see the
On Thu, Mar 20, 2014 at 5:28 PM, Mike Dean md...@emacinc.com wrote:
I'm curious. You mentioned earlier that code is never freed from memory.
If you're this concerned with bloat, why don't you fix your problem of never
deallocating the init code instead of worrying about some small feature like
Michael, Denys,
I'm sorry; it seems you don't understand. I wasn't referring to depending
on gcc to do the linking for you, but rather doing it yourselves. I'm
aware that you guys are used to depending on compilers, linkers and the
kernel to do the hard work for you, but really, it's not that
On Thu, Mar 20, 2014 at 6:47 PM, Mike Dean md...@emacinc.com wrote:
Michael, Denys,
I'm sorry; it seems you don't understand. I wasn't referring to depending
on gcc to do the linking for you, but rather doing it yourselves. I'm aware
that you guys are used to depending on compilers, linkers
The key word is, can, as in your statement, can be read back in again.
If it's designed to only ever be loaded the first time it's executed after
boot, then there will be no reason to load it back in again when executed
after that first time. If there's no need for the code, it won't be read
For characters with the top bit set od_bloaty produces silly octal
values with the -c flag:
$ echo £ | busybox od -c # od_bloaty.c (CONFIG_DESKTOP set)
000 0H2 0D3 \n
003
$ echo £ | busybox od -c # od.c (CONFIG_DESKTOP not set)
000 302 243 \n
003
$ echo £ | od -c
On Thu, 20 Mar 2014, Denys Vlasenko wrote:
On Wed, Mar 19, 2014 at 6:47 PM, Cristian Ionescu-Idbohrn
cristian.ionescu-idbo...@axis.com wrote:
On Mon, 17 Mar 2014, Cristian Ionescu-Idbohrn wrote:
I just had a look att commit 109ee5d33694a03cda3424b4846584250832ba8e.
IMO, to imitate bash
20 matches
Mail list logo
