Is this the same Hurd that will ship one year after Duke Nukem Forever?
Frankly, one of the greatest features of Hurd is that people still talk about it, in the present tense no less, despite appearances that it will never exist.
From GNU Hurd: It is not ready for production use, as there are still many bugs and missing features.
On the negative side, the support for character devices (like sound cards) and other hardware is mostly missing.
There's no set architecture in Linux. All roads lead to madness
To the newbie this perception is immediately apparent.
First question: Which of the hundreds of distros do I use? Hundreds of different answers.
Second question: If they are all Linux, why will this application run on one but not the other? Development geek speak. Third question: Of the hundreds of choices of this particular application, which is best? Hundreds of naswers and then a massive flame war.
Microsoft's quote may sound pathetic to you but, when they tell a neophyte to check for themselves, they are "proven" correct. The uninitiated are confused and intimidated by the vast number of choices, incompatibilities and varied advice from a pleathora of zealots. Just ask a technical question about a mail program like Postfix or Sendmail. Half the responses will be to change distributions. Change the OS because of an issue with the MTA???
Why is this odd? It is an excellent business strategy.
First: When you are about to execute an IPO it is usually undesireable to have lawsuits hanging over your business. This is especially true when the suit is over a patent on your primary source of revenue.
Second: Settling lawsuits is common business practice even with suites that you would likely win. The cost of going to court and defending against the suit, not to mention possible damage to your company's image, is usually higher than the settlement's cost. Therefore, the settlement is viewed as a reduction in operating cost.
Finally: This particular settlement costs Google $0.00. They are literally manufacturing the "money" for this settlement. They are paying in stock. Stock that does not yet have a market value. And, any perceived loss on the potential sale of the stock is made up for by adding more stock to the IPO. It works GREAT for Google, from a business perspective.
The most interesting thing about this article is that, as you stated, the vast majority of posts is in reference to KDE naming. Noticeably absent are posts deriding KDE for technical problems, design issues and or performance issues.
It would suggest, anecdotally anyway, that users have no major issues with KDE which is something that cannot be said about almost any other Linux desktop. Observe other Slashdot articles about Gnome, xFCE or others and you will see lots of comments complaining about bugs, design issues, performance, lack of features and more. There are very few posts of this nature with this article and that alone speaks volumes for KDE.
Could it be that despite the flame wars, KDE is indeed the best/preferred desktop for Linux?
This "protocol" basically combines several different pre-existing protocols. It seems most like a combination of Auto-IP addressing and SLP. The thing is that OS X and several other OSes including Netware and Linux already use SLP. Now Apple wants everyone to change again?
Here's the really strange part. With SLP, unless you do static configurations, the requests are sent via multi cast. This creates an issue because most routers are not configured to handle multicasting so the SLP scope is limited to the local segment.
Apple's new protocol relies on multicast DNS where, DNS requests are sent via multicast. But, the problem with multicasts being restricted to the local segment still exists. This means that Rendezvous offers no clear advantage over SLP, an already defined and implemented standard. So, why should anyone adopt Rendezvous?
policy is to have support contracts on all software that operates mission-critical applications.
I assume that this policy also applies to operating systems. If you are using Windows, Microsoft won't offer any help with Apache. However, Novell uses Jakarta in their Netware OS. Switching your platform to Netware would give you Jakarta support from Novell. Additionally, with Novell's acquisition of SuSE, you may also be able to get a support plan with Novell running Jarkarta on SuSE.
If your agency is willing to spend a lot of money IBM may be the one to choose for Jarkarta support. Although I suspect that they will try to sell you Websphere instead.
Not really. Right now they are receiving a choice of messages based on which stream they choose:
File not founded. Server timeout. Pre-buffering.
Some may say that this due to a Slashdotting but, the streams are supposedly mirrored on Icecast (File not found.) which should definitely be able to handle a Slashdotting.
Sadly, I think that they have proven that their concept is still just that. A working prototype that scales to levels needed for the internet has yet to be realized.
The tiny fuel cell uses 2cc of concentrated methanol to provide 20 hours of power at 100 milliwatts, max.
With regard to refilling. This will be done with a can of compressed methanol. Simply plug the can into the cell for a few seconds and you're good to go for another 20 hours. This process will be very similar to the way that butane cigarette lighters are refilled and have been for more than 30 years. Just for the record, butane is much more flamable/explosive than methanol. Yet, when last did you read of a can of butane or a refillable cigarette lighter exploding?
I never hear about a windowsOS with SQL2000 running on IIS making a site like this work...reliably...it would never happen.
Hold on a second. I'm a big Linux fan and all but, to make claims like this is just not right. There are many large sites that use just the setup that you describe and they work just fine. Look at Dell or eBay for starters.
the more your solution sounds like a taxi service.
I think you are trying to be too high tech in your solution. The way I see it, based on your post, there are two options.
1. If it is a minibus that runs a scheduled service, then put up a poster with the schedule on it.
2. If there isn't a fixed schedule but, rather an on demand arrangement, then use a central dispatcher like taxi services do. The rider calls the dispatcher to request service and the dispatcher tells them when the bus will be there.
Electronic scheduling boards that update in real time, like they have in big cities and airports, are wonderful. But, minibuses and taxis have been running fine without such amenities for more than 100 years.
Perhaps you have noticed that most broadcasters are super imposing their logos and other copyrighted images on your screen. That logo effectively stamps the film that they are broadcasting. They own the logo. You can't copy or distribute that logo without their permission. Therefore, you can't use the film in the background without their permission either.
I don't really think that this is something that most people want. It seems like it might be slightly interesting, for about two minutes, and then you'd turn it off permanently.
But, while we are mentioning Jabber, I have to say that I am a bit disappointed with Jabber. Overall development of the Jabber messaging platform has been slow since the ratification of the protocol and it seems like this is the type of open source project that should really be making advancements. Messaging in the open source community is second only to mp3 listening. I would have expected a project like Jabber to be leading the way in feature development but, compared to the commercial services, Jabber lags far behind.
While commercial services are refining their relatively mature products, Jabber has yet to show any sign of features like voice or video conferencing. Features the commercial competitors have had for some time. Indeed, the existing Jabber components are themselves not yet mature. The newer 2.0 reference server lacks 80% of the features of the original Jabber reference server and configuration is a tangled mess.
This new presence feature is something that no one else has and therefore is a leading innovation. But, at the same time it is a little needed and likely unwanted feature so why not concentrate on other advancements?
Because the tribe, as are most casino operators, are good business men. They know a good investment when they see one and they know how to take advantage of an opportunity to make more money.
Looking at it from a business perspective, it isn't very attractive at all. However, looking at it from the perspective of using someone else's money to provide yourselve's with services is quite attractive. Hence, the casino avoids such investments and the tribe benefits. It's sort of the same way that government grants support crappy research projects that the private sector wouldn't touch.
Conversely, do you mean that there is no room for further change or improvement beyond LSB? Are we to follow LSB without change forever?
The Gobo Linux system creates its own directory structure using simple descriptive names. It looks loike a very nice idea to me. They also have links in place to allow compatibility with the Posix directory structure. LSB is not threatened. Yet.
I like their Compile concept and I like their descriptive path concept. However, I haven't tried this distibution yet so I can't say whether I like it in practice or not. I have difficulty believing that it would be bad.
You claim to be at a large company, that you are the only IT staff, and you are about to be downsized. You don't say whether or not the company will continue operations, will it?
If this company is going to continue operating it will need support for its IT infrastructure. Where will this support be coming from? There is no one better to support them, right now, than you so, use this as an opportunity. Set yourself up as a consultant or the one they outsource their support to. This lets them keep operating smoothly and offers you a chance at a pay rise.
It happens like this all the time. The full-time IT staff is downsized, only to return the next day as contractors getting paid much more than they were the day before.
If however, you play pranks and are generally unprofessional about the job then you lose your job and a good opportunity.
He says 16% (IIRC from the last time slashdot posted this) is needed to be 'edge nodes', ie: internet connected with DSL/cable.
You are right, that is what he said. However, the reality is that the 16% only need to be OSPF Border Gateways. It doesn't matter if the gateways are attached to xDSL, dedicated circuits or other wireless Border Gateways.
Imagine a fully blanketed city with 16% of the access points acting as OSPF Border Gateways connected to other OSPF Border Gateways in other cities by long range wireless shots. You then have the ability to go from one city to the next in two or more hops completely via wireless. Now mesh multiple cities together in the same way and you start to get the picture. It's how the internet works now, it's only a matter of replacing the physical layer. The wires and fibre are replaced with radios.
Also, these mesh protocols are not great (and I doubt they will ever be as good as the current routed internet) and I personally wouldn't like to enjoy 10,000 hop internet from Texas to Michican. Just my 2 cents...
I certainly agree with you here. I wouldn't like so many hops either. Nor would I like the restriction in the bandwidth. Replacing OC12 circuits with 1Mbps wireless shots isn't going to cut it. But, it remains possible. Theoretically, at least. The present routed internet works using the same meshed network principle. Most of those networks run OSPF with BGP on the edges and BGP can run on the Linksys too. There just isn't any need for it yet. Mostly because of the bandwidth.
With heavy enough saturation to provide blanket coverage, these mesh networks would negate the need for the xDSL connection completely. Basically, with enough hotspots in place, the entire internet would be wireless.
Highly, unlikely using 802.11 but, theoretically possible.
Slashdot Mirror
Is this the same Hurd that will ship one year after Duke Nukem Forever?
Frankly, one of the greatest features of Hurd is that people still talk about it, in the present tense no less, despite appearances that it will never exist.
From GNU Hurd: It is not ready for production use, as there are still many bugs and missing features.
On the negative side, the support for character devices (like sound cards) and other hardware is mostly missing.
There's no set architecture in Linux. All roads lead to madness
To the newbie this perception is immediately apparent.
First question: Which of the hundreds of distros do I use? Hundreds of different answers.
Second question: If they are all Linux, why will this application run on one but not the other? Development geek speak.
Third question: Of the hundreds of choices of this particular application, which is best? Hundreds of naswers and then a massive flame war.
Microsoft's quote may sound pathetic to you but, when they tell a neophyte to check for themselves, they are "proven" correct. The uninitiated are confused and intimidated by the vast number of choices, incompatibilities and varied advice from a pleathora of zealots. Just ask a technical question about a mail program like Postfix or Sendmail. Half the responses will be to change distributions. Change the OS because of an issue with the MTA???
Why is this odd? It is an excellent business strategy.
First: When you are about to execute an IPO it is usually undesireable to have lawsuits hanging over your business. This is especially true when the suit is over a patent on your primary source of revenue.
Second: Settling lawsuits is common business practice even with suites that you would likely win. The cost of going to court and defending against the suit, not to mention possible damage to your company's image, is usually higher than the settlement's cost. Therefore, the settlement is viewed as a reduction in operating cost.
Finally: This particular settlement costs Google $0.00. They are literally manufacturing the "money" for this settlement. They are paying in stock. Stock that does not yet have a market value. And, any perceived loss on the potential sale of the stock is made up for by adding more stock to the IPO. It works GREAT for Google, from a business perspective.
The story doesn't say but, if Seagate doesn't have a non-compete contract with him, then they don't have a leg to stand on.
The most interesting thing about this article is that, as you stated, the vast majority of posts is in reference to KDE naming. Noticeably absent are posts deriding KDE for technical problems, design issues and or performance issues.
It would suggest, anecdotally anyway, that users have no major issues with KDE which is something that cannot be said about almost any other Linux desktop. Observe other Slashdot articles about Gnome, xFCE or others and you will see lots of comments complaining about bugs, design issues, performance, lack of features and more. There are very few posts of this nature with this article and that alone speaks volumes for KDE.
Could it be that despite the flame wars, KDE is indeed the best/preferred desktop for Linux?
This "protocol" basically combines several different pre-existing protocols. It seems most like a combination of Auto-IP addressing and SLP. The thing is that OS X and several other OSes including Netware and Linux already use SLP. Now Apple wants everyone to change again?
Here's the really strange part. With SLP, unless you do static configurations, the requests are sent via multi cast. This creates an issue because most routers are not configured to handle multicasting so the SLP scope is limited to the local segment.
Apple's new protocol relies on multicast DNS where, DNS requests are sent via multicast. But, the problem with multicasts being restricted to the local segment still exists. This means that Rendezvous offers no clear advantage over SLP, an already defined and implemented standard. So, why should anyone adopt Rendezvous?
policy is to have support contracts on all software that operates mission-critical applications.
I assume that this policy also applies to operating systems. If you are using Windows, Microsoft won't offer any help with Apache. However, Novell uses Jakarta in their Netware OS. Switching your platform to Netware would give you Jakarta support from Novell. Additionally, with Novell's acquisition of SuSE, you may also be able to get a support plan with Novell running Jarkarta on SuSE.
If your agency is willing to spend a lot of money IBM may be the one to choose for Jarkarta support. Although I suspect that they will try to sell you Websphere instead.
Not really. Right now they are receiving a choice of messages based on which stream they choose:
File not founded.
Server timeout.
Pre-buffering.
Some may say that this due to a Slashdotting but, the streams are supposedly mirrored on Icecast (File not found.) which should definitely be able to handle a Slashdotting.
Sadly, I think that they have proven that their concept is still just that. A working prototype that scales to levels needed for the internet has yet to be realized.
But, important none the less. Visio.
Anyone that seriously suggests Dia as an alternative deserves to be bitch slapped.
Perhaps a RTFA is in order.
The tiny fuel cell uses 2cc of concentrated methanol to provide 20 hours of power at 100 milliwatts, max.
With regard to refilling. This will be done with a can of compressed methanol. Simply plug the can into the cell for a few seconds and you're good to go for another 20 hours. This process will be very similar to the way that butane cigarette lighters are refilled and have been for more than 30 years. Just for the record, butane is much more flamable/explosive than methanol. Yet, when last did you read of a can of butane or a refillable cigarette lighter exploding?
And makes julienne fries to boot!
:(
Is this a Grub config option or do you have to use Lilo to get the fries? I've tried everything I could find in Grub and so far no fries.
(poor NoMachine might lose business now).
This is compounded by higher bandwidth charges due to their present Slashdotting. They'll be tits up in no time.
Does anyone else remember seeing that? I can't seem to find a link.
Sure, here it is. Scroll down for pictures.
I never hear about a windowsOS with SQL2000 running on IIS making a site like this work...reliably...it would never happen.
Hold on a second. I'm a big Linux fan and all but, to make claims like this is just not right. There are many large sites that use just the setup that you describe and they work just fine. Look at Dell or eBay for starters.
I would also expect IBM to use Linux during the upcoming Olympics.
the more your solution sounds like a taxi service.
I think you are trying to be too high tech in your solution. The way I see it, based on your post, there are two options.
1. If it is a minibus that runs a scheduled service, then put up a poster with the schedule on it.
2. If there isn't a fixed schedule but, rather an on demand arrangement, then use a central dispatcher like taxi services do. The rider calls the dispatcher to request service and the dispatcher tells them when the bus will be there.
Electronic scheduling boards that update in real time, like they have in big cities and airports, are wonderful. But, minibuses and taxis have been running fine without such amenities for more than 100 years.
Perhaps you have noticed that most broadcasters are super imposing their logos and other copyrighted images on your screen. That logo effectively stamps the film that they are broadcasting. They own the logo. You can't copy or distribute that logo without their permission. Therefore, you can't use the film in the background without their permission either.
I don't really think that this is something that most people want. It seems like it might be slightly interesting, for about two minutes, and then you'd turn it off permanently.
But, while we are mentioning Jabber, I have to say that I am a bit disappointed with Jabber. Overall development of the Jabber messaging platform has been slow since the ratification of the protocol and it seems like this is the type of open source project that should really be making advancements. Messaging in the open source community is second only to mp3 listening. I would have expected a project like Jabber to be leading the way in feature development but, compared to the commercial services, Jabber lags far behind.
While commercial services are refining their relatively mature products, Jabber has yet to show any sign of features like voice or video conferencing. Features the commercial competitors have had for some time. Indeed, the existing Jabber components are themselves not yet mature. The newer 2.0 reference server lacks 80% of the features of the original Jabber reference server and configuration is a tangled mess.
This new presence feature is something that no one else has and therefore is a leading innovation. But, at the same time it is a little needed and likely unwanted feature so why not concentrate on other advancements?
Why doesn't their own tribe fund this effort?
Because the tribe, as are most casino operators, are good business men. They know a good investment when they see one and they know how to take advantage of an opportunity to make more money.
Looking at it from a business perspective, it isn't very attractive at all. However, looking at it from the perspective of using someone else's money to provide yourselve's with services is quite attractive. Hence, the casino avoids such investments and the tribe benefits. It's sort of the same way that government grants support crappy research projects that the private sector wouldn't touch.
Conversely, do you mean that there is no room for further change or improvement beyond LSB? Are we to follow LSB without change forever?
The Gobo Linux system creates its own directory structure using simple descriptive names. It looks loike a very nice idea to me. They also have links in place to allow compatibility with the Posix directory structure. LSB is not threatened. Yet.
It works opposite to that but, you have the right idea.
/System/Settings/X11 and they create a link for backward compatibility the posix directory structure.
/System/Settings/X11 /etc/X11
The files are in
ln -s
I like their Compile concept and I like their descriptive path concept. However, I haven't tried this distibution yet so I can't say whether I like it in practice or not. I have difficulty believing that it would be bad.
You claim to be at a large company, that you are the only IT staff, and you are about to be downsized. You don't say whether or not the company will continue operations, will it?
If this company is going to continue operating it will need support for its IT infrastructure. Where will this support be coming from? There is no one better to support them, right now, than you so, use this as an opportunity. Set yourself up as a consultant or the one they outsource their support to. This lets them keep operating smoothly and offers you a chance at a pay rise.
It happens like this all the time. The full-time IT staff is downsized, only to return the next day as contractors getting paid much more than they were the day before.
If however, you play pranks and are generally unprofessional about the job then you lose your job and a good opportunity.
He says 16% (IIRC from the last time slashdot posted this) is needed to be 'edge nodes', ie: internet connected with DSL/cable.
You are right, that is what he said. However, the reality is that the 16% only need to be OSPF Border Gateways. It doesn't matter if the gateways are attached to xDSL, dedicated circuits or other wireless Border Gateways.
Imagine a fully blanketed city with 16% of the access points acting as OSPF Border Gateways connected to other OSPF Border Gateways in other cities by long range wireless shots. You then have the ability to go from one city to the next in two or more hops completely via wireless. Now mesh multiple cities together in the same way and you start to get the picture. It's how the internet works now, it's only a matter of replacing the physical layer. The wires and fibre are replaced with radios.
Also, these mesh protocols are not great (and I doubt they will ever be as good as the current routed internet) and I personally wouldn't like to enjoy 10,000 hop internet from Texas to Michican. Just my 2 cents...
I certainly agree with you here. I wouldn't like so many hops either. Nor would I like the restriction in the bandwidth. Replacing OC12 circuits with 1Mbps wireless shots isn't going to cut it. But, it remains possible. Theoretically, at least. The present routed internet works using the same meshed network principle. Most of those networks run OSPF with BGP on the edges and BGP can run on the Linksys too. There just isn't any need for it yet. Mostly because of the bandwidth.
With heavy enough saturation to provide blanket coverage, these mesh networks would negate the need for the xDSL connection completely. Basically, with enough hotspots in place, the entire internet would be wireless.
Highly, unlikely using 802.11 but, theoretically possible.