pkg-devel problem with incremental update

, no need to fetch fresh copy What should I do to make incremental updates possible? -- Michael Gass mg...@csbsju.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo

Re: What is the correct CPUTYPE for this machine?

On Sat, Jun 08, 2013 at 10:10:10AM -0400, ill...@gmail.com wrote: > On 8 June 2013 09:34, Michael Gass wrote: > > > I have an old laptop: > > > > FreeBSD 9.1-RELEASE #0 r243826: Tue Dec 4 06:55:39 UTC 2012 > > r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GE

What is the correct CPUTYPE for this machine?

1 Features=0x383f9ff AMD Features=0xc0480800 What is the correct value for CPUTYPE in make.conf? Thanks, mg -- Michael Gass mg...@csbsju.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.o

Re: Error building math/sage

On Thu, Jun 06, 2013 at 09:41:46AM -0500, Michael Gass wrote: > Trying to build math/sage-5.9_1 from ports. Everything builds > except sage itself. > > Here is the system info. > > FreeBSD dc7800.home.net 9.1-STABLE FreeBSD 9.1-STABLE #0 r251294: Mon Jun 3 > 17:52:11 CD

Error building math/sage

helpful information. WARNING: if you now run 'make' again, the build directory will, by default, be deleted. Set the environment variable SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. gmake: *** [build] Error 1 *** [do-build] Error code 1 Stop

Should I move to amd64 ?

, worse, or the same after the change? I may eventually bring the memory up to 4GB, but not anytime soon. I understand some ports my not work - like WINE - but I do not use WINE. Would there be other problems? -- Michael Gass mg...@csbsju.edu

Should I move to amd64 ?

, worse, or the same after the change? I may eventually bring the memory up to 4GB, but not anytime soon. I understand some ports my not work - like WINE - but I do not use WINE. Would there be other problems? -- Michael Gass mg...@csbsju.edu

Why obsoleted if_watchdog interface ?

I installed an old 3Com network card in my machine (Pavilion 4455) and it works fine, but I get the following warning in dmesg ep0: <3Com 3C509-TPO EtherLink III> at port 0x300-0x30f irq 10 on isa0 ep0: WARNING: using obsoleted if_watchdog interface ep0: Ethernet address: 00:01:02:69:4f:7c ep0: [I

Custom Kernel Problem

# FireWire bus code #device sbp # SCSI over FireWire (Requires scbus and da) #device fwe # Ethernet over FireWire (non-standard!) #device fwip# IP over FireWire (RFC 2734,3146) #device dcons # Dumb console d

Re: Garbled text in xterm

On Mon, Jul 16, 2007 at 03:06:47AM +0200, Nikola Lecic wrote: > On Sun, 15 Jul 2007 19:15:03 -0500 > Michael Gass <[EMAIL PROTECTED]> wrote: > > > Lowell Gilbert wrote: > > > > > Hmm. I've never heard of any symptoms quite like this. > > > A

Re: Garbled text in xterm

construct a configure file for me (Xorg -configure), but same problem. What do you think? Mike Gass > On Fri, Jul 13, 2007 at 10:10:38AM -0500, Michael Gass wrote: > > > > Just installed Xorg 7.2 on an old 486DX cpu machine (Compaq ProLinea) > > running FreeBSD (Just to do it!). O

Re: Garbled text in xterm

construct a configure file for me (Xorg -configure), but same problem. What do you think? Mike Gass > On Fri, Jul 13, 2007 at 10:10:38AM -0500, Michael Gass wrote: > > > > Just installed Xorg 7.2 on an old 486DX cpu machine (Compaq ProLinea) > > running FreeBSD (Just to do it!). O

Garbled text in xterm

ST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension XAccessControlExtension (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extens