Slashdot Mirror

← Back to Stories (view on slashdot.org)

FreeBSD 4.4-RELEASE Is Ready

Posted by Nik on from the coming-full-circle dept.

ocipio writes: "The FreeBSD team announced that 4.4-RELEASE is available for download. There are a whole bunch of changes and notes. Please be sure to use a mirror." Those installing for the first time will no doubt find chapter two of the Handbook invaluable.

6 of 267 comments (clear)

  1. Wow... by Anonymous Coward · · Score: -1, Offtopic

    Wow.. this article was up for a good 5 minutes without even a FP!

    Guess no one cares.

  2. 4.4 by Anonymous Coward · · Score: -1, Offtopic

    yay!

  3. Wow... by Anonymous Coward · · Score: -1, Offtopic

    Wow again. Past 10 minutes, and not even a troll. BSD *is* dying!

  4. Should have waited... by turbine216 · · Score: 1, Offtopic


    the developers should have delayed this release until October so they could steal some of WinXP's thunder...

  5. The women's locker room by Anonymous Coward · · Score: -1, Offtopic

    What will you see in the women's locker room? You will see fat jodhpur thighs and cellulite buttocks which look like buckets of spoiled cottage cheese. You will see asymmetrical lop-sided breasts with hairs growing out of the nipples. You will see industrial size panties stretched over roly-poly guts. You will see hairy unshaven ape-like underarms. You will see various residues of menstrual fluid stains and paraphernalia. That is what you will see in the women's locker room.

  6. 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?