Re: 4.4-STABLE hanging problem with ibm thinkpad laptop

On 2001.11.03 23:08 Jason Hunt wrote: > I have an IBM Thinkpad 560E laptop. I was running a 4.4-STABLE from > September, and it was great. I cvsup'd to 4.4-STABLE on November 3rd, > and > now when I reboot or shutdown, it kills daemons, synch's disks, and > shows > the uptime. Normally it woul

4.4-STABLE hanging problem with ibm thinkpad laptop

I have an IBM Thinkpad 560E laptop. I was running a 4.4-STABLE from September, and it was great. I cvsup'd to 4.4-STABLE on November 3rd, and now when I reboot or shutdown, it kills daemons, synch's disks, and shows the uptime. Normally it would either reboot or turn the machine off, or tell yo

Re: ICQ and NAT again.. :(

Andreas Ntaflos wrote: > On Fri, Nov 02, 2001 at 09:21:05PM -0500, Allen Landsidel wrote: > >>To be able to open a TCP connection to port 5190 on login.icq.com > > Does this work for file transfers too? /me doesn't think so. File transfers > require direct connection, that's what the range of li

Re: ICQ and NAT again.. :(

At 04:08 AM 11/4/2001 +0100, you wrote: >Does this work for file transfers too? /me doesn't think so. File transfers >require direct connection, that's what the range of listening ports are for >if I am not completely mistaken... I haven't tried one in ages to be honest, but I don't really feel

Re: Crash Using ogle

> I did a little digging, and it's still not immediately obvious to > me why the crash occurs (this is only the first time I've looked at > that code). The "quick-and-dirty" (and probably wrong) solution may > be to increase the value of ATA_DMA_ENTRIES, but I'm not sure what > side effects t

Re: ICQ and NAT again.. :(

On Fri, Nov 02, 2001 at 09:21:05PM -0500, Allen Landsidel wrote: > To be able to open a TCP connection to port 5190 on login.icq.com > > After that, it needs nothing. Configure it to use no listening ports, and > it will use none and work just fine by transferring messages through the > server

Re: Crash Using ogle

On Sun, 28 Oct 2001, Heath Nielson wrote: > On Sunday 28 October 2001 05:40 pm, Chris BeHanna wrote: > > I attempted to view a DVD with the ogle port (nice DVD menu > > support), and I crashed my machine (4.4-STABLE, cvsup'd at > > Fri Oct 19 01:08:36 EDT 2001). There was no crashdump, but t

Ports spawning thousands of makes...

Does anyone know why when I go to build a port the last 2 days after a fresh stable world those 2 days, make spawns thousands of makes and wedges my box till I ^C the port build? portupgrade does it, and any port I build does it. World builds just fine. I'm assuming one of the ports Mk files is o

Re: /usr/src/UPDATING

: * Bill Fenner's code to make ipfw/dummynet/bridge KLD'able : : BOTH THESE THINGS REQUIRES REBUILDING OF ipfw.ko and /sbin/ipfw : :I am not sure if that should be added to UPDATING. After all, it was not :added to -CURRENT's /usr/src/UPDATING neither ;-) : : Regards, : JMA :-- Wheneve

Re: /usr/src/UPDATING

On Sat, Nov 03, 2001 at 09:11:36AM -0800, Bruce A. Mah wrote: > If memory serves me right, "Jose M. Alcaide" wrote: > > Hmmm... what about dirpref and UFS_DIRHASH? And the recent MFC of ipfw > > also comes to my mind. > > UPDATING lists potential breakages: > > This file contains a list, in re

sysinstall/disklabel and auto-default values for partition sizes

Hello, Sysinstall(disklabel) still chooses a size of 20 MB for the /var partition. This is, in my opinion, way too small since the installing of packages uses /var/tmp (maybe adding a separate /var/tmp partition to the defaults would be interesting?). I've mentioned this also before the 4.4-RELE

Re: strange mail(1) behavior

The problem is fixed, thanks to everybody responded. It's all about "metoo" option for the mail(1). I didn't expect mail(1) to do alias expansion on its own. I thought it was done by mail.local, which in its turn was reading sendmail.cf Also, the man page for mail(1) is somewhat confusing:

Re: Burncd errors...

In local.freebsd.stable you write: >On Wed, 31 Oct 2001, Mikko Tyolajarvi wrote: >> >acd0: CD-RW at ata1-master using PIO4 >> >> Not that it is any help to you, but I have the same problem (data >> burns ok, audio does not) with an 8083B. And apparently we're not >> alone: