Displaying 20 results from an estimated 129 matches for "reissues".
Did you mean:
reissue
1999 Sep 15
0
FreeBSD Security Advisory: FreeBSD-SA-99:03.ftpd REISSUED
-----BEGIN PGP SIGNED MESSAGE-----
=============================================================================
FreeBSD-SA-99:03 Security Advisory
FreeBSD, Inc.
Topic: Three ftp daemons in ports vulnerable to attack.
Category: ports
Module: wu-ftpd and proftpd
2000 Nov 06
0
FreeBSD Security Advisory: FreeBSD-SA-00:61.tcpdump [REISSUED]
-----BEGIN PGP SIGNED MESSAGE-----
=============================================================================
FreeBSD-SA-00:61 Security Advisory
FreeBSD, Inc.
Topic: tcpdump contains remote vulnerabilities [REISSUED]
Category: core
Module: tcpdump
Announced:
2011 Jan 04
0
[LLVMdev] Is PIC code defeating the branch predictor?
On Jan 3, 2011, at 11:30 PM, Jakob Stoklund Olesen wrote:
> I noticed that we generate code like this for i386 PIC:
>
> calll L0$pb
> L0$pb:
> popl %eax
> movl %eax, -24(%ebp) ## 4-byte Spill
>
> I worry that this defeats the return address prediction for returns in the function because calls and returns no longer are matched.
Yes, this will defeat the
2011 Sep 22
4
R CMD check file issues
This problem is likely to be specific to Windows, and particularly Win7.
After a successful build of a package (R CMD build addendum), I immediately
run an R CMD check for the same package.
Not always, but _very_ often, I get the following error:
C:\Users\nisabbe\Documents\@Doctoraat\R>R CMD check addendum
Loading required package: tcltk
Loading Tcl/Tk interface ... done
Loading
2011 Jan 04
4
[LLVMdev] Is PIC code defeating the branch predictor?
I noticed that we generate code like this for i386 PIC:
calll L0$pb
L0$pb:
popl %eax
movl %eax, -24(%ebp) ## 4-byte Spill
I worry that this defeats the return address prediction for returns in the function because calls and returns no longer are matched.
From Intel's Optimization Reference Manual:
"The return address stack mechanism augments the static and dynamic
2011 Jan 07
0
Idea to possibly improve flac?
On Fri, Jan 07, 2011 at 02:22:51PM -0800, brianw at sounds.wa.com wrote:
>
> First of all, I am not aware of any official source of FLAC files
> that provide MP3 sourced data.
Unofficial sources (such as Usenet and that torrent site with the old
fashioned sailing ship as its logo) are much more likely to have FLAC
files that were made from lossy audio.
And I vaguely remember reading
2011 Jan 08
5
Idea to possibly improve flac?
Lots of comments throughout this one...
On Jan 7, 2011, at 15:28, Declan Kelly wrote:
> On Fri, Jan 07, 2011 at 02:22:51PM -0800, brianw at sounds.wa.com wrote:
>> However, you should be aware that many modern producers use software
>> to create their music, and when the software stores sound clips in
>> MP3 format, what you end up with is music that sometimes looks like
2024 Apr 07
1
NUT v2.8.2, the Easter Egg Edition
A hiccup was reported about validating the tarball signature on some
systems, so it was reissued from another workstation. Please don't worry :)
Jim Klimov
On Tue, Apr 2, 2024, 01:06 Jim Klimov <jimklimov+nut at gmail.com> wrote:
> Hello all,
>
> After a prolonged labour with a few re-issues of the tag and many pushes
> during the day, NUT v2.8.2 was found in a strange
2024 Apr 07
1
NUT v2.8.2, the Easter Egg Edition
Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes:
> A hiccup was reported about validating the tarball signature on some
> systems, so it was reissued from another workstation. Please don't worry :)
Do you mean the signature was re-issued, which is ok, or that the
tarball was re-issued, which is very much not ok(!) ?
2024 Apr 07
1
NUT v2.8.2, the Easter Egg Edition
A hiccup was reported about validating the tarball signature on some
systems, so it was reissued from another workstation. Please don't worry :)
Jim Klimov
On Tue, Apr 2, 2024, 01:06 Jim Klimov <jimklimov+nut at gmail.com> wrote:
> Hello all,
>
> After a prolonged labour with a few re-issues of the tag and many pushes
> during the day, NUT v2.8.2 was found in a strange
2024 Apr 07
1
NUT v2.8.2, the Easter Egg Edition
Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes:
> A hiccup was reported about validating the tarball signature on some
> systems, so it was reissued from another workstation. Please don't worry :)
Do you mean the signature was re-issued, which is ok, or that the
tarball was re-issued, which is very much not ok(!) ?
2008 Apr 18
1
Message UID Question
I have referred to the wiki and the RFC, but I still can't find the
exact answer I'm looking for. From what I know, Dovecot uses the IMAP
standard of 32 bit integers to uniquely identify messages.
After a message is deleted from the mbox, can this UID ever be reissued
to a new message or is that UID retired? What about after the 2 billion
limit is reached?
Thanks!
2004 Aug 18
0
CentOS-2 update 5
...ages which have been modified for
CentOS-2, the release suffix .c2.release will be appended to the
existing release. All packages which currently are missing this suffix
will be reissued with the new suffix. The suffix release will always
start at 1 and be incremented if a package needs to be reissues with
only centos changes. When the original release is increased, the centos
release will start again at 1.
This is part of a new automated procedure which should result in
reproducible modifications which will speed up the release of errata for
modified packages and cut down on errors in the...
2011 Jan 19
1
courier-imap to dovecot-imap migration: missing TLS_TRUSTCERTS feature
Hi,
I'm attempting an one-to-one migration from courier-imap to dovecot-imap.
current state:
Imap-server has a self signed certificate
Every client/user has a self signed client certificate that is used for
SSL/TLS client authentication.
All certificates are self signed "standalone" cerfificates - no CA
hierarchy/structure is made.
With courier-imap we could just put every
2011 Feb 27
1
Standard location for hotplug-time hdparm invocation
I need to disable the spin-down on an external USB drive because it spins
down spontaneously while in use. The drive forgets the spindown-disable
state across power outage so I need to reissue the hdparm command with each
boot or hotplug. Where should I put the hdparm command to do this?
2005 Oct 02
3
What does the error "stale nonce' mean?
I'm receiving the following error over and over, adnauseam:
Oct 1 23:59:53 NOTICE[3194]: chan_sip.c:5890 check_auth: stale nonce
received from 'CNAME-CID <sip:5551212@192.168.1.X>'
Does anyone know what "stale nonce" is?
Thanks!
Paul Conn
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2003 Dec 13
2
Change one file, and they all get sent!
Hi,
Just starting out with rsync, and I think I might be missing a
fundamental point of how it works.
Scenario:
I start an rsync daemon on host A, and define a module 'test' on the
rsyncd.conf file. 'test' is essentially my home directory on host A
I then sign on to host B and issue
rsync --progress --recursive --links --stats arthur::test/ /var/tmp/haggis
This copies
2007 May 16
5
[RFC] pv-scsi driver (scsiback/scsifront)
Hi all.
We developped a pv-scsi driver that we refered Fujita-san''s scsi-driver
and blkback.
(see, http://www.xensource.com/files/xensummit_4/Xen_Summit_8_Matsumoto.pdf)
The pv-scsi driver''s feature is as follow:
* Guest has dedicated SCSI-HBAs of Dom0.
* Guest can send scsi_cdb to the HBAs.
* Guest recognises the HBAs from hostno of xenstore.
Currentlly, We are
2008 Dec 27
3
[LLVMdev] Using CallingConvLower in ARM target
Attached is a prototype patch that uses CCState to lower RET nodes in
the ARM target. Lowering CALL nodes will come later.
This patch does not handle f64 and i64 types. For these types, it
would be ideal to request the conversions below:
def RetCC_ARM_APCS : CallingConv<[
CCIfType<[f32], CCBitConvertToType<i32>>,
CCIfType<[f64], CCBitConvertToType<i64>>,
2016 Jul 21
2
Blockpull behavior when interrupted
Hello,
I use snapshot-create-as followed by blockpull when creating external snapshots
of VMs. This works well, however I am curious about the behavior of blockpull
after an unexpected shutdown (or SIGKILL). If a blockpull is in progress and an
unexpected power loss occurs, will the VM continue to reference the backing file
for the parts of it that have not yet been copied? Or, will will the disk