Displaying 20 results from an estimated 20 matches for "truested".
Did you mean:
trested
2006 Jan 12
4
Loading Excel file into Limma
Dear mailing group,
This is my first time here. Glad to have this resource!
I am currently trying to load an Excel file into R (limma package loaded)
using the source(*name of directory*) command, but it cannot open the file.
I renamed the file as .R and .RData, to no avail. The Excel data contains
one gene name per row and about 100 data points per gene (columns).
I am only used to
2013 Jul 11
3
SSL cert problem
Hi,
I'm running a new dovecot 2.0.9 under Centos 6.4. I'm having an issue with
SSL certificate not being accepted by the email client.
I have my own CA and I have generated certificates for web usage without a
problem.
For imaps and pop3s what I did was generate a certificate for the hostname
of my dovecot server and then cat that cert with the intermediate and root
CA certificates. No
2011 May 20
2
Creating a Centos endorsed 3rd part repo
Hi all.
I'd like to put together a small repo for Centos packages
that I build on my machine, and make them available for
other Centos users.
Are there any guidlines for creating an officially endorsed
Centos 3rd party repo please?
Kind Regards,
Keith Roberts
-----------------------------------------------------------------
Websites:
http://www.karsites.net
http://www.php-debuggers.net
2005 May 15
0
Inter Domain Trusts
...PDC2(PRJLINUX2) - 192.168.43.251 - NETBIOS NAME = PRJARQ5
OpenLDAP 2.2.24
Samba 3.0.14a Backports
Deban 3 Woody
OpenLDAP:
The servers are using the same DataBase and the PRJARQ6 is a Slave from
PRJARQ5.
The Networks are connected through VPN (FreesWan) and it's working.
I need to make set Truested RelationShip "Two-way" and here's the behavior
that was adopted:
First Step: Trusted of PDC1 to PDC2:
In PDC1 (PRJLINUX1) - 192.168.42.2
# smbldap-useradd -i prjlinux2$
In PDC2 (PRJLINUX2) - 192.168.43.251
[root@prjarq5 /]# net rpc trustdom establish prjlinux2
Password:
Cou...
2013 Dec 19
0
ZFS on Linux testing
On 12/19/2013, 04:00 , lists at benjamindsmith.com wrote:
> BackupPC is a great product, and if I knew of it and/or it was available
> when I started, I would likely have used it instead of cutting code. Now
> that we've got BackupBuddy working and integrated, we aren't going to be
> switching as it has worked wonderfully for a decade with very few issues
> and little
2001 Nov 15
1
Win2k joining Samba 2.2.2 domain.
Hello, everyone. I'm trying to make Samba 2.2.2 a PDC
for Win2000 clients.
I believe that I have set the Linux Samba machine up
correctly. For your review, these are the steps that I
have taken:
* compile Samba 2.2.2 from source, no extra options.
* make; make install. (to /usr/local/samba)
* groupadd machines (for my machine trust accounts)
* groupadd smbadm (samba domain admin group)
*
2019 Feb 05
4
Release notify (2.2.36.1 and 2.3.4.1)
On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo Washington via dovecot wrote:
> On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot <dovecot at dovecot.org>
> wrote:
>
> > Due to DMARC issues some people have failed to receive the latest security
> > information, so here it is repeated for both releases:
> >
> > 2.3.4.1
> >
> >
2019 Feb 05
4
Release notify (2.2.36.1 and 2.3.4.1)
On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo Washington via dovecot wrote:
> On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot <dovecot at dovecot.org>
> wrote:
>
> > Due to DMARC issues some people have failed to receive the latest security
> > information, so here it is repeated for both releases:
> >
> > 2.3.4.1
> >
> >
2019 Feb 05
2
Release notify (2.2.36.1 and 2.3.4.1)
pull the patches from the port.....
On Tue, Feb 5, 2019 at 2:28 PM Odhiambo Washington via dovecot <
dovecot at dovecot.org> wrote:
> Oh, so manual compile should NOT work and it's okay or am I missing
> something?
>
> On Tue, 5 Feb 2019 at 23:26, The Doctor <doctor at doctor.nl2k.ab.ca> wrote:
>
>> On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo
2019 Feb 05
2
Release notify (2.2.36.1 and 2.3.4.1)
the patches are already in git master. I've pulled them into the
mail/dovecot port.
The dovecot guys/gals will release it eventually, but the port works TODAY.
On Tue, Feb 5, 2019 at 2:33 PM Odhiambo Washington <odhiambo at gmail.com>
wrote:
> I have always been able to compile manually, even from RCs so I believe I
> should be able to compile from the tarball as well.
>
2019 Feb 05
2
Release notify (2.2.36.1 and 2.3.4.1)
2.3.4 had the same compile issues....
On Tue, Feb 5, 2019 at 2:44 PM Odhiambo Washington <odhiambo at gmail.com>
wrote:
> Noted.
>
> I will wait for dovecot-2.3.4.2 tarball then.
>
> In all the servers I listed (+2 more), I never use the mail/dovecot port.
>
> I rely on mail/dovecot port on my own prototype (FreeBSD 12) which I have
> built in preparation for the
2019 Feb 05
0
Release notify (2.2.36.1 and 2.3.4.1)
Oh, so manual compile should NOT work and it's okay or am I missing
something?
On Tue, 5 Feb 2019 at 23:26, The Doctor <doctor at doctor.nl2k.ab.ca> wrote:
> On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo Washington via dovecot
> wrote:
> > On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot <dovecot at dovecot.org>
> > wrote:
> >
> > > Due to
2019 Feb 05
0
Release notify (2.2.36.1 and 2.3.4.1)
Oh, so manual compile should NOT work and it's okay or am I missing
something?
On Tue, 5 Feb 2019 at 23:26, The Doctor <doctor at doctor.nl2k.ab.ca> wrote:
> On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo Washington via dovecot
> wrote:
> > On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot <dovecot at dovecot.org>
> > wrote:
> >
> > > Due to
2019 Feb 05
0
Release notify (2.2.36.1 and 2.3.4.1)
I have always been able to compile manually, even from RCs so I believe I
should be able to compile from the tarball as well.
Something is broken,
On Tue, 5 Feb 2019 at 23:29, Larry Rosenman <larryrtx at gmail.com> wrote:
> pull the patches from the port.....
>
>
> On Tue, Feb 5, 2019 at 2:28 PM Odhiambo Washington via dovecot <
> dovecot at dovecot.org> wrote:
>
2019 Feb 05
0
Release notify (2.2.36.1 and 2.3.4.1)
Noted.
I will wait for dovecot-2.3.4.2 tarball then.
In all the servers I listed (+2 more), I never use the mail/dovecot port.
I rely on mail/dovecot port on my own prototype (FreeBSD 12) which I have
built in preparation for the upgrade of all the servers I currently have
(except the 11.2).
So for now, they have to run with 2.3.4, because of that reason - I am not
using the port. And yes, I
2019 Feb 05
0
Release notify (2.2.36.1 and 2.3.4.1)
Bueno.
I don't even remember well.
Wasn't that issue about mysql-8.0.12 to 8.0.13??
On Tue, 5 Feb 2019 at 23:46, Larry Rosenman <larryrtx at gmail.com> wrote:
> 2.3.4 had the same compile issues....
>
>
> On Tue, Feb 5, 2019 at 2:44 PM Odhiambo Washington <odhiambo at gmail.com>
> wrote:
>
>> Noted.
>>
>> I will wait for dovecot-2.3.4.2
2019 Feb 05
0
Release notify (2.2.36.1 and 2.3.4.1)
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Did I say so? It's known issue and will be fixed in future release.
</div>
<div>
<br>
</div>
<div>
Aki
</div>
<blockquote type="cite">
<div>
On 05 February 2019 at 22:27
2004 Sep 11
25
Broadvoice
Hello,
I am just curious how many people are hooked up with BroadVoice and have
recently been experiencing a lot of dificulty.
Joel
2019 Feb 05
3
Release notify (2.2.36.1 and 2.3.4.1)
Due to DMARC issues some people have failed to receive the latest security information, so here it is repeated for both releases:
2.3.4.1
https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz
https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz.sig
<https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig>
Binary packages in https://repo.dovecot.org/
* CVE-2019-3814: If
2019 Feb 05
3
Release notify (2.2.36.1 and 2.3.4.1)
Due to DMARC issues some people have failed to receive the latest security information, so here it is repeated for both releases:
2.3.4.1
https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz
https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz.sig
<https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig>
Binary packages in https://repo.dovecot.org/
* CVE-2019-3814: If