Sorry, no. As soon as he's finished it's a never ending grind for 'what have you published lately?'. Now is the time to enjoy life. It's hard to get the chance after.
The LSB is a steaming pile of crap and always has been. That said, your specific complaints are... bizaare. Linux systems can maintain an arbitrary number of old libraries transparently, with no breakage.
Of course one can, provided the library maintainers do not change the ABI while retaining the same library version numbers...
Did the study evaluate the amount of non native speakers visiting the hotel? If you do not speak fluently the receptionist's language, it is much more comfortable to deal with the virtual keyboard of a kiosk.
I stand by my opinion: You're free to say or believe in anything you want.
Should you? In most european countries, there are some opinions that are an offence. You can believe in them, but saying them in public may get you a fine. The best example is saying that the nazis never killed the jews during WWII. Even in the US, libel laws limit free speech.
Do you think there should be no limit to free speech?
If the LSB worked anthing close to how it was envisioned, developers would flock to the platform and then so would users
LSB solves some bits of the problem, but not the most troublesome. It does not help you with libraries or kernel changing ABI in a backward incompatible way, something that causes packaging headaches when upgrading a given system.
What is a bit frustrating is that it could be done cleanly, if developers just took the time for it. For instance NetBSD base system is nicely backward compatible. A binary built on NetBSD-0.8 is still able to run 20 years later on NetBSD 6.0.1. And you can throw a package built for NetBSD 5.0 on NetBSD 6.0.1, it works... provided you have also installed the dependencies for it, which are provided in other packages outside of NetBSD base system, and this is where things goes wrong. Package A will need version 1.0.1 of package B, you have version 1.0 installed. You need to upgrade B. But B is required by packages C, D, E... Z, and you will have to upgrade them too. But they require new versions of others packages, and so on.
Every gram of carbon dioxide you emit while cycling was previously fixed directly from the atmosphere by a plant or alga. If you didn't re-emit it, the food you would have eaten would rot instead.
You can also not re-emit it by making fat. But this is not satisfying, as obesity has a huge cost for society, which translates into a CO2 emission footprint. And if you get incinerated when you die, all your fat-stored carbon will go to the atmosphere again
If you want universal access, even in rural places where infrastructure costs will push profitability decades away, the you should not rely on free market to do it. Would you refute that?
But as I understand, the US telecom market is neither a free market, not a government-controlled public service. It is a mix of the bad sides of both approach: profit-seeking private operators that do not have to compete with each others.
NetBSD is not famous, but it definitively deserves a look for an embedded OS.
First, it supports major CPU used in the embedded field: ARM, SH3, SH5, PowerPC. So does Linux, but NetBSD has the nice ability to be cross-buildable from any POSIX/ANSI C platform. You can build your NetBSD embedded system from Linux, MacOS X, and even Windows + cygwin
Then there are the architecture and bus independant drivers. NetBSD uses the same driver for a given chip, whatever the CPU is, or whatever the bus the chip is hooked to. This means most of the time you do not have to rewrite or tweak drivers when working on an embedded platform: you reuse existing code.
Oh really? So far as I know, nothing has broken backward compatibility for the Office document formats since Office 2007.
If you have people using different versions of Office, you can always open the document from your peers, but you get myriad small issues. The document never looks exactly the same.
It could be a good move if MS used a stable standard file format, but since they always slightly breake backward compatibility, the more upgrade we get, the more mess we have.
And if the assailant does have a gun, I prefer to give him my wallet rather than having a gun on my own to defend myself. Odds are high that I would be shot, and my wallet is not worth my life.
The missing bit that strikes me here is the serial console. If a server does not boot anymore and you want to go single user to fix things, the serial console is convenient, as it allows you to do it without going into the data center an hook a keyboard and a screen.
I tend to be a mac person on the desktop, but I am not convinced by mac servers since the day they retired their 1U Xserve
Not enough skilled engineers? Perhaps big companies could stop working on tax evasion, so that more money could go to the educational system, lowering the need for student debt (the net bubble, anyway), and allowing more students to go through college.
Your entertainment lobby got 6 strikes for you, whereas it pushed 3 strikes in most of the world. I am not sure why they did this gift to you, but I guess you should feel lucky
One way to help shore up defenses would be to improve--or replace--the existing certificate authority infrastructure, the panelists said
Indeed. IMO SSL public keys could be stored in DNSsec protected DNS records. That way one would only have to trust the manager of the root zone and the TLD, which would be a good improvement compared to the CA debacle.
"American made" is not a selling point, it's bigotry. Idiots.
American patriotism halts at the wallet?
Re:how does it compare to NetBSD as a teaching too
on
Minix 3.2.1 Released
·
· Score: 1
One thing I think is that the NetBSD guys should consider adapting this as their kernel, given that they target mainly embedded systems, and Minix, w/ the microkernel, is a much better fit for that. Maybe merge the 2, and make it the standard target for current x86 and ARM systems.
Merging kernels is no trivial job. The only reasonable thing that could be done would be to have the BSD kernel sitting on the top of a microkernel, just like MacOS X does.
Slashdot Mirror
Sorry, no. As soon as he's finished it's a never ending grind for 'what have you published lately?'. Now is the time to enjoy life. It's hard to get the chance after.
The next chance is emeritus
The LSB is a steaming pile of crap and always has been. That said, your specific complaints are... bizaare. Linux systems can maintain an arbitrary number of old libraries transparently, with no breakage.
Of course one can, provided the library maintainers do not change the ABI while retaining the same library version numbers...
Did the study evaluate the amount of non native speakers visiting the hotel? If you do not speak fluently the receptionist's language, it is much more comfortable to deal with the virtual keyboard of a kiosk.
I stand by my opinion: You're free to say or believe in anything you want.
Should you? In most european countries, there are some opinions that are an offence. You can believe in them, but saying them in public may get you a fine. The best example is saying that the nazis never killed the jews during WWII. Even in the US, libel laws limit free speech.
Do you think there should be no limit to free speech?
If the LSB worked anthing close to how it was envisioned, developers would flock to the platform and then so would users
LSB solves some bits of the problem, but not the most troublesome. It does not help you with libraries or kernel changing ABI in a backward incompatible way, something that causes packaging headaches when upgrading a given system.
What is a bit frustrating is that it could be done cleanly, if developers just took the time for it. For instance NetBSD base system is nicely backward compatible. A binary built on NetBSD-0.8 is still able to run 20 years later on NetBSD 6.0.1. And you can throw a package built for NetBSD 5.0 on NetBSD 6.0.1, it works... provided you have also installed the dependencies for it, which are provided in other packages outside of NetBSD base system, and this is where things goes wrong. Package A will need version 1.0.1 of package B, you have version 1.0 installed. You need to upgrade B. But B is required by packages C, D, E... Z, and you will have to upgrade them too. But they require new versions of others packages, and so on.
No. The second point is complete nonsense.
Every gram of carbon dioxide you emit while cycling was previously fixed directly from the atmosphere by a plant or alga. If you didn't re-emit it, the food you would have eaten would rot instead.
You can also not re-emit it by making fat. But this is not satisfying, as obesity has a huge cost for society, which translates into a CO2 emission footprint. And if you get incinerated when you die, all your fat-stored carbon will go to the atmosphere again
If you want universal access, even in rural places where infrastructure costs will push profitability decades away, the you should not rely on free market to do it. Would you refute that?
But as I understand, the US telecom market is neither a free market, not a government-controlled public service. It is a mix of the bad sides of both approach: profit-seeking private operators that do not have to compete with each others.
NetBSD is not famous, but it definitively deserves a look for an embedded OS.
First, it supports major CPU used in the embedded field: ARM, SH3, SH5, PowerPC. So does Linux, but NetBSD has the nice ability to be cross-buildable from any POSIX/ANSI C platform. You can build your NetBSD embedded system from Linux, MacOS X, and even Windows + cygwin
Then there are the architecture and bus independant drivers. NetBSD uses the same driver for a given chip, whatever the CPU is, or whatever the bus the chip is hooked to. This means most of the time you do not have to rewrite or tweak drivers when working on an embedded platform: you reuse existing code.
Sometimes I think that mankind deserves to become extinct.
Don't worry, we are working on it
Oh really? So far as I know, nothing has broken backward compatibility for the Office document formats since Office 2007.
If you have people using different versions of Office, you can always open the document from your peers, but you get myriad small issues. The document never looks exactly the same.
It could be a good move if MS used a stable standard file format, but since they always slightly breake backward compatibility, the more upgrade we get, the more mess we have.
And if the assailant does have a gun, I prefer to give him my wallet rather than having a gun on my own to defend myself. Odds are high that I would be shot, and my wallet is not worth my life.
All of a sudden you are outside and a thug walks by making obvious threats and you start running inside to get away or get your gun
It is amazing how guns are differently perceived among countries. This scenario is just science fiction for me.
The missing bit that strikes me here is the serial console. If a server does not boot anymore and you want to go single user to fix things, the serial console is convenient, as it allows you to do it without going into the data center an hook a keyboard and a screen.
I tend to be a mac person on the desktop, but I am not convinced by mac servers since the day they retired their 1U Xserve
Why not go further, and only allow patent litigation between practicing entities?
The US Federal Government SEIZED GM from the bondholders
And you think no other country government could do such a thing? I am sure the Chineese government could do the ame thing in China
Only setup AAAA records in DNS, instead of A records, that way your server will only be reached through IPv6.
I understand Antigua already won their case, but indeed I wonder how such decision would have played in it.
Exactly, plus the ability to roll a new key with no delay.
Not enough skilled engineers? Perhaps big companies could stop working on tax evasion, so that more money could go to the educational system, lowering the need for student debt (the net bubble, anyway), and allowing more students to go through college.
How is it relevant for other FOSS operating systems, such as NetBSD, FreeBSD, OpenBSD, Haiku, DragonflyBSD, etc... ?
Your entertainment lobby got 6 strikes for you, whereas it pushed 3 strikes in most of the world. I am not sure why they did this gift to you, but I guess you should feel lucky
From TFA
One way to help shore up defenses would be to improve--or replace--the existing certificate authority infrastructure, the panelists said
Indeed. IMO SSL public keys could be stored in DNSsec protected DNS records. That way one would only have to trust the manager of the root zone and the TLD, which would be a good improvement compared to the CA debacle.
"American made" is not a selling point, it's bigotry. Idiots.
American patriotism halts at the wallet?
One thing I think is that the NetBSD guys should consider adapting this as their kernel, given that they target mainly embedded systems, and Minix, w/ the microkernel, is a much better fit for that. Maybe merge the 2, and make it the standard target for current x86 and ARM systems.
Merging kernels is no trivial job. The only reasonable thing that could be done would be to have the BSD kernel sitting on the top of a microkernel, just like MacOS X does.