Re: rsync trouble

2000-09-17 Thread Swoop
"J.H.M. Dassen (Ray)" wrote: > > On Sat, Sep 16, 2000 at 20:33:56 +0200, Swoop wrote: > > I'm using rsync to make a mirror of Debian - for a long time it had worked > > very well, but suddenly this error appears: > > > > Resource temporarily unavailab

rsync trouble

2000-09-16 Thread Swoop
Hi, I'm using rsync to make a mirror of Debian - for a long time it had worked very well, but suddenly this error appears: Resource temporarily unavailable I'm using a command similar to this: rsync -avr ftp.sunet.se::pub/os/Linux/distributions/debian/dists/potato/contrib/binary-all/ /home/ftp/

rsync trouble

2000-09-15 Thread Swoop
Hi, I'm using rsync to make a mirror of Debian - for a long time it had worked very well, but suddenly this error appears: Resource temporarily unavailable I'm using a command similar to this: rsync -avr ftp.sunet.se::pub/os/Linux/distributions/debian/dists/potato/contrib/binary-all/ /home/ftp/

Re: hard joke ? ....

1998-09-15 Thread swoop
ustry news, there's only one place to go Sorry for that. And wasted bandwidth On Tue, 15 Sep 1998, swoop wrote: > > http://www.denounce.com/linux.html > > http://www.denounce.com/fbi.html > > > > Yeah , bad bad day on inet or something e

hard joke ? ....

1998-09-15 Thread swoop
http://www.denounce.com/linux.html http://www.denounce.com/fbi.html Yeah , bad bad day on inet or something else ... PS. No flames, FUD or whatever .. maybe smomeone coould explain. ;)

Re: Failure to recompile a system library (pthreads) under Debian 2.0

1998-09-12 Thread swoop
hurry .. half read letter. Sorry for wasted bandwidth. On Sat, 12 Sep 1998, swoop wrote: > > The 1.3.1 is based on libc 5 whereas debian 2.0 is glibc 2.0 > (a.k.a libc 6.0 ) . You need to remove all #include > because they now belong to the kernels and therefore should not be &

Re: Failure to recompile a system library (pthreads) under Debian 2.0

1998-09-12 Thread swoop
The 1.3.1 is based on libc 5 whereas debian 2.0 is glibc 2.0 (a.k.a libc 6.0 ) . You need to remove all #include because they now belong to the kernels and therefore should not be included by developers to maintain portability issues . On Sat, 12 Sep 1998, Martin Weinberg wrote: >