Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!howland.reston.ans.net!newsfeed.internetmci.com!in2.uu.net!newsfeed.pitt.edu!jlfox From: jlfox+@pitt.edu (James L Fox) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Packages download problems Date: 21 Jun 1996 14:59:52 GMT Organization: University of Pittsburgh Lines: 38 Message-ID: <4qedd8$eii@usenet.srv.cis.pitt.edu> References: <4q7ecl$jdm@usenet.srv.cis.pitt.edu> NNTP-Posting-Host: unixs-eval.cis.pitt.edu Last week, --> I <-- wrote: > As root, running sysinstall/configure/packages I'm getting the > following error after the program successfully negotiates with > Walnet Creek for an index and me to select bash and tcsh.... > > "DEBUG: Command `(pwd; cat +CONTENTS) | pkg_add -v -S' returns status of 2" > > I get the errors once for each package. > > Anyone know what status 2 means? > Perhaps my question isn't clear. I can't get the "Packages" option from the "FreeBSD Configuration Menu" in the /stand/sysinstall program when I run as root from the console, -- to succeed! It's not a network problem - I'm using the ftp option to Walnut Creek and I'm observing a rich dialog between my machine and theirs via ALT-F2 with the debug option on. For each of three shell package attempts, the dialogue ends as above. Today I tried Netscape 2.xx and got a different error: "DEBUG: FTP: No such file packages/All/netscape-2.0b1.tgz, moving on. DEBUG: pkg_extract: get operation returned -1 DEBUG: Switching back to VTY1" I just read the Ports section of the FreeBSD Handbook and observed the disclaimer about availability at the ftp sites. Is this my problem - bash, tcsh, zsh, and netscape are JUST NOT AVAILABLE? My boss is getting impatient and the unopened shrink wrapped box labeled "Windows NT Workstation" that he gave me is starting to look more inviting with each hangup. I don't want to bail out of FreeBSD (Apache is working great) but I must get it all wired together asap. Any help would be appreciated... > Thanks, > --Jim Fox >