Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror

Comment: Re:libressl-2.1.3 (Score 1) 97

by Anon E. Muss (#48904753) Attached to: OpenSSL 1.0.2 Released

Just because one compiler for one platform fails to support a popular C extension doesn't mean the library isn't portable.

Except that the one platform is Windows, which accounts for the vast majority of desktop PC's and laptops, and a significant chunk of servers. And the one compiler is the standard for Windows, used by the vast majority of Windows developers.

You don't have to like this, but it is the truth.

In my opinion, any software that can't compile on Windows using the native toolchain doesn't qualify as "portable". That doesn't make it bad software. It just isn't "portable" software.

Comment: Re:libressl-2.1.3 (Score 1) 97

by Anon E. Muss (#48904623) Attached to: OpenSSL 1.0.2 Released

libressl supports pretty much any unix-like OS

Oh good, both Country and Western.

I know there's a guy working on Windows support as well.

Let me know what the guy working on Windows support actually gets it working. Until then it doesn't count. And by "working", I mean working with the Microsoft toolchain, which like it or not, is the official and most widely used toolchain for Windows.

Comment: Re:libressl-2.1.3 (Score 5, Insightful) 97

by Anon E. Muss (#48895959) Attached to: OpenSSL 1.0.2 Released

libressl is NOT portable. Supporting BSD and Linux is not the definition of "portable" (see also: "We play both types of music: Country and Western"). The libressl code depends on the non-standard #include_next preprocessor directive, so it can only build with GCC (and probably clang, which emulates many GCC-isms). Forget about building on Windows using Microsoft's C compiler.

OpenSSL remains the only portable SSL library that can be used by both open source and commercial developers alike. Which is really a shame, because OpenSSL sucks. All the bad things the libressl people have said about OpenSSL are absolutely true.

Comment: Re:Thank you! (Score 2, Interesting) 125

by Anon E. Muss (#48289669) Attached to: OpenBSD 5.6 Released

... check out OpenBSD before checking out FreeBSD, and I cannot stress this enough. FreeBSD developers don't use their own operating system; they run it in a Virtual machine on their Macs, and it shows.

Citation needed.

Suspend/resume has been broken there since 2008, and drivers for any recent Intel graphics adapter will not run (you cannot switch from Xorg to a console and back) properly.

Yeah, it can suck to run a server-focused OS on a desktop/laptop.

FreeBSD devs do not care about their OS

This is objectively false. Any devs working for free must care, of they'd hack on something else. Any devs being paid must have an employer who cares. The problem is that the people hacking/funding FreeBSD don't care about the same parts of the system that you do.

Comment: Re:are the debian support forums down? (Score 3, Informative) 286

by Anon E. Muss (#48176459) Attached to: Ask Slashdot: Stop PulseAudio From Changing Sound Settings?

... the way systemd has turned into something similar to the bloated beast that is the Windows 'svchost.exe' ...

+1 to the anti-systemd sentiment.

-1 to using svchost.exe to make your case. svchost is just a container process. The real issue is the Windows architecture/philosophy that encourages a proliferation of services.

(I like Unix and I like Windows. Each has their place. Trying to turn one into the other is a big mistake.)

Comment: Good luck with that (Score 1) 139

by Anon E. Muss (#47783659) Attached to: Australian Consumer Watchdog Takes Valve To Court

Option #1: Valve has no physical presence in Australia, and tells the Australian government to go fuck themselves. Government responds by banning Valve from doing business in Australia. Good luck enforcing that. To the extent they do manage to enforce it, it will be taking action against Australian citizens, since they have no power over Valve.

Option #2: Valve doubles prices in Australia. Y'all can have all the consumer protection you want, but you're going to pay for it.

Comment: The fix is to delete the font cache (Score 5, Informative) 179

by Anon E. Muss (#47675037) Attached to: Microsoft Black Tuesday Patches Bring Blue Screens of Death

The way to fix this is to delete \Windows\System32\FNTCACHE.DAT. The file will automatically be regenerated on the next boot.

(Information found on Microsoft Support Forum and used to successfully fix my own system.)

How do you delete the file if you can't boot?

(1) Press F8 during boot to get to the Windows boot manager advanced options screen.
(2) Select "Repair".
(3) Provide password for a local account that's a member of the Administrator group.
(4) Select "Command Prompt".
(5) Find drive letter assigned to Windows partition (may not be C: in the repair environment!).
(6) Delete \Windows\System32\FNTCACHE.DAT.
(7) Exit command prompt and reboot system.
(8) Fixed!

----------

And now, since this is /., here is the required Windows bashing...

This bug demonstrates the danger of running your GUI in kernel mode (win32k.sys). One stray pointer can ruin your whole day. In this case the pointer was sufficiently invalid to cause a bugcheck. A stray pointer that silently scribbles on other kernel data structures is even worse.

"Those who would give up essential Safety, to purchase a little temporary Performance, deserve neither Performance nor Safety."

Comment: The Mill (Score 2) 125

I think NVidia tied their hands by retaining the ARM architecture. I suspect the result will be a "worst of both worlds" processor that doesn't use less power or provide better performance than competitors.

In order execution, exposed pipelines, and software scheduling are not new ideas. They sound great in theory, but never seem to work out in practice. These architectures are unbeatable for certain tasks (e.g. DSP), but success as general purpose processors has been elusive. History is littered with the corpses of dead architectures that attempted (and failed) to tame the beast.

Personally, I'm very excited about the Mill architecture. If anybody can tame the beast, it will be these guys.

Comment: Re:Legally correct decision with awful results (Score 1) 303

Splits in the circuits are more common than you might imagine, and the Supreme Court doesn't always resolve them. A lot depends on how substantial the split is. Minor differences don't always get resolved.

In any event, this case isn't "ripe" for appeal to the Supreme Court yet. The Supremes rarely get involved until all lower court proceedings have been exhausted, and this case just got sent back for retrial on the issue of fair use. The process can be maddening for the individual litigants, but it makes sense for the legal system overall.

Comment: Legally correct decision with awful results (Score 5, Informative) 303

(I actually read the court ruling before posting this)

tl;dr version: The results will likely be awful, but the decision appears legally correct.

Google won at trial because the judge decided that the Java API was not copyrightable. I absolutely believe that API's should not be copyrightable, but that isn't what the law says. Copyrightability has a very low threshold. The trial judge screwed up by applying legal standards related to fair use to the question of copyrightability. The appeals court was correct to reverse.

The case now goes back to the district court. There will be a new trail with a new jury, but the only issue will be whether Googe's copying of the Java API is fair use. The original jury deadlocked on this question. Fair use decisions are very subjective, so it's hard to predict how this will turn out. All I can say is that I hope Google wins.

P.S. None of this decision was related to patents. Oracle lost on their patent claims at trial, and that stands.

Comment: Re:It's a trap! (Score 2) 171

by Anon E. Muss (#41896225) Attached to: GM Brings IT Dev Back In House; Self-Driving Caddy In the Works
At the macro level, adding employment to Detroit would be a good thing. At the micro level, it could be a bad thing for individuals who take a job at GM, and then find themselves working in conditions that make Dilbert look good by comparison. I understand "any port in a storm, and any job in a recession." But if you have a choice, would you really want to go to work for somebody who is absolutely hated by many of his prior employees?

Elliptic paraboloids for sale.

Working...