Forgot your password?
typodupeerror

Comment Re:Two problems (Score 2) 233

Neither Intel nor AMD have a packaging plant for CPUs in the US. Similarly, I don't think there's a packaging plant in the US for discrete semiconductor components like diodes, bipolar transistors and power-mosfets. The parts might be US designed, even diffused in the US, but for being "Made in America" they need to be packaged in the US also.

I think that's a show-stopper for his idea.

Comment Re:cheating your way through college with AI (Score 1) 115

Professors should create high-quality teaching material and teach their students well. I don't care what tools they use. They can copy from textbooks, reuse material from other professors or use a LLM - or even do it all by themselves.

My professor in theoretical physics did his classes by memory - deriving all the math live on chalk-board. Didn't give a single handout ever. Impressive and I learnt a lot that way. My materials science professor used a textbook, talked and explained that book with a few excourses left and right. Great course.

None of those guys was sloppy, though.

Comment Audiobooks are more than plain reading aloud... (Score 2) 14

So instead of paying for a dramatic reading of a book with all the nuances of the narrator's interpretation of the book we will get a monotone unreflected drawl of a reading. This assumes people only pay for audiobooks because they're too lazy to read.

I hope people will return those AI audiobooks. That may be the only way Amazon might learn.

Comment Re:That is called fraud (Score 1) 141

That's correct. But in that case they would have needed to inform all customers at the time the purchase was effective. Instead they decided to continue service and by that demonstrating concludently that they honor the liabilities of the previous owner. You can't dump your own lazyness on your customers.

In my country, chances are pretty solid that any court will agree that you still have a lifetime contract with them. And any competitor can actually sent you binding cease-and-desist letters to stop that uncompetitive procedure.

Comment Not paying attention is easy remote and in-person (Score 1) 160

From FTA:

>In-office requirements will not be left up to managers, Dimon said.
>
>“There is no chance that I will leave it up to managers,” he said. “Zero chance. The abuse that took place is extraordinary.”

Well, from my experience people can drift off in in-person meetings as easily. Especially the "important" people prefer typing and reading on their laptop to listening to the meeting.

He's such a smartass. Makes me wonder how he got there.

Comment Re:They're already unelected internet sheriffs. (Score 2) 11

If you would actually *use* their service you would know that CF does not block much unless you specifically configure them to do so.

That's the beaut of their service, they allow you to control who can visit your domains and who cannot.

They're not without blame, but I would actually consider them to be sensible good guys in this snake pit that we call the web.

Comment Re:Very Skewed (Score 1) 83

I am using Manjaro as my daily driver. It's Arch dialed down to a less bothersome level. It just works. They even made the AUR more easily usable. Props to them for that!

That said, I've realized that I would probably also be happy with plain Debian. Being on the cutting-edge isn't so important for me nowadays.

Comment Re:no, no...that's SOME of it (Score 1) 119

But the real question here is,... is America safer if Russia successfully invades the Ukraine. Or is it safer if Putin gets stuck in this mess and keeps bloodying his nose. If you say yes to the former, then you have all the reason to complain. If you agree with the latter, then it's money well spent.

Comment Sad that magnitude 4.5 is considered "dark" (Score 4, Informative) 54

Magnitude 4.5 is not dark. It should be easily visible from a suburb sky - just don't try to find the comet standing right next to a streetlight.

Light pollution is bad as it is, but at least in my area 80% is darker than 4m5. Now, true 7m skies... that would be a treat, but nobody in central europe is ever going to have that anymore.

Comment Re:easy solution: (Score 2, Informative) 472

The trouble is that in server workloads you generally don't see ONE LARGE I/O operation - lots of small ones instead. There are very very few server workloads that involve transferring >100MB data at a time (even when it comes to DB snapshoting).

There's lots of server workloads that involve large IO requests:

  - backups
  - DB startup/shutdown
  - DB traffic that generates or reads a lot of new data (say report generation)
  - HPC workloads that work with huge data sets
  - animation farms that work with huge images/movies
  - web servers streaming out big files
  - fsck
  - virtual desktop servers where the desktops are virtual instances running on the server. There any IO load within that 'desktop' runs on the server.

etc. As there is a fair number of server workloads that are IO heavy but which use small IO requests.

On the desktop this is common (all your AVI files).

If you have those big files in networked storage or if you are backing them up to some network host then you've already transformed those kinds of IO requests into big IO requests on the server side as well: the big file you read or write on the desktop the network file/backup server will read/write from its own disks, etc.

Really, "interactivity sucks during big IO" kind of bugs can hurt servers just as much as they can hurt desktops. The boundary between desktops and servers is very fluid.

Comment Re:It sucks I agree (Score 4, Interesting) 472

There's also the VM fix from Wu Fengguang, included in v2.6.36, which addresses similar "slowdown while copying large amounts of data" bugs.

There were about a dozen kernel bugs causing similar symptoms, which we fixed over the course of several kernel releases. They were almost evenly spread out between filesystem code, the VM and the IO scheduler. And yes, i agree that it took too long to acknowledge and address them - these problems have been going on for several years. It's a serious kernel development process failure.

If anyone here still experiences bad desktop stalls while handling big files with v2.6.36 too then we'd appreciate a quick bug report sent to linux-kernel@vger.kernel.org.

Thanks,

Ingo

Slashdot Top Deals

"Who cares if it doesn't do anything? It was made with our new Triple-Iso-Bifurcated-Krypton-Gate-MOS process ..."

Working...