Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!decwrl!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.questions Subject: Re: XV version 3.0 Date: 29 Oct 1993 20:48:39 GMT Organization: Montana State University, Bozeman MT Lines: 54 Message-ID: <2arvj7$ika@pdq.coe.montana.edu> References: <RUSSO.93Oct29085933@bogon.lanl.gov> NNTP-Posting-Host: bsd.coe.montana.edu In article <RUSSO.93Oct29085933@bogon.lanl.gov>, Thomas Russo <russo@lanl.gov> wrote: > >Ok, I'm running this really old version of 386bsd (0.2.1 patchkit and >XFree86 1.2!) but every time I think of upgrading I decide to put it >off for a while because my current setup works Just Fine for me. >Except right now. Does anybody have the XV image viewer/manipulator, >version 3.0, compiled on a FreeBSD box WITH the tiff library >installed? Hmm, I've got a version of xv3.0 compiled for FreeBSD, but I got it from someone else, and I dont' have any tiff files to check it on. > My version of 386bsd, with it's gccosaurus 1.39 chokes on >the file tif_fax3.c because it runs out of virtual memory (I've got >8Mb of ram, 20Mb of swap) while reading the header file g3states.h, >which contains some *huge* initializers. FreeBSD is much better about such things. (And even gcc2 isn't too bad when compiled with the gnumalloc routines). >Is this something I can expect to gain from upgrading to FreeBSD and >XFree86 1.3? Or is there a bug in the tiff libraries mkg3states >program which causes it to generate wierdness? Or what? See above. I suspect highly that if you can't compile it on your machine, you could probably find a nice FreeBSD person to compile it for you. *grin* >(I don't want to spark a discussion of all the other things I'd gain >by upgrading right away. I'll upgrade, it's just a matter of when and >to what version. Besides, I'm running a slightly crippled system; I >don't have a tape backup, just floppies, so if I break my installation >by upgrading to FreeBSD, I have to go back to the OLD 386bsd-0.1 >distribution disks+patchkits... Ouch. Better to suffer the slings >and arrows of outrageous bugs...) I'm not sure if you tried my upgrade script, but I just squashed the last of the bugs in it last week. It now works correctly with the EPSILON release, and will only require one slight change for the final release. (The directory structure has changed a teeny bit, so I need to upgrade the mtree files to the final versions) It actually WORKS in upgrading your 386BSD machine to FreeBSD. Nate -- nate@bsd.coe.montana.edu | Freely available *nix clones benefit everyone, nate@cs.montana.edu | so let's not compete with each other, let's work #: (406) 994-4836 | compete with folks who try to tie us down to home #: (406) 586-0579 | proprietary O.S.'s (Microsloth) - Me