Hello High School Alumni
Dear High School Alumni, This email is to inform you of a new website that allows you to stay in touch with your high school friends. A HREF="http://www.tdyalumni.com"www.tdyalumni.com/A Wouldn't it be great to surprise an old friend with an email. Spark up that old friendship, see what the captain of the football team is up to today, find out if the prom queen is still all that. Go to A HREF="www.tdyalumni.com"www.tdyalumni.com/A and contact them now! This is the number one site for contacting high school alumni. The Digital Yearbook allows you to create your own personal page, which mcan include now and then photos, yearbook pages, group/team photos, or your own collage of photos. With over 25,000 schools listed on The Digital Yearbook you are able to not only stay in touch with friends from your high school, but you are also able to rekindle friendships with people you meet from any other high school in the United States. If you would like to be removed from this automated mailing list please A HREF="mailto:[EMAIL PROTECTED]?SUBJECT=REMOVE"CLICK HERE/A. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MVP3 problems - current state?
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 into correcting it. I think that the warnding should likely be changed to: if you have crappy disks, you'll be beter off in pio mode :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 into correcting it. I think that the warnding should likely be changed to: if you have crappy disks, you'll be beter off in pio mode :-) Good wording :) I've run tests on everything I can get my hands on with my MVP3 based chaintec board, and it "just works", so I dont think the ata driver has a problem with this chipset. However as I said earlier, it _could_ be that VIA has changed vital things in a new rev of the 82c586, but I havn't seen any evidence to this (yet)... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 [...] Wow! That sounds awesome! I wish you good luck with implementing this *eg* Alex -- I need a new ~/.sig. 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?
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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 said it was wrong.. (to my memory). I recall he said that as it would be grandfathered into freeBSD, (because we had 1.x already) and that anyone running their software under freeBSD could do so without added licencing, because it was already present on the platform. Ah - but that's "running under FreeBSD" - what about taking the FreeBSD source and using it in a different product... Just what does "running under FreeBSD" mean, anyway? If I sell a black box and use FreeBSD as the internal OS, but don't call it FreeBSD - is it "running under FreeBSD?" What if, for example, what if a product came together that was the Linux kernel with the FreeBSD command set? Is that "running under FreeBSD?" Would you be forced to send out your complete sources in that event? This is where the license issues are... - Dave Rivers - 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?
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 said it was wrong.. (to my memory). I recall he said that as it would be grandfathered into freeBSD, (because we had 1.x already) and that anyone running their software under freeBSD could do so without added licencing, because it was already present on the platform. -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000 --- X_.---._/ presently in: Perth v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 == failure to start init? If Linux emulation is non modular, what happens if /sbin/init is a linux binary? I admit to being tempted to find out exactly how good Linux emulation is... -- Mike Bristow, seebitwopie 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?
On Tue, 02 May 2000 17:14:31 +0200, Brad Knowles wrote: Sleepycats license is not FreeBSD compatible :-/ I don't understand. Reading http://www.sleepycat.com/license.net, it seems to me that FreeBSD meets all the necessary requirements. Can someone who understands the details of the licensing issues either explain the situation to me, or provide pointers to references that do? This is taken from http://www.sleepycat.com/licensing.html: If you redistribute your application outside of your site and your source code is not freely available and redistributable by others, then you require a commercial license from Sleepycat Software. This means that the software's presence in FreeBSD makes FreeBSD unsuitable for building and selling a black box solution. Ciao, Sheldon. 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 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. 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 be using FreeBSD and linking with our libc? Besides, don't we use gcc as the system-standard compiler, and doesn't this likewise infect everything compiled on FreeBSD with the GPL? As I vaguely recall, there was recently a loosening of the GPL to include the LGPL for what appear to be precisely these sorts of reasons. Since FreeBSD use Berkeley DB for passwd.db and other system databases, we would have to provide DB 3 for non-commercial users and DB 1.85 for commercial users. Neither DB 2 or 3 provide any features that FreeBSD needs (concurrent multi-user modification and transactions), so there's no great need to replace our current DB. Ahh, okay so there are also valid technical reasons -- it's too big to put into libc. Sadly, I fear that the result is that many people will tend to stick with db 1.85, or that this will be the only exposure to Berkeley DB for many people, and this will give them an unnecessarily negative impression of this library. Thus is the power of defaults, and one of the potential pitfalls. Thanks everybody! -- These are my opinions -- not to be taken as official Skynet policy == Brad Knowles, [EMAIL PROTECTED]|| Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium 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?
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 instance. Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. 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?
Sleepycats license is not FreeBSD compatible :-/ I don't understand. Reading http://www.sleepycat.com/license.net, it seems to me that FreeBSD meets all the necessary requirements. Can someone who understands the details of the licensing issues either explain the situation to me, or provide pointers to references that do? Sure, I built a commercial application on FreeBSD. It looked up usernames (which use DB routines). Therefore, according to the licensing scheme, I must now give away the entire source code to my commercial application. Second issue. I use FreeBSD in an embedded system. In order to not *have* to distribute source code to my application, it's in my best interest to strip out any GNU and similar code from the system before I 'ship' it. (Which allows me to ship binaries to make the distribution of my product easier). However, I'm not using the newer DB routines, so I must now provide source code to *everything*, and pointing to the FreeBSD site is not adequate, because there are no time limitations, and FreeBSD might yank the distribution on their site before a customer stops using my hardware. Is that easier? Nate 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?
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 is not freely available and redistributable by others, then you require a commercial license from Sleepycat Software. Contact us for commercial licensing terms and pricing. .. 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. Since FreeBSD use Berkeley DB for passwd.db and other system databases, we would have to provide DB 3 for non-commercial users and DB 1.85 for commercial users. Neither DB 2 or 3 provide any features that FreeBSD needs (concurrent multi-user modification and transactions), so there's no great need to replace our current DB. Another big personal minus for me is that neither DB 2 or DB 3 will compile at all under DOS, so I can't write portable programs with them. -- Dan Nelson [EMAIL PROTECTED] 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?
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 license below. Also, since DB 1.x is part of libc (including the getpwent() stuff for /etc/pwd.db etc), we're stuck with that file format as all binaries linked with that (or older libc major versions) versions of libc will not be able to lookup usernames if we change to 2.x. We could probably have a special hidden internal version of db 1.x to use within libc though. db 2.x+ is *way* too big to put in libc IMHO. For what it's worth, we do include it at "some level" - see ports/databases/ db.. This is safely out of the way of people using it accidently. _F Sleepycat Software Product Licensing Berkeley DB is an Open Sourcetm product, and complete source code is availabl e from our Web site. If you build an application that you do not redistribute outside of your site , or if you build an application and your source code is freely available and redistributable by others, you may use Berkeley DB at no charge . You must, of course, abide by the terms of the copyrights that apply to the Berkeley DB software. If you redistribute your application outside of your site and your source cod e is not freely available and redistributable by others, then you require a commercial license from Sleepycat Software. Contact us for commerci al licensing terms and pricing. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 also installed FreeBSD 3.4 on it and worked fine. I have also enabled DMA on that with flags setting and that also worked fine. 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. A verbose dmesg with version numbers was sent in an email to -current with this id: [EMAIL PROTECTED] Cant seem to find that, could you mail me a copy of that please? Ok, done that. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 what the PNP info stuff is in dmesg. I've got an Intel SunRiva M/B w/ the onboard TNT + ES1371 (detected correctly as can be seen) and a PCI ethernet card - nothing else is plugged in to the box. I've mentioned the ldconfig segfault problem as I'm under suspicion I have to do something extra (other than make world) to update the Linux kernel modules? Note, kldload/unload of linux.ko works hassle free - as soon as /usr/sbin/linux is executed from rc.i386, /compat/linux/sbin/ldconfig is exec'd and cores. I'll re-compile with debugging if requested. FreeBSD breaker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed May 3 05:20:41 WST 2000 root@:/usr/src/sys/compile/breaker_02May2000 i386 Thanks in advance. Regards, Trent. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Wed May 3 05:20:41 WST 2000 root@:/usr/src/sys/compile/breaker_02May2000 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (232.79-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x633 Stepping = 3 Features=0x80f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,MMX real memory = 66977792 (65408K bytes) avail memory = 60973056 (59544K bytes) Preloaded elf kernel "kernel" at 0xc0346000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: NVidia Riva TNT graphics accelerator at 0.0 irq 11 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xef80-0xef9f irq 10 at device 7.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered chip1: Intel 82371AB Power management controller port 0x440-0x44f at device 7.3 on pci0 pcm0: AudioPCI ES1371 port 0xef00-0xef3f irq 9 at device 12.0 on pci0 fxp0: Intel EtherExpress Pro 10/100B Ethernet port 0xee80-0xeebf mem 0xfea0-0xfeaf,0xfebff000-0xfebf irq 9 at device 14.0 on pci0 fxp0: Ethernet address 00:04:ac:53:46:dd fxp0: supplying EUI64: 00:04:ac:ff:fe:53:46:dd fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: ppbus0: Canon BJC-265SP/1.00 PRINTER BJ,LQ,BJL,BJRaster,BSCC lpt0: Printer on ppbus0 lpt0: Interrupt-driven port unknown0: PNP0c01 at iomem 0-0x9fbff,0x9fc00-0x9,0xe-0xf,0x3fe-0x3ff7fff,0x3ff8000-0x3ff,0xfec0-0xfec00fff,0xfee0-0xfee00fff,0xfff8-0x on isa0 unknown1: PNP0c01 at iomem 0x10-0x3fd on isa0 unknown: PNP can't assign resources unknown2: PNP0200 at port 0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xde drq 4 on isa0 unknown3: PNP0100 at port 0x40-0x43 irq 0 on isa0 unknown4: PNP0b00 at port 0x70-0x71 irq 8 on isa0 unknown: PNP0303 can't assign resources unknown5: PNP0800 at port 0x61 on isa0 unknown6: PNP0c04 at port 0xf0-0xff irq 13 on isa0 unknown7: PNP0c02 at port 0x4d0-0x4d1,0xcf8-0xcff,0x10-0x1f,0x22-0x3f,0x50-0x52,0x72-0x77,0x91-0x93,0xa2-0xbe,0x400-0x43f,0x440-0x44f on isa0 unknown8: PNP0c02 at port 0x290-0x297,0x370-0x371 on isa0 unknown: PNP0501 can't assign resources unknown9: PNP0c02 on isa0 unknown: PNP0400 can't assign resources unknown: PNP0700 can't assign resources unknown: PNP0f13 can't assign resources unknown10: PNP0a03 on isa0 ad0: 8063MB QUANTUM FIREBALL CR8.4A [16383/16/63] at ata0-master using UDMA33 ad1: 3079MB QUANTUM FIREBALL ST3.2A [6256/16/63] at ata0-slave using UDMA33 acd0: CD-RW Hewlett-Packard CD-Writer Plus 8200 at
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 KLD file linuxaout found" and then core dumped. What you need to do is/ brandelf -t Linux /compat/linux/sbin/ldconfig and then reboot. Actually, I'm not sure that I see how this has to do with the message above. What was reported was a diagnostic message from the kernel module loader about having a kernel with the new kld interface but an old-style kld. The original poster has just got the kernel and kld's out of sync. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 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?
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 application that you do not redistribute outside of your site, or if you build an application and your source code is freely available and redistributable by others, you may use Berkeley DB at no charge. You must, of course, abide by the terms of the copyrights that apply to the Berkeley DB software. If you redistribute your application outside of your site and your source code is not freely available and redistributable by others, then you require a commercial license from Sleepycat Software. Contact us for commercial licensing terms and pricing. 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?
On Tue, 02 May 2000 13:16:03 +0200, Poul-Henning Kamp [EMAIL PROTECTED] 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 now that would screw many more users. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 of the message
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 into correcting it. I think that the warnding should likely be changed to: if you have crappy disks, you'll be beter off in pio mode :-) Good wording :) Uhm. There is no way to turn it off when you do an installation. 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 also installed FreeBSD 3.4 on it and worked fine. I have also enabled DMA on that with flags setting and that also worked fine. I've run tests on everything I can get my hands on with my MVP3 based chaintec board, and it "just works", so I dont think the ata driver has a problem with this chipset. However as I said earlier, it _could_ be that VIA has changed vital things in a new rev of the 82c586, but I havn't seen any evidence to this (yet)... A verbose dmesg with version numbers was sent in an email to -current with this id: [EMAIL PROTECTED] But then maybe it is just me that have the problem. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 core dumped. What you need to do is/ brandelf -t Linux compat/linux/sbin/ldconfig and then reboot. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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. but same message appear... Please help me! I believe I miss out something really important in pass few days thx 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?
In message v0422080ab53464df3042@[195.238.1.121], 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/libc/db), although there is a port for 2.7.7 in /usr/ports/databases/db. Now, correct me if I'm wrong, but I believe that db 1.85 is pretty widely known to be broken in a number of ways (see http://www.sleepycat.com/historic.html), and I'm wondering what it would take to get this updated to at least 2.x, if not make the jump all the way to 3.x (currently at 3.0.55, according to http://www.sleepycat.com/download.html)? Sleepycats license is not FreeBSD compatible :-/ On a related issue, as another Berkeley alumni, how easy would it be for Keith to get committer access to FreeBSD, assuming he wanted it (and doesn't have it already ;-)? For maintaining db ? Sure. But I understand that the license issue holds up the upgrade to a newer DB and that Keith has no interest in maintaining the older version we use. Out of curiosity, is there a public list of all the people who have commit access to FreeBSD? Yes, it's in the CVS tree in the file CVSROOT/access and in the Handbook as well. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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. Now, correct me if I'm wrong, but I believe that db 1.85 is pretty widely known to be broken in a number of ways (see http://www.sleepycat.com/historic.html), and I'm wondering what it would take to get this updated to at least 2.x, if not make the jump all the way to 3.x (currently at 3.0.55, according to http://www.sleepycat.com/download.html)? On a related issue, as another Berkeley alumni, how easy would it be for Keith to get committer access to FreeBSD, assuming he wanted it (and doesn't have it already ;-)? Out of curiosity, is there a public list of all the people who have commit access to FreeBSD? Thanks! -- These are my opinions -- not to be taken as official Skynet policy == Brad Knowles, [EMAIL PROTECTED]|| Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 anybody else have one of these boards? Have you seen the problem? (How) did you fix it? If not, does anybody know the incantations to disable the APM during system startup? If so, I'll play around with it myself. I'm attaching the dmesg output in case it's of any use. Greg Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-RELEASE #0: Mon Mar 20 22:50:22 GMT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: AMD Athlon(tm) Processor (751.71-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x621 Stepping = 1 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR AMD Features=0xc040AMIE,DSP,3DNow! real memory = 268369920 (262080K bytes) avail memory = 256479232 (250468K bytes) Preloaded elf kernel "kernel" at 0xc03c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib2: PCI to PCI bridge (vendor=1106 device=8391) at device 1.0 on pci0 pci1: PCI bus on pcib2 pci1: Matrox MGA G400 AGP graphics accelerator at 0.0 isab0: VIA 82C686 PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C686 ATA66 controller port 0xd000-0xd00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: VIA 83C572 USB controller at 7.2 irq 10 chip2: VIA 82C686 AC97 Audio port 0xe400-0xe403,0xe000-0xe003,0xdc00-0xdcff irq 5 at device 7.5 on pci0 ahc0: Adaptec 2940 Pro Ultra SCSI adapter port 0xe800-0xe8ff mem 0xdb00-0xdb000fff irq 11 at device 8.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs xl0: 3Com 3c905C-TX Fast Etherlink XL port 0xec00-0xec7f mem 0xdb001000-0xdb00107f irq 10 at device 11.0 on pci0 xl0: Ethernet address: 00:50:da:cf:17:97 miibus0: MII bus on xl0 xlphy0: 3c905C 10/100 internal PHY on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: supplying EUI64: 00:50:da:ff:fe:cf:17:97 pcib1: Host to PCI bridge on motherboard pci2: PCI bus on pcib1 fdc0: direction bit not set fdc0: cmd 3 failed at out byte 1 of 3 atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppi0: Parallel I/O on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port plip0: PLIP network interface on ppbus0 ad0: 19574MB WDC WD205BA [39770/16/63] at ata0-master using UDMA66 ad2: 19574MB WDC WD205BA [39770/16/63] at ata1-master using UDMA33 afd0: 120MB LS-120 F250 01 UHD Floppy [963/8/32] at ata1-slave using PIO3 Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 4 lun 0 sa0: SONY SDT-1 0101 Removable Sequential Access SCSI-2 device sa0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 KLD file linuxaout found" and then core dumped. What you need to do is/ brandelf -t Linux compat/linux/sbin/ldconfig and then reboot. Actually, I meant brandelf -t Linux /compat/linux/sbin/ldconfig. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 also installed FreeBSD 3.4 on it and worked fine. I have also enabled DMA on that with flags setting and that also worked fine. What board make/version is this ? A verbose dmesg with version numbers was sent in an email to -current with this id: [EMAIL PROTECTED] Cant seem to find that, could you mail me a copy of that please? But then maybe it is just me that have the problem. Dunno, just because I can't reproduce it on any of the MVP3 baords I've access to doesn't mean a problem cant exist, so please get the above requested info in my mailbox and I'll see what i can do... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 version numbers was sent in an email to -current with this id: [EMAIL PROTECTED] Cant seem to find that, could you mail me a copy of that please? Ok, done that. Thanks, I'll look into it asap -Søren 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?
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 http://www.sleepycat.com/license.net, it seems to me that FreeBSD meets all the necessary requirements. Can someone who understands the details of the licensing issues either explain the situation to me, or provide pointers to references that do? FreeBSD meets the license requirements. A non-FreeBSD developed application that used the DB interfaces might not. I don't think it would be a good idea for FreeBSD to do things that make it harder to produce commerical software. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 shows "Old-style KLD file linuxelf found" and "Old-style KLD file linuxaout found" and then core dumped. What you need to do is/ brandelf -t Linux compat/linux/sbin/ldconfig and then reboot. 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? 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?
On Tue, 2 May 2000 12:32:20 -0400 (EDT), Thomas David Rivers [EMAIL PROTECTED] 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 another was not a particularly useful tradeoff, and 2) the file-format changes would make this sort of change exceedingly painful to our users. For these reasons, we said ``thanks but no thanks''. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 offer: 1 - Online tools services, and information for businesses (Business Center Section) 2 - Online marketplace connecting buyers and sellers (Trade Leads Section) 3 - Business-related products (Shopping Section) 4 - Business-related news and information (Global News Section) 5 - Directories of companies, products, services, websites, etc. (Databases Section) Please, take a look at http://www.directoris.com and let me know whether you can help me financially. Of course, this website is not fully working at the moment but if you are interested in this project you will get the idea. We also have a special introductory offer on banner advertising. We will be happy to give you any further information you may need. Thank you again for giving me your time and let me apologize in advance for any inconvenience this email may have caused. Best Regards Vincent [EMAIL PROTECTED] PS: You can register your company, products, services, etc. in our database. This part is working. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 userland build issues. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 electronics product in the United States it _will_ have an FCC ID printed somewhere on it. If you can locate that number and run it through the FCC's ID database @ fcc.gov you can determine the manufacturer. From there a good net search for that manufacturer's name should at least turn up a .ch or .tw address with more info on the board. Good luck. Brandon D. Valentine -- [EMAIL PROTECTED] Illegitimi non carborundum. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 access an NFS mounted FS, in any way. Other network activities like telnet, ftp and cvsup cause no panics, so it doesn't seem to a problem in the IP stack or the rl driver itself. I have a crash dump, but I haven't analyzed it yet. Just looking for reports from other users. BTW I've seen this panic with various kernels, including one with sources cvsup'd yesterday (about 10 AM MEST). BTW2 the server (an x86 with rl0) is also running -current of the same vintage. Gary Jennejohn / [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 try to access an NFS mounted FS, in any :way. This is almost certainly related to differences in how the packet is aligned in memory between de0 and rl0. If you are getting panics, it is probably at the same location every time. If you can get a kernel core dump and backtrace I'll bet we can find and fix this problem quickly. -Matt 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?
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 be using FreeBSD and linking with our libc? 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 modification of the license and so we elected to remain with DB 1.85 at that time. There have been no changes to the license or any apparant willingness on Sleepycat's part to modify it in the ensuing 12 months. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 key) simply results in a beep. By booting off of the mfsroot.flp floppy, and then telling it to boot from 0:da(0,a)/kernel, the system boots up normally. I've installed the boot code again via: boot0cfg -v da0 disklabel -B da0 # flag start chs type end chsoffsetsize 1 0x80 0: 1: 1 0xa51023: 70: 27 27 4163697 drive=0x80 mask=0xf options=nopacket,update,nosetdrv ticks=182 This does not fix the problem. I'm continuing to look into this problem. If anyone has any ideas on what I should look at, please let me know. Thanks, John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 distribution, would be great. Thanks in advance, Wayne 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 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 modification of the license and so we elected to remain with DB 1.85 at that time. I've also been discussing these issues privately with Keith, and from what I've read on the list plus what I've received from him in private, I understand that he made an offer to modify the license and allow the incorporation of newer versions in FreeBSD[0], specifically: FreeBSD could include the Berkeley DB package, and commercial companies would only have to separately license Berkeley DB if they used it outside of the functionality provided by FreeBSD, that is, FreeBSD can use DB, and companies that ship FreeBSD code can use DB as long as they only use it in the same ways that FreeBSD uses it. IANAL, nor do I have any first-hand knowledge of the previous discussions on this topic. However, it would seem to me that this modification to the license into something more akin to the LGPL should largely solve that issue. I also mentioned the technical issues that I've seen raised on the list (specifically, the size of the newer versions of the library and the unwillingness/lack of interest in incorporating a significantly larger version of Berkeley DB within libc). His response was: The footprint isn't that much bigger when only the access methods are used. Regardless, with shared libraries, who cares? The "new feature" it offers is that it doesn't drop core. :-) I brought up the idea that perhaps additional compile-time options could be used so that the linked in version of the libraries would only have the necessary code for the "access methods", and the rest of the code simply wouldn't be present in the standard FreeBSD binary as a result of #ifdef's sprinkled throughout the code. Therefore you wouldn't be able to violate the terms of the license, unless you went out of your way to build your own fully-functional version of Berkeley DB, such as using the port. However, my impression was that he did not consider this to be a feasible idea. There have been no changes to the license or any apparant willingness on Sleepycat's part to modify it in the ensuing 12 months. Whether or not there has been a shift from previous positions on this subject, I am not qualified to say. However, it seems to me that Keith has apparently addressed the issues he can in such a way that it would be compatible with the aims and goals of the FreeBSD Project, although it would also require work from this side -- obviously someone would have to go through the code and make the necessary changes as to which set of library calls we'd be using. The real shame in all this is that I fear that many future FreeBSD users will get the wrong impression of Berkeley DB, simply because their only exposure to it will be through the system-supplied db 1.85 routines. In addition, Linux users appear to be able to get the full benefit of more modern versions of Berkeley DB being incorporated by default, which would seem to leave us at a disadvantage. However, I get the feeling that there is more to this issue than I have learned so far, or am likely to ever learn. As far as I'm concerned, I think this is going to be my last post on this subject. The appropriate people have been informed (or reminded yet once again) of the situation, and are going to get together and work towards getting this issue resolved or not, and either way there's not really anything more I can say or do on this subject that could potentially be considered to be useful. [1] [0] Yes, I checked with him first to confirm that I may directly quote him. ;-) [1] That's assuming that I have done or said anything useful on this subject. ;-( -- These are my opinions -- not to be taken as official Skynet policy == Brad Knowles, [EMAIL PROTECTED]|| Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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, libungif, uulib, automake autoconf. That will also install some other things (Mesa, TCL, TK...) we need for KDE, that's OK. Make the following links : ln -s /usr/X11R6/bin/moc2 /usr/X11R6/bin/moc ln -s /usr/X11R6/lib/libgtk12.so.2 /usr/X11R6/lib/libgtk.so ln -s /usr/X11R6/lib/libqt2.so.3 /usr/X11R6/lib/libqt.so ln -s /usr/X11R6/lib/libqt2.so.3 /usr/X11R6/lib/libqt.so.3 ln -s /usr/local/lib/libpng.so.3 /usr/X11R6/lib/libpng.so ln -s /usr/local/lib/libpng.so.3 /usr/X11R6/lib/libpng.so.3 ln -s /usr/X11R6/include/qt2 /usr/X11R6/include/qt ln -s /usr/X11R6/include/gtk12 /usr/X11R6/include/gtk ln -s /usr/X11R6/include/gtk10 /usr/X11R6/include/gtk ln -s /usr/X11R6/bin/gtk12-config /usr/X11R6/bin/gtk-config That will "fool" the software into thinking he's accessing the "old" versions, when in fact it's using the new ones. In case they already exist, rename any "older" versions/dirs of any of those listed above that might conflict when making the links. Run the "./configure" script for KDE using the following options : --with-qt-dir=/usr/X11R6/bin --with-qt-includes=/usr/X11R6/include/qt2 --with-qt-libraries=/usr/X11R6/lib --with-extra-includes=/usr/local/include --with-extra-libs=/usr/local/lib You might want to add some other configuration options, like "--enable-threads", etc. See the "./configure" script for other possible options. Use GMAKE (!very important!) to make/install KDE, NOT the BSD "native" Make. Add "/usr/local/kde/lib/" to your LD_LIBRARY_PATH, e.g., add it to the line "ldconfig_paths=..." in /etc/defaults/rc.conf Add "/usr/local/kde/bin" to your path, e.g. add it to your ".cshrc" file (for example, if you are using the default shell) The order in which you make the KDE parts is important : first make/install "Support", then "KDE-qt-add-on", then "Libs", then "Base". From there on it almost makes no difference in what order you make/install the rest. In a couple of parts during the compilations it will stop with an error saying that "this or that" is not there, or it's bad, etc. I had to remove those dirs and run GMake again... :-( Add a file called ".xinitrc" to you home dir, that says "exec startkde", and Run "xinit". "Disclaimer" : This is by NO MEANS neither a "recommendable" or "clean" way of forcing KDE2-preALPHA to run on -current, it's just what I did, and clearly it's NOT guaranteed to work. ;-) !Good Luck! - Original Message - From: "VINSON WAYNE HOWARD" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, May 02, 2000 6:46 PM Subject: 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 distribution, would be great. Thanks in advance, Wayne To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message 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.7 in /usr/ports/databases/db. If this is an issue for some nntp software, perhaps that port (the freebsd 'port collection' port...) should build and use the newer version of db? Would that help whatever issue got you interested in this? Now, correct me if I'm wrong, but I believe that db 1.85 is pretty widely known to be broken in a number of ways (see http://www.sleepycat.com/historic.html) Let us assume for the moment that the licensing issues mean that freebsd can't include the newer versions of Berkley db in the main system. Should we consider fixing a few of the nastier problems in 1.85? (whatever those would be...). Or does trying to fix those open a different can of worms? --- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
subscribe freebsd-current subscribe cvs-all
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 binaries, but I could compile on 4.0-stable. You need to set $KDEDIR and $QTDIR before you configure. -Arun 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?
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/getpwent.c lib/libc/gen/ttyname.c libexec/ypxfr sbin/init sys/dev/aic7xxx usr.bin/finger usr.bin/tsort usr.bin/vacation usr.sbin/sa usr.sbin/rpc.yppasswdd usr.sbin/rpc.ypupdated usr.sbin/ypserv contrib/amd contrib/cvs lib/libkvm pr/9350 is an example of db bugs effecting vi. (Would someone PLEASE apply the simple patch and close the damn PR!) -- Danny J. Zerkel [EMAIL PROTECTED] 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?
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 the "libgcc" code, but that code is specifically exempted from the GPL. Programs that link against the Berkeley DB 2.x library, however, will end up including the DB code, and thus end up including code covered by the 2.x licence. [Note: of course, if you link against a shared library, the actual code from the library doesn't appear in your binary. It seems to be the general consensus opinion that the courts would treat this the same as the static linking case, i.e. your binary would be covered under the licence "as if" you had statically linked against the relevant library, but I don't know if this has ever been tested in court anywhere. If you're in a situation where the legalities really matter, you should probably ask a real lawyer instead of relying on the semi-informed opinion of people posting to mailing lists.] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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). -- -- David([EMAIL PROTECTED]) 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?
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 commit it. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 "brute
force" method, ending up with (so far) this:
ppc0: Parallel port at port 0x378-0x37f on isa0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
ppbus_attach(0xc0840d00) -- added this line
ppi0: Parallel I/O on ppbus0
ppi0 - BUS_READ_IVAR returns IRQ 0 -- added this line
lpt0: Printer on ppbus0
lpt0: Polled port
plip0: PLIP network interface on ppbus0
...with the enclosed patches, the geek port once again works, but I really
don't have the know-how to really test it correctly... I'm able to read
write the data lines on the port without blowing up the machine.
Essentially, ppiopen() in sys/dev/ppbus/ppi.c will not call
BUS_SETUP_INTR() if it sees an IRQ of 0. (Not using polled mode on the
parallel port def in the config file didn't make any difference.)
I'm going to beat on this some more over the next few days, but this is a
start. I'd be interested to know if anyone can make the
"ppi-intr_resource != 0 -- activating IRQ" message show up when opening
/dev/ppi0, especially if their machine doesn't crash when opening up
the device without this patch...
--mike
---
diff -u /usr/src/sys/dev/ppbus/ppbconf.c newppbus/ppbconf.c
--- /usr/src/sys/dev/ppbus/ppbconf.cSun Jan 23 09:41:04 2000
+++ newppbus/ppbconf.c Tue May 2 22:45:52 2000
@@ -390,6 +390,7 @@
static int
ppbus_attach(device_t dev)
{
+ printf("ppbus_attach(%p)\n", dev);
/* Locate our children */
bus_generic_probe(dev);
diff -u /usr/src/sys/dev/ppbus/ppi.c newppbus/ppi.c
--- /usr/src/sys/dev/ppbus/ppi.cSun Jan 23 09:41:04 2000
+++ newppbus/ppi.c Tue May 2 23:04:43 2000
@@ -169,6 +169,8 @@
/* retrive the irq */
BUS_READ_IVAR(device_get_parent(dev), dev, PPBUS_IVAR_IRQ, irq);
+ printf("ppi%d - BUS_READ_IVAR returns IRQ %d\n",
+ device_get_unit(dev), irq);
/* declare our interrupt handler */
ppi-intr_resource = bus_alloc_resource(dev, SYS_RES_IRQ,
@@ -271,10 +273,16 @@
return (res);
ppi-ppi_flags |= HAVE_PPBUS;
-
+
+ if (!ppi-intr_resource) {
/* register our interrupt handler */
- BUS_SETUP_INTR(device_get_parent(ppidev), ppidev, ppi-intr_resource,
+ printf("ppi-intr_resource != 0 -- activating IRQ\n");
+ BUS_SETUP_INTR(device_get_parent(ppidev), ppidev,
+ppi-intr_resource,
INTR_TYPE_TTY, ppiintr, dev, ppi-intr_cookie);
+ }
+ else {
+ printf("ppi-intr_resource = 0 -- not using IRQ\n");
+ }
}
ppi-ppi_count += 1;
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
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: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
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/ghostscript5. *** Error code 1 Stop in /usr/ports/print/ghostscript5. *** Error code 1 Stop in /usr/ports/print/ghostscript5. hmmm, okay, that is odd, considering the other two have png.3 dependencies, and they build... 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 WARRANTY: see the file PUBLIC for details. showpage, press return to continue GS And there it sits. Nothing happending. ps -x shows: 3020 p5 I+ 0:00.70 gs /usr/local/share/ghostscript/5.50/examples/tiger.ps Ghostscript6: This, too, will build and install. When I run "gs" this time, I get: bash-2.03# gs /usr/local/share/ghostscript/6.01/examples/tiger.ps Aladdin Ghostscript 6.01 (2000-03-17) Copyright (C) 2000 Aladdin Enterprises, Menlo Park, CA. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Error: /invalidfileaccess in --.outputpage-- Operand stack: 1 true Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1 3 %oparray_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- 0 4 %oparray_pop --nostringval-- --nostringval-- --nostringval-- --nostringval-- Dictionary stack: --dict:929/983(ro)(G)-- --dict:0/20(G)-- --dict:67/200(L)-- --dict:45/100(L)-- Current allocation mode is local Current file position is 78508 Aladdin Ghostscript 6.01: Unrecoverable error, exit code 1 bash-2.03# Sigh. Any ideas or suggestions? Thank you, Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. showpage, press return to continue GS And there it sits. Nothing happending. ps -x shows: 3020 p5 I+ 0:00.70 gs /usr/local/share/ghostscript/5.50/examples/tiger.ps As far as I know, GS 5.5 is build w/o default output device; e.g. try to setenv GS_DEVICE x11or export GS_DEVICE=x11 before starting gs. Maybe something similar applies to GS6. Regards Konrad HeuerPersonal Bookmarks: Gesellschaft für wissenschaftliche Datenverarbeitung mbH GÖttingen http://www.freebsd.org Am Faßberg, D-37077 GÖttingen http://www.daemonnews.org Deutschland (Germany) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 WARRANTY: see the file PUBLIC for details. showpage, press return to continue GS snip bash-2.03# gs /usr/local/share/ghostscript/6.01/examples/tiger.ps Aladdin Ghostscript 6.01 (2000-03-17) Copyright (C) 2000 Aladdin Enterprises, Menlo Park, CA. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Error: /invalidfileaccess in --.outputpage-- snip Try gs -sDEVICE=x11 /usr/local/share/ghostscript/6.01/examples/tiger.ps gs --help will give you available options. For viewing stuff on the screen, install a front-end such as gv -- there's no point in messing with gs directly. Rahul. 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:16 PM +0200 2000/5/2, Poul-Henning Kamp wrote: Sleepycats license is not FreeBSD compatible :-/ I don't understand. Reading http://www.sleepycat.com/license.net, it seems to me that FreeBSD meets all the necessary requirements. Can someone who understands the details of the licensing issues either explain the situation to me, or provide pointers to references that do? I mean, I found http://www.freebsd.org/cgi/getmsg.cgi?fetch=1468896+0+/usr/local/www/ db/text/1999/freebsd-current/19990607.freebsd-current and http://www.freebsd.org/cgi/getmsg.cgi?fetch=932597+0+/usr/local/www/d b/text/1999/freebsd-current/19990607.freebsd-current, but I must be missing something because I still don't understand how it is "worse than the GPL" or why it would require "publication of sources to all binaries linked against libc". Technical issues I can understand, but I just don't get this licensing issue. [0] Out of curiosity, is there a public list of all the people who have commit access to FreeBSD? Yes, it's in the CVS tree in the file CVSROOT/access and in the Handbook as well. Is there a version online that is actually kept up-to-date? I only count fifteen names at http://www.freebsd.org/handbook/staff.html, 178 names at http://www.freebsd.org/handbook/staff-committers.html, and nine unique names at http://www.freebsd.org/handbook/staff-doc.html. I was under the impression that there are well over 200 people that currently have commit access? Hmm. Looking at http://www.FreeBSD.org/cgi/cvsweb.cgi/CVSROOT/access.diff?r1=texttr1 =1.1r2=texttr2=1.147f=c, it looks to me like maybe there are only 199 current committers, although this number seems to slightly disagree with what I counted above, unless there are additional duplicates on those separate lists that I failed to eliminate. Hmm. I don't suppose we could get a link to this page from the handbook, could we? If I can figure out a better way to list all these names and to break them up into the appropriate groups, I'll submit a PR. [0] On a side note, can anyone tell me why the search interface on the FreeBSD web site is showing messages such as http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=1071225+1073014+/usr/loca l/www/db/text/1999/freebsd-current/19990607.freebsd-current that have a date/time stamp of "Sat, 15 May 1999 03:09:28 +0400" to instead have "Score: 1204; Lines: 47; 20-Jan-1998; Archive: freebsd-current" in the summary response to the search? How about http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=1417079+1418703+/usr/loca l/www/db/text/2000/freebsd-questions/2220.freebsd-questions, which has a date/time stamp of "Thu, 3 Feb 2000 09:35:19 -0600" but shows up in the summary response as having "Score: 1305; Lines: 43; 18-Dec-1996; Archive: freebsd-questions"? -- These are my opinions -- not to be taken as official Skynet policy == Brad Knowles, [EMAIL PROTECTED]|| Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 need to make world and kernel to get them both into sync. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
