Re: Problem Installing native jdk1.5.0 on FreeBSD 5.3-RELEASE
All I had to do was to disable Kernel Security in /etc/rc.conf.. -V On Fri, 2005-10-14 at 18:03, Vincent Ngundi wrote: Objective - I'm trying to install native jdk 1.5.0 on a box running FreeBSD 5.3-RELEASE. Problem --- When I run make install clean, I'm getting a message telling me that I should mount LINPROCFS before starting to build jdk 1.5.0 and that the commands kldload linprocfs and mount -t linprocfs linprocfs /compat/linux/proc should do that. ** Major Problem: When I run kldload linprocfs (as root), I get the following error: kldload: can't load linprocfs: Operation not permitted I have the following files on my box: /usr/src/sys/compat/linprocfs /usr/src/sys/i386/compile//modules/usr/src/sys/modules/linprocfs /usr/src/sys/modules/linprocfs What I have done ) I have tried to googled out the error ) I have lowered the _kernel_secure_level to 1...even to -1 ) I have added the following line into my /etc/fstab file: linprocfs /compat/linux/proc linprocfs rw 0 0 I still get the same error when I run kldload linprocfs. Please help!! -- -Vincent ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with modem Zyxel OMNI PCI in FreeBSD 5.3-RELEASE
Hi all How use this modem in FreeBSD I have read HandBook, as well as HARDWARE.TXT on Install CD, but don't find necessary information. I will be grateful for the help ! Sukharew Andrew System Administrator State institution Research of Yamal Tel.(work) +7(34922)7-16-05 (Internal) 502, 777 (home) +7 (34922) 7-27-17 e-mail: [EMAIL PROTECTED] ICQ UIN# 174811927 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem Installing native jdk1.5.0 on FreeBSD 5.3-RELEASE
Objective - I'm trying to install native jdk 1.5.0 on a box running FreeBSD 5.3-RELEASE. Problem --- When I run make install clean, I'm getting a message telling me that I should mount LINPROCFS before starting to build jdk 1.5.0 and that the commands kldload linprocfs and mount -t linprocfs linprocfs /compat/linux/proc should do that. ** Major Problem: When I run kldload linprocfs (as root), I get the following error: kldload: can't load linprocfs: Operation not permitted I have the following files on my box: /usr/src/sys/compat/linprocfs /usr/src/sys/i386/compile//modules/usr/src/sys/modules/linprocfs /usr/src/sys/modules/linprocfs What I have done ) I have tried to googled out the error ) I have lowered the _kernel_secure_level to 1...even to -1 ) I have added the following line into my /etc/fstab file: linprocfs /compat/linux/proc linprocfs rw 0 0 I still get the same error when I run kldload linprocfs. Please help!! -- -Vincent ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 5.3-release crashes when mouse not plugged in ?!
Pentium II / 433 MHz, VIA 693 chipset At kernel booting system regulary crashes followed with spontaneous restart. After many experiments I've figured out it was caused by absence of connected PS/2 mouse. It's very strange, but when I plug it in, system normaly boots and is working. It's very annoyng and this box should be dedicated to mail server without any peripherials like mouse and keyboard connected. How do I tweak kernel settings to prevent such a dumb behaviour ? Thanks in an advance Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Low HDD tranfer rate with FreeBSD 5.3-Release
Hi all, I am using Tyan S2098 MB with 160GB Maxtor ATA Drive and the transfer rate is very low. FreeBSD 5.3-Release. Any ideas what is going on here. The transfer rate is about 15MB/s when I run #dd if=/dev/zero of=/usr/junk bs=8192 then do #iostat 1 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Low HDD tranfer rate with FreeBSD 5.3-Release
Amandeep wrote: Hi all, I am using Tyan S2098 MB with 160GB Maxtor ATA Drive and the transfer rate is very low. FreeBSD 5.3-Release. Any ideas what is going on here. The transfer rate is about 15MB/s when I run #dd if=/dev/zero of=/usr/junk bs=8192 then do #iostat 1 You should probably provide the appropriate information from dmesg output, along with what you expect it to be, and the outputs of the dd command. Eric -- Eric AndersonSr. Systems AdministratorCentaur Technology A lost ounce of gold may be found, a lost moment of time never. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Low HDD tranfer rate with FreeBSD 5.3-Release
Hi Eric, Shouldnt it be around 54MB/s for a regular IDE drive. Here is the output of dmesg and iostat Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2391.14-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 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 real memory = 1064173568 (1014 MB) avail memory = 1031811072 (984 MB) ACPI APIC Table: IntelR AWRDACPI ioapic0 Version 2.0 irqs 0-23 on motherboard npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: IntelR AWRDACPI on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 acpi_tz0: Thermal Zone on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82845G (845G GMCH) SVGA controller mem 0xe810-0xe817,0xe000-0xe7ff irq 16 at device 2.0 on pci0 agp0: detected 8060k stolen memory agp0: aperture size is 128M uhci0: Intel 82801DB (ICH4) USB controller USB-A port 0xe200-0xe21f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82801DB (ICH4) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801DB (ICH4) USB controller USB-B port 0xe000-0xe01f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: Intel 82801DB (ICH4) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801DB (ICH4) USB controller USB-C port 0xe100-0xe11f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: Intel 82801DB (ICH4) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: serial bus, USB at device 29.7 (no driver attached) pcib1: ACPI PCI-PCI bridge at device 30.0 on pci0 pci1: ACPI PCI bus on pcib1 em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0xd000-0xd03f mem 0xe802-0xe803,0xe800-0xe801 irq 21 at device 3.0 on pci1 em0: Ethernet address: 00:e0:81:56:1e:64 em0: Speed:N/A Duplex:N/A em1: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0xd100-0xd13f mem 0xe806-0xe807,0xe804-0xe805 irq 20 at device 4.0 on pci1 em1: Ethernet address: 00:e0:81:56:1e:65 em1: Speed:N/A Duplex:N/A isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH4 UDMA100 controller port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: serial bus, SMBus at device 31.3 (no driver attached) fdc0: floppy drive controller port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 orm0: ISA Option ROM at iomem 0xcc000-0xccfff on isa0 pmtimer0 on isa0 ppc0: parallel port not found. sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 2391144260 Hz quality 800 Timecounters tick every 10.000 msec ad0: 156334MB Maxtor 6Y160P0/YAR41BW0 [317632/16/63] at ata0-master UDMA100 acd0: DVDROM HL-DT-STDVD-ROM GDR8082N/0002 at ata1-master UDMA33 Mounting root from ufs:/dev/ad0s1a em0: Link is up 100 Mbps Full Duplex em0: Link is up 100 Mbps Full Duplex em0: Link is up 100 Mbps Full Duplex IOSTAT tty ad0 cpu tin tout KB/t tps MB/s us ni sy in id 0 20 114.15 10 1.09 0 0 1 0 98 00 0.00 0 0.00 0 0 0 0 100 00 0.00 0 0.00 0 0 0 0 100 13 128.00 21 2.60 0 0 3 0 97 00 128.00 124 15.47 0 0 6 2 91 00 117.49 133 15.22 0 0 6 0 94 00 128.00 124 15.47 0 0 8 0 92 00 126.11 125 15.36 0 0 10 2 88 00 128.00 124 15.47 0 0 8 0 92 00 128.00 124 15.47 0 0 6 0 94 00 127.10 123 15.24 0 0 6 0 94 00 128.00
Re: Low HDD tranfer rate with FreeBSD 5.3-Release
Eric Anderson wrote: Amandeep wrote: Hi all, I am using Tyan S2098 MB with 160GB Maxtor ATA Drive and the transfer rate is very low. FreeBSD 5.3-Release. Any ideas what is going on here. The transfer rate is about 15MB/s when I run #dd if=/dev/zero of=/usr/junk bs=8192 then do #iostat 1 You should probably provide the appropriate information from dmesg output, along with what you expect it to be, and the outputs of the dd command. Eric Amandeep wrote: Hi Eric, Shouldnt it be around 54MB/s for a regular IDE drive. Here is the output of dmesg and iostat [..snip dmesg blob..] IOSTAT tty ad0 cpu tin tout KB/t tps MB/s us ni sy in id 0 20 114.15 10 1.09 0 0 1 0 98 00 0.00 0 0.00 0 0 0 0 100 00 0.00 0 0.00 0 0 0 0 100 13 128.00 21 2.60 0 0 3 0 97 00 128.00 124 15.47 0 0 6 2 91 [..snip iostat blob..] (please try to avoid top-posting, it's hard to follow) What about other block sizes? Also - you should paste your actual dd output here too. What's the model number of that drive? Maxtor claims (on one of their 160G drives) 17.8MB/s from inner diameter disk and 35.6MB/s for outer diameter for the 5400rpm drives. Eric -- Eric AndersonSr. Systems AdministratorCentaur Technology A lost ounce of gold may be found, a lost moment of time never. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Low HDD tranfer rate with FreeBSD 5.3-Release
In the last episode (May 09), Eric Anderson said: Eric Anderson wrote: Amandeep wrote: I am using Tyan S2098 MB with 160GB Maxtor ATA Drive and the transfer rate is very low. FreeBSD 5.3-Release. Any ideas what is going on here. The transfer rate is about 15MB/s when I run #dd if=/dev/zero of=/usr/junk bs=8192 Shouldnt it be around 54MB/s for a regular IDE drive. What about other block sizes? Also - you should paste your actual dd output here too. What's the model number of that drive? Maxtor claims (on one of their 160G drives) 17.8MB/s from inner diameter disk and 35.6MB/s for outer diameter for the 5400rpm drives. Yes, try 64k instead of 8k, and also compare read speeds. If you have the time (could take an hour or so), try dd if=/dev/ad0 of=/dev/null bs=64k, run an iostat 60 in another window, let the dd run through the entire disk, and compare the relative speeds from start to finish. For the DiamondMax 160, the sustained throughput should be 26MB - 50MB as you go from inner to outer tracks. -- Dan Nelson [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: Low HDD tranfer rate with FreeBSD 5.3-Release
Dan Nelson wrote: In the last episode (May 09), Eric Anderson said: Eric Anderson wrote: Amandeep wrote: I am using Tyan S2098 MB with 160GB Maxtor ATA Drive and the transfer rate is very low. FreeBSD 5.3-Release. Any ideas what is going on here. The transfer rate is about 15MB/s when I run #dd if=/dev/zero of=/usr/junk bs=8192 Shouldnt it be around 54MB/s for a regular IDE drive. What about other block sizes? Also - you should paste your actual dd output here too. What's the model number of that drive? Maxtor claims (on one of their 160G drives) 17.8MB/s from inner diameter disk and 35.6MB/s for outer diameter for the 5400rpm drives. Yes, try 64k instead of 8k, and also compare read speeds. If you have the time (could take an hour or so), try dd if=/dev/ad0 of=/dev/null bs=64k, run an iostat 60 in another window, let the dd run through the entire disk, and compare the relative speeds from start to finish. For the DiamondMax 160, the sustained throughput should be 26MB - 50MB as you go from inner to outer tracks. OK with the above dd dd if=/dev/ad0 of=/dev/null bs=64k it gives me 56MB/s. from the start. Aman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Low HDD tranfer rate with FreeBSD 5.3-Release
Amandeep wrote: Dan Nelson wrote: In the last episode (May 09), Eric Anderson said: Eric Anderson wrote: Amandeep wrote: I am using Tyan S2098 MB with 160GB Maxtor ATA Drive and the transfer rate is very low. FreeBSD 5.3-Release. Any ideas what is going on here. The transfer rate is about 15MB/s when I run #dd if=/dev/zero of=/usr/junk bs=8192 Shouldnt it be around 54MB/s for a regular IDE drive. What about other block sizes? Also - you should paste your actual dd output here too. What's the model number of that drive? Maxtor claims (on one of their 160G drives) 17.8MB/s from inner diameter disk and 35.6MB/s for outer diameter for the 5400rpm drives. Yes, try 64k instead of 8k, and also compare read speeds. If you have the time (could take an hour or so), try dd if=/dev/ad0 of=/dev/null bs=64k, run an iostat 60 in another window, let the dd run through the entire disk, and compare the relative speeds from start to finish. For the DiamondMax 160, the sustained throughput should be 26MB - 50MB as you go from inner to outer tracks. OK with the above dd dd if=/dev/ad0 of=/dev/null bs=64k it gives me 56MB/s. from the start. Aman So how does the block size makes the difference?? What is the true transfer rate.? Aman ___ 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: Low HDD tranfer rate with FreeBSD 5.3-Release
In the last episode (May 09), Amandeep said: Amandeep wrote: The transfer rate is about 15MB/s when I run #dd if=/dev/zero of=/usr/junk bs=8192 OK with the above dd dd if=/dev/ad0 of=/dev/null bs=64k it gives me 56MB/s. from the start. So how does the block size makes the difference?? What is the true transfer rate.? At the moment, 56MB/sec :) Those two speeds aren't directly comparable, since your first was testing writes through the filesystem with a small blocksize, and the second was testing reads to the raw device with a large blocksize. Usually reading, using raw devices, and using large blocksizes are faster then writing, using a filesystem, and using small blocksizes, so all three changes probably contributed a little to the speed difference. -- Dan Nelson [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: Low HDD tranfer rate with FreeBSD 5.3-Release
At 03:50 PM 5/9/2005, you wrote: So how does the block size makes the difference?? What is the true transfer rate.? FWIW, there's a nice little disk IO benchmark Bonnie available in the ports packages. Tests several variations of sequential and random IO. I don't know how accurate its numbers in absolute terms, but it's at least good for relative comparisons of devices on similar systems. Be sure to use the -s option to increase the test file size to something larger than your ram. Sample Output: /datatel bonnie -s 1000 File './Bonnie.709', size: 1048576000 Writing with putc()...done Rewriting...done Writing intelligently...done Reading with getc()...done Reading intelligently...done Seeker 1...Seeker 3...Seeker 2...start 'em...done...done...done... ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 1000 10835 98.5 26996 18.1 19876 15.2 8925 83.6 62490 23.0 325.9 3.3 -Wayne ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Low HDD tranfer rate with FreeBSD 5.3-Release
Amandeep wrote: Hi all, I am using Tyan S2098 MB with 160GB Maxtor ATA Drive and the transfer rate is very low. FreeBSD 5.3-Release. Any ideas what is going on here. The transfer rate is about 15MB/s when I run #dd if=/dev/zero of=/usr/junk bs=8192 then do #iostat 1 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] Check the performance archive for a long thread on disk tweaking. sysctl vfs.read_max=32 should give you a good boost, but read that thread being attempting this. There was another tweak in there I found interesting, but can be dangerous. I'll let you look that one up. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Scanning in FreeBSD 5.3-RELEASE, niash, and a busy signal
Hello all, My HP ScanJet 3300C will not scan due to being busy. I followed the steps of the FreeBSD manual and will show its output below in the event that it may help. I should note that the configuration is as follows: FreeBSD 5.3-RELEASE // GENERIC KERNEL Pentium III, 450 MHz If I had to guess the problem, I would say that it is possible that the niash driver (that is the sane-backend for this scanner) does not work well with FreeBSD's kernel driver, the kernel driver and libusb do not coexist well, or scanimage is only trying to use libusb and the kernel driver is not allowing it to. I know when I installed sane-backends (make make install make clean with a fully-updated Ports tree), it installed libusb as well, and I know this scanner works with libusb (I have gotten it to work on Mac OS X this way), hence my above conclusion. Does anyone have any other input on this? I should also note that I am root running these commands and that I have rebooted since plugging it in just in case. sane-find-scanner -q found USB scanner (vendor=0x03f0, product=0x0205) at /dev/uscanner0 scanimage -L device `niash:/dev/uscanner0' is a Hewlett-Packard ScanJet 3300C flatbed scanner scanimage image.pnm scanimage: open of device niash:/dev/uscanner0 failed: Device busy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 5.3-RELEASE error creating jail
$uname -a FreeBSD twinmp.tcbug.org 5.3-RELEASE-p5 FreeBSD 5.3-RELEASE-p5 #0: Wed Feb 9 16:54:40 CST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TWINMP i386 I am following the directions in man jail to set up a jail on my system: D=/here/is/the/jail cd /usr/src mkdir -p $D make world DESTDIR=$D cd etc make distribution DESTDIR=$D mount_devfs devfs $D/dev cd $D ln -sf dev/null kernel make world DESTDIR=$D fails with the following error: make: don't know how to make /storage1/jail/usr/lib/libc.a. Stop *** Error code 2 I've tried rm -rf /usr/obj and also rm -rf /usr/src -- Thanks, Josh Paetzel ___ 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.3-RELEASE error creating jail
it was said: I am following the directions in man jail to set up a jail on my system: D=/here/is/the/jail cd /usr/src mkdir -p $D make world DESTDIR=$D ^ Try changing this line to env DESTDIR=$D make world cd etc make distribution DESTDIR=$D mount_devfs devfs $D/dev cd $D ln -sf dev/null kernel make world DESTDIR=$D fails with the following error: make: don't know how to make /storage1/jail/usr/lib/libc.a. Stop I think this is a bug, but because a simple workaround exists, maybe it will become a training issue HTH, stheg __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Location of openssl certs in FreeBSD 5.3-RELEASE
On Fri, 11 Mar 2005 22:29:24 -0500, Madhusudan Singh [EMAIL PROTECTED] wrote: Anyways, where are the certs installed in FreeBSD ? There are no default certificates in FreeBSD. They are easy to create however. Look in the Handbook here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/openssl.html. If you want to create your own CA you can search for a howto on Google. There are enough of these published so you won't have a problem finding one. Frem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Native POSIX threads + Java under FreeBSD 5.3 release i386
Dear Dan, Thanks for your answer! A follow-up: Why would they require an OS-specific threads library, instead of simply requiring Posix threads? I can tell you right now that Solaris doesn't support NPTL, just the same way Linux doesn't support Solaris's thread library :) Interesting. The people who wrote the software told me that they used to have a version that worked well with the Linux 2.4 kernel threads version. Then, they said they had improved their software, and that it's based around the threading system as it is present in the Linux 2.6 kernel. They did indeed mention that we require Posix threads, so I guess they mean to say that we require Posix threads (rather than relying on a Linux 2.6 kernel perse). If you have limited time, I'd say just use either Solaris 10 or Linux. If you have problems on FreeBSD, they won't help you. Yes, I just called the client, and he strongly recommended simply looking for a Debian-9 or SuSe-9 system. I think I'll simply try that... I'm looking somewhat into the support for NPTL under FreeBSD 5.3 release i386, and I have come across the following URL: http://www.unobvious.com/bsd/freebsd-threads.html From this, it sounds like the LinuxThreads (i.e. /usr/ports/devel/linuxthreads) should do the trick. That page is 2 years old, and even says right in the middle, before comparing libc_r and linuxthreads: WARNING: The rest of this document does not describe thread support in FreeBSD 5.x . You have been warned. :) I think I didn't express myself the way I meant to (sorry for that). Basically what I meant to write was that from the document I gathered that the /usr/ports/devel/linuxthreads port is what should be used. But indeed upon re-reading my own text, it suggests that I had gathered from the document that that would work under versions 5.x as well (which was not what I meant to imply). Anyway, your following answer basically answers what I wanted to know: Can anyone tell me something about the following: 1) Does the linuxthreads library provide 100% NPTL support, as under Linux? Linuxthreads is the Linux 2.4 and below threads package. NPTL is the name for the threads implementation in Linux 2.6 kernels. As far as I know, linuxthreads and NPTL are relatively ABI-compatible. From this, I gather the linuxthreads port will not give me the threading system as used in the Linux 2.6 kernel then... O.k., I think I know enough for now: I'll first try having a go at Red Hat or SuSe then Thanks again, and cheers! Olafo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Location of openssl certs in FreeBSD 5.3-RELEASE
Hi I am trying to set up bincimap with ssl support as a part of a wider qmail setup for a mailserver. I have openssl installed (man openssl opens up the right manpage). I want to know where are the certs installed. The reason is that the FAQ on bincimap's webpage states : SSL in Binc IMAP is quite simple to set up. First you need a PEM encoded private key and certificate file. In some distributions, you can generate this file by changing to /usr/share/ssl/certs and running make. A script will give you the option to build a PEM file. http://www.bincimap.org/bincimap-faq.html#q3 I tried locate cert. It throws up an openssl tree (looks like an installation tree) in /usr/src (might have been the result of an aborted cvsup operation a few days ago). Anyways, where are the certs installed in FreeBSD ? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Native POSIX threads + Java under FreeBSD 5.3 release i386
Hi all, As is typical, I have once again been given very limited time to get something running, and there are some interesting things to figure about about it. :) In brief, the application is a distributed one, loosely based on some CORBA concepts, though differently (fortunately!). The supported programming languages are C/C++/Java/Ada, of which Java will probably be the one we would like to use. Now, the issue is (or may be), that the recommended (and only tested) platforms are Solaris and Linux (particularly Red Hat and SuSe - kernel versions 9). The apparent reason for this, is that the platform requires the NPTL (Native Posix Threads Library). I'm looking somewhat into the support for NPTL under FreeBSD 5.3 release i386, and I have come across the following URL: http://www.unobvious.com/bsd/freebsd-threads.html From this, it sounds like the LinuxThreads (i.e. /usr/ports/devel/linuxthreads) should do the trick. However, I have no experience with these threads and I wonder whether it is a good idea to try to get the platform working under FreeBSD (my favourite Unix), or whether it may be better to install Red Hat or SuSe this once. :) Can anyone tell me something about the following: 1) Does the linuxthreads library provide 100% NPTL support, as under Linux? 2) Does usage of the library incur a kernel recompilation, or will all scripts of the platform have to be changed such that the linuxthreads library is linked in? 3) A different question: what is the best JDK 1.4.x port to install, and does one of those perhaps have support for NPTL? I hope anyone can help me out a bit with this, even if it only is about whether to make the best choice between figuring out how to get this platform going under FreeBSD (being the Unix with which most experience I have), or whether to try to go Linux and have a -perhaps- more straightforward installation of the platform (at the expense of not knowing the particular intricacies of those Linuxes). Help/opinions are very much appreciated. :) Cheers! Olafo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Native POSIX threads + Java under FreeBSD 5.3 release i386
In the last episode (Mar 10), Olaf Greve said: As is typical, I have once again been given very limited time to get something running, and there are some interesting things to figure about about it. :) In brief, the application is a distributed one, loosely based on some CORBA concepts, though differently (fortunately!). The supported programming languages are C/C++/Java/Ada, of which Java will probably be the one we would like to use. Now, the issue is (or may be), that the recommended (and only tested) platforms are Solaris and Linux (particularly Red Hat and SuSe - kernel versions 9). The apparent reason for this, is that the platform requires the NPTL (Native Posix Threads Library). Why would they require an OS-specific threads library, instead of simply requiring Posix threads? I can tell you right now that Solaris doesn't support NPTL, just the same way Linux doesn't support Solaris's thread library :) If you have limited time, I'd say just use either Solaris 10 or Linux. If you have problems on FreeBSD, they won't help you. If it was a longer-term project where you had time to resolve problems yourself, I'd say spend the time to get it working on FreeBSD. I'm looking somewhat into the support for NPTL under FreeBSD 5.3 release i386, and I have come across the following URL: http://www.unobvious.com/bsd/freebsd-threads.html From this, it sounds like the LinuxThreads (i.e. /usr/ports/devel/linuxthreads) should do the trick. That page is 2 years old, and even says right in the middle, before comparing libc_r and linuxthreads: WARNING: The rest of this document does not describe thread support in FreeBSD 5.x . You have been warned. However, I have no experience with these threads and I wonder whether it is a good idea to try to get the platform working under FreeBSD (my favourite Unix), or whether it may be better to install Red Hat or SuSe this once. :) Can anyone tell me something about the following: 1) Does the linuxthreads library provide 100% NPTL support, as under Linux? Linuxthreads is the Linux 2.4 and below threads package. NPTL is the name for the threads implementation in Linux 2.6 kernels. As far as I know, linuxthreads and NPTL are relatively ABI-compatible. 2) Does usage of the library incur a kernel recompilation, or will all scripts of the platform have to be changed such that the linuxthreads library is linked in? The kernel don't come into the equation. If you want to use Linuxthreads with an existing threaded application, you will need to recompile (take a look at one of the mysql ports to see how to configure a program for linuxthreads). All the native FreeBSD threads libraries (libpthread, libthr, libc_r) are ABI-compatible with each other (so you can switch between them via libmap.conf) but not with Linuxthreads. 3) A different question: what is the best JDK 1.4.x port to install, and does one of those perhaps have support for NPTL? The native one (ports/java/jdk14), and no. I hope anyone can help me out a bit with this, even if it only is about whether to make the best choice between figuring out how to get this platform going under FreeBSD (being the Unix with which most experience I have), or whether to try to go Linux and have a -perhaps- more straightforward installation of the platform (at the expense of not knowing the particular intricacies of those Linuxes). Help/opinions are very much appreciated. :) -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with start up script - qmail on FreeBSD 5.3 RELEASE
Hi, I am trying to install and configure qmail on FreeBSD 5.3-RELEASE. I manage to start qmail automatically upon reboot, but whenever I start another daemon through /usr/local/etc/rc.d/daemonname.sh, I get this: %sudo sh /usr/local/etc/rc.d/samba.sh restart [1] 13163 Starting qmail %sudo sh apache2.sh start [1] 85041 Starting qmail %sudo sh apache2.sh stop [1] 85657 Starting qmail Qmail is not working properly, but that is an entirely different matter. Any clues what is producing the Starting qmail message? It is definitely not in the daemonname.sh files. Any help is greatly appreciated. Thank you. Best regards, Lee Hanxue ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
A possibly simple query about pf on FreeBSD 5.3-RELEASE
After nearly a week of fighting the dual problem of OpenBSD 3.6 release freezing on my hardware, and some rather odious personalities on the [EMAIL PROTECTED] mailing list, I decided to install FreeBSD 5.3-RELEASE on the web server I am deploying and stick to it. I went through the webpage on firewalling on FreeBSD (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls-pf.html) and decided to pick pf as my firewall solution. The OpenBSD guide on this simply and elegantly written and is very easy to get the hang of. I have created a packet filtering ruleset in /etc/pf.conf, enabled the switches in /etc/rc.conf and am fiddling around with it. I tried to connect on port ssh (22, I think) and did a few tests with different IP addresses and it works as I expect. Since this beast is going to be a webserver, I wrote the following filter for port www : (previously blocking all and scrubbing all of course) pass in on $ext_if proto tcp from any to $ext_if \ port www flags S/SA keep state \ (max 200,source-track rule,max-src-nodes 100,max-src-states 3) Question : Is the above a reasonably good rule for my situation (if you have further questions, fire away) ? Second, whenever I load my rule set (pfctl -f /etc/pf.conf), I get a warning : No ALTQ support in kernel ALTQ related functions disabled Now, I would probably want to use queueing and bandwidth allotment if I am to run a webserver that allows a few IP addresses to connect via ssh. Question : How do I enable ALTQ support in the kernel ? And since I have the choice of either using a loadable module for pf (like I am doing) or compiling in PF support into the kernel, which is better from a security and performance pov ? Another issue, unrelated to pf : I am trying to install plone, zope (and a bunch of zope/plone related packages) and apache on the machine. However, the pkg_add process quit with some errors for some of the packages and refered me to some log (which log ?) during installation. Question : Are versions in the ports tree for these packages kosher, i.e., do they compile, install and work cleanly ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A possibly simple query about pf on FreeBSD 5.3-RELEASE
On Tuesday 01 March 2005 10:44 am, Madhusudan Singh wrote: After nearly a week of fighting the dual problem of OpenBSD 3.6 release freezing on my hardware, and some rather odious personalities on the [EMAIL PROTECTED] mailing list, I decided to install FreeBSD 5.3-RELEASE on the web server I am deploying and stick to it. I went through the webpage on firewalling on FreeBSD (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls- pf.html) and decided to pick pf as my firewall solution. The OpenBSD guide on this simply and elegantly written and is very easy to get the hang of. I have created a packet filtering ruleset in /etc/pf.conf, enabled the switches in /etc/rc.conf and am fiddling around with it. I tried to connect on port ssh (22, I think) and did a few tests with different IP addresses and it works as I expect. Since this beast is going to be a webserver, I wrote the following filter for port www : (previously blocking all and scrubbing all of course) pass in on $ext_if proto tcp from any to $ext_if \ port www flags S/SA keep state \ (max 200,source-track rule,max-src-nodes 100,max-src-states 3) Question : Is the above a reasonably good rule for my situation (if you have further questions, fire away) ? Second, whenever I load my rule set (pfctl -f /etc/pf.conf), I get a warning : No ALTQ support in kernel ALTQ related functions disabled Now, I would probably want to use queueing and bandwidth allotment if I am to run a webserver that allows a few IP addresses to connect via ssh. Question : How do I enable ALTQ support in the kernel ? And since I have the Add the following line to your kernel configuration file and compile/install a new kernel. options ALTQ For instructions regarding kernel configuration/installation, see Chapter 8 of the online manual: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html choice of either using a loadable module for pf (like I am doing) or compiling in PF support into the kernel, which is better from a security and performance pov ? pf is compiled into the GENERIC kernel by default in FreeBSD 5.3. Another issue, unrelated to pf : I am trying to install plone, zope (and a bunch of zope/plone related packages) and apache on the machine. However, the pkg_add process quit with some errors for some of the packages and refered me to some log (which log ?) during installation. Question : Are versions in the ports tree for these packages kosher, i.e., do they compile, install and work cleanly ? Best of luck, Andrew Gould ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with start up script - qmail on FreeBSD 5.3 RELEASE
Hi, I am trying to install and configure qmail on FreeBSD 5.3-RELEASE. I manage to start qmail automatically upon reboot, but whenever I start another daemon through /usr/local/etc/rc.d/daemonname.sh, I get this: %sudo sh /usr/local/etc/rc.d/samba.sh restart [1] 13163 Starting qmail %sudo sh apache2.sh start [1] 85041 Starting qmail %sudo sh apache2.sh stop [1] 85657 Starting qmail Qmail is not working properly, but that is an entirely different matter. Any clues what is producing the Starting qmail message? It is definitely not in the daemonname.sh files. Any help is greatly appreciated. Thank you. Best regards, Lee Hanxue ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ruby-1.8.2_2 failed to install under Freebsd 5.3 release on AMD64
Bachelier Vincent wrote: Hi, I have a problem to install this programs In fact I want to use port version of portupgrade and it need ruby, but this version wouldn't install This is le log === Installing for ruby-1.8.2_2 === Generating temporary packing list === Checking if lang/ruby18 already installed ./miniruby ./instruby.rb --dest-dir= --make=make --mflags= -j 3 --make-flags= ARCH=amd64 OPSYS=FreeBSD OSREL=5.3 OSVERSION=503001 PORTOBJFORMAT=elf SYSTEMVERSION= -j 3 --mantype=doc install -c -p -m 0755 ruby18 /usr/local/bin/ruby18 ./miniruby ./ext/extmk.rb --dest-dir= --make=make --mflags= -j 3 --make-flags= ARCH=amd64 OPSYS=FreeBSD OSREL=5.3 OSVERSION=503001 PORTOBJFORMAT=elf SYSTEMVERSION= -j 3 install Do you have an idea ? Hi Vincent. Idem here for me: http://lists.freebsd.org/pipermail/freebsd-ports/2005-February/020660.html My solution: http://lists.freebsd.org/pipermail/freebsd-ports/2005-February/020512.html The attached makefile work for me. Bye Jacula ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ruby-1.8.2_2 failed to install under Freebsd 5.3 release on AMD64
Ok thx, it work but I have to modify the cut part because of the form of the html links you give me Why this patch aren't include in official branch of ports-cvs ? Well, thx for that, I will be able to update my system now :d Le Wed, Feb 09, 2005 at 10:24:14AM +0100, jacula a écrit: Date: Wed, 09 Feb 2005 10:24:14 +0100 From: jacula [EMAIL PROTECTED] User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.5) Gecko/20050206 To: freebsd-questions@freebsd.org Subject: Re: ruby-1.8.2_2 failed to install under Freebsd 5.3 release on AMD64 Bachelier Vincent wrote: Hi, I have a problem to install this programs In fact I want to use port version of portupgrade and it need ruby, but this version wouldn't install This is le log === Installing for ruby-1.8.2_2 === Generating temporary packing list === Checking if lang/ruby18 already installed ./miniruby ./instruby.rb --dest-dir= --make=make --mflags= -j 3 --make-flags= ARCH=amd64 OPSYS=FreeBSD OSREL=5.3 OSVERSION=503001 PORTOBJFORMAT=elf SYSTEMVERSION= -j 3 --mantype=doc install -c -p -m 0755 ruby18 /usr/local/bin/ruby18 ./miniruby ./ext/extmk.rb --dest-dir= --make=make --mflags= -j 3 --make-flags= ARCH=amd64 OPSYS=FreeBSD OSREL=5.3 OSVERSION=503001 PORTOBJFORMAT=elf SYSTEMVERSION= -j 3 install Do you have an idea ? Hi Vincent. Idem here for me: http://lists.freebsd.org/pipermail/freebsd-ports/2005-February/020660.html My solution: http://lists.freebsd.org/pipermail/freebsd-ports/2005-February/020512.html The attached makefile work for me. Bye Jacula ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Vincent Bachelier [EMAIL PROTECTED] Societe : Solintech Site pro: http://www.solintech.fr Project : Ripperwww: http://www.sourceforge.net/projects/ripperwww pgpmdZonrzcyK.pgp Description: PGP signature
ruby-1.8.2_2 failed to install under Freebsd 5.3 release on AMD64
Hi, I have a problem to install this programs In fact I want to use port version of portupgrade and it need ruby, but this version wouldn't install This is le log === Installing for ruby-1.8.2_2 === Generating temporary packing list === Checking if lang/ruby18 already installed ./miniruby ./instruby.rb --dest-dir= --make=make --mflags= -j 3 --make-flags= ARCH=amd64 OPSYS=FreeBSD OSREL=5.3 OSVERSION=503001 PORTOBJFORMAT=elf SYSTEMVERSION= -j 3 --mantype=doc install -c -p -m 0755 ruby18 /usr/local/bin/ruby18 ./miniruby ./ext/extmk.rb --dest-dir= --make=make --mflags= -j 3 --make-flags= ARCH=amd64 OPSYS=FreeBSD OSREL=5.3 OSVERSION=503001 PORTOBJFORMAT=elf SYSTEMVERSION= -j 3 install Do you have an idea ? -- Vincent Bachelier [EMAIL PROTECTED] Societe : Solintech Site pro: http://www.solintech.fr Project : Ripperwww: http://www.sourceforge.net/projects/ripperwww ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Enemy-Territory for Linux run Problem on FreeBSD 5.3 Release
On Tue, 25 Jan 2005 18:20:26 -0800, Derrick Ryalls wrote I am running FreeBSD 5.3 Release on a AMD Athlon 2800+ with Linux compatibility installed. I have just installed Linux-EnemyTerritory from ports and I tried to run it: ./et in /usr/compat/linux/usr/games/et . I then get this error message: ...loading libGL.so.1: QGL_Init: dlopen libGL.so.1 failed: libGL.so.1: cannot open shared object file: No such file or directory failed - CL_Shutdown - RE_Shutdown( 1 ) --- - CL_Shutdown - --- Sys_Error: GLimp_Init() - could not load OpenGL subsystem I have located libGL.so.1 in my /usr/X11R6/lib/ . I read the handbook page on Linux Compatibilty, however that didn't seem to help. Any assistance would be greatly appreciated. I'm not sure where it searches for its required libs. You can try making an symbolic link to /usr/compat/linux/usr/lib if it's not there. Or perhaps /usr/compat/linux/usr/local/lib. Jorn Can you run an OpenGL screen saver? I am guessing that OpenGL is not enabled for your video for whatever reason. You might check your config file. That doesn't matter too much AFAIK. I've been running Gentoo for quite a while, and I could run OpenGL screen savers without a problem, but once I started UT2004 or any other OpenGL app it said that it couldn't find the libs. And I don't think it's platform dependant. Correct me if I'm wrong, of course :) Jorn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Enemy-Territory for Linux run Problem on FreeBSD 5.3 Release
I run ET on 5.2.1-RELEASE and didn't have to do anything else than installing nvidia-driver and downloading the game (linux version) Jorn Argelo wrote: On Tue, 25 Jan 2005 18:20:26 -0800, Derrick Ryalls wrote I am running FreeBSD 5.3 Release on a AMD Athlon 2800+ with Linux compatibility installed. I have just installed Linux-EnemyTerritory from ports and I tried to run it: ./et in /usr/compat/linux/usr/games/et . I then get this error message: ...loading libGL.so.1: QGL_Init: dlopen libGL.so.1 failed: libGL.so.1: cannot open shared object file: No such file or directory failed - CL_Shutdown - RE_Shutdown( 1 ) --- - CL_Shutdown - --- Sys_Error: GLimp_Init() - could not load OpenGL subsystem I have located libGL.so.1 in my /usr/X11R6/lib/ . I read the handbook page on Linux Compatibilty, however that didn't seem to help. Any assistance would be greatly appreciated. I'm not sure where it searches for its required libs. You can try making an symbolic link to /usr/compat/linux/usr/lib if it's not there. Or perhaps /usr/compat/linux/usr/local/lib. Jorn Can you run an OpenGL screen saver? I am guessing that OpenGL is not enabled for your video for whatever reason. You might check your config file. That doesn't matter too much AFAIK. I've been running Gentoo for quite a while, and I could run OpenGL screen savers without a problem, but once I started UT2004 or any other OpenGL app it said that it couldn't find the libs. And I don't think it's platform dependant. Correct me if I'm wrong, of course :) Jorn ___ 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: Enemy-Territory for Linux run Problem on FreeBSD 5.3 Release
On Mon, 24 Jan 2005 18:04:56 -0500, Kevin Coles wrote Hello, I am running FreeBSD 5.3 Release on a AMD Athlon 2800+ with Linux compatibility installed. I have just installed Linux-EnemyTerritory from ports and I tried to run it: ./et in /usr/compat/linux/usr/games/et . I then get this error message: ...loading libGL.so.1: QGL_Init: dlopen libGL.so.1 failed: libGL.so.1: cannot open shared object file: No such file or directory failed - CL_Shutdown - RE_Shutdown( 1 ) --- - CL_Shutdown - --- Sys_Error: GLimp_Init() - could not load OpenGL subsystem I have located libGL.so.1 in my /usr/X11R6/lib/ . I read the handbook page on Linux Compatibilty, however that didn't seem to help. Any assistance would be greatly appreciated. I'm not sure where it searches for its required libs. You can try making an symbolic link to /usr/compat/linux/usr/lib if it's not there. Or perhaps /usr/compat/linux/usr/local/lib. Jorn Thanks, Kevin Coles ___ 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: Enemy-Territory for Linux run Problem on FreeBSD 5.3 Release
I am running FreeBSD 5.3 Release on a AMD Athlon 2800+ with Linux compatibility installed. I have just installed Linux-EnemyTerritory from ports and I tried to run it: ./et in /usr/compat/linux/usr/games/et . I then get this error message: ...loading libGL.so.1: QGL_Init: dlopen libGL.so.1 failed: libGL.so.1: cannot open shared object file: No such file or directory failed - CL_Shutdown - RE_Shutdown( 1 ) --- - CL_Shutdown - --- Sys_Error: GLimp_Init() - could not load OpenGL subsystem I have located libGL.so.1 in my /usr/X11R6/lib/ . I read the handbook page on Linux Compatibilty, however that didn't seem to help. Any assistance would be greatly appreciated. I'm not sure where it searches for its required libs. You can try making an symbolic link to /usr/compat/linux/usr/lib if it's not there. Or perhaps /usr/compat/linux/usr/local/lib. Jorn Can you run an OpenGL screen saver? I am guessing that OpenGL is not enabled for your video for whatever reason. You might check your config file. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with nss_ldap in FreeBSD 5.3-RELEASE/AMD64
Hey All, Not entirely sure which list this should be sent to, so I figured sending to the general list would be a good start. If there's a more appropriate list, could someone kindly reply and direct me as to who else may be better able to help solve or at least point me in the right direction to solve this problem myself. - Thanks. That said, here goes; I am apparently encountering an overflow of sorts with nss_ldap on FreeBSD: - Currently running OpenLDAP server, to store all local usernames/passwords/groups/shells/homedirs info. The accounts are shared between the system on the FreeBSD side using posixAccount attributes, and on the Windows side using sambaSamAccount attributes. We are using the FreeBSD port of LAM to create/modify/manage users and groups internally through a web-based interface running on Apache/php. Further details, including version specifics, etc will follow, just prefer to give you an idea of the problem we're having before wasting your time reading all the really specific stuff. Here's the problem, only a few selected usernames (4 out of about 190 or so), root cannot do a 'cd ~username'. This seems to cause issues with samba, and the list just goes on from there. What happens when one logged in as root types in the command 'cd ~username', is apparently an overflow of some sort which leaves one connected to the LDAP session, a simple [CRTL]+D releases one back to console. This same condition occurs when ANY user (not just root) attempts to cd to one of these 4 user directories; what troubles me most, is this happens regardless of permission issues to the filesystem, as it is apparently during the username lookup that it happens, to what extent the open session can allow someone access as an intruder of sorts I do not know - but nonetheless fear as an administrator, that this could be a security risk as well. I have attached a UNICODE txt file of a session which shows what one gets on the console when one attempts to 'cd ~USERNAME', where 'USERNAME' was edited removing the original username. Here's what I've tried to resolve the issue: First tried re-creating the user objects in the LDAP tree, failing that, I removed them, and re-created them with different UID numbers; essentially making them different objects with different distinctive names (DN's) in the database - nothing, same problem. Removed and re-created the physical directory entries on the disk as well, including proper ownership and permissions each time I changed the associated entry in the LDAP tree as well - even tried changing where/which disk the homedir was physically stored on. Lastly, I tried removing the entire LDAP database, and restoring FIRST the troublesome users only - same problem still. Added in the rest of the users via an LDIF export (backup of db before I toasted it) - still same problem. I figure spelling can't really be an issue; all usernames here follow the same convention (first letter of first name, followed by first 7 characters of last name, no numeric nor punctual characters of any sort). All four usernames are phonetically distinct and do not share any alphabetic pattern whatsoever either (I'd prefer not to send them out to the general list, as this machine is currently in production, and given the nature of what these accounts are causing I'd prefer not opening up a whole new security risk here). More Detailed Information Follows: -- FreeBSD 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 5 03:50:01 UTC 2004 amd64 OpenLDAP nss_ldap pam_ldap installed from ports-tree, using versions as follows (pkg_info -a reports: openldap-client-2.2.15, openldap-server-2.2.15, pam_ldap-1.7.1_1, nss_ldap-1.204_5) Samba Version Samba-3.0.8, compiled with LDAP SAM support, acting as PDC for Win2K/WinXP Clients Still running GENERIC kernel (intent upon eventually getting around to making a new one, removing a lot of debugging and what-not once all is up and running well for a boost in performance). The machine is an AMD Opteron 146-based system, with 2GB ECC registered memory, (dual capable board, eventually going to go with dual 246 Opterons when we can take them from a workstation and upgrade the workstation to faster cpus). Using WDC RAID Edition S-ATA 250GB Drives, the on-board Broadcom GigE controllers (2), and on-board ATI video controller. The drives are configured in a RAID 5 array, attached each to an independent channel on a 3Ware Escalade 9500 series S-ATA controller, for a total of 705GB and change storage across 4 partitions (2GB /, 10GB /usr, 40GB /var, rest as /server). Attached is a copy of an (edited for username) session which details what happens when this error occurs. There are no errors reported in the OpenLDAP nor the system/auth logs to give you, but if anything else is needed please don't hesitate to ask
Problem with nss_ldap in FreeBSD 5.3-RELEASE/AMD64 (2nd edition)
Hey All, - Sorry, forgot the attachement, same msg as earlier follows: Not entirely sure which list this should be sent to, so I figured sending to the general list would be a good start. If there's a more appropriate list, could someone kindly reply and direct me as to who else may be better able to help solve or at least point me in the right direction to solve this problem myself. - Thanks. That said, here goes; I am apparently encountering an overflow of sorts with nss_ldap on FreeBSD: - Currently running OpenLDAP server, to store all local usernames/passwords/groups/shells/homedirs info. The accounts are shared between the system on the FreeBSD side using posixAccount attributes, and on the Windows side using sambaSamAccount attributes. We are using the FreeBSD port of LAM to create/modify/manage users and groups internally through a web-based interface running on Apache/php. Further details, including version specifics, etc will follow, just prefer to give you an idea of the problem we're having before wasting your time reading all the really specific stuff. Here's the problem, only a few selected usernames (4 out of about 190 or so), root cannot do a 'cd ~username'. This seems to cause issues with samba, and the list just goes on from there. What happens when one logged in as root types in the command 'cd ~username', is apparently an overflow of some sort which leaves one connected to the LDAP session, a simple [CRTL]+D releases one back to console. This same condition occurs when ANY user (not just root) attempts to cd to one of these 4 user directories; what troubles me most, is this happens regardless of permission issues to the filesystem, as it is apparently during the username lookup that it happens, to what extent the open session can allow someone access as an intruder of sorts I do not know - but nonetheless fear as an administrator, that this could be a security risk as well. I have attached a UNICODE txt file of a session which shows what one gets on the console when one attempts to 'cd ~USERNAME', where 'USERNAME' was edited removing the original username. Here's what I've tried to resolve the issue: First tried re-creating the user objects in the LDAP tree, failing that, I removed them, and re-created them with different UID numbers; essentially making them different objects with different distinctive names (DN's) in the database - nothing, same problem. Removed and re-created the physical directory entries on the disk as well, including proper ownership and permissions each time I changed the associated entry in the LDAP tree as well - even tried changing where/which disk the homedir was physically stored on. Lastly, I tried removing the entire LDAP database, and restoring FIRST the troublesome users only - same problem still. Added in the rest of the users via an LDIF export (backup of db before I toasted it) - still same problem. I figure spelling can't really be an issue; all usernames here follow the same convention (first letter of first name, followed by first 7 characters of last name, no numeric nor punctual characters of any sort). All four usernames are phonetically distinct and do not share any alphabetic pattern whatsoever either (I'd prefer not to send them out to the general list, as this machine is currently in production, and given the nature of what these accounts are causing I'd prefer not opening up a whole new security risk here). More Detailed Information Follows: -- FreeBSD 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 5 03:50:01 UTC 2004 amd64 OpenLDAP nss_ldap pam_ldap installed from ports-tree, using versions as follows (pkg_info -a reports: openldap-client-2.2.15, openldap-server-2.2.15, pam_ldap-1.7.1_1, nss_ldap-1.204_5) Samba Version Samba-3.0.8, compiled with LDAP SAM support, acting as PDC for Win2K/WinXP Clients Still running GENERIC kernel (intent upon eventually getting around to making a new one, removing a lot of debugging and what-not once all is up and running well for a boost in performance). The machine is an AMD Opteron 146-based system, with 2GB ECC registered memory, (dual capable board, eventually going to go with dual 246 Opterons when we can take them from a workstation and upgrade the workstation to faster cpus). Using WDC RAID Edition S-ATA 250GB Drives, the on-board Broadcom GigE controllers (2), and on-board ATI video controller. The drives are configured in a RAID 5 array, attached each to an independent channel on a 3Ware Escalade 9500 series S-ATA controller, for a total of 705GB and change storage across 4 partitions (2GB /, 10GB /usr, 40GB /var, rest as /server). Attached is a copy of an (edited for username) session which details what happens when this error occurs. There are no errors reported in the OpenLDAP nor the system/auth logs to give you
Enemy-Territory for Linux run Problem on FreeBSD 5.3 Release
Hello, I am running FreeBSD 5.3 Release on a AMD Athlon 2800+ with Linux compatibility installed. I have just installed Linux-EnemyTerritory from ports and I tried to run it: ./et in /usr/compat/linux/usr/games/et . I then get this error message: ...loading libGL.so.1: QGL_Init: dlopen libGL.so.1 failed: libGL.so.1: cannot open shared object file: No such file or directory failed - CL_Shutdown - RE_Shutdown( 1 ) --- - CL_Shutdown - --- Sys_Error: GLimp_Init() - could not load OpenGL subsystem I have located libGL.so.1 in my /usr/X11R6/lib/ . I read the handbook page on Linux Compatibilty, however that didn't seem to help. Any assistance would be greatly appreciated. Thanks, Kevin Coles ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Enemy-Territory for Linux run Problem on FreeBSD 5.3 Release
well, you might wanna try to install the following port: graphics/linux_mesa3 i dunno if FreeBSD has such a thing, for now im using the debian.org package search interface for finding which library is part of which archive... Greetings Oliver Leitner Technical Staff http://www.shells.at On Tuesday 25 January 2005 00:04, Kevin Coles wrote: Hello, I am running FreeBSD 5.3 Release on a AMD Athlon 2800+ with Linux compatibility installed. I have just installed Linux-EnemyTerritory from ports and I tried to run it: ./et in /usr/compat/linux/usr/games/et . I then get this error message: ...loading libGL.so.1: QGL_Init: dlopen libGL.so.1 failed: libGL.so.1: cannot open shared object file: No such file or directory failed - CL_Shutdown - RE_Shutdown( 1 ) --- - CL_Shutdown - --- Sys_Error: GLimp_Init() - could not load OpenGL subsystem I have located libGL.so.1 in my /usr/X11R6/lib/ . I read the handbook page on Linux Compatibilty, however that didn't seem to help. Any assistance would be greatly appreciated. Thanks, Kevin Coles ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- By reading this mail you agree to the following: using or giving out the email address and any other info of the author of this email is strictly forbidden. By acting against this agreement the author of this mail will take possible legal actions against the abuse. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: System Freeze with freebsd-5.3-Release-p5
On Mon, Jan 17, 2005 at 03:38:09PM +0800, Lin, Tsung Ching wrote: I had recompiled the kernel without those kern options. if I enable both nis client and the second network interface, the console shows bge1: gigabit link up and then the system freezes without any log. I don't think you posted a dmesg yet. Can you please do so? Kris pgp1zZ60CWC7m.pgp Description: PGP signature
Re: System Freeze with freebsd-5.3-Release-p5
On Mon, Jan 17, 2005 at 03:38:09PM +0800, Lin, Tsung Ching wrote: I had recompiled the kernel without those kern options. if I enable both nis client and the second network interface, the console shows bge1: gigabit link up and then the system freezes without any log. OK, I asked a colleague, who told me that the IBM xseries 335 is known to have buggy ACPI support, which causes this problem. You could try to disable ACPI, but this also may not work. Kris pgpsm570kGz0O.pgp Description: PGP signature
System Freeze with freebsd-5.3-Release-p5
hi everyone, I want to upgrade the mail server from 4.10 to 5.3 on IBM xSeries 335. If I enable nis client and config the second network interface, the system alwayse freeze without any log. If I boot the system first, then config the second network interface, the system still freezes. If I only eanble nis client or network interface, the system is ok. how do I solve this problem?? thank you very much. -- Lin, Tsung Ching [EMAIL PROTECTED] Institute of Information Science, Academia Sinica ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: System Freeze with freebsd-5.3-Release-p5
On Mon, Jan 17, 2005 at 10:32:38AM +0800, Lin, Tsung Ching wrote: hi everyone, I want to upgrade the mail server from 4.10 to 5.3 on IBM xSeries 335. If I enable nis client and config the second network interface, the system alwayse freeze without any log. If I boot the system first, then config the second network interface, the system still freezes. If I only eanble nis client or network interface, the system is ok. how do I solve this problem?? thank you very much. Please specify more details about your system and its configuration. Kris pgp4GDarF61Rl.pgp Description: PGP signature
Re: System Freeze with freebsd-5.3-Release-p5
Kris Kennaway wrote: On Mon, Jan 17, 2005 at 10:32:38AM +0800, Lin, Tsung Ching wrote: hi everyone, I want to upgrade the mail server from 4.10 to 5.3 on IBM xSeries 335. If I enable nis client and config the second network interface, the system alwayse freeze without any log. If I boot the system first, then config the second network interface, the system still freezes. If I only eanble nis client or network interface, the system is ok. how do I solve this problem?? thank you very much. Please specify more details about your system and its configuration. Kris Here ya go: http://www-1.ibm.com/servers/eserver/xseries/xcampaigns/campaign1_flat.html -- Best regards, Chris A pat on the back is only a few inches from a kick in the pants. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: System Freeze with freebsd-5.3-Release-p5
On Sun, Jan 16, 2005 at 08:42:48PM -0600, Chris wrote: Kris Kennaway wrote: On Mon, Jan 17, 2005 at 10:32:38AM +0800, Lin, Tsung Ching wrote: hi everyone, I want to upgrade the mail server from 4.10 to 5.3 on IBM xSeries 335. If I enable nis client and config the second network interface, the system alwayse freeze without any log. If I boot the system first, then config the second network interface, the system still freezes. If I only eanble nis client or network interface, the system is ok. how do I solve this problem?? thank you very much. Please specify more details about your system and its configuration. Kris Here ya go: http://www-1.ibm.com/servers/eserver/xseries/xcampaigns/campaign1_flat.html I don't see a dmesg, kernel configuration or /etc/rc.conf file at that URL :-) Kris pgpOlmA5wnVZx.pgp Description: PGP signature
Re: System Freeze with freebsd-5.3-Release-p5
Kris Kennaway wrote: On Sun, Jan 16, 2005 at 08:42:48PM -0600, Chris wrote: Kris Kennaway wrote: On Mon, Jan 17, 2005 at 10:32:38AM +0800, Lin, Tsung Ching wrote: hi everyone, I want to upgrade the mail server from 4.10 to 5.3 on IBM xSeries 335. If I enable nis client and config the second network interface, the system alwayse freeze without any log. If I boot the system first, then config the second network interface, the system still freezes. If I only eanble nis client or network interface, the system is ok. how do I solve this problem?? thank you very much. Please specify more details about your system and its configuration. Kris Here ya go: http://www-1.ibm.com/servers/eserver/xseries/xcampaigns/campaign1_flat.html I don't see a dmesg, kernel configuration or /etc/rc.conf file at that URL :-) Kris Yer right - was just helping him along - at least ya got an idea on the the type of hardware -- Best regards, Chris A pat on the back is only a few inches from a kick in the pants. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: System Freeze with freebsd-5.3-Release-p5
2005-01-16 20:49 -0600Chris Kris Kennaway wrote: On Sun, Jan 16, 2005 at 08:42:48PM -0600, Chris wrote: Kris Kennaway wrote: On Mon, Jan 17, 2005 at 10:32:38AM +0800, Lin, Tsung Ching wrote: hi everyone, I want to upgrade the mail server from 4.10 to 5.3 on IBM xSeries 335. If I enable nis client and config the second network interface, the system alwayse freeze without any log. If I boot the system first, then config the second network interface, the system still freezes. If I only eanble nis client or network interface, the system is ok. how do I solve this problem?? thank you very much. Please specify more details about your system and its configuration. Kris Here ya go: http://www-1.ibm.com/servers/eserver/xseries/xcampaigns/campaign1_flat.html I don't see a dmesg, kernel configuration or /etc/rc.conf file at that URL :-) Kris Yer right - was just helping him along - at least ya got an idea on the the type of hardware sorry, I forget to attach the configuration files. here they are. :) # rc.conf hostname=ccstest.iis.sinica.edu.tw nisdomainname=isd1 usbd_enable=YES defaultrouter=140.109.20.1 ifconfig_bge0=inet 140.109.20.9 netmask 255.255.255.0 #ifconfig_bge1=inet 192.168.20.9 netmask 255.255.255.0 firewall_enable=YES # Set to YES to enable firewall functionality firewall_type=/etc/ipfw.conf # Firewall type (see /etc/rc.firewall) rpcbind_enable=YES nis_client_enable=YES nfs_client_enable=YES nfs_server_enable=YES rpc_lockd_enable=YES rpc_statd_enable=YES sshd_enable=YES inetd_enable=YES ntpd_enable=YES # # KERNCONF include SMP ident IBM-XSERIES-335 options MROUTING# Multicast routing options PIM # Protocol Independent Multicast options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #enable logging to syslogd(8) #options IPFIREWALL_VERBOSE_LIMIT=100#limit verbosity #options IPFIREWALL_DEFAULT_TO_ACCEPT#allow everything by default options IPFIREWALL_FORWARD #packet destination changes options IPV6FIREWALL#firewall for IPv6 options IPV6FIREWALL_VERBOSE #options IPV6FIREWALL_VERBOSE_LIMIT=100 #options IPV6FIREWALL_DEFAULT_TO_ACCEPT options IPDIVERT#divert sockets options IPSTEALTH #support for stealth forwarding options TCPDEBUG options MBUF_STRESS_TEST options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN #optionsTCP_SIGNATURE #include support for RFC 2385 options DUMMYNET options BRIDGE options ZERO_COPY_SOCKETS -- Lin, Tsung Ching [EMAIL PROTECTED] Institute of Information Science, Academia Sinica ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: System Freeze with freebsd-5.3-Release-p5
On Mon, Jan 17, 2005 at 11:01:27AM +0800, Lin, Tsung Ching wrote: # # KERNCONF include SMP ident IBM-XSERIES-335 options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #enable logging to syslogd(8) #options IPFIREWALL_VERBOSE_LIMIT=100#limit verbosity #options IPFIREWALL_DEFAULT_TO_ACCEPT#allow everything by default options IPFIREWALL_FORWARD #packet destination changes options IPV6FIREWALL#firewall for IPv6 options IPV6FIREWALL_VERBOSE #options IPV6FIREWALL_VERBOSE_LIMIT=100 #options IPV6FIREWALL_DEFAULT_TO_ACCEPT options IPDIVERT#divert sockets options IPSTEALTH #support for stealth forwarding options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN #optionsTCP_SIGNATURE #include support for RFC 2385 options DUMMYNET options BRIDGE options ZERO_COPY_SOCKETS Some of these are suspicious: options MBUF_STRESS_TEST This is designed to induce failures in buggy code. You might be provoking a problem you wouldn't otherwise see in normal operation. options TCPDEBUG This is undocumented i.e. you probably don't want it. options MROUTING# Multicast routing options PIM # Protocol Independent Multicast These two are not widely used, so it's conceivable that they may be buggy. Take them all out (if you need the last 2, still try without them to see if the problem is there). Kris pgp2uaHTChnox.pgp Description: PGP signature
Re: System Freeze with freebsd-5.3-Release-p5
Lin, Tsung Ching wrote: hi everyone, I want to upgrade the mail server from 4.10 to 5.3 on IBM xSeries 335. If I enable nis client and config the second network interface, the system alwayse freeze without any log. If I boot the system first, then config the second network interface, the system still freezes. If I only eanble nis client or network interface, the system is ok. how do I solve this problem?? thank you very much. Hey ... Wait a minute Note the subject... p5 ??? -- Best regards, Chris A large system, produced by expanding the dimensions of a smaller system, does not behave like the smaller system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: System Freeze with freebsd-5.3-Release-p5
2005-01-16 19:10 -0800Kris Kennaway On Mon, Jan 17, 2005 at 11:01:27AM +0800, Lin, Tsung Ching wrote: # # KERNCONF include SMP ident IBM-XSERIES-335 options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #enable logging to syslogd(8) #options IPFIREWALL_VERBOSE_LIMIT=100#limit verbosity #options IPFIREWALL_DEFAULT_TO_ACCEPT#allow everything by default options IPFIREWALL_FORWARD #packet destination changes options IPV6FIREWALL#firewall for IPv6 options IPV6FIREWALL_VERBOSE #options IPV6FIREWALL_VERBOSE_LIMIT=100 #options IPV6FIREWALL_DEFAULT_TO_ACCEPT options IPDIVERT#divert sockets options IPSTEALTH #support for stealth forwarding options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN #optionsTCP_SIGNATURE #include support for RFC 2385 options DUMMYNET options BRIDGE options ZERO_COPY_SOCKETS Some of these are suspicious: options MBUF_STRESS_TEST This is designed to induce failures in buggy code. You might be provoking a problem you wouldn't otherwise see in normal operation. options TCPDEBUG This is undocumented i.e. you probably don't want it. options MROUTING# Multicast routing options PIM # Protocol Independent Multicast These two are not widely used, so it's conceivable that they may be buggy. Take them all out (if you need the last 2, still try without them to see if the problem is there). Kris hi I had recompiled the kernel without those kern options. if I enable both nis client and the second network interface, the console shows bge1: gigabit link up and then the system freezes without any log. -- Lin, Tsung Ching [EMAIL PROTECTED] Institute of Information Science, Academia Sinica ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sil 3114 RAID controller issues with FreeBSD 5.3 Release AMD-64 - and Promise RAID controllers???
Hi, Last Friday I ranted: In this case, time IS money, so that's why I'm trying to convince my client to better spend that money (and my time) on simply buying a supported hardware RAID controller, which really is a win-win situation for both my client and myself. However, somehow I've not yet been able to drive that argument home, so who knows...:/ Well, eureka, I did it! :) That is... I managed to convince the client to go hardware RAID. ;) They have a preference for the following controller: Promise FAST Trak S150TX4 But.. As far as I gather from the supported hardware list (fbsd 5.3, amd-64) at: http://www.freebsd.org/releases/5.3R/hardware-amd64.html#DISK It looks like this controller is not supported. :( To further compound matters, checking the docs on the controller suggests that, again, this is basically a software RAID solution (no CPU, no on-board memory, and a 66MHz PCI 2.2 32-bit interface): nice to complement their otherwise blazingly fast 64-bit AMD machine, duh! :((( Oh well, again I made a very strong suggestion to buy the Adaptec 2200s U320 SCSI RAID controller, but we'll see... :) Meanwhile, does anyone know of a good hardware SATA RAID controller capable of supporting RAID 10, and which is properly supported by FreeBSD 5.3 (amd64)? Any experiences? Any do's and dont's? Tnx cheerz! Olafo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sil 3114 RAID controller issues with FreeBSD 5.3 Release AMD-64 - and Promise RAID controllers???
On Mon, Jan 10, 2005 at 02:26:34PM +0100, Olaf Greve wrote: Hi, Last Friday I ranted: In this case, time IS money, so that's why I'm trying to convince my client to better spend that money (and my time) on simply buying a supported hardware RAID controller, which really is a win-win situation for both my client and myself. However, somehow I've not yet been able to drive that argument home, so who knows...:/ Well, eureka, I did it! :) That is... I managed to convince the client to go hardware RAID. ;) They have a preference for the following controller: Promise FAST Trak S150TX4 But.. As far as I gather from the supported hardware list (fbsd 5.3, amd-64) at: http://www.freebsd.org/releases/5.3R/hardware-amd64.html#DISK It looks like this controller is not supported. :( To further compound matters, checking the docs on the controller suggests that, again, this is basically a software RAID solution (no CPU, no on-board memory, and a 66MHz PCI 2.2 32-bit interface): nice to complement their otherwise blazingly fast 64-bit AMD machine, duh! :((( Oh well, again I made a very strong suggestion to buy the Adaptec 2200s U320 SCSI RAID controller, but we'll see... :) Meanwhile, does anyone know of a good hardware SATA RAID controller capable of supporting RAID 10, and which is properly supported by FreeBSD 5.3 (amd64)? Any experiences? Any do's and dont's? Hi, I'am runnig some 3ware Storage Controllers on 5.2.1 and 5.3 on i386 Hardware. They work well. I use a 3ware 3W-8500-8 disk controller with 4 disks in Raid 5 Mode and some 3ware 3W-7006-2 disk controller with 2 disks in Raid 1 Mode. So far no problems with them. They react well on HotSwaps of defectiv disks (had one diskfailure allready). Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | Privat: [EMAIL PROTECTED] | auf Anfrage/ Germany||on request pgpxQ7cH4nKo0.pgp Description: PGP signature
Sil 3114 RAID controller issues with FreeBSD 5.3 Release AMD-64
Hi, A client of mine asked me to install their AMD-64 machine as a MySQL database server. Totally against my strong suggestion to use a proper SCSI hardware RAID 10 solution (or at least a hardware SATA RAID solution), they insist on using the internal Sil 3114 software RAID controller in RAID 1 mode. Now, this 'cost reduction' from them backfires, as FreeBSD 5.3 Release AMD-64 does not properly recognise this controller. First, it locks up when booting with ACPI enabled (easily fixable by either disabling ACPI in the BIOS, or by booting without ACPI), then the bootstrap loader first seemingly does recognise the RAID 1 array (at least it states something to the effect of Drive C from BIOS..., but when the installation CD-ROM has booted, lo and behold! It does not see both drives as an array, but as separate drives! I looked around a bit on the Internet, and seemingly this issue started to occur around mid june last year with FreeBSD 5.3 versions for these type of Silicon RAID controllers. Now, of course I am still trying to get my client to do it properly and forget this el-cheapo RAID solution and simply buy a hardware RAID controller, but if I can't succeed in convincing them, I'd really like to enable the RAID array of this controller after all. Does anyone know how this can be achieved? Is it possible to patch the device driver once FreeBSD is installed, and somehow get FreeBSD to build the RAID array? Thanks in advance, and cheers! Olafo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sil 3114 RAID controller issues with FreeBSD 5.3 Release AMD-64
On Fri, Jan 07, 2005 at 01:16:35PM +0100, Olaf Greve wrote: Hi, A client of mine asked me to install their AMD-64 machine as a MySQL database server. Totally against my strong suggestion to use a proper SCSI hardware RAID 10 solution (or at least a hardware SATA RAID solution), they insist on using the internal Sil 3114 software RAID controller in RAID 1 mode. Now, this 'cost reduction' from them backfires, as FreeBSD 5.3 Release AMD-64 does not properly recognise this controller. First, it locks up when booting with ACPI enabled (easily fixable by either disabling ACPI in the BIOS, or by booting without ACPI), then the bootstrap loader first seemingly does recognise the RAID 1 array (at least it states something to the effect of Drive C from BIOS..., but when the installation CD-ROM has booted, lo and behold! It does not see both drives as an array, but as separate drives! I looked around a bit on the Internet, and seemingly this issue started to occur around mid june last year with FreeBSD 5.3 versions for these type of Silicon RAID controllers. Now, of course I am still trying to get my client to do it properly and forget this el-cheapo RAID solution and simply buy a hardware RAID controller, but if I can't succeed in convincing them, I'd really like to enable the RAID array of this controller after all. Does anyone know how this can be achieved? Is it possible to patch the device driver once FreeBSD is installed, and somehow get FreeBSD to build the RAID array? I don't think FreeBSD supports the SiI 3114 as a RAID controller, but only as a normal controller. All the RAID stuff for that controller is done in software anyway, but FreeBSD needs to know what format the BIOS uses for a RAID setup, and it doesn't. I guess you could set up a pure software RAID-1 solution using vinum, but not having done that myself I can't say for sure. See http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/vinum-vinum.html for information on how to use and setup vinum. -- Insert your favourite quote here. Erik Trulsson [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: Sil 3114 RAID controller issues with FreeBSD 5.3 Release AMD-64
Hi Erik, Thanks for your answer! I don't think FreeBSD supports the SiI 3114 as a RAID controller, but only as a normal controller. All the RAID stuff for that controller is done in software anyway, but FreeBSD needs to know what format the BIOS uses for a RAID setup, and it doesn't. Indeed that is what I also fear, hence my reluctance at having to spend much time trying to figure out a way to enable this controller for RAID purposes, whereas it is an -IMO- bad choice anyway to use this for their RAID strategy. :((( I guess you could set up a pure software RAID-1 solution using vinum, but not having done that myself I can't say for sure. See http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/vinum-vinum.html for information on how to use and setup vinum. Yes, that would probably be another option. Again it would have the same downside though: I've never done this before, so I'll have to spend time getting that going. In this case, time IS money, so that's why I'm trying to convince my client to better spend that money (and my time) on simply buying a supported hardware RAID controller, which really is a win-win situation for both my client and myself. However, somehow I've not yet been able to drive that argument home, so who knows...:/ Oh well, enough of this rant - surely someday they'll see the light. Until then, I'll just continue to scream in the desert. ;) Cheerz! Olafo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wine 20041201 on FreeBSD 5.3-RELEASE
On Wednesday 29 December 2004 12:05 am, Matthew Bluestone wrote: (I apologize for replying to jason henson rather than the list; either his reply-to was set individually, gmail doesn't correctly respect reply-to (though it seems to in other cases), or I made an error.) Some of my response to jason and his later reply are included. (I didn't think that was so clear from the page.) I applied the patch, rebuilt, and installed my kernel, and I continue to get the same error. [snip] # patch filename and got normal-looking messages about discarding junk headers and footers and applying patches in two spots. I checked the source file /usr/src/sys/vm/vm_mmap.c and found the appropriate sections updated. I had also edited a custom kernel config file in preparation for building a custom kernel anyway, and I did # cd /usr/src # make buildkernel KERNCONF=MYKERNELNAME # make installkernel KERNCONF=MYKERNELNAME (substituting the appropriate name, of course). The commands finished successfully, and I rebooted and got a functioning system without a hitch. Looks like you did the right patch command. [snip] Ok, first Kris responded to the thread with It also clearly states (in the followup) that the kernel patch is no longer needed. Sounds like what Kris was saying was you just needed to cvsup your ports system and not do the patch anymore. The wine-mmap.patch is no longer needed since that code has been #ifdef'd=20 out in the wine CVS. So you could just rm vm_mmap.c and cvsup your source then update your system and kernel. Depending on hold old your release is you should read UPDATING very carefully. As I said in my original post, my ports tree was updated the day before I tried all that (which is well after the bug is listed as being closed). Since I have apparently the latest port of wine and have tried both with and without the kernel patch, I'm at a loss. I thought this may be an issue with common enough components that somebody on this list might have encountered and solved the same problem. I figured that maybe I had misunderstood about the kernel patch no longer being needed; maybe it was merged into CURRENT, but I'd have to do it myself with my 5.3-RELEASE system. Incidentally, if I should *undo* this patch (I'm not a kernel hacker; it intuitively seems that messing with the virtual memory manager, esp. w/ code marked this is messy; somebody who knows what he's doing should fix it, could be a bad idea), I'd appreciate somebody's letting me know. Try emailing [EMAIL PROTECTED], he's the port maintainer for wine. I will also email gerald directly. Thank you. I have basically the same setup (5.3 patchlevel 2 and Wine 120104) and get the same error. However, strangely enough, the error shows up on some apps that actually run. I was able to run Mozilla's Sunbird calendar program with no apparent errors on-screen, but , if I start it from a terminal window I see the heap error, but it runs anyway... I looked at the vm_mmap.c in the latest sources and the patch would not apply, so I assume the code has been merged, but couldn't really verify that. I searched for some of the variables from the patch and they weren't in the file. So, now I'm really confused as to what needs to be done. -Jim Durham ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wine 20041201 on FreeBSD 5.3-RELEASE
(I apologize for replying to jason henson rather than the list; either his reply-to was set individually, gmail doesn't correctly respect reply-to (though it seems to in other cases), or I made an error.) Some of my response to jason and his later reply are included. (I didn't think that was so clear from the page.) I applied the patch, rebuilt, and installed my kernel, and I continue to get the same error. [snip] # patch filename and got normal-looking messages about discarding junk headers and footers and applying patches in two spots. I checked the source file /usr/src/sys/vm/vm_mmap.c and found the appropriate sections updated. I had also edited a custom kernel config file in preparation for building a custom kernel anyway, and I did # cd /usr/src # make buildkernel KERNCONF=MYKERNELNAME # make installkernel KERNCONF=MYKERNELNAME (substituting the appropriate name, of course). The commands finished successfully, and I rebooted and got a functioning system without a hitch. Looks like you did the right patch command. [snip] Ok, first Kris responded to the thread with It also clearly states (in the followup) that the kernel patch is no longer needed. Sounds like what Kris was saying was you just needed to cvsup your ports system and not do the patch anymore. The wine-mmap.patch is no longer needed since that code has been #ifdef'd=20 out in the wine CVS. So you could just rm vm_mmap.c and cvsup your source then update your system and kernel. Depending on hold old your release is you should read UPDATING very carefully. As I said in my original post, my ports tree was updated the day before I tried all that (which is well after the bug is listed as being closed). Since I have apparently the latest port of wine and have tried both with and without the kernel patch, I'm at a loss. I thought this may be an issue with common enough components that somebody on this list might have encountered and solved the same problem. I figured that maybe I had misunderstood about the kernel patch no longer being needed; maybe it was merged into CURRENT, but I'd have to do it myself with my 5.3-RELEASE system. Incidentally, if I should *undo* this patch (I'm not a kernel hacker; it intuitively seems that messing with the virtual memory manager, esp. w/ code marked this is messy; somebody who knows what he's doing should fix it, could be a bad idea), I'd appreciate somebody's letting me know. Try emailing [EMAIL PROTECTED], he's the port maintainer for wine. I will also email gerald directly. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wine 20041201 on FreeBSD 5.3-RELEASE
On Mon, Dec 27, 2004 at 05:17:18AM +, jason henson wrote: On 12/26/04 23:13:19, Matthew Bluestone wrote: I am running FreeBSD 5.3-RELEASE, Xorg 6.8.1 (portupgraded today), and KDE 3.3.3 (portupgraded today). My ports tree was updated yesterday. I am trying to run Wine, and I have the 20041201 port. The release notes say that it now runs under FreeBSD 5.3. While Wine's doc suggests that a kernel patch may be necessary, the discussion on this at http://www.freebsd.org/cgi/query-pr.cgi?pr=73092 suggests that that is not the case and that Wine itself has been patched. Incidentally, I am only bothering with all this in order to run the Party Poker client, which is listed on winehq as running (http://appdb.winehq.org/appview.php?appId=1567;whq_appdb=acc45b9fbc40a720bb99098126f77753) http://www.freebsd.org/cgi/query-pr.cgi?pr=73092 clearly states there were 2 patches to get wine running. One to wine and one to bsd. It also clearly states (in the followup) that the kernel patch is no longer needed. To the OP: You should raise questions about third party ports with the port maintainer, or the software authors. Kris pgpy3tochXrFj.pgp Description: PGP signature
Wine 20041201 on FreeBSD 5.3-RELEASE
I am running FreeBSD 5.3-RELEASE, Xorg 6.8.1 (portupgraded today), and KDE 3.3.3 (portupgraded today). My ports tree was updated yesterday. I am trying to run Wine, and I have the 20041201 port. The release notes say that it now runs under FreeBSD 5.3. While Wine's doc suggests that a kernel patch may be necessary, the discussion on this at http://www.freebsd.org/cgi/query-pr.cgi?pr=73092 suggests that that is not the case and that Wine itself has been patched. Incidentally, I am only bothering with all this in order to run the Party Poker client, which is listed on winehq as running (http://appdb.winehq.org/appview.php?appId=1567;whq_appdb=acc45b9fbc40a720bb99098126f77753) I successfully did # make and # make install on the wine port, and I have set up a link to a directory that functions as c:, the subdirectories within it, and the ~/.wine/config file as suggested in the documentation. wineserver runs, but my Windows application crashes, as follows: - wine PartyPokerSetup.exe fixme:file:get_default_drive_device auto detection of DOS devices not supported on this platform fixme:ntdll:NtQueryVolumeInformationFile device info not properly supported on this platform err:heap:HEAP_CreateSystemHeap system heap base address 0x8000 not available fixme:ntdll:NtQueryVolumeInformationFile device info not properly supported on this platform err:heap:HEAP_CreateSystemHeap system heap base address 0x8000 not available === [EMAIL PROTECTED] (/dev/ttyp3) ~/.wine/wine-c/Program Files 70 - err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 fixme:ntdll:NtQueryVolumeInformationFile device info not properly supported on this platform err:heap:HEAP_CreateSystemHeap system heap base address 0x8000 not available ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wine 20041201 on FreeBSD 5.3-RELEASE
On 12/26/04 23:13:19, Matthew Bluestone wrote: I am running FreeBSD 5.3-RELEASE, Xorg 6.8.1 (portupgraded today), and KDE 3.3.3 (portupgraded today). My ports tree was updated yesterday. I am trying to run Wine, and I have the 20041201 port. The release notes say that it now runs under FreeBSD 5.3. While Wine's doc suggests that a kernel patch may be necessary, the discussion on this at http://www.freebsd.org/cgi/query-pr.cgi?pr=73092 suggests that that is not the case and that Wine itself has been patched. Incidentally, I am only bothering with all this in order to run the Party Poker client, which is listed on winehq as running (http://appdb.winehq.org/appview.php?appId=1567;whq_appdb=acc45b9fbc40a720bb99098126f77753) http://www.freebsd.org/cgi/query-pr.cgi?pr=73092 clearly states there were 2 patches to get wine running. One to wine and one to bsd. You'll have to pacth your system with the attached patch. The patch is for src/sys/vmvm_mmap.c. The one on stable is dated Sun Nov 28 20:52:16 2004 UTC, the patch in the pr listes Wed Aug 18 21:31:13 2004. The port will handle the one on wine, you got the other until it is merged. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems with nge driver on FreeBSD 5.3-RELEASE i386
I am continuing to have problems with the nge driver on FreeBSD 5.3-RELEASE. I have already posted the necessary information. In summary, the OS panics and dies when there is any traffic load on the nic. I have experienced this on IDS systems that are just monitoring AND just recently on 2 file/web servers. I have a few questions: 1. What changed in FreeBSD 5.3-RELEASE that is causing the nge to crash the OS? Can it be changed back? 5.2.1 worked without crashing. 2. How can I get some attention to this problem? I am not the only person having this problem. I've posted a few messages and have not recieved ANY response. 3. Is this the right list for this question? If it is, how do I get some visibility on this? So far, my only workaround is to run OpenBSD 3.6. I *could* roll back to 5.2.1 but that's ignoring the problem. Thanks for whatever help anyone can provide. If you want me to repost the panic message, I can. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
SKYPE problems -- FreeBSD 5.3-RELEASE-p2
Hi, I am trying to install skype im my machine using ports. I did a cvsup procedure and now I am with 5.3-RELEASE-p2. The problem is that I cannot listen or talk to the remote person. I am using a sound blaster Live! board. phantor# dmesg | grep pcm0 pcm0: Creative EMU10K1 port 0x8800-0x881f irq 16 at device 12.0 on pci0 pcm0: SigmaTel STAC9708/11 AC97 Codec phantor# cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: pcm0: Creative EMU10K1 at io 0x8800 irq 16 kld snd_emu10k1 (4p/3r/0v channels duplex default) Looks like OK. I can listen to CD and mp3 files and I can REC using my MIC. What can I do to solve it ? I have to apply a patch in the kernel ? Or I have to use CURRENT ? Thanks a lot Giuliano ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
nvidia drivers do not want to work Sony-Vaio PCG-GRT100 FreeBSD 5.3 Release
Dear FreeBSD users, I tried and tried and tried again to make Nvidia Drivers work on my Laptop(Sony-Vaio PCG-GRT100), with Release 5.3. I followed all the instrunctions in the README. I am sending you my /boot/loader.conf /boot/defaults/loader.conf kernel-config: SONY-VAIO-NVIDIA my xorg.conf, my Xorg.0.log my kldstat output. you can find averything in the attached tarball! Any ideas? Thank you in advance! Drosos.___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 5.3-RELEASE kernel boot problems
First the system specs: * Motherboard: SuperMicro 370SED (manuf. in 2000; see [1]) * CPU: Intel Pentium III 933 MHz * RAM: 384 MB (128 MB PC100; 256 MB PC133) * network: * Linksys LNE100TX Etherfast 10/100 (device dc0) * Linksys LNE100TX Etherfast 10/100 (device dc1; unused for now) * video: integrated * storage: * built-in primary IDE controller * primary master: 24x CD-ROM (unknown manuf.) * built-in secondary IDE controller: disabled in BIOS * Maxtor Ultra/ATA 100 PCI IDE controller: * primary master: Maxtor 80 GB ATA/133 DiamondMax Plus 9 (new) using entire disk for FreeBSD slice; geometry is OK. partitions: ad4s1a150 MB / ad4s1b768 MB swap ad4s4d8 GB/var ad4s1e7 GB/usr ad4s1f 61 GB/milo (misc) * primary slave: Maxtor 60 GB ATA/100 (DiamondMax Plus 60) * secondary master: Maxtor 30 GB (DiamondMax VL40) * secondary slave: none Now for my problem: If I install FreeBSD 4.10 from a miniinst CD-R on this system, it works great, no problems. If I install FreeBSD 5.3 from a miniinst CD-R on the same system with no hardware changes, the CD boots up fine (no need to disable ACPI), it fails to make it through the boot process; it just keeps rebooting. More on that in a sec. It also fails to install if all of the following are true: - partitions were set up already from a previous install; - in the slice editor I just re-entered the mount points (they come up as asterisks each time sysinstall is run... I assume that's normal?) - the newfs flag is NOT set on each partition Under these circumstances, the install process freezes at the first fsck_ffs operation (Doing fsck_ffs -y /mnt/dev/ad4s1f which is my /milo partition) ...and no key combos can get out of it. I thought it maybe just took a while but after 30 minutes I decided it was dead. OK, anyway, so if I set newfs on the partitions, then the base distribution installs OK. I can set up the network and root user password, enable SSH and inetd, and then let it boot... BSP CPU.Microcode OK Searching for Boot Record from CDROM..Not Found Searching for Boot Record from Floppy..Not Found Searching for Boot Record from SCSI..Not Found ...and then I get a stack dump that I can't copy here because it disappears as the system automatically reboots right away. If I press a key during the boot, before /boot/loader runs, I can enter 0:ad(0,a) /boot/kernel/kernel -p The result is a rapidly twirling - that then slows and then freezes. A cold reboot is then needed. Same effect when using -sv or -C. I have also tried putting in a different drive (an old 5 GB Seagate instead of the 80 GB Maxtor) and installing to that. For some reason, it doesn't automatically reboot after printing the kernel stack dump, but otherwise there's no change in behavior. I tried using an old 5 GB Seagate drive instead of the Maxtor 80 GB. I tried using a different drive cable. I tried disconnecting all drives other than the boot drive. I have tried setting the partition active and not modifying the MBR. I have also tried using UFS1 instead of UFS2 on all partitions. I have tried using the FreeBSD boot loader. No difference in any case. Twirl twirl twirl freeze. Help? Thanks, Mike [1] http://www.supermicro.com/manuals/motherboard/810/MNL-0618.pdf ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[FreeBSD-Announce] FreeBSD 5.3-RELEASE Announcement
It is my great pleasure and privilege to announce the availability of FreeBSD 5.3-RELEASE. This release marks a milestone in the FreeBSD 5.x series and the beginning of the 5-STABLE branch of releases. Some of the many changes since 5.2.1 include: - A binary compatibility interface has been introduced for the i386 platform that allows running Microsoft Windows NDIS network drivers natively in the kernel. - The network and socket subsystems are now multi-threaded and reentrant. This allows for much better use of SMP parallelism when processing and forwarding local and remote network traffic. - The development environment has been updated to GCC 2.4.2, Binutils 2.15, and GDB 6.1 - The choices for graphical environments have been updated to include X.org 6.7, Gnome 2.6.2 and KDE 3.3.0. There has also been a significant focus on testing and bug-fixing with this release, as well as the freezing of most kernel and userland APIs. Users and vendors are encouraged to consider transitioning to it as FreeBSD 5.x is no longer considered a 'New Technology' release series. Information on migrating from FreeBSD 4.x to 5.x can be found at http://www.FreeBSD.org/releases/5.3R/migration-guide.html For a complete list of new features and known problems, please see the release notes and errata list, available at: http://www.FreeBSD.org/releases/5.3R/relnotes.html http://www.FreeBSD.org/releases/5.3R/errata.html For more information about FreeBSD release engineering activities, please see: http://www.FreeBSD.org/releng Availability - FreeBSD 5.3-RELEASE supports the i386, pc98, alpha, sparc64, amd64, and ia64 architectures and can be installed directly over the net using bootable media or copied to a local NFS/FTP server. Distributions for all architectures are available now. Please continue to support the FreeBSD Project by purchasing media from one of our supporting vendors. The following companies will be offering FreeBSD 5.3 based products: FreeBSD Mall, Inc.http://www.freebsdmall.com/ Daemonnews, Inc. http://www.bsdmall.com/freebsd1.html If you can't afford FreeBSD on media, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO images. We can't promise that all the mirror sites will carry the larger ISO images, but they will at least be available from the following sites. MD5 checksums for the release images are included at the bottom of this message. Bittorrent -- Bittorrent distribution is being tested on an experimental basis. A collection of trackers for the release ISO images is available at http://people.freebsd.org/~scottl/5.3-torrent FTP --- ftp://ftp.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.FreeBSD.org/pub/FreeBSD/ ftp://ftp3.FreeBSD.org/pub/FreeBSD/ ftp://ftp4.FreeBSD.org/pub/FreeBSD/ ftp://ftp5.FreeBSD.org/pub/FreeBSD/ ftp://ftp6.FreeBSD.org/pub/FreeBSD/ ftp://ftp7.FreeBSD.org/pub/FreeBSD/ ftp://ftp10.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.au.FreeBSD.org/pub/FreeBSD/ ftp://ftp.cz.FreeBSD.org/pub/FreeBSD/ ftp://ftp.fr.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.jp.FreeBSD.org/pub/FreeBSD/ ftp://ftp1.ru.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.ru.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.tw.FreeBSD.org/pub/FreeBSD/ ftp://ftp3.us.FreeBSD.org/pub/FreeBSD/ ftp://ftp10.us.FreeBSD.org/pub/FreeBSD/ ftp://ftp11.us.FreeBSD.org/pub/FreeBSD/ ftp://ftp15.us.FreeBSD.org/pub/FreeBSD/ FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, China, Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Japan, Korea, Lithuania, Amylonia, the Netherlands, New Zealand, Poland, Portugal, Romania, Russia, Saudi Arabia, South Africa, Slovak Republic, Slovenia, Spain, Sweden, Taiwan, Thailand, Ukraine, and the United Kingdom. Before trying the central FTP site, please check your regional mirror(s) first by going to: ftp://ftp.yourdomain.FreeBSD.org/pub/FreeBSD Any additional mirror sites will be labeled ftp2, ftp3 and so on. More information about FreeBSD mirror sites can be found at: http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html For instructions on installing FreeBSD, please see Chapter 2 of The FreeBSD Handbook. It provides a complete installation walk-through for users new to FreeBSD, and can be found online at: http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html Acknowledgments Many companies donated equipment, network access, or man-hours to finance the release engineering activities for FreeBSD 5.2 including The FreeBSD Mall, Compaq, Yahoo!, Sentex Communications, Sandvine, Inc., FreeBSD Systems, Inc, and NTT/Verio. The release engineering team for 5.3-RELEASE includes: Scott Long [EMAIL PROTECTED] Release Engineering
Re: [FreeBSD-Announce] FreeBSD 5.3-RELEASE Announcement
Scott Long wrote: It is my great pleasure and privilege to announce the availability of FreeBSD 5.3-RELEASE. This release marks a milestone in the FreeBSD 5.x FTP --- ftp://ftp.FreeBSD.org/pub/FreeBSD/ The file ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/README.TXT needs an updated for 5.3, without the New Technology tag. R. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.3 Release and Dell Poweredge 6450 Install issues
On Nov 6, 2004, at 11:43 PM, [EMAIL PROTECTED] wrote: I get an error during the read of the CDROM install acd0: FAILURE - READ_BIG HARDWARE ERROR asc=0x08 ascq=0x03 error=4ABORTED This did not occur on FreeBSD 5.2.1. Is your CD bad? burn another and see if it works Chad ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD 5.3 Release and Dell Poweredge 6450 Install issues
Found the problem, I had to set this during boot time. set hw.ata.ata_dma=0 set hw.ata.atapi_dma=0 Once I did that, it now installs. I am currently doing the install as I write this. Hope this helps anyone out there that is having this same issue. Btw, I burned 3 cd's using different brands and one was at 1x. Eddie -Original Message- From: Chad Leigh -- Shire.Net LLC [mailto:[EMAIL PROTECTED] Sent: Saturday, November 06, 2004 10:51 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: FreeBSD 5.3 Release and Dell Poweredge 6450 Install issues On Nov 6, 2004, at 11:43 PM, [EMAIL PROTECTED] wrote: I get an error during the read of the CDROM install acd0: FAILURE - READ_BIG HARDWARE ERROR asc=0x08 ascq=0x03 error=4ABORTED This did not occur on FreeBSD 5.2.1. Is your CD bad? burn another and see if it works Chad ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Freebsd 5.3-RELEASE
Hello, Is there anyone who can tell me when Build and release of 5.3-RELEASE will be there? I am closely following this link last weeks: http://www.freebsd.org/releases/5.3R/schedule.html But even the 5.3-RC1 is not out yet. Because there is a error in vinum for 5.2.1-RELEASE i need the new g_vinum function that comes with 5.3-RELEASE. Cheers Mark. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freebsd 5.3-RELEASE
On Sat, Oct 16, 2004 at 02:21:46PM +0200, Mark Frasa wrote: Hello, Is there anyone who can tell me when Build and release of 5.3-RELEASE will be there? No. 5.3 will be released when the developers feel it is ready. My personal guess is that -RC1 will be released in a few days time, and the release about a week after that, but that assumes no new last-minute issues come up. I don't think *any* FreeBSD release so far has actually been released on schedule, but all of them have suffered some delays and 5.3 is no exception in this regard. -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Freebsd 5.3-RELEASE
Hello, Is there anyone who can tell me when Build and release of 5.3-RELEASE will be there? I am closely following this link last weeks: http://www.freebsd.org/releases/5.3R/schedule.html But even the 5.3-RC1 is not out yet. Because there is a error in vinum for 5.2.1-RELEASE i need the new g_vinum function that comes with 5.3-RELEASE. Cheers Mark. If you want to be notified of the new release, you should sign up for the announce mailing list _ Is your PC infected? Get a FREE online computer virus scan from McAfee® Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freebsd 5.3-RELEASE
Mark Frasa wrote: Hello, Is there anyone who can tell me when Build and release of 5.3-RELEASE will be there? I am closely following this link last weeks: http://www.freebsd.org/releases/5.3R/schedule.html But even the 5.3-RC1 is not out yet. Because there is a error in vinum for 5.2.1-RELEASE i need the new g_vinum function that comes with 5.3-RELEASE. Cheers Mark. Greetings! You could just install one of the betas, and upgrade to -RELEASE when the time comes. -- Henrik W Lund ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
