Another garage product also fares badly on COUNT(*) however if you do COUNT() they both do real well. It has to do with the fact that when you do COUNT(*) you have to count every row and that takes a fair bit of time. When you do COUNT(key) you count rows in the index file and that is real quick:-)
Yeah, it has all I need (tabs, smart blocking etc) it's relatively lean. It has none of the bloat like semi-working mail etc. I did not even know Mozilla was up to 1.7!!
In my systems and my company CVS has long since been replaced with subversion. This is a OSS replacement that fixes CVS's shortcomings (such as atomic check in and directory versioning) It works real well, i'll never turn back.
I worked at a place where working more than 42 hours was a matter for the department director and more than 48 had to be approved by VP. Why? Because they had clear evidence that if you work more you produce shittier and shittier code, and that cost the company money. If there was some kind of situation that warranted OT they felt that the potential gain had to be weighed against the increased risk to the company and that descition was not to be taken by a lower manager. This company produced mission critical software, but the effects are just as valid for any company. It does cost money to fix bugs, and if you can avoid stupid bugs created just because you had to play macho and work lots of hours the company saves plenty money.
You are partially right. Having worked with unix for over 20 years I can assure you that originally/usr WAS short for user and that all user home directories were indeed in/usr. Unix originally shipped on two 1/2 inch tapes one was the root and the other one/usr with "userland" software. As Unix has grown over time user homedirs were moved to/home and/usr took a more general place and/usr has been officially re-identified as an acronym for Unix System Resources.
Having worked with unix for over 20 years I can assure you that originally/usr WAS short for user and that all user home directories were indeed in/usr. As a previous poster pointed out Unix shipped on two 1/2 inch tapes one was the root and the other one/usr with "userland" software. As Unix has grown over time user homedirs were moved to/home and/usr took a more general place and/usr was re-identified as an acronym for Unix System Resources.
What if your tag is broken? And you don't know for a week?
What if you forget your tag. Is it gonna be subdermal inplant. (now we're getting close to Third Reich)
It _will_ be misused by police. Robbery at a local store by a "teenager in a hood". All students out of school area at the time will be the suspects, while the real robber "tinfoiled" himself out and has a solid alibi...
Now these persons are used to beeing tagged, what's next (see Third Reich)
You cannot replace human interaction with students with computer checks.
No, I am unhappy because ~ 20 packages were (key word "examples" in my previous post...) installed despite my say so AND that responsible (?) parties claimed that this was desirable to protect me from myself. I say (w. 20 year experience) that it is far from desirable to run software to service non existent hardware... Yeah I run 2 distros. Mandrake because it installed easily on my old laptop and slack on everything else because it works. I might try SuSE as a replacement for Mandrake (or both). FC is just a bother and leaves me fixing more and more for each new "improved" release. So no thanx
A fancy-schmancy gooey during install may be nice or a BIG bother. The important is wether it works or not. I gave up on RH/FC with FC2. It insisted on installing and starting a whole bunch of shit that I explicitly unchecked. Examples:
install and start IR on an old server that neither has nor ever will have IR interface
install and start CUPS on a server that neither has nor will have access to a printer
The reason "it has to be installed to satisfy dependencies". In previous RH/FC you could ignore those dependencies in expert mode. Now I spent lotsa time turning of stuff that didn't do anything (I wonder WTF the IR daemon actually does on a server w/o IR card???) Now I use Mandrake/slackware. I might try the new SuSE...
I wholehartedly agree about finding ways to prevent bugs in the future. However, I strongly suggest that this is done mostly by how you work not what tool you use. Secure software is created by good design and good practice. Tools tends to create complacency and over-reliance on the tool (that tool may or may not be good enough...) You can safely hammer a nail with an axe if you are careful and pay attention and easily smash your hand to pieces with a good new hammer if you are careless.
In conclusion, yes you may improve your software with good tools but only if you are alreeady doing things "The Right Way"
How many of you can honestly say "I have never, ever ignored a return code"? How may of you can honestly say "I have never, ever created an interface without possibility to change expected behaviour"? How may of you can honestly say "I have never, ever made a mistake while coding or designing program logic and flow"?
If you answered "I can" to all three you are lying!
That is the essence of secure software. We all make mistakes, including seasoned, paranoid veterans as myself. Some of us less others more, noone make NO mistakes. The more complex a system is the greater the risk of a fatal mistake...
The only way to make secure software is;
good design practice.
good coding practice.
good testing practice.
a healthy dose of paranoia in your good practices.
teamwork with peer review.
a common realization that noone is perfect.
stop spreading blame and start fixing the problem.
As a matter of fact the article stated that some of OOo's advanced features did not degrade nicely in M$ Office... Yeah OOo is Good Enough(TM) whareas M$ Office might not be. And one of them costs $300 or so >-) My company uses strictly OOo, because of price and cross platform compatibility!
As a matter of fact I did not post any link, I just read the link and made conclusions from that and other sources. What is suggested (i.e not implemented) is that the network should be able to somehow limit demand by shutting down consumers based on some rules. Suggested was among other things air conditioning. I thought it was a rather clever idea, as I mentioned I'd rather have my A/C shut down than another big blackout. We are not there now though (and wount be any time soon)
You are correct. However, you can argue that the fault in the big blackout was not the failed powerlines in Ohio but the fact that that part of the grid was not disconnected. The fact that Ontario and New York was blacked out is an operational fault. The fact that parts of Ohio was blacked out was the result of mitigating a powerline fault and protecting generating plants. Other parts of Ohio was possibly blacked out by the same operational fault that blacked out Ontario.
Demand side management in this context means the grid has the ability to shutdown nonessential use PDQ to avoid poweroutage. If the alternative last August would be Ontario Hydro shutting of my A/C for an hour rather than having 26 hours without power including spoilt food, no A/C, no computers for my business, guess what my pick would be...
Disengaging generating capacity should be last resort not pretty much the only available tool to save the grid. Therefore it is in fact another fault.
He did not claim a $10 receipt, M$ offered him $10. He stated that he wanted to get paid for business cards advertising etc as well as the cost to reestablish himself under another domain. Could easily run up $10K
Slashdot Mirror
Noo, not on /.
I stand corrected! The problem may be corrected in versions newer than 8 of Oracle.
Oracle...
Another garage product also fares badly on COUNT(*) however if you do COUNT() they both do real well. It has to do with the fact that when you do COUNT(*) you have to count every row and that takes a fair bit of time. When you do COUNT(key) you count rows in the index file and that is real quick :-)
Yeah, it has all I need (tabs, smart blocking etc) it's relatively lean. It has none of the bloat like semi-working mail etc.
I did not even know Mozilla was up to 1.7!!
In my systems and my company CVS has long since been replaced with subversion. This is a OSS replacement that fixes CVS's shortcomings (such as atomic check in and directory versioning) It works real well, i'll never turn back.
I worked at a place where working more than 42 hours was a matter for the department director and more than 48 had to be approved by VP. Why? Because they had clear evidence that if you work more you produce shittier and shittier code, and that cost the company money. If there was some kind of situation that warranted OT they felt that the potential gain had to be weighed against the increased risk to the company and that descition was not to be taken by a lower manager.
This company produced mission critical software, but the effects are just as valid for any company. It does cost money to fix bugs, and if you can avoid stupid bugs created just because you had to play macho and work lots of hours the company saves plenty money.
You are partially right. Having worked with unix for over 20 years I can assure you that originally /usr WAS short for user and that all user home directories were indeed in /usr. Unix originally shipped on two 1/2 inch tapes one was the root and the other one /usr with "userland" software. /home and /usr took a more general place and /usr has been officially re-identified as an acronym for Unix System Resources.
As Unix has grown over time user homedirs were moved to
Having worked with unix for over 20 years I can assure you that originally /usr WAS short for user and that all user home directories were indeed in /usr. As a previous poster pointed out Unix shipped on two 1/2 inch tapes one was the root and the other one /usr with "userland" software. As Unix has grown over time user homedirs were moved to /home and /usr took a more general place and /usr was re-identified as an acronym for Unix System Resources.
No, the fact that the parent claimed that 417 mm is 4.17 cm (or 1.6 inch) when it is as you stoutly observed 16.4 inch
Umm, noooo!
0.417 m = 4.17 dm = 41.7 cm = 417 mm
1m = 10 dm = 100 cm = 1000 mm
You cannot replace human interaction with students with computer checks.
No, I am unhappy because ~ 20 packages were (key word "examples" in my previous post...) installed despite my say so AND that responsible (?) parties claimed that this was desirable to protect me from myself. I say (w. 20 year experience) that it is far from desirable to run software to service non existent hardware...
Yeah I run 2 distros. Mandrake because it installed easily on my old laptop and slack on everything else because it works. I might try SuSE as a replacement for Mandrake (or both).
FC is just a bother and leaves me fixing more and more for each new "improved" release. So no thanx
The important is wether it works or not. I gave up on RH/FC with FC2. It insisted on installing and starting a whole bunch of shit that I explicitly unchecked. Examples:
The reason "it has to be installed to satisfy dependencies". In previous RH/FC you could ignore those dependencies in expert mode. Now I spent lotsa time turning of stuff that didn't do anything (I wonder WTF the IR daemon actually does on a server w/o IR card???)
Now I use Mandrake/slackware. I might try the new SuSE...
I wholehartedly agree about finding ways to prevent bugs in the future. However, I strongly suggest that this is done mostly by how you work not what tool you use.
Secure software is created by good design and good practice. Tools tends to create complacency and over-reliance on the tool (that tool may or may not be good enough...)
You can safely hammer a nail with an axe if you are careful and pay attention and easily smash your hand to pieces with a good new hammer if you are careless.
In conclusion, yes you may improve your software with good tools but only if you are alreeady doing things "The Right Way"
How may of you can honestly say "I have never, ever created an interface without possibility to change expected behaviour"?
How may of you can honestly say "I have never, ever made a mistake while coding or designing program logic and flow"?
If you answered "I can" to all three you are lying!
That is the essence of secure software. We all make mistakes, including seasoned, paranoid veterans as myself. Some of us less others more, noone make NO mistakes. The more complex a system is the greater the risk of a fatal mistake...
The only way to make secure software is;
There is a miniscule risk that you will get a broken cellfone to produce a big enough spark (that is big in size and duration).
:-D
There is an equally small chance that the starter of your engine will NOT create that spark when you start your car after filling...
Hence, to minimize risk of fire prohibit starting of your engine at gasstations
As a matter of fact the article stated that some of OOo's advanced features did not degrade nicely in M$ Office...
Yeah OOo is Good Enough(TM) whareas M$ Office might not be. And one of them costs $300 or so >-)
My company uses strictly OOo, because of price and cross platform compatibility!
Plus, how computer many games can you think of for Linux?
:-D
This alone should encourage a lot of companies to switch... Think of the productivity gain
My options are
At a cost of CAD $399 (not including the box) my choice will be #2
As a matter of fact I did not post any link, I just read the link and made conclusions from that and other sources. What is suggested (i.e not implemented) is that the network should be able to somehow limit demand by shutting down consumers based on some rules. Suggested was among other things air conditioning. I thought it was a rather clever idea, as I mentioned I'd rather have my A/C shut down than another big blackout. We are not there now though (and wount be any time soon)
You are correct. However, you can argue that the fault in the big blackout was not the failed powerlines in Ohio but the fact that that part of the grid was not disconnected. The fact that Ontario and New York was blacked out is an operational fault. The fact that parts of Ohio was blacked out was the result of mitigating a powerline fault and protecting generating plants. Other parts of Ohio was possibly blacked out by the same operational fault that blacked out Ontario.
Demand side management in this context means the grid has the ability to shutdown nonessential use PDQ to avoid poweroutage. If the alternative last August would be Ontario Hydro shutting of my A/C for an hour rather than having 26 hours without power including spoilt food, no A/C, no computers for my business, guess what my pick would be...
Disengaging generating capacity should be last resort not pretty much the only available tool to save the grid. Therefore it is in fact another fault.
They do not comply with GPL, hence any GPL licensed software is out of reach for them!
He did not claim a $10 receipt, M$ offered him $10. He stated that he wanted to get paid for business cards advertising etc as well as the cost to reestablish himself under another domain. Could easily run up $10K
Nope He wanted to regain his costs (that is actually more than the cost of the domain)
my previous comment