Slashdot Mirror


User: estate

estate's activity in the archive.

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

Comments · 7

  1. No recent mention of SCO and on Subdomains Part Of The Patent Frenzy · · Score: 0, Redundant

    Ideaflood just isn't in their league

  2. Re:What about other carbon arrangements? on Buckyballs Kill Fish · · Score: 1

    You can get the story elsewhere - http://tinyurl.com/2bw9b

    No registration required on eurekalert.

  3. Darl for President on SCO Lobbying Congress Against Open Code · · Score: 1

    'nuff said.

  4. Re:The Danger of Congress on SCO Lobbying Congress Against Open Code · · Score: 1

    And some state legislature passed (or came close to passing) a bill specifying that Pi equals three.

  5. Re:Dear Apple: why? on HP Licenses Apple's iPod & iTMS · · Score: 1

    Apple gains a lot from the agreement with HP. According to CBS Marketwatch (see
    http://tinyurl.com/2yqf4) Phil Schiller, Apple's senior vice president of worldwide product marketing is reported to have said that "the multi-year exclusive deal has Apple building the players with the H-P name and in colors that are more familiar to H-P's product line".

    Since Apple is building the HP iPods, it will benefit from the economies of scale in producing the additional units. This in turn will result in either lower prices down the road (consumers benefit) or better margins for Apple or some combination of both.

    And the HP version of the iPod will not suck, since it is essentially a re-badged iPod.

  6. Re:SCO Sued By SCO For IP Infringement on SCO Drops Linux, Says Current Vendors May Be Liable · · Score: 1

    If SCO wins this suit, does this mean that they will write themselves a check?

  7. This is nothing new on Sprint DSL's Security Hole Easy As 1,2,3,4 · · Score: 5, Interesting

    Use of the default password has been going on since time immemorial. Apparently Richard Feynmann who worked on the Manhatten Project (which developped the first atom bomb) had a reputation as an expert safecracker because very few people on the project changed the combination of the safes from the way it had been programmed at the factory.

    Perhaps the problem arises because we have so many passwords to remember. My solution is to have one password for most of my accounts, which I share with nobody. This led to a nasty family argument, when I refused to tell my passwword to my daughter so that she could logon to my linux box at home. That was solved by giving her an account of her own.

    Another possibility is that most people are simply unaware of the need for security. I got a taste of this when I taught an introductory course on Unix to a group at one company who shared files with each other. When I asked how they did it, they told me that each one of them posted a little yellow sticky with their userid and password on their monitors so whoever had to could simply log on as them!!