Re: dlsym can't use handle returned by dlopen?
On Thu, Nov 13, 2008 at 09:00:21AM +0100, Markus Hoenicka wrote: Quoting Jeremy Chadwick [EMAIL PROTECTED]: I know that the .so's you're loading with dlopen() need to be built a specific way/with certain arguments, otherwise they won't work (I believe what I saw was dlsym() returning NULL). My symbol names were getting stomped on, and there was a compiler flag that addressed that. Is that a BSD-specific problem? As mentioned previously, I don't run into trouble on other platforms. Is there any documentation available which tells me how to build a dlopen()'able object in a portable way? I wouldn't classify is as a problem in any way, and I cannot imagine it's specific to BSD; I'm much more inclined to believe it's specific to gcc. When I looked at the resulting symbol names using nm or objdump, certain characters were prepended to them. There's a gcc or ld flag which disables this behaviour. I'll have to dig around to remind myself what it is. Once I read about it, it made perfect sense. Again, if you want me to write some code and provide some output of what I'm talking about, I can do so. function_pointer = dlsym(RTLD_DEFAULT, function_name); Why is that? Or rather: what am I doing wrong? This code right here is *completely* wrong. RTLD_DEFAULT is a mode bit for dlopen(). I'm willing to bet a strict set of warnings would Citing the FreeBSD dlsym(3) man page: If dlsym is called with the special handle RTLD_DEFAULT, the search for the symbol follows the algorithm used for resolving undefined symbols when objects are loaded. You probably had RTLD_LAZY and RTLD_NOW in mind which are dlopen() flags. BTW RTLD_NEXT works just as well instead of RTLD_DEFAULT. You are right -- I missed that part of the man page, and I was most definitely thinking of RTLD_LAZY and RTLD_NOW. I cannot explain the behaviour using dlsym(RTLD_DEFAULT, ...). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dlsym can't use handle returned by dlopen?
Quoting Jeremy Chadwick [EMAIL PROTECTED]: When I looked at the resulting symbol names using nm or objdump, certain characters were prepended to them. There's a gcc or ld flag which disables this behaviour. I'll have to dig around to remind myself what it is. Once I read about it, it made perfect sense. Again, if you want me to write some code and provide some output of what I'm talking about, I can do so. I'd greatly appreciate any help here. I feel what I'm doing now is writing ugly hacks to make things work somehow. I'd prefer to do it properly. regards, Markus -- Markus Hoenicka [EMAIL PROTECTED] (Spam-protected email: replace the quadrupeds with mhoenicka) http://www.mhoenicka.de ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dlsym can't use handle returned by dlopen?
Quoting Jeremy Chadwick [EMAIL PROTECTED]: I know that the .so's you're loading with dlopen() need to be built a specific way/with certain arguments, otherwise they won't work (I believe what I saw was dlsym() returning NULL). My symbol names were getting stomped on, and there was a compiler flag that addressed that. Is that a BSD-specific problem? As mentioned previously, I don't run into trouble on other platforms. Is there any documentation available which tells me how to build a dlopen()'able object in a portable way? function_pointer = dlsym(RTLD_DEFAULT, function_name); Why is that? Or rather: what am I doing wrong? This code right here is *completely* wrong. RTLD_DEFAULT is a mode bit for dlopen(). I'm willing to bet a strict set of warnings would Citing the FreeBSD dlsym(3) man page: If dlsym is called with the special handle RTLD_DEFAULT, the search for the symbol follows the algorithm used for resolving undefined symbols when objects are loaded. You probably had RTLD_LAZY and RTLD_NOW in mind which are dlopen() flags. BTW RTLD_NEXT works just as well instead of RTLD_DEFAULT. regards, Markus -- Markus Hoenicka [EMAIL PROTECTED] (Spam-protected email: replace the quadrupeds with mhoenicka) http://www.mhoenicka.de ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dlsym can't use handle returned by dlopen?
On Thu, Nov 13, 2008 at 09:20:59AM +0100, Markus Hoenicka wrote: Quoting Jeremy Chadwick [EMAIL PROTECTED]: When I looked at the resulting symbol names using nm or objdump, certain characters were prepended to them. There's a gcc or ld flag which disables this behaviour. I'll have to dig around to remind myself what it is. Once I read about it, it made perfect sense. Again, if you want me to write some code and provide some output of what I'm talking about, I can do so. I'd greatly appreciate any help here. I feel what I'm doing now is writing ugly hacks to make things work somehow. I'd prefer to do it properly. No problem. I'll try to get something small/simple written up tonight (I'm at work right now) and send it out. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
Hi Guys I am running RAID 10. Here is the dmesg output: $ dmesg Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-PRERELEASE #0: Fri Aug 29 13:42:13 CEST 2008 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/KERNEL Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5450 @ 3.00GHz (2995.54-MHz K8-class CPU) Origin = GenuineIntel Id = 0x10676 Stepping = 6 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xce3bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,b19 AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF Cores per package: 4 usable memory = 17166688256 (16371 MB) avail memory = 16619601920 (15849 MB) ACPI APIC Table: DELL PE_SC3 FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: DELL PE_SC3 on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci4: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci4 pci5: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge at device 0.0 on pci5 pci6: ACPI PCI bus on pcib3 pcib4: PCI-PCI bridge at device 0.0 on pci6 pci7: PCI bus on pcib4 bce0: Broadcom NetXtreme II BCM5708 1000Base-T (B2) mem 0xf400-0xf5ff irq 16 at device 0.0 on pci7 miibus0: MII bus on bce0 brgphy0: BCM5708C 10/100/1000baseTX PHY PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bce0: Ethernet address: 00:1e:c9:d5:88:f0 bce0: [ITHREAD] bce0: ASIC (0x57081020); Rev (B2); Bus (PCI-X, 64-bit, 133MHz); F/W (0x04000305); Flags( MFW MSI ) pcib5: ACPI PCI-PCI bridge at device 1.0 on pci5 pci8: ACPI PCI bus on pcib5 pcib6: PCI-PCI bridge at device 0.3 on pci4 pci9: PCI bus on pcib6 pcib7: ACPI PCI-PCI bridge at device 3.0 on pci0 pci1: ACPI PCI bus on pcib7 mfi0: Dell PERC 6 port 0xec00-0xecff mem 0xfc68-0xfc6b,0xfc64-0xfc67 irq 16 at device 0.0 on pci1 mfi0: Megaraid SAS driver Ver 2.00 mfi0: 2145 (279883150s/0x0020/info) - Shutdown command received from host mfi0: 2146 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/1f0c/1028) mfi0: 2147 (boot + 3s/0x0020/info) - Firmware version 1.11.52-0396 mfi0: 2148 (boot + 3s/0x0008/info) - Battery Present mfi0: 2149 (boot + 3s/0x0020/info) - Package version 6.0.2-0002 mfi0: 2150 (boot + 21s/0x0004/info) - Enclosure (SES) discovered on PD 20(c None/p0) mfi0: 2151 (boot + 21s/0x0002/info) - Inserted: Encl PD 20 mfi0: 2152 (boot + 21s/0x0002/info) - Inserted: PD 20(c None/p0) Info: enclPd=20, scsiType=d, portMap=09, sasAddr=5001e0f03d0c6f00, mfi0: 2153 (boot + 21s/0x0002/info) - Inserted: PD 00(e0x20/s0) mfi0: 2154 (boot + 21s/0x0002/info) - Inserted: PD 00(e0x20/s0) Info: enclPd=20, scsiType=0, portMap=00, sasAddr=5000cca00904b705, mfi0: 2155 (boot + 21s/0x0002/info) - Inserted: PD 01(e0x20/s1) mfi0: 2156 (boot + 21s/0x0002/info) - Inserted: PD 01(e0x20/s1) Info: enclPd=20, scsiType=0, portMap=01, sasAddr=5000cca009024231, mfi0: 2157 (boot + 21s/0x0002/info) - Inserted: PD 02(e0x20/s2) mfi0: 2158 (boot + 21s/0x0002/info) - Inserted: PD 02(e0x20/s2) Info: enclPd=20, scsiType=0, portMap=02, sasAddr=5000cca00904d92d, mfi0: 2159 (boot + 21s/0x0002/info) - Inserted: PD 03(e0x20/s3) mfi0: 2160 (boot + 21s/0x0002/info) - Inserted: PD 03(e0x20/s3) Info: enclPd=20, scsiType=0, portMap=03, sasAddr=5000cca009048865, mfi0: 2161 (boot + 21s/0x0002/info) - Inserted: PD 04(e0x20/s4) mfi0: 2162 (boot + 21s/0x0002/info) - Inserted: PD 04(e0x20/s4) Info: enclPd=20, scsiType=0, portMap=04, sasAddr=5000cca009048d2d, mfi0: 2163 (boot + 21s/0x0002/info) - Inserted: PD 05(e0x20/s5) mfi0: 2164 (boot + 21s/0x0002/info) - Inserted: PD 05(e0x20/s5) Info: enclPd=20, scsiType=0, portMap=05, sasAddr=5000cca009048f31, mfi0: 2165 (279879506s/0x0020/info) - Time established as 11/13/08 8:18:26; (26 seconds since power on) mfi0: 2166 (279879548s/0x0008/info) - Battery temperature is normal mfi0: [ITHREAD] pcib8: ACPI PCI-PCI bridge at device 4.0 on pci0 pci10: ACPI PCI bus on pcib8 pcib9: PCI-PCI bridge at device 5.0 on pci0 pci11: PCI bus on pcib9
Re: tool to recover fat partition
On Wed, 12 Nov 2008 18:32:14 -0200, Gonzalo Nemmi [EMAIL PROTECTED] wrote: So ... newfs_msdos /dev/insert_typo_in_here .. new filesystem succesfully created ... lost partition on the wrong drive ... Is there a tool to recover the files on said partition in FreeBSD (7 release)? Thanks for you help :) It seems my problems can at least be helpful to someone else. :-) There are many good tools for recovering data from MSDOS partitions, but you'll have to check which one serves your particular needs best, depending on the amount of damage done to the file system. From the ports, there's magicrescue in the first place for file recovery. To scan and repair disk partitions, you can use testdisk. If everything else fails, go use the basics: The Sleuth Kit with its dls, dls or ils tools. There's helpful documentation installed that gives informations not mentioned in the manpages. I would recommend you do first do a dd copy of the drive, just in order to do no harm to the partition where your important files are located. Then, do all operations on the dd image, it's mich more safe. If dd is not possible, use dd_rescue or ddrescue. For most operations, it's good to use mdconfig to put the dd file onto a md device which is then used by the particular program. I can imagine how you feel about data loss, so good luck! -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tool to recover fat partition
On Wed, 12 Nov 2008 18:32:14 -0200, Gonzalo Nemmi [EMAIL PROTECTED] wrote: So ... newfs_msdos /dev/insert_typo_in_here .. new filesystem succesfully created ... lost partition on the wrong drive ... Is there a tool to recover the files on said partition in FreeBSD (7 release)? Thanks for you help :) It seems my problems can at least be helpful to someone else. :-) There are many good tools for recovering data from MSDOS partitions, but you'll have to check which one serves your particular needs best, depending on the amount of damage done to the file system. From the ports, there's magicrescue in the first place for file recovery. To scan and repair disk partitions, you can use testdisk. If everything else fails, go use the basics: The Sleuth Kit with its dls, dls or ils tools. There's helpful documentation installed that gives informations not mentioned in the manpages. I would recommend you do first do a dd copy of the drive, just in order to do no harm to the partition where your important files are located. Then, do all operations on the dd image, it's mich more safe. If dd is not possible, use dd_rescue or ddrescue. For most operations, it's good to use mdconfig to put the dd file onto a md device which is then used by the particular program. I can imagine how you feel about data loss, so good luck! -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
On Thu, Nov 13, 2008 at 02:24:33AM -0800, Unga wrote: Hi all I have compiled and installed grub-0.97.tar.gz on FreeBSD 7.0 (i386). It shows the grub cannot recognize ufs2 file systems. grub root (hd1,0, Possible partitions are: Partition num: 0, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'b', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'd', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'e', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'f', Filesystem type unknown, partition type 0xa5 All stage1, stage2 and *_stage1_5 are in /boot/grub/. The fstype used for bsdlabel for b is swap and for others its 4.2BSD. Files systems were created as follows: newfs -U /dev/ad2s1a newfs /dev/ad2s1d newfs -U /dev/ad2s1e newfs -U /dev/ad2s1f Do others experience this issue? Do I need to patch the Grub to recognize ufs2 file systems? Your reply is very much appreciated. How about asking the GNU GRUB folks if GRUB 0.97 supports UFS2? Also, GRUB is up to 1.96, and does work with amd64. The port is horribly outdated. ftp://alpha.gnu.org/gnu/grub/ -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.4 - filesystem full
Booting into single-user via serial console, KVM, KVM-over-IP, or iLO/LOM (if HP/Compaq) is sufficient. If you have servers which are remote and you lack any of these features, I'm both surprised and not sure what to tell you. You'll encounter this problem with any OS, not just FreeBSD. I'm looking for something similar to /forcefsck file on the linux systems. Alexander Varshavchick, Metrocom Joint Stock Company Phone: (812)718-3322, 718-3115(fax) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
--- On Thu, 11/13/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: How about asking the GNU GRUB folks if GRUB 0.97 supports UFS2? It seems some old version of GRUB on a old version of FreeBSD has worked: http://lists.freebsd.org/pipermail/freebsd-hackers/2004-May/006944.html Also, GRUB is up to 1.96, and does work with amd64. The port is horribly outdated. I don't mind try GRUB 1.96. The problem is I have never used GRUB2 and I have no idea how to configure it. Is there a good notes/documentation on how to use GRUB2? What I need basically is where to put files (eg. stage1, stage2 and *_stage1_5 of GRUB1 in /boot/grub/.) and a sample configuration file. Anyway meanwhile I'll try to find some documentation. ftp://alpha.gnu.org/gnu/grub/ I got my file from above location. Regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
On Thu, Nov 13, 2008 at 03:16:40AM -0800, Unga wrote: --- On Thu, 11/13/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: How about asking the GNU GRUB folks if GRUB 0.97 supports UFS2? It seems some old version of GRUB on a old version of FreeBSD has worked: http://lists.freebsd.org/pipermail/freebsd-hackers/2004-May/006944.html Also, GRUB is up to 1.96, and does work with amd64. The port is horribly outdated. I don't mind try GRUB 1.96. The problem is I have never used GRUB2 and I have no idea how to configure it. Is there a good notes/documentation on how to use GRUB2? What I need basically is where to put files (eg. stage1, stage2 and *_stage1_5 of GRUB1 in /boot/grub/.) and a sample configuration file. Anyway meanwhile I'll try to find some documentation. ftp://alpha.gnu.org/gnu/grub/ I got my file from above location. I think these kinds of questions should probably go to the GNU GRUB folks though, don't you think? I don't mean to sound like I'm stepping on your efforts, but the sysutils/grub port has very little to it (meaning, issues/problems of this type should very likely be issues with GRUB itself and not with the port or FreeBSD). It would be really cool if since you're working on getting GRUB2 working, you could make a port for it, e.g. sysutils/grub2. :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
On Thu, Nov 13, 2008 at 01:29:11PM +0100, VeeJay wrote: If it looks healthy, why there are these errors on the screen? Is it controller problem or disk? SCSI normally reports 3 things when it encounters an error (particularly disk errors): Sense Key (SK), Additional Sense Code (ASC), and Additional Sense Code Qualifier (ASCQ). What appears in the below screenshot is a large amount of sense data, but I can't make heads or tails out of it, because it's written in a driver-centric manner (Encl PD means nothing to me). I can read part of the CDB data, but it doesn't tell me much. Scott Long might know. http://digitalfreaks.org/~lavalamp/20081023_server3_screen_dump.png You should try asking the system manufacturer if they know what any of the data means. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
On Thu, Nov 13, 2008 at 02:16:58PM +0100, VeeJay wrote: I have asked the system manufacturers (Dell) but they don't provide support for FreeBSD based systems [?] Thats why I have only hope here with FreeBSD List... I've CC'd Scott Long, who is the author of the mfi(4) driver. He should be able to explain what the error messages mean. Scott, check out the URL below. On Thu, Nov 13, 2008 at 1:41 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Thu, Nov 13, 2008 at 01:29:11PM +0100, VeeJay wrote: If it looks healthy, why there are these errors on the screen? Is it controller problem or disk? SCSI normally reports 3 things when it encounters an error (particularly disk errors): Sense Key (SK), Additional Sense Code (ASC), and Additional Sense Code Qualifier (ASCQ). What appears in the below screenshot is a large amount of sense data, but I can't make heads or tails out of it, because it's written in a driver-centric manner (Encl PD means nothing to me). I can read part of the CDB data, but it doesn't tell me much. Scott Long might know. http://digitalfreaks.org/~lavalamp/20081023_server3_screen_dump.png You should try asking the system manufacturer if they know what any of the data means. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
On Thursday 13 November 2008, Unga wrote: --- On Thu, 11/13/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: From: Jeremy Chadwick [EMAIL PROTECTED] Subject: Re: GRUB: Filesystem type unknown (ufs2) To: Unga [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Date: Thursday, November 13, 2008, 7:21 PM On Thu, Nov 13, 2008 at 03:16:40AM -0800, Unga wrote: --- On Thu, 11/13/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: How about asking the GNU GRUB folks if GRUB 0.97 supports UFS2? It seems some old version of GRUB on a old version of FreeBSD has worked: http://lists.freebsd.org/pipermail/freebsd-hackers/2004-May/006944.html Also, GRUB is up to 1.96, and does work with amd64. The port is horribly outdated. I don't mind try GRUB 1.96. The problem is I have never used GRUB2 and I have no idea how to configure it. Is there a good notes/documentation on how to use GRUB2? What I need basically is where to put files (eg. stage1, stage2 and *_stage1_5 of GRUB1 in /boot/grub/.) and a sample configuration file. Anyway meanwhile I'll try to find some documentation. ftp://alpha.gnu.org/gnu/grub/ I got my file from above location. I think these kinds of questions should probably go to the GNU GRUB folks though, don't you think? I don't mean to sound like I'm stepping on your efforts, but the sysutils/grub port has very little to it (meaning, issues/problems of this type should very likely be issues with GRUB itself and not with the port or FreeBSD). Well, I thought FreeBSD guys use GRUB. Its easy to communicate with those who use FreeBSD rather than those who use Linux and discuss mostly on a theoretical basis. I mostly wanted to know does GRUB works for other FreeBSD users. If so, I could investigate what went wrong on mine. Btw, I did not use the port, its straight away compiled from sources. That I mentioned as the first line in my original post. Regards Unga I've used GRUB in the past to boot FreeBSD. The GRUB boot directory was located on the FreeBSD root partition, so it can work. I did use the port though. -- Pieter de Goeje ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
vnconfig virtual nodes - how is that done nowadays in 7.x?
There was a vnconfig way back in FreeBSD that allowed for managing virtual disks or disks as files. What is the means to handle that kind of situation? I have a couple of NTFS and UFS partitions on physical disks which I would like to dd to files and then mount them as virtual nodes or whatever that is called now. -- Christoph Kukulies ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
--- On Thu, 11/13/08, Pieter de Goeje [EMAIL PROTECTED] wrote: I've used GRUB in the past to boot FreeBSD. The GRUB boot directory was located on the FreeBSD root partition, so it can work. I did use the port though. Now the issue is the root partition itself cannot access. Were your partitions ufs2? Which version of GRUB you used? Any possibility to give it a try again? Regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tool to recover fat partition
On Wednesday 12 November 2008, Gonzalo Nemmi wrote: So ... newfs_msdos /dev/insert_typo_in_here .. new filesystem succesfully created ... lost partition on the wrong drive ... Is there a tool to recover the files on said partition in FreeBSD (7 release)? Thanks for you help :) Regards If the destroyed parition is an UFS partition, you could try fsck_ffs'ing it. Hopefully some superblock backups are still intact. Just to be extra safe, copy the entire partition to a file, create an md device from it and fsck the md device. -- Pieter de Goeje ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tool to recover fat partition
On Thursday 13 November 2008, Pieter de Goeje wrote: On Wednesday 12 November 2008, Gonzalo Nemmi wrote: So ... newfs_msdos /dev/insert_typo_in_here .. new filesystem succesfully created ... lost partition on the wrong drive ... Is there a tool to recover the files on said partition in FreeBSD (7 release)? Thanks for you help :) Regards If the destroyed parition is an UFS partition, you could try fsck_ffs'ing it. Hopefully some superblock backups are still intact. Just to be extra safe, copy the entire partition to a file, create an md device from it and fsck the md device. Nevermind, didn't read the subject ;-). On topic, sysutils/fatback seems promising. -- Pieter de Goeje ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.4 - filesystem full
On Wed, 12 Nov 2008, Adrian Penisoara wrote: What kind of applications are you running on the machine ? Are they mmap'ing files on the filesystem in quesiton (which one ?) ? mainly apache, sphinx's search daemon and several perl scripts AFAIR even if you delete a big file the disk space may not be reclaimed if a process still has the file open. but even if you run df -ki in the exact moment of when the filesystem full messages are appearing in the logs, it reports of having 40G free and a lot of free inodes. If you reboot the machine or restart some of the applications, does the issue disappear ? after rebooting during several days the issue doesn't arise, then it repeats again. Alexander Varshavchick, Metrocom Joint Stock Company Phone: (812)718-3322, 718-3115(fax) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dlsym can't use handle returned by dlopen?
On Thu, Nov 13, 2008 at 12:24:02AM -0800, Jeremy Chadwick wrote: On Thu, Nov 13, 2008 at 09:20:59AM +0100, Markus Hoenicka wrote: Quoting Jeremy Chadwick [EMAIL PROTECTED]: When I looked at the resulting symbol names using nm or objdump, certain characters were prepended to them. There's a gcc or ld flag which disables this behaviour. I'll have to dig around to remind myself what it is. Once I read about it, it made perfect sense. Again, if you want me to write some code and provide some output of what I'm talking about, I can do so. I'd greatly appreciate any help here. I feel what I'm doing now is writing ugly hacks to make things work somehow. I'd prefer to do it properly. No problem. I'll try to get something small/simple written up tonight (I'm at work right now) and send it out. As promised: http://www.malkavian.com/~jdc/myprog.tar.gz I couldn't figure out what the gcc flag was that I needed to keep certain characters from getting prepended to the symbol names. I believe the char added was an underscore, but I could be wrong. Either way, the example should help you, I think. (You can change RTLD_LAZY to RTLD_NOW and it still functions as expected) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dlsym can't use handle returned by dlopen?
Quoting Jeremy Chadwick [EMAIL PROTECTED]: As promised: http://www.malkavian.com/~jdc/myprog.tar.gz I couldn't figure out what the gcc flag was that I needed to keep certain characters from getting prepended to the symbol names. I believe the char added was an underscore, but I could be wrong. Either way, the example should help you, I think. (You can change RTLD_LAZY to RTLD_NOW and it still functions as expected) Thanks a lot, I'll have a look at it when I get home tonight. regards, Markus -- Markus Hoenicka [EMAIL PROTECTED] (Spam-protected email: replace the quadrupeds with mhoenicka) http://www.mhoenicka.de ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
The sense data in the screen shot boils down to an ASC/ASCQ pair of 0x35/0x05. Looking this up in the ASC table found at t10.org gives the following: 35h/05h ENCLOSURE SERVICES CHECKSUM ERROR What this basically means is that the disk enclosure that you're using has some sort of an unknown defect or failure. It has nothing to do with the OS. Dell needs to send you a new enclosure, plain and simple. Scott Jeremy Chadwick wrote: On Thu, Nov 13, 2008 at 02:16:58PM +0100, VeeJay wrote: I have asked the system manufacturers (Dell) but they don't provide support for FreeBSD based systems [?] Thats why I have only hope here with FreeBSD List... I've CC'd Scott Long, who is the author of the mfi(4) driver. He should be able to explain what the error messages mean. Scott, check out the URL below. On Thu, Nov 13, 2008 at 1:41 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Thu, Nov 13, 2008 at 01:29:11PM +0100, VeeJay wrote: If it looks healthy, why there are these errors on the screen? Is it controller problem or disk? SCSI normally reports 3 things when it encounters an error (particularly disk errors): Sense Key (SK), Additional Sense Code (ASC), and Additional Sense Code Qualifier (ASCQ). What appears in the below screenshot is a large amount of sense data, but I can't make heads or tails out of it, because it's written in a driver-centric manner (Encl PD means nothing to me). I can read part of the CDB data, but it doesn't tell me much. Scott Long might know. http://digitalfreaks.org/~lavalamp/20081023_server3_screen_dump.png You should try asking the system manufacturer if they know what any of the data means. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vnconfig virtual nodes - how is that done nowadays in 7.x?
On Thu, Nov 13, 2008 at 02:47:27PM +0100, Christoph Kukulies wrote: There was a vnconfig way back in FreeBSD that allowed for managing virtual disks or disks as files. What is the means to handle that kind of situation? mdconfig(8) nowadays. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
--- On Thu, 11/13/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: From: Jeremy Chadwick [EMAIL PROTECTED] Subject: Re: GRUB: Filesystem type unknown (ufs2) To: Unga [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Date: Thursday, November 13, 2008, 7:21 PM On Thu, Nov 13, 2008 at 03:16:40AM -0800, Unga wrote: --- On Thu, 11/13/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: How about asking the GNU GRUB folks if GRUB 0.97 supports UFS2? It seems some old version of GRUB on a old version of FreeBSD has worked: http://lists.freebsd.org/pipermail/freebsd-hackers/2004-May/006944.html Also, GRUB is up to 1.96, and does work with amd64. The port is horribly outdated. I don't mind try GRUB 1.96. The problem is I have never used GRUB2 and I have no idea how to configure it. Is there a good notes/documentation on how to use GRUB2? What I need basically is where to put files (eg. stage1, stage2 and *_stage1_5 of GRUB1 in /boot/grub/.) and a sample configuration file. Anyway meanwhile I'll try to find some documentation. ftp://alpha.gnu.org/gnu/grub/ I got my file from above location. I think these kinds of questions should probably go to the GNU GRUB folks though, don't you think? I don't mean to sound like I'm stepping on your efforts, but the sysutils/grub port has very little to it (meaning, issues/problems of this type should very likely be issues with GRUB itself and not with the port or FreeBSD). Well, I thought FreeBSD guys use GRUB. Its easy to communicate with those who use FreeBSD rather than those who use Linux and discuss mostly on a theoretical basis. I mostly wanted to know does GRUB works for other FreeBSD users. If so, I could investigate what went wrong on mine. Btw, I did not use the port, its straight away compiled from sources. That I mentioned as the first line in my original post. Regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
If it looks healthy, why there are these errors on the screen? Is it controller problem or disk? Regards VJ On Thu, Nov 13, 2008 at 9:49 AM, VeeJay [EMAIL PROTECTED] wrote: Hi Guys I am running RAID 10. Here is the dmesg output: $ dmesg Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-PRERELEASE #0: Fri Aug 29 13:42:13 CEST 2008 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/KERNEL Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5450 @ 3.00GHz (2995.54-MHz K8-class CPU) Origin = GenuineIntel Id = 0x10676 Stepping = 6 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xce3bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,b19 AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF Cores per package: 4 usable memory = 17166688256 (16371 MB) avail memory = 16619601920 (15849 MB) ACPI APIC Table: DELL PE_SC3 FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: DELL PE_SC3 on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci4: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci4 pci5: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge at device 0.0 on pci5 pci6: ACPI PCI bus on pcib3 pcib4: PCI-PCI bridge at device 0.0 on pci6 pci7: PCI bus on pcib4 bce0: Broadcom NetXtreme II BCM5708 1000Base-T (B2) mem 0xf400-0xf5ff irq 16 at device 0.0 on pci7 miibus0: MII bus on bce0 brgphy0: BCM5708C 10/100/1000baseTX PHY PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bce0: Ethernet address: 00:1e:c9:d5:88:f0 bce0: [ITHREAD] bce0: ASIC (0x57081020); Rev (B2); Bus (PCI-X, 64-bit, 133MHz); F/W (0x04000305); Flags( MFW MSI ) pcib5: ACPI PCI-PCI bridge at device 1.0 on pci5 pci8: ACPI PCI bus on pcib5 pcib6: PCI-PCI bridge at device 0.3 on pci4 pci9: PCI bus on pcib6 pcib7: ACPI PCI-PCI bridge at device 3.0 on pci0 pci1: ACPI PCI bus on pcib7 mfi0: Dell PERC 6 port 0xec00-0xecff mem 0xfc68-0xfc6b,0xfc64-0xfc67 irq 16 at device 0.0 on pci1 mfi0: Megaraid SAS driver Ver 2.00 mfi0: 2145 (279883150s/0x0020/info) - Shutdown command received from host mfi0: 2146 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/1f0c/1028) mfi0: 2147 (boot + 3s/0x0020/info) - Firmware version 1.11.52-0396 mfi0: 2148 (boot + 3s/0x0008/info) - Battery Present mfi0: 2149 (boot + 3s/0x0020/info) - Package version 6.0.2-0002 mfi0: 2150 (boot + 21s/0x0004/info) - Enclosure (SES) discovered on PD 20(c None/p0) mfi0: 2151 (boot + 21s/0x0002/info) - Inserted: Encl PD 20 mfi0: 2152 (boot + 21s/0x0002/info) - Inserted: PD 20(c None/p0) Info: enclPd=20, scsiType=d, portMap=09, sasAddr=5001e0f03d0c6f00, mfi0: 2153 (boot + 21s/0x0002/info) - Inserted: PD 00(e0x20/s0) mfi0: 2154 (boot + 21s/0x0002/info) - Inserted: PD 00(e0x20/s0) Info: enclPd=20, scsiType=0, portMap=00, sasAddr=5000cca00904b705, mfi0: 2155 (boot + 21s/0x0002/info) - Inserted: PD 01(e0x20/s1) mfi0: 2156 (boot + 21s/0x0002/info) - Inserted: PD 01(e0x20/s1) Info: enclPd=20, scsiType=0, portMap=01, sasAddr=5000cca009024231, mfi0: 2157 (boot + 21s/0x0002/info) - Inserted: PD 02(e0x20/s2) mfi0: 2158 (boot + 21s/0x0002/info) - Inserted: PD 02(e0x20/s2) Info: enclPd=20, scsiType=0, portMap=02, sasAddr=5000cca00904d92d, mfi0: 2159 (boot + 21s/0x0002/info) - Inserted: PD 03(e0x20/s3) mfi0: 2160 (boot + 21s/0x0002/info) - Inserted: PD 03(e0x20/s3) Info: enclPd=20, scsiType=0, portMap=03, sasAddr=5000cca009048865, mfi0: 2161 (boot + 21s/0x0002/info) - Inserted: PD 04(e0x20/s4) mfi0: 2162 (boot + 21s/0x0002/info) - Inserted: PD 04(e0x20/s4) Info: enclPd=20, scsiType=0, portMap=04, sasAddr=5000cca009048d2d, mfi0: 2163 (boot + 21s/0x0002/info) - Inserted: PD 05(e0x20/s5) mfi0: 2164 (boot + 21s/0x0002/info) - Inserted: PD 05(e0x20/s5) Info: enclPd=20, scsiType=0, portMap=05, sasAddr=5000cca009048f31, mfi0: 2165 (279879506s/0x0020/info) - Time established as
GRUB: Filesystem type unknown (ufs2)
Hi all I have compiled and installed grub-0.97.tar.gz on FreeBSD 7.0 (i386). It shows the grub cannot recognize ufs2 file systems. grub root (hd1,0, Possible partitions are: Partition num: 0, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'b', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'd', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'e', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'f', Filesystem type unknown, partition type 0xa5 All stage1, stage2 and *_stage1_5 are in /boot/grub/. The fstype used for bsdlabel for b is swap and for others its 4.2BSD. Files systems were created as follows: newfs -U /dev/ad2s1a newfs /dev/ad2s1d newfs -U /dev/ad2s1e newfs -U /dev/ad2s1f Do others experience this issue? Do I need to patch the Grub to recognize ufs2 file systems? Your reply is very much appreciated. Kind regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.4 - filesystem full
On Thu, Nov 13, 2008 at 02:05:28PM +0300, Varshavchick Alexander wrote: Booting into single-user via serial console, KVM, KVM-over-IP, or iLO/LOM (if HP/Compaq) is sufficient. If you have servers which are remote and you lack any of these features, I'm both surprised and not sure what to tell you. You'll encounter this problem with any OS, not just FreeBSD. I'm looking for something similar to /forcefsck file on the linux systems. Ideally this should be handled either nextboot(8), via a special flag passed to boot(8). However, I see no such capability in the man pages, so you might be out of luck. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
Thanks guys... I have forwarded the comments from Scott to the Dell and hope for the best Thank you again. VJ On Thu, Nov 13, 2008 at 2:51 PM, Scott Long [EMAIL PROTECTED] wrote: The sense data in the screen shot boils down to an ASC/ASCQ pair of 0x35/0x05. Looking this up in the ASC table found at t10.org gives the following: 35h/05h ENCLOSURE SERVICES CHECKSUM ERROR What this basically means is that the disk enclosure that you're using has some sort of an unknown defect or failure. It has nothing to do with the OS. Dell needs to send you a new enclosure, plain and simple. Scott Jeremy Chadwick wrote: On Thu, Nov 13, 2008 at 02:16:58PM +0100, VeeJay wrote: I have asked the system manufacturers (Dell) but they don't provide support for FreeBSD based systems [?] Thats why I have only hope here with FreeBSD List... I've CC'd Scott Long, who is the author of the mfi(4) driver. He should be able to explain what the error messages mean. Scott, check out the URL below. On Thu, Nov 13, 2008 at 1:41 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Thu, Nov 13, 2008 at 01:29:11PM +0100, VeeJay wrote: If it looks healthy, why there are these errors on the screen? Is it controller problem or disk? SCSI normally reports 3 things when it encounters an error (particularly disk errors): Sense Key (SK), Additional Sense Code (ASC), and Additional Sense Code Qualifier (ASCQ). What appears in the below screenshot is a large amount of sense data, but I can't make heads or tails out of it, because it's written in a driver-centric manner (Encl PD means nothing to me). I can read part of the CDB data, but it doesn't tell me much. Scott Long might know. http://digitalfreaks.org/~lavalamp/20081023_server3_screen_dump.png You should try asking the system manufacturer if they know what any of the data means. -- Thanks! BR / vj ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot splash screen, was Disabling boot messages
Daniel Bye wrote: On Wed, Nov 12, 2008 at 06:40:29PM +0800, Fbsd1 wrote: Running a release 7.0 Xorg / Gdm / Xfce Desktop world. Would like to go from powering on the PC directly to the Gdm login screen. Don't want the users seeing all those boot message roll by. Can this be done? It can - see the FAQ: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/x.html#INSTALL-SPLASH Dan Thank you for the pointer to the boot splash screen. That was exactly what is was looking for. The documentation on activating the boot splash screen is not up to date. It was written for Freebsd 3.1 and seems to have bugs and undocumented functions. The FAQ says; FreeBSD have a feature to allow the display of “splash” screens during the boot messages. The splash screens currently must be a 256 color bitmap (*.BMP) or ZSoft PCX (*.PCX) file. In addition, they must have a resolution of 320x200 or less to work on standard VGA adapters. If you compile VESA support into your kernel, then you can use larger bitmaps up to 1024x768. The actual VESA support can either be compiled directly into the kernel with the VESA kernel config option or by loading the VESA kld module during bootup. To use a splash screen, you need to modify the startup files that control the boot process for FreeBSD. You need to create a /boot/loader.rc file that contains the following lines: include /boot/loader.4th start and a /boot/loader.conf that contains the following: splash_bmp_load=YES bitmap_load=YES This assumes you are using /boot/splash.bmp for your splash screen. If you would rather use a PCX file, copy it to /boot/splash.pcx, create a /boot/loader.rc as instructed above, and create a /boot/loader.conf that contains: splash_pcx_load=YES bitmap_load=YES bitmap_name=/boot/splash.pcx *** end of faq First the /boot/loader.rc already contains these statements include /boot/loader.4th start So nothing needs to be done to it. Secondly. /boot/loader.conf statements splash_bmp_load=YES bitmap_load=YES are doing the same thing. you only need one or the other, not both. Thirdly: If you move a 320x200 resolution image named the default name of splash.bmp to /boot and reboot the system you will get this error, module_ register_init: mod_load (splash_bmp) error 2 But if you rename that splash.bmp file to something like splash320x200.bmp and make your loader.conf look like this bitmap_load=YES bitmap_name=/boot/splash320x200.bmp you no longer get the module_ register_init: error 2 message at boot time and your splash image will show up centered on a white background screen. You still see the boot messages through boot options menu and the timed wait count down. If you want a full screen splash image, the easiest way is to load vesa in the loader.conf vesa_load=YES bitmap_load=YES bitmap_name=/boot/splash640x400.bmp In both these cases you still see the boot massages through boot options menu and the timed wait count down. There are 2 another loader.conf options you may be interested in. Loader_logo=beastie This will replace the default FREE BDS words next to the boot menu with the beastie logo like in releases in the past had. beastie_disable=YES Will stop the boot options menu from being displayed. You will still get the timed wait count down. While the splash screen is displayed during the booting process you can hit any keyboard key to return to the boot message display. Now for the undocumented behavior. First your boot splash screen becomes the system default screen saver. Secondly this new default screen saver cycles through steps of changing intensity of the image, from bright intensity to a very dark intensity. Adding a saver= option to /etc/rc.conf will disable the boot splash screen as the default system screen saver and the saver= selection will be used. This post is for the archives so others can benefit from finding this post in a search of questions archives. Would also like to find out to get this info used to update the FAQ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
I have asked the system manufacturers (Dell) but they don't provide support for FreeBSD based systems [?] Thats why I have only hope here with FreeBSD List... On Thu, Nov 13, 2008 at 1:41 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Thu, Nov 13, 2008 at 01:29:11PM +0100, VeeJay wrote: If it looks healthy, why there are these errors on the screen? Is it controller problem or disk? SCSI normally reports 3 things when it encounters an error (particularly disk errors): Sense Key (SK), Additional Sense Code (ASC), and Additional Sense Code Qualifier (ASCQ). What appears in the below screenshot is a large amount of sense data, but I can't make heads or tails out of it, because it's written in a driver-centric manner (Encl PD means nothing to me). I can read part of the CDB data, but it doesn't tell me much. Scott Long might know. http://digitalfreaks.org/~lavalamp/20081023_server3_screen_dump.png You should try asking the system manufacturer if they know what any of the data means. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | -- Thanks! BR / vj ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
port upgrade problem: libncurses.so.5.6 not found
Hi, just cvsup my port tree and upgrade a few of them by portmaster, but somehow there is this error that blocks a lot of upgrades: shared object libncurses.so.5.6 not found, required by xgettext/msgmerge/msgfmt... if there something i missed these days? if was find a couple days ago when I did my last upgrade. Any idea is appreciated!! thansk!! TFC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: port upgrade problem: libncurses.so.5.6 not found
On Thursday 13 November 2008 15:41:13 Tsu-Fan Cheng wrote: Hi, just cvsup my port tree and upgrade a few of them by portmaster, but somehow there is this error that blocks a lot of upgrades: shared object libncurses.so.5.6 not found, required by xgettext/msgmerge/msgfmt... FreeBSD only uses 1 library version number (it would be libncurses.so.5 OR libncurses.so.6), so can you provide the output of: ldd `which xgettext` -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Re: port upgrade problem: libncurses.so.5.6 not found
learned a new thing, here is the output: /usr/local/bin/xgettext: libgettextsrc-0.17.so = /usr/local/lib/libgettextsrc-0.17.so (0x280a9000) libgettextlib-0.17.so = /usr/local/lib/libgettextlib-0.17.so (0x280de000) libcroco-0.6.so.3 = /usr/local/lib/libcroco-0.6.so.3 (0x281bb000) libxml2.so.5 = /usr/local/lib/libxml2.so.5 (0x281ef000) libz.so.4 = /lib/libz.so.4 (0x2831b000) libm.so.5 = /lib/libm.so.5 (0x2832d000) libglib-2.0.so.0 = /usr/local/lib/libglib-2.0.so.0 (0x28342000) libicui18n.so.38 = /usr/local/lib/libicui18n.so.38 (0x283f1000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x28559000) libpcre.so.0 = /usr/local/lib/libpcre.so.0 (0x28562000) libncurses.so.5.6 = not found (0x0) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libbsdxml.so.3 = /lib/libbsdxml.so.3 (0x28685000) libc.so.7 = /lib/libc.so.7 (0x286a3000) libncurses.so.5.6 = not found (0x0) libicuuc.so.38 = /usr/local/lib/libicuuc.so.38 (0x287a4000) libicudata.so.38 = /usr/local/lib/libicudata.so.38 (0x288b9000) libstdc++.so.5 = /usr/lib/libstdc++.so.5 (0x2939) libm.so.4 = /lib/libm.so.4 (0x2945b000) it's weird that it still shows libncurses.so.5.6, any thoughts?? thanks!! TFC On Nov 13, 2008 10:37am, Mel [EMAIL PROTECTED] wrote: On Thursday 13 November 2008 15:41:13 Tsu-Fan Cheng wrote: Hi, just cvsup my port tree and upgrade a few of them by portmaster, but somehow there is this error that blocks a lot of upgrades: shared object libncurses.so.5.6 not found, required by xgettext/msgmerge/msgfmt... FreeBSD only uses 1 library version number (it would be libncurses.so.5 OR libncurses.so.6), so can you provide the output of: ldd `which xgettext` -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Re: port upgrade problem: libncurses.so.5.6 not found
On Thu, Nov 13, 2008 at 08:12:49AM -0800, [EMAIL PROTECTED] wrote: learned a new thing, here is the output: /usr/local/bin/xgettext: libgettextsrc-0.17.so = /usr/local/lib/libgettextsrc-0.17.so (0x280a9000) libgettextlib-0.17.so = /usr/local/lib/libgettextlib-0.17.so (0x280de000) libcroco-0.6.so.3 = /usr/local/lib/libcroco-0.6.so.3 (0x281bb000) libxml2.so.5 = /usr/local/lib/libxml2.so.5 (0x281ef000) libz.so.4 = /lib/libz.so.4 (0x2831b000) libm.so.5 = /lib/libm.so.5 (0x2832d000) libglib-2.0.so.0 = /usr/local/lib/libglib-2.0.so.0 (0x28342000) libicui18n.so.38 = /usr/local/lib/libicui18n.so.38 (0x283f1000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x28559000) libpcre.so.0 = /usr/local/lib/libpcre.so.0 (0x28562000) libncurses.so.5.6 = not found (0x0) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libbsdxml.so.3 = /lib/libbsdxml.so.3 (0x28685000) libc.so.7 = /lib/libc.so.7 (0x286a3000) libncurses.so.5.6 = not found (0x0) libicuuc.so.38 = /usr/local/lib/libicuuc.so.38 (0x287a4000) libicudata.so.38 = /usr/local/lib/libicudata.so.38 (0x288b9000) libstdc++.so.5 = /usr/lib/libstdc++.so.5 (0x2939) libm.so.4 = /lib/libm.so.4 (0x2945b000) it's weird that it still shows libncurses.so.5.6, any thoughts?? thanks!! It's not weird at all. When a binary is linked to a shared library (during the linking phase), the library filename (libXXX.so.X.X) is stored in the binary, not libXXX.so. I'm not sure how/why a rebuild xgettext is linking to what appears to be a very old version of libncurses. libncurses.so.5.6 would be for FreeBSD 5.x, I believe; my FreeBSD 6.x machines have libncurses.so.6, and my FreeBSD 7.x + CURRENT machines have libncurses.so.7. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: port upgrade problem: libncurses.so.5.6 not found
On Thursday 13 November 2008 17:47:34 Jeremy Chadwick wrote: On Thu, Nov 13, 2008 at 08:12:49AM -0800, [EMAIL PROTECTED] wrote: learned a new thing, here is the output: /usr/local/bin/xgettext: libgettextsrc-0.17.so = /usr/local/lib/libgettextsrc-0.17.so (0x280a9000) libgettextlib-0.17.so = /usr/local/lib/libgettextlib-0.17.so (0x280de000) libcroco-0.6.so.3 = /usr/local/lib/libcroco-0.6.so.3 (0x281bb000) libxml2.so.5 = /usr/local/lib/libxml2.so.5 (0x281ef000) libz.so.4 = /lib/libz.so.4 (0x2831b000) libm.so.5 = /lib/libm.so.5 (0x2832d000) libglib-2.0.so.0 = /usr/local/lib/libglib-2.0.so.0 (0x28342000) libicui18n.so.38 = /usr/local/lib/libicui18n.so.38 (0x283f1000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x28559000) libpcre.so.0 = /usr/local/lib/libpcre.so.0 (0x28562000) libncurses.so.5.6 = not found (0x0) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libbsdxml.so.3 = /lib/libbsdxml.so.3 (0x28685000) libc.so.7 = /lib/libc.so.7 (0x286a3000) libncurses.so.5.6 = not found (0x0) libicuuc.so.38 = /usr/local/lib/libicuuc.so.38 (0x287a4000) libicudata.so.38 = /usr/local/lib/libicudata.so.38 (0x288b9000) libstdc++.so.5 = /usr/lib/libstdc++.so.5 (0x2939) libm.so.4 = /lib/libm.so.4 (0x2945b000) it's weird that it still shows libncurses.so.5.6, any thoughts?? thanks!! It's not weird at all. When a binary is linked to a shared library (during the linking phase), the library filename (libXXX.so.X.X) is stored in the binary, not libXXX.so. But the requirement is, that the library exists at link time. I'm not sure how/why a rebuild xgettext is linking to what appears to be a very old version of libncurses. libncurses.so.5.6 would be for FreeBSD 5.x, I believe; my FreeBSD 6.x machines have libncurses.so.6, and my FreeBSD 7.x + CURRENT machines have libncurses.so.7. It's libncurses.so.5 for FreeBSD 5: # grep ncurses /usr/ports/misc/compat5x/pkg-plist lib/compat/libncurses.so.5 The .5.6 is what's bugging me. Aparently, there was a library like this at link time, that does not exist anymore. Can you provide output of: ldd -a `which xgettext` so we know which library pulls in libncurses.so.5.6. I doubt it's the binary itself. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Re: port upgrade problem: libncurses.so.5.6 not found
as I look into my system, under /usr/local/lib, I found out that I not only don't have libncurses.so.5.6, but instead I have libncurses.so.5.7. And this file was created this morning (Nov 13, 09:03) while I was trying to upgrade my ports. Odd I am running freebsd 7.0, as my uname tells me.. TFC On Thu, Nov 13, 2008 at 11:47 AM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Thu, Nov 13, 2008 at 08:12:49AM -0800, [EMAIL PROTECTED] wrote: learned a new thing, here is the output: /usr/local/bin/xgettext: libgettextsrc-0.17.so = /usr/local/lib/libgettextsrc-0.17.so (0x280a9000) libgettextlib-0.17.so = /usr/local/lib/libgettextlib-0.17.so (0x280de000) libcroco-0.6.so.3 = /usr/local/lib/libcroco-0.6.so.3 (0x281bb000) libxml2.so.5 = /usr/local/lib/libxml2.so.5 (0x281ef000) libz.so.4 = /lib/libz.so.4 (0x2831b000) libm.so.5 = /lib/libm.so.5 (0x2832d000) libglib-2.0.so.0 = /usr/local/lib/libglib-2.0.so.0 (0x28342000) libicui18n.so.38 = /usr/local/lib/libicui18n.so.38 (0x283f1000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x28559000) libpcre.so.0 = /usr/local/lib/libpcre.so.0 (0x28562000) libncurses.so.5.6 = not found (0x0) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libbsdxml.so.3 = /lib/libbsdxml.so.3 (0x28685000) libc.so.7 = /lib/libc.so.7 (0x286a3000) libncurses.so.5.6 = not found (0x0) libicuuc.so.38 = /usr/local/lib/libicuuc.so.38 (0x287a4000) libicudata.so.38 = /usr/local/lib/libicudata.so.38 (0x288b9000) libstdc++.so.5 = /usr/lib/libstdc++.so.5 (0x2939) libm.so.4 = /lib/libm.so.4 (0x2945b000) it's weird that it still shows libncurses.so.5.6, any thoughts?? thanks!! It's not weird at all. When a binary is linked to a shared library (during the linking phase), the library filename (libXXX.so.X.X) is stored in the binary, not libXXX.so. I'm not sure how/why a rebuild xgettext is linking to what appears to be a very old version of libncurses. libncurses.so.5.6 would be for FreeBSD 5.x, I believe; my FreeBSD 6.x machines have libncurses.so.6, and my FreeBSD 7.x + CURRENT machines have libncurses.so.7. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Re: port upgrade problem: libncurses.so.5.6 not found
On Thu, Nov 13, 2008 at 12:03:14PM -0500, Tsu-Fan Cheng wrote: as I look into my system, under /usr/local/lib, I found out that I not only don't have libncurses.so.5.6, but instead I have libncurses.so.5.7. And this file was created this morning (Nov 13, 09:03) while I was trying to upgrade my ports. Odd I am running freebsd 7.0, as my uname tells me.. Mel's question applies as well (and is something that I've wondered too). Now I'm wondering this as well: How/why do you have libncurses* in /usr/local/lib? FreeBSD 7.0 comes with ncurses (see /usr/lib/libncurses.so.7). You must have some port or piece of software on your machine which is requiring an old (compat5x) version of libncurses, or you have a machine that has been upgraded from FreeBSD 5.x to 6.x to 7.x. I really don't know what to make of this. On Thu, Nov 13, 2008 at 11:47 AM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Thu, Nov 13, 2008 at 08:12:49AM -0800, [EMAIL PROTECTED] wrote: learned a new thing, here is the output: /usr/local/bin/xgettext: libgettextsrc-0.17.so = /usr/local/lib/libgettextsrc-0.17.so (0x280a9000) libgettextlib-0.17.so = /usr/local/lib/libgettextlib-0.17.so (0x280de000) libcroco-0.6.so.3 = /usr/local/lib/libcroco-0.6.so.3 (0x281bb000) libxml2.so.5 = /usr/local/lib/libxml2.so.5 (0x281ef000) libz.so.4 = /lib/libz.so.4 (0x2831b000) libm.so.5 = /lib/libm.so.5 (0x2832d000) libglib-2.0.so.0 = /usr/local/lib/libglib-2.0.so.0 (0x28342000) libicui18n.so.38 = /usr/local/lib/libicui18n.so.38 (0x283f1000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x28559000) libpcre.so.0 = /usr/local/lib/libpcre.so.0 (0x28562000) libncurses.so.5.6 = not found (0x0) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libbsdxml.so.3 = /lib/libbsdxml.so.3 (0x28685000) libc.so.7 = /lib/libc.so.7 (0x286a3000) libncurses.so.5.6 = not found (0x0) libicuuc.so.38 = /usr/local/lib/libicuuc.so.38 (0x287a4000) libicudata.so.38 = /usr/local/lib/libicudata.so.38 (0x288b9000) libstdc++.so.5 = /usr/lib/libstdc++.so.5 (0x2939) libm.so.4 = /lib/libm.so.4 (0x2945b000) it's weird that it still shows libncurses.so.5.6, any thoughts?? thanks!! It's not weird at all. When a binary is linked to a shared library (during the linking phase), the library filename (libXXX.so.X.X) is stored in the binary, not libXXX.so. I'm not sure how/why a rebuild xgettext is linking to what appears to be a very old version of libncurses. libncurses.so.5.6 would be for FreeBSD 5.x, I believe; my FreeBSD 6.x machines have libncurses.so.6, and my FreeBSD 7.x + CURRENT machines have libncurses.so.7. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: port upgrade problem: libncurses.so.5.6 not found
Mel, thank you for your help, here is the output: /usr/local/bin/xgettext: libgettextsrc-0.17.so = /usr/local/lib/libgettextsrc-0.17.so (0x280a9000) libgettextlib-0.17.so = /usr/local/lib/libgettextlib-0.17.so (0x280de000) libcroco-0.6.so.3 = /usr/local/lib/libcroco-0.6.so.3 (0x281bb000) libxml2.so.5 = /usr/local/lib/libxml2.so.5 (0x281ef000) libz.so.4 = /lib/libz.so.4 (0x2831b000) libm.so.5 = /lib/libm.so.5 (0x2832d000) libglib-2.0.so.0 = /usr/local/lib/libglib-2.0.so.0 (0x28342000) libicui18n.so.38 = /usr/local/lib/libicui18n.so.38 (0x283f1000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x28559000) libpcre.so.0 = /usr/local/lib/libpcre.so.0 (0x28562000) libncurses.so.5.6 = not found (0x0) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libbsdxml.so.3 = /lib/libbsdxml.so.3 (0x28685000) libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libgettextsrc-0.17.so: libgettextlib-0.17.so = /usr/local/lib/libgettextlib-0.17.so (0x280de000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x28559000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libgettextlib-0.17.so: libcroco-0.6.so.3 = /usr/local/lib/libcroco-0.6.so.3 (0x281bb000) libxml2.so.5 = /usr/local/lib/libxml2.so.5 (0x281ef000) libz.so.4 = /lib/libz.so.4 (0x2831b000) libm.so.5 = /lib/libm.so.5 (0x2832d000) libglib-2.0.so.0 = /usr/local/lib/libglib-2.0.so.0 (0x28342000) libicui18n.so.38 = /usr/local/lib/libicui18n.so.38 (0x283f1000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x28559000) libpcre.so.0 = /usr/local/lib/libpcre.so.0 (0x28562000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libncurses.so.5.6 = not found (0x0) libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libcroco-0.6.so.3: libglib-2.0.so.0 = /usr/local/lib/libglib-2.0.so.0 (0x28342000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libxml2.so.5 = /usr/local/lib/libxml2.so.5 (0x281ef000) libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libxml2.so.5: libz.so.4 = /lib/libz.so.4 (0x2831b000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libm.so.5 = /lib/libm.so.5 (0x2832d000) libc.so.7 = /lib/libc.so.7 (0x286a3000) /lib/libz.so.4: libc.so.7 = /lib/libc.so.7 (0x286a3000) /lib/libm.so.5: libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libglib-2.0.so.0: libicui18n.so.38 = /usr/local/lib/libicui18n.so.38 (0x283f1000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x28559000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libpcre.so.0 = /usr/local/lib/libpcre.so.0 (0x28562000) libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libicui18n.so.38: libicuuc.so.38 = /usr/local/lib/libicuuc.so.38 (0x287a4000) libicudata.so.38 = /usr/local/lib/libicudata.so.38 (0x288b9000) libstdc++.so.5 = /usr/lib/libstdc++.so.5 (0x2939) libm.so.4 = /lib/libm.so.4 (0x2945b000) /usr/local/lib/libintl.so.8: libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libpcre.so.0: libc.so.7 = /lib/libc.so.7 (0x286a3000) /lib/libbsdxml.so.3: libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libicuuc.so.38: libicudata.so.38 = /usr/local/lib/libicudata.so.38 (0x288b9000) libstdc++.so.5 = /usr/lib/libstdc++.so.5 (0x2939) libm.so.4 = /lib/libm.so.4 (0x2945b000) /usr/lib/libstdc++.so.5: libm.so.4 = /lib/libm.so.4 (0x2945b000) thanks!! TFC On Thu, Nov 13, 2008 at 12:02 PM, Mel [EMAIL PROTECTED] wrote: On Thursday 13 November 2008 17:47:34 Jeremy Chadwick wrote: On Thu, Nov 13, 2008 at 08:12:49AM -0800, [EMAIL PROTECTED] wrote: learned a new thing, here is the output: /usr/local/bin/xgettext: libgettextsrc-0.17.so = /usr/local/lib/libgettextsrc-0.17.so (0x280a9000) libgettextlib-0.17.so = /usr/local/lib/libgettextlib-0.17.so (0x280de000) libcroco-0.6.so.3 = /usr/local/lib/libcroco-0.6.so.3 (0x281bb000) libxml2.so.5 = /usr/local/lib/libxml2.so.5 (0x281ef000) libz.so.4 = /lib/libz.so.4 (0x2831b000) libm.so.5 = /lib/libm.so.5 (0x2832d000) libglib-2.0.so.0 = /usr/local/lib/libglib-2.0.so.0 (0x28342000) libicui18n.so.38 = /usr/local/lib/libicui18n.so.38 (0x283f1000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x28559000) libpcre.so.0 = /usr/local/lib/libpcre.so.0 (0x28562000) libncurses.so.5.6 = not found (0x0) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libbsdxml.so.3 = /lib/libbsdxml.so.3 (0x28685000) libc.so.7 = /lib/libc.so.7 (0x286a3000) libncurses.so.5.6 = not found (0x0) libicuuc.so.38 = /usr/local/lib/libicuuc.so.38
Re: Re: port upgrade problem: libncurses.so.5.6 not found
yes, I found libncurses.so under /usr/lib, which is actual linked to libncurses.so.7 under /lib. And I also have libncurses.so.6 too. I did upgrade my system from 5 to 6 to 7. I didn't do a clean install, since there is so many to back up. TFC On Thu, Nov 13, 2008 at 12:09 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Thu, Nov 13, 2008 at 12:03:14PM -0500, Tsu-Fan Cheng wrote: as I look into my system, under /usr/local/lib, I found out that I not only don't have libncurses.so.5.6, but instead I have libncurses.so.5.7. And this file was created this morning (Nov 13, 09:03) while I was trying to upgrade my ports. Odd I am running freebsd 7.0, as my uname tells me.. Mel's question applies as well (and is something that I've wondered too). Now I'm wondering this as well: How/why do you have libncurses* in /usr/local/lib? FreeBSD 7.0 comes with ncurses (see /usr/lib/libncurses.so.7). You must have some port or piece of software on your machine which is requiring an old (compat5x) version of libncurses, or you have a machine that has been upgraded from FreeBSD 5.x to 6.x to 7.x. I really don't know what to make of this. On Thu, Nov 13, 2008 at 11:47 AM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Thu, Nov 13, 2008 at 08:12:49AM -0800, [EMAIL PROTECTED] wrote: learned a new thing, here is the output: /usr/local/bin/xgettext: libgettextsrc-0.17.so = /usr/local/lib/libgettextsrc-0.17.so (0x280a9000) libgettextlib-0.17.so = /usr/local/lib/libgettextlib-0.17.so (0x280de000) libcroco-0.6.so.3 = /usr/local/lib/libcroco-0.6.so.3 (0x281bb000) libxml2.so.5 = /usr/local/lib/libxml2.so.5 (0x281ef000) libz.so.4 = /lib/libz.so.4 (0x2831b000) libm.so.5 = /lib/libm.so.5 (0x2832d000) libglib-2.0.so.0 = /usr/local/lib/libglib-2.0.so.0 (0x28342000) libicui18n.so.38 = /usr/local/lib/libicui18n.so.38 (0x283f1000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x28559000) libpcre.so.0 = /usr/local/lib/libpcre.so.0 (0x28562000) libncurses.so.5.6 = not found (0x0) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libbsdxml.so.3 = /lib/libbsdxml.so.3 (0x28685000) libc.so.7 = /lib/libc.so.7 (0x286a3000) libncurses.so.5.6 = not found (0x0) libicuuc.so.38 = /usr/local/lib/libicuuc.so.38 (0x287a4000) libicudata.so.38 = /usr/local/lib/libicudata.so.38 (0x288b9000) libstdc++.so.5 = /usr/lib/libstdc++.so.5 (0x2939) libm.so.4 = /lib/libm.so.4 (0x2945b000) it's weird that it still shows libncurses.so.5.6, any thoughts?? thanks!! It's not weird at all. When a binary is linked to a shared library (during the linking phase), the library filename (libXXX.so.X.X) is stored in the binary, not libXXX.so. I'm not sure how/why a rebuild xgettext is linking to what appears to be a very old version of libncurses. libncurses.so.5.6 would be for FreeBSD 5.x, I believe; my FreeBSD 6.x machines have libncurses.so.6, and my FreeBSD 7.x + CURRENT machines have libncurses.so.7. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
(no subject)
Good Day! I have The Sun Fire T1000 machine! I want to install Freebsd7.0 on it I am reading the paper about it on http://www.ee.freebsd.org/fr/relnotes/CURRENT/installation/sparc64/index.htmlbut i dont find any loader-nfs.gz or loader-tftp.gz inftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/loader-tftp.gzftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/loader-nfs.gzits emptyPlease to help in this problemSincerelyDmitri Boltenkov Rostov on The Don Russia ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: port upgrade problem: libncurses.so.5.6 not found
On Thursday 13 November 2008 18:17:02 Tsu-Fan Cheng wrote: Mel, thank you for your help, here is the output: /usr/local/bin/xgettext: libgettextsrc-0.17.so = /usr/local/lib/libgettextsrc-0.17.so (0x280a9000) libgettextlib-0.17.so = /usr/local/lib/libgettextlib-0.17.so (0x280de000) libcroco-0.6.so.3 = /usr/local/lib/libcroco-0.6.so.3 (0x281bb000) libxml2.so.5 = /usr/local/lib/libxml2.so.5 (0x281ef000) libz.so.4 = /lib/libz.so.4 (0x2831b000) libm.so.5 = /lib/libm.so.5 (0x2832d000) libglib-2.0.so.0 = /usr/local/lib/libglib-2.0.so.0 (0x28342000) libicui18n.so.38 = /usr/local/lib/libicui18n.so.38 (0x283f1000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x28559000) libpcre.so.0 = /usr/local/lib/libpcre.so.0 (0x28562000) libncurses.so.5.6 = not found (0x0) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libbsdxml.so.3 = /lib/libbsdxml.so.3 (0x28685000) libc.so.7 = /lib/libc.so.7 (0x286a3000) FreeBSD 7 /usr/local/lib/libgettextsrc-0.17.so: libgettextlib-0.17.so = /usr/local/lib/libgettextlib-0.17.so (0x280de000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x28559000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libgettextlib-0.17.so: libcroco-0.6.so.3 = /usr/local/lib/libcroco-0.6.so.3 (0x281bb000) libxml2.so.5 = /usr/local/lib/libxml2.so.5 (0x281ef000) libz.so.4 = /lib/libz.so.4 (0x2831b000) libm.so.5 = /lib/libm.so.5 (0x2832d000) Also FreeBSD 7 libglib-2.0.so.0 = /usr/local/lib/libglib-2.0.so.0 (0x28342000) libicui18n.so.38 = /usr/local/lib/libicui18n.so.38 (0x283f1000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x28559000) libpcre.so.0 = /usr/local/lib/libpcre.so.0 (0x28562000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libncurses.so.5.6 = not found (0x0) libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libcroco-0.6.so.3: libglib-2.0.so.0 = /usr/local/lib/libglib-2.0.so.0 (0x28342000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libxml2.so.5 = /usr/local/lib/libxml2.so.5 (0x281ef000) libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libxml2.so.5: libz.so.4 = /lib/libz.so.4 (0x2831b000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libm.so.5 = /lib/libm.so.5 (0x2832d000) libc.so.7 = /lib/libc.so.7 (0x286a3000) /lib/libz.so.4: libc.so.7 = /lib/libc.so.7 (0x286a3000) /lib/libm.so.5: libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libglib-2.0.so.0: libicui18n.so.38 = /usr/local/lib/libicui18n.so.38 (0x283f1000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x28559000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libpcre.so.0 = /usr/local/lib/libpcre.so.0 (0x28562000) libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libicui18n.so.38: libicuuc.so.38 = /usr/local/lib/libicuuc.so.38 (0x287a4000) libicudata.so.38 = /usr/local/lib/libicudata.so.38 (0x288b9000) libstdc++.so.5 = /usr/lib/libstdc++.so.5 (0x2939) libm.so.4 = /lib/libm.so.4 (0x2945b000) FreeBSD 6 /usr/local/lib/libintl.so.8: libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libpcre.so.0: libc.so.7 = /lib/libc.so.7 (0x286a3000) /lib/libbsdxml.so.3: libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libicuuc.so.38: libicudata.so.38 = /usr/local/lib/libicudata.so.38 (0x288b9000) libstdc++.so.5 = /usr/lib/libstdc++.so.5 (0x2939) FreeBSD 6 libm.so.4 = /lib/libm.so.4 (0x2945b000) /usr/lib/libstdc++.so.5: libm.so.4 = /lib/libm.so.4 (0x2945b000) Your system has stale libraries from the updates and linking is messy. It does not adequately explain the .5.6 library version numbers, but your system is in need of cleaning. Specifically, you forgot to do 'make delete-old-libs' when you upgraded from 6 to 7 (and maybe from 5 to 6 as well,tho there's no evidence of that in this mail). The best course of action is to go into /usr/src and type: # make delete-old # make delete-old-libs Delete everything that the program offers you to delete. Then drop to single user mode, so that no services are running and recompile *all* ports, using portupgrade -fa. you may need to do /etc/rc.d/netif start, so you can download stuff. I'm quite confident this will fix your problems, even tho it gives no explanation for this rogue ncurses library. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail
Openssl port upgrade (FreeBSD 6.2)
Hi All, I ran the openssl updgrade (to OpenSSL 0.9.8d), but it seems the original openssl libs are still being used for SSH session creation and other system crypto functionality. What are the final steps needed to allow all user space programs to use the upgraded OpenSSL? Is there a good guide for this kind of upgrade somewhere? Best Regards, Brendan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
immediate reboot switching window (alt-tab) to google earth
I figured I'd make my pain public, but I doubt we're ever going to find the cause, because there's no crashdump (and yes, unplugging a mounted usb stick causes a real panic and dump so it is configured correctly) - immediate freeze for 60 seconds, then skipped the panic went straight to the reboot. Anyway, if there are other reports, here's mine. I'd like to blame X, since I have yet to observe an X that really felt stable to me, but I suspect the culprit is more likely linux-base-fc4...shame. I suppose I shouldn't be surprised that running linux programs makes BSD as unstable as linux. I just wish there was some foolproof way to protect the OS from apps killing it. But, who really cares, it's just my desktop, right? I don't run this crap on my server. Steve google-earth-4.3.7284.3916_2 Explore, Search and Discover linux_base-fc-4_13 Base set of packages needed in Linux mode (for i386/amd64) linux-xorg-libs-6.8.2_5 Xorg libraries, linux binaries linux-glib2-2.6.6_1 Version 2.X Linux/i386 binary port of GLib xorg-7.3_2 X.Org complete distribution metaport xorg-drivers-7.3_3 X.org drivers meta-port xorg-libraries-7.3_2 X.org libraries meta-port xorg-server-1.4.2,1 X.Org X server and related programs FreeBSD 7.1-PRERELEASE #1: Mon Sep 29 21:12:11 MST 2008 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: zfs on disk with ufs
On Thu, 13 Nov 2008, Nicolas de Bari Embriz Garcia Rojas wrote: Hi all, I have 2 disk using raid 1 (hardware) ~ 250gb with default freebsd partition schema, I would like to resize /usr partition and to use ZFS on the space left on disk. It is posible to do so ? Or can I reinstall freebsd and only have 10GB for /usr and the rest of the disk for ZFS. It is posible to have ZFS and UFS on the same disk. freebsd-questions@ might be a better place to ask. Reply-To: set /bz -- Bjoern A. Zeeb Stop bit received. Insert coin for new game. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
I'm using GRUB and it has no problem recognizing UFS2 slices. Same version than you, GRUB 0.97. Regards Ezequiel R. Aguerre 2008/11/13 Unga [EMAIL PROTECTED] --- On Thu, 11/13/08, Pieter de Goeje [EMAIL PROTECTED] wrote: I've used GRUB in the past to boot FreeBSD. The GRUB boot directory was located on the FreeBSD root partition, so it can work. I did use the port though. Now the issue is the root partition itself cannot access. Were your partitions ufs2? Which version of GRUB you used? Any possibility to give it a try again? Regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: port upgrade problem: libncurses.so.5.6 not found
what would happen if I don't compile ports all over again? will my system crash? TFC On Thu, Nov 13, 2008 at 1:02 PM, Mel [EMAIL PROTECTED] wrote: On Thursday 13 November 2008 18:17:02 Tsu-Fan Cheng wrote: Mel, thank you for your help, here is the output: /usr/local/bin/xgettext: libgettextsrc-0.17.so = /usr/local/lib/libgettextsrc-0.17.so (0x280a9000) libgettextlib-0.17.so = /usr/local/lib/libgettextlib-0.17.so (0x280de000) libcroco-0.6.so.3 = /usr/local/lib/libcroco-0.6.so.3 (0x281bb000) libxml2.so.5 = /usr/local/lib/libxml2.so.5 (0x281ef000) libz.so.4 = /lib/libz.so.4 (0x2831b000) libm.so.5 = /lib/libm.so.5 (0x2832d000) libglib-2.0.so.0 = /usr/local/lib/libglib-2.0.so.0 (0x28342000) libicui18n.so.38 = /usr/local/lib/libicui18n.so.38 (0x283f1000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x28559000) libpcre.so.0 = /usr/local/lib/libpcre.so.0 (0x28562000) libncurses.so.5.6 = not found (0x0) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libbsdxml.so.3 = /lib/libbsdxml.so.3 (0x28685000) libc.so.7 = /lib/libc.so.7 (0x286a3000) FreeBSD 7 /usr/local/lib/libgettextsrc-0.17.so: libgettextlib-0.17.so = /usr/local/lib/libgettextlib-0.17.so (0x280de000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x28559000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libgettextlib-0.17.so: libcroco-0.6.so.3 = /usr/local/lib/libcroco-0.6.so.3 (0x281bb000) libxml2.so.5 = /usr/local/lib/libxml2.so.5 (0x281ef000) libz.so.4 = /lib/libz.so.4 (0x2831b000) libm.so.5 = /lib/libm.so.5 (0x2832d000) Also FreeBSD 7 libglib-2.0.so.0 = /usr/local/lib/libglib-2.0.so.0 (0x28342000) libicui18n.so.38 = /usr/local/lib/libicui18n.so.38 (0x283f1000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x28559000) libpcre.so.0 = /usr/local/lib/libpcre.so.0 (0x28562000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libncurses.so.5.6 = not found (0x0) libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libcroco-0.6.so.3: libglib-2.0.so.0 = /usr/local/lib/libglib-2.0.so.0 (0x28342000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libxml2.so.5 = /usr/local/lib/libxml2.so.5 (0x281ef000) libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libxml2.so.5: libz.so.4 = /lib/libz.so.4 (0x2831b000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libm.so.5 = /lib/libm.so.5 (0x2832d000) libc.so.7 = /lib/libc.so.7 (0x286a3000) /lib/libz.so.4: libc.so.7 = /lib/libc.so.7 (0x286a3000) /lib/libm.so.5: libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libglib-2.0.so.0: libicui18n.so.38 = /usr/local/lib/libicui18n.so.38 (0x283f1000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x28559000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libpcre.so.0 = /usr/local/lib/libpcre.so.0 (0x28562000) libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libicui18n.so.38: libicuuc.so.38 = /usr/local/lib/libicuuc.so.38 (0x287a4000) libicudata.so.38 = /usr/local/lib/libicudata.so.38 (0x288b9000) libstdc++.so.5 = /usr/lib/libstdc++.so.5 (0x2939) libm.so.4 = /lib/libm.so.4 (0x2945b000) FreeBSD 6 /usr/local/lib/libintl.so.8: libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28591000) libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libpcre.so.0: libc.so.7 = /lib/libc.so.7 (0x286a3000) /lib/libbsdxml.so.3: libc.so.7 = /lib/libc.so.7 (0x286a3000) /usr/local/lib/libicuuc.so.38: libicudata.so.38 = /usr/local/lib/libicudata.so.38 (0x288b9000) libstdc++.so.5 = /usr/lib/libstdc++.so.5 (0x2939) FreeBSD 6 libm.so.4 = /lib/libm.so.4 (0x2945b000) /usr/lib/libstdc++.so.5: libm.so.4 = /lib/libm.so.4 (0x2945b000) Your system has stale libraries from the updates and linking is messy. It does not adequately explain the .5.6 library version numbers, but your system is in need of cleaning. Specifically, you forgot to do 'make delete-old-libs' when you upgraded from 6 to 7 (and maybe from 5 to 6 as well,tho there's no evidence of that in this mail). The best course of action is to go into /usr/src and type: # make delete-old # make delete-old-libs Delete everything that the program offers you to delete. Then drop to single user mode, so that no services are running and recompile *all* ports, using portupgrade -fa. you may need to do /etc/rc.d/netif start, so you can download stuff. I'm quite confident this will fix your problems, even tho it gives no explanation for this rogue ncurses library. -- Mel Problem with today's modular software: they start with the modules and never get to the software part.
Re: port upgrade problem: libncurses.so.5.6 not found
Tsu-Fan Cheng [EMAIL PROTECTED] writes: what would happen if I don't compile ports all over again? will my system crash? No, but any new program linked to some old libraries will. If you've rebuilt *any* ports, then (in practice) you really want to rebuild all of them. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
SSH timeouts from remote connections on 7.1beta
This is a recent phenomenon. I use a Mac client (iTerm) to connect to all my hosts internally. Same network. My connections to the FreeBSD-7.1.x system continually timeout when idle, and I have to re-connect (thankfully, I use screen). It's becoming annoying, and though I've set TcpKeepAlive, it still happens. I'm trying to track this down and understand where the problem is. The connections to my other hosts (Linux and Solaris) are fine - my FreeBSD connections have been fine until recently. Anyone see this happening or have more info. Thanks. /F ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 128 Bucket Failures?
Chris Pratt wrote: I have asked this before a couple of years ago but received no replies. I assumed that's because it's a somewhat obscure question. I'm still interested and thought I might try again in case someone new is watching this list who might know. A vmstat -z on my highest traffic server always shows the failures as below on 128 Bucket. It also goes to having 0 free rather soon after the system is restarted and never returns to having more than 1 free in that column and yet always has the highest number of requests by far. Does this mean anything significant? Is it something I should tune or even can be tuned? UMA buckets seem to be some kind of cache for SMP-optimized allocations - I hope someone who knows it better will explain them. Here is the output of the vmstat -z with everything chopped out besides the 128 Bucket line. The machine it's on is an 8 core 8 GB Tyan and shouldn't really be starved for anything in my way of thinking. vmstat -z ITEM SIZE LIMIT USED FREE REQUESTS FAILURES 128 Bucket: 1048,0, 2043,0,13591, 6511069 What is the server used for? Here's a snapshot from a very loaded apache+php+pgsql web server, uptime 60 days (since the last power outage): 16 Bucket: 76,0, 42, 58, 125, 0 32 Bucket:140,0, 76, 64, 183, 0 64 Bucket:268,0, 74, 38, 438, 11 128 Bucket: 524,0, 2060, 642, 788828, 6985 A generic advice would be to increase vm.kmem_size (you're using AMD64, right?) and see what happens. signature.asc Description: OpenPGP digital signature
Re: SSH timeouts from remote connections on 7.1beta
On Thursday 13 November 2008 22:29:40 Forrest Aldrich wrote: This is a recent phenomenon. I use a Mac client (iTerm) to connect to all my hosts internally. Same network. My connections to the FreeBSD-7.1.x system continually timeout when idle, and I have to re-connect (thankfully, I use screen). It's becoming annoying, and though I've set TcpKeepAlive, it still happens. ServerAliveInterval client side is what you're looking for. From ssh_config(5): ServerAliveCountMax Sets the number of server alive messages (see below) which may be sent without ssh(1) receiving any messages back from the server. If this threshold is reached while server alive messages are being sent, ssh will disconnect from the server, terminating the session. It is important to note that the use of server alive messages is very different from TCPKeepAlive (below). The server alive messages are sent through the encrypted channel and there- fore will not be spoofable. The TCP keepalive option enabled by TCPKeepAlive is spoofable. The server alive mechanism is valu- able when the client or server depend on knowing when a connec- tion has become inactive. The default value is 3. If, for example, ServerAliveInterval (see below) is set to 15 and ServerAliveCountMax is left at the default, if the server becomes unresponsive, ssh will disconnect after approximately 45 seconds. This option applies to protocol version 2 only. ServerAliveInterval Sets a timeout interval in seconds after which if no data has been received from the server, ssh(1) will send a message through the encrypted channel to request a response from the server. The default is 0, indicating that these messages will not be sent to the server. This option applies to protocol version 2 only. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Openssl port upgrade (FreeBSD 6.2)
Brendan Kennedy wrote: Hi All, I ran the openssl updgrade (to OpenSSL 0.9.8d), but it seems the original openssl libs are still being used for SSH session creation and other system crypto functionality. What are the final steps needed to allow all user space programs to use the upgraded OpenSSL? Is there a good guide for this kind of upgrade somewhere? Best Regards, Brendan This might be useful - it is from 'Building a Server with FreeBSD 7' by Bryan Hong. Default search path for /usr/local, where local software is typically installed, is near the end of the path statement, after base command paths. Edit /root/.cshrc as follows: a) comment out the existing or default 'set path' statement by preceding it with a hash mark (#) b) insert this statement: set path = (/usr/local/sbin /usr/local/bin /usr/sbin /usr/bin /sbin /bin $HOME/bin) hope this works Cam ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: port upgrade problem: libncurses.so.5.6 not found
On Thu, 13 Nov 2008 15:41:25 -0500 Tsu-Fan Cheng [EMAIL PROTECTED] wrote: what would happen if I don't compile ports all over again? will my system crash? I believe that the total stability of your system might be jeopardized. Personally, I use 'portmanager' to force an update of all my installed ports. After updating your ports tree, using 'portmanager -u -f -y -l' will update everything in the correct order. If you have 'java' installed, make sure you download the required files prior to starting the update procedure. -- Jerry [EMAIL PROTECTED] There are two kinds of pedestrians... the quick and the dead. Lord Thomas Rober Dewar signature.asc Description: PGP signature
Re: 128 Bucket Failures?
On Nov 13, 2008, at 1:34 PM, Ivan Voras wrote: Chris Pratt wrote: I have asked this before a couple of years ago but received no replies. I assumed that's because it's a somewhat obscure question. I'm still interested and thought I might try again in case someone new is watching this list who might know. A vmstat -z on my highest traffic server always shows the failures as below on 128 Bucket. It also goes to having 0 free rather soon after the system is restarted and never returns to having more than 1 free in that column and yet always has the highest number of requests by far. Does this mean anything significant? Is it something I should tune or even can be tuned? UMA buckets seem to be some kind of cache for SMP-optimized allocations - I hope someone who knows it better will explain them. Here is the output of the vmstat -z with everything chopped out besides the 128 Bucket line. The machine it's on is an 8 core 8 GB Tyan and shouldn't really be starved for anything in my way of thinking. vmstat -z ITEM SIZE LIMIT USED FREE REQUESTS FAILURES 128 Bucket: 1048,0, 2043,0, 13591, 6511069 What is the server used for? A busy webserver (about 5G Views a month, average view is 3-4 hits). Not really large pages, we keep graphics minimal. It's apache, perl cgi, mysqld. Tends to collect a lot of garbage traffic attacks on top of real traffic, both TCP and UDP. Here's a snapshot from a very loaded apache+php+pgsql web server, uptime 60 days (since the last power outage): 16 Bucket: 76,0, 42, 58, 125, 0 32 Bucket:140,0, 76, 64, 183, 0 64 Bucket:268,0, 74, 38, 438, 11 128 Bucket: 524,0, 2060, 642, 788828, 6985 A generic advice would be to increase vm.kmem_size (you're using AMD64, right?) and see what happens. I'll try that. I had heard this before in relation to KVA but have been concerned about trying it. If I can just change that knob and have an effect, seems worth a try. If more than one person is doing it, it must be safe? Yes, AMD64. Thank you very much. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
error message eval: 1: Syntax error: | unexpected, [libglib-2.0.la] error 2 when I portupgrade glib-2\*
Hello ladies and gentlemen, In /usr/ports/UPDATING, you can see there is a glib upgrade issue on the date 20080323, I perform portupgrade glib-2\* , but get an error message ntf.o .libs/giounix.o .libs/gspawn.o libcharset/.libs/libcharset.a | | /usr/bin/sed 's/.* //' | sort | uniq .libs/libglib-2.0.exp eval: 1: Syntax error: | unexpected gmake[4]: *** [libglib-2.0.la] error 2 gmake[4]: Leaving directory `/usr/ports/devel/glib20/work/glib-2.16.5/glib Anybody can help me to fix it ? Thanks a lot. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Looking information about CF files of LPD
Hi: I have the idea of had seen the description of the content of CF files, but I can't find anymore in the handbook. That information had been removed? maps ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Terminal vt220 to vt100
Hi: I use vt220 to acces aPc with FreeBSD, but I need to telnet to a divice in my network that only acept vt100 man telnet did not help. maps ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Terminal vt220 to vt100
On Thu, Nov 13, 2008, Martin Alejandro Paredes Sanchez wrote: Hi: I use vt220 to acces aPc with FreeBSD, but I need to telnet to a divice in my network that only acept vt100 man telnet did not help. Telnet does not know anything about terminal emulations, that is controlled by your TERM environment variable and the program from which you are running telnet (e.g. an xterm, putty, etc.). Setting the environment variable TERM=vt100 after telnet'ing to the remote system may work or perhaps using the command TERM=vt100 telnet destination Bill -- INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way Voice: (206) 236-1676 Mercer Island, WA 98040-0820 Fax:(206) 232-9186 I have never been molested by any person but those who represented the state -- Thoreau ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
