News for hackers. Stuff that matters.
Re:BSD vs. Linux (2005) by redwall_hp on Tuesday July 05, 2016 @03:14AM (#12034860)
ChuckMcM's criticisms seem to be of the X Window System, not of any particular desktop environment. Architecturally, it really doesn't fit with modern systems and has a lot of legacy baggage. It doesn't matter what DE you like, X still powers it, and it's the issue.

Wayland is on the way, which may bring Linux graphics into the 21st century, but I haven't been following that very closely.

Apple's way more on the ball about GUI stuff. While OS X lags behind in OpenGL support, which sucks for games, they nail everything their desktop environment needs to function. But notably, they don't use something like X. They have their own software stack.

Re:BSD vs. Linux (2005) by _wdzx on Tuesday July 05, 2016 @03:21AM (#12034877)
Enlighten me - what's the problem with the linux desktops?
Re:BSD vs. Linux (2005) by eropple on Tuesday July 05, 2016 @03:28AM (#12034901)
I would suggest reading (and comprehending) this excellent post for a review as to some of the tire-fire issues of X: http://blog.mecheye.net/2012/06/the-linux-graphics-stack/

DRI2 is an improvement over DRI, of course (which was already about five to eight years behind SOTA for GPUs when it came out), but it's still a rickety, insecure mess--for one, any application can fire messages at any window in the X environment and read input sent to any window, which has some obvious implications for the usefulness of containers on the desktop--that is sorely in need of replacement. This isn't to criticize X when it was developed, mind you--it was fine then. It should have been defenestrated by 2002.

Full disclosure: I get the feeling from your posts that you're looking to win an argument, rather than learn anything, so I'm not likely to respond to you further unless your tone changes. HTH. HAND.

Re:BSD vs. Linux (2005) by Anthony-G on Tuesday July 05, 2016 @04:40AM (#12035123)
Thanks for the informative link on the technologies that comprise the graphics stack on a typical GNU/Linux system. I see the author also has a great explanation of the different code components that form part of the Direct Rendering Infrastructure (DRI): http://blog.mecheye.net/2016/01/dri/
Re:BSD vs. Linux (2005) by _wdzx on Tuesday July 05, 2016 @04:27AM (#12035082)
For summary - X is just as insecure as windows/macos - we know it: wayland, mir and snappy is coming.

For your disclosure - don't be too lofty with me - I'm trying to understand your problems because I've a very different experience.

Re:BSD vs. Linux (2005) by roblabla on Tuesday July 05, 2016 @05:03AM (#12035209)
It's not a security problem really. That's just a side issue. The problem is, today, if I want to watch a movie, play a game, do anything that requires using some slightly advanced GPU stuff, I'll get tearing, artifacts, or downright crashes.

This is mostly because X11 sucks. (It's also partly because the proprietary nvidia drivers sucks). Nowadays I reboot on windows to watch netflix or play games (even linux-compatible ones) because the experience is just much better. Linux has been constrained to work stuff.

Now wayland is coming (apparently. NVidia is still trying to pull some shit[0]) and should fix all that. That's great ! I tested wayland a few months ago though, and my GPU's proprietary drivers weren't supported. So still no games, still no movies. :(.

0: http://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-Wa...

Re:BSD vs. Linux (2005) by fao_ on Tuesday July 05, 2016 @05:59AM (#12035398)
I think this honestly comes down to driver support rather than the Xorg stack. I dual boot with Windows 8.1 (Which is the OS supported by my manufacturer) and Arch Linux, and Arch is consistently more stable and faster for viewing videos and playing games than W8.1.

For example, I tried watching TNG from my external drive the other day (Using the latest VLC for both). On Linux this isn't a problem, the quality is good and there's no stuttering. On Windows it was hellish: The quality was extremely poor and it froze every (literal) 10 seconds to grab more data from the disk.

Re:BSD vs. Linux (2005) by cocotino on Tuesday July 05, 2016 @06:55AM (#12035555)
VLC is just a shadow of what it used to be. On Windows I recommend you to try something else like MPC-HC
Re:BSD vs. Linux (2005) by suby on Tuesday July 05, 2016 @08:53PM (#12040564)
How is VLC a shadow of what it used to be? I'm not trying to be argumentative, genuinely curious.
Re:BSD vs. Linux (2005) by vetinari on Tuesday July 05, 2016 @06:07AM (#12035424)
I've been using a Linux machine (Ubuntu+X11+nvidia+Kodi) as my HTPC for years. What's so sucky about it that I didn't notice during that time? No tearing, no artifacts, no crashes.
Re:BSD vs. Linux (2005) by roblabla on Tuesday July 05, 2016 @08:06AM (#12035807)
If you're using the nouveau drivers, everything's fine, but you don't get hardware acceleration. That means no games, but mostly tearing-free rendering, and no artifacts. The nvidia proprietary drivers is probably what's causing problems.
Re:BSD vs. Linux (2005) by vetinari on Tuesday July 05, 2016 @09:59AM (#12036450)
I'm using the proprietary drivers, 340.96-0ubuntu0.14.04.1 to be exact. The machine is 2009 vintage Atom 330 with Nvidia ION graphics, so I need VDPAU support for Full HD video decoding.
Re:BSD vs. Linux (2005) by krakensden on Tuesday July 05, 2016 @10:28AM (#12036632)
Nouveau has had hardware acceleration for years, although it has been desktop focused, not game focused.
Re:BSD vs. Linux (2005) by xorcist on Tuesday July 05, 2016 @07:20AM (#12035627)
Wayland is not going to make your Nvidia drivers more stable.
Re:BSD vs. Linux (2005) by digi_owl on Tuesday July 05, 2016 @08:03AM (#12035793)
I have the suspicion that by the time Wayland is done, it is as much a mess as X is right now. Meaning that we would be better of just finding a way to treat every program as a root window (effectively killing the information leakage that exist right now).
Re:BSD vs. Linux (2005) by Anthony-G on Tuesday July 05, 2016 @04:51AM (#12035163)
Back in 2011, security researcher, Joanna Rutkowska wrote a very enlightening article on the inherent security deficiencies of the X server architecture which allows allows any windowed application to control any other one: http://blog.invisiblethings.org/2011/04/23/linux-security-ci...
Re:BSD vs. Linux (2005) by nickpsecurity on Tuesday July 05, 2016 @09:10AM (#12036136)
Back in the 90's, the high-assurance community fleshed out the issues and solved many of them on top of strong endpoints. Here's an example:

https://www.acsac.org/2006/papers/epstein-paper.pdf

One from 2005 that I sent Joanna in gripe about Qubes not having a trusted path:

https://www.acsac.org/2005/papers/54.pdf

Good to see she added a better graphics system at some point. I suggest looking at prior work, though, as it's by security engineers with knowledge of adding it to every aspect of lifecycle and intent to minimize TCB. For example, GenodeOS is using Nitpicker + a microkernel. The abandoned EROS OS, whose site is still up, combined a different windowing system with a capability kernel and new networking stack. All to minimize risk in system in fine-grained way.

Re:BSD vs. Linux (2005) by velodrome on Tuesday July 05, 2016 @07:01AM (#12035571)
Re:BSD vs. Linux (2005) by danieldk on Tuesday July 05, 2016 @03:43AM (#12034954)
For a start, X11's security model. Every X11 application can read all keystrokes, mouse events, do screengrabs of other window's contents, etc.

In other words, your browser can snoop on what passwords you type into an X terminal if it wanted to or is compromised.

Re:BSD vs. Linux (2005) by eropple on Tuesday July 05, 2016 @03:52AM (#12034980)
Yup yup. Like, I recall a blog post by a Docker core contributor and employee saying, "Run your desktop apps in Docker containers to sandbox them! Just volume the X socket into the container."

(Of course, the Dockerfiles were also running apps--like, say, Chrome--as root, with no user namespaces, so it wasn't exactly great anyway.)

Re:BSD vs. Linux (2005) by Filligree on Tuesday July 05, 2016 @07:33AM (#12035677)
Sure it's breakable, but that still isn't bad advice. In practice, an application run with the evil bit set won't know how to break out of such a container, nor how to abuse the X socket.

It's only bad advice if you're relying on Docker to provide security against targeted threats. Know your enemy.

Re:BSD vs. Linux (2005) by lisivka on Tuesday July 05, 2016 @04:19AM (#12035062)
I.e. X11 working in same way as Windows, OS/2, BeOS, MacOS, OSX, etc.

But in Linux, I can run application in container or VM and then use VNC, RDP, or Spice to connect to it in secure manner.

Re:BSD vs. Linux (2005) by danieldk on Tuesday July 05, 2016 @05:40AM (#12035335)
I.e. X11 working in same way as Windows, OS/2, BeOS, MacOS, OSX, etc.

No, it's not. OS X has GUI isolation, an application cannot read keystrokes or read other application's contents, unless you explicitly give permission to do so. This is the reason why applications that can do more, such as Alfred, require you to explicitly enable these rights in the Privacy section of the Security & Privacy prefpane.

Windows also has GUI isolation (UIPI), but it's a bit murkier. As far as I understand, lower-privileged applications cannot read events from higher-privileged applications.

https://msdn.microsoft.com/en-us/library/bb625963.aspx

Re:BSD vs. Linux (2005) by idobai on Tuesday July 05, 2016 @04:22AM (#12035068)
Windows10 is already recording every keystroke/data of yours - what's the difference here? Also, Canonical's snappy packages can kinda solve this problem.
Re:BSD vs. Linux (2005) by dsp1234 on Tuesday July 05, 2016 @04:46AM (#12035150)
Since about the time of Windows Vista, non-administrative windows aren't able to hook keyboard events for administrative windows.[0]

So while it's possible for a program to listen to keyboard events for other non-administrative windows (such as the password for a browser), it isn't possible for a non-administrative window to grab keyboard input for stuff like windows password prompts, or information typed into administrative console windows, etc.

[0] - http://stackoverflow.com/questions/3169675/how-to-use-setwin...

Re:BSD vs. Linux (2005) by tychuz on Tuesday July 05, 2016 @08:02AM (#12035790)
This great argument again...
Re:BSD vs. Linux (2005) by aaron-lebo on Tuesday July 05, 2016 @03:25AM (#12034888)
Based on this thread, I'd say the problem is a lot of people haven't given them the time.

If you select your hardware, they work pretty flawlessly. Certainly right there with Windows or OSX or anything else. In a lot of cases you don't even need to be very selective, you just need to have a modern machine.

Re:BSD vs. Linux (2005) by merijnv on Tuesday July 05, 2016 @03:56AM (#12034991)
> Based on this thread, I'd say the problem is a lot of people haven't given them the time. > If you select your hardware, they work pretty flawlessly.

Maybe the fact that I have to give them time is one of the major problems? You know how much time I invested in getting my Windows and OSX desktops to work flawlessly? Zero.

Re:BSD vs. Linux (2005) by xorcist on Tuesday July 05, 2016 @07:32AM (#12035674)
If that's your anecdote, here's mine: _Every_ time I install Windows I need some third party driver just to make graphics and networking go. Then I need third party software just to get a development environment or a decent shell.

Upgrading these are hit and miss, and it's more common than not that third party drivers do not support newer versions of the operating system.

Linux, meanwhile, integrates all of these components. As long as you stay away from non-supported third party drivers it just works, and upgrades are painless. (Until some desktop developers change the GUI again, but that's another story.)

Re:BSD vs. Linux (2005) by throw2016 on Tuesday July 05, 2016 @05:15AM (#12035253)
I have been using Linux for a long time and while all the underlying criticisms of X and the desktop environments are valid I have to concede things have come a long way.

I think a modern Ubuntu 16.04 Unity desktop for instance is actually a bit of a revelation for long time Linux users because it just works out of the box. I didn't have to install a single package or fiddle with anything for a change. It's fast, smooth, robust and works exceedingly well out of the box and wait for this it's even a delight to use.

It's another thing I am a long time Gnome user and won't even have tried Unity because of the now I think inexplicable bad press Unity has got but it's been quite a revelation. I urge those who have not tried it yet due to bad press to give it a shot and prepare to be suprised.

I compare it to my Windows machines and OSX laptops and do not feel a particular difference apart from preferences and of course once you get into specific use cases like adobe apps or gaming there is still ground to cover. But for a general productivity desktop with full acceleration I think it's there in many ways. If you need a rich ecosystem of dev tools it goes to the top. There is of course always scope for improvement architecturally and other things and I think that is happening with mir, wayland and Vulcan.

Re:BSD vs. Linux (2005) by belorn on Tuesday July 05, 2016 @04:53AM (#12035175)
I do a windows reinstallation about once every second year, and I routinely get problems.

Network drivers are almost always missing. Looking at the device manager, about 5-10 different devices fails to auto-install, all part of the motherboards. The default graphic drivers tend to "start", but is limited in refresh rate and resolution, and moving around windows shows a noticeable stutter until I install some official drivers from the graphic card manufacturer. Sound normally works without issues.

On linux, the problems are almost the reverse. I have yet to have network problems on a fresh debian installation. Graphic is a all-or-nothing deal, which means either x-server starts up normally or it refuses to start completely. Sound is normally a pain, but looks to have better default behavior in the last 3 years or so.

Re:BSD vs. Linux (2005) by Decade on Tuesday July 05, 2016 @12:47PM (#12037734)
> I do a windows reinstallation about once every second year, and I routinely get problems. Network drivers are almost always missing. Looking at the device manager, about 5-10 different devices fails to auto-install, all part of the motherboards.

What are you reinstalling, Windows XP every time?

Newer versions of Windows are getting better at finding and installing sane drivers for the hardware. It’s still not perfect, Windows Update doesn’t have all the latest drivers and OEMs ruin everything especially on laptops, but these days I install the latest Windows and everything usually just works.

Re:BSD vs. Linux (2005) by belorn on Tuesday July 05, 2016 @02:11PM (#12038327)
Windows 7, desktop machine, and windows update don't really work without a functioning network connection.

But if you don't believe me, and choose to believe those reporting issues with Linux, just do a google search on windows install and network issues. There is plenty of people reporting the same issue. to cite windows own support page:

"If Windows can’t find a new driver for your network adapter, visit the PC manufacturer’s website and download the latest network adapter driver from there. If your PC can't connect to the Internet, you'll need to download a driver on a different PC and save it to a USB flash drive so you can install the driver on your PC"

Re:BSD vs. Linux (2005) by Sanddancer on Tuesday July 05, 2016 @03:24PM (#12038857)
At this point, Windows 7 is 7 years old. Do an apples to apples comparison here, and try getting your same hardware working on a copy of Ubuntu 9.04 or RHEL 5.3. How hard is it?
Re:BSD vs. Linux (2005) by belorn on Wednesday July 06, 2016 @06:00AM (#12042133)
Why should I only look at the exact date which windows 7 was released, rather than the date when a major release of debian got out, say 2011 with Debian 6.0? No network issue, occasional problems with x-server, problems with sound (as said above). Network works out of the box. On windows, issue with network, issue with graphics (until driver was installed), no problem with sound.

A few months ago I bought a gaming laptop on release date. Guess what, network worked without issue. X-server did not start until proprietary drivers were installed. Sound worked.

Windows release schedule do not match Debian's release schedule. Each year after a release, the default drivers will get worse, but the general experience can still be obtained by people who experience the install process. The experience I have endured with windows is issue with new motherboards and especially network drivers (and built-in raid cards for the installer... good grief, that was a wasted afternoon trying to get the installer to accept the raid drivers). Second to that, the fall back graphic drivers look crappy and is bad in every way except that its slightly better than a basic command prompt.

Re:BSD vs. Linux (2005) by aaron-lebo on Tuesday July 05, 2016 @04:04AM (#12035016)
We're literally talking about a 15 minute setup on a variety of nixes on a wide-range of hardware.

Intel chipsets and their graphics drivers have excellent support out of the box. That goes for everything from refurbished Thinkpads to Chromebooks to used Macbook Pros to new desktops.

Re:BSD vs. Linux (2005) by pbhjpbhj on Tuesday July 05, 2016 @04:19AM (#12035060)
Are you comparing like with like, your Windows & OSX desktops were preinstalled presumably, same price brackets too?
Re:BSD vs. Linux (2005) by eropple on Tuesday July 05, 2016 @03:32AM (#12034910)
I run a Linux desktop for work (typing on it right now) as a dual-boot with my Windows setup. It is a "modern machine", at least if an i7-6700K and a 980Ti are modern, and I couldn't get X to start with Ubuntu 16.04 LTS. And yet it did with Ubuntu 14.04, which is bizarre. My time is valuable enough that I didn't debug it further than that--if I wanted to light my time on fire I'd just go set up a Hackintosh and have a better desktop experience, so for now I'm getting by with 14.04. But that sucks profoundly; it was my first attempt at a Linux desktop in probably three years and I was pretty disheartened by how things have gotten worse for my use cases in that time.

"If you select your hardware," you can definitely have a decent time. But I don't know many people for whom the operating system is more important than what you can do with it, and part of "what you can do with it" is "use your hardware."

Re:BSD vs. Linux (2005) by aaron-lebo on Tuesday July 05, 2016 @03:41AM (#12034940)
That is bizarre. I don't use a lot of Ubuntu.

Having had an issue with Ubuntu and nvidia in the past, you might want to google NOMODESET and setting it at boot, which should let you boot into X/Unity and get the latest drivers.

> But I don't know many people for whom the operating system is more important than what you can do with it, and part of "what you can do with it" is "use your hardware."

Absolutely. But if OSes aren't directly equivalent (and the hackability of a nix gives it more power than Windows can ever have), then it's worth sorting out those hardware issues (as frustrating as they are).

Re:BSD vs. Linux (2005) by eropple on Tuesday July 05, 2016 @03:44AM (#12034956)
> Having had an issue with Ubuntu and nvidia in the past, you might want to google NOMODESET and setting it at boot.

Thanks; I later ran into something that hinted at that. Frankly, though, at this point I don't care. I have something that works and will be patched until 2019. I don't care about my desktops. Every second I spend debugging something stupid on a desktop is a wasted second. This is bad for me and I resent it.

> and the hackability of a nix gives it more power than Windows can ever have

Ehh--if you have to use that "hackability" to get something that is minimally usable, that's kind of a push. (Or, when you consider OS X, a serious negative, because the only thing I have to do to get OS X to where I want is install Homebrew and a short list of packages, none of which require configuration.) I don't care about desktop environments or tiled window managers, the extent of my interaction with my WM, which I could not name, is a sort-of reimplementation of Aero Snap. Again, if I wanted to throw a bunch of time away on an operating system, I would set up a Hackintosh and actually be able to use Photoshop. Which, in keeping with the theme of "Linux desktops are a fractal of unusability", would be a significant improvement. I tried to avoid a reboot and use the GIMP yesterday for something. I think I need counseling now. I ended up using Pinta, whose layered image format ("OpenRaster", which wants to be a standard but it seems like nobody uses it?) is so bonkers and edge-case that ImageMagick doesn't even support it, to say nothing of Photoshop or even Paint.NET.

It turned out, kind of to my surprise, that Linux on the desktop offers very little to me as a Linux developer, sysadmin, and long-time entrails-reading "power user". That's pretty damning, in my book.

Re:BSD vs. Linux (2005) by throwanem on Tuesday July 05, 2016 @12:55PM (#12037806)
> OpenRaster

Another ocean boiled, courtesy of the Free Desktop Project.

Re:BSD vs. Linux (2005) by eropple on Tuesday July 05, 2016 @01:02PM (#12037861)
Yeah...I went down a pretty bad rabbit hole trying to figure that one out. I mean, XCF already exists? And application support is marginal, rather than nonexistent.
Re:BSD vs. Linux (2005) by throwanem on Tuesday July 05, 2016 @01:09PM (#12037917)
I'm pretty sure the only reason the initials are "FDP" and not "NIH" is because somebody else came up with the latter.
Re:BSD vs. Linux (2005) by vbernat on Tuesday July 05, 2016 @03:58AM (#12034996)
Without a bug report, nobody can tell if your case is unique or general. You spend time to rant here but with a bit of additional time, you could have opened a bug report with the appropriate information and maybe help people running into the same problem.
Re:BSD vs. Linux (2005) by eropple on Tuesday July 05, 2016 @04:13AM (#12035045)
I think it should be obvious that I don't have a reproducible case anymore; this was a couple months ago now, after I built a desktop. Nor am I interested in expending multiple hours creating one, because that doesn't benefit me--my stuff works now, if suboptimally. I couldn't leave it in that state then, because I had work to do with that hardware; I couldn't leave it in a trashed state just in case somebody had questions and needed to autopsy it, now, could I? Expending more time than I did would be better served just biting the bullet and setting up a Hackintosh so I have an environment I like, rather than tolerate.

And this isn't a "rant". I promise you, when I'm ranting, you will know.

Re:BSD vs. Linux (2005) by criddell on Tuesday July 05, 2016 @08:46AM (#12035981)
> if I wanted to light my time on fire I'd just go set up a Hackintosh and have a better desktop experience

As I understand it, installing macOS on non-Apple hardware is a license violation. Your employer is okay with that?

Re:BSD vs. Linux (2005) by eropple on Tuesday July 05, 2016 @12:12PM (#12037436)
I'm self-employed, so yes. I've got four grand of Apple gear in my office, and if they sold an xMac I'd buy one tomorrow. I don't consider it to be a moral question, and in practice Apple doesn't seem to really care.
Re:BSD vs. Linux (2005) by criddell on Tuesday July 05, 2016 @01:35PM (#12038099)
I work for a software company and it's pretty strict about honoring license terms because we want our customers to do the same.
Re:BSD vs. Linux (2005) by eropple on Tuesday July 05, 2016 @02:39PM (#12038563)
That's a fair position. From mine, Apple gets its vig from me in plenty of other ways. There's zero pirated software, music, videos, etc. in my house or my business; giving Apple another channel through which to sell me stuff, from developer licenses to apps, doesn't trouble me.
Re:BSD vs. Linux (2005) by mozumder on Tuesday July 05, 2016 @10:47AM (#12036778)
They're Linux.

How are you supposed to run Adobe inDesign on a Linux desktop?

Or any other useful application, really.

Linux should just kill off its desktop. Mac OS X won the Unix desktop wars, and has the expected use models of a desktop, with a proper modern GUI API as well, instead of the ancient X hacks.

Re:BSD vs. Linux (2005) by _wdzx on Sunday July 10, 2016 @10:17AM (#12065643)
> Linux should just kill off its desktop. Mac OS X won the Unix desktop wars, and has the expected use models of a desktop, with a proper modern GUI API as well, instead of the ancient X hacks.

Mac OSX won the "desktop wars"? That's not even funny - it's one of the most awful DEs. You people have clearly no experience with any other OS besides the one from your favorite brand. "Hacker news"... more like "Noob Army News".

Re:BSD vs. Linux (2005) by _wdzx on Sunday July 10, 2016 @02:57PM (#12066709)
> How are you supposed to run Adobe inDesign on a Linux desktop?

With wine...

> Or any other useful application, really.

You search in the software center or in your menu and start the app. Simple. FUD elsewhere, apple-noob.

Re:BSD vs. Linux (2005) by dang on Sunday July 10, 2016 @05:31PM (#12067357)
We've banned this account for repeatedly violating the HN guidelines. If you don't want it to be banned, you're welcome to email [email protected]. We're happy to unban people when there's reason to believe that they'll only post civil and substantive comments in the future.
Re:BSD vs. Linux (2005) by cbd1984 on Monday July 11, 2016 @06:09AM (#12070013)
Please stop disrupting conversations.
Re:BSD vs. Linux (2005) by dang on Monday July 11, 2016 @05:30PM (#12074856)
You have a longstanding pattern of abusing HN, including (I believe) with multiple accounts that we've had to ban in the past. We've given you many warnings and requests to stop. Since it seems you can't or won't stop, I'm banning this account as well.