Max Cleland did not lose his limbs in a combat action. Go read what he was doing when the grenade exploded.
So what if it was the result of enemy action or an accident? It was still in the field during a war, and it certainly doesn't invalidate the Bronze and Silver Stars he earned in Khe Sanh.
You really know how to make yourself look like a jackass, don't you?
I'm just starting to learn Chinese, and I use Linux exclusively. What do you recomend for chinese input on linux? One of my class assignments will require that I create a powerpoint presentation in chinese, which I'm hoping I can do in OOo, but I haven't yet figured out how to input stuff.
Do you honestly think that a small firm can afford to put someone in a position for which they are not qualified?
What does "being able to afford it" have to do with nepotism? It happens all the time. Yes, in small companies. Maybe you've been lucky enough not to run into it, but it's far more common in small companies than in large ones.
Your consent is ABSOLUTELY required. The reason is because every credit check performed on/against you has a small negative effect on your credit score.
Yeah, that's what he said, you could get a program made that would convert your image files to that format. If you shopped your local university for talent, you could probably find someone who would do it for much less than $1000.
I have another alternative for you: Hunt down some officers of the company and find out who owns the rights to the software (somebody does, they don't just disappear). Maybe they can give you a crack for it, or suggest a reputable dealer you can get it from. Or maybe they can give you a code that will make the dongle happy again (same thing, really). Or maybe you can get a bunch of other people who are in the same boat as you to band together and buy the source code, sort of like the Blender project did.
Dude, you should maybe try reading what I actually wrote. Did I say link to object data? No. I said link to CODE. Like, for example, it seems perfectly reasonable that cdrecord might need direct access to device buffers, and it might need to interface with the kernel to acquire that access, and that might bring about a situation where the conflicts between CDDL and GPL are a concern (I don't believe it does, but it wouldn't be a totally unreasonable design choice if one were only concerned with providing cdr support for Linux, which I'm well aware is not the case here).
I can't think of any reason why Apache would need to interface with the kernel so intimately, so the situations aren't comparable.
Of course the situations aren't comparable in another way: Apache, in it's entirety, is under the Apache license. Cdrtools, OTOH, is now a mixture of CDDL and GPL, which is to say that it's much worse than the scenario I was envisioning; it's actually in license conflict with itself!
I'm not saying every transaction has to be verified, I'm saying things should maybe be a bit more compartmentalized so when, for example, there's a buffer overflow on your network card it doesn't take down the whole system.
Your video example is pretty contrived, but you had no way of knowing that I spent 2 years repairing video servers at Grass Valley Group. And actually, the way the Profile works is a perfect illustration of my point. The user interface is some flavor NT (3.1, 4, or 2k, depending on age) running on a COTS PC card, but it's seperated from the video system. I saw several situations where Windows was hosed, even BSODed, but the video kept rolling (albeit with a potential loss of human control). Of course, it doesn't use ethernet for transfering video generally, it uses dedicated fibrechannel or one of the standard video distribution methods, like SDI.
The only time I ever saw gigabit used for video transfer was with the M-Series, and honestly there was no discernable difference from standard 100b ethernet, even over short distances with no cross traffic. But then you're really limited by the PCI bus, which is barely up to the task of saturating a 100b connection anyway. IMO, a post house that's using gig-e for video transfer is using low-end equipment anyway, and not likely to be serving the kind of customers who can afford to pay for "right here, right now" speeds. And that's fine, not everyone needs or even wants to deal with a technicolor level post house.
Can you give me a good reason why a network driver absolutely has to have enough low level access that it can hijack the system? If not, then I still call that arguement a strawman. Just because everyone does it that way doesn't mean it's the right way to do it.
True, it is a possibility. However, on the other side my old Dell laptop had bad drivers that came standard. They kept performing illegal operations (and blue-screening) Windows 2000. When I found updated drivers, the illegal operations went away.
That doesn't mean it was the fault of the driver manufacturer. Maybe they had to do some non-standard stuff in order to make win2k behave properly? You don't know that isn't the case.
This highlights the problem I've spent most of my other posts to this article discussing: even if it is a bad driver, it's still the OS's fault for letting the driver take the whole system down, so it's still the OS writer's problem.
Yes, there are some situations where this isn't true: if your northbridge stops functioning, for whatever reason, you're hosed. But there should be no way that a non-critical piece of hardware, like a soundcard or network card, can crash the system, and that goes double for a USB peripheral. If it can, then you've found a flaw in the OS, regardless of how bad the driver might be.
And everything that's going to be discovered in physics already has been.
And there's no reason an average consumer could possibly want a computer in their home.
And...
So basically you're saying we should limit ourselves to only what small-minded individuals can concieve of, and we should expect no better from the tools that are available to us?
No matter what, it IS an OSX issue. OSX is allowing a USB network adapter to be used to hijack the system, and this points to a fundamental flaw in their security. There may also be some blame for the writer of the drivers, but from Apple's standpoint that should be a side issue.
Maybe because former employers are more likely to have an axe to grind?
That's one way to look at it. My own experience is that it's far more likely the former employee simply no longer has a vested interest in hiding the ugly truth about their former employer's methods, motivations, or prectices.
I'm much more inclined to believe a former employee than a current one.
Now, I'm just taking a stab in the dark here, but it seems to me that cdrtools requires much lower-level system access than Apache does, and therefore runs a higher risk of needing to link against GPL code, and thus create an ACTUAL license conflict. Two packages with incompatible licenses can be distributed together, the problems occur when one links against the other.
Who cares where the problem originates? If a USB network adapter allows someone to hijack your macbook, it IS and OSX problem, regardless of where it originates.
A secure system cannot be so trusting of third party drivers as to allow that kind of access to the system. If you're going for security, you have to assume anything you don't have direct control over is wrong and bad, and you have to account for that. Anything else is worse than a bug: it's a serious design flaw.
- how can a driver have the same bug on windows and macos x?
Perhaps both drivers are derivd from the same codebase? Or perhaps the developers of both drivers made the same faulty assumtion that leads to this bug?
- This guy did overrate some minor problem in a misleading way for Apple laptops. Oh.. a third party driver with a bug. Or it's Apple driver with only a thirdparty card. In that case, he's discredited in the domain of security for the rest of his life.
What if the third-party driver is behaving exactly as it's supposed to, per the API, and the problem is actually in the OS itself? I mean, seriously: how else does a network card exploit crash the system?
- and odds are the bug is a buffer overrun... does it take a SO LONG for apple to fix a stupid memory overrun?
You really have no idea what you're talking about, do you?
Seems to me it would open the state up to serious libel cases. I mean, being put on this list could easily ompletely destroy someones life and livelyhood.
Maybe you have multiple computers in your house, and maybe you have multiple users as well. Wouldn't it be nice if any given user could log on to any given computer and have their environment be the same without having to go through the pain of configuring it on every machine, and have access to all their files without having to remember which machine those files are stored on?
There are men out there who have mastery over their biology.
Generally it comes with age. Some never have the desire to learn it, of course, just as some never have the desire to learn how to read or practise basic hygene. By age, by the way, I mean 30+, and really by that point we mostly just learn to be more subtle about it.
As for manner of dress, I never knew slacks and a loose fitting blouse or a knee length skirt, blazer and shell could be erotic.
Maybe, maybe not. It depends on how they hang on you, or the material they're made of (many loose fitting articles are made of light fabrics that can be seen through at certain angles, for example). Or maybe it has more to do with your attitude, how you carry yourself, the personality you project.
Or, what sesms more likely after reading a few of your posts, you're stuck in the knee-jerk, male-bashing feminist mindset that became so popular in the late 70's/early 80's, and assume these things in the absence of direct, compelling (and unreasonably expected) evidence to the contrary. In other words, you've made it quite clear that all men, in your eyes, are guilty until proven innocent.
I wouldn't bring cookies, unless you happen to have a big pile of cookies lying around that you need to get rid of, but that's a different situation.
Another respondant mentioned birthday parties. One thing I've noticed is that these parties only happen in departments that have women in them, which strongly suggests that it is women who make them happen (departments that are majority female even have spontaneous potlucks, apparently). If you're the only woman, you're it. What the other post said about these events is spot on, and is the avenue I would suggest.
The thing about joining in the jokes is also true. I worked with a woman once who, in a department meeting where our supervisor was obligated to remind us of the dangers of sexual harassment, and avenues of recourse, because of some silly situation in another department, responded with, "But what if I like it?" Needless to say, she was not an outsider. This one doesn't work for everyone, obviously, and you may not want to be "one of the guys" to that extent anyway.
I don't know much about cygwin, I installed it once years ago and wasn't able to do much of interest with it. Basically, it came down to a culture clash. One of the reasons the *nix CLI is so powerful is that everything is configured via text files, and all data is passed as text, which means you can do all kinds of nifty things with automatable text editing tools like sed. Things aren't done that way in Windows; things there are almost always some proprietary binary format, so you're never going to achieve the same kind of flexibility on a Windows system, no matter what tools you install.
That said, in most *nix systems the basic setup for each user is found in/etc/passwd, where each user has one line consisting of fields seperated by ':', and the user's home directory is set in the 6th field (at least in Linux, but it should be obvious when you look at it). So, you could edit that file (assuming it exists in cygwin) to change you're home to C:\. Alternatively, when a user logs in *nix looks for/home/user/.profile, which is where all the user's environment stuff is set, such as $PATH. You could probably put a line in there that would cd you to C:\.
Also, you make a good point about people who are obsessed with scripting. I do plenty of 1 or 2 line scripts though, usually because it's a command string that's complex enough that I know I'll never be able to remember it, and would probably spend far to long going through man files to reconstruct it on the once-a-month-or-so occasions when I'll need it.
Don't extrapolate your experience with Gnome to KDE. They are very different. If I used Gnome I would certainly feel, as you do, that Linux GUIs are primitive and clunky. However, I suggest that you spend some time with KDE. IMO it kicks the crap out of Windows Explorer any day of the week, and twice on Sundays, while beating down MacOS with it's other hand. Konqueror is what all file browsers should aspire to be (splitable windows, optional inset terminal, tabs).
And don't be so quick to dismiss that "simple" search crap that you can do on Linux but not in Windows. Window's pattern matching is pathetic. Yeah, you might be able to find a file that you can't remember the exact name of, but that's really of only minimal utility. On a *nix CLI, search is an actual tool that one uses to get stuff done. For example, maybe I want to change an IP address in every file that has the string "host" in the name; I can search the system for all files having names which fit that pattern and pipe that list to a stream editor which will find each instance of the old IP address and replace it with the new one, without me having to browse to, open, or otherwise have to deal with any of those files on my own.
And while we're on the subject, let me just say that the *nix pipe is about the most wonderful thing ever invented, better even than regexps, and unless something has drastically changed in the Windows world in the last few years, you'll find nothing at all like it there.
That's why your former mentor wanted you to learn scripting: because you can use it to automate menial, but time consuming, sysadmin tasks, and save yourself a lot of time.
Slashdot Mirror
Max Cleland did not lose his limbs in a combat action. Go read what he was doing when the grenade exploded.
So what if it was the result of enemy action or an accident? It was still in the field during a war, and it certainly doesn't invalidate the Bronze and Silver Stars he earned in Khe Sanh.
You really know how to make yourself look like a jackass, don't you?
I'm just starting to learn Chinese, and I use Linux exclusively. What do you recomend for chinese input on linux? One of my class assignments will require that I create a powerpoint presentation in chinese, which I'm hoping I can do in OOo, but I haven't yet figured out how to input stuff.
Do you honestly think that a small firm can afford to put someone in a position for which they are not qualified?
What does "being able to afford it" have to do with nepotism? It happens all the time. Yes, in small companies. Maybe you've been lucky enough not to run into it, but it's far more common in small companies than in large ones.
Your consent is ABSOLUTELY required. The reason is because every credit check performed on/against you has a small negative effect on your credit score.
It's the program I need, not the files.
Yeah, that's what he said, you could get a program made that would convert your image files to that format. If you shopped your local university for talent, you could probably find someone who would do it for much less than $1000.
I have another alternative for you: Hunt down some officers of the company and find out who owns the rights to the software (somebody does, they don't just disappear). Maybe they can give you a crack for it, or suggest a reputable dealer you can get it from. Or maybe they can give you a code that will make the dongle happy again (same thing, really). Or maybe you can get a bunch of other people who are in the same boat as you to band together and buy the source code, sort of like the Blender project did.
Dude, you should maybe try reading what I actually wrote. Did I say link to object data? No. I said link to CODE . Like, for example, it seems perfectly reasonable that cdrecord might need direct access to device buffers, and it might need to interface with the kernel to acquire that access, and that might bring about a situation where the conflicts between CDDL and GPL are a concern (I don't believe it does, but it wouldn't be a totally unreasonable design choice if one were only concerned with providing cdr support for Linux, which I'm well aware is not the case here).
I can't think of any reason why Apache would need to interface with the kernel so intimately, so the situations aren't comparable.
Of course the situations aren't comparable in another way: Apache, in it's entirety, is under the Apache license. Cdrtools, OTOH, is now a mixture of CDDL and GPL, which is to say that it's much worse than the scenario I was envisioning; it's actually in license conflict with itself!
I'm not saying every transaction has to be verified, I'm saying things should maybe be a bit more compartmentalized so when, for example, there's a buffer overflow on your network card it doesn't take down the whole system.
Your video example is pretty contrived, but you had no way of knowing that I spent 2 years repairing video servers at Grass Valley Group. And actually, the way the Profile works is a perfect illustration of my point. The user interface is some flavor NT (3.1, 4, or 2k, depending on age) running on a COTS PC card, but it's seperated from the video system. I saw several situations where Windows was hosed, even BSODed, but the video kept rolling (albeit with a potential loss of human control). Of course, it doesn't use ethernet for transfering video generally, it uses dedicated fibrechannel or one of the standard video distribution methods, like SDI.
The only time I ever saw gigabit used for video transfer was with the M-Series, and honestly there was no discernable difference from standard 100b ethernet, even over short distances with no cross traffic. But then you're really limited by the PCI bus, which is barely up to the task of saturating a 100b connection anyway. IMO, a post house that's using gig-e for video transfer is using low-end equipment anyway, and not likely to be serving the kind of customers who can afford to pay for "right here, right now" speeds. And that's fine, not everyone needs or even wants to deal with a technicolor level post house.
Quite high, thank you, largely due to the fact that I'm able to take in the entire arguement rather than focusing on pedantic details.
Can you give me a good reason why a network driver absolutely has to have enough low level access that it can hijack the system? If not, then I still call that arguement a strawman. Just because everyone does it that way doesn't mean it's the right way to do it.
True, it is a possibility. However, on the other side my old Dell laptop had bad drivers that came standard. They kept performing illegal operations (and blue-screening) Windows 2000. When I found updated drivers, the illegal operations went away.
That doesn't mean it was the fault of the driver manufacturer. Maybe they had to do some non-standard stuff in order to make win2k behave properly? You don't know that isn't the case.
This highlights the problem I've spent most of my other posts to this article discussing: even if it is a bad driver, it's still the OS's fault for letting the driver take the whole system down, so it's still the OS writer's problem.
Yes, there are some situations where this isn't true: if your northbridge stops functioning, for whatever reason, you're hosed. But there should be no way that a non-critical piece of hardware, like a soundcard or network card, can crash the system, and that goes double for a USB peripheral. If it can, then you've found a flaw in the OS, regardless of how bad the driver might be.
You got poor marks in reading comprehension in school, didn't you?
Nowhere did I assert that his hack works. That's what the "if" in that statement means. Here, let me highlight it for you in case you missed it:
" If his hack works, it works."
What I did assert is that his status as an Apple-hater has no bearing on the effectiveness of his hack.
Nice strawman.
The numerical superiority of flawed implementations does not magically make this one unflawed.
Uh-huh.
And everything that's going to be discovered in physics already has been.
And there's no reason an average consumer could possibly want a computer in their home.
And...
So basically you're saying we should limit ourselves to only what small-minded individuals can concieve of, and we should expect no better from the tools that are available to us?
No matter what, it IS an OSX issue. OSX is allowing a USB network adapter to be used to hijack the system, and this points to a fundamental flaw in their security. There may also be some blame for the writer of the drivers, but from Apple's standpoint that should be a side issue.
Maybe because former employers are more likely to have an axe to grind?
That's one way to look at it. My own experience is that it's far more likely the former employee simply no longer has a vested interest in hiding the ugly truth about their former employer's methods, motivations, or prectices.
I'm much more inclined to believe a former employee than a current one.
I remember those days too. It meant I had nothing, because I couldn't get xcdroast to work.
Of course, I was less technically competent in those days than I am now, but I'm not sure how much of a difference that made.
Now, I'm just taking a stab in the dark here, but it seems to me that cdrtools requires much lower-level system access than Apache does, and therefore runs a higher risk of needing to link against GPL code, and thus create an ACTUAL license conflict. Two packages with incompatible licenses can be distributed together, the problems occur when one links against the other.
Who cares where the problem originates? If a USB network adapter allows someone to hijack your macbook, it IS and OSX problem, regardless of where it originates.
A secure system cannot be so trusting of third party drivers as to allow that kind of access to the system. If you're going for security, you have to assume anything you don't have direct control over is wrong and bad, and you have to account for that. Anything else is worse than a bug: it's a serious design flaw.
- how can a driver have the same bug on windows and macos x?
Perhaps both drivers are derivd from the same codebase? Or perhaps the developers of both drivers made the same faulty assumtion that leads to this bug?
- This guy did overrate some minor problem in a misleading way for Apple laptops. Oh.. a third party driver with a bug. Or it's Apple driver with only a thirdparty card. In that case, he's discredited in the domain of security for the rest of his life.
What if the third-party driver is behaving exactly as it's supposed to, per the API, and the problem is actually in the OS itself? I mean, seriously: how else does a network card exploit crash the system?
- and odds are the bug is a buffer overrun... does it take a SO LONG for apple to fix a stupid memory overrun?
You really have no idea what you're talking about, do you?
So what if he is? If his hack works, it works. Period.
An attack on his personality doesn't invalidate that.
Seems to me it would open the state up to serious libel cases. I mean, being put on this list could easily ompletely destroy someones life and livelyhood.
Maybe you have multiple computers in your house, and maybe you have multiple users as well. Wouldn't it be nice if any given user could log on to any given computer and have their environment be the same without having to go through the pain of configuring it on every machine, and have access to all their files without having to remember which machine those files are stored on?
There are men out there who have mastery over their biology.
Generally it comes with age. Some never have the desire to learn it, of course, just as some never have the desire to learn how to read or practise basic hygene. By age, by the way, I mean 30+, and really by that point we mostly just learn to be more subtle about it.
As for manner of dress, I never knew slacks and a loose fitting blouse or a knee length skirt, blazer and shell could be erotic.
Maybe, maybe not. It depends on how they hang on you, or the material they're made of (many loose fitting articles are made of light fabrics that can be seen through at certain angles, for example). Or maybe it has more to do with your attitude, how you carry yourself, the personality you project.
Or, what sesms more likely after reading a few of your posts, you're stuck in the knee-jerk, male-bashing feminist mindset that became so popular in the late 70's/early 80's, and assume these things in the absence of direct, compelling (and unreasonably expected) evidence to the contrary. In other words, you've made it quite clear that all men, in your eyes, are guilty until proven innocent.
I wouldn't bring cookies, unless you happen to have a big pile of cookies lying around that you need to get rid of, but that's a different situation.
Another respondant mentioned birthday parties. One thing I've noticed is that these parties only happen in departments that have women in them, which strongly suggests that it is women who make them happen (departments that are majority female even have spontaneous potlucks, apparently). If you're the only woman, you're it. What the other post said about these events is spot on, and is the avenue I would suggest.
The thing about joining in the jokes is also true. I worked with a woman once who, in a department meeting where our supervisor was obligated to remind us of the dangers of sexual harassment, and avenues of recourse, because of some silly situation in another department, responded with, "But what if I like it?" Needless to say, she was not an outsider. This one doesn't work for everyone, obviously, and you may not want to be "one of the guys" to that extent anyway.
I don't know much about cygwin, I installed it once years ago and wasn't able to do much of interest with it. Basically, it came down to a culture clash. One of the reasons the *nix CLI is so powerful is that everything is configured via text files, and all data is passed as text, which means you can do all kinds of nifty things with automatable text editing tools like sed. Things aren't done that way in Windows; things there are almost always some proprietary binary format, so you're never going to achieve the same kind of flexibility on a Windows system, no matter what tools you install.
/etc/passwd, where each user has one line consisting of fields seperated by ':', and the user's home directory is set in the 6th field (at least in Linux, but it should be obvious when you look at it). So, you could edit that file (assuming it exists in cygwin) to change you're home to C:\. Alternatively, when a user logs in *nix looks for /home/user/.profile, which is where all the user's environment stuff is set, such as $PATH. You could probably put a line in there that would cd you to C:\.
That said, in most *nix systems the basic setup for each user is found in
Also, you make a good point about people who are obsessed with scripting. I do plenty of 1 or 2 line scripts though, usually because it's a command string that's complex enough that I know I'll never be able to remember it, and would probably spend far to long going through man files to reconstruct it on the once-a-month-or-so occasions when I'll need it.
Don't extrapolate your experience with Gnome to KDE. They are very different. If I used Gnome I would certainly feel, as you do, that Linux GUIs are primitive and clunky. However, I suggest that you spend some time with KDE. IMO it kicks the crap out of Windows Explorer any day of the week, and twice on Sundays, while beating down MacOS with it's other hand. Konqueror is what all file browsers should aspire to be (splitable windows, optional inset terminal, tabs).
And don't be so quick to dismiss that "simple" search crap that you can do on Linux but not in Windows. Window's pattern matching is pathetic. Yeah, you might be able to find a file that you can't remember the exact name of, but that's really of only minimal utility. On a *nix CLI, search is an actual tool that one uses to get stuff done. For example, maybe I want to change an IP address in every file that has the string "host" in the name; I can search the system for all files having names which fit that pattern and pipe that list to a stream editor which will find each instance of the old IP address and replace it with the new one, without me having to browse to, open, or otherwise have to deal with any of those files on my own.
And while we're on the subject, let me just say that the *nix pipe is about the most wonderful thing ever invented, better even than regexps, and unless something has drastically changed in the Windows world in the last few years, you'll find nothing at all like it there.
That's why your former mentor wanted you to learn scripting: because you can use it to automate menial, but time consuming, sysadmin tasks, and save yourself a lot of time.