I can't help but ask... Why didn't you try a burn in test across a few of your systems first? I come from the Linux side if things so maybe there's something I missed or don't know how Microsoft mandates the update process in a Windows environment.
Sincerely curious.
I'm in San Jose, Ca, and I've been seeing some intermittent connectivity loss the last 1-2 weeks... But that might be a localized issue. Otherwise I'm fine.
This big outage isn't affecting me. If it is DNS, then I won't see any issues. I'm running my own DNS servers. I'm also running Comcast business rather than Xfinity, so slight chance that's a factor as well.
I honestly don't think it would make that much of a difference on all 3 of my points. For example, I definitely recall other people having their cars vandalized over other GOP candidates in the past.
I'm not a Trump supporter (but I was also never a Hilary supporter), but I am a San Francisco native, I work in Silicon Valley, and I did interview with Google and did fairly well (though I chose to work elsewhere, a decision I'm very thankful for after this debacle). I also consider myself to be independent these days.
That being said, I think there's several reasons for a lack of Trump bumper stickers you'd see in Google's parking lot.
1) I think you're right, that conservatives would be afraid (and rightfully so) to show Trump bumper stickers in the Google parking lot for fear of violating the group think.
2) Silicon Valley is pretty left leaning in general, there's just not a whole lot of conservatives in the area.
3) I think having a Trump bumper sticker in the bay area would be a great way to get your car vandalized.
I think it's easy to fall into the trap of "But your employers are the ones paying you!". And that is a good point, but not the whole story.
I think, depending on the situation, it can absolutely be okay. For example, some years ago, I worked for a large company where between long stretches of activity, we'd also get some downtime, sometimes even for a month or 2. Now that's not to say that NOTHING was going on. But for the moment, all the big projects were completed, and there were absolutely no other deadlines. At first it would be nice, but very quickly I'd get bored out of my mind so I'd start working on personal projects.
During these times, there would literally be nothing else for me to do. It was maddening. There's only so much slashdot and only so many kitten videos that can pass the day. By the time more big projects started coming down the pipeline, I was RELIEVED! The team would bang on those for a few months, and the cycle would repeat.
It helped that no one knew this is what I was doing, and my personal work looked exactly like my regular work. However, I'd check my inbox regularly as well as the ticket queue, and I'd immediately jump on anything that came through. I _always_ gave absolute priority to my work over my personal projects.
If it's okay to browse the web while things are slow because there's literally nothing else to do... Why not personal projects? Like browsing the web, just don't let it interfere with your work.
Now if you're working on personal projects INSTEAD of doing your job, that's a really shitty thing to do. However, it's probably worth talking to that employee before outright canning them to make sure you have a good understanding of the situation rather than just jumping conclusions.
Fedora 25 marks the first release of a mainstream distro to switch to Wayland as the default display server (it will set X11 if it's detected that you're using incompatible drivers such as the nvidia drivers for example). I'm surprised there's no front page story about this on/.
Hell, there's not even token a mention of it in this summary.
Does anyone have any good recommendations for a device that can mount NFS (I guess smb/cifs would be okay too) that also supports a wide range of media formats? Currently, I'm using a Boxee, and it still mostly works, but it's getting long in the tooth. I may need to build my own custom XBMC device as the eventual replacement...
I've had the same experiences with 15.10. 15.04 was much less unreliable. The most common crash I see in KDE (and occurs several times daily for me in 15.10) is with krunner (the run dialog you bring up with alt-F2). It crashes several times a day for me. 50% of the time, krunner is automatically restarted for me, the remaining time I have to manually run "krunner &" in a terminal. For whatever reason, whether it's distribution centric or it's KDE 5.4 (or possibly 5.5, whatever is in the KDE backports ppa for 15.10) has become extremely crashy. More often than not, KDE ends up crashing back to the login screen when I resume on my laptop.
I've been using KDE since the 1.1.x days, and I haven't really liked gnome much since the 1.2.x (although I have yet to try gnome 3 at all)... So it's not like I'm some anti-KDE zealot.
I think I'll give gnome 3 under X11 a try when Fedora 24 comes out, and then try it under Wayland (so I have a basis for comparison). I may or may not like Gnome 3, but I'm very excited to try Wayland which should be a much more complete experience. I've tried Weston and Enlightenment via Rebecca Black OS, and while I certainly encountered too many bugs to even think about daily use, the experience was otherwise much superior. Never do I see random little lags or skips when dragging windows around, etc in Wayland. I see these relatively often on my system under X11 with an i75960x, and Nvidia titan X, so it's certainly not due to lack of hardware...
I read the article a few hours ago on my way to work, and I don't recall it being mentioned that the KDE port to Wayland is very much a work in progress, but this is slashdot and no one readons TFA's anyway so it's worth mentioning here. Of course the KDE port to Wayland isn't going to be very good as in a work-in-progress and more of a technology preview at this point.
I've been meaning to try Gnome 3 under Wayland... This blog post makes me even more interested. Although I should probably try Gnome 3 under X11 first so I have a basis for comparison.
This is supposed to be a major issue with X. X lets any client read all input sent to the X server, view any window, etc. These aren't bugs in X, it's how it's designed.
Wayland doesn't allow this behavior so probably such a trojan wouldn't be possible with Wayland (outside of the audio aspect that is).
I've been a KDE user since the 1.1.x days, but even I'm pretty excited about the Gnome 3.18 release. This release is supposed to have very polished Wayland support!
If the Wayland support is all it's cracked up to be, Fedora should default to Wayland over X.org with Gnome 3.20. I don't use Fedora either, but if 24 defaults to Wayland, I'll install it to another partition at the very least.
At this point, it's mostly just you. All this work going on vastly simplifies the stack. Wayland compositors are much simpler than the entire X stack (which has to be supported even though much of it isn't used). Unfortunately, X still needs to stay around in some capacity so we can still play our proprietary games,etc.
Agreed. Wayland development appeared to accelerate after Ubuntu announced Mir. If the only thing that ever happens because of Mir is that it made the rest of the Linux community unite behind Wayland and speed its adoption, that's still a good thing.
From what I've heard about the commit statistics, there was no real change in Wayland development itself. Where we're seeing the acceleration is the desktop environments realizing they really needed to start their porting work. THIS is definitely a good thing.
And Ubuntu started Mir because their engineers seem to believe Mir has fundamental performance advantages over Wayland in resource-constrained environments like phones. It's possible they're completely wrong, but if they're right then we need Mir for Linux on smart phones.
There seems to be this myth that Wayland doesn't work with Android GPU drivers. Mir's support for Android drivers uses libhybris to achieve this, which is atually Wayland library for allowing Wayland to work with Android GPU drivers.
And we're starting to this sort of thing a lot. Mir really just isn't too fundamentally different from Wayland. Typically when Mir support is added to something, they've simply taken the Wayland support and have made a relatively small amount of changes (sdl2, xwayland/xmir, etc). I think in the long run, Canonical will partially throw in the towel and Mir will end up being a Wayland compositor that's also capable of running Mir specific (mobile?) apps.
I don't know that the Mir devs really believed these issues. That's not to say that such claims weren't made (most/all of which were thoroughly debunked the same day they came out), but the real reason for Mir's existence is control for their mobile platform. Wayland is MIT licensed, and Mir is GPLv3 which a CLA. If canonical had been more honest about their reasons for Mir, I think they'd be receiving far less flak for it. No other reason really makes much sense. They're just too similar.
This quote makes zero sense:
"...reliance on Windows and DirectX (and to a lesser extent Mac OS), systems that cannot be relied upon in the long term."
Really, because my experience with Linux and backwards / forwards support for both software and hardware has been vastly worse than Windows from XP through 8. Sure before XP, Windows 9x was terrible, but are we really going to keep basing derp derp FUD on a 5 year window of hard lessons from nearly 15 years ago?
Can we just fess up and admit that SteamOS is an effort predicated on a personal beef Gabe Newell has with Microsoft and especially the fact that Windows 8 included it's own store and that store was not Steam. The story is well documented and the whole industry is going to blow a lot of money on development just to satisfy one man's ego.
Linux supports older hardware than windows 7 and 8, no question. Regarding the software... You definitely have a point there. Almost. The Linux kernel itself actually has backwards compatibility for userspace software going back quite a bit. It's mostly glibc that breaks this. If it isn't happening already, it will eventually. You'll be downloading games from that simply ship with their own libraries. I believe a lot of Windows software works this way.
You can actually get a lot of old loki games to run in linux by installing older versions of various libraries. Although, you do encounter some issues. For example, Simcity 3000 won't give you sound since it wants to use esd (which hasn't seen use in years), but the game will otherwise run. This takes some work to setup, but if the games on steam do this for you, it's a non-issue.
Not anymore. Asus mentioned they have sold millions of high end/gaming motherboards as gamers no longer buy Dells and replace the GPU like they did in the old days.
You can thank crappy PSU's and proprietary tiny cases for this decline as gamers are the only ones who upgrade besides corporations and they only do so every 10 years now when MS decides it needs more money for another OS upgrade.
The article is a bit dated, but apparently Asus was expecting to ship 22.2 million mid to high end boards in 2013. It's starting to seem custom rigs (particularly for gaming) is hardly a niche. Maybe the market's somewhat smaller than desktop machines, but it's certainly large enough to be considered healthy and is still growing.
I think I may very well put this on to my S4. I got the S4, because nothing else really looked appealing to me, but I'm really not a fan of touchwiz. If this is better than touchwiz (very hard not to be), then I'll give it a shot.
The fact that Sailfish uses Wayland also makes this very interesting to me.
steam works pefect in GNOME shell in archlinux. unity is not a requeriment.
To add to this, I don't think SteamOS will use unity period. I suspect they'll use a custom window manager or perhaps full screen mode for steam os will be the window manager.
I personally run steam in KDE without issues.
But kubuntu 13.10 won't be using xmir, that's just vanilla ubuntu (and possibly xubuntu I think).
Running an X desktop on Mir by using the XMir layer just adds another unnecessary layer (that is bound to have bugs), so it's good the Lubuntu and Kubuntu folks are avoiding that. It's a shame KDE5 (which will have Wayland support) is a good ways off.
Slashdot Mirror
Bacteria Discovered In Irish Soil Kills Four Drug-Resistant Superbugs
Although missing from the summary, it also kills potatoes.
I can't help but ask... Why didn't you try a burn in test across a few of your systems first? I come from the Linux side if things so maybe there's something I missed or don't know how Microsoft mandates the update process in a Windows environment. Sincerely curious.
I'm in San Jose, Ca, and I've been seeing some intermittent connectivity loss the last 1-2 weeks... But that might be a localized issue. Otherwise I'm fine. This big outage isn't affecting me. If it is DNS, then I won't see any issues. I'm running my own DNS servers. I'm also running Comcast business rather than Xfinity, so slight chance that's a factor as well.
I honestly don't think it would make that much of a difference on all 3 of my points. For example, I definitely recall other people having their cars vandalized over other GOP candidates in the past.
I'm not a Trump supporter (but I was also never a Hilary supporter), but I am a San Francisco native, I work in Silicon Valley, and I did interview with Google and did fairly well (though I chose to work elsewhere, a decision I'm very thankful for after this debacle). I also consider myself to be independent these days.
That being said, I think there's several reasons for a lack of Trump bumper stickers you'd see in Google's parking lot.
1) I think you're right, that conservatives would be afraid (and rightfully so) to show Trump bumper stickers in the Google parking lot for fear of violating the group think.
2) Silicon Valley is pretty left leaning in general, there's just not a whole lot of conservatives in the area.
3) I think having a Trump bumper sticker in the bay area would be a great way to get your car vandalized.
This totally wouldn't be happening if Hillary had been elected.
Sarcasm aside, I hope more and more people are starting to get that we're being screwed by both sides of the aisle.
Bleh.
I think it's easy to fall into the trap of "But your employers are the ones paying you!". And that is a good point, but not the whole story.
I think, depending on the situation, it can absolutely be okay. For example, some years ago, I worked for a large company where between long stretches of activity, we'd also get some downtime, sometimes even for a month or 2. Now that's not to say that NOTHING was going on. But for the moment, all the big projects were completed, and there were absolutely no other deadlines. At first it would be nice, but very quickly I'd get bored out of my mind so I'd start working on personal projects.
During these times, there would literally be nothing else for me to do. It was maddening. There's only so much slashdot and only so many kitten videos that can pass the day. By the time more big projects started coming down the pipeline, I was RELIEVED! The team would bang on those for a few months, and the cycle would repeat.
It helped that no one knew this is what I was doing, and my personal work looked exactly like my regular work. However, I'd check my inbox regularly as well as the ticket queue, and I'd immediately jump on anything that came through. I _always_ gave absolute priority to my work over my personal projects.
If it's okay to browse the web while things are slow because there's literally nothing else to do... Why not personal projects? Like browsing the web, just don't let it interfere with your work.
Now if you're working on personal projects INSTEAD of doing your job, that's a really shitty thing to do. However, it's probably worth talking to that employee before outright canning them to make sure you have a good understanding of the situation rather than just jumping conclusions.
Not Duke Nukem status. There's been working live CD demos for years now.
Fedora 25 marks the first release of a mainstream distro to switch to Wayland as the default display server (it will set X11 if it's detected that you're using incompatible drivers such as the nvidia drivers for example). I'm surprised there's no front page story about this on /.
Hell, there's not even token a mention of it in this summary.
Does anyone have any good recommendations for a device that can mount NFS (I guess smb/cifs would be okay too) that also supports a wide range of media formats? Currently, I'm using a Boxee, and it still mostly works, but it's getting long in the tooth. I may need to build my own custom XBMC device as the eventual replacement...
No, Wayland fixes all of this. In fact, this is in part why Mir uses the exact same input library as wayland: libinput.
Responding to my own post because I realized that citation is need:
https://lwn.net/Articles/51737...
https://blog.martin-graesslin....
No, Wayland fixes all of this. In fact, this is in part why Mir uses the exact same input library as wayland: libinput.
I've had the same experiences with 15.10. 15.04 was much less unreliable. The most common crash I see in KDE (and occurs several times daily for me in 15.10) is with krunner (the run dialog you bring up with alt-F2). It crashes several times a day for me. 50% of the time, krunner is automatically restarted for me, the remaining time I have to manually run "krunner &" in a terminal. For whatever reason, whether it's distribution centric or it's KDE 5.4 (or possibly 5.5, whatever is in the KDE backports ppa for 15.10) has become extremely crashy. More often than not, KDE ends up crashing back to the login screen when I resume on my laptop.
I've been using KDE since the 1.1.x days, and I haven't really liked gnome much since the 1.2.x (although I have yet to try gnome 3 at all)... So it's not like I'm some anti-KDE zealot.
I think I'll give gnome 3 under X11 a try when Fedora 24 comes out, and then try it under Wayland (so I have a basis for comparison). I may or may not like Gnome 3, but I'm very excited to try Wayland which should be a much more complete experience. I've tried Weston and Enlightenment via Rebecca Black OS, and while I certainly encountered too many bugs to even think about daily use, the experience was otherwise much superior. Never do I see random little lags or skips when dragging windows around, etc in Wayland. I see these relatively often on my system under X11 with an i75960x, and Nvidia titan X, so it's certainly not due to lack of hardware...
I read the article a few hours ago on my way to work, and I don't recall it being mentioned that the KDE port to Wayland is very much a work in progress, but this is slashdot and no one readons TFA's anyway so it's worth mentioning here. Of course the KDE port to Wayland isn't going to be very good as in a work-in-progress and more of a technology preview at this point.
I've been meaning to try Gnome 3 under Wayland... This blog post makes me even more interested. Although I should probably try Gnome 3 under X11 first so I have a basis for comparison.
This is supposed to be a major issue with X. X lets any client read all input sent to the X server, view any window, etc. These aren't bugs in X, it's how it's designed.
Wayland doesn't allow this behavior so probably such a trojan wouldn't be possible with Wayland (outside of the audio aspect that is).
"...suggesting that after their massive push towards Ashley Madison users, people have stopped falling for their scams."
...Or they're just casting a wider net.
I've been a KDE user since the 1.1.x days, but even I'm pretty excited about the Gnome 3.18 release. This release is supposed to have very polished Wayland support! If the Wayland support is all it's cracked up to be, Fedora should default to Wayland over X.org with Gnome 3.20. I don't use Fedora either, but if 24 defaults to Wayland, I'll install it to another partition at the very least.
At this point, it's mostly just you. All this work going on vastly simplifies the stack. Wayland compositors are much simpler than the entire X stack (which has to be supported even though much of it isn't used). Unfortunately, X still needs to stay around in some capacity so we can still play our proprietary games ,etc.
Agreed. Wayland development appeared to accelerate after Ubuntu announced Mir. If the only thing that ever happens because of Mir is that it made the rest of the Linux community unite behind Wayland and speed its adoption, that's still a good thing.
From what I've heard about the commit statistics, there was no real change in Wayland development itself. Where we're seeing the acceleration is the desktop environments realizing they really needed to start their porting work. THIS is definitely a good thing.
And Ubuntu started Mir because their engineers seem to believe Mir has fundamental performance advantages over Wayland in resource-constrained environments like phones. It's possible they're completely wrong, but if they're right then we need Mir for Linux on smart phones.
There seems to be this myth that Wayland doesn't work with Android GPU drivers. Mir's support for Android drivers uses libhybris to achieve this, which is atually Wayland library for allowing Wayland to work with Android GPU drivers.
And we're starting to this sort of thing a lot. Mir really just isn't too fundamentally different from Wayland. Typically when Mir support is added to something, they've simply taken the Wayland support and have made a relatively small amount of changes (sdl2, xwayland/xmir, etc). I think in the long run, Canonical will partially throw in the towel and Mir will end up being a Wayland compositor that's also capable of running Mir specific (mobile?) apps.
I don't know that the Mir devs really believed these issues. That's not to say that such claims weren't made (most/all of which were thoroughly debunked the same day they came out), but the real reason for Mir's existence is control for their mobile platform. Wayland is MIT licensed, and Mir is GPLv3 which a CLA. If canonical had been more honest about their reasons for Mir, I think they'd be receiving far less flak for it. No other reason really makes much sense. They're just too similar.
Wikipedia's article about PulseAudio claims that PulseAudio can emulate ESD. Or is this emulation too broken to work with SimCity 3000?
I have no idea... I didn't know about this so I never tried... But thanks for the info, I just may give this a shot!
This quote makes zero sense: "...reliance on Windows and DirectX (and to a lesser extent Mac OS), systems that cannot be relied upon in the long term." Really, because my experience with Linux and backwards / forwards support for both software and hardware has been vastly worse than Windows from XP through 8. Sure before XP, Windows 9x was terrible, but are we really going to keep basing derp derp FUD on a 5 year window of hard lessons from nearly 15 years ago? Can we just fess up and admit that SteamOS is an effort predicated on a personal beef Gabe Newell has with Microsoft and especially the fact that Windows 8 included it's own store and that store was not Steam. The story is well documented and the whole industry is going to blow a lot of money on development just to satisfy one man's ego.
Linux supports older hardware than windows 7 and 8, no question. Regarding the software... You definitely have a point there. Almost. The Linux kernel itself actually has backwards compatibility for userspace software going back quite a bit. It's mostly glibc that breaks this. If it isn't happening already, it will eventually. You'll be downloading games from that simply ship with their own libraries. I believe a lot of Windows software works this way.
You can actually get a lot of old loki games to run in linux by installing older versions of various libraries. Although, you do encounter some issues. For example, Simcity 3000 won't give you sound since it wants to use esd (which hasn't seen use in years), but the game will otherwise run. This takes some work to setup, but if the games on steam do this for you, it's a non-issue.
Not anymore. Asus mentioned they have sold millions of high end/gaming motherboards as gamers no longer buy Dells and replace the GPU like they did in the old days.
You can thank crappy PSU's and proprietary tiny cases for this decline as gamers are the only ones who upgrade besides corporations and they only do so every 10 years now when MS decides it needs more money for another OS upgrade.
I was about to ask you to back up that claim, but a quick google shows what you're saying as true: http://www.maximumpc.com/gigabyte_asus_wrestle_motherboard_shipment_crown2013
The article is a bit dated, but apparently Asus was expecting to ship 22.2 million mid to high end boards in 2013. It's starting to seem custom rigs (particularly for gaming) is hardly a niche. Maybe the market's somewhat smaller than desktop machines, but it's certainly large enough to be considered healthy and is still growing.
I think I may very well put this on to my S4. I got the S4, because nothing else really looked appealing to me, but I'm really not a fan of touchwiz. If this is better than touchwiz (very hard not to be), then I'll give it a shot.
The fact that Sailfish uses Wayland also makes this very interesting to me.
steam works pefect in GNOME shell in archlinux. unity is not a requeriment.
To add to this, I don't think SteamOS will use unity period. I suspect they'll use a custom window manager or perhaps full screen mode for steam os will be the window manager. I personally run steam in KDE without issues.
But kubuntu 13.10 won't be using xmir, that's just vanilla ubuntu (and possibly xubuntu I think).
Running an X desktop on Mir by using the XMir layer just adds another unnecessary layer (that is bound to have bugs), so it's good the Lubuntu and Kubuntu folks are avoiding that. It's a shame KDE5 (which will have Wayland support) is a good ways off.