search for: alarmist

Hi Colin! I would like to know, that these following "vulnerabilities" does affect FreeBSD's reliability? If the answer is "yes", what version of FreeBSD affected, when will be fixed, etc. http://projects.info-pull.com/moab/MOAB-12-01-2007.html http://projects.info-pull.com/moab/MOAB-10-01-2007.html Thank you! -- kobi

...panes which could be tampered with. Also permissions have been reset at every boot in my working directory. I've worked on this machine for about 17 months, and I know its rhythms and what should be what. The permissions problem is persistent and new. I do not think I am being paranoid or alarmist. I have always had a NAT router, commercial firewall, and virus protection. The only thing I can think of is a hidden *nix program from a downloaded program (shareware/freeware) (I have scanned all packages for viruses). I am almost positive it did not come via e-mail. I say almost because I h...

On 06.07.2017 15:35, Robert Nichols wrote: > On 07/06/2017 04:43 AM, Volker wrote: >> Hi all, >> >> one of my lv has become completely unaccessible. Every read access >> results in a buffer io error: >> >> Buffer I/O error on dev dm-13, logical block 0, async page read >> >> this goes for every block in the lv. A ddrescue failed on every single

...rst round to know the size of the damage. I just wanted to warn all other buildbot owners and general public that we do have a tough situation going, and if their patches are not essential, maybe voluntarily hold on for a while would be a good idea. (Though, now that I read my email, it does sound alarmist. I'm in panic mode right now, so I apologise :). But all other affected bots won't come back until Galina reverts and restart the master (or until their owners work around like I did). There's no way of knowing how bad it is if the bots continue chugging bogus green status to every com...

...D > should read as some special "nothing here" value (0?), everything > else can RAZ/WI". > > We could just say "all RAZ/WI", since this merely causes Linux > currently to print a warning about the bad magic number, and > then subsequently make Linux less alarmist about the zero. > > We could also define that the transport should look as if > there's some sort of 'null' backend plugged in. This would > be more effort on the qemu side though, I think. There are two aspects of the problem: 1. Current implementation of the virtio core...

...D > should read as some special "nothing here" value (0?), everything > else can RAZ/WI". > > We could just say "all RAZ/WI", since this merely causes Linux > currently to print a warning about the bad magic number, and > then subsequently make Linux less alarmist about the zero. > > We could also define that the transport should look as if > there's some sort of 'null' backend plugged in. This would > be more effort on the qemu side though, I think. There are two aspects of the problem: 1. Current implementation of the virtio core...

We''re still hard at work on Rails 1.2, which features all the new dandy REST stuff and more, but a serious security concern has come to our attention that needed to be addressed sooner than the release of 1.2 would allow. So here''s Rails 1.1.5! This is a MANDATORY upgrade for anyone not running on a very recent edge (which isn''t affected by this). If you have a public

...I remove the only the snapshot but not the base volume? Will > > $ lvremove /dev/vg0/lv-vm-tviewer > > leave the base volume untouched? That should do it. You will get one less warning if you deactivate that LV first: lvchange -an vg0/lv-vm-tviewer You will still get an overly alarmist warning that removing the snapshot LV will change the source LV. Don't worry about it. The only "change" is that the source LV will no longer be flagged as a snapshot origin. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it.

Hi, Is it possible to implement some kind of alarmist triggering some action, by sending SIP OPTIONS messages regularly to check that other peer is still online? I'm using Asterisk version 1.2.11 which I know it doesn't have any SNMP module, just 1.4 branch is being developing one; but is it any other way in Asterisk 1.2 to trigger some ac...

Hello, I'm using samba 3.4.8~dfsg-2 with "vfs objects = acl_xattr". [share] path = /home/users/xxxx valid users = xxxx read only = No create mask = 0666 directory mask = 0770 vfs objects = acl_xattr Here is my problem, i'm connecting to my share, which have a folder 'f01' with some acl. I created a folder and broke inherit 'f02'.

Folks, As Nico and Diana investigated earlier [1], there was a change in Zorg which made buildbots update one source directory (llvm.src) but build from another (llvm), which made *all* builds from the same revision, no matter the update. Essentially, the bots were all lying when they said this or that commit "passed", since they were still testing the same old commit. All our bots

Guys, After i got the port forwarding and everything else working as per my previous post, i ran a shields-up scan from grc.com on the firewall, i.e. a scan of the external interface. I m a little suprised at the results. On the firewall i have postfix running ( smtp port 26 ), openssh ( ssh port 22) and port forwarding of port 85 (on the firewall ) to an internal host. The Shields-Up scan

On 13 November 2016 at 00:13, Kirill M?ller wrote: | On 13.11.2016 00:00, Dirk Eddelbuettel wrote: | > On 12 November 2016 at 22:54, Kirill M?ller wrote: | > | > [... lots of stuff deleted ...] | > | > | I noticed this because plogr logging crashed in dplyr (compiled with gcc | > | 6) right after upgrading to yakkety; I still had a gcc-5 built version | > | of Rcpp installed.

Hi all, I''ve got xen-4.1.1 running with linux-3.0.0-rc5 and am trying to start my first guest, f14-x86_64, which does boot on bare metal. The configs below show kernel, ramdisk, and disk assignments for the virtual machine. They also show that the virtual machine uses the target disk devices. The last section shows part of the boot sequence starting with the disk assignments,

...easy way > to test at compile-time whether the difference between two labels was > zero, then skip that entry in the lists entirely. Would save space and > address the original issue I had with debug_ranges terminating early. > (should've thought about that much earlier than my more alarmist "oh > deer, we need to fundamentally change how linkers resolve relocations > because everything's been broken and we just didn't realize it" - > fixing the compiler not to produce zero-length ranges would've been > less risky & probably still worth doing - tho...

...compile-time whether the difference between two labels was >>> zero, then skip that entry in the lists entirely. Would save space and >>> address the original issue I had with debug_ranges terminating early. >>> (should've thought about that much earlier than my more alarmist "oh >>> deer, we need to fundamentally change how linkers resolve relocations >>> because everything's been broken and we just didn't realize it" - >>> fixing the compiler not to produce zero-length ranges would've been >>> less risky &...

>On Mon, Jul 20, 2020 at 10:32 AM Alexey Lapshin ><alapshin at accesssoftek.com> wrote: >> >> >On Fri, Jul 17, 2020 at 1:55 PM Alexey Lapshin <a.v.lapshin at mail.ru> wrote: >> >> >> >> >Пятница, 17 июля 2020, 19:42 +03:00 от David Blaikie <dblaikie at gmail.com>: >> >> > >> >> >On Fri, Jul 17, 2020 at

...e between two labels was > > >>> zero, then skip that entry in the lists entirely. Would save space > and > > >>> address the original issue I had with debug_ranges terminating early. > > >>> (should've thought about that much earlier than my more alarmist "oh > > >>> deer, we need to fundamentally change how linkers resolve relocations > > >>> because everything's been broken and we just didn't realize it" - > > >>> fixing the compiler not to produce zero-length ranges would've been...

...hether the difference between two labels was > >>> zero, then skip that entry in the lists entirely. Would save space and > >>> address the original issue I had with debug_ranges terminating early. > >>> (should've thought about that much earlier than my more alarmist "oh > >>> deer, we need to fundamentally change how linkers resolve relocations > >>> because everything's been broken and we just didn't realize it" - > >>> fixing the compiler not to produce zero-length ranges would've been > >>&g...

...en two labels was >> > >>> zero, then skip that entry in the lists entirely. Would save space and >> > >>> address the original issue I had with debug_ranges terminating early. >> > >>> (should've thought about that much earlier than my more alarmist "oh >> > >>> deer, we need to fundamentally change how linkers resolve relocations >> > >>> because everything's been broken and we just didn't realize it" - >> > >>> fixing the compiler not to produce zero-length ranges would&...