Well... they have had plans to switch over from the single Cisco to a system that has 2 boxes for redundancy.
Problem is, their network is poorly documented, and one of the few people that had a clue about it is in the hospital. This basicly put the tech in the position of trying to fix a problem that Cisco was claiming that it was the provider's fault for several hours (and it wasn't Exodus' fault, clearly) or to switch over to the Foundries all by herself, trying to get a complex network back up and running when she didn't know all the details about said network.
I've worked there, it's a great environment for the most part. But the networking side sucks due to lack of documentation and lack of staffing. There should never be a situation like the one she was placed in.
Taco, thanks for retracting the "wasn't as qualified as we'd hoped" comment. It's appreciated.
Oh, and who the fuck are you to judge the intent of the author? Especially considering the AUTHOR is the one who's asking the FSF for help SUING the infringing company!!
You're using exising "applications" en masse. You're not taking the code for perl and the code for gzip, embedding them in your app and selling it. (If you are, you can't do that.)
The GPL has nothing to do with how applications use other applications. It has to do with how you take someone's code and use it in your own.
Try Rhode Island as well, they're pushing it so you can't get a permit until 17 and license until 18.
Which is stupid, since these idiots will be driving cars around in college with no frickin' clue of what they're doing when they should have a few years of experience.
Business failures? Read a bit back, these guys just raised about $80million recently.
Bah, they're still buying companies. Sounds to me like they HAVE the money, they just dont want to SPEND the money.
Class action lawsuit (these are people's PAYCHECKS, people) and all the participants in the CLA get together, find a good businessman and form their own ad network.
Heh. Like anyone that bad off is going to be able to load windows from scratch either. "Oh, I have to boot off of a floppy, then install the DOS drivers for the CDROM, then reboot on the floppy again with a modified config.sys and run mscdex.exe and then d: and run setup"?
*ROFL*
Um, no, the only way clueless people can install operating systems is from rescue disks. And anyone who wanted to could make the same type of rescue disks for Linux that HP/DELL/IBM/COMPAQ/etc. make for their pre-installed Windows systems.
Heck, you could even mail her updated Linux rescue disks... if something happens, she'll get a more up-to-date installation that before.
Themes all depend on the WM. That isn't something that will be happening.
That said, there is a whole mailing list dedicated to KDE-GNOME interaction. And in whole, the WM Spec mailing list got very good interaction from WM developers, KDE developers, and GNOME developers.
I think it all depends on what you define as 'beautiful' code.
Is it aesthetically pleasing code, that's idented properly, uses newlines for readability rather than new commands?
Or is it a piece of code that you must sit and spend a few hours on a few lines of code to truly grok all that it is?
A good example of this is procmail. It's an extremely widely used mail delivery agent. Its code however, in my opinion is ugly. It's hard to follow (hell, they even use 'goto' in C...)... but if you spend the time to grok it, you are amazed at exactly how tightly the code was written.
I consider procmail, for all its performance stretching obfuscated elegance, to be ugly code. I consider something like qPopper (sponsored by Eudora) to be beautiful code. It's highly readable, the variable names make sense, it's modular, it's logical.
In working on developing a customized mail service, I had to modify both procmail and qpopper. I absolutely hated working on procmail and loved working on qpopper.
Just my $0.02cp... all that's left after Uncle Sam takes his damn taxes...
Um, ICANN is the new person on the block to be the over all controller of sub registrars, one of which will be NSI. That's why there is the issue; NSI is loosing it's monopoly and they're like "Fuck you, we'll make it a bitch to happen. You got it on paper, come and take it in real life."
Slashdot Mirror
Well... they have had plans to switch over from the single Cisco to a system that has 2 boxes for redundancy.
Problem is, their network is poorly documented, and one of the few people that had a clue about it is in the hospital. This basicly put the tech in the position of trying to fix a problem that Cisco was claiming that it was the provider's fault for several hours (and it wasn't Exodus' fault, clearly) or to switch over to the Foundries all by herself, trying to get a complex network back up and running when she didn't know all the details about said network.
I've worked there, it's a great environment for the most part. But the networking side sucks due to lack of documentation and lack of staffing. There should never be a situation like the one she was placed in.
Taco, thanks for retracting the "wasn't as qualified as we'd hoped" comment. It's appreciated.
--etrnl--
Oh, and who the fuck are you to judge the intent of the author? Especially considering the AUTHOR is the one who's asking the FSF for help SUING the infringing company!!
--etrnl--
And then someone hears about it, and inspects the files on the CD without installing it and clicking to aggree to it.
Or you put their asses in court and subpeona it to investigate it... using the DMCA to shut them down until the court case is settled.
--etrnl--
What you're doing is very different.
You're using exising "applications" en masse. You're not taking the code for perl and the code for gzip, embedding them in your app and selling it. (If you are, you can't do that.)
The GPL has nothing to do with how applications use other applications. It has to do with how you take someone's code and use it in your own.
(Ie, it's not about USE but DISTRIBUTION.)
--etrnl--
Try Rhode Island as well, they're pushing it so you can't get a permit until 17 and license until 18.
Which is stupid, since these idiots will be driving cars around in college with no frickin' clue of what they're doing when they should have a few years of experience.
What a moronic country we live in...
--etrnl
Business failures? Read a bit back, these guys just raised about $80million recently.
Bah, they're still buying companies. Sounds to me like they HAVE the money, they just dont want to SPEND the money.
Class action lawsuit (these are people's PAYCHECKS, people) and all the participants in the CLA get together, find a good businessman and form their own ad network.
My $0.02. Granted, IANAL.
--etrnl
Heh. Like anyone that bad off is going to be able to load windows from scratch either. "Oh, I have to boot off of a floppy, then install the DOS drivers for the CDROM, then reboot on the floppy again with a modified config.sys and run mscdex.exe and then d: and run setup"?
*ROFL*
Um, no, the only way clueless people can install operating systems is from rescue disks. And anyone who wanted to could make the same type of rescue disks for Linux that HP/DELL/IBM/COMPAQ/etc. make for their pre-installed Windows systems.
Heck, you could even mail her updated Linux rescue disks... if something happens, she'll get a more up-to-date installation that before.
THAT is the power of Open Source.
--etrnl--
Themes all depend on the WM. That isn't something that will be happening.
That said, there is a whole mailing list dedicated to KDE-GNOME interaction. And in whole, the WM Spec mailing list got very good interaction from WM developers, KDE developers, and GNOME developers.
You'll see more in Gnome 1.4 and above.
--etrnl--
I think it all depends on what you define as 'beautiful' code.
Is it aesthetically pleasing code, that's idented properly, uses newlines for readability rather than new commands?
Or is it a piece of code that you must sit and spend a few hours on a few lines of code to truly grok all that it is?
A good example of this is procmail. It's an extremely widely used mail delivery agent. Its code however, in my opinion is ugly. It's hard to follow (hell, they even use 'goto' in C...)... but if you spend the time to grok it, you are amazed at exactly how tightly the code was written.
I consider procmail, for all its performance stretching obfuscated elegance, to be ugly code. I consider something like qPopper (sponsored by Eudora) to be beautiful code. It's highly readable, the variable names make sense, it's modular, it's logical.
In working on developing a customized mail service, I had to modify both procmail and qpopper. I absolutely hated working on procmail and loved working on qpopper.
Just my $0.02cp... all that's left after Uncle Sam takes his damn taxes...
--etrnl
So what, Linux isn't a UNIX variant?
Christ, ye people...
-=-etrnl-=-
Actually, it seems to be a router blocking it, or somesuch as opposed to a traffic issue. See:
http://bugzilla.mozilla.org/show_bug.cgi?id=62130
-=-etrnl-=-
If search engines updated within a reasonable amount of time, it wouldnt be bad... as it, it's hell.
Um, ICANN is the new person on the block to be the over all controller of sub registrars, one of which will be NSI. That's why there is the issue; NSI is loosing it's monopoly and they're like "Fuck you, we'll make it a bitch to happen. You got it on paper, come and take it in real life."