Except that Apple is suing Samsung, in Europe, under community design law - not patent law. So your protestations as to the operation of U.S. patent law seem rather irrelevant.
(Besides, isn't 'use it or lose it' a feature of *trademark* law, not patent law?)
"Those two ingredients really give you most of what you need for UIs and groupware/calendaring type software to iron timezone issues out in the background, while still letting everyone who isn't necessarily a jet-lagged globetrotter use a set of local times that roughly correspond to what the sun is doing where they are. Some packages already do support this, to a greater or lesser extent."
To a greater or lesser extent? Every groupware system, cellphone and calendaring protocol I know of does this, because it makes no sense at all to do it any other way. Appointment times are always stored and transmitted in UTC and converted to $CURRENT_DISPLAY_TIMEZONE when shown to you in your calendar.
"Grub (legacy) is no longer supported. Patches are not accepted. Grub2 is also nearing a stable release (14-May-2011 GRUB 1.99) which is something that Grub (legacy) never reached. "
Upstream support, essentially. But yeah, our installer team isn't terribly happy with the design of GRUB 2 either. It's a choice between two evils.
A USB 3.0 drive? Way to test two variables at once, dude.
When you say "It sees the spindle, and it sees the huge NTFS partition the vendor sprayed on it, but offered no clue - i.e., didn't propose a suitable partition scheme that might be appropriate", what point of the installation are you talking about? Because the point at which it _discovers_ drives and the point at which you choose a partition scheme are different. Also, if you select any of the pre-set partitioning options - 'Use free space', 'Use entire disk', 'Replace existing Linux partitions' - Fedora will come up with a partition scheme for you. If you choose 'custom partitioning', it won't, because hey, _you chose custom partitioning_, which means you want to do it yourself. If the disk is entirely consumed by an NTFS partition you'll need to pick 'Use entire disk', because there's no 'free space' or 'existing Linux partitions', so if you try either of those methods, anaconda won't have any space to put Linux partitions into.
"I decided at that point that it was just as futile under F16 as it was under F15, F14, F13,..."
Might I suggest the shocking, nay, _radical_ thought that a more complete test might be TO FINISH OFF THE FRACKING INSTALLATION BEFORE YOU SPRAY VITRIOL ALL OVER SLASHDOT?
Whew. Sorry. I feel better now. But, I mean, come on.
F16 uses gpt disk labels by default, for all disks. There's no reason it shouldn't work on your disk, if you pick an appropriate partitioning method.
If by 'it' you mean 'GNOME 3', and we ignore the inaccuracies in your rant for the sake of concision, then yes, yes 'it' does. But Fedora is not GNOME 3, so why are you posting about this here? Fedora features at least eight desktops, two of which are equally supported as 'premier' environments - GNOME 3 and KDE - and two of which are fairly actively supported and tested - Xfce and LXDE.
We don't support VirtualBox. Mainly because the Fedora kernel developers consider it a pile of...well...something awfully rude. If an issue with VirtualBox is isolated and traced back to something being wrong in Fedora, sure, it'll likely get fixed, but VBox is not something Fedora actively tracks and tests for.
Fedora supports the qemu/kvm/libvirt/virt-manager virtualization stack, and we do test that quite extensively. But running as a virt client is required functionality for Beta, not Alpha.
(FWIW, though, recent VBox releases _do_ have 3D passthrough, and I've seen reports of people getting it working with F15. So it sounds like you maybe have an old VBox?)
Patents don't work how you think. _Every_ claim in the patent counts: you don't have to infringe all of them together to be infringing the patent. I haven't looked at this one, but just because claim 16 is a rather interesting refinement of the system, doesn't mean you have to be doing what claim 16 claims to be in violation of the patent. If you violate claim 1, you're in violation of the patent.
Of course, you could argue for a re-examination of the patent that strikes every claim _but_ claim 16, but until that happens, all the other claims have force.
Going way back, Wolfenstein 3-D - Doom's predecessor - had reasonably accurate damage; you could only take a few pops from any enemy gun, even the weakest brownshirts' pistols. You were still one guy taking down an entire enemy army, so, y'know, not TERRIBLY realistic, but the damage model was a lot closer to reality than Doom's. The gameplay tended to rely on getting in situations where you had the drop on enemies, and the fact that they were mostly terrible, terrible shots (I'd cite the TV Trope for that, only I don't want to lose another fifteen hours of my day to that damn site...). Except those fuckers in white from Spear of Destiny. Those guys were evil.
It's mentioned in TFA. Really. Go read it. If you're so lazy you can't be bothered, here's a summary: the author reckons FPGAArcade is great, but accessible to relatively few people.
RTFA. You're working on entirely different levels. The amount of 'thinking' involved in emulating a 20 year old video game console is, obviously, below trivial for a modern PC (or graphing calculator, frankly). If we're going to continue with the metaphor, accurately emulating a NES is more a problem of emulating the precise eccentric way in which it thinks. Anyway, there's a perfectly good technical explanation of why it's a problem right behind the link in the summary. It's written by a guy who's been doing this for years. Just go read it.
if it had hardware that was way more powerful than necessary it wouldn't be a homebrew snes, would it? it'd be a somewhat similar arrangement of hardware that you hoped would run the software more or less okay. thus kinda defeating the point.
except that this actually isn't security theater. It's the useful kind of security procedure that actually prevents bad stuff happening. Screening of cargo and investigation of suspicious looking bits of cargo is how they stopped the printer-cartridge-bomb plot, for instance.
It's all very well to knee-jerk off about how the TSA is full of idiots and they're trampling over your inalienable rights and freedoms and blah fucking blah, but at least spend a few minutes thinking about the context. This science project was a fairly simple, hand-built electronic device with improvised casing whose purpose isn't immediately determinable. The TSA says, and I'm happy to defer to their superior experience on this specific point, that bomb detonators they catch often look like - in fact, are - fairly simple, hand-built electronic devices with hand-built cases whose purpose isn't immediately discernible. Are you seriously suggesting it's 'security theater' to screen airplane cargo and take a closer look at improvised electronic devices? Really? If so, I'm damn well not flying on _your_ airline.
It's not like they arrested the kid and hauled him off to Guantanamo Bay or something. They found a suspicious device and performed an exhaustive investigation to figure out what it was. Which came to the right conclusion. I don't really see that anything happened wrong here.
Yes. And this is what happens all the time in F/OSS license violation cases. No-one pays out zillions of dollars: they fix the infringement. Happens to hardware vendors who haven't got a clue, malicious software vendors who got caught, well-intentioned ones who made a mistake...happens all the time. I dunno why this is suddenly news.
(For example, I suspect it's somewhat unlikely that any Linux distribution's 'F/OSS only' repositories are actually F/OSS only. The distros which take license compliance most seriously - Debian and Fedora/Red Hat - actively search out licensing issues, find them all the time, and get them resolved. This is a deeply un-sexy ongoing background process which most people are shielded from by the power of not giving a crap. But yeah, since we've been finding licensing issues that affect all distros that haven't been caught in years _all the time_, it seems unreasonable to assume that the last big one we found was the last one and everything's fine now.)
Let's see - sneakers, flip-flops, black formal, dark brown formal, light brown formal, tennis, golf, badminton, slip-ons. I'm at 9 and I don't even have a white pair!
Slashdot Mirror
"The difference in labor and other overhead between the US and China is considerable"
ooh! nice subtle handwave there. You hid a lot of stuff in that 'other overhead', didn't you?
"'Some of [the U.S.'s] best engineers are not doing engineering, and some of its best potential engineers are not even studying engineering"
That sure sounds like an 'engineer shortage' to me.
I don't see anyone cheering on Samsung, exactly. I see people laughing at Apple's blatant hypocrisy. There's a difference.
Except that Apple is suing Samsung, in Europe, under community design law - not patent law. So your protestations as to the operation of U.S. patent law seem rather irrelevant.
(Besides, isn't 'use it or lose it' a feature of *trademark* law, not patent law?)
"indefinite amounts of Jaegermeister"
Isn't Jaeger one of those drinks whose quantity is indefinite more or less by definition? Like absinthe. Or Special Brew...
There aren't many floodlit public tennis courts.
"Those two ingredients really give you most of what you need for UIs and groupware/calendaring type software to iron timezone issues out in the background, while still letting everyone who isn't necessarily a jet-lagged globetrotter use a set of local times that roughly correspond to what the sun is doing where they are. Some packages already do support this, to a greater or lesser extent."
To a greater or lesser extent? Every groupware system, cellphone and calendaring protocol I know of does this, because it makes no sense at all to do it any other way. Appointment times are always stored and transmitted in UTC and converted to $CURRENT_DISPLAY_TIMEZONE when shown to you in your calendar.
Rick me!
"Grub (legacy) is no longer supported. Patches are not accepted. Grub2 is also nearing a stable release (14-May-2011 GRUB 1.99) which is something that Grub (legacy) never reached. "
Upstream support, essentially. But yeah, our installer team isn't terribly happy with the design of GRUB 2 either. It's a choice between two evils.
A USB 3.0 drive? Way to test two variables at once, dude.
When you say "It sees the spindle, and it sees the huge NTFS partition the vendor sprayed on it, but offered no clue - i.e., didn't propose a suitable partition scheme that might be appropriate", what point of the installation are you talking about? Because the point at which it _discovers_ drives and the point at which you choose a partition scheme are different. Also, if you select any of the pre-set partitioning options - 'Use free space', 'Use entire disk', 'Replace existing Linux partitions' - Fedora will come up with a partition scheme for you. If you choose 'custom partitioning', it won't, because hey, _you chose custom partitioning_, which means you want to do it yourself. If the disk is entirely consumed by an NTFS partition you'll need to pick 'Use entire disk', because there's no 'free space' or 'existing Linux partitions', so if you try either of those methods, anaconda won't have any space to put Linux partitions into.
"I decided at that point that it was just as futile under F16 as it was under F15, F14, F13, ..."
Might I suggest the shocking, nay, _radical_ thought that a more complete test might be TO FINISH OFF THE FRACKING INSTALLATION BEFORE YOU SPRAY VITRIOL ALL OVER SLASHDOT?
Whew. Sorry. I feel better now. But, I mean, come on.
F16 uses gpt disk labels by default, for all disks. There's no reason it shouldn't work on your disk, if you pick an appropriate partitioning method.
"Hey, Fedora devs! How 'bout helping out us folks who run older hardware? The kind of hardware that F15 seems to have left behind."
We've thought about it, and, no. Here's a nickel, kid.
(Fedora isn't the distro you're looking for. There are many that are.)
Yeah, that's an icky upstream glibc bug, there's a patch submitted upstream: http://sourceware.org/bugzilla/show_bug.cgi?id=13013
If by 'it' you mean 'GNOME 3', and we ignore the inaccuracies in your rant for the sake of concision, then yes, yes 'it' does. But Fedora is not GNOME 3, so why are you posting about this here? Fedora features at least eight desktops, two of which are equally supported as 'premier' environments - GNOME 3 and KDE - and two of which are fairly actively supported and tested - Xfce and LXDE.
Then...that's probably not something Fedora can do a lot about.
We don't support VirtualBox. Mainly because the Fedora kernel developers consider it a pile of...well...something awfully rude. If an issue with VirtualBox is isolated and traced back to something being wrong in Fedora, sure, it'll likely get fixed, but VBox is not something Fedora actively tracks and tests for.
Fedora supports the qemu/kvm/libvirt/virt-manager virtualization stack, and we do test that quite extensively. But running as a virt client is required functionality for Beta, not Alpha.
(FWIW, though, recent VBox releases _do_ have 3D passthrough, and I've seen reports of people getting it working with F15. So it sounds like you maybe have an old VBox?)
they went on sale Friday afternoon in Canada and were sold out everywhere about half an hour later...
Patents don't work how you think. _Every_ claim in the patent counts: you don't have to infringe all of them together to be infringing the patent. I haven't looked at this one, but just because claim 16 is a rather interesting refinement of the system, doesn't mean you have to be doing what claim 16 claims to be in violation of the patent. If you violate claim 1, you're in violation of the patent.
Of course, you could argue for a re-examination of the patent that strikes every claim _but_ claim 16, but until that happens, all the other claims have force.
Going way back, Wolfenstein 3-D - Doom's predecessor - had reasonably accurate damage; you could only take a few pops from any enemy gun, even the weakest brownshirts' pistols. You were still one guy taking down an entire enemy army, so, y'know, not TERRIBLY realistic, but the damage model was a lot closer to reality than Doom's. The gameplay tended to rely on getting in situations where you had the drop on enemies, and the fact that they were mostly terrible, terrible shots (I'd cite the TV Trope for that, only I don't want to lose another fifteen hours of my day to that damn site...). Except those fuckers in white from Spear of Destiny. Those guys were evil.
It's mentioned in TFA. Really. Go read it. If you're so lazy you can't be bothered, here's a summary: the author reckons FPGAArcade is great, but accessible to relatively few people.
RTFA. You're working on entirely different levels. The amount of 'thinking' involved in emulating a 20 year old video game console is, obviously, below trivial for a modern PC (or graphing calculator, frankly). If we're going to continue with the metaphor, accurately emulating a NES is more a problem of emulating the precise eccentric way in which it thinks. Anyway, there's a perfectly good technical explanation of why it's a problem right behind the link in the summary. It's written by a guy who's been doing this for years. Just go read it.
if it had hardware that was way more powerful than necessary it wouldn't be a homebrew snes, would it? it'd be a somewhat similar arrangement of hardware that you hoped would run the software more or less okay. thus kinda defeating the point.
except that this actually isn't security theater. It's the useful kind of security procedure that actually prevents bad stuff happening. Screening of cargo and investigation of suspicious looking bits of cargo is how they stopped the printer-cartridge-bomb plot, for instance.
It's all very well to knee-jerk off about how the TSA is full of idiots and they're trampling over your inalienable rights and freedoms and blah fucking blah, but at least spend a few minutes thinking about the context. This science project was a fairly simple, hand-built electronic device with improvised casing whose purpose isn't immediately determinable. The TSA says, and I'm happy to defer to their superior experience on this specific point, that bomb detonators they catch often look like - in fact, are - fairly simple, hand-built electronic devices with hand-built cases whose purpose isn't immediately discernible. Are you seriously suggesting it's 'security theater' to screen airplane cargo and take a closer look at improvised electronic devices? Really? If so, I'm damn well not flying on _your_ airline.
It's not like they arrested the kid and hauled him off to Guantanamo Bay or something. They found a suspicious device and performed an exhaustive investigation to figure out what it was. Which came to the right conclusion. I don't really see that anything happened wrong here.
Yes. And this is what happens all the time in F/OSS license violation cases. No-one pays out zillions of dollars: they fix the infringement. Happens to hardware vendors who haven't got a clue, malicious software vendors who got caught, well-intentioned ones who made a mistake...happens all the time. I dunno why this is suddenly news.
(For example, I suspect it's somewhat unlikely that any Linux distribution's 'F/OSS only' repositories are actually F/OSS only. The distros which take license compliance most seriously - Debian and Fedora/Red Hat - actively search out licensing issues, find them all the time, and get them resolved. This is a deeply un-sexy ongoing background process which most people are shielded from by the power of not giving a crap. But yeah, since we've been finding licensing issues that affect all distros that haven't been caught in years _all the time_, it seems unreasonable to assume that the last big one we found was the last one and everything's fine now.)
tl;dr summary: licensing is hard, mmkay?
"I'm certainly more impressed by Google's willingness to let me export their data"
Once you give it to Google, it ain't yours any more.
Let's see - sneakers, flip-flops, black formal, dark brown formal, light brown formal, tennis, golf, badminton, slip-ons. I'm at 9 and I don't even have a white pair!