Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Comment Re:The OEM UEFI locked with M$ keys issue. (Score 1) 208 208

I suspect the big change we'll see trusted computing. Features like Samsung Knox but for PC. Microsoft was too chicken to go all the way and take all the heat when they were leading the effort along with Intel. This way Intel and Microsoft have just enabled it, there will need to be other 3rd party software but it will be the hardware OEMs that actually deploy it. Lots of pieces and no one but the security vendors doing more than enabling.

As far as the general fear of blocking other OSes, I doubt it. Microsoft has been generous, supportive and and cooperative with Linux vendors in terms of getting keys to work. Those vendors have been supportive with more open players.

Comment Re:who cares? the market has made them irrelevant (Score 1) 208 208

How much does it rein supreme? The market has been falling in size in terms of units now for 6 years. At the same time another wave of APU falling is starting up. The upper end is firmly in the hands of Apple whose reach is expanding. The bottom end is being eaten by $75-150 Android tablets and by iPads. Mobile is decreasing usage as well. Losing ground rapidly above and below with the middle softening doesn't sound like reining supreme. That sounds like being rapidly displaced.

Comment Re:Windows 10 Sucks (Score 1) 208 208

Your point is spot on. Apple wouldn't have cared and Linux would have done it both ways until people got used to the change. Microsoft's Windows 8 was supposed to be a transitional operating system with touch becoming an important and key part. All applications needed to have a reasonable touch mode. They ultimately have pulled back from touch which means they pulled back from ubiquitous computing ( https://www.youtube.com/watch?... ) Windows 8 was there last chance to prevent themselves from being a niche: the standard enterprise desktop product. Now that's still a huge niche but moving from the default everything to just one particular submarket is a big loss.

Comment Re:Whats left unsaid... (Score 1) 118 118

Remember this thread started with a conversation about the cost of going to 1gbs. Customers that are having to move from say 30-200mbs to 1gbs+ are going to want more than 1-2mbs dedicated. They are going to want much more than 300gb / month total. Your numbers are way too low for connections that fast. For example residential traffic in the USA is becoming much more steady because of things like Netflix. Netflix needs about 7mbs and that's not including other traffic in the household. And that's all running comfortably on today's 50mbs type connections not for near future when Netflix is using 8x as much and people are pulling down multiple streams.

We know that home providers right now are underprovisioned. 7pm to 11pm they are only able to deliver 4mbs per home on average, while at times like 4:00 am they can do 18mbs / household and customers express satisfaction. And again that's with many customers buying as little as 10mbs. We know that 2mbs dedicated is less than 1/2 what customers are getting now in the worst markets.

My .2 multiplier I think is fair for good quality peak usage (what the original poster wants). But even if I am to high it is nothing like a .001-.002 as a multiplier. 1000x to one overprovision you just aren't delivering anything like 1gbs of bandwidth.

As for my house. I have about 8 copper lines running to my house. I have a switch box which connect the outlets to up to 3 of those incoming lines. I also have an older system using lead wires inside glass. 2 of those lines were setup for DSL. 0 of them are supported by the phone company today. All of that is abandoned infrastructure.

As for ROI... Remember where I started. 5 years to pay off the original investment (no profit) then Y years of profit. The goal of infrastructure is not to break even,. not to have an ROI of 0. Your $120 box is a perfect example. You are renting it at $5/mo which means a 24 mo breakeven point not 25 years. A 25 year payoff would be you renting the box for $.40 / mo, a 50 year payoff $.20/mo.

Comment Re:If there was a criteria for safe unlocking (Score 1) 68 68

this sandwich very likely isn't as expensive as you think

Only because, like most armchair engineers, you've breezily handwaved away issues you have quite cleary no clue about.

Yet, for being the least reliable, it's a method that works very well - presuming the operator is properly trained.

No it doesn't. Not even in the slightest.

Millions (billions?) of man hours of operation of aircraft, spacecraft, submarines, etc... etc.. says just the opposite. Again, you have no fucking clue what you're talking about.

Comment Re:No kidding. (Score 1) 250 250

How many popular web apps can you name that completely separate the back end and the front end and provide documentation for users to talk directly to the back end and substitute their own UI or amalgamate the data with that from other services?

I can't count every web site that has an API, but examples include Amazon, eBay, and Twitter.

Comment Left behind. (Score 1) 524 524

Business as usual until we find a buyer (and hopefully after).

Slashdot opened for business in 1997 --- and it remains, despite cosmetic changes good and bad, very much a reflection of the us vs them geek mind-set of the nineties.

It's been awhile since a new idea has made it past the gates.

Compared to the Internet population as a whole, far, far, more people who stop by here are still in school --- and they aren't hanging around as long as they used to.

"The cow goes moo."

The Slashdot gender gap is real, though much narrower than the Great Divide you see at Ars Technica. "Who visits Slashdot?", "Who Visits Ars Technica?"

You can't hope to talk sensibly about tech unless you can place it in a larger social context --- and if at least 40% of your audience is female, you can't put gender issues in tech on the back burner and expect to survive.

Comment Re:A "safety feature" (Score 1) 68 68

It's interesting as the unique tail section was actually touted as a "safety feature" by the company. I'm not necessarily saying it can't be the case, but like any feature, even a safety feature (see: exploding airbags), defects or improper use can cause more harm than in it's absence.

An improperly implemented safety feature (emergency ballast blow system) contributed to the loss of USS Thresher... In the same way, the Apollo 1 crew died (in part) because of a system (a well locked down hatch) that had been installed to prevent a repeat of an earlier accident. (Which, by morbid coincidence, one of the crew had been involved in.)

It's a bit strange, as it seems like such a fundamental error - not some obscure feature that could be overlooked. What pilot would say to himself "Hey, I know I'm supposed to unlock the tail at time X, but what the hell, why not just do it now?" It seems really strange that they wouldn't have precise procedures for this, since it's such a critical part of the entire design.

It's not so much that, as the pilot appears to have become confused due to a) the simulator not properly conditioning them, b) lack of recent and overall experience with the vehicle, and c) high cockpit workload at that point in the flight compounding a) and b). At least that's how I read the report. (The abstract and summary of which is not clearly linked of the summary or TFA but which can be found here.)

From my experience in the Navy, I can say that obtaining those reflexes isn't easy, and neither is maintaining them (regardless of experience).

Comment Re:What's the point? (Score 1) 214 214

Ah.. but I thought remote access was a niche application, no longer relevant enough for developers to care about?

That's a bit much. I suspect what you are hearing is that Network Transparency is a niche application.... Remote access while vastly less important than it was 20 years ago is still used. Which is why Wayland supports it and supports it better than X11. This is what I keep saying you cannot confuse remote access which is far better with Wayland and X11's specific methods of remote access. BTW we know KDE and Gnome are going to support remote because they have been working with Wayland already.

I use Stumpwm along with the pager from Lxde.

LXDE is in the process of becoming LXQt. It fully intends to support remote using Qt's system. As per the June 2013 announcement Hong Jen Yee (PCMAn) is waiting on the freedesktop guys to tell him the messy details are worked out, right now they've told him what not to use in Qt 5 if he wants to easily be on Wayland and along with Razor they are making sure that LXQt doesn't use that stuff some of which is being backported to LXDE. I suspect that LXDE will never be native Wayland. I do know they are ripping out X11 dependencies from the LXDE codebase to make such a port easier if they choose to go all the way but they don't intend to.

However getting to your use case: LXDE right now works beautifully with SOC configurations. That's why it is exist. So the kind of lighweight dumb system you are asking for now that you want it for LXDE become much easier. These are sold all over Asia using LXDE based distributions and they are cheap (generally under $200, often like $125). I'm not sure if they include additional languages or even test against English but even if this is not a "just go out and buy this" it certainly is a proof of concept. So there you go: If you want to use LXDE you will have terrific support and get an upgrade.

As far as Stumpwm none of the X11 windows managers will work with Wayland. Window management for most is a rewrite from scratch. You can use Stumpwm for X11 on Wayland of course. However Stump isn't really a window manager as much as a programming exercise demonstrating how to do windows management in LISP. So in theory you got lucky while someone is going to have to port it to Wayland, it very well might be pretty easy. However to complicate this under Wayland the display server, window manager and compositor are complied into one process there is no abstraction like there is in X11. So Stumpwm while getting to run native on Wayland is easy to do anything useful with it it is going to need to be hard paired with a display server and compositor. I don't see any evidence that Stump will go there. So let's assume Stumpwm as an end user product is gone even if it still exists as a teaching tool.

Moreover I'm not sure the culture is going to allow you to be able to just casually change window managers under Wayland. For example LXQt will only be tested against its own compositor which will be tuned to LXQt. You can run other applications but when you run LXQt (again the version of LXDE that will exist on Wayland) you have picked your GUI.

This BTW is where you get huge advantages. You LXDE top to bottom can be compiled for the SOC hardware (the way Android works today) so you will see huge increases in battery life and much better performance.

By texting I mean SMS. You have something that lets you do that from your computer?

Yes. There are many solutions. Apple's built in Messages application does this. http://mightytext.net/ works for Android.

Why keep upping the hardware requirements when we have a working solution already? Aren't the landfills full enough?

We don't have a working solution already. X11 doesn't work. New OSes / features up hardware requirements. That's the norm.

But i'm not even sure you are being environmentally sound. Even on the kind of crappy hardware you are probably burning about 3GB / hr of network for remote X usage assuming this is all wired (wireless is more) or about $.03/hr in electricity over a WAN (wired LAN is close to 0). Or about $.25 / day ~ $50 / yr. The landfill is less environmentally destructive than all the electricity you are using by consuming all that extra bandwidth to have everything sent to you post processed instead of storing the bulk locally and just getting instructions.

Comment Re:If there was a criteria for safe unlocking (Score 2) 68 68

If there was a criteria for safe unlocking of the hinged tail section then why wasn't it interlocked until the criteria was satisfied?

There are problems with interlocks that aren't often appreciated by the armchair engineer. They add weight and complexity to a system. They themselves can fail. They add to the maintenance burden. They add to training, Etc... etc... TANSTAAFL.

A bigger error here is reliance on operator training. It's the least reliable form of ensuring a certain outcome.

Yet, for being the least reliable, it's a method that works very well - presuming the operator is properly trained.

Comment Re:What's the point? (Score 1) 214 214

OK... it certainly is the case that Wayland remote will work worse with dumb terminal type setups. Wayland is assuming the the box remoting into is smart. A phone is plenty smart to run Wayland, and if you kept your applications light (i.e. about 10 years old) would be able handle the toolkits. So for your lapdock type setup you could actually run your desktop applications in a way that is comfortable over mobile data and not chew up insane amounts of data. Again as is usual for the actual use case you are describing Wayland is likely far better than X11. Not far better at doing things the X way but far better at doing the same function as long as you are willing to not cut against the grain.

As far as security goes the receiving machine can have an unwritable filesystem (or unwritable from the OS running Wayland) or be virtualized and just blow away and restore the image after use.... You can achieve the same security with smart as you do with dumb.

But if you want actually dumb, then you need to virtualize your screen. Then you talking something like VNC. Wayland makes use of smart so doesn't support dumb as well. Smart is the more common situation today....

Availability of choice is something that has made Linux great for a very long time. Will there be no future development in this area? Is it going to be QT/GTK forever?

Any toolkit can have Wayland remoting. That's going to be a standard part of writing new toolkits in say 10 years.

Providing network support at a layer between the toolkits and what Wayland provides would be fine by me so long as it meant that this layer was what the toolkits or applications are coded to talk to, not Wayland directly.

In theory Wayland supports that. In practice it isn't going to be what's going to happen so I don't consider it particularly relevant. In practice it happens at the toolkit level and applications pick up their remoting from their toolkit unless they want something more complex.

But... if I don't have my lapdock on me remoting the phone to a computer would be a handy way to handle long-winded text conversations.

That's session sharing. What's better is not remoting the conversation to the computer but that the computer syncs with the phone and has a copy of the conversations at all times. Many messaging systems already provide that. I do that today. No reason to remote just push the data.

I see something like moving the remote support out to the toolkits as making this dream far less likely.

I disagree it makes the dream far more likely. To actually be remote you need good WAN behavior on high latency connections, like a cell phone. That's unfixable not available with X11. Everything else is just using a secure potentially unwritable image for remote machines (VM...) and enjoy. Yes when your main OS changes toolkits (something like KDE 5 to 6) you will need to update your dumb images to match but that's not hard in your scenario.


Scientists Identify Possible New Substance With Highest Melting Point 82 82

JoshuaZ writes: Researchers from Brown University have tentatively identified an alloy of hafnium, nitrogen and carbon as having an expected melting point of about 7,460 degrees Fahrenheit (4120 Celsius). This exceeds that of the previous record-breaker, tantalum hafnium carbide, which melts at 7,128 F (3942 C). Its record stood for almost a century. At this point, the new alloy is still hypothetical, based on simulations, so the new record has not yet been confirmed by experiment. The study was published in Physical Review B (abstract), and a lay-summary is available at the Washington Post. If the simulations turn out to be correct, the new alloy may be useful in parts like jet engines, and the door will be opened to using similar simulations to search for substances with even higher melting points or with other exotic properties.

Brain damage is all in your head. -- Karl Lehenbauer