Can any one enlighten me on how announce() etc. can be used design an
echo server with UDP,
or point to samle code?
...
char adir[40];
int afd ;
afd = announce("udp!*!1234", adir);
and??
...
-ishwar
On Mon, Jan 31, 2011 at 09:45:44AM +, ish wrote:
>
>afd = announce("udp!*!1234", adir);
>
>and??
> ...
while (read (afd, ...) > 0) {
write (afd, ...);
}
... sort of thing?
++L
Lucio De Re once said:
> On Mon, Jan 31, 2011 at 09:45:44AM +, ish wrote:
> >
> >afd = announce("udp!*!1234", adir);
> >
> >and??
> > ...
> while (read (afd, ...) > 0) {
> write (afd, ...);
> }
>
> ... sort of thing?
This works if you write "headers" to the control
file after
On Jan 31, 12:28 pm, al...@pbrane.org (Anthony Martin) wrote:
> Lucio De Re once said:
>
> > On Mon, Jan 31, 2011 at 09:45:44AM +, ish wrote:
>
> > > afd = announce("udp!*!1234", adir);
>
> > > and??
> > > ...
> > while (read (afd, ...) > 0) {
> > write (afd, ...);
> > }
>
> > ... sor
Richard Miller <9f...@hamnavoe.com> writes:
> YMMV. My fossil has never locked up, but I get a corrupted daily
> dump two or three times a month.
My system/file system locks up periodically, and (as I recently
discovered) I don't even appear to have dumps/snapshots enabled. If the
system doesn'
> My system/file system locks up periodically, and (as I recently
> discovered) I don't even appear to have dumps/snapshots enabled. If the
> system doesn't lock up hard, any command that needs to read from the
> filesystem (i.e. running any command that's not built into rc) causes
> the shell to
"Steve Simon" writes:
> This is the exact scenario I had when I ran fossil + venti with ephemerial
> snapshots enabled, are you sure you don't have them on?
Quite sure. :) That's why I ended up recovering the data from Linux.
> fossil/conf /dev/sd??/fossil | grep snaptime
I have just tw
John Floren writes:
> I've continually meant to write some sort of beginners-level summary
> of the system including things like Fossil and Venti, but the
> magnitude of the task is daunting. I may try to do a more clear
> description of how the filesystems work together in the near future.
I've
On Tue, Feb 01, 2011 at 06:02:06AM +, smi...@zenzebra.mv.com wrote:
>
> I'm not someone to complain without also offering solutions, though.
> I'm in the process of writing some C macros that might help clean up the
> source code, ensure intended bounary conditions, improve some
> interfaces,
On Mon, Jan 31, 2011 at 10:02 PM, wrote:
> term% mkdir trashdir && cd trashdir && mkdir x
> term% touch `{i=0; while (test $i -lt 128) { echo -n abcdefghijklmnop;
> i=`{echo $i+1|hoc} } }
> term% cp abc* abc* x
> # watch the cp executable suicide
> # now, make SURE there's nothing in this rio w
have you checked the wiki?
http://www.plan9.bell-labs.com/wiki/plan9/Documentation/
there are tons of articles on Using this or that, a recommended
readings section and even a "UNIX to Plan 9 command translation."
there's also:
http://www.quanstro.net/newbie-guide.pdf
On Tue, Feb 1, 2011 at 3:
Writing a newbie guide is a newbie rite of passage :)
John
On Mon, Jan 31, 2011 at 10:47 PM, Federico G. Benavento
wrote:
> have you checked the wiki?
>
> http://www.plan9.bell-labs.com/wiki/plan9/Documentation/
>
> there are tons of articles on Using this or that, a recommended
> readings secti
On Sat, Jan 29, 2011 at 2:47 PM, wrote:
> I'm REALLY hoping someone can help me with this...
>
>
BTW, apropos this sad tale, go ahead and install python and mercurial
on your plan 9 system. Then set up a repo on a free place like
bitbucket. Voila, standard tools, which make Plan 9 a better place
> 8l $LDFLAGS -o important.h important.h.8
I'm interested in seeing this mkfile which causes mk misbehavior
--
Federico G. Benavento
Lucio De Re writes:
> Also, you have managed to stomp all over a couple of this mailing list's
> most sacred cows with your suggestion that the Plan 9 kernel code is less
> than perfect
Ooh! No intent to offend. I actually haven't even looked at the kernel
code, yet. I was referring to the bi
On Tue, Feb 01, 2011 at 07:07:30AM +, smi...@zenzebra.mv.com wrote:
> Lucio De Re writes:
>
> > Also, you have managed to stomp all over a couple of this mailing list's
> > most sacred cows with your suggestion that the Plan 9 kernel code is less
> > than perfect
>
> Ooh! No intent to offen
16 matches
Mail list logo
