error compiling kernel
Hi all, In an effort to compile a new kernel on my amd64 system running freebsd 6.3 I get the following error message after the make buildkernel KERNCONF=MYKERNEL step. The error I get is: /usr/src/sys/dev/usb/udbp.c: 426: undefined reference to 'ng_parse_int32_type' udbp.o (.rodata + 0xc0):/usr/src/sys/dev/usb/udbp.c: 438: undefined reference to 'ng_parse_int32_type' *** Error code 1 Stop in /usr/obj/usr/src/sys/MYKERNEL *** Error code 1 Stop in /usr/src *** Error code 1 Stop in /usr/src My kernel configuration called MYKERNEL looks like this: # # GENERIC -- Generic kernel configuration file for FreeBSD/amd64 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/amd64/conf/GENERIC,v 1.439.2.6.2.1 2005/10/28 19:22:41 jhb Exp $ machine amd64 cpu HAMMER ident MYKERNEL # To statically compile in device wiring instead of /boot/device.hints #hints GENERIC.hints # Default places to look for devices. makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler #optionsSCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFS_ROOT# NFS usable as /, requires NFSCLIENT options NTFS# NT File System options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework options GEOM_GPT# GUID Partition Tables. options COMPAT_43 # Needed by COMPAT_LINUX32 options COMPAT_IA32 # Compatible with i386 binaries options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_LINUX32 # Compatible with i386 linux binaries #optionsSCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~215k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. # Workarounds for some known-to-be-broken chipsets (nVidia nForce3-Pro150) device atpic # 8259A compatability # Linux 32-bit ABI support options LINPROCFS # Cannot be a module yet. options EXT2FS # Linux ext2 filesystem support # Bus support. device acpi device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atapicam device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # atkbdc0 controls
Re: can't add interfaces to bridge
On Saturday 27 September 2008 20:52:43 Steve Franks wrote: I'm getting the following error - ifconfig: BRDGADD ath0: Invalid argument Given the following commands (which work for my tap interface with qemu on 7.1, but apparently not with two regular network cards on 6.3): sudo kldload if_bridge sudo ifconfig ath0 down sudo ifconfig rl0 down sudo ifconfig bridge0 destroy sudo ifconfig bridge0 create sudo ifconfig bridge0 addm ath0 sudo ifconfig bridge0 addm rl0 sudo ifconfig bridge0 up sudo ifconfig ath0 up sudo ifconfig rl0 up sudo dhclient bridge0 ifconfig I get the following output: [EMAIL PROTECTED] /usr/home/steve]$ bridge kldload: can't load if_bridge: File exists net.link.tap.user_open: 1 - 1 net.link.tap.devfs_cloning: 1 - 1 net.link.tap.up_on_open: 1 - 1 I don't see any sysctl related commands in the script above. ? ifconfig: BRDGADD ath0: Invalid argument ifconfig: BRDGADD rl0: Invalid argument DHCPDISCOVER on bridge0 to 255.255.255.255 port 67 interval 8 ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.2.69 netmask 0xff00 broadcast 192.168.2.255 ether 00:13:f7:4a:0f:a8 media: IEEE 802.11 Wireless Ethernet autoselect (DS/1Mbps) status: no carrier ssid channel 3 authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpowmax 39 bmiss 7 protmode CTS burst bintval 100 rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255 ether 00:01:6c:16:44:6f media: Ethernet autoselect (none) status: no carrier plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 bridge0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether ea:57:36:3c:28:0c priority 32768 hellotime 2 fwddelay 15 maxage 20 [EMAIL PROTECTED] /usr/home/steve]$ (I think that) Your wireless card doesn't seem to be in AP mode and if_bridge can only bridge 802.11 interfaces in AP mode with ethernet inter- faces. Two things though: 1) I am not sure if it complains about it as it does above ifconfig: BRDGADD ath0: Invalid argument 2) I do not undestand why it complains about rl0. What are you trying to achieve? Maybe there is some other way... Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Drive Geometry fail
Hey all, Installing FreeBSD 7.0 on Intel Server Board S3200, WD HDDs 750 GB, it gives me this A geometry of yadayadayada is incorrect, using a more likely geometry error. Of course, in the past I usually just pressed ok and all installations were fine. Till today. It gets to install and then starts to complain that it doesn't have any inodes free. Now, my bios on this motherboard doesn't give out what IT thinks the geometry is, so I'm hosed there. Basically I have no idea how to get FreeBSD moving on that box. Any advice? :) Matiss ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Which mailing list?
I'm running FreeBSD 7.1-PRERELEASE and I want to keep track on when it's updated so that I can upgrade. I'm on the freebsd-announce list but I'm not sure if it's the right list to follow for this purpose. /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: stop in usr/ports/www/firefox3
Hi, Do you cvsup-ed your system? Laci - Original Message From: Dino Vliet [EMAIL PROTECTED] To: freebsd-questions@freebsd.org; [EMAIL PROTECTED] Sent: Sunday, September 28, 2008 2:25:15 PM Subject: stop in usr/ports/www/firefox3 Hi peeps, I want to install firefox3 beside my working firefox2 port on my amd64 system running freebsd 6.3 but the installation fails here: ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x13b8): In function `nsACString::SetLength(unsigned int)': : undefined reference to `NS_CStringGetMutableData' ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x13ea): In function `nsACString::BeginWriting(char**, char**, unsigned int)': : undefined reference to `NS_CStringGetMutableData' ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x14f8): In function `nsACString::BeginWriting(unsigned int)': : undefined reference to `NS_CStringGetMutableData' ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x151d): In function `nsACString::EndWriting()': : undefined reference to `NS_CStringGetMutableData' ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x1aac): In function `nsDependentSubstring_external::nsDependentSubstring_external(nsAString const, unsigned int)': : undefined reference to `NS_StringContainerInit2' ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x1b14): In function `nsDependentSubstring_external::nsDependentSubstring_external(nsAString const, unsigned int, unsigned int)': : undefined reference to `NS_StringContainerInit2' ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x1b68): In function `nsDependentCSubstring_external::nsDependentCSubstring_external(nsACString const, unsigned int)': : undefined reference to `NS_CStringContainerInit2' ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x1bd0): In function `nsDependentCSubstring_external::nsDependentCSubstring_external(nsACString const, unsigned int, unsigned int)': : undefined reference to `NS_CStringContainerInit2' ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x1c73): In function `CompressWhitespace(nsAString)': : undefined reference to `NS_StringGetMutableData' ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x1e13): In function `ToLowerCase(nsACString const, nsACString)': : undefined reference to `NS_CStringGetMutableData' ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x1e93): In function `ToUpperCase(nsACString const, nsACString)': : undefined reference to `NS_CStringGetMutableData' ../../../../dist/lib/libxpcomglue_s.a(nsCRTGlue.o)(.text+0x14f): In function `NS_strndup(unsigned short const*, unsigned int)': : undefined reference to `NS_Alloc' ../../../../dist/lib/libxpcomglue_s.a(nsCRTGlue.o)(.text+0x1d1): In function `NS_strdup(char const*)': : undefined reference to `NS_Alloc' ../../../../dist/lib/libxpcomglue_s.a(nsMemory.o)(.text+0x1d): In function `nsMemory::Clone(void const*, unsigned long)': : undefined reference to `NS_Alloc' gmake[5]: *** [libimgicon.so] Error 1 gmake[5]: Leaving directory `/usr/ports/www/firefox3/work/mozilla/modules/libpr0n/decoders/icon' gmake[4]: *** [tools] Error 2 gmake[4]: Leaving directory `/usr/ports/www/firefox3/work/mozilla/modules/libpr0n/decoders' gmake[3]: *** [tools] Error 2 gmake[3]: Leaving directory `/usr/ports/www/firefox3/work/mozilla/modules/libpr0n' gmake[2]: *** [tools_tier_gecko] Error 2 gmake[2]: Leaving directory `/usr/ports/www/firefox3/work/mozilla' gmake[1]: *** [tier_toolkit] Error 2 gmake[1]: Leaving directory `/usr/ports/www/firefox3/work/mozilla' gmake: *** [default] Error 2 *** Error code 2 Stop in /usr/ports/www/firefox3. *** Error code 1 Stop in /usr/ports/www/firefox3. [EMAIL PROTECTED] /usr/ports/www/firefox3]# What is wrong here? uname -a: FreeBSD zouk.alice.nl 6.3-RELEASE-p1 FreeBSD 6.3-RELEASE-p1 #18: Thu Mar 20 21:01:24 CET 2008 root@:/usr/obj/usr/src/sys/MYKERNEL amd64 Hope somebody can help. Brgds Dino ___ 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: error compiling kernel
On Sun, Sep 28, 2008 at 11:09:01PM -0700, Dino Vliet wrote: Hi all, In an effort to compile a new kernel on my amd64 system running freebsd 6.3 I get the following error message after the make buildkernel KERNCONF=MYKERNEL step. The error I get is: /usr/src/sys/dev/usb/udbp.c: 426: undefined reference to 'ng_parse_int32_type' udbp.o (.rodata + 0xc0):/usr/src/sys/dev/usb/udbp.c: 438: undefined reference to 'ng_parse_int32_type' *** Error code 1 Stop in /usr/obj/usr/src/sys/MYKERNEL *** Error code 1 Stop in /usr/src *** Error code 1 Stop in /usr/src My kernel configuration called MYKERNEL looks like this: # # GENERIC -- Generic kernel configuration file for FreeBSD/amd64 # snip options SCHED_ULE # ULE scheduler #options SCHED_4BSD # 4BSD scheduler snip What is causing this error? Brgds Dino devicefwe # Ethernet over FireWire (non-standard!) Dino, I don't know if it's possibly related but IIRC the SCHED_ULE scheduler is deprecated for use in 6.* (I stand to be corrected!:) although I believe it works with 7.* So I suggest trying SCHED_4BSD and see if that works better. As to the specific error, it looks like you might need: options NETGRAPH in your kernel conf. See: netgraph(4) You might also want to use the tag: RELENG_6_4 for your source supfile. I'm pretty sure there is a 6.4 branch now the BETA has come out. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: stop in usr/ports/www/firefox3
Hi Laci, I did portsnap fetch update so I guess that should do the trick. Or not? Brgds Dino --- On Mon, 9/29/08, Dánielisz László [EMAIL PROTECTED] wrote: From: Dánielisz László [EMAIL PROTECTED] Subject: Re: stop in usr/ports/www/firefox3 To: [EMAIL PROTECTED], freebsd-questions@freebsd.org, [EMAIL PROTECTED] Date: Monday, September 29, 2008, 2:14 PM Hi, Do you cvsup-ed your system? Laci - Original Message From: Dino Vliet [EMAIL PROTECTED] To: freebsd-questions@freebsd.org; [EMAIL PROTECTED] Sent: Sunday, September 28, 2008 2:25:15 PM Subject: stop in usr/ports/www/firefox3 Hi peeps, I want to install firefox3 beside my working firefox2 port on my amd64 system running freebsd 6.3 but the installation fails here: ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x13b8): In function `nsACString::SetLength(unsigned int)': : undefined reference to `NS_CStringGetMutableData' ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x13ea): In function `nsACString::BeginWriting(char**, char**, unsigned int)': : undefined reference to `NS_CStringGetMutableData' ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x14f8): In function `nsACString::BeginWriting(unsigned int)': : undefined reference to `NS_CStringGetMutableData' ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x151d): In function `nsACString::EndWriting()': : undefined reference to `NS_CStringGetMutableData' ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x1aac): In function `nsDependentSubstring_external::nsDependentSubstring_external(nsAString const, unsigned int)': : undefined reference to `NS_StringContainerInit2' ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x1b14): In function `nsDependentSubstring_external::nsDependentSubstring_external(nsAString const, unsigned int, unsigned int)': : undefined reference to `NS_StringContainerInit2' ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x1b68): In function `nsDependentCSubstring_external::nsDependentCSubstring_external(nsACString const, unsigned int)': : undefined reference to `NS_CStringContainerInit2' ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x1bd0): In function `nsDependentCSubstring_external::nsDependentCSubstring_external(nsACString const, unsigned int, unsigned int)': : undefined reference to `NS_CStringContainerInit2' ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x1c73): In function `CompressWhitespace(nsAString)': : undefined reference to `NS_StringGetMutableData' ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x1e13): In function `ToLowerCase(nsACString const, nsACString)': : undefined reference to `NS_CStringGetMutableData' ../../../../dist/lib/libxpcomglue_s.a(nsStringAPI.o)(.text+0x1e93): In function `ToUpperCase(nsACString const, nsACString)': : undefined reference to `NS_CStringGetMutableData' ../../../../dist/lib/libxpcomglue_s.a(nsCRTGlue.o)(.text+0x14f): In function `NS_strndup(unsigned short const*, unsigned int)': : undefined reference to `NS_Alloc' ../../../../dist/lib/libxpcomglue_s.a(nsCRTGlue.o)(.text+0x1d1): In function `NS_strdup(char const*)': : undefined reference to `NS_Alloc' ../../../../dist/lib/libxpcomglue_s.a(nsMemory.o)(.text+0x1d): In function `nsMemory::Clone(void const*, unsigned long)': : undefined reference to `NS_Alloc' gmake[5]: *** [libimgicon.so] Error 1 gmake[5]: Leaving directory `/usr/ports/www/firefox3/work/mozilla/modules/libpr0n/decoders/icon' gmake[4]: *** [tools] Error 2 gmake[4]: Leaving directory `/usr/ports/www/firefox3/work/mozilla/modules/libpr0n/decoders' gmake[3]: *** [tools] Error 2 gmake[3]: Leaving directory `/usr/ports/www/firefox3/work/mozilla/modules/libpr0n' gmake[2]: *** [tools_tier_gecko] Error 2 gmake[2]: Leaving directory `/usr/ports/www/firefox3/work/mozilla' gmake[1]: *** [tier_toolkit] Error 2 gmake[1]: Leaving directory `/usr/ports/www/firefox3/work/mozilla' gmake: *** [default] Error 2 *** Error code 2 Stop in /usr/ports/www/firefox3. *** Error code 1 Stop in /usr/ports/www/firefox3. [EMAIL PROTECTED] /usr/ports/www/firefox3]# What is wrong here? uname -a: FreeBSD zouk.alice.nl 6.3-RELEASE-p1 FreeBSD 6.3-RELEASE-p1 #18: Thu Mar 20 21:01:24 CET 2008 root@:/usr/obj/usr/src/sys/MYKERNEL amd64 Hope somebody can help. Brgds Dino ___ 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: Which mailing list?
I'm running FreeBSD 7.1-PRERELEASE and I want to keep track on when it's updated so that I can upgrade. I'm on the freebsd-announce list but I'm not sure if it's the right list to follow for this purpose. /Leslie you will be surprised how often the code is getting modified and becomes instantly available for updating over cvs and svn routines. sending notifications to [EMAIL PROTECTED] in my opinion would be nice but speaking in terms of data management very inappropriate since it is already there available for you in updated applications change log as well as planned in the todo list bundled with the source code. if there is something missing that only you could have expected i think it doesnt worth a while discussing it with someone who isnt actually doing it ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Which mailing list?
Leslie Jensen wrote: I'm running FreeBSD 7.1-PRERELEASE and I want to keep track on when it's updated so that I can upgrade. I'm on the freebsd-announce list but I'm not sure if it's the right list to follow for this purpose. /Leslie At the moment there hasn't been a RELENG_7_1 tag laid down, so anything labelled 7.1 is from the RELENG_7 branch. Technically both of RELENG_7 and any RELENG_7_x are covered by the freebsd-stable@ mailing list, although there is not usually any great amount of traffic to do with the progress of new releases there. Also, RELENG_7 is a development branch: patches and updates are added to it all the time without any special fanfare or announcements; although right now as we're in the middle of a release process, that's being controlled by the Release Engineering team and is limited to bug fixes and release preparations. If you really want to track all the activity on RELENG_7 then you can join one of the lists that distributes CVS e-mails. This is the most appropriate one for your purposes: http://lists.freebsd.org/mailman/listinfo/cvs-src Even so, that contains all the messages about all the commits to all the branches of the src collection, not just to RELENG_7. You'll need to filter it pretty stringently to pull out just the stuff you're interested in. I believe there is an internal FreeBSD service somewhere which provides quite fine grained filtering, but it may only be available to people with @freebsd.org accounts. (I saw it mentioned on a mailing list many years ago but I've mostly forgotten what I knew about it.) Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: installing 7.0-release from .isos: endless mfi status msgs on console
Jacob Yocom-Piatt a écrit : FreeBSD wrote: Jacob Yocom-Piatt a écrit : am setting up a new fileserver on a poweredge 1950 and installing from the freebsd 7.0-release .isos but can't read anything on the console since the PERC 5/i or 5/e card(s) are dumping status messages to the console non-stop (~1000 lines / minute). What are exactly those messages? I have the same server with FreeBSD 7.0-Release too and I don't get any annoying messages. I would be tempted to say that there is something wrong... martin, they are status messages of some sort that are coming from the two PERC cards installed in the machine, a 5/i for the SAS disks inside it and a 5/e for the MD1000 disk array attached to it via a SAS cable. since i don't have a console attached at this machine's location, i can't easily dump the messages here. suffice it to say that i get similar messages on my other freebsd fileserver running on essentially the same hardware (amd64 on poweredge 1950 + MD1000 enclosure). if you really want to see them, i can acquire them from the console whenever i reboot the machine but only after i have the console reading out. Jake, Maybe you're getting those messages because you have 2 cards installed but I still don't think it's normal that you get that much messages from good working cards. I think it would be interesting to see those messages. Martin if i wait 5-10 minutes, the messages 'settle' and the installer gets further along, but the amd64 installer seizes whereas the i386 one gets to the usual install menu, i.e. 'choose your country', etc. if the amd64 installer is seizing up, can anyone recommend a workaround? i'm not about to install a 32-bit arch onto this machine since it needs to do ZFS which is known to have additional problems with 32-bit arches. cheers, jake Martin is there any way to disable these status messages so that i can get freebsd installed? AFAICT there is nothing broken with the battery on either of the PERC 5/i or 5/e cards installed. cheers, jake ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Which mailing list?
On Monday 29 September 2008 13:47:45 Leslie Jensen wrote: I'm running FreeBSD 7.1-PRERELEASE and I want to keep track on when it's updated so that I can upgrade. I'm on the freebsd-announce list but I'm not sure if it's the right list to follow for this purpose. /Leslie If your intention is to know when 7.1-RELEASE is available and possibly track security advisories afterwards, it is the correct list: http://lists.freebsd.org/pipermail/freebsd-announce/2008-February/001172.html -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Which mailing list?
Mel skrev: On Monday 29 September 2008 13:47:45 Leslie Jensen wrote: I'm running FreeBSD 7.1-PRERELEASE and I want to keep track on when it's updated so that I can upgrade. I'm on the freebsd-announce list but I'm not sure if it's the right list to follow for this purpose. /Leslie If your intention is to know when 7.1-RELEASE is available and possibly track security advisories afterwards, it is the correct list: http://lists.freebsd.org/pipermail/freebsd-announce/2008-February/001172.html Well, my intention is to be updated even on the prerelease. As I understand from the answers, it might be somewhat ambiguous. Do you recommend that I update once a week for example. I understand that not all modifications will affect me, some will of course others will not Thanks /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Which mailing list?
On Monday 29 September 2008 17:06:56 Leslie Jensen wrote:
Mel skrev:
On Monday 29 September 2008 13:47:45 Leslie Jensen wrote:
I'm running FreeBSD 7.1-PRERELEASE and I want to keep track on when
it's updated so that I can upgrade. I'm on the freebsd-announce list but
I'm not sure if it's the right list to follow for this purpose.
/Leslie
If your intention is to know when 7.1-RELEASE is available and possibly
track security advisories afterwards, it is the correct list:
http://lists.freebsd.org/pipermail/freebsd-announce/2008-February/001172.
html
Well, my intention is to be updated even on the prerelease. As I
understand from the answers, it might be somewhat ambiguous. Do you
recommend that I update once a week for example. I understand that not
all modifications will affect me, some will of course others will not
Depends what you want. Everything that goes on RELENG_7 branch currently, is a
bug fix. Each bug fix, has the risk of introducing a regression bug.
If you want to part of the process that tests this PRERELEASE and report any
bugs, confirming bugfixes etc, then you should track RELENG_7. Best way to do
that is to csup your system in the daily periodic(7). Then you can see if any
fixes have been comitted, and rebuild your system.
If you simply want to know if your system still works, subscribe to announce
to know when to stop testing and to build the final release, and build
whenever you have time.
The script below my sig, adds csup to daily, when adding
daily_csup_enable=YES to /etc/periodic.conf and putting the proper csup
file in the proper loc and/or setting the variables in /etc/periodic.conf.
--
Mel
$ cat /usr/local/etc/periodic/daily/340.csup
#!/bin/sh
#
if [ -r /etc/defaults/periodic.conf ]
then
. /etc/defaults/periodic.conf
source_periodic_confs
fi
# Set defaults
daily_csup_enable=${daily_csup_enable:-NO}
daily_csup_files=${daily_csup_files:-/etc/stable-supfile}
daily_csup_flags=${daily_csup_flags:--L2}
case $daily_csup_enable in
[Yy][Ee][Ss])
echo ''
echo 'Running csup:'
for file in ${daily_csup_files}; do
/usr/bin/csup ${daily_csup_flags} ${file}
rc=$((${rc} + $?))
done
echo ''
;;
*) rc=0;;
esac
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Which mailing list?
Mel skrev: On Monday 29 September 2008 17:06:56 Leslie Jensen wrote: Mel skrev: On Monday 29 September 2008 13:47:45 Leslie Jensen wrote: I'm running FreeBSD 7.1-PRERELEASE and I want to keep track on when it's updated so that I can upgrade. I'm on the freebsd-announce list but I'm not sure if it's the right list to follow for this purpose. /Leslie If your intention is to know when 7.1-RELEASE is available and possibly track security advisories afterwards, it is the correct list: http://lists.freebsd.org/pipermail/freebsd-announce/2008-February/001172. html Well, my intention is to be updated even on the prerelease. As I understand from the answers, it might be somewhat ambiguous. Do you recommend that I update once a week for example. I understand that not all modifications will affect me, some will of course others will not Depends what you want. Everything that goes on RELENG_7 branch currently, is a bug fix. Each bug fix, has the risk of introducing a regression bug. If you want to part of the process that tests this PRERELEASE and report any bugs, confirming bugfixes etc, then you should track RELENG_7. Best way to do that is to csup your system in the daily periodic(7). Then you can see if any fixes have been comitted, and rebuild your system. If you simply want to know if your system still works, subscribe to announce to know when to stop testing and to build the final release, and build whenever you have time. The script below my sig, adds csup to daily, when adding daily_csup_enable=YES to /etc/periodic.conf and putting the proper csup file in the proper loc and/or setting the variables in /etc/periodic.conf. Thanks! I'll try it out. /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
(no subject)
Dear Madam/Sir. Sorry for disturbing you. Would u pleae tell me the maximum number of CPUs which are supported by FreeBSD v7? Thanks. -- B.R Mostafa Nikpour H/P:+60-17-334-6796 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: can't add interfaces to bridge
On Mon, Sep 29, 2008 at 2:17 AM, Nikos Vassiliadis [EMAIL PROTECTED] wrote: On Saturday 27 September 2008 20:52:43 Steve Franks wrote: I'm getting the following error - ifconfig: BRDGADD ath0: Invalid argument Given the following commands (which work for my tap interface with qemu on 7.1, but apparently not with two regular network cards on 6.3): sudo kldload if_bridge sudo ifconfig ath0 down sudo ifconfig rl0 down sudo ifconfig bridge0 destroy sudo ifconfig bridge0 create sudo ifconfig bridge0 addm ath0 sudo ifconfig bridge0 addm rl0 sudo ifconfig bridge0 up sudo ifconfig ath0 up sudo ifconfig rl0 up sudo dhclient bridge0 ifconfig I get the following output: [EMAIL PROTECTED] /usr/home/steve]$ bridge kldload: can't load if_bridge: File exists net.link.tap.user_open: 1 - 1 net.link.tap.devfs_cloning: 1 - 1 net.link.tap.up_on_open: 1 - 1 I don't see any sysctl related commands in the script above. ? ifconfig: BRDGADD ath0: Invalid argument ifconfig: BRDGADD rl0: Invalid argument DHCPDISCOVER on bridge0 to 255.255.255.255 port 67 interval 8 ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.2.69 netmask 0xff00 broadcast 192.168.2.255 ether 00:13:f7:4a:0f:a8 media: IEEE 802.11 Wireless Ethernet autoselect (DS/1Mbps) status: no carrier ssid channel 3 authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpowmax 39 bmiss 7 protmode CTS burst bintval 100 rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255 ether 00:01:6c:16:44:6f media: Ethernet autoselect (none) status: no carrier plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 bridge0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether ea:57:36:3c:28:0c priority 32768 hellotime 2 fwddelay 15 maxage 20 [EMAIL PROTECTED] /usr/home/steve]$ (I think that) Your wireless card doesn't seem to be in AP mode and if_bridge can only bridge 802.11 interfaces in AP mode with ethernet inter- faces. Two things though: 1) I am not sure if it complains about it as it does above ifconfig: BRDGADD ath0: Invalid argument 2) I do not undestand why it complains about rl0. What are you trying to achieve? Maybe there is some other way... Just trying to string some old printers the like off my rl0 and get them onto the local wifi net via ath0. ath0 is connected to an AP. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: can't add interfaces to bridge
On Monday 29 September 2008 18:40:56 Steve Franks wrote: On Mon, Sep 29, 2008 at 2:17 AM, Nikos Vassiliadis [EMAIL PROTECTED] wrote: On Saturday 27 September 2008 20:52:43 Steve Franks wrote: I'm getting the following error - ifconfig: BRDGADD ath0: Invalid argument Given the following commands (which work for my tap interface with qemu on 7.1, but apparently not with two regular network cards on 6.3): sudo kldload if_bridge sudo ifconfig ath0 down sudo ifconfig rl0 down sudo ifconfig bridge0 destroy sudo ifconfig bridge0 create sudo ifconfig bridge0 addm ath0 sudo ifconfig bridge0 addm rl0 sudo ifconfig bridge0 up sudo ifconfig ath0 up sudo ifconfig rl0 up sudo dhclient bridge0 ifconfig I get the following output: [EMAIL PROTECTED] /usr/home/steve]$ bridge kldload: can't load if_bridge: File exists net.link.tap.user_open: 1 - 1 net.link.tap.devfs_cloning: 1 - 1 net.link.tap.up_on_open: 1 - 1 I don't see any sysctl related commands in the script above. ? ifconfig: BRDGADD ath0: Invalid argument ifconfig: BRDGADD rl0: Invalid argument DHCPDISCOVER on bridge0 to 255.255.255.255 port 67 interval 8 ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.2.69 netmask 0xff00 broadcast 192.168.2.255 ether 00:13:f7:4a:0f:a8 media: IEEE 802.11 Wireless Ethernet autoselect (DS/1Mbps) status: no carrier ssid channel 3 authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpowmax 39 bmiss 7 protmode CTS burst bintval 100 rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255 ether 00:01:6c:16:44:6f media: Ethernet autoselect (none) status: no carrier plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 bridge0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether ea:57:36:3c:28:0c priority 32768 hellotime 2 fwddelay 15 maxage 20 [EMAIL PROTECTED] /usr/home/steve]$ (I think that) Your wireless card doesn't seem to be in AP mode and if_bridge can only bridge 802.11 interfaces in AP mode with ethernet inter- faces. Two things though: 1) I am not sure if it complains about it as it does above ifconfig: BRDGADD ath0: Invalid argument 2) I do not undestand why it complains about rl0. What are you trying to achieve? Maybe there is some other way... Just trying to string some old printers the like off my rl0 and get them onto the local wifi net via ath0. ath0 is connected to an AP. Unless you have 506 devices on those networks, consider using lagg(4). It has a warning for WPA, but since you use WEP, it should theoretically work. Now if it would work with WPA and ap mode on any 802.11 device, we can finally have 'real wireless routers'. ;) -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [OT] Apache SSL certificate authentication
Fraser Tweedale wrote: - Create my CA key and a CSR, and have CACert sign it. Are you sure it's signed as an intermediary CA? cacert.org's website suggests they will only sign leaf certificates. http://wiki.cacert.org/wiki/SubRoot Fortunately, your client certs need not be signed by the same CA as your server cert, and it's probably somewhat pointless to have a client cert (which will be used for your infrastructure alone) vetted by a third party. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net [EMAIL PROTECTED] Furry Peace! - http://.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Midnight Commander's subshell gone..
Hi Daemons, I have just updated /usr/ports/misc/mc to Mignight Commander 4.6.1. As root I can switch with CTRL+O to the shell prompt, all fine. But as a normal user the shell prompt disappears when I hit CTRL+O. Both xterm and without X I have the same symptoms. So I have set all mc-related files in /usr/local/share/mc to 777 to check. I use both in /root/ as well in /home/herbs/ the same .profile and ./mc files -- still not working.. The previous mc-version ran just fine. What am I doing wrong?? Thanks for ideas! herbs ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Midnight Commander's subshell gone..
Both xterm and without X I have the same symptoms. So I have set all mc-related files in /usr/local/share/mc to 777 to check. I use both in /root/ as well in /home/herbs/ the same .profile and ./mc files -- still not working.. The previous mc-version ran just fine. What am I doing wrong?? using new versions.. install mc-light from ports. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Writing hald .fdi files
On Monday 29 September 2008 21:27:36 Zahemszky Gábor wrote: So my question: how can I make an .fdi file, which tells to these automounters: if this is device X from vendor Y, mount it with mount option XY! Add a noauto mountpoint to /etc/fstab, with all the correct options. Though, hal is one of those projects that sparked my sig - too many ways to possibly do it, not enough straight ways to really do it. So, maybe check this too: http://www.freebsd.org/gnome/docs/halfaq.html#q3 -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Writing hald .fdi files
Hi!
I've bought an external disk. I can mount it by hand, with
mount -t msdosfs -o large /dev/xxx /mnt
command. (I have to use the -o large option.)
I use XFCE4, with Thunar-volman-plugin. When I plug my new disk in, I
got a message box: Cannot mount, try with -o large option. So I'd
like to say to the automounter of Thunar, to use the mount_msdosfs
command with that -o large option. After some googling, I found HAL
specification on
http://webcvs.freedesktop.org/hal/hal/doc/spec/hal-spec.html?view=copathrev=HEAD
and wrote that .fdi file:
== /usr/local/share/hal/fdi/policy/30user/10-add-mount-option-for-Verbatim.fdi
==
?xml version=1.0 encoding=UTF-8?
deviceinfo version=0.2
device
match key=block.device string=/dev/msdosfs/VERBATIM
match key=info.category string=volume
merge key=volume.policy.mount_option.large type=booltrue/merge
/match
/match
/device
/deviceinfo
My problem is: after plugging my disk in, in lshal output, I can see the new
key:
volume.policy.mount_option.large ( = true) , but got the same error message
about
the mounting problem.
I tried it with Linux (+GNOME). Linux can mount my disk, so I tried to
mount with read-only flag. The same problem: I can see my new key, but
it hasn't got any effect (well, it has. without my .fdi file, it can mount with
rw,
but with my .fdi file, it cannot mount. Neither rw, nor ro.)
So my question: how can I make an .fdi file, which tells to these
automounters:
if this is device X from vendor Y, mount it with mount option XY!
Thanks, Gábor
--
#!/bin/ksh
Z='21N16I25C25E30, 40M30E33E25T15U!';IFS=' ABCDEFGHIJKLMNOPQRSTUVWXYZ
';set -- $Z;for i;{ [[ $i = ? ]]print $ibreak;[[ $i
= ??? ]]j=$ii=${i%?};typeset -i40 i=8#$i;print -n ${i#???};[[ $j
= ??? ]]print -n ${j#??} j=;typeset +i i;};IFS=' 0123456789 ';set
-- $Z;for i;{ [[ $i = , ]]i=2;[[ $i = ?? ]]||typeset -l i;j=$j
$i;typeset +l i;};print $j
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
AuthPF not updating rules
I have /etc/authpf created, with an empty authpf.conf inside. Also inside is users/'username'/authpf.rules, which is not writable by anyone but root. Also, my AuthPF user has authpf as a shell. I've also jumped through 2 undocumented hoops of creating and permission-ing /var/authpf and mounting fdescfs. All that aside, I can log in and get my Hello. However, not only does my rule not work, but doing pfctl -s rules | grep 'client-ip-address' brings back nothing. Can anyone tell me something I may have missed? If I make a syntax error, I see pfctl complain, so I'm sure that the file is being read. Appreciate any help, Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Jailing net/skype
For the archive: I finally got skype working in a jailed environment. The hardest part was to define the ports needed using trial and error. Here are the leaf ports installed in my jail: === skype-2.0.0.72,1 === xauth-1.0.2 === xorg-fonts-100dpi-7.3 === xorg-fonts-75dpi-7.3 === xorg-fonts-cyrillic-7.3 === xorg-fonts-miscbitmaps-7.3 === xorg-fonts-truetype-7.3 === xorg-fonts-type1-7.3 === 8 leaf ports xauth is needed to enable X-forwarding in ssh. The fonts are needed to avoid the core dumps mentioned earlier in this thread. I hope somenone finds this useful. Regards Tobias -- Tobias Rehbein PGP key: 4F2AE314 server: keys.gnupg.net fingerprint: ECDA F300 1B6E 9B87 8524 8663 E8B6 3138 4F2A E314 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
SATA READ_DMA timeouts - SOLVED?
I've seen a number of people having DMA troubles with SATA disks on FreeBSD6 and FreeBSD7, and I'm in the same boat. A while back I posted looking for help but none could really be found. Today I finally got to the bottom of things (at least so far). Hardware incompatibility. According to http://en.wikipedia.org/wiki/SATA#SATA_1.5_Gbit.2Fs_and_SATA_3_Gbit.2Fs there is an upward compatibility problem between a number of VIA and SiS chipsets and SATA300 disks. I happen to have one of those controllers (SiS964) and a pair of WD1600AAJS disks, which are SATA300 disks. I ripped apart my machine, and sure enough I had a jumper on each disk labelled 'OPT1', which is documented to force SATA150 operation. I've since cold booted, warm booted, and booted after a power interruption with no READ_DMA timeouts on these disks. I think this solved the problem in my case. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA READ_DMA timeouts - SOLVED?
(I'm not subscribed to freebsd-questions, so please CC me on replies. I'm also not sure how I ended up getting this mail in the first place; it looks like someone BCC'd my [EMAIL PROTECTED] address). Reid, The Wikipedia article you refer to documents a very well-known topic: the SATA150-limiting jumpers on hard disks. Drive vendors have this jumper enabled (capped) by default due to incompatibilities with certain chipsets (VIA, SiS, and nVidia -- who isn't mentioned). The jumper in question is available on Western Digital and Seagate disks; I have not checked to see if Maxtor, Samsung, or Fujitsu disks offer this capability. Maxtor disks also have further incompatibilities with nVidia chipsets, specifically with regards to broken NCQ support (the disk will literally lock up/hang, causing Windows or other operating systems to blue screen or crash). A disk firmware update from Maxtor is available to fix this problem, but you have to go through Tier 1 support hell to get the patch. Additionally, the patch does not increment/change the f/w version string, so there's no way to tell if your drive already has the patch or not. (I do have the patch laying around, but I can't remember which models of Maxtor disk it affects.) Furthermore, one of the most common reports on the FreeBSD lists is the exact opposite -- users complaining that their disks are SATA300 but only operate at SATA150 (caused by that jumper). Users are told to remove the jumper, and are reminded that the reason the jumper is enabled by default is said chipset incompatibilities. That said, your mail confuses me for one reason: Were you receiving DMA errors with the jumper REMOVED (e.g. SATA300 operation), or with the jumper ENABLED (SATA150 operation)? Your below description does not state what exactly you did with the jumper to make your drives work reliably, only that the jumper capability on your disks was available. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | On Mon, Sep 29, 2008 at 04:19:22PM -0500, Reid Linnemann wrote: I've seen a number of people having DMA troubles with SATA disks on FreeBSD6 and FreeBSD7, and I'm in the same boat. A while back I posted looking for help but none could really be found. Today I finally got to the bottom of things (at least so far). Hardware incompatibility. According to http://en.wikipedia.org/wiki/SATA#SATA_1.5_Gbit.2Fs_and_SATA_3_Gbit.2Fs there is an upward compatibility problem between a number of VIA and SiS chipsets and SATA300 disks. I happen to have one of those controllers (SiS964) and a pair of WD1600AAJS disks, which are SATA300 disks. I ripped apart my machine, and sure enough I had a jumper on each disk labelled 'OPT1', which is documented to force SATA150 operation. I've since cold booted, warm booted, and booted after a power interruption with no READ_DMA timeouts on these disks. I think this solved the problem in my case. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
