ipfilter and ipfstat

Okay, so I finally decided to take the plunge and check out ipfilter. ipf seemed to load my ruleset with no problems, but ipfstat dies with: ioctl(SIOCGETFS): Invalid argument I have remade the 'ipl' target in MAKEDEV, and my kernel and userland are in sync. I have options IPFILTER and options I

Re: Missing ATAPI CD

It seems Kris Kennaway wrote: > Since the most recent round of ATA updates, my CDROM is no longer even > probed at boot time. > > deviceata0 > deviceatadisk0 > deviceatapicd0 > options ATA_STATIC_ID > I know of this, it should be fixed in my

int10?

Is there a way to initialized a vga card after the system is booted? What I am looking for is to initialize a second vga in my system so that I can run X in a dual headed configuration with XFree86 or to be able to chose which vga card to run X with on my system. Tnks -- Amancio Ha

Re: bzip2 in src tree

David O'Brien <[EMAIL PROTECTED]> wrote in list.freebsd-current: > On Sun, Jan 23, 2000 at 10:26:48AM +0100, Oliver Fromme wrote: >> >> Saving 10% or 20% on disk space is not worth wasting >= 10 times more >> CPU time than gzip. Disk space is cheap nowadays, but upgrading to a >> CPU that is

VESA modes broken in syscons driver

