Deploy basic safety nets at the framework (kernel/library) level. Whole classes of buffer overflows can be avoided with very little effort these days. Yet, MS refuses to do so. Remember, a while back, you could use a specially crafted BMP image to trigger an exploitable buffer overflow. This is ridiculous.
Don't encourage the user run as "Administrator". Heck, don't let him. At the very least there must be prominent warning messages all over the place, screaming that the user is doing something exceptionally stupid right now.
Don't let fucking office macros write to the filesystem or exec() without popping up 20 warning messages.
Do something to the so called outlook address book so that not every fucking trojan can use it to broadcast itself.
Do not open RPC ports to the world. No, the dysfunct firewall that ships with windows (have they fixed it finally?) doesnt help. Audit *all* services that *could under any circumstance* be exposed to the outside world and harden them. Better would be generic mechanisms (see "safety nets" above) so that at least these exposed services are protected from buffer overflows and the like.
Well, I could on for a bit, but the essence is: Windows is so broken (securitywise and in many other aspects) that large parts would have to be rewritten to fix only the worst of insanity. They need to scrap it and start from scratch - just like apple did.
Mac OS X shows the way how a modern "Joe Sixpak" operating system is supposed to work. Stable foundation for the backbone and a shiny surface that can't cause much harm even when there are bugs. It sure has some flaws of its own but none that I know of comes even close to the truckloads of braindead-ness from redmond.
I know someone who had a CD-ROM scatter in, I think, "only" a 40x drive. He said nothing really bad happened, just a very wierd, loud noise and the tower shook a bit. So, yes, they actually can fragment at lower speeds - at least when they're damaged as the said disk most likely was.
Just in case a very rich person with a similar problem is reading this: Invest in me!
Give me only one million of your chump change and my gratitude will haunt you forever. And I'll write tons of screaming testimonials for any product that you may be selling. With pics.
Oh, you can actually do that with windows nowadays, leave it always on?
Last time I checked it would gradually slow down to a crawl (can admittedly take a week or two) and eventually behave really funny - like certain folders just won't open anymore or networking stops working.
I think important is less the brand name of the board but of the chipset. Avoid cheap ALi and VIA parts and try to go for... well... any recommendations?
I, personally, have recently had surprisingly good expirience with SiS Chipsets (Linux support seems to be good). I can't say anything about performance, though so there might be better options.
Now two anecdotes to back up why you should avoid VIA:
1. My old Athlon 900 used to live on a ASUS A7V (or somesuch) with via KT133
(or somesuch) chipset. Linux wouldn't run well. I needed a kernel patch
to prevent the system time to jump back and forward randomly (!!).
It would seriously just jump half an hour back or fwd about 10 times a
day - obviously breaking just about everything. Now with the patch this
problem was resolved but various other stuff stopped working (NFS for
example). No good expirience.
2. The USB-Ports on my current VIA board KT266/A/333 refuse to work properly
with most external mass storage device. USB sticks seem to work but
external HDD-enclosements don't and, which hurts most, my iPod mini
doesn't either. This is on both linux *and* windows. The drive will
connect and work fine for a few MB but then crap out with random I/O
errors (gently fucking up any data that may have been in transit, had
to reformat my ipod three times during testing).
Funny thing is, to get around the obviously broken USB I bought a
PCI-Card to provide alternative USB ports. The card has an ALi chipset
and shows the exact same problems!
Some googling revealed that there are known problems with USB and this
VIA chipset and by my expirience these even affect USB add-on cards!
PS: Yes, the external devices all work like a charme on different host.
Needless to say my next board will *not* be a VIA (nor ALi, just to be sure...). If someone has similar expiriences, please share. I'm curious, really!
If it fails, wait a few hours, and cvsup your ports tree, and try again, it is almost guaranteed to be fixed, and it is almost guaranteed to work.
Well, which part of *will* work did you fail to understand?
Now please, tell me why you still wait 3 years for a new release which comes with old software?
The same reason why some people choose OpenBSD over FreeBSD. They prefer "tested and tortured for a very long time" over "almost guaranteed to work" in a mission critical environment.
That's exactly what I was trying to say; don't do that. Design your pages so they work in all browsers.
There's plenty of free knowlegde available online about how to properly design accessible pages that work in all browsers. Do yourself a favor and learn to do it right.
Stable is not for your desktop. You don't need stable on your desktop. Run testing or unstable. Or fedora or ubuntu.
The 15 people running alphas and ARM are very happy that there is a full fledged linux distro to go with. Oh, btw, did you know that most of the little gadgets of today (PDAs and game handhelds in particular) run on ARM? So, maybe your "15 people" is a tiny bit off.
Slashdot Mirror
Netbeans.. eclipse... netbeans... eclipse....
can't decide. i think i'll stick with vim.
And emulating longhorn inside vmware?
The link you provided is snake-oil.
This "Peer-Guardian" software does not provide anonymity.
And it does not protect you from anyone (RIAA, Government, not even your
mom).
It's not much more than a blacklist. If the RIAA wants to play sherlock they'll probably just use some random AOL dialup. Go figure.
Someone slap these kids over with a cluestick.
Nope.
13:11:01 up 98 days, 10:14, 1 user, load average: 114.24, 103.98, 112.67
Ok, this one is not exactly idle. CTCS burnin, baby.
Ever hear of Lotus Notes?
Yes, I have and it is a nice proof for grandparents statement.
Maybe when MS entered the market and people fell for the advertising.
But today? Isn't it common sense by now that MS does not belong on a server?
ActiveX (get rid of it altogether).
Deploy basic safety nets at the framework (kernel/library) level.
Whole classes of buffer overflows can be avoided with very little effort these days. Yet, MS refuses to do so. Remember, a while back, you could use a specially crafted BMP image to trigger an exploitable buffer overflow. This is ridiculous.
Don't encourage the user run as "Administrator". Heck, don't let him.
At the very least there must be prominent warning messages all over the place, screaming that the user is doing something exceptionally stupid right now.
Don't let fucking office macros write to the filesystem or exec() without popping up 20 warning messages.
Do something to the so called outlook address book so that not every fucking trojan can use it to broadcast itself.
Do not open RPC ports to the world. No, the dysfunct firewall that ships with windows (have they fixed it finally?) doesnt help.
Audit *all* services that *could under any circumstance* be exposed to the outside world and harden them. Better would be generic mechanisms (see "safety nets" above) so that at least these exposed services are protected from buffer overflows and the like.
Well, I could on for a bit, but the essence is: Windows is so broken (securitywise and in many other aspects) that large parts would have to be rewritten to fix only the worst of insanity. They need to scrap it and start from scratch - just like apple did.
Mac OS X shows the way how a modern "Joe Sixpak" operating system is supposed to work. Stable foundation for the backbone and a shiny surface that can't cause much harm even when there are bugs.
It sure has some flaws of its own but none that I know of comes even close to the truckloads of braindead-ness from redmond.
It's only when the sides are mismatched that it becomes a methodical process.
cf. Iraq.
And because of their ugly shape, I always assumed you can even used them to vacuum potato chips crumbles under your desk.
Not quite but even better, you get french fries!
Or Nintendo GameBoy. Oops! Wrong thread.
No, make a cube and paint the individual chips all funny.
Revenge of the rubics cube, encrypt your sensible data by physically scrambling it!
I know someone who had a CD-ROM scatter in, I think, "only" a 40x drive.
He said nothing really bad happened, just a very wierd, loud noise and the tower shook a bit. So, yes, they actually can fragment at lower speeds - at least when they're damaged as the said disk most likely was.
Just in case a very rich person with a similar problem is reading this:
Invest in me!
Give me only one million of your chump change and my gratitude will haunt you forever. And I'll write tons of screaming testimonials for any product that you may be selling. With pics.
Dude, the 404 is *it*.
Oh, you can actually do that with windows nowadays, leave it always on?
Last time I checked it would gradually slow down to a crawl (can admittedly take a week or two) and eventually behave really funny - like certain folders just won't open anymore or networking stops working.
Who has seen a real-live Guru Meditation Error?
I have seen plenty of them.
Here's one for those who don't know it.
Definately more stylish than the atari bombs or the mac sorryface.
Ah, from the adventures of sam verner, isnt it?
Well, the Timer/Systemtime issue might have been fixable with a BIOS update. I can't remember if I tried that, it's been years ago now.
About the USB-problem on the new board (KT266): Yes, I've tried all the drives on other boards and they work fine (same cable etc).
I think important is less the brand name of the board but of the chipset.
Avoid cheap ALi and VIA parts and try to go for... well... any recommendations?
I, personally, have recently had surprisingly good expirience with SiS Chipsets (Linux support seems to be good). I can't say anything about performance, though so there might be better options.
Now two anecdotes to back up why you should avoid VIA:
1. My old Athlon 900 used to live on a ASUS A7V (or somesuch) with via KT133
(or somesuch) chipset. Linux wouldn't run well. I needed a kernel patch
to prevent the system time to jump back and forward randomly (!!).
It would seriously just jump half an hour back or fwd about 10 times a
day - obviously breaking just about everything. Now with the patch this
problem was resolved but various other stuff stopped working (NFS for
example). No good expirience.
2. The USB-Ports on my current VIA board KT266/A/333 refuse to work properly
with most external mass storage device. USB sticks seem to work but
external HDD-enclosements don't and, which hurts most, my iPod mini
doesn't either. This is on both linux *and* windows. The drive will
connect and work fine for a few MB but then crap out with random I/O
errors (gently fucking up any data that may have been in transit, had
to reformat my ipod three times during testing).
Funny thing is, to get around the obviously broken USB I bought a
PCI-Card to provide alternative USB ports. The card has an ALi chipset
and shows the exact same problems!
Some googling revealed that there are known problems with USB and this
VIA chipset and by my expirience these even affect USB add-on cards!
PS: Yes, the external devices all work like a charme on different host.
Needless to say my next board will *not* be a VIA (nor ALi, just to be sure...). If someone has similar expiriences, please share. I'm curious, really!
Sounds interesting. Just what would be a practical application for "small distance"?
If it fails, wait a few hours, and cvsup your ports tree, and try again, it is almost guaranteed to be fixed, and it is almost guaranteed to work.
Well, which part of *will* work did you fail to understand?
Now please, tell me why you still wait 3 years for a new release which comes with old software?
The same reason why some people choose OpenBSD over FreeBSD.
They prefer "tested and tortured for a very long time" over "almost guaranteed to work" in a mission critical environment.
That's exactly what I was trying to say; don't do that.
Design your pages so they work in all browsers.
There's plenty of free knowlegde available online about how to properly design
accessible pages that work in all browsers. Do yourself a favor and learn to do it right.
In that case, the majority of pages that Google displays would most likely be rendered as IE compatible ones.
See? Yet another reason to not design for a browser.
Stick to the standard.
*sigh*
Stable is not for your desktop. You don't need stable on your desktop.
Run testing or unstable. Or fedora or ubuntu.
The 15 people running alphas and ARM are very happy that there is a full fledged linux distro to go with.
Oh, btw, did you know that most of the little gadgets of today (PDAs and game handhelds in particular) run on ARM?
So, maybe your "15 people" is a tiny bit off.