Re: Heads up! config(8) changes..

> >> What do you do about the "ppc" device? Formerly, it needed to be "net > >> irq ..." if the "plip" device was going to be used, but "tty irq ..." > >> otherwise. Which one did you pick? > > > >It needs to flip between one or both, but I can't raise Nicolas lately, > >so I'm starting to fear

Re: disk slices and MAKEDEV confusion

> > > > The problem is that if you made all of the nodes for all of the > > supported slices, /dev would be incredibly bloated. There are 8 > > potential nodes per slice, and 20 potential slices per disk, plus the > > compatability slice, so that's 168 node pairs (raw and buffered) > > _per_di

Re: disk slices and MAKEDEV confusion

> > The problem is that if you made all of the nodes for all of the > supported slices, /dev would be incredibly bloated. There are 8 > potential nodes per slice, and 20 potential slices per disk, plus the > compatability slice, so that's 168 node pairs (raw and buffered) > _per_disk_. > Acc

Vortex sound support in FreeBSD

I was just wondering if anyone has gotten a soundcard based on the Vortex chip to work under FreeBSD. I know that OSS (www.opensound.com) supports it, but I don't want to use OSS because of the problems with it. If nobody has gotten that card to work, then can someone point me in the right directio

process getting stuck in objtrm at exit

On recent -currents, one of our users has managed to wedge a job in objtrm when its exiting. Anybody know what's causing this? I've appended a stack trace of the offending process, as well as a printout of the offending object. The machine seems otherwise healthy. I don't really understand

Mounting CD-ROM as root

I've been trying to mount a CD-ROM as root on FreeBSD so as to have a self-contained demo of a project that I could run anywhere. However, I found that the "-C" option was apparently being ignored by the new boot loader. The following patch fixed the problem: --- sys/boot/i386/libi386/bootinfo.c

natd as a 'routing daemon'

Just a thought... Might it not be logical to put natd in the 'routing daemons' section of the boot process? That would start it before things like quota checking, which can take a lot of time and prevent a combination worgroup server/NAT box from providing network access, even when it could

Re: disk slices and MAKEDEV confusion

On Mon, 24 May 1999, Mike Smith wrote: > > I am confused! > > > > The /boot/loader is "announcing" that it wants the root device to be > > "da0s1a". > > > > It appears that the "normal" fstab entries want "sliced" versions as well, > > eg. > > # DeviceMountpoint FStype Opti

Effect of compiler options on performance

I have recently done a series of tests using the HINT benchmark () to see whether various compiler options have any useful effect under EGCS. Unsurprisingly, the only option which has any effect at all on this benchmark is `-ffast-math'. See a graph at

Re: disk slices and MAKEDEV confusion

> I am confused! > > The /boot/loader is "announcing" that it wants the root device to be > "da0s1a". > > It appears that the "normal" fstab entries want "sliced" versions as well, > eg. > # DeviceMountpoint FStype Options Dump > Pass# > /dev/da0s1b none

Re: calcru and upages

On Mon, May 24, 1999 at 08:13:57AM +0800, Peter Wemm wrote: > I'd also like to implement a proper clone(2) ala Linux. We have most of > the infrastructure in place already, using that and comparing with NetBSD's > take on the subject should be fairly useful in the end. The main > difference betw

Re: ethernet card problems

Hello, Honestly, FreeBSD-current is not what you want if you're having this sort of problem. -current is for people who want to read C code, debug device drivers, and who are perfectly willing to have their system, hardware, and or software destroyed by bugs. Since the machine in question connec

Re: Heads up! config(8) changes..

On Thu, Apr 29, 1999 at 10:26:48PM -0700, Mike Smith wrote: > >> In article <19990424190901.d3a791...@spinner.netplex.com.au>, >> Peter Wemm wrote: >> > This shouldn't cause much in the way of trouble, but it will complain >> > about old lint in your config files. That includes 'net/tty/bio/cam'

Re: ed0 not recognized (even tried it as ed1)

On Mon, 24 May 1999, Doug Rabson wrote: > On Sun, 23 May 1999, Bill Pechter wrote: > > > Following my latest rebuild (make world on Friday, make of kernel > > on Friday) -- I can no longer find my ed0 (WD 8216) network card. > > > > dmesg.yesterday:ed0 at port 0x280-0x29f iomem 0xd8000-0xdbfff i

Re: ed0 not recognized (even tried it as ed1)

On Sun, 23 May 1999, Bill Pechter wrote: > Following my latest rebuild (make world on Friday, make of kernel > on Friday) -- I can no longer find my ed0 (WD 8216) network card. > > dmesg.yesterday:ed0 at port 0x280-0x29f iomem 0xd8000-0xdbfff irq 10 on isa0 > dmesg.yesterday:ed0: address 00:00:c0