search for: fiascos

Displaying 20 results from an estimated 67 matches for "fiascos".

Did you mean: fiasco
2000 Jun 26
0
FIASCO
[ cc'd to the vorbis list because I thought y'all would be interested ] Hi, I saw the freshmeat.net posting for FIASCO (http://ulli.linuxave.net/fiasco/) this afternoon, and was really excited another bright mind had put some cool A/V software out for free. I was wondering if you have ever heard of the Ogg and Vorbis projects (more info on them at xiph.org). They are
2001 Sep 18
1
Printer fiasco...
OK, First, thanks for all of the help recently. I appreciate it. But...I have just implemented the cvs code as to be able to use the 'use client driver' option because win nt/2k machines have been seeing an 'Access denied, unable to connect' error for the print queues and this will apparently fix this. I will describe my setup and what I have done thus far: RH 7.1 Samba 2_2 cvs
2004 Nov 10
3
[LLVMdev] LLVM and the "static initialization order fiasco"
Hello, I'm getting bitten by the "static initialization order fiasco" http://www.parashift.com/c++-faq-lite/ctors.html#faq-10.12 The static data causing the problem is the static TypeMap<PointerValType, PointerType> PointerTypes; and other typemaps. The background is that in our product we are using an overridden new operator to track memory allocations. This system is
2009 Sep 05
1
the opengl and glu fiasco with wine 1.1.29 and nvidia binary
i have been compiling wine from git regularly with no problems whatsoever until now. ./configure now always spits out not found messages for -lGL and -lGLU. opengl and direct3d support cannot be enabled. how do i fix that. i'm on fedora 11 with nvidia 190.32 drivers. thanks for any help i can get.
2016 Nov 11
2
initialization-order-fiasco in MCTargetDesc/X86MCAsmInfo.cpp
Mehdi, Teresa, Not sure if this is caused by one of your recent commits, or by someone else's, please excuse me if that's unrelated to your work... http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fast/builds/542/steps/check-llvm%20asan/logs/stdio ==26383==ERROR: AddressSanitizer: initialization-order-fiasco on address 0x000002ef41d8 at pc 0x0000009d1aa5 bp 0x7ffd0cd72b50 sp
2014 Apr 18
4
Changing SSL certificates - switching from self-signed to RapidSSL
Hi all, Ok, been wanting to do this for a while, and I after the Heartbleed fiasco, the boss finally agreed to let me buy some real certs... Until now, we've been using self-signed certs with the following dovecot config: ssl = required ssl_cert = </etc/ssl/ourCerts/imap.pem ssl_key = </etc/ssl/ourCerts/imap_key.pem Now, I've created new keys/certs and the CSR, got the new
2020 Nov 13
0
[RFC] Defined initialization order in Support/Registry
Dear List, First things first, this is based off a bug report and a (less than ideal) patch by yours truly: https://github.com/clangd/clangd/issues/578 https://reviews.llvm.org/D91351 Currently Plugins appear in the Registry linked list in an undefined order due to the 'static initialization order fiasco'. For most registries this doesn't pose a problem as there is no observable
2015 May 15
2
https everywhere.
On 05/15/2015 02:49 PM, Matthew Miller wrote: > On Fri, May 15, 2015 at 03:44:39PM -0400, James B. Byrne wrote: >> What are the plans for the CentOS repos with respect to authentication >> and https everywhere? At the moment it is a trivial exercise to >> perform a MTM attack during a yum update over http. > > Since the packages themselves are signed, what risk are you
2000 Apr 25
1
How will META data be handled
In order to avoid another fiasco like ID3 tags in MP3 elemental audio streams, what's the plan for handling META data? --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/
2005 Nov 05
1
Bother
This afternoon, after my fiasco with the other machine, I decided to bring the drive home and install it in the primary machine here, boot from the normal drive, then mount the 4.1 i386 drive so I could make changes and check things. What happened next was totally unexpected. After decompressing the kernel and starting the boot, there were all kinds of error messages scrolling off the
2018 Oct 22
5
[fdo] Code of Conduct questions
Hi, I've cross-posted this to freedesktop@, as the xdg@ list is only used for actual specification development. On Mon, 22 Oct 2018 at 00:36, Jacob Lifshay <programmerjake at gmail.com> wrote: > Hi, we were thinking of asking if freedesktop would host Kazan (https://github.com/kazan-3d/kazan) for us, however some of our community members have objections with how freedesktop's
2010 Oct 15
8
fraud advice
Hi, Embarrassed as I am to write this, I am hoping for some advice. One of our very first PBX installs, now six years old, was "taken advantage of" over the past few weeks. A victim of sipvicious, I assume, that managed to guess one of the SIP passwords. 4000 calls to various middle eastern destinations have been placed, which ended up being sent over our customer's PSTN
2004 Mar 28
4
Could someone email me with the code for glm.nb ?
Hi -- subject says all. I just want the code for that function, which I guess was in Venables and Ripley as early as 1994. Well, and for any of the sub-functions that glm.nb calls. I can't install the entire MASS library. If the code for just glm.nb (again, don't want to touch the MASS library, last time I tried to install it was a complete nightmare and fiasco) is somewhere on a
2010 Jul 18
1
DSL battling rojter - help!
My internet connection is through a Siemens Speedstream 4100 DSL modem connected to AT&T (sbcglobal.net), and a Dlink WBR-2310 router. Late last night, I changed the administrative password on the router, and for some reason it didn't take right, so I had to reset the router to get the password cleared. Unfortunately, this also lost all my connection settings to the DSL, and I lost the
2007 Jul 10
3
Re: Online Monthly Meeting scheduled to 11th July 2007, 06:00 UTC; Confirmed
Guys and Silvia, do come please. If this meeting is a fiasco, there will be a lot of stuff to discuss on some other meeting in what...? November? Not good. If you cannot come in time (like Silvia and Sebastian) we will wait a bit, but do come. If you cannot come at all, state your opinions on the issues at hand through the mailing lists. Your opinion is important.
2007 Jul 10
3
Re: Online Monthly Meeting scheduled to 11th July 2007, 06:00 UTC; Confirmed
Guys and Silvia, do come please. If this meeting is a fiasco, there will be a lot of stuff to discuss on some other meeting in what...? November? Not good. If you cannot come in time (like Silvia and Sebastian) we will wait a bit, but do come. If you cannot come at all, state your opinions on the issues at hand through the mailing lists. Your opinion is important.
2007 Jul 10
3
Re: Online Monthly Meeting scheduled to 11th July 2007, 06:00 UTC; Confirmed
Guys and Silvia, do come please. If this meeting is a fiasco, there will be a lot of stuff to discuss on some other meeting in what...? November? Not good. If you cannot come in time (like Silvia and Sebastian) we will wait a bit, but do come. If you cannot come at all, state your opinions on the issues at hand through the mailing lists. Your opinion is important.
2007 Jul 10
3
Re: Online Monthly Meeting scheduled to 11th July 2007, 06:00 UTC; Confirmed
Guys and Silvia, do come please. If this meeting is a fiasco, there will be a lot of stuff to discuss on some other meeting in what...? November? Not good. If you cannot come in time (like Silvia and Sebastian) we will wait a bit, but do come. If you cannot come at all, state your opinions on the issues at hand through the mailing lists. Your opinion is important.
2003 May 23
0
Shorewall 1.4.4
Given that there are new features and there are external changes to get around the Fireparse fiasco, I have called this release 1.4.4 rather than 1.4.3b. Problems Corrected: None. New Features: 1) A REDIRECT-rule target has been added. This target behaves for REDIRECT in the same was as DNAT-does for DNAT in that the Netfilter nat table REDIRECT rule is added but not the companion
2003 May 27
0
Shorewall 1.4.4a
The Fireparse --log-prefix fiasco continues. Version 1.4.4a omits the logging rule number if the LOGFORMAT value does not contain ''%d''. The default value of LOGFORMAT is then changed to "Shorewall:%s:%s:" so that the maximum length of a short zone name is once again back at 5. -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \