You are doing it wrong; permanently failing on recoverable EINTR and EAGAIN errors. See here for how to do it right.
Re:I can't feel any responsiveness improvements.
on
Gnome 2.18 Released
·
· Score: 1
Isn't that whhat gnome-keybinding-properties is for? Interesting, that's new (or at least new since I stopped using GNOME). Maybe in another five years they will revert all their other asshat dogma (I seem to recall them being dead set against preferences like this) and have a desktop that I will want to use.
Re:I can't feel any responsiveness improvements.
on
Gnome 2.18 Released
·
· Score: 1
Likewise, I reported a bug in gnome-terminals handling of tab-selection keypresses, also with a patch. It languished for a couple of years before someone finally tweaked the patch and committed it.
In the meantime, I quit using GNOME and started using KDE. I haven't looked back - it is heaps faster, uses less memory and is able to do simple things like configure my keyboard shortcuts from a GUI.
No, IPv6 is enabled in the default install, though it does use only link-local addresses by default. This means that the attacker has to be on the same layer-2 network as the victim, but this is still classified as a remote exploit. Theo agreed, and the homepage has already been updated.
Even interior routing for multicast is in flux; just a few years ago, the model changed to single-sender, which simplifies routing but changes the service model so only one source can efficiently send data.
I would disagree that intradomain multicast is in flux - PIM sparse is eight years old and widely supported. It sucks to firewall if you are stuck using Vendor C equipment though*, though (better) alternatives exist.
* it wasn't so long ago that their recommendation was to bypass firewalls using GRE tunnels:)
Well, by definition, the 95th percentile is far from average
No, the 95th percentile is not defined as being "far" from average (it could be below the mean in fact) and it doesn't even need to be "far" from the median (it could be equal to the median in some distributions).
You are displaying your ignorance (or are just trolling) - porting software exposes bugs. Most frequently these bugs are precisely things that work "by luck" on the platform on which the software originally ran because they depend on false assumptions. As the software is ported to another platform, the false assumptions are made visible. This applies doubly to something like OpenBSD, which goes out of its way to make bad assumptions visible, particulaly those related to memory management
It is disappointing to see a free software project dismissing threats as "theoretical". Today's "theoretical" vulnerabilities are tomorrow's exploits. Worse, the article hints that these threats are fundamental design flaws - the developers should be working to fix these and not issuing PR speak to cover them.
IANAOE, but an obvious solution would be to use selective mirror, prism or diffraction grate to permit only the wavelengths tho which the PV cells are sensitive through. In particular they could eliminate the IR portion - IIRC no PV cells are really sensitive to this section of the spectrum.
This is broadcasted very loudly in their choice to integrate a memory controller onboard their CPUs; in order to upgrade chips with an integrated memory controller, you have to replace the whole board, and managers aren't going to want to do that very often.
I have yet to see any enterprise server that has had its "chips upgraded" beyond installing a 2nd CPU in a SMP-capable system with only one processor shipped. Never. Not once.
If you prefer a text-based environment for preparation of documents, etc. then you may prefer MagicPoint to Powerpoint. It has a bit of a learning curve and imperfect documentation but once you have some templates prepared, making a presentation is as simple as plonking a couple of lines of text in a file.
Oh, it doesn't do spinning/jiggling/blinking/etc. transitions, but I view this as a (major) plus.
Even if your systems are on all the time, you can use CPU speed throttling to save some watts - I bet most 24x7 servers are not at full capacity all the time. Packages exist for several operating systems (OpenBSD and Linux at least) to dynamically throttle CPU clock speed, thereby reducing power consumption. It isn't likely to be a huge saving, but even a couple of % across a number of machines can add up to quite a saving.
"War"? Oh, you probably mean "proxy war", where the US government sponsored assassins, fascist states and terrorists. Though you might possibly be referring to a real war where you had the shame of killing over a million humans in the name of "freedom".
Government paying for free software? send in the troops...
You are misinformed, trolling or both. Most of OpenBSD's efforts in recent years have been directed at proactive security. OpenBSD was the first operating system to add ProPolice to its compiler, the first to implement address space randomisation, the first to add privilege separation to every daemon that needs privilege.
The result of this is that a security hole is either a) not exploitable to begin with, b) incredibly difficult to exploit, or c) not very productive even if it is exploited. All your caps-lock-on ranting misses this entirely.
I doubt that you want to educate yourself rather than ranting, but other people might be interested in Theo's paper on all this.
In addition to good, audited code and these proactive measures, OpenBSD includes systrace, which can enforce mandatory policy on application basis. It doesn't do everything that SELinux does, but it is far, far easier to use.
No, that has nothing to do with compression performance. (it isn't a bugfix either: it is a new feature)
Re:Did that say signed vs. unsigned integer bugs?
on
OpenSSH 4.2 released
·
· Score: 1
We have checked the code for these problems before, but these changes are about changing internal APIs so mistakes are easier t see and more difficult to make in new code.
Your lame sarcasm aside, these were changes to internal APIs to make signed vs unsigned errors more difficult for developers to make. E.g. we changed several internal functions to not accept or return signed values, thus eliminating the need for signed integers in many contexts. So yeah, it is proactive.
Slashdot Mirror
You are doing it wrong; permanently failing on recoverable EINTR and EAGAIN errors. See here for how to do it right.
Except that they aren't.
I reported a bug in Metacity's focus-follows-mouse behaviour years ago. It turned out to be a dupe of another bug where we were told that the behaviour (different to every other WM I have ever used) was "by design". When a few other people chimed in agreeing and suggesting that the traditional behaviour restored or a (possibly hidden) preference added to control it, the bug was unceremoniously closed. The Metacity developer preferred some tweaky special casing approach that could "do the right thing", but five years later noone has gotten it to work.
Likewise, I reported a bug in gnome-terminals handling of tab-selection keypresses, also with a patch. It languished for a couple of years before someone finally tweaked the patch and committed it.
In the meantime, I quit using GNOME and started using KDE. I haven't looked back - it is heaps faster, uses less memory and is able to do simple things like configure my keyboard shortcuts from a GUI.
No, IPv6 is enabled in the default install, though it does use only link-local addresses by default. This means that the attacker has to be on the same layer-2 network as the victim, but this is still classified as a remote exploit. Theo agreed, and the homepage has already been updated.
I would disagree that intradomain multicast is in flux - PIM sparse is eight years old and widely supported. It sucks to firewall if you are stuck using Vendor C equipment though*, though (better) alternatives exist.
* it wasn't so long ago that their recommendation was to bypass firewalls using GRE tunnels :)
No, the 95th percentile is not defined as being "far" from average (it could be below the mean in fact) and it doesn't even need to be "far" from the median (it could be equal to the median in some distributions).
So tell me, what does 0 ÷ nullity equal?
You are displaying your ignorance (or are just trolling) - porting software exposes bugs. Most frequently these bugs are precisely things that work "by luck" on the platform on which the software originally ran because they depend on false assumptions. As the software is ported to another platform, the false assumptions are made visible. This applies doubly to something like OpenBSD, which goes out of its way to make bad assumptions visible, particulaly those related to memory management
It is disappointing to see a free software project dismissing threats as "theoretical". Today's "theoretical" vulnerabilities are tomorrow's exploits. Worse, the article hints that these threats are fundamental design flaws - the developers should be working to fix these and not issuing PR speak to cover them.
Is AMD's Pacifica virtualisation system any better?
Nice work trimming out the ones from other countries.
IANAOE, but an obvious solution would be to use selective mirror, prism or diffraction grate to permit only the wavelengths tho which the PV cells are sensitive through. In particular they could eliminate the IR portion - IIRC no PV cells are really sensitive to this section of the spectrum.
except when you are in the digital domain.
you are SQUEEZING THE JUICE!
This is broadcasted very loudly in their choice to integrate a memory controller onboard their CPUs; in order to upgrade chips with an integrated memory controller, you have to replace the whole board, and managers aren't going to want to do that very often.
I have yet to see any enterprise server that has had its "chips upgraded" beyond installing a 2nd CPU in a SMP-capable system with only one processor shipped. Never. Not once.
If you prefer a text-based environment for preparation of documents, etc. then you may prefer MagicPoint to Powerpoint. It has a bit of a learning curve and imperfect documentation but once you have some templates prepared, making a presentation is as simple as plonking a couple of lines of text in a file.
Oh, it doesn't do spinning/jiggling/blinking/etc. transitions, but I view this as a (major) plus.
Even if your systems are on all the time, you can use CPU speed throttling to save some watts - I bet most 24x7 servers are not at full capacity all the time. Packages exist for several operating systems (OpenBSD and Linux at least) to dynamically throttle CPU clock speed, thereby reducing power consumption. It isn't likely to be a huge saving, but even a couple of % across a number of machines can add up to quite a saving.
it is quite clear, if you rtfa
"War"? Oh, you probably mean "proxy war", where the US government sponsored assassins, fascist states and terrorists. Though you might possibly be referring to a real war where you had the shame of killing over a million humans in the name of "freedom".
Government paying for free software? send in the troops...
yawn, another lame PAX troll who won't put his name to his invective.
You are misinformed, trolling or both. Most of OpenBSD's efforts in recent years have been directed at proactive security. OpenBSD was the first operating system to add ProPolice to its compiler, the first to implement address space randomisation, the first to add privilege separation to every daemon that needs privilege.
The result of this is that a security hole is either a) not exploitable to begin with, b) incredibly difficult to exploit, or c) not very productive even if it is exploited. All your caps-lock-on ranting misses this entirely.
I doubt that you want to educate yourself rather than ranting, but other people might be interested in Theo's paper on all this.
In addition to good, audited code and these proactive measures, OpenBSD includes systrace, which can enforce mandatory policy on application basis. It doesn't do everything that SELinux does, but it is far, far easier to use.
No, that has nothing to do with compression performance. (it isn't a bugfix either: it is a new feature)
We have checked the code for these problems before, but these changes are about changing internal APIs so mistakes are easier t see and more difficult to make in new code.
Your lame sarcasm aside, these were changes to internal APIs to make signed vs unsigned errors more difficult for developers to make. E.g. we changed several internal functions to not accept or return signed values, thus eliminating the need for signed integers in many contexts. So yeah, it is proactive.