RE: [cobalt-users] does cobalt talk to each other?

["Dan" <dan@xxxxxxxxxxxxx>]

I would recommend you not post the full URL of the .rpm that is not
supported. Instead, post the file name and the directory it is located in
with instructions each time to see the README file in the directory. This
will force users to not just click on the link in their email to download
the .rpm file without first navigating to the directory. At least then
they'll see README. Although, there is no README in the
ftp://ftp.cobaltnet.com/pub/experimental/security/proftpd/ directory. And
clicking on the "Up to higher level directory" link at the above, takes you
to ftp://ftp.cobaltnet.com/pub/experimental/ where the README is different.

--
Dan Kriwitsky


> -----Original Message-----
> From: cobalt-users-admin@xxxxxxxxxxxxxxx
> [mailto:cobalt-users-admin@xxxxxxxxxxxxxxx]On Behalf Of Jeff Bilicki
> Sent: Wednesday, January 19, 2000 2:22 PM
> To: cobalt-users@xxxxxxxxxxxxxxx
> Subject: Re: [cobalt-users] does cobalt talk to each other?
>
>
> Hello Gary,
>     I post pre-releases in rpm format of upcoming updates that Cobalt
> will officially release in pkg format at a future date.   These are in
> no way official Cobalt releases, also you you might have noticed in the
> FTP path the word "experimental".  Also, from
> ftp://ftp.cobaltnet.com/pub/experimental/security/README:
> "All rpms in this directory ARE in the process of being tested by Cobalt
> and are NOT SUPPORTED
>
>
> Install and use at your own risk!!!!!!
>
>
> If you find a problems please send it to jeffb@xxxxxxxxxxxxx"
>
> Oops, I messed up! I forgot to change the logrotate entry when moving
> from the srpm from RaQ 3 to RaQ 2.
>
> Copy the following shell script to your RaQ 2.
> ---- Cut Here ----
> #!/bin/sh
>
> xferlog=/etc/logrotate.d/proftpd
>
> cat > $xferlog << _EOF_
> /var/log/xferlog {
>     # ftpd doesn't handle SIGHUP properly
>     nocompress
> }
> _EOF_
>
> chown root.root $xferlog
> chmod 644 $xferlog
>
> ---- End Script -----
> As root type:
> $ chmod 700 nameofscript
> $ ./nameofscript
>
> Sorry about that.
>
>