Fortunately, almost no one really takes ATM seriously. Thank ! Also, your point is a little misguided, since someone in the middle of the ATM network has to trap your UNI cells to figure out the ATM address the circuit came from. There's also the possibility of interrogating the user's switch for its VC table. But just looking at some cell stream can't tell you the ATM address to whom it belongs. At least not immediately (you might see some OAM cells that carry interesting information). OTOH, it's not easy to subvert the PNNI routing or (as is mostly the case) the static PVP/PVC routing.
And yes, the IETF neterati ABSOLUTELY HATE WITH A PASSTION ATM. But... I digress...
There is an RFC which encodes the ATM ESI, stripping off the 13 byte NSAP prefix.
God forbid the enlisted actually have a marketable skill when they get detached! Wouldn't want one of those folks knowing how to admin a Linux system now, would we? Boiler maintenance, now there's a marketable skill for ya!
Speaking as reservist in the military, you need to get a less pedestrian and provincial view of what the armed forces do. Perform a rectal craniotomy while you're at it. The fact that someone in a military research lab somewhere (NRL, Mitre, The Aerospace Corportaion, Rome Labs, DARPA JPO) is looking at deploying Linux should not come as a surprise.
If any of you all recall last year's incident with the USS Yorktown (needing a tow because all NT systems controlling propulsion crashed), maybe Linux is a step forward. Look it on Wired. It's certainly more cost effective and it really is more reliable than NT.
And c'mon, just 'cos the military uses it doesn't mean that mean that storm troopers will pour out of the sky and invalidate the GPL. The military is not about taking rights away. There are borders to this world, whether we like it or not, that must be defended. The US armed forces are dedicated to preserving the Constitution of the United States and the rights thereunto contained from all foreign enemies. (Yes, that may sound a little idealistic, but that's why I signed up -- to put my mouth where my beliefs are: The US Constitution's preservation.)
Guess who the last people who want to fight conflicts are? Military commanders! Why? Because they are the ones responsible for sending the letter home that reads, "Dear Mrs. Smith: We regret to inform you that..."
Operating systems can be interesting things to rewrite. But let's look at the OS utilities and packages.
Like I asked, how many PPP managers does the world really need? It's almost gotten to the point of being like Kama Sutra position number 468, which was 467 with left pinky extended.:-)
They do use BSD. The trend today is "Commercial, Off-The-Shelf" which is usually used in the same breath as "Windows NT". Sometimes it's used in polite company as a way to refer to NT without causing ladies to puke.
Many installations use Solaris and some use BSD variants of one shade or another. The problem comes down to enlisted people learning how to do system administration. When an enlisted person became competent (and despite what you may think, many enlisted are seriously competent people [can you tell I'm an officer yet?]), they had no incentive to stay in the military.
The gov't gets really pissy about upholding the law and respecting copyrights and lefts. They won't "end run" it. If the gov't doesn't uphold and respect the law, who will?
If memory serves me correctly, but the Linux kernel isn't the security problem. It's all of the utilities that generate security problems. Remember AMD's root exploit last year?
One question that really begs to be asked: If an organization of programmers gets together and designs a new windowing environment or window manager, why is it that the fan club has to reinvent apps that were previously debugged and secured?
I mean, how many PPP managers does the world need? The world needs the code that manages the back end, obviously, but the FE's should be replaceable. After all, that's been a holy grail of software development for years now, right?
As for 'public defamation of a prior employer', why not? You say it's unprofessional, I say it's fair game, and in most cases it does public good. I have chosen not to accept positions with some entertainment studios due to former employees bad experiences. Saved myself grief and stress. And that's bad?
You can say a lot by saying nothing at all. Venting spew all over the place doesn't accomplish much and tends to piss a lot of people off. Secondly, you might need a recommendation from someone at your last employer; burning bridges isn't necessary either.
Not that Rasterman needs a recommendation, but the rest of us mortals might.
Linux isn't about marketing and making $, Linux is about what we want it to be.
Red Hat != Linux. Red Hat == Linux distribution
Of course Red Hat is in the business of productizing Linux in a form that people, generally unwashed masses, will actually use. We can all dream on about why Linux suddenly is so visible in the trade press (my theory is hypercaustic chihuahuas yapping at the top of their lungs on certain news groups). That doesn't preclude the need for someone to step up to the plate, define a distro, provide support for it (not everyone out there is a coder, BTW), forge alliances with distribution channels, pry it into new markets, etc.
As for Rasterman's "integrity" and the "authenticity" spooge, get real. Yes, one would like to keep one's self intact, but sometimes one has to sell out temporarily to acheive another goal. Permanently selling out is a bad thing, but to change a couple of songs to please the corporate mavens (in another message) isn't a bad thing. It's part of a give and take -- if one isn't a good negotiator and can't assert oneself to keep a couple of the unchanged songs, one deserves to be road-kill.
I'm not sure why there's always been an anti-biz slant to just about every one of these divorces. Sometimes, and I've been there and done that, one has to do code which productizes software.
Overall, I think RH is on the right track to making Linux (or broadly, Unix, since most Linux apps will run on other x86 Unix platforms) usable for the masses. Yes, it means "selling out" to "the corporates" -- but it's not selling out, per se. The reason why mediocrity has 90% of the users out there is because it has an incredible marketing machine (and really crafty contract writers.) Part of the RH strategy is to give the ordinary (dare I say, mediocre?) users something they're familiar with... and then be completely subversive by introducing changes that get them on the road to something more useful (UI-wise, application-wise, etc.)
While I appreciate and try to code to perfection too, there's a point at which the code has to be released and shipped. Usually companies have two sets of coders: one which creates the features and the "cool stuff" and another set which productizes. It seems to me that RHAD combined the two, pissed off one of their developers, and now we all get to hear about the bad blood.
Personally, I hope there's an opening when I finish this degree at RHAD. The important lesson is to choke down one's ego when it's appropriate.
Slashdot Mirror
Fortunately, almost no one really takes ATM seriously. Thank ! Also, your point is a little misguided, since someone in the middle of the ATM network has to trap your UNI cells to figure out the ATM address the circuit came from. There's also the possibility of interrogating the user's switch for its VC table. But just looking at some cell stream can't tell you the ATM address to whom it belongs. At least not immediately (you might see some OAM cells that carry interesting information). OTOH, it's not easy to subvert the PNNI routing or (as is mostly the case) the static PVP/PVC routing.
And yes, the IETF neterati ABSOLUTELY HATE WITH A PASSTION ATM. But... I digress...
There is an RFC which encodes the ATM ESI, stripping off the 13 byte NSAP prefix.
-scooter
God forbid the enlisted actually have a marketable skill when they get detached! Wouldn't want one of those folks knowing how to admin a Linux system now, would we? Boiler maintenance, now there's a marketable skill for ya!
-scooter
It's true.
Speaking as reservist in the military, you need to get a less pedestrian and provincial view of what the armed forces do. Perform a rectal craniotomy while you're at it. The fact that someone in a military research lab somewhere (NRL, Mitre, The Aerospace Corportaion, Rome Labs, DARPA JPO) is looking at deploying Linux should not come as a surprise.
..."
If any of you all recall last year's incident with the USS Yorktown (needing a tow because all NT systems controlling propulsion crashed), maybe Linux is a step forward. Look it on Wired. It's certainly more cost effective and it really is more reliable than NT.
And c'mon, just 'cos the military uses it doesn't mean that mean that storm troopers will pour out of the sky and invalidate the GPL. The military is not about taking rights away. There are borders to this world, whether we like it or not, that must be defended. The US armed forces are dedicated to preserving the Constitution of the United States and the rights thereunto contained from all foreign enemies. (Yes, that may sound a little idealistic, but that's why I signed up -- to put my mouth where my beliefs are: The US Constitution's preservation.)
Guess who the last people who want to fight conflicts are? Military commanders! Why? Because they are the ones responsible for sending the letter home that reads, "Dear Mrs. Smith: We regret to inform you that
Operating systems can be interesting things to rewrite. But let's look at the OS utilities and packages.
:-)
Like I asked, how many PPP managers does the world really need? It's almost gotten to the point of being like Kama Sutra position number 468, which was 467 with left pinky extended.
-scooter
They do use BSD. The trend today is "Commercial, Off-The-Shelf" which is usually used in the same breath as "Windows NT". Sometimes it's used in polite company as a way to refer to NT without causing ladies to puke.
Many installations use Solaris and some use BSD variants of one shade or another. The problem comes down to enlisted people learning how to do system administration. When an enlisted person became competent (and despite what you may think, many enlisted are seriously competent people [can you tell I'm an officer yet?]), they had no incentive to stay in the military.
The gov't gets really pissy about upholding the law and respecting copyrights and lefts. They won't "end run" it. If the gov't doesn't uphold and respect the law, who will?
-scooter
If memory serves me correctly, but the Linux kernel isn't the security problem. It's all of the utilities that generate security problems. Remember AMD's root exploit last year?
One question that really begs to be asked: If an organization of programmers gets together and designs a new windowing environment or window manager, why is it that the fan club has to reinvent apps that were previously debugged and secured?
I mean, how many PPP managers does the world need? The world needs the code that manages the back end, obviously, but the FE's should be replaceable. After all, that's been a holy grail of software development for years now, right?
-scooter
As for 'public defamation of a prior employer', why not? You say it's unprofessional, I say it's fair game, and in most cases it does public good. I have chosen not to accept positions with some entertainment studios due to former employees bad experiences. Saved myself grief and stress. And that's bad?
You can say a lot by saying nothing at all. Venting spew all over the place doesn't accomplish much and tends to piss a lot of people off. Secondly, you might need a recommendation from someone at your last employer; burning bridges isn't necessary either.
Not that Rasterman needs a recommendation, but the rest of us mortals might.
-scooter
Linux isn't about marketing and making $, Linux is about what we want it to be.
Red Hat != Linux. Red Hat == Linux distribution
Of course Red Hat is in the business of productizing Linux in a form that people, generally unwashed masses, will actually use. We can all dream on about why Linux suddenly is so visible in the trade press (my theory is hypercaustic chihuahuas yapping at the top of their lungs on certain news groups). That doesn't preclude the need for someone to step up to the plate, define a distro, provide support for it (not everyone out there is a coder, BTW), forge alliances with distribution channels, pry it into new markets, etc.
As for Rasterman's "integrity" and the "authenticity" spooge, get real. Yes, one would like to keep one's self intact, but sometimes one has to sell out temporarily to acheive another goal. Permanently selling out is a bad thing, but to change a couple of songs to please the corporate mavens (in another message) isn't a bad thing. It's part of a give and take -- if one isn't a good negotiator and can't assert oneself to keep a couple of the unchanged songs, one deserves to be road-kill.
-scooter
WindowManager, to some extent, does this already.
I'm not sure why there's always been an anti-biz slant to just about every one of these divorces. Sometimes, and I've been there and done that, one has to do code which productizes software.
Overall, I think RH is on the right track to making Linux (or broadly, Unix, since most Linux apps will run on other x86 Unix platforms) usable for the masses. Yes, it means "selling out" to "the corporates" -- but it's not selling out, per se. The reason why mediocrity has 90% of the users out there is because it has an incredible marketing machine (and really crafty contract writers.) Part of the RH strategy is to give the ordinary (dare I say, mediocre?) users something they're familiar with... and then be completely subversive by introducing changes that get them on the road to something more useful (UI-wise, application-wise, etc.)
While I appreciate and try to code to perfection too, there's a point at which the code has to be released and shipped. Usually companies have two sets of coders: one which creates the features and the "cool stuff" and another set which productizes. It seems to me that RHAD combined the two, pissed off one of their developers, and now we all get to hear about the bad blood.
Personally, I hope there's an opening when I finish this degree at RHAD. The important lesson is to choke down one's ego when it's appropriate.
-scooter