>On Thu, 27 Aug 98 13:33:44 -0600, Jeff Woolley wrote:
>> 
>> I'm running NetBSD 1.3 (GENERIC) #56 on a SE/30 with 32MB RAM.
>> 
>> What is the best way to install software? I want to get GhostScript 
>> working with my HP Desk Writer.
>
>I'm not sure if HP DW driver's built in, but you could install the GS
>precompiled binary pkg.  It is found at:
>
>ftp://ftp.NetBSD.ORG/pub/NetBSD/packages/1.3.2/m68k/All/ghostscript-5.10.tgz
>
>You can directly install it by specifying this URL as the argument to
>pkg_add command.  Ur, wait.  Since you're running 1.3, this binary
>might have trouble running on your system though I'm not sure it will.

Is the pkg_add command different than using the pkgsrc stuff, i.e., going 
to the directory that the package is in (cd 
/usr/pkgsrc/print/ghostscript5) and typing make. This downloaded other 
packages/libs that where need for ghostscript. I don't think it was a 
binary, since it was compiling it.

How hard is it to upgrade to 1.3.2?

>> In an attempt to install GhostScript I type
>> 	
>> 	   cd /usr/pkgsrc/print/ghostscript5
>>    	make
>> 
>> After downloading, while the script is extracting some of the files, I 
>> get the following
>> 
>>    	gzip: stdout: Broken pipe
>> 	   /usr/bin/tar: child returned status 1
>> 	
>> Was something not extracted properly?
>
>Quite likely, yes.  It may be safer to redownload the distfile.
>
>> During the compile of GhostScript, the machine crashed.
>> 
>>     panic: cleaned vnode isn't stopped at _Debugger+0x6: unlk a6
>>     db>trace
>>     _Debugger(0,8b7ccc,3f6b4,3f59c,3f58e) + 6
>>     _panic(3f58e,6c43380,0,408) + 40
>>     _getnewvnode(1,6c0ee00,6bf9200,8b7d0c) + e0
>>     _ffs_vget(6c0ee00,2443,8b7d90) 60
>>     _ufs_lookup(8b7e00) a46
>>     _lookup(8b7e9c) + 23e
>>     _namei(8b7e9c) + 152
>>     _sys___lstat13(6c3a200,8b7f88,8b7f80) + 2c
>>     _syscall(118) + 13e
>>     _trap0() + e
>>     db>
>> 
>> What happened?
>
>I'm not sure but this is weird...  The panic message isn't even
>complete.  However, if fsck after reboot finds nothing wrong with your
>filesystem, it's probably OK.

I copied it from the screen, but that's all that was there.

It stopped in single user and said run fsck_ffs manually. I did, and 
answered yes for everything that was messed up.



__
Jeff