Right. It should perform substantially as advertised. Most secure whatever yet, should be pretty secure.
I like OpenBSD's "No remote root in n years in the default install". It implies that there probably are some, but it's going to take an awful amount of hard work to find one.
IIRC there is a critical point on liquid-gas phase. So it is possible to take a liquid, evaporate it with a change of state, then change it continuously without a change of state back to a liquid. At very high temperatures and pressures, if you come back one way, it was a liquid. If you come back a different way, it was a gas.
Except that Lisp can define an APL interpreter and EVAL APL expressions. It can do this for several APL-like languages. Simultaneously. This is BEFORE it starts to get vile.
Disclaimer. I am no way anything like an expert is Lisp, but using things like ATOM, LIST, CAR, CDR as variable or function names, and getting away with it, is child's play.
Why should RedHat care about recovering broken XP systems? No reason they should. They do care about recovering broken RedHat systems, but that pretty much translates to recovering broken systems, XP systems not excluded.
Shouldn't the vendor have provided said facility? Yep. Will they? Nope.
If linux were on %90 of the desktops there would be 100 times less problems than with a Microsoft OS. Security flaws are usally either coding error or design errors and their rate is partially determined by lines of code. That's the rate of creation. The Linux community might be much smarter than the folks at Redmond, but that isn't the point. I think they enjoy a bug hunt. Not just uncovering the bug, but getting rid of the bug's friends and relations. OpenBSD calls it being proactive.
When Linux reaches 90% of the desktops (or will it be one of the BSDs?), there will be viruses. "You just got a virus from your buddy. Do you want to run the virus?" Dull day. Sure, Why not. These worms/viruses are all varients of the Honor Virus, if the user is aware of what's going on.
ReadHat at least has an automatic update. Haven't tried it. You don't want the initial version from RedHat 7.0, but that would just quickly update itself. Most of the patches are for things the normal user isn't running. Finding and applying them is easy. Even a kernel recompile is almost brain-dead simple, although "users" would use someone else's compile.
Where the OS is exposed to the outside world there is a posibility of compromise. The probabilities, however are far from equal.
Nicely put. I've almost come to the point of beliving that "your only friend in the business" are the black-hats. A security hole is a bug. It is a spectacular bug in that the computer which is suposedly under the control of the victim, is shown to really be under the control of somebody else. Realistically, which does more damage to an e-commerce site. An "evil" hacker who paints Kilroy was here on the walls, or a shipping clerk who puts too much information in a form field?
Windows. Pieces of glass affixed to holes in the wall. Must have missed some places. Plenty of holes left.
Carmine chapeaux?
For a rip, I prefer RedNeck Linux.
Nope, trolling on/. makes the PHBs want to buy things like Red Hat Professional Server.
It's a long time since I was a teenager. And I was never pimply-faced. For funzies, imagine Unix before fsck.
They already are. They have been dealinging with it. Starting with OpenBSD, they are finding and fixing the holes, and not with just a few bandaids. They aren't finished yet. Ideally, one should be able to run virus/worm infected email with impunity. If you know what's goin on, any of the virus/worms is just a variant of the Honor Virus.
My boss had something similar. New laptop. Not keyboard/mouse, but couldn't make a network connection. Finally I booted RedHat 7.2 Systems Administrator Survival CD, downloaded NTFS kernal module, and put about 3 gig of stuff where I could later recover. (Hint to RedHat: It'd be easier rescuing broken XP systems if you included the NTFS (READ ONLY) kernel module.) Reinstalled and reloaded. 1000MHz with 512Meg. Pathetic performance. Turned off what eye-candy I could find. Brought it back to somewhat reasonable.
Just wait 'till the press starts a feeding frenzy on the Microsoft worm du jour.;-)
Once the magic aura is gone and they start looking,.... (chortle, snicker, gufaw, hehe,...)
Maybe it still works this way. There was a time when you could go to a small-time farmer and get a gallon of fresh, whole, unpasturized milk. The standards were not the same as what was required for the local dairies. Milk from one or two cows. If there is a problem, the spread is severly limited. The local dairy combines milk from thousands of cows. Any problem affects thousands.
What I'm trying to say is that this should have no effect on authors of free software. Besides, with the source you do have recourse. If all else fails, you can fix it yourself.
Maybe it's just me, but with the source, or reasonable access to the source, if there is a problem, I can (or hire someone to do it) find and fix the problem. If I do not have access to the source, then the vendor is the only one in a position to fix any problems.
Probably a bit of protection for respondents. Even email address is optional.
Probably they feel that the risk to the privacy of residents of the stat of Washington is too great. It will be interesting to watch the process of discovery for what Microsoft does with this information. Remember, Microsft is the bunch bringing you.NET, Passport, etc.
"Concurrent provide four windows so you can view each application while it runs. For instance, you can..."
Page (v) Concurrent PC DOS User's Guide
Copyright (c) 1984 by Digital Research Inc.
"WINDOW
Form
WINDOW command NUMBER=n parameter [,parameter...]
Explanation
The WINDOW command displays and changes window parameters and records the window and screen contents...."
Page 8-103 Concurrent User's Guide
Some interesting TRADEMARKS listed.
CP/M, CP/M-86... dBASEII is a registered trademark of Ashton-Tate. CompuServe is a registered trademark of CompuServ, Inc., an H&R Block Company. Telenet is a registered trademark of GTE Telenet Communications Corporation .... MultiPlan is a registered trademark of Microsoft Corporation....
Slashdot Mirror
Here's one.
Read two numbers.
Add them together.
Print the result.
(No restriction on size other than assuming that you have enough memory)
Right. It should perform substantially as advertised. Most secure whatever yet, should be pretty secure.
I like OpenBSD's "No remote root in n years in the default install". It implies that there probably are some, but it's going to take an awful amount of hard work to find one.
IIRC there is a critical point on liquid-gas phase. So it is possible to take a liquid, evaporate it with a change of state, then change it continuously without a change of state back to a liquid. At very high temperatures and pressures, if you come back one way, it was a liquid. If you come back a different way, it was a gas.
Except that Lisp can define an APL interpreter and EVAL APL expressions. It can do this for several APL-like languages. Simultaneously. This is BEFORE it starts to get vile.
Disclaimer. I am no way anything like an expert is Lisp, but using things like ATOM, LIST, CAR, CDR as variable or function names, and getting away with it, is child's play.
Don't forget the cost of anti-virus software that at best is always trying to play catch-up. And the cost of recovering when it misses a beat.
The alternatives are an experienced admin running Linux or a bunch of clowns running NT. It may not start out that way, but it is the way it ends up.
Why should RedHat care about recovering broken XP systems?
No reason they should. They do care about recovering broken RedHat systems, but that pretty much translates to recovering broken systems, XP systems not excluded.
Shouldn't the vendor have provided said facility?
Yep. Will they? Nope.
If linux were on %90 of the desktops there would be 100 times less problems than with a Microsoft OS. Security flaws are usally either coding error or design errors and their rate is partially determined by lines of code. That's the rate of creation. The Linux community might be much smarter than the folks at Redmond, but that isn't the point. I think they enjoy a bug hunt. Not just uncovering the bug, but getting rid of the bug's friends and relations. OpenBSD calls it being proactive.
When Linux reaches 90% of the desktops (or will it be one of the BSDs?), there will be viruses. "You just got a virus from your buddy. Do you want to run the virus?" Dull day. Sure, Why not. These worms/viruses are all varients of the Honor Virus, if the user is aware of what's going on.
ReadHat at least has an automatic update. Haven't tried it. You don't want the initial version from RedHat 7.0, but that would just quickly update itself. Most of the patches are for things the normal user isn't running. Finding and applying them is easy. Even a kernel recompile is almost brain-dead simple, although "users" would use someone else's compile.
Where the OS is exposed to the outside world there is a posibility of compromise. The probabilities, however are far from equal.
Nicely put. I've almost come to the point of beliving that "your only friend in the business" are the black-hats. A security hole is a bug. It is a spectacular bug in that the computer which is suposedly under the control of the victim, is shown to really be under the control of somebody else. Realistically, which does more damage to an e-commerce site. An "evil" hacker who paints Kilroy was here on the walls, or a shipping clerk who puts too much information in a form field?
Wow 28 whole days. Cause for celebrations.
Windows. Pieces of glass affixed to holes in the wall. Must have missed some places. Plenty of holes left.
Carmine chapeaux?
For a rip, I prefer RedNeck Linux.
Ever been to a glass shop?
Tinted windows by an auto shop?
Well the ads do say you can fly.
Nope, trolling on /. makes the PHBs want to buy things like Red Hat Professional Server.
It's a long time since I was a teenager. And I was never pimply-faced. For funzies, imagine Unix before fsck.
They already are. They have been dealinging with it. Starting with OpenBSD, they are finding and fixing the holes, and not with just a few bandaids. They aren't finished yet. Ideally, one should be able to run virus/worm infected email with impunity. If you know what's goin on, any of the virus/worms is just a variant of the Honor Virus.
My boss had something similar. New laptop. Not keyboard/mouse, but couldn't make a network connection. Finally I booted RedHat 7.2 Systems Administrator Survival CD, downloaded NTFS kernal module, and put about 3 gig of stuff where I could later recover. (Hint to RedHat: It'd be easier rescuing broken XP systems if you included the NTFS (READ ONLY) kernel module.) Reinstalled and reloaded. 1000MHz with 512Meg. Pathetic performance. Turned off what eye-candy I could find. Brought it back to somewhat reasonable.
Just wait 'till the press starts a feeding frenzy on the Microsoft worm du jour. ;-)
.... (chortle, snicker, gufaw, hehe, ...)
Once the magic aura is gone and they start looking,
Or build a housse correctly?
...
Like the houses in inland Florida when Andrew hit?
Impossible, maybe not. But highly improbable.
The key question is how good is good enough? A car at 155 is not the same as a car at 55.
You're very right about Sircam. Follow the progression since Melissa (Remember Melissa? Melissa was nice!). Now extrapolate
And how is closed source any better?
Between poor chance and no chance, I'll take poor chance.
Maybe it still works this way. There was a time when you could go to a small-time farmer and get a gallon of fresh, whole, unpasturized milk. The standards were not the same as what was required for the local dairies. Milk from one or two cows. If there is a problem, the spread is severly limited. The local dairy combines milk from thousands of cows. Any problem affects thousands.
What I'm trying to say is that this should have no effect on authors of free software. Besides, with the source you do have recourse. If all else fails, you can fix it yourself.
Maybe it's just me, but with the source, or reasonable access to the source, if there is a problem, I can (or hire someone to do it) find and fix the problem. If I do not have access to the source, then the vendor is the only one in a position to fix any problems.
Licrosoft is a Lickey Louse company?
Haven't you realized that Micro-what's-it's-name is an AOL wannabe? Even the AOL users are dumping on Microsoft :-)
Probably a bit of protection for respondents. Even email address is optional. .NET, Passport, etc.
Probably they feel that the risk to the privacy of residents of the stat of Washington is too great. It will be interesting to watch the process of discovery for what Microsoft does with this information. Remember, Microsft is the bunch bringing you
"Concurrent provide four windows so you can view each application while it runs. For instance, you can ..."
..."
... dBASEII is a registered trademark of Ashton-Tate. CompuServe is a registered trademark of CompuServ, Inc., an H&R Block Company. Telenet is a registered trademark of GTE Telenet Communications Corporation . ... MultiPlan is a registered trademark of Microsoft Corporation. ...
Page (v) Concurrent PC DOS User's Guide
Copyright (c) 1984 by Digital Research Inc.
"WINDOW
Form
WINDOW command NUMBER=n parameter [,parameter...]
Explanation
The WINDOW command displays and changes window parameters and records the window and screen contents.
Page 8-103 Concurrent User's Guide
Some interesting TRADEMARKS listed.
CP/M, CP/M-86