Slashdot Mirror


User: RassilonOmega

RassilonOmega's activity in the archive.

Stories
0
Comments
4
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 4

  1. Relevant Links on David Tennant Cast as New Doctor Who · · Score: 0, Flamebait

    Official BBC Announcement: http://www.bbc.co.uk/doctorwho/series.shtml Official Doctor Who Homepage: http://www.bbc.co.uk/doctorwho/ Official Questional Legality Distribution Site: http://www.btefnet.net/index.php?show=129 [Posting Disclaimer] I claim no responsibilty for anything I do, especially posting links in SlashDot. If anyone asks, a computer virus did it. It was them "bad hacker" persons. I am not guilty. Additionally, I do not recommend any illegal activity, particularly if I think I will get caught.

  2. Re:[OT] The court hearing today on SCO Adds Copyright Claim to IBM Suit · · Score: 1

    Eek! I mistyped my command line...I knew I should have posted while I was at work!

  3. Re:[OT] The court hearing today on SCO Adds Copyright Claim to IBM Suit · · Score: 1

    There are indeed plenty of ways to do it.
    Personally, I did:
    grep -rc "\$" linux-2.6.1 | gawk -F: > line_counts.txt

    Then summed it in OpenOfficeOrg (couldn't think of a commandline summation tool). I counted 5.9+ million lines and mine included makefiles and various other trash from my kernel build.

  4. If I was a student...I would prefer... on Handling User Grown Machines on a Large Network? · · Score: 1

    I know that I wouldn't want some person I do not know "examining" my computer for patches, etc. nor would I want said person to knock on my door early some Sat. morning saying "Oh, you have that new virus, I'm hear to fix it. Point me at your computer and give me your password."

    I think the only reasonable way to handle the issue is to detect and block access for infected computers. When the user calls, inform them whey they were blocked and give them their options to fix the problem:

    * Patches...lots of patches...
    * Anti-Virus and a well controlled Firewall...
    * Trust the campus tech...

    The last option would of course have to be a very strange agreement where the college guarantees nothing, but will do their best.

    Also, each semester, give out a leaflet about basic computer security / maintainence...on the back do the whole scary statistic things that always gets managers at work to buy things (you know: vulnerabilities found in the last 6 months: x for windows, y for linux, z for Mac OS...Number of new viruses in the last 6 months: a for windows, b for linux, c for Mac OS) Also, providing a option to sign up for a campus email about new vulnerabilities and worms may help.

    I have noticed that some people keep saying "install *nix"...This does not stop future problems. It just reduces the number of current worms and adds to the confusion of most users.