Re: kern/16767 (A.K.A. Re: Geek Port crash)

> ...with the enclosed patches, the geek port once again works, but I really DUH! Sent the wrong patch file! Change the following line: > + if (!ppi->intr_resource) { to: > + if (ppi->intr_resource) { (stupid little single-char mistake) mike To Unsubscribe:

kern/16767 (A.K.A. Re: Geek Port crash)

Lots of crashes, lots of fsck's, and lots of swearing resulted in the following: Opening /dev/ppi* in 4.0 (After Jan 14) causes a panic when the system tries to allocate what appears to be IRQ 0 to the parallel port... I know little about the interrupt handling, so I went after this with the "b

Re: db 1.85 --> 2.x or 3.x?

On Tue, May 02, 2000 at 10:07:25PM -0400, Danny J. Zerkel wrote: > > pr/9350 is an example of db bugs effecting vi. > (Would someone PLEASE apply the simple patch and close the damn PR!) Ok. I've applied to my local sources. If it passes my next makeworld and doesn't crash things on me, I'll c

Re: KDE 2-preALPHA

On Tue, May 02, 2000 at 04:46:13PM -0600, VINSON WAYNE HOWARD wrote: > Has anyone had any luck with kde 2-preALPHA on -current. I couldn't get Please take this discussion to [EMAIL PROTECTED] where there are KDE knowledgeable people (and where it belongs by the FreeBSD mailing list charters). -

Re: db 1.85 --> 2.x or 3.x?

In servalan.mailinglist.fbsd-current Brad Knowles writes: > Besides, don't we use gcc as the system-standard compiler, and >doesn't this likewise infect everything compiled on FreeBSD with the >GPL? No, because none of the gcc code appears in the resulting binary. The binary does include

Re: db 1.85 --> 2.x or 3.x?

One of the things to consider is the number of places db is used in FreeBSD code. Any bugs in db can manifest in any of these: contrib/bind contrib/global contrib/nvi contrib/perl5 contrib/sendmail crypto/kerberosIV crypto/heimdal lib/libc/gen/devname.c lib/libc/gen/getcap.c lib/libc/gen/getpwen

Re: KDE 2-preALPHA

In muc.lists.freebsd.current, you wrote: > Has anyone had any luck with kde 2-preALPHA on -current. I couldn't get > it to recognize QT even after installing the QT snapshot, and ldconfig did > wierd things. When I finally found the libs(via a reboot), I still got > unresolved symbols. No bina

subscribe freebsd-current subscribe cvs-all

To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: db 1.85 --> 2.x or 3.x?

At 1:05 PM +0200 5/2/00, Brad Knowles wrote: > A thread on news.software.nntp got me checking into this, >and now I've gotten very curious. From what I can determine, it >looks like what is integrated into FreeBSD is Berkeley db 1.85 >(in /usr/src/libc/db), although there is a port for 2.7.

Re: KDE 2-preALPHA

Since I'm interested in this too, and nobody has posted a better way yet, I'll tell you what I did to make it work, in a VERY "dirty way", in -current. Hope somebody posts a better and cleaner way. This is what I did : Use the ports to install QT 2.1, gtk12, gmake, jpeg, png, xpm, tiff, gettext

Re: db 1.85 --> 2.x or 3.x?

At 3:12 PM -0700 2000/5/2, Jordan K. Hubbard wrote: > Yes, this was brought up by the sleepycat people themselves over a > year ago and was part of a long discussion thread involving Keith > Bostic and a host of FreeBSD developers. We were unable to reach such > an agreement or get any such

KDE 2-preALPHA

Has anyone had any luck with kde 2-preALPHA on -current. I couldn't get it to recognize QT even after installing the QT snapshot, and ldconfig did wierd things. When I finally found the libs(via a reboot), I still got unresolved symbols. Any sucess stories, or the location of a binary distribu

5.0-20000502-SNAP install does not boot

Hi, Today, I tried a test install of the last nights -current, 0502-SNAP. The cd boots correctly and the install works like a charm. However, after finishing the install and attempting to boot the newly installed system, it hands at the "F1 FreeBSD" prompt. Hitting the F1 key (or any other ke

Re: db 1.85 --> 2.x or 3.x?

> Does anyone know if this has been brought up with the folks at > Sleepycat to see if we could get a modification/clarification of this > point, so that as long as FreeBSD satisfies the necessary > requirements that this point of the license doesn't then recurse upon > people who might

Re: NFS, rl0 and Alpha

:Is anyone else observing kernel panics in the NFS code with Alpha :(pc164) and rl0 (the Alpha is running as a client only) ? : :NFS worked just fine when I had a de0 in the box. After installing an :rl0 (I know they suck, but they're so cheap :) I _always_ get an :unaligned access panic when I t

NFS, rl0 and Alpha

Is anyone else observing kernel panics in the NFS code with Alpha (pc164) and rl0 (the Alpha is running as a client only) ? NFS worked just fine when I had a de0 in the box. After installing an rl0 (I know they suck, but they're so cheap :) I _always_ get an unaligned access panic when I try to a

Re: MVP3 problems - current state?

On Tue, 2 May 2000, John Hay wrote: >> What board make/version is this ? > >There is no name or version on the board itself. The box it came in >said it is a "A+ Mainboard" and on the side there is a label that >says "APRO/BAT Motherboard". And it is made in China. If it was sold as an electroni

Re: problems with Ghostscript5/55/6

On Tue, May 02, 2000 at 09:52:43AM -0500, Bruce Burden wrote: > I am trying to get Ghostscript running on a 4.0-STABLE >environment. Here is what I get: Please post this to [EMAIL PROTECTED] where Ports savy people hang out. [EMAIL PROTECTED] is to discuss FreeBSD kernel and native use

I am looking for investors

Hello, Please, pardon me for this intrusion. No further emails will be sent to you. I recently designed a website called directoris.com (a Business Portal) but I am at a stage where I need financial investment and more people to work with me on this huge project. Mainly, directoris.com will

Re: db 1.85 --> 2.x or 3.x?

Thomas David Rivers wrote: > > > > > Brad Knowles wrote: > > > > > > At 10:00 AM -0500 2000/5/2, Dan Nelson wrote: > > > > > > > .. means that a user that wanted to use FreeBSD in a commercial > > > > application would not be able to simply sell his product; he would have > > > > to get a lice

Re: Old-style KLD file linuxelf found?

Idea Receiver wrote: > > On Tue, 2 May 2000, Donn Miller wrote: > > Actually, I meant brandelf -t Linux /compat/linux/sbin/ldconfig. > > > > as i said before. i did try to brandelf it. doesnt work. > > anyway. i think maybe due to the modules not sync? but how can this > happen? You probably

Re: db 1.85 --> 2.x or 3.x?

Then, with the problems associated with the Sleepycat license, is there some other alternative to this particular DB product? Surely ours is not the only area that has experienced frustration with this point. What other DB-like projects are out there, etc. _F To Unsubscribe: send mail to [E

Re: db 1.85 --> 2.x or 3.x?

< said: > This is where the license issues are... Keith offered to make a one-time lobotomy of the DB 2.x code to trim it down to just the 1.85 API, with a standard Berkeley-style license. We discussed this for a while, but determined that: 1) exchanging one unmaintained database package for

Re: db 1.85 --> 2.x or 3.x?

> > Brad Knowles wrote: > > > > At 10:00 AM -0500 2000/5/2, Dan Nelson wrote: > > > > > .. means that a user that wanted to use FreeBSD in a commercial > > > application would not be able to simply sell his product; he would have > > > to get a license from Sleepycat. > > > > I asked the K

Re: db 1.85 --> 2.x or 3.x?

Brad Knowles wrote: > > At 10:00 AM -0500 2000/5/2, Dan Nelson wrote: > > > .. means that a user that wanted to use FreeBSD in a commercial > > application would not be able to simply sell his product; he would have > > to get a license from Sleepycat. > I asked the Keith about this and he

Re: cvs commit: src/lib/libstand ext2fs

On Mon, May 01, 2000 at 09:08:02PM -0700, Mike Smith wrote: > > > What sort of fallback behaviour would you want in case of error here? > > > > Just let chroot() either succeed or fail. It's own "fallback behavior" > > in such a case should prove adequate. :) > > Hmm. Failure to chroot == fa

Re: Old-style KLD file linuxelf found?

On Tue, 2 May 2000, Donn Miller wrote: > Donn Miller wrote: > > > > Idea Receiver wrote: > > > > > > My mail server was down for pass few days. Hope I didnt miss anything > > > important! > > > > > > Today, I try to make world and then rebuild the kernel. > > > After I restart the machine, it

Re: db 1.85 --> 2.x or 3.x?

On Tue, 02 May 2000 17:14:31 +0200, Brad Knowles wrote: > > Sleepycats license is not FreeBSD compatible :-/ > > I don't understand. Reading > , it seems to me that FreeBSD > meets all the necessary requirements. Can someone who understands the > d

Re: db 1.85 --> 2.x or 3.x?

At 10:00 AM -0500 2000/5/2, Dan Nelson wrote: > .. means that a user that wanted to use FreeBSD in a commercial > application would not be able to simply sell his product; he would have > to get a license from Sleepycat. Ahh, okay. Now I think I understand the licensing issue.

Re: db 1.85 --> 2.x or 3.x?

On Tue, 2 May 2000, Brad Knowles wrote: > At 1:16 PM +0200 2000/5/2, Poul-Henning Kamp wrote: > > > Sleepycats license is not FreeBSD compatible :-/ > > I don't understand. Reading > , it seems to me that FreeBSD > meets all the necessary requirem

Re: db 1.85 --> 2.x or 3.x?

In message <[EMAIL PROTECTED]>, Forrest Aldrich writes: >I've been curious about this. Would someone clarify what in this >license prevents FreeBSD from including it, at some level? People wouldn't be able to use FreeBSD without giving away their source. /etc/passwd is stored in a db file for i

Re: db 1.85 --> 2.x or 3.x?

> > Sleepycats license is not FreeBSD compatible :-/ > > I don't understand. Reading > , it seems to me that FreeBSD > meets all the necessary requirements. Can someone who understands > the details of the licensing issues either explain the situa

Re: db 1.85 --> 2.x or 3.x?

At 1:16 PM +0200 2000/5/2, Poul-Henning Kamp wrote: > Sleepycats license is not FreeBSD compatible :-/ I don't understand. Reading , it seems to me that FreeBSD meets all the necessary requirements. Can someone who understands the details of th

Re: problems with Ghostscript5/55/6

> Ghostscript55: > > It will build and install. When I run "gs", I get: > > bash-2.03# gs /usr/local/share/ghostscript/5.50/examples/tiger.ps > Aladdin Ghostscript 5.50 (1998-9-16) > Copyright (C) 1998 Aladdin Enterprises, Menlo Park, CA. All rights reserved. > This software comes with NO

Re: problems with Ghostscript5/55/6

On Tue, 2 May 2000, Bruce Burden wrote: > Ghostscript55: > > It will build and install. When I run "gs", I get: > > bash-2.03# gs /usr/local/share/ghostscript/5.50/examples/tiger.ps > Aladdin Ghostscript 5.50 (1998-9-16) > Copyright (C) 1998 Aladdin Enterprises, Menlo Park, CA. All righ

Re: Problematic PNP probing, faulty /compat/linux/sbin/ldconfig.

Trent Nelson wrote: > pid 159 (ldconfig), uid 0: exited on signal 11 (core dumped) As suggested by Donn Miller in a previous thread, the command `brandelf -t Linux /compat/linux/sbin/ldconfig' fixes that up. Thanks. Trent. To Unsubscribe: send mail

Re: db 1.85 --> 2.x or 3.x?

In the last episode (May 02), Forrest Aldrich said: > I've been curious about this. Would someone clarify what in this > license prevents FreeBSD from including it, at some level? Basically, the part that says > If you redistribute your application outside of your site and your > source code i

problems with Ghostscript5/55/6

Hi, I am trying to get Ghostscript running on a 4.0-STABLE environment. Here is what I get: Ghostscript5: Won't build - bash-2.03# make ===> Building for ghostscript-5.10 make: don't know how to make libpng/png.h. Stop *** Error code 2 Stop in /usr/ports/print/ghosts

Re: db 1.85 --> 2.x or 3.x?

Forrest Aldrich wrote: > I've been curious about this. Would someone clarify what in this > license prevents FreeBSD from including it, at some level? The problem is that we export the DB API from libc, and if anything uses the DB interface for a local application they'd be subject to the licens

Re: MVP3 problems - current state?

It seems John Hay wrote: > > What board make/version is this ? > > There is no name or version on the board itself. The box it came in > said it is a "A+ Mainboard" and on the side there is a label that > says "APRO/BAT Motherboard". And it is made in China. Uhm > > > A verbose dmesg with v

Re: MVP3 problems - current state?

> It seems John Hay wrote: > > Interesting that those same disks work in the same UDMA33 mode on > > another motherboard with a different chipset. I have tried both > > Samsung and Seagate disks. I have also tried more than one > > motherboard and they do the same, so it isn't just a faulty board.

Problematic PNP probing, faulty /compat/linux/sbin/ldconfig.

Originally cvsup'd and made world successfully on the 30th and found the following problems to occur. Cvsup'ing to a new -current and a new kernel still sees the same things occurring. Everything's detected at boot time hassle free (printer, sound, network card) so I have no idea

Re: Old-style KLD file linuxelf found?

Donn Miller wrote: > Idea Receiver wrote: > > > > My mail server was down for pass few days. Hope I didnt miss anything > > important! > > > > Today, I try to make world and then rebuild the kernel. > > After I restart the machine, it shows "Old-style KLD file linuxelf found" > > and "Old-style

Re: db 1.85 --> 2.x or 3.x?

I've been curious about this. Would someone clarify what in this license prevents FreeBSD from including it, at some level? _F Sleepycat Software Product Licensing Berkeley DB is an Open Sourcetm product, and complete source code is available from our Web site. If you build an applicatio

Re: db 1.85 --> 2.x or 3.x?

< said: > Sleepycats license is not FreeBSD compatible :-/ Even worse, the 2.x file format is not FreeBSD compatible. Having already had one flag day between 1.x and 2.x (the FreeBSD versions) when the installed base was much, much smaller, we were not particularly inclined to have another one

Re: MVP3 problems - current state?

Thus spake John Hay ([EMAIL PROTECTED]): > But then maybe it is just me that have the problem. Yes. New world/kernel, no problems in UDMA33 mode with two UDMA-33 disks. Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body

Re: MVP3 problems - current state?

It seems John Hay wrote: > Interesting that those same disks work in the same UDMA33 mode on > another motherboard with a different chipset. I have tried both > Samsung and Seagate disks. I have also tried more than one > motherboard and they do the same, so it isn't just a faulty board. > I have

Re: MVP3 problems - current state?

> It seems Warner Losh wrote: > > In message <[EMAIL PROTECTED]> Soren Schmidt writes: > > : Ehm, is that a warning you have written or ?? I certainly havn't > > : issued this warning as the maintainer/author of the ata driver... > > > > I think that I wrote it, and that it is basically wrong. I

Re: Old-style KLD file linuxelf found?

Donn Miller wrote: > > Idea Receiver wrote: > > > > My mail server was down for pass few days. Hope I didnt miss anything > > important! > > > > Today, I try to make world and then rebuild the kernel. > > After I restart the machine, it shows "Old-style KLD file linuxelf found" > > and "Old-style

Re: Old-style KLD file linuxelf found?

Idea Receiver wrote: > > My mail server was down for pass few days. Hope I didnt miss anything > important! > > Today, I try to make world and then rebuild the kernel. > After I restart the machine, it shows "Old-style KLD file linuxelf found" > and "Old-style KLD file linuxaout found" and then

Old-style KLD file linuxelf found?

My mail server was down for pass few days. Hope I didnt miss anything important! Today, I try to make world and then rebuild the kernel. After I restart the machine, it shows "Old-style KLD file linuxelf found" and "Old-style KLD file linuxaout found" and then core dumped. I tried to brandelf.

Re: db 1.85 --> 2.x or 3.x?

In message , Brad Knowles writes: >Folks, > > A thread on news.software.nntp got me checking into this, and now >I've gotten very curious. From what I can determine, it looks like >what is integrated into FreeBSD is Berkeley db 1.85 (in >/usr/src/li

db 1.85 --> 2.x or 3.x?

Folks, A thread on news.software.nntp got me checking into this, and now I've gotten very curious. From what I can determine, it looks like what is integrated into FreeBSD is Berkeley db 1.85 (in /usr/src/libc/db), although there is a port for 2.7.7 in /usr/ports/databases/db.

Anybody using Epox EP-7KXA Athlon motherboard?

I've just got a new Athlon machine with an Epox EP-7KXA motherboard. It comes highly recommended, but I have some severe problems with the timekeeping: it seems that the BIOS does not allow me to disable APM, and the 8254 timekeeping goes crazy, running up to 10 times as fast as real time. Does a

Re: HEADS UP: loader updated to handle module metadata

Thus spake Peter Wemm ([EMAIL PROTECTED]): > ld -shared -o netbundle.ko setdef0.o if_dc.kld if_vr.kld if_xl.kld \ > miibus.kld setdef1.o > If you then preloaded 'netbundle', then you will get a whole stack of > modules in one chunk. If you then kldload if_sk (another miibus user), it [...] W

Re: MVP3 problems - current state?

It seems Warner Losh wrote: > In message <[EMAIL PROTECTED]> Soren Schmidt writes: > : Ehm, is that a warning you have written or ?? I certainly havn't > : issued this warning as the maintainer/author of the ata driver... > > I think that I wrote it, and that it is basically wrong. I'll look > i