Displaying 20 results from an estimated 1295 matches for "cautioned".
2005 Mar 25
0
CAUTION: Re: grandstream firmware update 1.0.5.23
Voicemail works fine for me.
Post console output here to let us know what went wrong.
Cheers,
Dean
-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of John
Breeden
Sent: Friday, March 25, 2005 12:55 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: CAUTION: Re: [Asterisk-Users] grandstream
2012 Dec 15
3
[LLVMdev] test-suite
I have an approved target independent putback and i've run all that we
have at Mips as well as on x86 " make TEST=simple"
Is there anything else that is easy to run that I can do before doing
the commit?
The patch touches a number of basic classes so I'm just trying to err on
the side of caution.
2008 Apr 25
0
[MailServer Resend] Quarantined email -- use caution when opening.Re: [PATCH 5/5] tun: vringfd xmit support.
----- Original Message Header -----
Subject: Re: [PATCH 5/5] tun: vringfd xmit support.
From: rusty at rustcorp.com.au;
To: akpm at linux-foundation.org;
Cc: netdev at vger.kernel.org; maxk at qualcomm.com;
virtualization at lists.linux-foundation.org; linux-kernel at vger.kernel.org;
-----------------------------------
Warning: Attachment contains virus code or meets the filtering/blocking
2004 Jul 04
0
[LLVMdev] [llvm-commits] CAUTION: Type != Value (fwd)
FYI to llvmdev. This is a huge win for LLVM. Thanks Reid!
-Chris
--
http://llvm.cs.uiuc.edu/
http://www.nondot.org/~sabre/Projects/
---------- Forwarded message ----------
Date: Sun, 04 Jul 2004 05:26:34 -0700
From: Reid Spencer <reid at x10sys.com>
To: llvm-commits at cs.uiuc.edu
Subject: [llvm-commits] CAUTION: Type != Value
LLVMers,
I have committed one of the major changes on the
2007 May 21
6
4.5 upgrades on production servers?
Anyone besides me totally throw (most) caution into the wind and yum update
any mission critical production 4.x boxen to 4.5 without any problems?
8-p
- rh
--
Abba Communications
Spokane, WA
www.abbacomm.net
2012 Dec 15
0
[LLVMdev] test-suite
On Sat, Dec 15, 2012 at 12:33 PM, Reed Kotler <rkotler at mips.com> wrote:
> I have an approved target independent putback and i've run all that we
> have at Mips as well as on x86 " make TEST=simple"
>
> Is there anything else that is easy to run that I can do before doing the
> commit?
>
> The patch touches a number of basic classes so I'm just
2008 Apr 16
3
Caution when deleting .wine ...
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/188361
says that at least some version of Nautilus followed
symlinks when deleting. Whoopsie!
2003 Jul 03
0
Caution: "admin users" and roaming profiles
This is information that might be useful to others, as it drove me nuts
until I could figure it out what I did incorrectly.
I recently installed the 3.0beta and moved everything from 2.2.8a. I'm
still in testing mode, so I rejoined the domain the the few test machines,
and have been deleting and rebuilding test user profiles as I check things
out.
The problem I had occurred with the
2007 Apr 12
2
4.92 beta update to centos5 proper words of caution
For those of you who are going to do the update from the centos5 beta
to centos 5 proper despite the warnings, this is a(n incomplete) list
of instructions for how to accomplish this
1. Get yourself into runlevel 3 (telinit 3 from terminal) as the dbus
update will die if you're in X.
2. Setenforce 0 # turn off selinux as there have been some unconfirmed
reports that it will interfere with the
2004 Jul 10
0
[LLVMdev] Re: [llvm-commits] CAUTION: Type != Value
Vladimir,
As you noted, the cast to Value* from (I presume) Type* is now invalid
as there is no inheritance relationship. You can give a type a name by
converting:
Ty->setName(Name, &ST)
to:
ST.insert(Name, Ty)
Hope that helps.
Reid.
On Sat, 2004-07-10 at 07:01, Vladimir Merzliakov wrote:
> In VMCore/Module.cpp i found line (254):
>
> ((Value*)Ty)->setName(Name,
2004 Jul 10
1
[LLVMdev] Re: [llvm-commits] CAUTION: Type != Value
> As you noted, the cast to Value* from (I presume) Type* is now invalid
> as there is no inheritance relationship. You can give a type a name by
> converting:
>
> Ty->setName(Name, &ST)
>
> to:
>
> ST.insert(Name, Ty)
>
> Hope that helps.
This is resolve problem for me.
Is attached patch ok for llvm/lib/VMCore/Module.cpp ?
Vladimir
--------------
2005 Jun 02
2
Caution on the use of model.matrix.
I have just been bitten by a quirk in the behaviour of model.matrix.
I used model.matrix inside a function, and passed to it a formula
that was built elsewhere.
The formula was of the form ``y ~ x + w + z''. Now, model.matrix
cheerfully accepts formulae of this form, although it only
***needs*** the right hand side, i.e. ``~ x + w + z'' --- the ``y''
can be dropped (but
2004 Jul 10
3
[LLVMdev] Re: [llvm-commits] CAUTION: Type != Value
In VMCore/Module.cpp i found line (254):
((Value*)Ty)->setName(Name, &ST);
Type is not Value now and for me this code call
llvm::DerivedType::addAbstractTypeUser (I think it have same index in Type
VMT in as setName in Value VMT)
with random argument values and terminated with assert fail:
Assertion failed: (isAbstract() && "addAbstractTypeUser: Current type not
2012 Dec 14
1
Found explanation for R-2.15.2 slowdown in one case; caution for any users of La_chol
2 days ago, I posted my long message about the observed slowdown in a
package between R-2.15.0 and R-2.15.2.
Uwe Ligges urged me to make a self-contained R example. That was the
encouragement I needed. I tracked the problem down to a failing use of
a LAPACK routine.
R's LAPACK C interface changed one variable in one function. But it
turned out to be an important change. In case others have
2011 May 02
2
Re: Caution when deleting .wine ...
David Shaw wrote:
>
> At the risk of getting flamed, you yourself have often told people to
> 'rm -rf ~/.wine' :-)
>
> David Shaw
When I entered 'rm -rf ~/.wine' it says:
rm: /Users/christopherwelch/.wine/drive_c/Program Files/Inbox Toolbar: Permission denied
rm: /Users/christopherwelch/.wine/drive_c/Program Files: Directory not empty
rm:
2007 Apr 13
1
[Fwd: 4.92 beta update to centos5 proper words of caution]
Jim Perrin wrote:
> For those of you who are going to do the update from the centos5 beta
> to centos 5 proper despite the warnings, this is a(n incomplete) list
> of instructions for how to accomplish this
>
> 1. Get yourself into runlevel 3 (telinit 3 from terminal) as the dbus
> update will die if you're in X.
> 2. Setenforce 0 # turn off selinux as there have been
2018 Feb 22
2
a few simple questions about upgrading an "official" centos 7 release
On Thu, 22 Feb 2018, Pete Biggs wrote:
>
> >
> > finally, any concerns i should have about upgrading the kernel from
> > 3.10 to 4.14 or 4.15, as explained in a number of places like this:
> >
> > https://www.tecmint.com/install-upgrade-kernel-version-in-centos-7/
> >
> > i simply prefer to run a current kernel but i can resist the
> >
2006 Sep 01
5
Kernel 2.6.9-42.0.2.plus.c4 doesn´t boot
Hi,
after upgrading with yum upgrade my server doesn?t boot with kernel
2.6.9-42.0.2.plus.c4 d. Kernel CentOS-4 x86_64 (2.6.9-34.EL) works just
fine.
I use 2 HDD as RAID1. Unfortunaly this is a root server so i do not have
any console output. This is rather disappointing cause i run mission
critical applications on the server.
I guess the updates should be used with more caution.
Regards,
2018 Feb 22
2
a few simple questions about upgrading an "official" centos 7 release
On Thu, 22 Feb 2018, hw wrote:
> Robert P. J. Day wrote:
... snip ...
> > oh, i appreciate the need for caution; on the other hand, it
> > always struck me that the training room is the *ideal* place for
> > students to experiment with things they're too nervous or unsure
> > of to try back at the office. this is typically why, when i'm
> >
2012 Dec 16
1
[LLVMdev] test-suite
On 12/15/2012 12:53 PM, Chandler Carruth wrote:
> On Sat, Dec 15, 2012 at 12:33 PM, Reed Kotler <rkotler at mips.com
> <mailto:rkotler at mips.com>> wrote:
>
> I have an approved target independent putback and i've run all
> that we have at Mips as well as on x86 " make TEST=simple"
>
> Is there anything else that is easy to run that I