would not be surprised that they are costing most companies more money over time then a virus running rampart in their network...
Could be true. But I would prefer the occasional problem with the virusscanner (on server or workstation), than one virus running wild over a network without protection.
I don't want to start a war about "what distro is better", but have a look at http://www.novell.com/linux/suse/. their distro was designed to operate in a novell environment.
A couple of weeks ago I did the (adv.) Netware 6.5 training. The (2) other guys were mcse and everything. they did the training because their company was moving from NT4 and W2000 to Windows2003, with Novell E-directory. At first I could not believe this, because it defies market trends. Their decision was based on scalability and performance, and E-directory outperforms AD on both accounts. So we're talking about an all-microsoft shop, that is using E-directory instead of AD. They do exist. The teacher told me that it is quite common for companies to use Microsoft servers with Novell E-directory instead of AD. But still, I'm gonna keep my linux skills up-to date.
the business world loves to make money. if hipness is involved or required, so be it. companies use linux because of the commercial advantages it offers.
Open standards have been the driving force behind the development of the PC. The only reason for closed standards is so that somebody can make money with them.
I think that there is another point to be made here. The lady is not able to use a keyboard, and speech is problematic. This situation will not get better. So do not focus on the technology she cannot use, but look elswhere for the solution. Perheps the best way to help her (in more than one way) is by having somebody else type the messages for her. Perhaps a nice voluntary job for the poster? Yes, this will cost time, and no, this problem cannot be bought off by installing some gizmo. If you want to help her, invest time.
You could be right. Another possibility: the nic-drivers. Excuse me for asking, but did you check things like network speed and duplex-settings? there might be a difference after operating system installs. my point was that if you use a sniffer you can see the communication on the network itself and where and why it fails. that's more informative than staring at kernels.
i can't understand why you would want to use a kernel debugger to troubleshoot network problems. Wouldn't a sniffer be a better idea? That way you can check out what's happening on the network level, where the problem seems to be.
Slashdot Mirror
Maybe they set up a honeypot? You know, the one that doesn't give actual information, but just logs all requests.
I think that "professionals" is spelled with one "f".
working day of 35 hour
Pussies! Working more that 24 hours a day hasn't killed anyone!
would not be surprised that they are costing most companies more money over time then a virus running rampart in their network...
Could be true. But I would prefer the occasional problem with the virusscanner (on server or workstation), than one virus running wild over a network without protection.
Your post dropped 5 points? What post are you referring to?
and put the toilet under the shower.
Tao te King. This is the book that Sun Tzu used when writing "The Art of War".
Ever heard of embedded windows? Thought so.
This guy is an expert in network management. His site contains lots of useful tips.
I don't want to start a war about "what distro is better", but have a look at http://www.novell.com/linux/suse/. their distro was designed to operate in a novell environment.
A couple of weeks ago I did the (adv.) Netware 6.5 training. The (2) other guys were mcse and everything. they did the training because their company was moving from NT4 and W2000 to Windows2003, with Novell E-directory. At first I could not believe this, because it defies market trends. Their decision was based on scalability and performance, and E-directory outperforms AD on both accounts. So we're talking about an all-microsoft shop, that is using E-directory instead of AD. They do exist. The teacher told me that it is quite common for companies to use Microsoft servers with Novell E-directory instead of AD. But still, I'm gonna keep my linux skills up-to date.
Was your software up-to-date at that time? If not, it's your own fault.
he is called Mantovani.
http://ktoon.toonka.com/
the business world loves to make money. if hipness is involved or required, so be it. companies use linux because of the commercial advantages it offers.
i would love to spote a problem, but i do not konw how.
Open standards have been the driving force behind the development of the PC. The only reason for closed standards is so that somebody can make money with them.
Silly question! Since you cannot see them, you cannot see what color they are.
They invented Intellectual Property Rights and sued each other to oblivion?
You are not the only one who doen'ts know the difference between a comma and a point.
oh come on, this is /. , home of old news. the dupe of this article is planned for aug. 19, 2015.
I think that there is another point to be made here. The lady is not able to use a keyboard, and speech is problematic. This situation will not get better. So do not focus on the technology she cannot use, but look elswhere for the solution. Perheps the best way to help her (in more than one way) is by having somebody else type the messages for her. Perhaps a nice voluntary job for the poster? Yes, this will cost time, and no, this problem cannot be bought off by installing some gizmo. If you want to help her, invest time.
does it run linux?
You could be right. Another possibility: the nic-drivers. Excuse me for asking, but did you check things like network speed and duplex-settings? there might be a difference after operating system installs.
my point was that if you use a sniffer you can see the communication on the network itself and where and why it fails. that's more informative than staring at kernels.
i can't understand why you would want to use a kernel debugger to troubleshoot network problems. Wouldn't a sniffer be a better idea? That way you can check out what's happening on the network level, where the problem seems to be.