Slashdot Mirror

← Back to Stories (view on slashdot.org)

HP Lays Off Unix/IA-64 gurus

Posted by Hemos on from the bad-times-for-everyone dept.

A reader writes "On Tuesday HP announced that it is closing a lab in NJ. This was an HP-UX development lab, responsible for porting HP-UX to IA64. The lab employed top engineers, including some who have worked in Unix kernels for over 20 years (originally from Bell Labs, Novell, and other companies). " That report came from a soon-to-be former employee.

6 of 341 comments (clear)

  1. Still no HP icon???? come on guys! by Gameshow+Bob · · Score: 0, Offtopic

    I'll even send one to you!

    --

    You Like Science?
    You Like bottomquark.
  2. DMCA in action by twitter · · Score: 0, Offtopic
    So if someone breaks your anti-copying technology, are you going to sue?

    The Digital Millennium Copyright Act prohibits users from circumventing copy protection. It's now a crime in America to do that.

    There you have it. Fair use is now illegal.

    --

    Friends don't help friends install M$ junk.

  3. Too bad the Apple zealots used up their mod points by Anonymous Coward · · Score: -1, Offtopic

    With all those recent Apple stories running around, they ran out of mod points to obliterate you. Sucks for them.

    Not that anyone else has any points left either, after the VIM article (article about VIM, yes, that's what it was, I won't fall into the trap of listing one text editor in front of the other or vice versa - or verse vica, or whatever ;).

  4. assembly woes by Anonymous Coward · · Score: -1, Offtopic


    I have been using tasm+tlink for a DOS app that I am writing but it turned out i needed MMX support and that forced
    me to change my assembler. I chose nasm because I have been using it before in my other programs. I am still linking
    everything with tlink.

    The problem is: Everything compiles and links without warnings and usually runs but I can't link the debug version
    correctly - if I do: nasm16 -f obj -g myfile.asm tlink /zi myfile.obj I get some messages
    about wrong segment offsets and don't get any executable (if I exclude -g and use tlink /x everything is fine)

    Other thing I found out is that the code mov ax,seg variable mov ds,ax mov di,var loads ds:di with different (however
    valid) segment and offset than equivalent tasm code. My question is: what should I do to make nasm produce object
    files that exactly match ones produced with tasm, so that I can link debug executable and don't get these segment/offset
    differences?

  5. Re:The downward spiral continues by Anonymous Coward · · Score: -1, Offtopic

    YHBT YHL HAND

  6. LAYOFFS by SirPsychoSexyMD · · Score: 0, Offtopic

    I am a recent computer science graduate and I have been laid off from my job. It has been three months now and I still haven't found a new job. I wonder if some of you guys know where there are developer jobs out there. I'm getting a little depressed. I graduated with high honors. But because I only have a year of experience, I cannot qualify for the mid-level positions. I also do not know where to find entry-level jobs because I do not qualify for on-campus interviews anymore. I need a little help. Someone point me to the right direction.