stable vs. current question

The handbook sez: > What is FreeBSD-current not? [...] >3.In any way ``officially supported'' by us. We do our best to > help people genuinely in one of the 3 ``legitimate'' FreeBSD-current > categories, but we simply do not have the time to provide > tech support for it. This

Re: 3.2-RELEASE Feedback

Randall Hopper wrote: > 8) (Nit) Boot-up probes spelling error: >"bt_isa_probe: Probe failled for card at 0x330" > > 9) rc.firewall - if firewall_type is a file, it feeds each line in it to >ipfw. > >BUT ipfw doesn't toss comments, so you can't document your firewall >commands,

Re: PR broken? was Re: Linux not FreeBSD?

Cy Schubert - ITSD Open Systems Group wrote: > > In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav > writes: > > Everything journalists write is true, except when they write about > > something you know. > > > > DES > > -- > > Dag-Erling Smorgrav - [EMAIL PROTECTED] > > Your comment should be

3.2-STABLE unable to stably run NEWEST INN Code...

Due to heavy usage of MMAP() in the newest INN's, 3.2-STABLE is unable to handle the load of a full news server :( The last I heard, Matt Dillon knew about and was planning on working on ~6 MMAP() related race conditions...with the latest decision by "the Core" concerning his commit privileges,

Re: NFS hanging in 3.2-STABLE

Robin Melville wrote: > While I'm happy to always use tcp mounts I wonder whether something is > quite badly wrong with the kernel nfs code, Yes, that's about the size of it. Fortunately these problems are A) old, B) well-known, and C) being worked on in -current. When the fixes are stab

Re: PR broken? was Re: Linux not FreeBSD?

In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav writes: > Everything journalists write is true, except when they write about > something you know. > > DES > -- > Dag-Erling Smorgrav - [EMAIL PROTECTED] Your comment should be incorporated into the fortune database. Regards,

Re: kern/10411: top, vmstat, iostat show 0% cpu idle & usage on SMP system

On Sat, Jun 05, 1999 at 03:49:29PM -0700, Andrew W. Flury wrote: > > FYI, this problem also exists if you have APM enabled in your BIOS setup but > not enabled in your kernel. Disabling it in the BIOS is one way to fix it > (it's enabled on ASUS P2B boards by default). Hmm, well I tried Danny

Natd unrecognized command

I am trying to get a VPN to a Machine on my local network from another outside machine. When I type the following: natd -pptpalias 192.168.2.7 Here is the response I get: natd: unknown option pptpalias Did I miss something.. It is there in the man page. The box

3.2-R mount lockup

3.2-RELEASE still locks the system hard when a file system is mismounted, just as 3.0-RELEASE did: # mount /dev/wd4s1 /mnt - fails with incorrect superblock (it's a FAT partition) # mount -t msdos /dev/wd4s1 /mnt - locks the system hard If you omit the first (incorrect) moun

3.2-R Disk Performance Woes

When copying directory trees between two IDE drives on the PCI bus, the system really dogs down -- emacs takes 15 seconds to come up when normally it takes 1 -- didn't do that on 3.0-RELEASE. I have these drives configed up for DMA: controller wdc0at isa? port "IO_WD1" bio irq 14 fla

NFS hanging in 3.2-STABLE

I searched the mailing list for clues on this with no luck. Running 3.2-STABLE on a variety of garage-sale pentium I and K6 boxes with and without scsi I almost always get hung and unkillable userland processes when they are reading writing NFS shares mounted over udp. Mounting -otcp always works