IRC is a protocol. Go read RFC 1459. We're saying the _protocol_ sucks, not the end user experience on a working IRC network. --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
SYN cookies only prevent SYN flooding. They don't prevent UDP flooding, ICMP flooding, TCP connection flooding, or any other DoS method. --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Instead of just giving your hired [ch]rackers the full brunt of your security, start by doing that, then periodically give them chunks of information they could gain from various employees, source code, passwords, etc, *until they break it*. That way, you'll know _how_ secure your system is, not just that it is too hard for so-and-so to crack. --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
When you want to be able to translate code into its optimal representation for a particular platform, you want to have as good of an idea of what that program does as possible. That way, your translator can "know" what's really going on and optimize your code for that purpose.
Some systems can do floating-point operations faster one way than another. The same goes for loops, graphics, sound, and every other conceivable task.
So, the idea was to break the code down to its lowest level possible, while still maintaining its structure and the intent of the programmer.
So, it's not really assembly language (what do you expect anyway, with a multiplatform system?), but it's lower-level than C, and it is the step right before the VM bytecode. --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
That's a good point. Very often, in law, people who are required to do/allow something don't necessarily have to do it for free. --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Over the years, copy protection has been proven to be impossible to achieve, and to be nothing more than an annoyance to legitimate users.
*Never* advocate copy protection. It just makes people's lives miserable, and it doesn't ever to its job properly. --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
I agree that Linux isn't ready for the desktop yet (depends what your desktop users do in a day, though). However, I'm going to argue some of your points anyway.
What happens, however, if a user turns his PC off with out shutting it down - It happens, especially when they want to
get out of the office as fast as possible on a Friday evening. Chances are that Linux will not boot up again,/dev/hda2
was not cleanly unmounted, cannot find superblock, kernel panic etc... Windows 95 can recover quite easily from bad
shutdowns, Linux can't... I'm sure some smart-alec will come along and mention some configuration change that
makes Linux more robust with regard to unclean shutdowns
In fact, you can get rid of the fscking altogether if you use journalling filesystems like reiserfs or ext3.
TCO lower? - I'm the only local IT person in my company who even uses Linux. The only difference of TCO with
Linux and MS is the client cost, less than $100 - which is an insignificant amount, when looking at total support costs,
and Linux has significantly higher support costs.
Depends on the size of your network. If you have 10000 workstations, all clones of each other booting off a network server, the TCO will definitely be lower, because your support people will only have to fix problems once. However, if you only have 10-100 workstations, it might not be worth it.
Uptime - Are you secretly trying to agree with me here? Uptime is not a desktop client feature - it is a server feature.
Nearly all desktop clients get rebooted daily.
Yes, but the *reason* OSes have bad uptime is because they *crash*. Crashing, AFAIK, is the number one problem users have with Microsoft products. Ever overheard a complaint about a computer? It's almost never about something that is a consistent problem with their computer; it's usually about how "I was just using it and suddenly it froze". Although 200-day uptimes aren't necessary, the point is that Linux won't just up and crash for no reason. --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Designing code is easy? I beg to differ. True, it's easy to write code, but designing it is another matter.
For instance, many algorithms can be written either as a 100-line piece of deeply-nested looping code, or as a single, simple, mathematical formula. Many people will find all sorts of different ways of writing the 100 lines, but few will see the simple math formula that will do the job a dozen times more quickly.
Those guys that say "I don't code anymore" spend their days coming up with the ways of making sure those 100000 lines of code never exist in the first place. I have more respect for those guys than the people who write code that simply works. --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Better to listen to him than to listen to an AC who isn't even a "division manager for an IT company".
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Re:Novell ain't dead, but on the back burner
on
Is Novell Doomed?
·
· Score: 1
If Netware 3.11 was perfect software, then everybody would be installing it.
<P>"Perfect" in this context means it does what it's supposed to do, and does it well. People won't buy Novell 3.11 when most of their network is TCP/IP. But they'll never consider "upgrading" their software, because it does what it is supposed to do, and does it well. --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Re:Novell ain't dead, but on the back burner
on
Is Novell Doomed?
·
· Score: 1
If Netware 3.11 was perfect software, then everybody would be installing it.
<P>"Perfect" in this context means it does what it's supposed to do, and does it well. People won't buy Novell 3.11 when most of their network is TCP/IP. But they'll never consider "upgrading" their software, because it does what it is supposed to do, and does it well. --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Not everyone purchases licenses for the newest version of NetWare. My school uses Netware 3.x, for instance. What's the cost for legacy versions of NetWare? --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
No, it places large restrictions on potential *distributors* (mainly those who don't want to distribute to others what they've been distributed to). --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
What we need to do is not increase the number of things that are illegal, but increase the PENALTY for doing those things. Too often, a person gets a "3 year sentence", but gets out in 6 months. (Or a "Life sentence" and gets out in 10-15 years.)
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Actually, it should be "KDE/Linux". Think division; It's pronounced "KDE over Linux" or "KDE on top of Linux". --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
You should have said "Yes! I'll do it," then waited a day, then said "here you are, now where's my vouchers?":-) --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
That downloads and installs all the KDE packages. If you managed to install the OS, you'll be able to do this. --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
I'm going to bitch about that stupid tag handling. I chose "Extrans", dammit!! --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
I'm not saying RMS is the person I'd want in charge. I'm saying he's a good, predictable, figurehead. Even the most zealous of free software fanatics can look up to him.
<I>Yeah, well, think "The Crusades".</I>
And this helps your argument how? --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Slashdot Mirror
IRC is a protocol. Go read RFC 1459. We're saying the _protocol_ sucks, not the end user experience on a working IRC network.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
SYN cookies only prevent SYN flooding. They don't prevent UDP flooding, ICMP flooding, TCP connection flooding, or any other DoS method.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Hmm.. What was around in 1985?
;-P
DOS, MacOS, AmigaOS, UNIX. (and others I'm sure).
Surely, DOS is the best of the pack.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Instead of just giving your hired [ch]rackers the full brunt of your security, start by doing that, then periodically give them chunks of information they could gain from various employees, source code, passwords, etc, *until they break it*. That way, you'll know _how_ secure your system is, not just that it is too hard for so-and-so to crack.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
...and therefore write cleaner code.
When you want to be able to translate code into its optimal representation for a particular platform, you want to have as good of an idea of what that program does as possible. That way, your translator can "know" what's really going on and optimize your code for that purpose.
Some systems can do floating-point operations faster one way than another. The same goes for loops, graphics, sound, and every other conceivable task.
So, the idea was to break the code down to its lowest level possible, while still maintaining its structure and the intent of the programmer.
So, it's not really assembly language (what do you expect anyway, with a multiplatform system?), but it's lower-level than C, and it is the step right before the VM bytecode.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
That's a good point. Very often, in law, people who are required to do/allow something don't necessarily have to do it for free.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Over the years, copy protection has been proven to be impossible to achieve, and to be nothing more than an annoyance to legitimate users.
*Never* advocate copy protection. It just makes people's lives miserable, and it doesn't ever to its job properly.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
I agree that Linux isn't ready for the desktop yet (depends what your desktop users do in a day, though). However, I'm going to argue some of your points anyway.
What happens, however, if a user turns his PC off with out shutting it down - It happens, especially when they want to get out of the office as fast as possible on a Friday evening. Chances are that Linux will not boot up again, /dev/hda2
was not cleanly unmounted, cannot find superblock, kernel panic etc... Windows 95 can recover quite easily from bad
shutdowns, Linux can't... I'm sure some smart-alec will come along and mention some configuration change that
makes Linux more robust with regard to unclean shutdowns
In fact, you can get rid of the fscking altogether if you use journalling filesystems like reiserfs or ext3.
TCO lower? - I'm the only local IT person in my company who even uses Linux. The only difference of TCO with Linux and MS is the client cost, less than $100 - which is an insignificant amount, when looking at total support costs, and Linux has significantly higher support costs.
Depends on the size of your network. If you have 10000 workstations, all clones of each other booting off a network server, the TCO will definitely be lower, because your support people will only have to fix problems once. However, if you only have 10-100 workstations, it might not be worth it.
Uptime - Are you secretly trying to agree with me here? Uptime is not a desktop client feature - it is a server feature. Nearly all desktop clients get rebooted daily.
Yes, but the *reason* OSes have bad uptime is because they *crash*. Crashing, AFAIK, is the number one problem users have with Microsoft products. Ever overheard a complaint about a computer? It's almost never about something that is a consistent problem with their computer; it's usually about how "I was just using it and suddenly it froze". Although 200-day uptimes aren't necessary, the point is that Linux won't just up and crash for no reason.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Designing code is easy? I beg to differ. True, it's easy to write code, but designing it is another matter.
For instance, many algorithms can be written either as a 100-line piece of deeply-nested looping code, or as a single, simple, mathematical formula. Many people will find all sorts of different ways of writing the 100 lines, but few will see the simple math formula that will do the job a dozen times more quickly.
Those guys that say "I don't code anymore" spend their days coming up with the ways of making sure those 100000 lines of code never exist in the first place. I have more respect for those guys than the people who write code that simply works.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Better to listen to him than to listen to an AC who isn't even a "division manager for an IT company".
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
If Netware 3.11 was perfect software, then everybody would be installing it.
<P>"Perfect" in this context means it does what it's supposed to do, and does it well. People won't buy Novell 3.11 when most of their network is TCP/IP. But they'll never consider "upgrading" their software, because it does what it is supposed to do, and does it well.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
If Netware 3.11 was perfect software, then everybody would be installing it.
<P>"Perfect" in this context means it does what it's supposed to do, and does it well. People won't buy Novell 3.11 when most of their network is TCP/IP. But they'll never consider "upgrading" their software, because it does what it is supposed to do, and does it well.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Not everyone purchases licenses for the newest version of NetWare. My school uses Netware 3.x, for instance. What's the cost for legacy versions of NetWare?
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
No, it places large restrictions on potential *distributors* (mainly those who don't want to distribute to others what they've been distributed to).
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
What we need to do is not increase the number of things that are illegal, but increase the PENALTY for doing those things. Too often, a person gets a "3 year sentence", but gets out in 6 months. (Or a "Life sentence" and gets out in 10-15 years.)
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
But they do anyway.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Careful: you are legally responsible for everything your barney does.
"Barney has performed an illegal operation and will be shut down."
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Take a look at apt-zip.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Actually, it should be "KDE/Linux". Think division; It's pronounced "KDE over Linux" or "KDE on top of Linux".
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
And, simplified, it would be
GNU/LinuxKDE
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
You should have said "Yes! I'll do it," then waited a day, then said "here you are, now where's my vouchers?" :-)
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Then get Debian. Two commands run as root:
apt-get update
apt-get install task-kde
That downloads and installs all the KDE packages. If you managed to install the OS, you'll be able to do this.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Personally, I always want a static IP. I realize that DHCP provides no real protection against cracks.
What's something that we can push to the general e-populace to make them want static IPs?
$200 mini-webservers? $100 firewall devices?
Post your suggestions here.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
I'm going to bitch about that stupid tag handling. I chose "Extrans", dammit!!
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
I'm not saying RMS is the person I'd want in charge. I'm saying he's a good, predictable, figurehead. Even the most zealous of free software fanatics can look up to him.
<I>Yeah, well, think "The Crusades".</I>
And this helps your argument how?
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.