[PATCH 0/4] dhcp6c: new applet

I have ported dhcp6c (DHCPv6 client) from wide-dhcpv6 20080615 to
busybox. It tested on MIPS32 busybox-based CPE's against several  ISP
(mostly Russian).
I would appreciate review and comments.

Patches will be in following messages, splitted by functionality.

Regards,
   Leonid

Re: [PATCH 1/4] dhcp6c: decode_base64()

This patch adds into libbb decode_base64() function to decode base64
string. Needs for DHCPv6 authorization keys decode.

_______________________________________________
busybox mailing list
busybox <at> busybox.net
http://lists.busybox.net/mailman/listinfo/busybox

Re: [PATCH 2/4] dhcp6c: Add sprint_nip6

This patch adds sprint_nip6() utility function, it used to print IPv6
address into string.

_______________________________________________
busybox mailing list
busybox <at> busybox.net
http://lists.busybox.net/mailman/listinfo/busybox

Re: [PATCH 3/4] dhcp6c: IF_UDHCP_VERBOSE() macro

This patch introduces IF_UDHCP_VERBOSE() macro - it just improve code
readability.

_______________________________________________
busybox mailing list
busybox <at> busybox.net
http://lists.busybox.net/mailman/listinfo/busybox

[PATCH 4/4] dhcp6c: DHCPv6 client

This patch contains ported DHCPv6 client. Due to patch is huge
(230Kb), attach is gzipped.

With all options enabled applet increases size of bb code approx. to
36Kb on x86.

_______________________________________________
busybox mailing list
busybox <at> busybox.net
http://lists.busybox.net/mailman/listinfo/busybox

Re: PATCH: inotifyd.c: Implement a builtin 'echo' command

On Monday 26 September 2011 20:55, Flemming Madsen wrote:
> inotifyd.c: Implement a builtin 'echo' command for simply outputting
> events on stdout.

But this already works, right?

$ ./busybox inotifyd echo .
r .
0 .
r . .config
a . .config
0 . .config
r . .config
a . .config
a . .config
0 . .config
...
...
...

If someone wants fancier output, they can use fancier formatter than /bin/echo.

--

-- 
vda

where do I find the NTP server address with 'dhcpc -O ntpsrv'

Hello,

The NTP server ip is distributed via DHCP in my case.
So I want to do 'ntpd -p $NTP_SERVER'.
But that variable $NTP_SERVER is empty, and also /etc/ntp.conf does not 
exist.

Does anybody know where to find the NTP server's IP address received 
with 'dhcpc -O ntpsrc' ?

Regards,
Jürgen

P.S.: when I try to search the mailing list on busybox.net, google gives 
an error that the site may be sending spam..

--

-- 
Jürgen Lambrecht
R&D Associate
Tel: +32 (0)51 303045    Fax: +32 (0)51 310670
http://www.televic-rail.com
Televic Rail NV - Leo Bekaertlaan 1 - 8870 Izegem - Belgium
Company number 0825.539.581 - RPR Kortrijk

Re: PATCH: inotifyd.c: Implement a builtin 'echo' command

Yes it works .. At the cost of a fork+exec per outputted line!

On Sun, Oct 2, 2011 at 12:53 AM, Denys Vlasenko
<vda.linux <at> googlemail.com> wrote:
> On Monday 26 September 2011 20:55, Flemming Madsen wrote:
>> inotifyd.c: Implement a builtin 'echo' command for simply outputting
>> events on stdout.
>
> But this already works, right?
>
> $ ./busybox inotifyd echo .
> r .
> 0 .
> r . .config
> a . .config
> 0 . .config
> r . .config
> a . .config
> a . .config
> 0 . .config
> ...
> ...
> ...
>
> If someone wants fancier output, they can use fancier formatter than /bin/echo.
>
> --
> vda
>

Re: PATCH: inotifyd.c: Implement a builtin 'echo' command

> Yes it works .. At the cost of a fork+exec per outputted line!

 Or not, if you have configured bb to prefer applets.

 Anyway, have you encountered a real case where you needed "inotifyd echo"
functionality, and the fork+exec cost was prohibitive ? If you have, then
your patch is a good thing (and would be even better with a config option
whether or not to include the functionality). If you have not, then it is
just creeping featurism.

--

-- 
 Laurent

Re: where do I find the NTP server address with 'dhcpc -O ntpsrv'

> The NTP server ip is distributed via DHCP in my case.
> So I want to do 'ntpd -p $NTP_SERVER'.
> But that variable $NTP_SERVER is empty, and also /etc/ntp.conf does not 
> exist.
> 
> Does anybody know where to find the NTP server's IP address received 
> with 'dhcpc -O ntpsrc' ?

 If I understand the udhcpc.c code correctly, result of unknown options
listed with "-O foobar" are put into the environment via the line
  ofs = sprintf(*curr, "opt%u=", i);

 So if you start your client with "udhcpc -O ntpsrv", if my guess is
correct, you should get the NTP server address in the "opt0" environment
variable.

--

-- 
 Laurent