The problem is the improper and non-specific unit usage. There are very few places that properly make a distinction between "MiB" and "MB". During the early part of the issue with OSX swapping to using base-10 for disk space, I submitted a bug report to Apple -- noting that the system information dialogue was displaying the wrong units for RAM, as it was saying "GB" for base-2 RAM just the same as disk space's base-10 "GB". While you can forgive incorrect, consistent usage of GB (such as when the entire OS uses it to mean base-2 units), making a fairly significant deal of switching the use for storage space, but then not actually fixing the unit usage elsewhere is intensely frustrating.
Of course, to my knowledge, the system information dialogue was never changed, and still happily reports your disk space in base-10 GB and your RAM in base-2 GB.
The most recent version of glibc supports kernels up to seven years old. The most recent kernel should be able to run any statically-linked ELF binary (and can, if configured for it, still run 32-bit a.out binaries).
So it's really a non-issue for anything that's being actively maintained, as long as they're willing to include a full copy of the libraries they use (and anything those libraries link to), or just statically link the entire thing. It's a bit of extra overhead, but considering just how many resources a modern game needs to load and use beyond the basic system libraries, it should be pretty much unnoticeable.
For something that isn't actively maintained, you might run into odd compatibility problems, but if it's 100% statically-linked (or includes the entire dependency tree for every library it links to), it should generally still be able to run fine unless something fundamentally changes about the system (i.e., X11 -> Weyland could cause issues).
Lastly, a question: did you vote for Obama? Remember, it's his minions who are spying on you.
The bureaucracy, which the FBI, DHS, etc. are a part of, is essentially unchanged for many, many years. Individuals come and go, but a change in the executive branch does not replace the entirety of the government structure, not by a long shot.
Furthermore, Obama actually doesn't have anywhere near as much power domestically as you give him credit for. His domestic power is essentially limited to what his charisma can do, not his actual legal powers -- so you can blame him for international incidents and issues, but it's very difficult to legitimately blame him, especially by placing the entirety of the blame on his shoulders, for domestic problems.
Best guess I have is that they removed their implementations of the *at syscalls added in 2.6.16 (since almost no one is using that old a kernel anyway and presumably it made the maintenance easier), and will always directly make use of the kernel versions of those. There were a few other syscalls added in 2.6.16, so it might be related to one of those instead (but the *at ones look most likely to me).
aparantly someone had earlier hacked the WBC, claiming to be anonymous, but it really wasn't.
Anonymous refuted, and even apologized, and tried to explain this to WBC. WBC, didn't want to back down, and kept talking smack to anonymous, and kept provoking anonymous.
The summary was pretty terribly worded -- it didn't get across the fact that, essentially, this is stuff you're horridly unlikely to be using. The actual article was much clearer and more matter-of-fact about it.
First, kmscon has only one dependency - libudev. It can be compiled to use Pango for font rendering, or EGL for hardware-accelerated rendering, but those are optional. X11 is never used.
Looking into the source briefly suggests it actually doesn't have a hard dependency on udev, but has optional dependencies on: systemd, udev, dbus, libdrm, gbm, egl (mesa), glesv2 (mesa), xkbcommon (a part of X11), freetype2, and pango. This means if you don't intentionally build it with the minimal of requirements (presumably making it no richer in features than the default VT system), it would be linked against all those and break if any of them broke during an upgrade or for any other reason.
This is aimed at people who don't need (or at least, don't want) X, but still want to use all the features of modern hardware.
This seems like a niche-of-a-niche market, so to speak. I greatly prefer terminal applications, but I always run them under X (using a minimal window manager, etc.) so that I have access to more complex things like PDF viewing or web browsing (beyond links) when needed.
It also claims to interact well with both the kernel VT system, and with X - you can keep an X session on one virtual screen, keep the kernel terminal on another (for those few cases where it is needed, like kernel error messages), and put kmscon on the rest.
Ah, I guess the Slashdot, Phoronix, and author's blog posts are a bit sensationalist, then -- all three of them make repeated references to completely replacing the standard kernel VT system, including the author recommending disabling CONFIG_VT entirely.
Framebuffer consoles are (or were), in some cases, surprisingly slow. Huge amounts of output at least used to overwhelm them, only catching up if you swapped back and forth between VTs -- this didn't happen in non-framebuffer consoles or in terminal emulators in X.
I think it has improved significantly over the past few years, but that's probably partly from already working some hardware-accelerated rendering into some of the framebuffer console drivers. Though I'm not sure why they're not just working on improving the framebuffer drivers further -- the project seems to aim to put every damn piece into userspace, which seems like a terrible idea for something so essential as the basic console. If you break one of the things it depends on (such as xkb -- yes, really, a piece of X11 for a console system), then you lose any ability to interact with your system, or even view the boot output.
I'm really not sure who it's aimed at. If you break your install and you don't have an old kernel-based VT fallback, you're screwed. If you don't break it and it works fine, what benefit is it? You'll more than likely just be starting up X11 momentarily anyway.
It's not in the best interests of society and societal stability (the general welfare) to have a growing underclass of people who are so poorly thought of and so poor that they would desire to tear the society down. Individual welfare benefits far, far beyond just the individual -- it benefits everyone in keeping society stable and prosperous, even for hard-line capitalists. After all, how can you be a capitalist if someone else is so unhappy with the society that's been created that they wish to murder you and steal your property?
Now I'm just imagining the day the poor schmuck who's Steam Tunnel Operations' webmaster is going to have tomorrow, starting with that e-mail, a few followups from other Slashdotters, and topped off by a heaping helping of spam.
That would be great, ideally (aside from maybe problems with it being absurdly over-engineered).
But it would be really hard to make it catch on. You'd need to manage support for 'traditional' HTTP and the new protocol in all clients, servers, *and* web applications. Because do you really think Microsoft would backport support into old versions of Internet Explorer that people are still using for some god-unknown reason?
I've actually been using extlinux (the ext2/3/4/btrfs version of syslinux) lately, and find it to be amazing. No issues with running it on a 64-bit native system without IA-32 emulation, which was a stumbling block for getting either grub or lilo working on a system that doesn't need 32-bit at all. Maybe grub2's better about that, but I've not tried it -- I've heard horror stories about grub2's configuration mess.
I think it means it would be contrary to the interests of consumers. Less choice, less competition -- while you can argue the merits of these, they are what the free market economy is, in theory, based on. Calling it 'public interest' to uphold that isn't really much of a stretch.
In much political theory since the, oh, seventeenth or eighteenth century (when democracy started becoming a thing), voting is considered a consent to the system in full, not just consent if whomever you want to win wins. In essence, once you've consented to the system you're consenting to be ruled by the will of the majority, determined however the system determines that will (which in some cases, such as first past the post systems, doesn't even mean an actual majority of the population).
Now, you can of course break that contract and attempt to change the system by revolution, or attempt to change the system from within the rules of that system -- but don't say you never consented and therefore shouldn't have to pay taxes but can reap the benefits of others' taxes.
The problem is getting all that information in one place, not really the basics of sorting out interactions. It'd need to be a large, centralized database (at least covering the entire country) and would need to, if this sort of change happened, also track a decent chunk of non-prescription medication somehow.
I remember reading some things back when Diaspora first showed up that suggested this is exactly the case, with both beginner mistakes in security and even the choice of Ruby on Rails for something intended to be run by 'normal users' (which, I've never used Ruby on Rails, but apparently has a habit of breaking applications with every upgrade).
The summary is confusing and inaccurate. The patent was filed in 2008 (not 2009), and the reference to MacOS 9 was referring to a piece in a book ("Insanely Simple: The Obsession That Drives Apple's Success" by Ken Segall, according to the linked article) that suggests that the idea for the patent originated in 1999 (not 2008 or 2009) with Steve Jobs -- back when OS9 was heading towards release, making the reference to OS9 actually make sense.
All this gleamed from clicking the sole link in the/. post, spending 15 seconds skimming it, and having a very basic knowledge of recent OS history. Proofreading, please?
Slashdot Mirror
My head hurts. You just advocated a race-to-the-bottom as being good for everyone...
The problem is the improper and non-specific unit usage. There are very few places that properly make a distinction between "MiB" and "MB". During the early part of the issue with OSX swapping to using base-10 for disk space, I submitted a bug report to Apple -- noting that the system information dialogue was displaying the wrong units for RAM, as it was saying "GB" for base-2 RAM just the same as disk space's base-10 "GB". While you can forgive incorrect, consistent usage of GB (such as when the entire OS uses it to mean base-2 units), making a fairly significant deal of switching the use for storage space, but then not actually fixing the unit usage elsewhere is intensely frustrating.
Of course, to my knowledge, the system information dialogue was never changed, and still happily reports your disk space in base-10 GB and your RAM in base-2 GB.
The most recent version of glibc supports kernels up to seven years old. The most recent kernel should be able to run any statically-linked ELF binary (and can, if configured for it, still run 32-bit a.out binaries).
So it's really a non-issue for anything that's being actively maintained, as long as they're willing to include a full copy of the libraries they use (and anything those libraries link to), or just statically link the entire thing. It's a bit of extra overhead, but considering just how many resources a modern game needs to load and use beyond the basic system libraries, it should be pretty much unnoticeable.
For something that isn't actively maintained, you might run into odd compatibility problems, but if it's 100% statically-linked (or includes the entire dependency tree for every library it links to), it should generally still be able to run fine unless something fundamentally changes about the system (i.e., X11 -> Weyland could cause issues).
The bureaucracy, which the FBI, DHS, etc. are a part of, is essentially unchanged for many, many years. Individuals come and go, but a change in the executive branch does not replace the entirety of the government structure, not by a long shot.
Furthermore, Obama actually doesn't have anywhere near as much power domestically as you give him credit for. His domestic power is essentially limited to what his charisma can do, not his actual legal powers -- so you can blame him for international incidents and issues, but it's very difficult to legitimately blame him, especially by placing the entirety of the blame on his shoulders, for domestic problems.
Canada.
Best guess I have is that they removed their implementations of the *at syscalls added in 2.6.16 (since almost no one is using that old a kernel anyway and presumably it made the maintenance easier), and will always directly make use of the kernel versions of those. There were a few other syscalls added in 2.6.16, so it might be related to one of those instead (but the *at ones look most likely to me).
I think my brain just exploded inside my skull.
The summary was pretty terribly worded -- it didn't get across the fact that, essentially, this is stuff you're horridly unlikely to be using. The actual article was much clearer and more matter-of-fact about it.
They were running internet ads for this in ~1998?
Looking into the source briefly suggests it actually doesn't have a hard dependency on udev, but has optional dependencies on: systemd, udev, dbus, libdrm, gbm, egl (mesa), glesv2 (mesa), xkbcommon (a part of X11), freetype2, and pango. This means if you don't intentionally build it with the minimal of requirements (presumably making it no richer in features than the default VT system), it would be linked against all those and break if any of them broke during an upgrade or for any other reason.
This seems like a niche-of-a-niche market, so to speak. I greatly prefer terminal applications, but I always run them under X (using a minimal window manager, etc.) so that I have access to more complex things like PDF viewing or web browsing (beyond links) when needed.
Ah, I guess the Slashdot, Phoronix, and author's blog posts are a bit sensationalist, then -- all three of them make repeated references to completely replacing the standard kernel VT system, including the author recommending disabling CONFIG_VT entirely.
Framebuffer consoles are (or were), in some cases, surprisingly slow. Huge amounts of output at least used to overwhelm them, only catching up if you swapped back and forth between VTs -- this didn't happen in non-framebuffer consoles or in terminal emulators in X.
I think it has improved significantly over the past few years, but that's probably partly from already working some hardware-accelerated rendering into some of the framebuffer console drivers. Though I'm not sure why they're not just working on improving the framebuffer drivers further -- the project seems to aim to put every damn piece into userspace, which seems like a terrible idea for something so essential as the basic console. If you break one of the things it depends on (such as xkb -- yes, really, a piece of X11 for a console system), then you lose any ability to interact with your system, or even view the boot output.
I'm really not sure who it's aimed at. If you break your install and you don't have an old kernel-based VT fallback, you're screwed. If you don't break it and it works fine, what benefit is it? You'll more than likely just be starting up X11 momentarily anyway.
Actually it's very closely linked.
It's not in the best interests of society and societal stability (the general welfare) to have a growing underclass of people who are so poorly thought of and so poor that they would desire to tear the society down. Individual welfare benefits far, far beyond just the individual -- it benefits everyone in keeping society stable and prosperous, even for hard-line capitalists. After all, how can you be a capitalist if someone else is so unhappy with the society that's been created that they wish to murder you and steal your property?
Now I'm just imagining the day the poor schmuck who's Steam Tunnel Operations' webmaster is going to have tomorrow, starting with that e-mail, a few followups from other Slashdotters, and topped off by a heaping helping of spam.
That would be great, ideally (aside from maybe problems with it being absurdly over-engineered).
But it would be really hard to make it catch on. You'd need to manage support for 'traditional' HTTP and the new protocol in all clients, servers, *and* web applications. Because do you really think Microsoft would backport support into old versions of Internet Explorer that people are still using for some god-unknown reason?
Only if you either jailbreak the device or they're (stupidly) not using some sort of public key signing to verify authenticity.
I've actually been using extlinux (the ext2/3/4/btrfs version of syslinux) lately, and find it to be amazing. No issues with running it on a 64-bit native system without IA-32 emulation, which was a stumbling block for getting either grub or lilo working on a system that doesn't need 32-bit at all. Maybe grub2's better about that, but I've not tried it -- I've heard horror stories about grub2's configuration mess.
I think it means it would be contrary to the interests of consumers. Less choice, less competition -- while you can argue the merits of these, they are what the free market economy is, in theory, based on. Calling it 'public interest' to uphold that isn't really much of a stretch.
There's also a lot of self-made porn that just seems like it's done because the 'creator' gets off on exhibitionism.
In much political theory since the, oh, seventeenth or eighteenth century (when democracy started becoming a thing), voting is considered a consent to the system in full, not just consent if whomever you want to win wins. In essence, once you've consented to the system you're consenting to be ruled by the will of the majority, determined however the system determines that will (which in some cases, such as first past the post systems, doesn't even mean an actual majority of the population).
Now, you can of course break that contract and attempt to change the system by revolution, or attempt to change the system from within the rules of that system -- but don't say you never consented and therefore shouldn't have to pay taxes but can reap the benefits of others' taxes.
A contract requires consent. Please show me where I consented to this contract.
You voted, right?
The problem is getting all that information in one place, not really the basics of sorting out interactions. It'd need to be a large, centralized database (at least covering the entire country) and would need to, if this sort of change happened, also track a decent chunk of non-prescription medication somehow.
...You mean Gecko?
gives the impression the author is incompetent.
I remember reading some things back when Diaspora first showed up that suggested this is exactly the case, with both beginner mistakes in security and even the choice of Ruby on Rails for something intended to be run by 'normal users' (which, I've never used Ruby on Rails, but apparently has a habit of breaking applications with every upgrade).
The summary is confusing and inaccurate. The patent was filed in 2008 (not 2009), and the reference to MacOS 9 was referring to a piece in a book ("Insanely Simple: The Obsession That Drives Apple's Success" by Ken Segall, according to the linked article) that suggests that the idea for the patent originated in 1999 (not 2008 or 2009) with Steve Jobs -- back when OS9 was heading towards release, making the reference to OS9 actually make sense.
All this gleamed from clicking the sole link in the /. post, spending 15 seconds skimming it, and having a very basic knowledge of recent OS history. Proofreading, please?
So you have to run your entire life around your work.
Something seems wrong, when that's how life is supposed to be lived.