> The Red Hat advisories include vulnerabilities for > Perl, Show me ONE RedHat machine, Hell show me *ANY* *NIX machine without Perl. If it isn't there by default, chances are someone installed it because quite frankly it's pretty hard to live without (At least IMHO).
> emacs, The editor of choice in the Linux community? I havent seen a machine installed by anyone other than myself that doesn't have emacs, either by default or added in later.
> xpdf, Something I can live without, although it is inconvenient if it isn't there on a desktop workstation.
> vim, My editor of choice? And pretty much the defacto standard (I can sit down at ANY *NIX machine and type "vi" and get an editor - it is expected). Again I've yet to see a *NIX machine that doesn't have vim or some other vi clone on it.
> PHP, Happily provided for you with many "default" prepackaged apache installs. If you're gonna count Apache vulnerabilities as OS holes (which I personally don't - I have several machines that don't have any httpd running b/c they aren't web servers) you need to count PHP holes too.
> acroread, something else I can live without, subject to the same caveat as xpdf.
> ruby, another thing I can live without (entirely).
> etc. gcc, make, et. al.? Even though RedHat Enterprise AS3 doesn't install them by default, *I* sure as hell consider development tools a MUST-HAVE on *NIX systems.
I cant think of any more stuff that's "standard" (i.e. people will be upset if it isn't there), but you should *ALL* be aware that we can't ignore things just because they are "optional" in the installer, unless you intend to sit down in front of a console-only machine where the only text editor is "cat > filename" and the only shell/interpreted language is/bin/sh and a few system-configuring commands.
Sometimes the flaws in the creature comforts are just as critical and just as unavoidable as the flaws in the kernel.
-------------- Now, having said that, Yea I do think we can ignore security holes in OpenOffice, the Weather Widget, etc. -- Things that you really can live without, which you may (as a normal, ordinary user) install for your own convenience that aren't part of the "standard" set of things you EXPECT to have. People using those features should obviously keep up with patches, but that's the equivalent of "Download the latest patch for SimCity 450000 so your system doesn't hang!"
The great weakness of Windows is that you can't get rid of many of the things that you could live without (MSN Messenger?), so for all intents and purposes those patches *ARE* part of the core OS patch list.
Well, I do understand their reasoning, and as others have pointed out, Apple will always be a "niche market" for OOo.
Of course, as a mac user I am somewhat pissed off that the platform is being relegated to the status of a second-class citizen. OSX X11 takes quite a while to start up, and incurs a NOTICABLE overhead compared to the Windows native version of OpenOffice. Also, on a platform that makes it name based on simplicity, having to install X11, with its cumbersome (and possibly confusing to users with no *NIX familiarity) configuration choices may drive users away.
On the flip side of this coin, Apple's iWork suite may get a boost from this (OpenOffice will never be native, iWork is native & integrates seamlessly with the rest of the iEverything world), which will help Apple's bottom line - so this isn't all bad.
Still, I was hoping for a native OpenOffice in v 2.0. Cest' la vie.
Assuming the poster lives within the United States, there are no special legal requirements in most cases. Simply declare the income on your tax return, and expect to owe the government some money come April (just like you're SUPPOSED to do when you sell stuff on eBay, or hold a yard sale, etc.).
The caveat here is *you* are the business - which means if someone wants to sue "the provider", they would be suing YOU, and anything you own is fair game in said lawsuit.
I see no problem with your copying code from the forked project. As you have said, both projects are under the GPL, so there is no legal restriction on taking the code that I am aware of. Further you are crediting the forked project with the changes, so I'd say your ass is covered in an ethical sense too.
As for the other project leader's idea of "obfuscating his changelog and only open the source as packages when he's doing a release", he's certainly free to do that (as long as the source is available he's not violating the GPL), but it seems to me he'd be shooting himself in both feet just to spite your project.
Bottom line, just keep doing what you're doing and let the twit blow off his steam however he wants.
A simple, serious answer to your simple, but not really serious question: We can't.
Delinking any large portion of the net now is difficult if not impossible, since the DoD no longer runs the show. Commercial backbone providers in Europe will continue to operate however they wany, and if the Russians pay their bills on time the packets keep flowing. Ditto for Nigeria and other (in)famous scam countries.
The amount of effort required to delink any node or set of nodes makes the operation time- and cost-prohibitive, since thanks to the wonders of routing if even one path remains open all the traffic will eventually be funneled over there. (Of course this COULD result in all of Russia's traffic going through a 14.4 modem somewhere in Siberia, which would certainly make things quite interesting and would effectively knock them off the 'net, but that's purely an academic comment:))
This has been a public service announcement by Blinky the Three-Eyed Phish.... er, fish:)
This is most certainly vigilante justice, and it is most certainly illegal. What people like you who want to go around DOSing phishing sites off the web seem to forget is that there are OTHER PEOPLE using the SAME BACKBONE.
When you can't get to www.pornopalace.com or whatever sites you like to visit every day because there just happened to be a phisher in the same co-lo, and a bunch of vigilantes decided to DOS that phisher off the net to protect the innocent (and the stupid), or when your personal site is knocked off the net for the same reason, you'll sing a different tune.
And that's to say nothing of the small web hosting providers (there ARE some of those still around ya know) who unknowingly sell an account to a phisher. They'd probably be more than happy to take the bastard's site down and keep his money, but by DOSing the phisher you wind up costing the poor hosting company money (remember, SOMEONE has to pay for that bandwidth you're using up with your DOS attack, so when that $9.95 a month website you're enjoying becomes a $19.95 a month site and they say it's to cope with "excessive bandwidth charges" don't come crying to me).
This is NOT the old west. The 'net is NOT a vast untamed frontier where you can just go taking down sites you don't agree with anymore. This is the REAL WORLD and in the REAL WORLD your ACTIONS have CONSEQUENCES.
THINK before you speak or act, or better yet, just STFU until you can say something useful.
> Okay, and how do the spammers get somebody's email > address to start with? Oh yes, a virus emails the contents of > their inbox to a russian server"
#1: Why a russian server? A little prejudiced?
#2: Use an IMAP server (preferably one running over a secure connection) like I do and don't store your email bodies on your local machine. Don't save your mail server password (oh is it REALLY going to kill you to type 10 characters?). Surprise Surprise, all they can get are headers unless they manage to break into the actual MAIL SERVER (in which case you have bigger problems than your winblows box getting a cold).
point of fact, Windows 2000 and later DO have a concept similar to sudo: the RunAs service.
If running, you can control(I believe)+Right Click on any program and there will be a "Run As..." option that lets you execute the program as another user.
It's been a while since I've been in front of a Windows box, but I believe if you're an administrator you can use your password to authorize the action (someone in front of a Windows box please confirm this, I may be wrong).
It can run as a regular user and wait until it sees the installer app show up in the process list, at which point it will open up its dialog box and ask you for your Admin password.
I tend to discount this personally - Even if I did fall for the "virus" window and enter my password, the (real) installer would most likely ask me for my password at some point too. Having the system ask you for your password TWICE should be a big tip off that something is not entirely kosher.
Quote: OO is great for problems where an interface applies naturally to a wide range of types, not so good for managing polymorphism (the machinations to get collections into OO languages are astounding to watch and can be hellish to work with), and remarkably ill-suited for network computing. ---
Perl solves half of this problem (collections are relatively easy to throw together) - Unfortunately the other half (making it Network Computing Friendly) is still a royal pain in the posterior.
While I'm not a huge fan of OOP, perhaps future research will conquer this gap and make it somewhat more paletable.
Are slashdotters becoming morons? I'm sad that I only have 5 mod points, and i'm not wasting them modding all the crap on this article as offtopc.
Clue in: We're not proposing new questions, and this *IS NOT* an Ask Slashdot. If you want your voice to have ANY chance of being heard go to the site (http://youthdebate.newvotersproject.org/) and vote for the questions you want to see answered by these candidates.
If y'all have INTELLIGENT comments to make, by all means make 'em, but quit baiting eachother with the usual republicrat false-posturing "A is a better choice than B because A stands for everything that B doesn't" crap, it's sickening.
FreeBSD 4.10 firewall (IPFW). Soon to be upgraded to 5.3 with pf. Blocks the majority of worms and snooping skr1p7 k1dd13 h4X0rZ.
No antivirus software - it's a waste of valuable resources. If you have half a brain you won't get infected (stop downloading and running everything just because a window popped up in your browser saying to).
If a machine DOES get infected the ONLY solution I accept is to wipe the damn thing out and start over from an empty disk -- No sense taking the chance that some other virus or worm is lurking around.
None of that net-nanny safe-surfing site-blocking shit. More damn trouble than it's worth. If you're worried about little Jane or Johnny going to eeeevil porno sites you can run a proxy server and then ground the little pervert when you see him lookin at www.sexwithmysaintbernard.com or whatever he/she is into.
Mozilla-derived browsers with popup blocking. Better than any commercial solution I've seen so far - they block the ad-crap but let most of my legit stuff through without needing intervention.
Best of all, all my machines perform at their peak since they're not tying up cycles with all this extra crap that really just gets in the way.
This is a new one on me, I've never seen LCDs lag like this before. I agree with what others have said about checking your resolution and refresh rates - LCDs are very picky about such things and running it out of spec may be enough to cause this sort of behavior.
Also, if it is unusually cold where you're using this monitor you may be getting lag because of that (LCDs don't respond as fast or as well when they're extremely cold or hot). I would suspect this is not your problem since if your environment is extreme enough to perturb the LCD it's probably extreme enough to piss you off too:)
Bottom line, get a new LCD if none of the suggestions you've seen already fix your problem - the monitor is probably hosed.
BTW (and slightly off topic), for everyone who thinks CRTs are god's gift to monitors please remember they do have their problems too - luminous trails following light objects across black screens can be very irritating, and I'm sure I'm not the only person who accidentally left a magnetic object too close to the screen and wound up with a big purple splotch on the side for a few days...
And THIS, ladies and gentlemen, is why I host MY little blog-like thing on MY OWN site, using MY OWN crappy software. That way I KNOW backups are getting done, and I KNOW when the machine will be down, and if something goes wrong I can fix it MY OWN DAMN SELF.
Sorry if I seem a little callous, but really how hard is it to write a few hundred lines of PHP for a simple online journal with comments? NOT VERY! And it runs on the same machine I use for all my other stuff (DNS, Mail, CVS) so it's not like I'm spending untold thousands extra each month, it really helps make the cost-benefit ratio of my server more tolerable.
If so, WYSE WY-60 (doesn't have its year of manufacture on the back plate) and an old Toshiba T-1200 laptop with its monochrome (blue on grey) LCD are the oldest displays I use regularly.
I too have a Sun-Branded Sony monster that outweighs any "modern" monitor... Sad part is these things outperform them all too.
MIT OpenCourseware -- As the parent post said this is a great starting point for any school redesigning their CS curriculum.
I'm sure it also has value as add-ons to an IT/IS/MIS curriculum.
No mod points - Someone please mod parent up.
Thx.
Too right - I am a HUGE proponent of the "if it's broken just reinstall it" school - In many cases it's faster.
On the other hand, sometimes it just IS NOT an option. When I took my current job (almost 5 years ago) I inherited a horribly broken NIS/NFS mess in our UNIX environment -- So broken that if machines needed to be turned off (or on) it had to be done in a specific order or the entire UNIX network would collapse on itself.
Surely blowing everything away and starting over would have fixed the problems, but it would also have taken me months to rebuild since I had no understanding of how the structure came to be the way it was (and my bosses had long since forgotten).
Instead I slowly repaired the mess from within, and within a year we had a setup where almost any machine can be switched off without causing any problems (the main NFS server, for obvious reasons, must remain on.:))
------------
Of course, there is the problem of HOW to give students this experience. At my school the CS department is not really responsible for its own equipment (a completely seperate issue involving university politics), and as a result if something breaks (like a machine losing its NFS or NIS+ lifeline) our only recourse is "reboot and hope it comes back". We can't even unmount/remount NFS partitions or force the systems to rebind to NIS+.
Many schools actively deny their students the experience of fixing broken systems, and as long as this is standard practice we will continue to get graduates who don't understand that sometimes a big magnet is NOT the best tool for the job.
Sounds to me like your DBA never learned the basics of database design.
In ANY data storage system where there are interrelations between the elements (objects) being stored (this includes the obvious relational systems as well as hierarchical systems) the design phase is always best carried out on paper using some kind of modeling scheme (UML, Entity-Relationship drawings, etc.)
This is the method my company uses to design large-scale databases to support our systems and network management software.
The result? A few whiteboards full of circles and arrows and dotted lines (the intermediate nastyness while we work out exactly who will be related to what in which ways) culminating in a diagram that translates very nicely into the Relational world, and subsequently into the hierarchical world (LDAP ala RFC 2307).
While sometimes staring at the code is the ONLY way to understand something, the importance of a thorough understanding of the reasoning behind the design CANNOT be overstated.
OK, I'm not qualified to give an IT/IS curriculum outline -- What I DO feel qualified to do is suggest a generic CS outline.
As many other posters have pointed out, the outline presented reads like a trade school/training course outline: Learn Cisco IOS. Learn MS Win2K+3. Learn Linux (presumably redhat). Learn MS SQL Server, MySQL, Whatever. Learn VB. Lern Visual C++. etc.
Rather than tying students to a particular product, teach them genericly useful skills.
For example:
CSC-101 : Introcuction to programming
CSC-101A : Lab for CSC-101 (people learn by DOING not by having Dr. Fuzzyeyebrows lecture for days on end)
CSC-102 : Discrete Mathematics 1
CSC-103 : Discrete Mathematics 2 (prereq: 102)
CSC-201 : Algorithms and Data Structures (Prereq. 101 & 101a) -- This is where they learn the algorithms...
CSC-202 : Analisys of Algorithms (prereq. 201) -- This is where they learn about efficency, complexity, etc.
Now that they are well-versed in the basics you can start feeding them more advanced topics:
Database design (How and why Relational databases work the way they do. Relational algebra, Query optimization & planning, the Hows and Whys of indexes, crash recovery)
Database implementation (seperate course where students go hands on and build a database as a semester-long project)
Artificial Intelligence (NLP, Neural networks, game-playing algorithms like minimax)
Programming Languages -- Not "in this course we are going to teach you lisp, prolog, C, Pascal and Ada", but "Learn lambda calculus, type theory, etc. and how it all ties together to make a programming language like C"
Networking and Data Communications - From the hardware level up: explain the basics of how ethernet signalling works, the REASONS behind those annoying "maximum length of a segment" rules, how TCP/IP works, culminating in the students building a network (with whatever software/hardware is available - They shouldn't NEED to use linux or windows or OS/2, they should be able to adapt)
This course would include a BASIC discussion of security.
System Security - How to build secure networks, good policies for security of local machines, encryption and its benefits/drawbacks/weaknesses.
Software Engineering - Theory (teach the students the basics of gathering requirements, designing solutions, etc. Get them accustomed to thinking like they will almost invariably have to in the Real World.
Software engineering - Practice (semester-long project in which the students use everything they learned in the Theory course to tackle a project, either one assigned to them by the professor or (preferably) one assigned to them by an outside concern. At my school the software engineering class was approached by another section of the university to design outreach software.
One of the most important things that any student - IS, IT, CS, Trade School, WHATEVER - needs to learn is HOW TO READ THE F***ING MANUAL -- The great failing of my school is that there are people at my level (seniors) who have been "using" the CS department's UNIX machines (Solaris) for almost four years now who do NOT know about "man" and "apropos".
The things employers (my employers anyway) look for are the ability to THINK and solve problems, and the skills to know where to look to find the answer -- Man pages, news groups, google, etc. are all resources that seem to be wasted on many of my peers. Not knowing where to look is a huge resource sink in the Real World, and will not be helpful to your chances of future employment.
OK, I just need to ask how this is a "shot" at FreeBSD when the developers themselves acknowledged the bugs that are mentioned in the/. story - In fact the release anouncement for the new RC uses the exact same wording.
Am I the ONLY fscking BSD user on slashdot without a persecution complex?
Yet another vote for GoDaddy.com - they seem to be quite popular (and the cheapest I've found to date)
I've never had a problem with them, their interface is (relatively) fast, clean, and easy to understand & use once you get used to it.
I haven't ever needed tech support from GoDaddy yet, so I can't comment on that, but I haven't had any double-billings or anything of that ilk which I have had with other registrars (who shall remain nameless, since nameless sites go there...).
GoDaddy has never bothered me with unsolicited snail or electronic mail, just my usual "Your domain is expiring..." message. They also (I believe, not logged in to my domain interface at the moment) have automatic renewal options now.
My personal patch policy is vastly different from my company patch policy.
Personal machines: Windows: Patched whenever the "Automatic Update" critter says I should. Granted this is a lousy policy, but with a new patch every week I can't be bothered to deal with them all.
UNIX: Source is CVS'd nightly. A general "upgrade" build is run every 2 months to keep my systems current with minor bug fixes & other small stuff like that.
When a security advisory comes out for a service I don't use, the patch is applied whenever the next upgrade build is run.
When a security advisory comes out for a service I DO use, I pull down the source tree as soon as a patch is available, then kick off an upgrade build. In the case of third-party software, ports and the like, the same methodology applies (if I don't run it I ignore it, if I do I patch it ASAP), but I perform the upgrade through the ports system (BSD) or by fetching and rebuilding the source for the appropriate service/package/etc.
At work, the general policy (small office situation so this is very loose) is-
Windows: If it seems OK on our personal machines after a 48 hour wait, the Windows machines in the office are patches.
UNIX: Internal machines are only patched when needed, often this amounts to "never". External machines are patched as-needed (depending on what services they run, what OS, etc.)
I try not to leave ANY machine (personal or corporate) that is on the internet at large unpatched against any vulnerability for more than a week, even if "patched" just means "disabled service X to prevent exploitation".
Every so often I'll log in to LambdaMOO (lambda.moo.mud.org:8888) just to keep my account alive or to see whats going on.
I used to be far more active, but as time goes on I have less free time between work and school. Pity really, Lambda is one of the few MUDs I really enjoy because of its multifaceted nature - There are MUD-Like spots with puzzles and interactive 'critters', an RPG that got swallowed (easy access from under the hot tub... creepy), and a huge social area.
Plus there are all those colorful guests.../~mikeg
Slashdot Mirror
So, at the risk of my karma:
/bin/sh and a few system-configuring commands.
> The Red Hat advisories include vulnerabilities for
> Perl,
Show me ONE RedHat machine, Hell show me *ANY* *NIX machine without Perl. If it isn't there by default, chances are someone installed it because quite frankly it's pretty hard to live without (At least IMHO).
> emacs,
The editor of choice in the Linux community? I havent seen a machine installed by anyone other than myself that doesn't have emacs, either by default or added in later.
> xpdf,
Something I can live without, although it is inconvenient if it isn't there on a desktop workstation.
> vim,
My editor of choice? And pretty much the defacto standard (I can sit down at ANY *NIX machine and type "vi" and get an editor - it is expected).
Again I've yet to see a *NIX machine that doesn't have vim or some other vi clone on it.
> PHP,
Happily provided for you with many "default" prepackaged apache installs. If you're gonna count Apache vulnerabilities as OS holes (which I personally don't - I have several machines that don't have any httpd running b/c they aren't web servers) you need to count PHP holes too.
> acroread,
something else I can live without, subject to the same caveat as xpdf.
> ruby,
another thing I can live without (entirely).
> etc.
gcc, make, et. al.? Even though RedHat Enterprise AS3 doesn't install them by default, *I* sure as hell consider development tools a MUST-HAVE on *NIX systems.
I cant think of any more stuff that's "standard" (i.e. people will be upset if it isn't there), but you should *ALL* be aware that we can't ignore things just because they are "optional" in the installer, unless you intend to sit down in front of a console-only machine where the only text editor is "cat > filename" and the only shell/interpreted language is
Sometimes the flaws in the creature comforts are just as critical and just as unavoidable as the flaws in the kernel.
--------------
Now, having said that, Yea I do think we can ignore security holes in OpenOffice, the Weather Widget, etc. -- Things that you really can live without, which you may (as a normal, ordinary user) install for your own convenience that aren't part of the "standard" set of things you EXPECT to have.
People using those features should obviously keep up with patches, but that's the equivalent of "Download the latest patch for SimCity 450000 so your system doesn't hang!"
The great weakness of Windows is that you can't get rid of many of the things that you could live without (MSN Messenger?), so for all intents and purposes those patches *ARE* part of the core OS patch list.
Well, I do understand their reasoning, and as others have pointed out, Apple will always be a "niche market" for OOo.
Of course, as a mac user I am somewhat pissed off that the platform is being relegated to the status of a second-class citizen. OSX X11 takes quite a while to start up, and incurs a NOTICABLE overhead compared to the Windows native version of OpenOffice.
Also, on a platform that makes it name based on simplicity, having to install X11, with its cumbersome (and possibly confusing to users with no *NIX familiarity) configuration choices may drive users away.
On the flip side of this coin, Apple's iWork suite may get a boost from this (OpenOffice will never be native, iWork is native & integrates seamlessly with the rest of the iEverything world), which will help Apple's bottom line - so this isn't all bad.
Still, I was hoping for a native OpenOffice in v 2.0. Cest' la vie.
I'm just impressed that my little shithole county's shithole courts are actually mentioned in a slashdot article.
Nothing to see here... move along...
Assuming the poster lives within the United States, there are no special legal requirements in most cases. Simply declare the income on your tax return, and expect to owe the government some money come April (just like you're SUPPOSED to do when you sell stuff on eBay, or hold a yard sale, etc.).
The caveat here is *you* are the business - which means if someone wants to sue "the provider", they would be suing YOU, and anything you own is fair game in said lawsuit.
Essentially UNIX talk (or ntalk), over an SSH tunnel?
Kinda sad.
I see no problem with your copying code from the forked project. As you have said, both projects are under the GPL, so there is no legal restriction on taking the code that I am aware of. Further you are crediting the forked project with the changes, so I'd say your ass is covered in an ethical sense too.
As for the other project leader's idea of "obfuscating his changelog and only open the source as packages when he's doing a release", he's certainly free to do that (as long as the source is available he's not violating the GPL), but it seems to me he'd be shooting himself in both feet just to spite your project.
Bottom line, just keep doing what you're doing and let the twit blow off his steam however he wants.
A simple, serious answer to your simple, but not really serious question: We can't.
:))
:)
Delinking any large portion of the net now is difficult if not impossible, since the DoD no longer runs the show. Commercial backbone providers in Europe will continue to operate however they wany, and if the Russians pay their bills on time the packets keep flowing.
Ditto for Nigeria and other (in)famous scam countries.
The amount of effort required to delink any node or set of nodes makes the operation time- and cost-prohibitive, since thanks to the wonders of routing if even one path remains open all the traffic will eventually be funneled over there. (Of course this COULD result in all of Russia's traffic going through a 14.4 modem somewhere in Siberia, which would certainly make things quite interesting and would effectively knock them off the 'net, but that's purely an academic comment
This has been a public service announcement by Blinky the Three-Eyed Phish.... er, fish
This is most certainly vigilante justice, and it is most certainly illegal. What people like you who want to go around DOSing phishing sites off the web seem to forget is that there are OTHER PEOPLE using the SAME BACKBONE.
When you can't get to www.pornopalace.com or whatever sites you like to visit every day because there just happened to be a phisher in the same co-lo, and a bunch of vigilantes decided to DOS that phisher off the net to protect the innocent (and the stupid), or when your personal site is knocked off the net for the same reason, you'll sing a different tune.
And that's to say nothing of the small web hosting providers (there ARE some of those still around ya know) who unknowingly sell an account to a phisher. They'd probably be more than happy to take the bastard's site down and keep his money, but by DOSing the phisher you wind up costing the poor hosting company money (remember, SOMEONE has to pay for that bandwidth you're using up with your DOS attack, so when that $9.95 a month website you're enjoying becomes a $19.95 a month site and they say it's to cope with "excessive bandwidth charges" don't come crying to me).
This is NOT the old west. The 'net is NOT a vast untamed frontier where you can just go taking down sites you don't agree with anymore. This is the REAL WORLD and in the REAL WORLD your ACTIONS have CONSEQUENCES.
THINK before you speak or act, or better yet, just STFU until you can say something useful.
Mod me however, I've got freakin' karma to burn.
> Okay, and how do the spammers get somebody's email
> address to start with? Oh yes, a virus emails the contents of
> their inbox to a russian server"
#1: Why a russian server? A little prejudiced?
#2: Use an IMAP server (preferably one running over a secure connection) like I do and don't store your email bodies on your local machine. Don't save your mail server password (oh is it REALLY going to kill you to type 10 characters?). Surprise Surprise, all they can get are headers unless they manage to break into the actual MAIL SERVER (in which case you have bigger problems than your winblows box getting a cold).
point of fact, Windows 2000 and later DO have a concept similar to sudo: the RunAs service.
If running, you can control(I believe)+Right Click on any program and there will be a "Run As..." option that lets you execute the program as another user.
It's been a while since I've been in front of a Windows box, but I believe if you're an administrator you can use your password to authorize the action (someone in front of a Windows box please confirm this, I may be wrong).
The "virus" is "installed" - just not as root.
It can run as a regular user and wait until it sees the installer app show up in the process list, at which point it will open up its dialog box and ask you for your Admin password.
I tend to discount this personally - Even if I did fall for the "virus" window and enter my password, the (real) installer would most likely ask me for my password at some point too. Having the system ask you for your password TWICE should be a big tip off that something is not entirely kosher.
Quote:
OO is great for problems where an interface applies naturally to a wide range of types, not so good for managing polymorphism (the machinations to get collections into OO languages are astounding to watch and can be hellish to work with), and remarkably ill-suited for network computing.
---
Perl solves half of this problem (collections are relatively easy to throw together) - Unfortunately the other half (making it Network Computing Friendly) is still a royal pain in the posterior.
While I'm not a huge fan of OOP, perhaps future research will conquer this gap and make it somewhat more paletable.
Are slashdotters becoming morons? I'm sad that I only have 5 mod points, and i'm not wasting them modding all the crap on this article as offtopc.
Clue in: We're not proposing new questions, and this *IS NOT* an Ask Slashdot. If you want your voice to have ANY chance of being heard go to the site (http://youthdebate.newvotersproject.org/) and vote for the questions you want to see answered by these candidates.
If y'all have INTELLIGENT comments to make, by all means make 'em, but quit baiting eachother with the usual republicrat false-posturing "A is a better choice than B because A stands for everything that B doesn't" crap, it's sickening.
FreeBSD 4.10 firewall (IPFW). Soon to be upgraded to 5.3 with pf. Blocks the majority of worms and snooping skr1p7 k1dd13 h4X0rZ.
No antivirus software - it's a waste of valuable resources. If you have half a brain you won't get infected (stop downloading and running everything just because a window popped up in your browser saying to).
If a machine DOES get infected the ONLY solution I accept is to wipe the damn thing out and start over from an empty disk -- No sense taking the chance that some other virus or worm is lurking around.
None of that net-nanny safe-surfing site-blocking shit. More damn trouble than it's worth. If you're worried about little Jane or Johnny going to eeeevil porno sites you can run a proxy server and then ground the little pervert when you see him lookin at www.sexwithmysaintbernard.com or whatever he/she is into.
Mozilla-derived browsers with popup blocking. Better than any commercial solution I've seen so far - they block the ad-crap but let most of my legit stuff through without needing intervention.
Best of all, all my machines perform at their peak since they're not tying up cycles with all this extra crap that really just gets in the way.
This is a new one on me, I've never seen LCDs lag like this before. I agree with what others have said about checking your resolution and refresh rates - LCDs are very picky about such things and running it out of spec may be enough to cause this sort of behavior.
:)
Also, if it is unusually cold where you're using this monitor you may be getting lag because of that (LCDs don't respond as fast or as well when they're extremely cold or hot). I would suspect this is not your problem since if your environment is extreme enough to perturb the LCD it's probably extreme enough to piss you off too
Bottom line, get a new LCD if none of the suggestions you've seen already fix your problem - the monitor is probably hosed.
BTW (and slightly off topic), for everyone who thinks CRTs are god's gift to monitors please remember they do have their problems too - luminous trails following light objects across black screens can be very irritating, and I'm sure I'm not the only person who accidentally left a magnetic object too close to the screen and wound up with a big purple splotch on the side for a few days...
And THIS, ladies and gentlemen, is why I host MY little blog-like thing on MY OWN site, using MY OWN crappy software. That way I KNOW backups are getting done, and I KNOW when the machine will be down, and if something goes wrong I can fix it MY OWN DAMN SELF.
Sorry if I seem a little callous, but really how hard is it to write a few hundred lines of PHP for a simple online journal with comments? NOT VERY! And it runs on the same machine I use for all my other stuff (DNS, Mail, CVS) so it's not like I'm spending untold thousands extra each month, it really helps make the cost-benefit ratio of my server more tolerable.
Think about it.
Do serial consoles count?
:-D
If so, WYSE WY-60 (doesn't have its year of manufacture on the back plate) and an old Toshiba T-1200 laptop with its monochrome (blue on grey) LCD are the oldest displays I use regularly.
I too have a Sun-Branded Sony monster that outweighs any "modern" monitor... Sad part is these things outperform them all too.
PLUS its a flat CRT
MIT OpenCourseware -- As the parent post said this is a great starting point for any school redesigning their CS curriculum. I'm sure it also has value as add-ons to an IT/IS/MIS curriculum. No mod points - Someone please mod parent up. Thx.
Too right - I am a HUGE proponent of the "if it's broken just reinstall it" school - In many cases it's faster.
:))
On the other hand, sometimes it just IS NOT an option. When I took my current job (almost 5 years ago) I inherited a horribly broken NIS/NFS mess in our UNIX environment -- So broken that if machines needed to be turned off (or on) it had to be done in a specific order or the entire UNIX network would collapse on itself.
Surely blowing everything away and starting over would have fixed the problems, but it would also have taken me months to rebuild since I had no understanding of how the structure came to be the way it was (and my bosses had long since forgotten).
Instead I slowly repaired the mess from within, and within a year we had a setup where almost any machine can be switched off without causing any problems (the main NFS server, for obvious reasons, must remain on.
------------
Of course, there is the problem of HOW to give students this experience. At my school the CS department is not really responsible for its own equipment (a completely seperate issue involving university politics), and as a result if something breaks (like a machine losing its NFS or NIS+ lifeline) our only recourse is "reboot and hope it comes back". We can't even unmount/remount NFS partitions or force the systems to rebind to NIS+.
Many schools actively deny their students the experience of fixing broken systems, and as long as this is standard practice we will continue to get graduates who don't understand that sometimes a big magnet is NOT the best tool for the job.
Sounds to me like your DBA never learned the basics of database design.
In ANY data storage system where there are interrelations between the elements (objects) being stored (this includes the obvious relational systems as well as hierarchical systems) the design phase is always best carried out on paper using some kind of modeling scheme (UML, Entity-Relationship drawings, etc.)
This is the method my company uses to design large-scale databases to support our systems and network management software.
The result? A few whiteboards full of circles and arrows and dotted lines (the intermediate nastyness while we work out exactly who will be related to what in which ways) culminating in a diagram that translates very nicely into the Relational world, and subsequently into the hierarchical world (LDAP ala RFC 2307).
While sometimes staring at the code is the ONLY way to understand something, the importance of a thorough understanding of the reasoning behind the design CANNOT be overstated.
OK, I'm not qualified to give an IT/IS curriculum outline -- What I DO feel qualified to do is suggest a generic CS outline.
As many other posters have pointed out, the outline presented reads like a trade school/training course outline: Learn Cisco IOS. Learn MS Win2K+3. Learn Linux (presumably redhat). Learn MS SQL Server, MySQL, Whatever. Learn VB. Lern Visual C++. etc.
Rather than tying students to a particular product, teach them genericly useful skills.
For example:
Now that they are well-versed in the basics you can start feeding them more advanced topics:
This course would include a BASIC discussion of security.
One of the most important things that any student - IS, IT, CS, Trade School, WHATEVER - needs to learn is HOW TO READ THE F***ING MANUAL -- The great failing of my school is that there are people at my level (seniors) who have been "using" the CS department's UNIX machines (Solaris) for almost four years now who do NOT know about "man" and "apropos".
The things employers (my employers anyway) look for are the ability to THINK and solve problems, and the skills to know where to look to find the answer -- Man pages, news groups, google, etc. are all resources that seem to be wasted on many of my peers. Not knowing where to look is a huge resource sink in the Real World, and will not be helpful to your chances of future employment.
OK, I just need to ask how this is a "shot" at FreeBSD when the developers themselves acknowledged the bugs that are mentioned in the /. story - In fact the release anouncement for the new RC uses the exact same wording.
Am I the ONLY fscking BSD user on slashdot without a persecution complex?
Yet another vote for GoDaddy.com - they seem to be quite popular (and the cheapest I've found to date)
I've never had a problem with them, their interface is (relatively) fast, clean, and easy to understand & use once you get used to it.
I haven't ever needed tech support from GoDaddy yet, so I can't comment on that, but I haven't had any double-billings or anything of that ilk which I have had with other registrars (who shall remain nameless, since nameless sites go there...).
GoDaddy has never bothered me with unsolicited snail or electronic mail, just my usual "Your domain is expiring..." message. They also (I believe, not logged in to my domain interface at the moment) have automatic renewal options now.
My personal patch policy is vastly different from my company patch policy.
Personal machines:
Windows:
Patched whenever the "Automatic Update" critter says I should.
Granted this is a lousy policy, but with a new patch every week I can't be bothered to deal with them all.
UNIX:
Source is CVS'd nightly.
A general "upgrade" build is run every 2 months to keep my systems current with minor bug fixes & other small stuff like that.
When a security advisory comes out for a service I don't use, the patch is applied whenever the next upgrade build is run.
When a security advisory comes out for a service I DO use, I pull down the source tree as soon as a patch is available, then kick off an upgrade build.
In the case of third-party software, ports and the like, the same methodology applies (if I don't run it I ignore it, if I do I patch it ASAP), but I perform the upgrade through the ports system (BSD) or by fetching and rebuilding the source for the appropriate service/package/etc.
At work, the general policy (small office situation so this is very loose) is-
Windows: If it seems OK on our personal machines after a 48 hour wait, the Windows machines in the office are patches.
UNIX: Internal machines are only patched when needed, often this amounts to "never".
External machines are patched as-needed (depending on what services they run, what OS, etc.)
I try not to leave ANY machine (personal or corporate) that is on the internet at large unpatched against any vulnerability for more than a week, even if "patched" just means "disabled service X to prevent exploitation".
Every so often I'll log in to LambdaMOO (lambda.moo.mud.org:8888) just to keep my account alive or to see whats going on.
/~mikeg
I used to be far more active, but as time goes on I have less free time between work and school. Pity really, Lambda is one of the few MUDs I really enjoy because of its multifaceted nature - There are MUD-Like spots with puzzles and interactive 'critters', an RPG that got swallowed (easy access from under the hot tub... creepy), and a huge social area.
Plus there are all those colorful guests...