Displaying 8 results from an estimated 8 matches for "getitng".
Did you mean:
geting
2004 Nov 28
2
am i baned or something?
Soemthing goes wrong with this mail list:
I am getitng something like it:
>Sorry. Your message could not be delivered to:
>Aster risk (Mailbox or Conference is full.)
??????????
Regards,
Corvin
2017 Apr 04
3
Compiling custom "vmlinuz" PXE kernel?
Hello CentOS list, I still need help.
Does anyone know how I would go about creating my own "vmlinuz" PXE
kernel? I'm still trying to get the NUC6CAYH to load to a LiveCD, and I'm
getitng nowhere with Intel.
My company wants to do hundreds of these per month; we're not above paying
for professional help at this point.
My current line of reasoning is to get whatever specialized memory and CPU
drivers the NUC6CAYH requires to recognize properly and bake them in to a
custom vmli...
2010 Feb 04
6
problems with SPC charts in R
...type="p")
Similarly I am able to plot P chart for defective dataset successfully
using following command
y<-read.table("Defect_data_2008.csv",sep=",",header=TRUE)
attach(y)
obj<-qcc(D[trial],sizes=size[trial],type="c")
But while plotting C chart I am getitng following error
Error in plot.new() : figure margins too large
Could u please help me in solving these error.
Thanks in advance.
--
View this message in context: http://n4.nabble.com/problems-with-SPC-charts-in-R-tp1467901p1467901.html
Sent from the R help mailing list archive at Nabble.com.
2017 Aug 08
2
DWARF: Ranges base address specifier entries & Gold's gdb-index 32 bit bug
...debugger tuning=gdb flag to your compiles, it wouldn't disable the feature,
because the flag would be consulted at CodeGen time and not at compile time
when you passed the tuning flag. (oh, actually the tuning is passed down
via TM Options anyway, not on the CU - so I guess you wouldn't be getitng
the tuning at all today because that flag already doesn't follow the per-CU
model... well I guess that makes it easier)
> Setting it via IR/metadata is adding a bunch of complexity just to work
> around a gold bug. Not worth it IMO.
>
Fair enough. Any thoughts on whether it should...
2017 Apr 04
0
Compiling custom "vmlinuz" PXE kernel?
...; Subject: [CentOS] Compiling custom "vmlinuz" PXE kernel?
>
> Hello CentOS list, I still need help.
>
> Does anyone know how I would go about creating my own "vmlinuz" PXE
> kernel? I'm still trying to get the NUC6CAYH to load to a LiveCD, and I'm
> getitng nowhere with Intel.
>
> My company wants to do hundreds of these per month; we're not above paying
> for professional help at this point.
>
> My current line of reasoning is to get whatever specialized memory and CPU
> drivers the NUC6CAYH requires to recognize properly and...
2004 Nov 27
4
very newbie question
Hi everyone!
I have very simple question, how to limit SIP phone user making
calls to for example longdistant calls?
Maybe:
Put in his context in sip.conf
context which don't provide possibility to make such calls?
Is it correct?
thanks for any help,
regards,
Corvin
2017 Aug 08
2
DWARF: Ranges base address specifier entries & Gold's gdb-index 32 bit bug
...g=gdb flag to your compiles, it wouldn't disable the feature,
> because the flag would be consulted at CodeGen time and not at compile time
> when you passed the tuning flag. (oh, actually the tuning is passed down
> via TM Options anyway, not on the CU - so I guess you wouldn't be getitng
> the tuning at all today because that flag already doesn't follow the per-CU
> model... well I guess that makes it easier)
>
>
> Setting it via IR/metadata is adding a bunch of complexity just to work
> around a gold bug. Not worth it IMO.
>
>
> Fair enough. Any tho...
2017 Aug 07
4
DWARF: Ranges base address specifier entries & Gold's gdb-index 32 bit bug
Context:
In r309526 (with a followup fix in r309529) I implemented the use of
DWARF's debug_ranges base address specifier entries to reduce the number of
object file relocations needed for debug_ranges*.
* in a particular binary internally, an optimized build had a 70% reduction
in debug_ranges.reloc, a 16% decrease in total object size (with compressed
debug info and fission)
Nico noted