On 03/08/2010 01:05 AM, anonymous wrote:
> Erlang is not good to write a port scanner.
Do you have any sane justification for this remarque?
On Sun, Mar 07, 2010 at 11:48:38PM +0100, Uriel wrote:
> On Sat, Mar 6, 2010 at 9:46 PM, anonymous wrote:
> > portscan compiles when I include u.h, libc.h and thread.h and set CC=9c,
> > LD=9l, I can try to switch to libthread.
>
> Or use libtask, hell, or even Erlang, there are plenty of options
On Sat, Mar 6, 2010 at 9:46 PM, anonymous wrote:
> Go has no raw sockets and no alternatives to it. In Plan 9 it is possible
> to call dial(..., 0, 0, 0) to create file descriptor that accepts raw
> packets (IPv4, IPv6 etc., depends on first argument of dial). Go libpcap
> bindings are not fully i
On 7 March 2010 18:43, wrote:
>> > As a remark: The plan is to remove the cursor handling from dmenu
>> > again, since it violates the single purpose idea of dmenu. Instead
>> > there will be a dinput or sinput program that basically is nothing
>> > else as a text field widget that prints the inp
> > As a remark: The plan is to remove the cursor handling from dmenu
> > again, since it violates the single purpose idea of dmenu. Instead
> > there will be a dinput or sinput program that basically is nothing
> > else as a text field widget that prints the input to standard out.
>
> That seems
> As a remark: The plan is to remove the cursor handling from dmenu
> again, since it violates the single purpose idea of dmenu. Instead
> there will be a dinput or sinput program that basically is nothing
> else as a text field widget that prints the input to standard out.
That seems a little fid
Hi,
thanks I applied your patch.
As a remark: The plan is to remove the cursor handling from dmenu
again, since it violates the single purpose idea of dmenu. Instead
there will be a dinput or sinput program that basically is nothing
else as a text field widget that prints the input to standard ou
