...he is getting at. The OS could be changed to compromise the organizations security - at a much more fundamental level than merely playing with password files and tweaking file permissions. Who knows what type of damage a malicous kernel hacker on the payroll could do. Well, *I* do!
Of course, this type of sabatoge is easily countered.... if it is thought about when designing the system.
Agree - there are more mature systems out there that beat out Linux (most of which cost more than a few dollars), but for this grad satudent, I'll stick with Linux and BSD every time.... unless of course someone else is footing the bill... or is it footing Bill?
...based on any PKI, watermark, what have you, I can break in 5 seconds: in the time it takes me to run a lead from my speaker jack to my microphone. But hey, atleast they will learn a lot while trying.:-)
...would be even coller if they included more keyboard shortcuts.
Not all of us are mousers.
While reading the article I noted that the word "Linux" had a registered trade mark adornment. When did this happen, and who registered the trademark? Being a FreeBSD weenie I am somewhoat out of touch with whatever direction the Linux crowd is taking (for this week anyway).
"...one's marketability is highest right after college and decreases geometrically thereafter..."
At 33, with my masters and 12 years of experience, I will take on ANY recent college grad interms of technical ability, all around knowledge, and I'll play paycheck poker with them. I'll win on all fronts.
Don't fool yourself kid - the only reason you'll ever be chosen over a more experienced (read: older) coder is because you are cheaper.
I wonder.... how many people will take the time to realize that it was a bunch of BSD hackers who implemented this hole, and not engineers at Microsoft?
Flamers... funny how you'll never meet one in person. They are oh so safe behind their keyboards, snug in the knowledge that that will not get a black eye for their efforts.
Pittsburgh doesn't have a very large tech community. It also has a very limited night life. It is far from any beaches, the skiing is mediocre, and it rains so much there! There are a fair amount of attractive women there, but that is true of anywhere except Cleveland. (I am from D.C. BTW).
That is a bunch of *crap*. I have been programming MS Windows for about 8 years now -- well before the days of the ubiquitous wizards. Additionally I have programmed professionally in the X Window (Motif and Xlib) environment. I will tell you that the basic skill set required is the same no matter what platform you develop for. Coders that suck in X suck in Windows.
I agree that there are lots of MFC programmers out there who don't know jack about the underlying API, but the same can be said about lots of Motif developers.
One thing is for sure, the MS Windows based (MS, Borland, Symantec, et al) development tools are far and away superior to the UNIX based tools out there (and they don't cost $$thousands per seat).
I also note the KDE project is doing it damnedest to emulate the functionality of Windows -- like it or not, Microsoft's development model will be around for years to come.
Slashdot Mirror
...he is getting at. The OS could be changed to compromise the organizations security - at a much more fundamental level than merely playing with password files and tweaking file permissions. Who knows what type of damage a malicous kernel hacker on the payroll could do. Well, *I* do!
Of course, this type of sabatoge is easily countered.... if it is thought about when designing the system.
Agree - there are more mature systems out there that beat out Linux (most of which cost more than a few dollars), but for this grad satudent, I'll stick with Linux and BSD every time.... unless of course someone else is footing the bill... or is it footing Bill?
...it is about serious, stable computing.
If I want a bunch of pretty flashing lights, then sure, M$ is the answer.
If I want scalability and power, then Linux is the answer.
If I want MORE power and stability.... it is time to download the lastest FreeBSD....
...based on any PKI, watermark, what have you, I can break in 5 seconds: in the time it takes me to run a lead from my speaker jack to my microphone. But hey, atleast they will learn a lot while trying. :-)
As far as writing a distributed kernel, I really don't see what the point would be, esp if we are talking microkernel.
Perhaps a distributed module layer, or distributed device drivers would be something to think about, but there are performance considerations.
Maybe distibuted plug-and-play: you install some hardware, the kernel detects it, and goes out and retrieves the latest driver for it.
I really like it (KDE). I hope they keep up the good work.
I like the work going on with GNOME as well, but it will never replace KDE in my heart.
No the mouse isn't broken. ;-)
I find it easier and faster to use keystrokes (where available). This really only applies to Window$ (my employer ia all NT)
...would be even coller if they included more keyboard shortcuts.
Not all of us are mousers.
While reading the article I noted that the word "Linux" had a registered trade mark adornment. When did this happen, and who registered the trademark? Being a FreeBSD weenie I am somewhoat out of touch with whatever direction the Linux crowd is taking (for this week anyway).
"...one's marketability is highest right after college and decreases geometrically thereafter..."
At 33, with my masters and 12 years of experience, I will take on ANY recent college grad interms of technical ability, all around knowledge, and I'll play paycheck poker with them. I'll win on all fronts.
Don't fool yourself kid - the only reason you'll ever be chosen over a more experienced (read: older) coder is because you are cheaper.
I wonder.... how many people will take the time to realize that it was a bunch of BSD hackers who implemented this hole, and not engineers at Microsoft?
Most "code monkeys" can't balance their checkbooks, much less run the business that provides them with their paycheck.
...engine altogether? Come on already! This is 19th century technology here - we can do much better than that!
...is what is really lacking. This is where ALL of the Unicies (free or otherwise) fall flat.
Flamers... funny how you'll never meet one in person. They are oh so safe behind their keyboards, snug in the knowledge that that will not get a black eye for their efforts.
Pittsburgh doesn't have a very large tech community. It also has a very limited night life. It is far from any beaches, the skiing is mediocre, and it rains so much there! There are a fair amount of attractive women there, but that is true of anywhere except Cleveland. (I am from D.C. BTW).
That is a bunch of *crap*. I have been programming MS Windows for about 8 years now -- well before the days of the ubiquitous wizards. Additionally I have programmed professionally in the X Window (Motif and Xlib) environment. I will tell you that the basic skill set required is the same no matter what platform you develop for. Coders that suck in X suck in Windows.
I agree that there are lots of MFC programmers out there who don't know jack about the underlying API, but the same can be said about lots of Motif developers.
One thing is for sure, the MS Windows based (MS, Borland, Symantec, et al) development tools are far and away superior to the UNIX based tools out there (and they don't cost $$thousands per seat).
I also note the KDE project is doing it damnedest to emulate the functionality of Windows -- like it or not, Microsoft's development model will be around for years to come.