Re: 6.0 release date and stability
On Fri, Oct 21, 2005 at 08:21:27PM +0200, dick hoogendijk wrote: > On Wed, 19 Oct 2005 18:53:51 -0400 > Kris Kennaway <[EMAIL PROTECTED]> wrote: > > > On Wed, Oct 19, 2005 at 11:36:35PM +0200, Ronald Klop wrote: > > > COMPAT_FREEBSD5 is meant for running FreeBSD-5 binary applications. > > > If you have them it's ok. If you recompile everything you don't > > > need the COMPAT_FREEBSD5 stuff. If you don't have the source of > > > some of your FreeBSD-5 applications you have to run with > > > COMPAT_FREEBSD5. And the switch to 6 is easier because your > > > 5-applications keep running. > > > > Yes. As long as you only use your old 5.x applications, you're fine > > with just the compat. The problem is when you start to link *new* 6.0 > > applications with *old* 5.x libraries (e.g. by installing a new port, > > e.g. a new X application, without rebuilding your 5.x X installation > > first). > > > > Thus, unless you upgrade all your 5.x ports (well, actually "many", > > i.e. only those that provide libraries or shared object modules, but > > it's easier to just do "all") you'll end up with 6.0 binaries that are > > linked to e.g. two versions of libc at once (the 5.x libc and the 6.0 > > libc), which is a recipe for disaster. > > I learn much from these kind of answers. Thanks Kris. > What I don't get is how I can /get rid/ of these old 4.x / 5.x > libraries on my "new" updated 6.0 system. > > I guess teh way to go is: > cvsup to the latest 6.0 source; do the well-known buildworld thing; > rebuild the kernel without compat_freebsd4/5 option (???) and rebuild > every port with portupgrade -fa > > But he old libraries are still on the system than, aren't they? > Or will they not be used and if not, why? Use libchk and pkg_which..see their manpages. Kris pgpIsHqejJYqA.pgp Description: PGP signature
Re: 6.0 release date and stability
On Wed, 19 Oct 2005 18:53:51 -0400 Kris Kennaway <[EMAIL PROTECTED]> wrote: > On Wed, Oct 19, 2005 at 11:36:35PM +0200, Ronald Klop wrote: > > COMPAT_FREEBSD5 is meant for running FreeBSD-5 binary applications. > > If you have them it's ok. If you recompile everything you don't > > need the COMPAT_FREEBSD5 stuff. If you don't have the source of > > some of your FreeBSD-5 applications you have to run with > > COMPAT_FREEBSD5. And the switch to 6 is easier because your > > 5-applications keep running. > > Yes. As long as you only use your old 5.x applications, you're fine > with just the compat. The problem is when you start to link *new* 6.0 > applications with *old* 5.x libraries (e.g. by installing a new port, > e.g. a new X application, without rebuilding your 5.x X installation > first). > > Thus, unless you upgrade all your 5.x ports (well, actually "many", > i.e. only those that provide libraries or shared object modules, but > it's easier to just do "all") you'll end up with 6.0 binaries that are > linked to e.g. two versions of libc at once (the 5.x libc and the 6.0 > libc), which is a recipe for disaster. I learn much from these kind of answers. Thanks Kris. What I don't get is how I can /get rid/ of these old 4.x / 5.x libraries on my "new" updated 6.0 system. I guess teh way to go is: cvsup to the latest 6.0 source; do the well-known buildworld thing; rebuild the kernel without compat_freebsd4/5 option (???) and rebuild every port with portupgrade -fa But he old libraries are still on the system than, aren't they? Or will they not be used and if not, why? -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: routing question
Matt Smith wrote: Hello all, I have a situation where I have my FreeBSD box that I want to run 2 Unreal IRCD's on both using port 6667. I've set up virtual IP addressing and one IRCD will run on 192.168.1.5:6667 and the other one will run on 192.168.1.7:6667. my problem is how would I go about routing the traffic into the machine so both the IRCD's can be used by different people using just a linksys router (I don't think it's possible, but I thought I bounce it off you guys. Only if there on your own private subnet, otherwise you must have multiple public IP addresses and (nat)forward them to the private ones accordingly. If you have only 1 public IP adress you could use multiple ports on the public IP and mapped them back to the right IP & ports, say (public IP):6667 -> 192.168.1.7:6667 and (public IP):6668 -> 192.168.1.7:6667 however with this option you could have saved your hassle to create a alias and just used the 6668 port for your other daemon on 192.168.1.5 -- mph ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: routing question
Hello all, I have a situation where I have my FreeBSD box that I want to run 2 Unreal IRCD's on both using port 6667. I've set up virtual IP addressing and one IRCD will run on 192.168.1.5:6667 and the other one will run on 192.168.1.7:6667. my problem is how would I go about routing the traffic into the machine so both the IRCD's can be used by different people using just a linksys router (I don't think it's possible, but I thought I bounce it off you guys. Matt Smith ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
unknown message
Hello, list. Today, when i was working remotely with my proxy server this message appeared on console Assertion failed: (lu->lu_myreq->lr_watcher == ((void *)0)), function _lock_acquire, file /usr/src/lib/libpthread/sys/lock.c, line 170. There was no point about this message in /var/log/message. The proxy software is oops. uname -srm is: FreeBSD 5.4-RELEASE-p8 i386 and dmesg is: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-RELEASE-p8 #0: Fri Oct 21 12:08:06 AZST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PROXY_AZERIN Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3000+ (2009.79-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0xfc0 Stepping = 0 Features=0x78bfbff AMD Features=0xe050 real memory = 1610547200 (1535 MB) avail memory = 1572720640 (1499 MB) npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf0-0xcf3,0xcf8-0xcff on acpi0 pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) pci0: at device 2.0 (no driver attached) pci0: at device 2.1 (no driver attached) pci0: at device 2.2 (no driver attached) pci0: at device 5.0 (no driver attached) pci0: at device 6.0 (no driver attached) atapci0: port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 8.0 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 atapci1: port 0xdc00-0xdc0f,0xb70-0xb73,0x970-0x977,0xbf0-0xbf3,0x9f0-0x9f7 irq 10 at device 10.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 pcib1: at device 11.0 on pci0 pci1: on pcib1 pcib2: at device 14.0 on pci0 pci2: on pcib2 pci2: at device 6.0 (no driver attached) fxp0: port 0xa000-0xa03f mem 0xf500-0xf50f,0xf510-0xf5100fff irq 5 at device 8.0 on pci2 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:90:27:5d:8d:a8 ncr0: port 0xa400-0xa4ff mem 0xf5102000-0xf5102fff,0xf5101000-0xf51010ff irq 11 at device 10.0 on pci2 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 orm0: at iomem 0xd-0xd0fff,0xc8000-0xc,0xc-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter "TSC" frequency 2009787198 Hz quality 800 Timecounters tick every 10.000 msec ipfw2 initialized, divert disabled, rule-based forwarding enabled, default to accept, logging disabled ad0: 38165MB [77542/16/63] at ata0-master UDMA100 acd0: CDROM at ata0-slave PIO4 Waiting 2 seconds for SCSI devices to settle da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) Mounting root from ufs:/dev/ad0s1a ohci0: mem 0xf8005000-0xf8005fff irq 10 at device 2.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ohci1: mem 0xf800-0xf8000fff irq 10 at device 2.1 on pci0 usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered ehci0: mem 0xf8001000-0xf80010ff irq 10 at device 2.2 on pci0 usb2: EHCI version 1.0 usb2: companion controllers, 4 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 8 ports with 8 removable, self powered -- Elkhanzade Sarkhan Azerin ISP, U.Hajibeyov 36, Baku Systems Administrator Phone work : +994124982533 e-mail : [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.0 release date and stability
On Oct 20, 2005, at 4:16 PM, Michael Nottebrock wrote: On Thursday, 20. October 2005 21:20, Vivek Khera wrote: personally, I don't see the point of doing that. just let your ports naturally get replaced as they are upgraded due to version bumps and such. That is dangerous, see other replies in this thread for the reasons why. I stand corrected; you need to update any provider of shared object libs at the minimum. Probably also any consumer of those shared objects too. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
