Displaying 20 results from an estimated 10000 matches similar to: "Migration Clarification Request"
2014 Jan 19
2
PCI Passthrough
I'm trying to pass-through my VGA card to a guest session.
I found: http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM - which is very frustrating because there's no date on the documentation. I suspect it's old. It does clearly say that you must have VT-d support for pci pass-through. It then goes on to say "Some work towards allowing this ["software
2014 Mar 18
0
Writing R Extensions: clarification/modification request
Hello R-core developers,
The upcoming release of R-3.1.0 is exciting, especially the support
structure changes for c++11!
But, just the other day I encountered an issue with the package
creation tools within Rcpp and Dirk referred me to 'Writing R
Extensions' [footnote 13] along with the comment that `.hpp` file
extensions are "verboten" on CRAN and then proceeded to find
2014 Apr 15
3
[LLVMdev] local lambdas: request for coding standard clarification/judgement call
Do local lambdas get named like variables or like functions?
E.g.
void foo() {
auto helper = [](...){...};
// or
auto Helper = [](...){...};
}
My gut is that it should be lowercase (named like a function) since I got a
weird feeling in my stomach seeing an upper-case name being called like a
function in new code.
-- Sean Silva
-------------- next part --------------
An HTML attachment
2005 Aug 07
1
request for clarification on Asterisk T.38 bounty
The bounty stands at $5,500. I'm seriously considering taking a shot
at it if I can find a decent T.38 provider to test with (I'm still
hoping for reliable PAYG T.38).
It looks like a lot of very smart people have done a lot of very hard
work (t38modem, spandsp) that would go towards getting this working.
At this point it appears to be mostly a matter of integration
2008 Mar 04
3
[LLVMdev] llvm-gcc 4.2 building failed on x86-64
Current llvm-gcc 4.2 building failed on X86-64, here is the dump
information:
xgcc -B/home/zsth/projects/llvm.org/build/cfe4.2obj/./prev-gcc/
-B/home/zsth/projects/llvm.org/install/x86_64-unknown-linux-gnu/bin/
-I../../../cfe4.2/libcpp -I. -I../../../cfe4.2/libcpp/../include
-I../../../cfe4.2/libcpp/include -DENABLE_LLVM -g -O2 -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
2013 Jun 12
0
[LLVMdev] "anchor" method policy, request for clarification
(+Chris, since I assume he wrote this policy - and, as I said in my
previous email, I wouldn't mind seeing some justification or just
seeing the rule go away & drop the anchors I added previously (or, if
we're going to keep it, we could add more anchors & actually get to
the point where we're -Wweak-vtable clean & enable that warning))
On Wed, Jun 12, 2013 at 1:44 PM,
2013 Jun 12
2
[LLVMdev] "anchor" method policy, request for clarification
I tried to build LLVM with 'gcc-4.8.1 -flto', and when linking unittest programs, I got the following error:
/tmp/cc8pMk84.ltrans30.ltrans.o:(.data.rel.ro._ZTIN4llvm2cl15OptionValueCopyISsEE[_ZTIN4llvm2cl15OptionValueCopyISsEE]+0x10): undefined reference to `typeinfo for llvm::cl::GenericOptionValue'
2016 Jan 30
0
Clarification requested
On Fri, 2016-01-29 at 14:38 +1100, John Gardeniers wrote:
> There are smb.conf items which can have multiple entries. e.g. "admin
> users". I see examples showing both comma separated and whitespace
> separated lists. Even our old Samba 3 conf file shows both being
> used.
> The man page doesn't show an example of a multiple list at all, so
> that
>
2016 Jan 29
2
Clarification requested
There are smb.conf items which can have multiple entries. e.g. "admin
users". I see examples showing both comma separated and whitespace
separated lists. Even our old Samba 3 conf file shows both being used.
The man page doesn't show an example of a multiple list at all, so that
doesn't help to clear this up.
So, for the sake of clarity, what is the proper/recommended
2011 Feb 08
1
Clarification about virsh migration options
I am trying to work out what all the options are for migrating a KVM
machine to another KVM machine, without using shared storage. The
documentation is not quite verbose and not intuitive, so I'm hoping
someone can explain this to me. The man pages show this syntax:
migrate optional --live --p2p --direct --tunnelled --persistent
--undefinesource --suspend --copy-storage-all --copy-storage-inc
2005 Feb 06
2
password ldap clarification requested...
Dear list,
I would like to know if the following statements are true, just to make
sure that my understanding of passwords/ldap stuff is correct...
Vampireing passwords from an nt4 pdc only populates the ldap server with
windows passwords, and not the (linux) userPassword. Authenticating
linux logons against this ldap server is therefore only possible using
winbind.
'Normal' ldap
2012 Jun 01
1
Requests for vignette clarification (re: Writing R Extensions)
I apologize that these questions are stupid and literal.
I write to ask for clarification of comments in the R extensions
manual about vignettes. I'm not great at LaTeX, but I'm not a
complete novice either, and some of the comments are puzzling to me.
1. I'm stumbling over this line:
"Make sure all files needed to run the R code in the vignette (data
sets, ...) are accessible
2019 Sep 12
3
Requesting clarification of some HWASAN behaviours.
Hello,
I'm working on implementing hwasan instrumentation in GCC, and have just
started discussing my current work-in-progress on the gcc-patches
mailing list.
(https://gcc.gnu.org/ml/gcc-patches/2019-09/msg00387.html -- the email
that Kostya saw and added people to).
I've gotten about as basic a user-space implementation as possible
(using the interceptor ABI) up and running, and would
2014 Jan 23
0
Re: PCI Passthrough
Oops! I blame Microsoft. I use Hotmail and am very, very unhappy that MS bought them out which leaves me stuck with Outlook, which sucks. I've always just hit reply in the past and it's worked. Now I'm going to have to be careful to make sure my replies go where I expect them.
Thank you very much for the information. I was really hoping to consolidate systems but that apparently
2009 Jun 10
3
Extracting Sequence Data from a Vector
Thanks in advance.
I have a vector of numbers which contain sections that are sequences
which increase by a value of 1 followed by a gap in the data and then
another sequence occurs, etc:
x<-c(1:3, 6: 7, 10:13)
From the vector I need to extract 2 items of information A) the first
number in the sequence (e.g., 1, 6, 10) and B) how many observations
were in each sequence section (e.g., 3,
2020 Oct 22
0
Samba clarification around GPL and VFS modules.
People who follow Samba development may
have noticed the following commit that
just went into the Samba repo:
https://git.samba.org/?p=samba.git;a=blob;f=VFS-License-clarification.txt;h=6b67381cc20412456d7d01a0587c0d627254a2b8;hb=1262b13f4db9502c36579b7dd740d8002e0baac9
For people who don't read git (I'm assuming
that's everyone :-) it's a clarification
around GPL license
2006 Mar 13
1
clarification on ipsec and masqing
Hi,
Just seeking some clarification on the current state of play with masqing
ipsec connections.
I have a client who establishs many different outbound ipsec connections. So
thats - many local clients, through linux firewall, to many different ipsec
''servers''.
they currently assign a public ip for outbound nat to each user to connect
out to the ipsec connection, so we have a one
2009 Sep 11
1
Clarification on Linux CD or DVD Writing
Dear All,
Currently working setup is CentOS4.4 Linux
I tried to google-out, but i can't able to findout
I need some clarification about CD writer support
1. How can i findout inserted disc is CD or DVD from command line
2. How can i findout inserted disc is empty from command line
3. How can i findout inserted disc size (like 700 MB or 4.7 GB) from
command line
2014 Aug 15
3
[Bug 2262] New: Clarification for the usage of Match directives with negations
https://bugzilla.mindrot.org/show_bug.cgi?id=2262
Bug ID: 2262
Summary: Clarification for the usage of Match directives with
negations
Product: Portable OpenSSH
Version: 6.6p1
Hardware: Other
OS: All
Status: NEW
Severity: enhancement
Priority: P5
Component:
2003 Apr 22
1
Ogg spec clarification
Hi,
I am considering implementing the Ogg bitstream spec. Having read the
spec, I am left with just one matter requiring clarification (making it
a pretty well written spec, in my book):
Can a packet begin on the same page as the previous packet ends on? The
spec does not appear to be explicit about this.
It would seem that I could indicate that there were (e.g.) 3 segments in
my page,