I'm very surprised someone from AMD would say this, given that they used to produce the AMD29000, which used to be rather popular in some niche areas. This used register windows, with 192 registers in total. Nice chip, back in the day.

The Wikipedia article also says that parts of the 29050 design were used as the basis for the K5 x86-compatible chips.

Really nice comment from Brian May:

"Patrick is irreplaceable. There will never be another Patrick Moore. But we were lucky enough to get one."

"That can still be ambiguous. Sure, after using it for a bit, users would learn by feel which way is the right way. But how do you know which way connector should go into the device without trial and error?"

"There may be an arrow on the device to help you align it, but that's still only part-way there..."

God help you if you ever get the chance to "recharge" a woman...

It depends on whether or not you adjust the actual dollar amount to account for inflation (i.e. measure the debt in dollars for a fixed value of "dollar").

This graph on Wikipedia does.

People can judge for themselves the validity of adjusting for inflation (though I'm sure many here will be eager to tell everyone what they should believe).

Your assertion to the previous poster that "You clearly have NO idea what you're talking about" was unjust.

Surprisingly level-header article, given the source (Phoronix).

I really do hope Wayland sorts out a good scheme for remote access. At the moment it seems to be just ignored.

I wish people who set out to *replace* an existing piece of software would endeavor to replace it in its entirety, not just the subset of features that they happen to be interested in.

Great. Do you know if they've fixed the weather?

And what about the motorway throughput? Is it really a driver problem?

I'd rather Samsung be allowed to sell its products in the US.

No AND.

Very interesting interview with the jury foreman on the BBC.

Especially his statements like:

"The jurors wanted to send a message to the industry at large..."

"And in example after example, when we put it to the test, the older prior art was just that. Not that there's anything [wrong] with older prior art - but the key was that the hardware was different, the software was an entirely different methodology, and the more modern software could not be loaded onto the older example and be run without error."

"And so consequently, when we looked at the source code - I was able to read source code - I showed the jurors that the two methods in software were not the same, nor could they be interchangeable because the hardware that was involved between the old processor and the new processor - you couldn't load the new software methodology in the old system and expect that it was going to work. And the converse of that was true."

I hope Samsung's lawyers are watching.

You don't seem much to like London or Nottingham either.

Where *do* you like?

Indeed. The area around Cambridge has also been known as "Silicon Fen".

Or what about somewhere like Manchester - a big city with an important place in the history of computing, a large, well-regarded university, and a large pool of experienced, well-qualified people?

But no, once again it seems to be London that gets the attention.

"Me, I want more of this. I want plans to 3D print a fully automatic weapon. Just to watch the heads explode at the realization that the genie is out of the bottle and ain't going back."

Yeah, won't it just be fucking fantastic when billions of people around the world can 3D-print gas centrifuges and the equipment necessary to extract uranium from seawater. Won't that be fun to watch.

"A car is always at its safest when stopped".

Dangerous and wrong. A stopped car on a motorway, for example, is very dangerous indeed.

I suspect that the point of the UK threat was: a) to piss off the Ecuadorians enough to make sure that they *did* grant him political asylum; b) to make sure that Assange stays holed up in a small building in London potentially for many years, severely limiting his ability to run Wikileaks for the duration.

Well done on the Ecuadorians for making that threat public.

It's a stupid threat for the UK government to have made, for the reasons so many posters have pointed out, and I'm ashamed of the stance the UK government is taking on this issue.

"An OS upgrade has no business resizing your /var or root partitions. Period. Heck, you have to be pretty ignorant if you presume they're always local."

An OS upgrade could conceivably slightly increase the amount of space used in /usr.

But according to this little gem /usr should now be part of your root partition. Which you will now presumably need to do an online resize of - assuming you actually installed your root partition on LVM, with the appropriate infrastructure needed to support that. Presumably, non-local /usr is no longer supported - similarly with having /usr (which is read-mainly) on a small SSD and the rest of the OS on spinning media.

Fuckup after fuckup after fuckup from Fedora these days. And an arsey attitiude from the likes of Poettering to go with it.

Moving every thing to /usr to make the filesystem more sane.

Meaning that the system no longer supports /usr in a separate filesystem: http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken.

Of course, you can still use /usr in a separate filesystem from / if you boot with an initrd, but you now almost need half an operating system (busybox, rescue shell and utilities, perhaps support for lvm and/or RAID) just to boot your real operating system.

Why would you want /usr on a separate filesytem? Perhaps you want it in LVM, so you can resize it easily if necessary (maybe to make room for installing a new desktop environment, for example), but don't want you root file system in LVM. Perhaps you want to periodically fsck /usr on boot, and fall into single-user mode if it fails. Perhaps you want /usr (which is a read-mainly file system) on a small SSD, and all other file systems (which are written to more frequently) on spinning disk storage. Perhaps you want to mount /usr over NFS. Not that I can still see many people doing this but it seems a pity to prevent something that has worked fine in the past - and in these days of "running applications in the cloud" it seems Linux will no longer run applications in the local network (ie. NFS-mounted /usr).

Seriously, read the level of professionalism and maturity on that page. This is the level or maturity to which Linux slowly seems to be sinking. As a long-time Linux user and supporter I find this deeply disappointing.

And what's the reason for all this? Because the udev developers can't wipe their own a{r|s}es, put their house in order, and properly sort out which files go where (or at least sort out what needs to be done to mount any necessary non-root filesystems, mount them, and then continue with any programs/scripts which use them). Instead, all of that gets pushed out to initrd (ie. oh no it's hard, let's give it to someone else to do). Seriously, they're like a bunch of 8-year-olds bragging to their friends that they won't clean their bedrooms, even when mummy thinks they should.