Hi, It seems that recent kernels have problems initialising syscons in VESA pixel modes. Particularly "vidcontrol VESA_800x600" (actually "vidcontrol VESA_800x600 < /dev/ttyv1" to see what's going on ttyv0) command make my kernel panicing with the following output: Fatal trap 18: integer divide

gimp 1.1.15 & -current

Hi, I've build gimp-1.1.15 (some minutes ago) on -current (cvsuped yesterday) and I'm getting sigsegv's after the parsing of the plug-in's. Anyone seeing this too? ---snip--- (150) netchild@ttyp0 > gimp gimp: fatal error: sigsegv caught gimp (pid:90581): [E]xit, [H]alt, show [S]tack trace or [P]r

Re: VESA modes broken in syscons driver

>It seems that recent kernels have problems initialising syscons in VESA pixel >modes. Particularly "vidcontrol VESA_800x600" (actually "vidcontrol >VESA_800x600 < /dev/ttyv1" to see what's going on ttyv0) command make my kerne >l >panicing with the following output: [...] >Looking into nm /kernel

[PATCH] Please test the PS/2 mouse driver patch

I wrote a patch for the psm driver to add support for several PS/2 mice. It is in http://www.freebsd.org/~yokota/ps2mice-24Jan2000.tar.gz. I am attaching README included in the patch. Thank you. Kazu -- PS/2 mouse driver patch

problem of burncd

Hi,there I install FreeBSD-current-2122. I tried to write CD-R with burncd, but writing of CD-R is failed at the 'fixate' sequence. At the same time, I got the next error message. The message is "burncd: ioctl(CDRIOCCLOSEDISK) : Device busy". Then, I add "sleep(10);" in 'fixate' code of burnc

APM still ignoring DEVICE_SUSPEND errors

The following patch fixes two things: First, DEVICE_SUSPEND errors are no longer ignored. Since we have defaults for methods we should no longer ignore these errors. Also, DEVICE_RESUME wasn't done when the apm_suspend_system event failed. Second, in the ordering of DEVICE_* and apm_hook_* is no

Re: VESA modes broken in syscons driver

Kazutaka YOKOTA wrote: > >It seems that recent kernels have problems initialising syscons in VESA pixel > >modes. Particularly "vidcontrol VESA_800x600" (actually "vidcontrol > >VESA_800x600 < /dev/ttyv1" to see what's going on ttyv0) command make my kerne > >l > >panicing with the following outp

Re: problem of burncd

It seems Yosuke Koshino wrote: > Hi,there > > I install FreeBSD-current-2122. > I tried to write CD-R with burncd, but writing of CD-R is failed > at the 'fixate' sequence. At the same time, I got the next error > message. > The message is "burncd: ioctl(CDRIOCCLOSEDISK) : Device busy". > The

Re: Moused hanging...

Kazutaka YOKOTA wrote: > What type of mouse is it, PS/2, serial, or USB? Is the power supply > in your system big enough? Is the mouse's cable and connector look > OK? Well, it's an ISA bus mouse. I bought this thing back in 1994. It's an IMSI mouse. I'll bet this stupid thing could last f

Re: problem of burncd

"Soren Schmidt <[EMAIL PROTECTED]>" wrote: > > The message is "burncd: ioctl(CDRIOCCLOSEDISK) : Device busy". > > Then, I add "sleep(10);" in 'fixate' code of burncd.c. > > You didn't get any other error messages ?? I didn't get no other error message. > Hmm, acd_close_track waits uptil 5 mins f

Re: Please help spread the CVSup mirror load more evenly

At 4:43 PM -0500 2000/1/21, Garance A Drosihn wrote: >>And to my best knowledge, BIND does not support anything >>like that. > > Not directly, but I think there are ways you can have it call > some external procedure to do "load-balancing" for an IP > rotary. We talked about doing this to add

Re: Please help spread the CVSup mirror load more evenly

At 5:07 PM -0500 2000/1/21, Louis A. Mamakos wrote: > As John mentioned earlier, what your probably most interested in is > patch quality (e.g., minimum packet loss) first and latency second as > far as network characteristics are concerned. Simply measure them if > you choose rather than tr

Re: Please help spread the CVSup mirror load more evenly

At 5:23 PM -0800 2000/1/21, Rodney W. Grimes wrote: > You don't even need to modify the protocol. Just write a small > tcp program that times the 3 way handshake on open to all the > servers, take the one with the sortest time and spit that out > for the user to stuff in his cvsupfile.

Re: Please help spread the CVSup mirror load more evenly

At 10:00 PM -0700 2000/1/21, Warner Losh wrote: > Hmmm. A thought just occurred to me. There's no need to measure > these things. Lookup all the IP addresses. Do a non blocking > connection to each of these machines. First one to come back with the > REL16_1 response wins, and all the ot

Re: Please help spread the CVSup mirror load more evenly

At 11:34 PM +1300 2000/1/22, Joe Abley wrote: > This should give you a relative performance metric between the servers > you measured, hopefully with local network performance variations > cancelled out by the fact that all tests are run around the same time. This is a really cool ide

Re: bzip2 in src tree

At 12:16 PM +0100 2000/1/24, Oliver Fromme wrote: > Using bzip2 for the FreeBSD distribution sets would increase > the minimum memory requirement by 4 Mbyte (or about 2.5 Mbyte > using the -s option of bunzip2, but which doubles decompression > time). I really don't see what everyone

Re: sigisempty?

* From: Bruce Evans <[EMAIL PROTECTED]> * The correct answer seems to be "you can't do that" :-). Even checking Err. Now why am I not surprised that you said that? ;) Anyway, I have committed the following patch submitted by Alexander Langer. It has a nice feature of working for both -curr

Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches)

On 23/01 22:36, David O'Brien wrote: > BUT, if we bzip2'ed the base system distribution, we'd be able to fit > more Packages on the 1st CDROM, and that is a BIG win. With it in the This would indeed be good. Let's also remember that 'tar' has built-in support for bzip2 so it's not as if it wou

Re: problem of burncd

It seems Yosuke Koshino wrote: > "Soren Schmidt <[EMAIL PROTECTED]>" wrote: > > > The message is "burncd: ioctl(CDRIOCCLOSEDISK) : Device busy". > > > Then, I add "sleep(10);" in 'fixate' code of burncd.c. > > > > You didn't get any other error messages ?? > I didn't get no other error message.

Re: Please help spread the CVSup mirror load more evenly

> I'm hatching in my head a scheme as follows: you may want to take a look at keith moore's work on what he called sonar. there was code, but the internet draft seems to have expired. keith is usually available at Keith Moore <[EMAIL PROTECTED]>. randy To Unsubscribe: send mail to [EMAIL PROT

Powerhousepress.com Press Release

{\rtf1\ansi\deff0\deftab720{\fonttbl{\f0\fswiss MS Sans Serif;}{\f1\froman\fcharset2 Symbol;}{\f2\fswiss\fprq2 Arial;}} {\colortbl\red0\green0\blue0;\red0\green0\blue255;} \deflang1033\pard\plain\f2\fs20 FOR IMMEDIATE RELEASE: \par \par \par CONTACT: \par Jeannette Guillermo \par Powerhousepress

4.0-release (ports) schedule

Hi, Since the 4.0 release is coming up soon, I'd like to remind people to check the build logs and fix what they can. The latest one is in http://bento.FreeBSD.org/errorlogs/errorlogs/e.4.2123/ There are over 200 broken ports. In particular, there are a few dozen (78 at last count) brok

Re: sigisempty?

On 24 Jan 2000, Satoshi - Ports Wraith - Asami wrote: > Anyway, I have committed the following patch submitted by Alexander > Langer. It has a nice feature of working for both -current and > -stable without any additional #ifdef's. I hope it's ok. > > Satoshi > === > --- lib/libxview/notif

Re: Please help spread the CVSup mirror load more evenly

Why don't we use the download accelerator (http://www.lidan.com/) methodology and make simultaneous connections to the top 4 sites as discovered by ping? :) On Mon, 24 Jan 2000, Brad Knowles wrote: > At 5:23 PM -0800 2000/1/21, Rodney W. Grimes wrote: > > > You don't even need to modify the

Re: int10?

> > Is there a way to initialized a vga card after the system is booted? > > What I am looking for is to initialize a second vga in my > system so that I can run X in a dual headed configuration > with XFree86 or to be able to chose which vga card > to run X with on my system. The Linux folks c

Re: sigisempty?

Thus spake Satoshi - Ports Wraith - Asami ([EMAIL PROTECTED]): > Langer. It has a nice feature of working for both -current and > -stable without any additional #ifdef's. I hope it's ok. I now saw Garret Wollman's function. I like the use of the static-vars. The use of sigemptyset makes it mo

Re: Please help spread the CVSup mirror load more evenly

Brad Knowles wrote: >At 4:43 PM -0500 2000/1/21, Garance A Drosihn wrote: > >>>And to my best knowledge, BIND does not support anything >>>like that. >> >> Not directly, but I think there are ways you can have it call >> some external procedure to do "load-balancing" for an IP >> rotary. We t

Re: Please help spread the CVSup mirror load more evenly

At 10:23 AM -0500 2000/1/24, Mr. K. wrote: > Why don't we use the download accelerator > (http://www.lidan.com/) methodology and make simultaneous connections to > the top 4 sites as discovered by ping? :) As mentioned before, not all sites allow ICMP packets through their networks.

Re: rtld-elf, java + tya

In article <[EMAIL PROTECTED]>, Max Khon <[EMAIL PROTECTED]> wrote: > > Seems that this patch fixed the problem for me. > I can not reproduce it anymore. That's good news. Thanks for testing it! I'll commit it later today. John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscri

Re: Neat little DPT utils...

On Wed, Jan 19, 2000 at 09:48:33AM -0600, damieon wrote: > Greetings, > > I administer several machines running freebsd. Most of > them are running FreeBSD-CURRENT, and all of them have DPT SmartRAID IV > raid controlers. I was looking though LINT and found that it made > re

Re: bzip2 in src tree

On Mon, Jan 24, 2000 at 12:16:32PM +0100, Oliver Fromme wrote: > > And just how do I increase the space on a CDROM??? > > Include another CD-ROM. You are missing the point. The installation CDROM only shows you the packages on that CDROM, this gives newbies the impression we don't have very ma

Re: Moused hanging...

On Sun, Jan 23, 2000 at 02:13:17PM -0500, Donn Miller wrote: > Hi, I've noticed a strange problem with vidcontrol and moused recently > with current. I also had the same problem about 3 weeks back, and it > doesn't seem to be occurring all that regularly. > > > Here's what I was doing: I had j

Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzi

Alex Zepeda <[EMAIL PROTECTED]> writes: > On Mon, 24 Jan 2000, Daniel O'Connor wrote: > > On 24-Jan-00 David O'Brien wrote: > > > running Winloose, so I actually *CAN* run this in the background. I > > > certainly was not idle while Bzip2 was compressing. > > Its pretty annoying waiting for som

Re: bzip2 in src tree

On Mon, 24 Jan 2000, Brad Knowles wrote: > And the only cost is the slight expansion of the amount of disk > space required to store the source code in /usr/src and the binaries > in /usr/bin [...] And the time and disk space required to make world. No thank you. Remember that the only

Re: Please help spread the CVSup mirror load more evenly

In message Brad Knowles writes: : Doesn't work. There might be a very low latency but : low-bandwidth connection between you and one of the servers, when you : (and everyone else) would be better off if you instead connected to a : server that show

Re: Please help spread the CVSup mirror load more evenly

On Mon, Jan 24, 2000 at 02:17:54PM +0100, Brad Knowles wrote: > At 11:34 PM +1300 2000/1/22, Joe Abley wrote: > > > This should give you a relative performance metric between the servers > > you measured, hopefully with local network performance variations > > cancelled out by the fact that al

Re: Please help spread the CVSup mirror load more evenly

> On Mon, Jan 24, 2000 at 02:17:54PM +0100, Brad Knowles wrote: > > At 11:34 PM +1300 2000/1/22, Joe Abley wrote: > > > > > This should give you a relative performance metric between the servers > > > you measured, hopefully with local network performance variations > > > cancelled out by the

Re: 4.0-release (ports) schedule

On Mon, Jan 24, 2000 at 06:36:44AM -0800, Satoshi - Ports Wraith - Asami wrote: > There are over 200 broken ports. In particular, there are a few dozen > (78 at last count) broken by the gcc upgrade (those marked by "new These are due to bogus i386 ASM: cooledit-3.11.3.log ja-kon2-14dot-0.3

Re: APM still ignoring DEVICE_SUSPEND errors

In message Nick Hibma writes: : The following patch fixes two things: First, DEVICE_SUSPEND errors are : no longer ignored. Since we have defaults for methods we should no : longer ignore these errors. Also, DEVICE_RESUME wasn't done when the : a

Re: Please help spread the CVSup mirror load more evenly

On Mon, 24 Jan 2000, Warner Losh wrote: > Agreed. The making lots of connections was a bad idea. However, I've > rarely seen low latency and low bandwidth go together. I've also > problems connecting accross high loss links more often. Sure, it is a > statistical argument. > > I still think

Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzi

On 23-Jan-00 Rod Taylor wrote: > On Sat, 22 Jan 2000, you wrote: >> On Sat, 22 Jan 2000, Rod Taylor wrote: >> >> > Personally, I'd like to see less stuff in the system source for >> > smaller installs and lower compile time leaving it up to me to >> > customize the individual stuff thats install

Re: Please help spread the CVSup mirror load more evenly

In message <[EMAIL PROTECTED]> Chuck Robey writes: : That's the precise reason I suggested a system that used no probing, had : feedback, and forced shared load in spite of user misconfiguration. Got : shouted down. One reason I think that you've been shouted down (and me too, since I had simila

Re: 4.0 CODE FREEZE WILL BEGIN IN FIVE (5) DAYS

On Mon, 24 Jan 2000, Jordan K. Hubbard wrote: > On the 29th of January, I'll be freezing the -current branch (well, > OK, the trunk). That means NO commits without my review first and I Hmm. What does this mean for the ATA driver? I know Soren has some more updates in the wings, and I'm gratefu

Re: 4.0-release (ports) schedule

Thus spake David O'Brien ([EMAIL PROTECTED]): > I would be happy to look review fixes or consult the maintainers. Hello David, compiler-maintainer ;-) I noticed that many ports are broken because the compiler handles ANSI-C++ violations too strict. That means, if you do, as an example: const

Re: 4.0-release (ports) schedule

On Mon, Jan 24, 2000 at 08:50:21PM +0100, Alexander Langer wrote: > I noticed that many ports are broken because the compiler handles > ANSI-C++ violations too strict. Not too strict -- to the ratified ISO-C++ specification. > Just FYI, maybe you can do something against this strict handling. N

Re: Please help spread the CVSup mirror load more evenly

On Mon, 24 Jan 2000, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Chuck Robey >writes: > : That's the precise reason I suggested a system that used no probing, had > : feedback, and forced shared load in spite of user misconfiguration. Got > : shouted down. > > One reason I think that y

Re: Please help spread the CVSup mirror load more evenly

On Mon, 24 Jan 2000, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Chuck Robey >writes: > : Oh. If that's a problem, it would be a fatal problem (would be for me, > : sometimes). > > It used to be a big problem. When cvsup was first getting mirrors, > some seemed to update every 15 minu

Re: Please help spread the CVSup mirror load more evenly

At 11:20 AM -0700 2000/1/24, Warner Losh wrote: > Agreed. The making lots of connections was a bad idea. However, I've > rarely seen low latency and low bandwidth go together. I have. Until recently, we had only a 512KB line between our operations facilities here in Brussels and th

Re: bzip2 in src tree

At 9:54 AM -0800 1/24/00, David O'Brien wrote: >On Mon, Jan 24, 2000 at 12:16:32PM +0100, Oliver Fromme wrote: > > > And just how do I increase the space on a CDROM??? > > > > Include another CD-ROM. > >You are missing the point. The installation CDROM only shows >you the packages on that CDROM,

Re: bzip2 in src tree

On Mon, 24 Jan 2000, Brad Knowles wrote: > Can't we do both? Use gzip on the install floppy, but include > bzip2 in /usr/src, and make sure that all the various programs that > deal with tarballs and gzip'ed tarballs can also deal with bzip2 > tarballs (including in the ports system)? >

Re: Please help spread the CVSup mirror load more evenly

In message <[EMAIL PROTECTED]> Chuck Robey writes: : Oh. If that's a problem, it would be a fatal problem (would be for me, : sometimes). It used to be a big problem. When cvsup was first getting mirrors, some seemed to update every 15 minutes, while others updated what seemed like every two da

Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Addbzi

At 2:01 PM -0500 2000/1/24, John Baldwin wrote: > The new install system is probably going to use zip rather than bzip2. I'm curious as to how a choice like this gets made. Could you elaborate? -- These are my opinions and should not be taken as official Skynet policy __

Re: bzip2 in src tree

At 1:17 PM -0500 2000/1/24, Ben Rosengart wrote: > And the time and disk space required to make world. No thank you. What is the time & disk space requirements without bzip2? I recall multiple hours to do this, and hundreds of MB, but then maybe I'm mis-remembering things.

HEADSUP!! burncd users..

The management of next_writeable has been move from the kernel to userspace. This means that the burncd command must be in sync with the kernel. So make world is your friend. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

3com 574-tx PCMCIA

Not to disrupt the facinating discussion about bzip2, but, 1. I've had some people tell me that support for the 3com 574-tx PCMCIA card was definitly in -current, and other people who weren't so sure. Is it, and if so, under what driver? 2. If it's included, is that driver in the GENERIC kernel

Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzi

> At 2:01 PM -0500 2000/1/24, John Baldwin wrote: > > > The new install system is probably going to use zip rather than bzip2. > > I'm curious as to how a choice like this gets made. Could you elaborate? Zip was selected because it's one of the few compressed bundle formats that allows

Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzi

On 24-Jan-00 Brad Knowles wrote: > At 2:01 PM -0500 2000/1/24, John Baldwin wrote: > >> The new install system is probably going to use zip rather than bzip2. > > I'm curious as to how a choice like this gets made. Could you > elaborate? I did not make the choice personally, I believe

Re: 4.0 CODE FREEZE WILL BEGIN IN FIVE (5) DAYS

It seems Kris Kennaway wrote: > On Mon, 24 Jan 2000, Jordan K. Hubbard wrote: > > > On the 29th of January, I'll be freezing the -current branch (well, > > OK, the trunk). That means NO commits without my review first and I > > Hmm. What does this mean for the ATA driver? I know Soren has some

Re: 4.0 CODE FREEZE WILL BEGIN IN FIVE (5) DAYS

On Mon, 24 Jan 2000, Soren Schmidt wrote: > Huh, you have only told me about the missing CDROM (should be fixed > with the commit I just did), what else seems to be a problem ?? My WDC drive falling back to PIO mode..see the dmesg in the previous message. Kris "How many roads must a man w

Re: 3com 574-tx PCMCIA

In message <[EMAIL PROTECTED]> VINSON WAYNE HOWARD writes: : 1. I've had some people tell me that support for the 3com 574-tx PCMCIA : card was definitly in -current, and other people who weren't so sure. Is : it, and if so, under what driver? The ep driver claims to support this card. the pcca

Re: bzip2 in src tree

On Mon, 24 Jan 2000, Ben Rosengart wrote: > And the time and disk space required to make world. No thank you. > Remember that the only win here is if bzip is used in an infrastructural > capacity (e.g. for packages and other install stuff), and it has been > pointed out that the savings on disk

Possible CTM problem

Looking at my CTM logs, I seem to be missing some pieces in the last 3 cvs-cur postings (cvs-cur 6021, 6022, 6023). I get two pieces simultaneously and then nothing until the next part. Is anyone else seeing this? Chuck isn't sure if it's anything he's done. Looking back, the `first two pieces

Re: Possible CTM problem

On Tue, 25 Jan 2000, Peter Jeremy wrote: > Looking at my CTM logs, I seem to be missing some pieces in the last 3 > cvs-cur postings (cvs-cur 6021, 6022, 6023). I get two pieces > simultaneously and then nothing until the next part. Is anyone else > seeing this? Chuck isn't sure if it's anythi

Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Addbzi

At 4:16 PM -0500 2000/1/24, John Baldwin wrote: > Since zip integrates the > compression and archiving in one file format, you can look in the zip header, > find the file you want, and then extract and uncompress just its data. This > func

Re: 4.0 CODE FREEZE vs patches to lpr/lpc

>On Mon, 24 Jan 2000, Jordan K. Hubbard wrote: > > > On the 29th of January, I'll be freezing the -current branch (well, > > OK, the trunk). That means NO commits without my review first ... Could someone commit the 2-line bug fix in bin/15728 before yet another system release goes out the door?

Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches)

< said: > Am I the only one that uses UNIX as a multitasking OS? > nice the bzip2 process by 20 and background it. Geez. Perhaps you're the only one who compresses files just for the hell of it. Most people normally compress files to meet an immediate need, and actually care how long it takes

Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Addbzi

< said: >I'm curious as to how a choice like this gets made. Could you elaborate? Other people have answered with the why but not the how. Choices (like this one about archive formats) get made when people sit down and actually do the work to improve FreeBSD. People with commit bits are gener

Re: 4.0 CODE FREEZE vs patches to lpr/lpc

:Could someone commit the 2-line bug fix in bin/15728 before yet :another system release goes out the door? Done! :Given that lpr/lpd seems to be very low priority in most committers :queues, is there any way to expedite changes like these? I'm :trying avoid any ranting or raving, but this

VESA_800x600 mode -> kernel crash at boot time?

Could someone with a recent (ie < 1 week) -CURRENT confirm whether they have problems booting their system when setting allscreens_flags to "VESA_800x600"? I have now verified the problem with two different systems -- Compaq Professional Workstation 5100 (UP, Matrox Millenium II) and Intel Provi

Re: VESA_800x600 mode -> kernel crash at boot time?

>Could someone with a recent (ie < 1 week) -CURRENT confirm whether they >have problems booting their system when setting allscreens_flags to >"VESA_800x600"? I have now verified the problem with two different >systems -- Compaq Professional Workstation 5100 (UP, Matrox Millenium >II) and Intel P

"perl in malloc(): warning: recursive call" on array write + signals

This is a bug report for perl from [EMAIL PROTECTED], generated with the help of perlbug 1.26 running under perl 5.00503. - [Please enter your report here] Running the following test script causes perl to crash. You may need to ru

big files, blocking in inode, kern.update, and so on...

Howdy, me again... I wrote to some freebsd list some months/years back asking about this, but now it's time to revisit things. We have an old t^Hrusty 2.2-RELENG box from '97 that's been running like a champ, kinda, after hacking around the problem. But it's time to retire that underpowered box

Re: 3com 574-tx PCMCIA

On Mon, 24 Jan 2000, Warner Losh wrote: > The ep driver claims to support this card. the pccard.conf.sample > file also claims to support this card. Matt Dodd claims to have fixed > support for this card. Claim nothing. It works for me and a number of other people who have tested it for me. >

pending patch to fix lack of signed sysctl values

Since the countdown is on to a new release, I'de like to take a second and nag some committers to take a look at PR kern/15251. Greg was going to take care of it for me before he got called away on business. In any event, it would good to get into 4.0 release if for no other reason than to prev

Re: 3com 574-tx PCMCIA

In message <[EMAIL PROTECTED]> "Matthew N. Dodd" writes: : On Mon, 24 Jan 2000, Warner Losh wrote: : > The ep driver claims to support this card. the pccard.conf.sample : > file also claims to support this card. Matt Dodd claims to have fixed : > support for this card. : : Claim nothing. It w

Re: My ATAPI CD not come ready

Hi At Sun, 23 Jan 2000 18:51:25 +0100 (CET), Soren Schmidt <[EMAIL PROTECTED]> wrote: > > I updated to today's -current from -stable. > > My ATAPI CD-ROM drive doesn't probed, > > and is seemed to be halted. > > (The tray is locked, won't open, and the LED keeps being on.) > > This is fixed in

Re: 4.0 CODE FREEZE WILL BEGIN IN FIVE (5) DAYS

>Huh, you have only told me about the missing CDROM (should be fixed >with the commit I just did), what else seems to be a problem ?? On some older PCI systems, including my Pentium 66, the driver still detects irq 0 for ata-pci0. Hardwiring it to irq 14 in the source as suggested recently is t

sys/net/bridge.c IPFIREWALL & DUMMYNET? WTF?

Any reason that the IPFIREWALL and DUMMYNET code is present in sys/net/bridge.c? It appears that it makes a number of bad assumptions and in general violates the semantics of 'bridging' vs. 'routing'. Should we even encourage people to use this functionality? Do we really want bridge.c to have

Re: big files, blocking in inode, kern.update, and so on...

Hmm. It sounds like the system is doing a huge amount of seeking to flush the dirty buffers. Your history file may be badly fragmented on the disk. The first thing I would do is take the system down and copy the history file to reorder all of its block. i.e. 'cp fubar fubar.ba

Re: sys/net/bridge.c IPFIREWALL & DUMMYNET? WTF?

* Matthew N. Dodd <[EMAIL PROTECTED]> [000124 18:11] wrote: > Any reason that the IPFIREWALL and DUMMYNET code is present in > sys/net/bridge.c? It appears that it makes a number of bad assumptions > and in general violates the semantics of 'bridging' vs. 'routing'. > > Should we even encourage

at driver problems (was: 4.0 CODE FREEZE WILL BEGIN IN FIVE (5) DAYS)

On Monday, 24 January 2000 at 13:33:43 -0800, Kris Kennaway wrote: > On Mon, 24 Jan 2000, Soren Schmidt wrote: > >> Huh, you have only told me about the missing CDROM (should be fixed >> with the commit I just did), what else seems to be a problem ?? > > My WDC drive falling back to PIO mode..see

Re: at driver problems (was: 4.0 CODE FREEZE WILL BEGIN IN FIVE (5) DAYS)

does it look like this ??? ad0: ATA-5 disk at ata0 as master ad0: 9770MB (20010816 sectors), 19852 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 acd0: CDROM drive at ata0 as slave acd0: read 6890KB/s (6890KB/s), 256KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA stream

Re: sys/net/bridge.c IPFIREWALL & DUMMYNET? WTF?

> * Matthew N. Dodd <[EMAIL PROTECTED]> [000124 18:11] wrote: > > Any reason that the IPFIREWALL and DUMMYNET code is present in > > sys/net/bridge.c? It appears that it makes a number of bad assumptions > > and in general violates the semantics of 'bridging' vs. 'routing'. > > > > Should we eve

Alpha world breakage in sys/modules/if_tun

This works on the i386 but fails on the Alpha: ===> sys/modules/if_tun @ -> /c/src/sys machine -> /c/src/sys/alpha/include touch opt_devfs.h echo "#define NETATALK 1" > opt_atalk.h echo "#define ATM_CORE 1" > opt_atm.h echo "#define INET 1" > opt_inet.h echo "#define INET6 1" > opt_inet6.h echo "

4.0 CODE FREEZE vs PR patches

While I don't have much time to hack, I have tried to spend a little time going through the open PRs. When I find something I can reproduce, I try to fix it. How can I get the patches I have submitted into 4.0? Some of the problems were not very "obvious" patches, but all of them have been very

ascii art in hosts.allow

What is the reason for putting a giant "Example!" in hosts.allow? I note that it was committed at 3 o'clock in the morning... was someone trying to make a point? What other files have this type of gross bit-bloat in them? Here is a patch: (please notice the spelling correction) --- host

Re: sys/net/bridge.c IPFIREWALL & DUMMYNET? WTF?

On Mon, 24 Jan 2000, Alfred Perlstein wrote: > I'm not sure what your proposing, if it's removing BRIDGE support from > the kernel, I'd have to object. BRIDGE enables me to run a transparent > firewall without worrying about routing issues, just drop a machine > with BRIDGE and IPFIREWALL in betw

Re: ascii art in hosts.allow

On Tue, Jan 25, 2000 at 03:03:32PM +1100, Andy Farkas wrote: > > > What is the reason for putting a giant "Example!" in hosts.allow? > > I note that it was committed at 3 o'clock in the morning... was someone > trying to make a point? > > What other files have this type of gross bit-bloat in

Swapping to NFS via diskless mount broken - patch / review

I'd like a quick review of this patch. It looks like swapdev_vnode changes broke diskless swapping too, not just swap-backed VN. I'm sure glad someone filed a PR on this (kern/16165) or we would have gone into release with this bug. Now, normally I would take this opportuni

connectivity problems with current.freebsd.org

[I know this perhaps isn't the proper list, but -questions and [EMAIL PROTECTED] haven't replied this post, and the -current list tends to be a bit more on the ball. Anyway, the problem is about getting a -CURRENT snapshot :) ] For the past several days (at least since 2118), I've been t

Re: at driver problems (was: 4.0 CODE FREEZE WILL BEGIN IN FIVE (5) DAYS)

It seems TrouBle wrote: > does it look like this ??? Could I have a complete dmesg, or at least all the lines that belongs to the ata driver ?? I need to know what chips etc to be able to diagnose further... > ad0: 9770MB (20010816 sectors), 19852 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/i

** HEADS UP ** Compiler / C++ library changes

Later tonight I will make a change to our base C++ compiler that will change the way virtual tables are handled. Currently we are using THUNKS for virtual inheritance. Unfortunately there are bugs that The GCC developers thought would be fixed in GCC 2.95. However it isn't. After this change e

Re: sys/net/bridge.c IPFIREWALL & DUMMYNET? WTF?

Hi, > Any reason that the IPFIREWALL and DUMMYNET code is present in > sys/net/bridge.c? It appears that it makes a number of bad assumptions > and in general violates the semantics of 'bridging' vs. 'routing'. the reason is that I needed that functionality, and according to my experience most

Need testers for libc_r patch

The attached patch makes libc_r use the recently added hooks in the dynamic linker to provide locking so that the dynamic linker is thread-safe. I have tested it in a simple program and I believe it works OK. If any of you have a -current system with a non-trivial libc_r application, I would app

Re: 4.0 CODE FREEZE WILL BEGIN IN FIVE (5) DAYS

It seems Greg Childers wrote: > > >Huh, you have only told me about the missing CDROM (should be fixed > >with the commit I just did), what else seems to be a problem ?? > > On some older PCI systems, including my Pentium 66, the driver still detects > irq 0 for ata-pci0. Hardwiring it to irq 1

nqnfs bug PR kern/15883, patch to review

This patch is designed to fix PR kern/15883. This PR is very easy to reproduce. http://www.freebsd.org/cgi/query-pr.cgi?pr=15883 Unfortunately the patch is not entirely trivial. NQNFS has a horrendous bug in the code in question -- it's accessing a structure pointer fro

  1   2   >