vBSDcon Registrations Remain Open!
Hi all, As many of you are aware, the social aspect of BSD-related conferences is very important and offers opportunities to meet and socialize with one another. Maintaining that tradition, Verisign's vBSDcon will feature a mid-conference social, brought to you exclusively by Juniper, and will be celebrating 20 years of FreeBSD. We encourage all attendees to join Verisign and Juniper to celebrate this milestone for the FreeBSD project. Conference activities start on October 25, 2013 at 6:00PM Eastern with a reception dinner hosted by Verisign at the Dulles Hyatt. General conference activities start the following morning with a presentation by David Chisnall, FreeBSD Core Team member, on the migration from GCC to LLVM/Clang within FreeBSD. David Chisnall is a Research Associate at the University of Cambridge, where he works on the interface between languages, operating systems, and hardware. He is also a member of the FreeBSD Core Team and an LLVM/Clang committer. He is the author of several books, including the Definitive Guide to the Xen Hypervisor. He created the current GNUstep implementation of Objective-C and has maintained it for some years, and is now mostly responsible for the C++ stack in FreeBSD, having implemented the ABI library and ported the STL implementation. We are in high gear planning for vBSDcon 2013 hosted by Verisign at the Dulles Hyatt in Herndon, VA and we are drawing closer by the week with 5 weeks left to register. Registrations are being accepted on the conference web site at http://www.vbsdcon.com/ through October 23, 2013 after which registrations will only be taken in person at the event. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to log sshd access in a single file
On Mon, Sep 16, 2013 at 9:36 AM, aurikus grande auri...@gmail.com wrote: Hello, just a few days ago i setup my first FreeBSD server, so i am new to this OS. I already tried to find the information i was looking for, but to no luck. I try to add a line in /etc/hosts.allow which would allow and log all attempts using SSH (sshd). [ snip ] I would recommend using the auth and authpriv facilities for syslog. Check the syslog.conf manpage for configuring such activity. I believe FreeBSD defaults to failed ssh authentication is logged to /var/log/messages while successful authentication is written to /var/log/auth.log. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to log sshd access in a single file
On Mon, Sep 16, 2013 at 1:57 PM, aurikus grande auri...@gmail.com wrote: Hello Rick, sorry that i did not reply to all, from now on i will use reply to all. Thanks for pointing it out. I will also open port 80 for web access, but i do not want to log those. Because i expect a huge amount of traffic on my server. Most web servers handle their own logging. So i only want to log successfull and unsuccessfull sshd access. Have you looked at /var/log/auth.log? twist is part of the FreeBSD 9.1 base installation, i did not yet install any other package. That was my mistake, I sent the email before editing that out as I had intended. The idea behind using hosts.allow was because i could specify the rule by the service (and not by the level of the message). And yes, in my case sshd is configured to run via inetd. You are correct, my main goal is to log all failed sshd attempts. If it is easier to log successfull and failed attempts (to the same file), this would also be fine for me. Can you elaborate on your reasons for running sshd via inetd? I'm curious as I've never even heard of anyone attempting this. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to log sshd access in a single file
Hi Aurikus, Selecting Reply all when replying to messages on the list allows the entire list to benefit from the discussion. On Mon, Sep 16, 2013 at 11:05 AM, aurikus grande auri...@gmail.com wrote: Hello Rick. thanks a lot for your quick reply. Does your recommendation - to use syslog.conf mean instead - that i cant accomplish what i want with hosts.allow and twist ? I am unfamiliar with twist and cannot authoritatively answer this question. Not to mention, it does not appear to be in base I´m still reading through the man pages and try to understand how to configure syslog.conf. I recommended syslog, because it is the stock logging mechanism for FreeBSD. On my 9.1 system, /etc/syslog.conf contains: auth.info;authpriv.info /var/log/auth.log These facilities are both logging to /var/log/auth.log. Your stated goal was logging of failed ssh attempts to your host. The above line in syslog.conf accomplishes this by sending the message to /var/log/auth.log. TCPWrappers will have no effect on logging of failed ssh attempts unless sshd is configured to run via inetd. I recommend pf or ipfw for filtering access to ssh. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to log sshd access in a single file
On Mon, Sep 16, 2013 at 2:44 PM, aurikus grande auri...@gmail.com wrote: Most web servers handle their own logging. I do _not_ want the web server acces to be logged (at least as of now). Which is fine, but still configured via your web server. Have you looked at /var/log/auth.log? yes, and as you mentioned in your previous update, it logs the success login (only). Unsuccessfull attempts are being sent to /var/log/messages . So there are 2 separate files. I would like to have all sshd access attempts in one single file - regardless if they are successfull or unsuccessfull. Quotation: I believe FreeBSD defaults to failed ssh authentication is logged to /var/log/messages while successful authentication is written to /var/log/auth.log. I was incorrect. Fail and success are both recorded here. Even if this were the case, the best way to accomplish what you're looking for is still syslog. Can you elaborate on your reasons for running sshd via inetd? I'm curious as I've never even heard of anyone attempting this. When i searched how to setup / configure sshd on internet, i found many hints to start it using inetd. Since it worked for me there was no reason to change it. In general, most administrators will not run ssh via inetd. A more common configuration is detailed in the FreeBSD handbook at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/openssh.html -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Make Release
On Thu, Aug 1, 2013 at 12:40 PM, Amitabh Kant amitabhk...@gmail.com wrote: Devin Teske Rick Miller have a fairly extensive explanation on their blogs on how to create your own modified iso's. Search the archives for links. Hopefully they can chime in with their respective links. Sorry to show up late for the discussion... Devin Teske definitely has more experience and knowledge than I. However, several of my blog posts may have relevant and helpful information on customizing images. There's not really one single answer as it depends largely on what you're looking to do. My customized images use a scripted sysinstall install.cfg that fetches a dynamically generated answer file from Cobbler. The answer file is based on a text template which includes Cheetah calls to Cobbler snippets for various things, including modifying the rc.conf. All lines modifying the rc.conf are placed in the answer file following the installCommit resword. Also understand that we replaced the http media type module with our own permitting direct http installs. In 8.4 or newer, there is a new media type called httpDirect (or similar) that accomplishes this as well. Here are some posts you may find helpful: http://blog.hostileadmin.com/2013/04/11/installing-freebsd-via-cobbler/ http://blog.hostileadmin.com/2012/10/08/building-freebsd-media-with-custom-packages/ http://blog.hostileadmin.com/2012/05/08/using-sysinstall-for-automated-freebsd-8-x-installs/ Bear in mind this applies specifically to FreeBSD 8.x. I will begin attacking 9.x in the coming months and anticipate more blog posts on accomplishing similar tasks within 9.x. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
vBSDcon Website Update
Hi all, The vBSDcon website has been updated with a full speaker line-up and schedule for the BSD-related conference October 25 - 27, 2013. Check it out at http://www.vbsdcon.com/. Registrations will begin in the coming weeks. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
vBSDcon Website Update
Hi all, For those interested in vBSDcon, a BSD-related conference scheduled for October 2013 in the Washington DC area, the web site has been updated to include a detailed schedule and speaker line-up including descriptions of their presentations. Registrations will begin in the coming month. Please feel free to check it out at http://www.vbsdcon.com/. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: vBSDcon Website Update
I just checked it out. Seems to be up for me...
On Monday, July 22, 2013, Виталий Туровец wrote:
The site seems down from here (AS58054).
2013/7/22 Rick Miller vmil...@hostileadmin.com javascript:_e({},
'cvml', 'vmil...@hostileadmin.com');
Hi all,
For those interested in vBSDcon, a BSD-related conference scheduled
for October 2013 in the Washington DC area, the web site has been
updated to include a detailed schedule and speaker line-up including
descriptions of their presentations. Registrations will begin in the
coming month. Please feel free to check it out at
http://www.vbsdcon.com/.
--
Take care
Rick Miller
___
freebsd-questions@freebsd.org javascript:_e({}, 'cvml',
'freebsd-questions@freebsd.org'); mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
freebsd-questions-unsubscr...@freebsd.org javascript:_e({}, 'cvml',
'freebsd-questions-unsubscr...@freebsd.org');
--
~~~
WBR,
Vitaliy Turovets
NOC Lead @TV-Net ISP
+38(093)265-70-55
VITU-RIPE
X-NCC-RegID: ua.tv
--
Take care
Rick Miller
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Mirroring Binary Packages
Hi all, I want to mirror binary packages for 8.x amd64 internally on an isolated network. It appears the appropriate source would be on an official mirror at pub/FreeBSD/ports/amd64/packages-8-stable/ for the most recent updates. However, it does not appear to have been updated since October 2012 as seen by the dates of files. Is this the appropriate source to mirror for the most recently built binary packages for 8.x amd64? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
8.4-RELEASE buildworld failure
Hi all, I checked out releng/8.4, executed buildworld, and received the following error. Wondering if someone might have experience with this scenario. === share/doc/psd/13.rcs/rcs_func (all) groff -Tascii -P-c -mtty-char -ms /usr/src/share/doc/psd/13.rcs/rcs_func/../../../../../gnu/usr.bin/rcs/doc/ rcs_func.ms | gzip -cn rcs_func.ascii.gz === share/doc/psd/15.yacc (all) touch _stamp.extra make: don't know how to make ssA. Stop *** Error code 2 Stop in /usr/src/share/doc/psd. *** Error code 1 Stop in /usr/src/share/doc. *** Error code 1 Stop in /usr/src/share. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. There is no src.conf and make.conf only sets PERL_VERSION. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: looking for command to display default route ip address
On Wed, May 29, 2013 at 2:03 PM, Joe fb...@a1poweruser.com wrote: Hello list How do I find the ip address of the default route? The following examples return the next hop, usually a router. # grep defaultrouter /etc/rc.conf defaultrouter=192.168.0.1 or # netstat -r Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default192.168.0.1 UGS 0 192em0 ... -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd-stable/release?
On Tue, May 21, 2013 at 2:18 PM, Pol Hallen freebsde...@fuckaround.org wrote: Hi all :-) quick question: for a production server, what it best way? I've done work with organizations that will not install anything that is considered a development branch, of which stable/ is. Therefore, for production environments, those organizations will only install -RELEASE or releng/ releases. It comes down to a decision you and/or your organization must make and that decision will be based on a risk/reward analysis. Hope that helps. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Installing FreeBSD via Cobbler
Hi All, For anyone interested, I posted a blog article explaining how to install FreeBSD via Cobbler posted at http://blog.hostileadmin.com/2013/04/11/installing-freebsd-via-cobbler/. I'd like to thank Devin Teske for his help with this project. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: building crunchgen fails
Hi All, In the thread below, my custom boot_crunch.conf works in releng/8, but fails in stable/8. Here is the failure message: cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo ls.lo test.lo cat.lo df.lo sleep.lo camcontrol.lo dhclient.lo fsck_ffs.lo ifconfig.lo mount_nfs.lo newfs.lo route.lo rtsol.lo tunefs.lo kenv.lo sysctl.lo mdmfs.lo mdconfig.lo mount.lo dmesg.lo fdisk.lo bsdlabel.lo uname.lo cpio.lo find.lo minigzip.lo sed.lo awk.lo fetch.lo arp.lo sysinstall.lo usbconfig.lo grep.lo -ll -ledit -lfetch -lmd -lcrypt -lftpio -lz -lnetgraph -ldialog -lncurses -lcam -lsbuf -lutil -ldisk -lufs -ldevinfo -lkvm -lgeom -lbsdxml -larchive -lbz2 -lusb -lgnuregex -llzma -lssl -lcrypto -ljail -lm camcontrol.lo(.text+0x13fe): In function `mode_list': : undefined reference to `mode_sense' camcontrol.lo(.text+0x1e93): In function `mode_edit': : undefined reference to `mode_sense' camcontrol.lo(.text+0x1ee7): In function `mode_edit': : undefined reference to `mode_sense' camcontrol.lo(.text+0x1f6a): In function `mode_edit': : undefined reference to `mode_sense' camcontrol.lo(.text+0x209e): In function `mode_edit': : undefined reference to `mode_sense' camcontrol.lo(.text+0x2118): In function `mode_edit': : undefined reference to `mode_select' *** Error code 1 Stop in /usr/obj/usr/src/release/boot_crunch. *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. I attempted my custom boot_crunch.conf as well as the default. Both fail with the same error. My custom boot_crunch.conf is @ http://pastebin.com/jfcJKb08 Note the special line included as Devin recommends the thread below. mode_sense and mode_select appear to be defined (but I am far from proficient with C to declare with any authority what the problem might be. I'm hoping someone could help me understand and correct the problem. On Wed, Jan 23, 2013 at 11:01 AM, Devin Teske devin.te...@fisglobal.com wrote: On Jan 23, 2013, at 7:22 AM, Rick Miller wrote: Hi All, When executing crunchgen -o boot_crunch.conf make -f boot_crunch.mk I get the following error: cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo ls.lo test.lo cat.lo df.lo sleep.lo camcontrol.lo dhclient.lo fsck_ffs.lo ifconfig.lo mount_nfs.lo newfs.lo route.lo rtsol.lo tunefs.lo kenv.lo sysctl.lo mdmfs.lo dmesg.lo fdisk.lo bsdlabel.lo uname.lo cpio.lo find.lo minigzip.lo sed.lo awk.lo fetch.lo arp.lo sysinstall.lo usbconfig.lo grep.lo -lcam -lsbuf -lutil -ll -ledit -lfetch -lmd -lcrypt -lftpio -lz -lnetgraph -ldialog -lncurses -ldisk -lufs -ldevinfo -lkvm -lgeom -lbsdxml -larchive -lbz2 -lusb -lgnuregex -llzma -lssl -lcrypto -ljail -lm camcontrol.lo(.text+0x730b): In function `main': : undefined reference to `mode_edit' camcontrol.lo(.text+0x73fa): In function `main': : undefined reference to `mode_list' *** Error code 1 Stop in /tmp/crunchtmp. I understand that there may need to be some shuffling of the libraries in the boot_crunch.conf, but I've done that to no avail. Wondering if anyone else may be able to shed some light on this... The boot_crunch.conf can be viewed at http://pastebin.com/ZwVPQn3h According to the Makefile, if RELEASE_CRUNCH is defined, then modeedit.o object is omitted (causing your undefined references). I perceive the long-term real solution would be to patch camcontrol.c (and pedantically camcontrol.h) to not use mode_edit()/mode_list() when RELEASE_CRUNCH is defined. However, you should be able to get through your problem by adjusting your boot_crunch.conf slightly: Try http://pastebin.com/Ge6UCZEZ The difference being: --- boot_crunch.conf.orig 2013-01-03 16:29:20.0 -0800 +++ boot_crunch.conf2013-01-03 16:29:13.0 -0800 @@ -17,6 +17,7 @@ srcdirs /usr/src/sbin progs camcontrol +special camcontrol objs camcontrol.o modeedit.o util.o progs dhclient progs fsck_ffs progs ifconfig -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: about unatteneded installation
Hi Devin, On 12/20/12 1:10 PM, Devin Teske devin.te...@fisglobal.com wrote: For now, people that prefer sysinstall can use my FreeBSD Druid pre-built install media: For 9.0: http://sourceforge.net/projects/druidbsd/files/FreeBSD-9.0_Druid-1.0b60.iso/download For 8.3: http://sourceforge.net/projects/druidbsd/files/FreeBSD-8.3_Druid-1.0b60.iso/download As for 10.0 (when it comes out), expect bsdinstall to surpass sysinstall (in many many great ways) in every way (unlike the current status in 9.x). I had begun evaluating FreeBSD Druid and DruidBSD, but was sidetracked with a different project. I'm hoping to return to this in the coming weeks. Having said that, I am wondering what disk partition utilities FreeBSD Druid/DruidBSD use when installing 9.x. Is it using fdisk/bsdlabel or gpart? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: about unatteneded installation
On Thu, Feb 14, 2013 at 12:34 PM, Teske, Devin devin.te...@fisglobal.com wrote: On Thu, 14 Feb 2013, Rick Miller wrote: No worries on time lapse. In fact, I had been needing to get back to you on assuaging those 4 failed patch hunks on your sysinstall work. FreeBSD Druid (both 8.x and 9.x) use sysinstall for disk partitioning. What does sysinstall use, you say? Glad you asked. sysinstall(8) uses a combination of: I anticipated this. I am under the impression one cannot force proper slice alignment on 4K sector drives with sysinstall (see http://ivoras.net/blog/tree/2011-01-01.freebsd-on-4k-sector-drives.html). Is it safe to assume that this also applies to 9.x when utilizing sysinstall based installer? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Cannot resolve localhost
Does the 'hosts' line in the nsswitch.conf direct the resolver to try 'files' before 'dns'? On 2/14/13, Martin Pola martin.p...@kottnet.net wrote: Hi, I'm trying to get my FreeBSD system to resolve localhost into 127.0.0.1, but unfortunately it doesn't work. It appears the resolver is never reading from /etc/hosts, where I have this line: 127.0.0.1 localhost Here's a sample output of what I get when I try to resolve the name: $ nslookup localhost ;; Got recursion not available from 91.90.24.250, trying next server Server: 8.8.8.8 Address:8.8.8.8#53 ** server can't find localhost: NXDOMAIN What am I missing? Kind regards, Martin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Sent from my mobile device Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: sh script ?
On Thu, Jan 24, 2013 at 1:07 PM, Fbsd8 fb...@a1poweruser.com wrote:
I get this message [: 10.0.10.21: bad number on this code
[ ${saved_ip} -eq ${used_ip} ] echo good match
Both variables have valid ip addresses in them.
Why does it think the variable content is a number and not text?
What am I doing wrong?
The -eq operator is used to compare integers. When comparing strings,
use the == operator.
--
Take care
Rick Miller
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
building crunchgen fails
Hi All, When executing crunchgen -o boot_crunch.conf make -f boot_crunch.mk I get the following error: cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo ls.lo test.lo cat.lo df.lo sleep.lo camcontrol.lo dhclient.lo fsck_ffs.lo ifconfig.lo mount_nfs.lo newfs.lo route.lo rtsol.lo tunefs.lo kenv.lo sysctl.lo mdmfs.lo dmesg.lo fdisk.lo bsdlabel.lo uname.lo cpio.lo find.lo minigzip.lo sed.lo awk.lo fetch.lo arp.lo sysinstall.lo usbconfig.lo grep.lo -lcam -lsbuf -lutil -ll -ledit -lfetch -lmd -lcrypt -lftpio -lz -lnetgraph -ldialog -lncurses -ldisk -lufs -ldevinfo -lkvm -lgeom -lbsdxml -larchive -lbz2 -lusb -lgnuregex -llzma -lssl -lcrypto -ljail -lm camcontrol.lo(.text+0x730b): In function `main': : undefined reference to `mode_edit' camcontrol.lo(.text+0x73fa): In function `main': : undefined reference to `mode_list' *** Error code 1 Stop in /tmp/crunchtmp. I understand that there may need to be some shuffling of the libraries in the boot_crunch.conf, but I've done that to no avail. Wondering if anyone else may be able to shed some light on this... The boot_crunch.conf can be viewed at http://pastebin.com/ZwVPQn3h -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: building crunchgen fails
On Wed, Jan 23, 2013 at 11:01 AM, Devin Teske devin.te...@fisglobal.com wrote: On Jan 23, 2013, at 7:22 AM, Rick Miller wrote: Hi All, When executing crunchgen -o boot_crunch.conf make -f boot_crunch.mk I get the following error: cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo ls.lo test.lo cat.lo df.lo sleep.lo camcontrol.lo dhclient.lo fsck_ffs.lo ifconfig.lo mount_nfs.lo newfs.lo route.lo rtsol.lo tunefs.lo kenv.lo sysctl.lo mdmfs.lo dmesg.lo fdisk.lo bsdlabel.lo uname.lo cpio.lo find.lo minigzip.lo sed.lo awk.lo fetch.lo arp.lo sysinstall.lo usbconfig.lo grep.lo -lcam -lsbuf -lutil -ll -ledit -lfetch -lmd -lcrypt -lftpio -lz -lnetgraph -ldialog -lncurses -ldisk -lufs -ldevinfo -lkvm -lgeom -lbsdxml -larchive -lbz2 -lusb -lgnuregex -llzma -lssl -lcrypto -ljail -lm camcontrol.lo(.text+0x730b): In function `main': : undefined reference to `mode_edit' camcontrol.lo(.text+0x73fa): In function `main': : undefined reference to `mode_list' *** Error code 1 Stop in /tmp/crunchtmp. I understand that there may need to be some shuffling of the libraries in the boot_crunch.conf, but I've done that to no avail. Wondering if anyone else may be able to shed some light on this... The boot_crunch.conf can be viewed at http://pastebin.com/ZwVPQn3h According to the Makefile, if RELEASE_CRUNCH is defined, then modeedit.o object is omitted (causing your undefined references). I perceive the long-term real solution would be to patch camcontrol.c (and pedantically camcontrol.h) to not use mode_edit()/mode_list() when RELEASE_CRUNCH is defined. However, you should be able to get through your problem by adjusting your boot_crunch.conf slightly: Try http://pastebin.com/Ge6UCZEZ The difference being: --- boot_crunch.conf.orig 2013-01-03 16:29:20.0 -0800 +++ boot_crunch.conf2013-01-03 16:29:13.0 -0800 @@ -17,6 +17,7 @@ srcdirs /usr/src/sbin progs camcontrol +special camcontrol objs camcontrol.o modeedit.o util.o progs dhclient progs fsck_ffs progs ifconfig Thanks, Devin! That worked...which Makefile did you find this in? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 8 or 9 on HP ML350 G8
Hi all, I'm just wondering if anyone has any experience running 8 or 9 on the ML350 G8. Is there anything that should be taken into consideration while using these chassis' such as having 2 or more of the built-in RAID controllers activated? Potential issues with disk volumes of varying sizes (like, 2T or more)? Any special BIOS settings or firmware versions? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
mfsroot starts sysinstall how?
Hi all, For anyone interested, I posted a blog with regards to how sysinstall is run from mfsroot. URL is http://blog.hostileadmin.com/2012/12/18/mfsroot-starts-sysinstall-how/ -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
mfsroot starts sysinstall how?
Hi All, How is sysinstall invoked in a FreeBSD 8.x mfsroot.gz? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mfsroot starts sysinstall how?
On Wed, Dec 12, 2012 at 10:44 AM, Rick Miller vmil...@hostileadmin.com wrote: Hi All, How is sysinstall invoked in a FreeBSD 8.x mfsroot.gz? To explain more, I would like to boot into a shell as opposed to sysinstall. safe mode and single user don't seem to. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
make release and mfsroot
Hi All,
I generate a bootonly ISO and want to add files to the mfsroot.gz
created by the release.8 target. I want sysinstall to load an
install.cfg which makes a call to doconfig.sh. The target destination
for the files is stand/. My question is will the below patch
accomplish this for me provided install.cfg and doconfig.sh exist in
/usr/src/release?
# diff -u Makefile.orig Makefile
--- Makefile.orig 2012-12-11 18:15:29.0 +
+++ Makefile2012-12-11 19:01:46.0 +
@@ -509,6 +509,7 @@
rm foo; \
fi
-test -f install.cfg cp install.cfg ${CHROOTDIR}/usr/src/release
+ -test -f doconfig.sh cp doconfig.sh ${CHROOTDIR}/usr/src/release
echo #!/bin/sh ${_MK}
echo set -ex ${_MK}
echo trap 'umount /dev || true' 0 ${_MK}
@@ -823,7 +824,9 @@
done
.endif
-test -f ${.CURDIR}/install.cfg \
-cp ${.CURDIR}/install.cfg ${RD}/mfsfd
+cp ${.CURDIR}/install.cfg ${RD}/mfsfd/stand
+ -test -f ${.CURDIR}/doconfig.sh \
+cp ${.CURDIR}/doconfig.sh ${RD}/mfsfd/stand
@mkdir -p ${RD}/mfsfd/boot
.if ${TARGET_ARCH} != ia64 ${TARGET_ARCH} != powerpc
@cp ${RD}/trees/base/boot/boot* ${RD}/mfsfd/boot
--
Take care
Rick Miller
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: make release and mfsroot
Hi Devin, On Tue, Dec 11, 2012 at 4:22 PM, Devin Teske devin.te...@fisglobal.com wrote: Hi Rick, If you want, you could follow my approach which is to take the completed mfsroot.gz and use a Makefile to manage the creation of custom mfsroots (keeping the original unmodified, making it simpler to test different iterations). Very interesting approach. I like it and will test it. It looks as though I would need to add code to the Makefile if files copied in later are greater in size than the space available. Would you agree? The advantage is that you don't have to re-perform the release(7) process each time you want to make a change to your mfsroot. This is a very compelling advantage. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: make release and mfsroot
On Tue, Dec 11, 2012 at 5:05 PM, Devin Teske devin.te...@fisglobal.com wrote: Though, to resize the mfsroot, I still rely on release(7) and the above patches. Here's another question, have you applied this approach to boot_crunch.conf? I simply replaced the default boot_crunch.conf with my own in the source tree. This is how I discovered MFSSIZE, because the resulting boot_crunch binary was larger than the available space. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD Ports Batch Install
For those interested... hostileadmin.com has published a new blog entitled FreeBSD Ports Batch Install at http://blog.hostileadmin.com/2012/12/10/freebsd-ports-batch-install/ -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: gPXE booting FreeBSD?
On Tue, Dec 4, 2012 at 10:55 AM, Rick Miller vmil...@hostileadmin.com wrote: Hi All, Does anyone have any experience booting FreeBSD via gPXE and have pointers to relevant documentation and/or blog posts? Thanks for all your replies. Our current direction appears to be one of modifying the FreeBSD bootonly ISO to perform installs and load it from gPXE as follows... The menu will appear something like (from memory, syntax may be wrong): kernel memdisk imgargs memdisk raw iso initrd http path to the ISO Once we have it tested and implemented, I'll likely blog the subject at http://blog.hostileadmin.com/ -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: root filesystem and soft-update
On Tue, Dec 4, 2012 at 4:50 PM, Rick Miller vmil...@hostileadmin.com wrote: Hi all, I remember one time seeing a site that explained why soft-updates was not enabled for the root filesystem. I tried looking for it earlier, but failed to locate it. Is there someone who knows where it is? Thanks Steve and Bas. Both answers were helpful. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ipfwNG project?
I came across the wiki doc for ipfwNG (http://wiki.freebsd.org/IpfwNg) and wondered if any of the concepts of this project are currently being developed for FreeBSD and when we might start seeing those concepts included in releng/ code. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
gPXE booting FreeBSD?
Hi All, Does anyone have any experience booting FreeBSD via gPXE and have pointers to relevant documentation and/or blog posts? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: gPXE booting FreeBSD?
Hi Dan, On Tue, Dec 4, 2012 at 11:44 AM, Daniel Feenberg feenb...@nber.org wrote: On Tue, 4 Dec 2012, Rick Miller wrote: Hi All, Does anyone have any experience booting FreeBSD via gPXE and have pointers to relevant documentation and/or blog posts? In the last paragraph of our description of PXE booting FreeBSD: http://www.nber.org/sys-admin/FreeBSD-diskless.html we report that gpxelinux did not work for us. (It hangs once a menu item is selected, or if more than one choice is available). Have you tried and gotten better/worse/similar results? Our trial was about a year ago, it would be worth trying again. Thanks for the reply and link. We've not tried booting FreeBSD from gPXE yet. Our goal is to PXE boot clients into a non-interactive FreeBSD installation. We do this now utilizing pxegrub from Grub2 to pass environment/kernel variables to stage 2 as documented at http://blog.hostileadmin.com/2012/05/04/pxe-booting-into-a-freebsd-installation/ Where $kernel_path is the FreeBSD kernel and $initrd_path is the mfsroot from the release build. The rest of the environment variables are dynamically derived based on data stored in a database for each host. We want to replace pxegrub with gPXE with the hope that we can still pass the environment/kernel variables to stage 2. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
root filesystem and soft-update
Hi all, I remember one time seeing a site that explained why soft-updates was not enabled for the root filesystem. I tried looking for it earlier, but failed to locate it. Is there someone who knows where it is? -- Rick -- Sent from my mobile device Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
gpart and FreeBSD 8.x
For anyone interested, Posted a new blog with regards to gpart on FreeBSD 8.x (with a link to one of Warren's blog posts): http://blog.hostileadmin.com/2012/12/03/freebsd-partitions-and-filesystems-with-gpart/ -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: gpart and FreeBSD 8.x
On Mon, Dec 3, 2012 at 7:49 AM, Julien Cigar jci...@ulb.ac.be wrote: gpart is in BASE on 8.x so there is nothing to install Thanks, Julien! I added a comment to this effect on the post! -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
How do you manage jails?
Hi All, I want to inquire how the majority of users manage jails within their own environments. Do you use the utilities described in the handbook in chapter 16 or some other management facility like qjail or ezjail? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
filesystem size does not equal free space
Hi All, I install FreeBSD 8.3-R on a DL360 G8 with two disk volumes, the 2nd of which is 3TB. The fdisk partition editor shows the disk geometry as 812160 cyl/255 heads/32 sectors = 6627225600 sectors (3235950MB). sysinstall creates a slice on the 3TB volume that uses the entire disk. However, when the filesystem is labelled and mounted, it is slightly over 1TB in size. Am I correct in assuming that it's only 1TB because the disk geometry is greater than what is supported by sysinstall and/or bsdlabel? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
computing kern.maxfilesperproc and kern.maxfiles
Hi All, I just posted a blog about how kern.maxfilesperproc and kern.maxfiles are computed at http://blog.hostileadmin.com/2012/11/12/freebsd-computing-kern-maxfilesperproc-and-kern-maxfiles/ for anyone who may be interested... -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Fault in Terminal Server causing server to hang on boot?
Hi All, I'm reaching out in hopes that someone may have seen something similar and can shed some light. Consider an HP DL360p G8 with FreeBSD 8.3-RELEASE-p4, serial port cabled to a Cisco 2800 series terminal server. Console is configured in the following manner: /boot/loader.conf: console=comconsole /etc/ttys: ttyu0 /usr/libexec/getty std.9600 vt100 on secure The system hangs at boot while the terminal server is cabled to the serial port. Output is displayed on the video console to the point that loader loads /boot/loader.conf. The system freezes. I have no visibility into the terminal server configuration or port which the hardware is cabled, but as soon as the serial cable is pulled from the serial port, the system resumes booting and is remotely accessible (via ssh) when it has come up. Attached to a different terminal server (same model), the system boots fine. Not sure what the fault is on the terminal server. What possible conditions would cause the system to freeze while the serial port is attached? Why would loader care about these conditions? The desired result would be that the system boots completely despite any fault with the terminal server. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 8.3 udp_input() kernel panic
Hi All, I posted a blog yesterday with regards to a FreeBSD kernel panic in FreeBSD 8.3 at http://blog.hostileadmin.com/2012/11/05/freebsd-kernel-panic-in-udp_input/ in case anyone has any interest... -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Burning .iso DVD's
On Fri, Nov 2, 2012 at 5:12 PM, Al Plant n...@hdk5.net wrote: Aloha, I am not able to get a successfull burn of .iso DVD's 9.0 or higher FreeBSD. Chapter 19.7 ... of Handbook says to use growisofs with ATAPI support same as I do for 7.* 8.* FreeBSD etc. I get error of no growisofs ..when I run growisofs -dvd-compat -Z /dev/cd0=image.iso growisofs is part of the dvd+rw-tools port/package. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD help require for DellpowerEdge R620
On Fri, Oct 26, 2012 at 6:54 AM, Md Samadul Sarker s.sar...@switch2link.com wrote: I have got DELL PowerEdge R620 which raid controller is H710. Can anyone help me that is there any chance to install FreeBSD on this and how? Any suggestions will be highly appreciated. I have a couple blog posts related to running FreeBSD on the R620. You may want to read through them. http://blog.hostileadmin.com/2012/05/22/freebsd-on-dell-poweredge-12g-servers/ http://blog.hostileadmin.com/2012/06/30/freebsd-dell-12g-x520-da2-10g-nic/ As far as I am aware, the mfi driver needed to support the H710 RAID controller is only in stable/8 and stable/9 right now. I believe it should be in 9.1-RELEASE, but I could be wrong. If/when 8.4-RELEASE is dropped, it should be in there too. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Adding boot options to the loader menu
Hi All, If you have any interest, I have posted a blog about adding boot options to the loader menu... http://blog.hostileadmin.com/2012/10/11/so-you-want-a-new-freebsd-boot-loader-option/ -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Building a release with custom packages
Hi All, If anyone has interest, I have a new blog post on building a FreeBSD release with custom packages at http://blog.hostileadmin.com/2012/10/08/building-freebsd-media-with-custom-packages/ -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 8.3 with LSI MegaRAID 9265-8i
On Thu, Oct 4, 2012 at 1:52 PM, Joseph Mays m...@win.net wrote: Trying to load FreeBSD 8.3 on to an LSI MegaRAID 9265i volume -- 3 3TB disks for a total volume size of 8.8 TB. The installer program runs from the DVD (we are using 8.3 because we couldn't get a 9.0 boot disk to load at all, actually.) But when it gets to the point of creating partitions it says no hard disk is present. Is this something I should have expected, or am I missing something? That device is based on the SAS2208 chip. I had the same issue (different card, same chip). Check out the blog post below, it may help. http://blog.hostileadmin.com/2012/05/22/freebsd-on-dell-poweredge-12g-servers/ -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 8.x sysisntall dists
On Wed, Sep 26, 2012 at 4:19 PM, Devin Teske devin.te...@fisglobal.com wrote: All patched. http://svn.freebsd.org/changeset/base/240972 Can you test? I'll close the PR upon success. Success! Thanks! -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 8.x sysisntall dists
Hi All, I performed a `make release` with FreeBSD 8.3p4 sources that built a secondary kernel (called DEBUG). It ended up in the release inside kernels/ as expected. The install.cfg file includes the line: dists=base kernels GENERIC SMP DEBUG doc catpages DEBUG was added to the above along with the new release build. All distributions get installed with the exception of DEBUG. In looking through sysinstall sources (I am not much of a C programmer to begin with) and it appears as though the sources need to be modified to support a new DEBUG distribution. I wonder if you might be able to confirm or refute this... -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 8.x sysisntall dists
dists=base kernels GENERIC SMP DEBUG doc catpages DEBUG was added to the above along with the new release build. All distributions get installed with the exception of DEBUG. In looking through sysinstall sources (I am not much of a C programmer to begin with) and it appears as though the sources need to be modified to support a new DEBUG distribution. I wonder if you might be able to confirm or refute this... Confirmed. I'll raise a PR with a patch to correct this. Awesome! Thanks for the quick reply, Devin! If you don't mind, will you pass on the PR so I can track it? I am also considering approaching one of our developers to ask if they can write a patch, would that be helpful? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 8.x sysisntall dists
Confirmed. I'll raise a PR with a patch to correct this. Awesome! Thanks for the quick reply, Devin! If you don't mind, will you pass on the PR so I can track it? Sure, no prob. It should appear in GNATS within 15-20 minutes. I'll get you the PR number when I get my response from GNATS. bin/172096: sysinstall does not support new DEBUG kernel distribution in 8.x I am also considering approaching one of our developers to ask if they can write a patch, would that be helpful? No need. Patch is already written. I'll be submitting it to my mentor for review/approval shortly. Submitted. Excellent, thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Creating kernel distribution from sources
Hi All,
I've generated a DVD iso and imported it into a provisioning platform.
After this integration, a decision was made to rebuild the kernel
with an option enabled. As opposed to executing a full `make
release`, I just want to build the kernel distribution. In reading
the manpage, it looks like I can just run `make release.3 make
release.5 make release.6` to accomplish this. Is this correct?
Would the resulting files be installed in ${CHROOTDIR}/R?
--
Take care
Rick Miller
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Installation Logs for FreeBSD 8.x?
Hi All, Is it possible to write FreeBSD 8.x installation logs onto a resulting FreeBSD 8.x host via sysinstall or some scripting method? I am interested in output one sees during a normal installation plus any warning/error conditions. Ideally, this information will end up on the installed host in a directory within /var. sysinstall docs don't seem to explain any sort of facility to accomplish this. Perhaps there is someone out there who has done something similar that might be able to share their knowledge? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Unable to get crash dump
Hi All, Running 8.3-STABLE 5/21/2012 on HP DL360. While testing crash dump functionality, the dump aborts with the following message: Aborting dump due to I/O error. status == 0xb, scsi status == 0x0 ** DUMP FAILED (ERROR 5) ** Automatic reboot in 5 seconds - press a key on the console to abort Googling and searching freebsd.org have produced what appeared to be some what relevant messages, but I found nothing pointing to a cause and fix. I'm hoping someone might be able to point me in a direction to figuring this out. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: vlan tagging in releng/8.3 not working
On Mon, Aug 13, 2012 at 3:39 PM, Rick Miller vmil...@hostileadmin.com wrote: Hi All, I am running the latest releng/8.3 on a HP DL360 with an Intel 82599 10G NIC using the ixgbe driver. Without vlan tagging, tcpdump sees traffic on the default vlan. With vlan tagging there is no traffic on the interface. Wondering if anyone else has seen similar and/or might be able to provide some additional information? I'm not seeing anything in syslog. The interface is configured via rc.conf: cloned_interfaces=vlan0 ifconfig_vlan0=inet 10.x.x.x netmask=255.255.255.0 vlan $id vlandev ix0 I was missing ifconfig_ix0=up in rc.conf. After inserting this, it worked! -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
vlan tagging in releng/8.3 not working
Hi All, I am running the latest releng/8.3 on a HP DL360 with an Intel 82599 10G NIC using the ixgbe driver. Without vlan tagging, tcpdump sees traffic on the default vlan. With vlan tagging there is no traffic on the interface. Wondering if anyone else has seen similar and/or might be able to provide some additional information? I'm not seeing anything in syslog. The interface is configured via rc.conf: cloned_interfaces=vlan0 ifconfig_vlan0=inet 10.x.x.x netmask=255.255.255.0 vlan $id vlandev ix0 Where $id is our vlan id. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Does FreeBSD start slices at head boundaries?
Hi All, Installing FreeBSD 8.x I select A at the fdisk partition editor to use the entire disk. It creates an unused slice with offset 0 and 63 sectors in size. Then partition 1 starts at sector 63 and utilizes the remaining disk space. Does sysinstall's diskPartitonEditor macro automatically start partitions at head boundaries? The reason I ask is because I am most familiar with sector 64 being the start of a head boundary as opposed to 63. Is my understanding incorrect? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Does FreeBSD start slices at head boundaries?
On Fri, Jul 6, 2012 at 11:19 AM, Ryan Coleman edi...@d3photography.com wrote: Sector 64 is sector 63 when you start at 0. OMG, so right...I cannot believe that went over my head! Thanks for pointing it out. It lets me know that diskPartitionEditor is automatically selecting start and end sectors at boundaries. Thanks! -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Does FreeBSD start slices at head boundaries?
[snip] I think Ryan means partition and not slice? I would not recommend no slices at all, It's deprecated to use dangerously dedicated disks First of all, it's dedicated disks, there's nothing dangerous related. :-) If you are using the MBR approach (old way), you can do either creating a DOS primary partition, a slice, which then will contain your partitions: a swap partition and one or more UFS partitions. So you have ad0s1a, ad0s1b and so on. When you omit the slice and create the partitions on the bare disk, you have a dedicated layout. FreeBSD will run with it without any problem. It _may_ be possible that some systems like Windows have trouble with this approach, but if you're going to use FreeBSD only on that disk, there is no danger, no problem. You have ad0a, ad0b and so on. If you are using the GPT approach (new way), you create partitions using a different tool set, setting them to be a file system or a swap partition. You end up in ad0p1, ad0p2 and so on. Note that those aren't DOS primary partitions anymore, outdated systems may not properly recognize them. If you label your partitions (you can do that with both approaches), you don't need to deal with device names at all. Thanks for this explanation. Is there any performance advantage to using a dedicated disk layout over the old way of creating a slice and having your partitions within it? [snip] To OP: If you omit the slice and just create two partitions (one for FS and one for swap), FreeBSD will use this fine. Just make sure to set the boot parameters properly. Or simply use the GPT-related tools, so you don't have to deal with the question at all. Thanks again for the concise explanation. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Does FreeBSD start slices at head boundaries?
I went through this exercise to determine if there were boundary issues installing FreeBSD on disks. I concluded that FreeBSD was indeed installing at head boundaries. A colleague then pointed me to http://ivoras.net/blog/tree/2011-01-01.freebsd-on-4k-sector-drives.html which calls into question whether sysinstall and fdisk really are installing FreeBSD's slice at the 64th cylinder. Should I be concerned with this? This came about due to a scenario where Linux would start its filesystem at sector 63, right before the head boundary. On I/O intensive applications, it was common for reads/write to cross the head boundary resulting in unnecessary disk thrashing and long I/O wait times. The issue was corrected in Linux by changing the start cylinder to 2048. Some theorized that FreeBSD was vulnerable to this scenario. Thoughts/feedback? On Fri, Jul 6, 2012 at 11:09 AM, Rick Miller vmil...@hostileadmin.com wrote: Hi All, Installing FreeBSD 8.x I select A at the fdisk partition editor to use the entire disk. It creates an unused slice with offset 0 and 63 sectors in size. Then partition 1 starts at sector 63 and utilizes the remaining disk space. Does sysinstall's diskPartitonEditor macro automatically start partitions at head boundaries? The reason I ask is because I am most familiar with sector 64 being the start of a head boundary as opposed to 63. Is my understanding incorrect? -- Take care Rick Miller -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 8-STABLE on R620 w/ X520-DA2/Intel 82599
Hi All, I have 2 hosts, HP DL360 G8 and Dell R620. Both have the X520-DA2/Intel 82599 10G Fiber NIC. Both also have the same FreeBSD 8-STABLE image. The Dell displays the following in dmesg and we are unable to configure the ix0 or ix1 interfaces where the HP works just fine. Wondering if anyone else has experienced this? pci4: network, ethernet at device 0.0 (no driver attached) pci4: network, ethernet at device 0.1 (no driver attached) -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 8-STABLE on R620 w/ X520-DA2/Intel 82599
On Fri, Jun 29, 2012 at 11:56 AM, Gary Palmer gpal...@freebsd.org wrote: On Fri, Jun 29, 2012 at 10:50:52AM -0400, Rick Miller wrote: Hi All, I have 2 hosts, HP DL360 G8 and Dell R620. Both have the X520-DA2/Intel 82599 10G Fiber NIC. Both also have the same FreeBSD 8-STABLE image. The Dell displays the following in dmesg and we are unable to configure the ix0 or ix1 interfaces where the HP works just fine. Wondering if anyone else has experienced this? pci4: network, ethernet at device 0.0 (no driver attached) pci4: network, ethernet at device 0.1 (no driver attached) Please see http://lists.freebsd.org/pipermail/freebsd-net/2012-June/032579.html it may be of some assistance. It looks like adding the Dell specific PCI IDs may be all thats required. Hrmm, very interesting indeed. How do I identify if/when/where the source has been updated? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 8-STABLE on R620 w/ X520-DA2/Intel 82599
On Fri, Jun 29, 2012 at 11:56 AM, Gary Palmer gpal...@freebsd.org wrote: On Fri, Jun 29, 2012 at 10:50:52AM -0400, Rick Miller wrote: Hi All, I have 2 hosts, HP DL360 G8 and Dell R620. Both have the X520-DA2/Intel 82599 10G Fiber NIC. Both also have the same FreeBSD 8-STABLE image. The Dell displays the following in dmesg and we are unable to configure the ix0 or ix1 interfaces where the HP works just fine. Wondering if anyone else has experienced this? pci4: network, ethernet at device 0.0 (no driver attached) pci4: network, ethernet at device 0.1 (no driver attached) Please see http://lists.freebsd.org/pipermail/freebsd-net/2012-June/032579.html it may be of some assistance. It looks like adding the Dell specific PCI IDs may be all thats required. We removed an Intel branded equivalent from the DL360 and tried it in the R620. It detected it no problem. Only problem was we could not see it in the BIOS, not a huge deal to us. -- Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: sysinstall diskPartitionEditor Question
On Tue, Jun 26, 2012 at 10:30 AM, Rick Miller vmil...@hostileadmin.com wrote: Hi All, I'd like to set the offset/starting cylinder in install.cfg so that partitions begin on appropriate boundaries. The applicable section of install.cfg looks like the following. My assumption is that I need to make the changes in the partition section. Is this correct? Is the format of this value the same as a typical fdisk config file? After copious amounts of reading and experimenting. It seems as though diskPartitionEdit doesn't support specifying a starting cylinder. When I specify partition=all, it starts that slice at sector 63. I'd like to start it at 64 or above. Is it feasible to include gpart in the mfsroot and use that to partition the drive before sysinstall continues with the installation? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
sysinstall diskPartitionEditor Question
Hi All,
I'd like to set the offset/starting cylinder in install.cfg so that
partitions begin on appropriate boundaries. The applicable section of
install.cfg looks like the following. My assumption is that I need to
make the changes in the partition section. Is this correct? Is the
format of this value the same as a typical fdisk config file?
### Begin install.cfg snippet
disk=\${disk}
partition=all
bootManager=standard
diskPartitionEditor
# root
\${disk}s1-1=ufs 12582912 /
# swap
\${disk}s1-2=swap ${swap} none
# tmp
\${disk}s1-3=ufs 2097152 /tmp 1
# 2 GB var
\${disk}s1-4=ufs 4194304 /var 1
# 2 GB home
\${disk}s1-5=ufs 4194304 /home 1
diskLabelEditor
### End snippet
--
Take care
Rick Miller
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Intel X520-DA2 Supported in stable/8?
On Fri, Jun 22, 2012 at 7:23 PM, Jack Vogel jfvo...@gmail.com wrote: Would probably be good to take care of the storm threshold if you haven't, set it to 0 and you disable the check, that's what we do internally. As for the queues and number of descriptors, that's kind of up to you, different work loads and environments work best with different setups. Hopefully, when you get rid of the rx ring setup failure you will get things working. Thanks, Jack. I did get rid of the rx ring failure. Link status still shows no carrier. I think everything looks right from the host's perspective. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Intel X520-DA2 Supported in stable/8?
Turns out the gbic in the switch was bad...I didn't think there was a problem on the host, but you all still gave me some good info. I appreciate it! On 6/25/12, Rick Miller vmil...@hostileadmin.com wrote: On Fri, Jun 22, 2012 at 7:23 PM, Jack Vogel jfvo...@gmail.com wrote: Would probably be good to take care of the storm threshold if you haven't, set it to 0 and you disable the check, that's what we do internally. As for the queues and number of descriptors, that's kind of up to you, different work loads and environments work best with different setups. Hopefully, when you get rid of the rx ring setup failure you will get things working. Thanks, Jack. I did get rid of the rx ring failure. Link status still shows no carrier. I think everything looks right from the host's perspective. -- Take care Rick Miller -- Sent from my mobile device Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Intel X520-DA2 Supported in stable/8?
Hi All, Wondering if the Intel X520-DA2 10G Fibre NIC is supported in stable/8. Hardware notes don't specify it, but I have a system up and the interfaces appear to be loaded by the ix driver. However, status indicates no carrier. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Intel X520-DA2 Supported in stable/8?
On Fri, Jun 22, 2012 at 3:13 PM, Rick Miller vmil...@hostileadmin.com wrote: Hi All, Wondering if the Intel X520-DA2 10G Fibre NIC is supported in stable/8. Hardware notes don't specify it, but I have a system up and the interfaces appear to be loaded by the ix driver. However, status indicates no carrier. Ok, brain fart. Please forgive my ineptitude. I once sent an email inquiring about the Intel 82599, which is this NIC. Responses to that mail say it's supported by the ixgbe driver. My stable/8 installation (5/21/2012) probes it with an ix driver that I cannot find any info on. The ixgbe manage indicates it only supports 82598 based controllers. Not sure what to think here... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Intel X520-DA2 Supported in stable/8?
On Fri, Jun 22, 2012 at 3:54 PM, Andrew Boyer abo...@averesystems.com wrote: The ixgbe driver creates devices named ix0, etc. I believe you need to run 'ifconfig ix0 up' before it will attempt to get link. Thanks for clarifying that tidbit. At least I know the driver loading is the correct driver :) I did try ifup'ing the interface...it shows the interface up, status is still no carrier. I've had confirmation that the cable itself is good. I wonder if it matters that the upstream switch has VLAN tagging enabled? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Intel X520-DA2 Supported in stable/8?
dmesg and ifconfig output below... On Fri, Jun 22, 2012 at 4:02 PM, Rick Miller vmil...@hostileadmin.com wrote: On Fri, Jun 22, 2012 at 3:54 PM, Andrew Boyer abo...@averesystems.com wrote: The ixgbe driver creates devices named ix0, etc. I believe you need to run 'ifconfig ix0 up' before it will attempt to get link. Thanks for clarifying that tidbit. At least I know the driver loading is the correct driver :) I did try ifup'ing the interface...it shows the interface up, status is still no carrier. I've had confirmation that the cable itself is good. I wonder if it matters that the upstream switch has VLAN tagging enabled? ix0: Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 2.4.5 port 0x7000-0x701f mem 0xf6b8-0xf6bf,0xf6b7-0xf6b73fff irq 40 at device 0.0 on pci7 ix0: Using MSIX interrupts with 9 vectors ix0: RX Descriptors exceed system mbuf max, using default instead! ix0: [ITHREAD] ix0: [ITHREAD] ix0: [ITHREAD] ix0: [ITHREAD] ix0: [ITHREAD] ix0: [ITHREAD] ix0: [ITHREAD] ix0: [ITHREAD] ix0: [ITHREAD] ix0: Ethernet address: 90:e2:ba:15:e2:60 ix0: PCI Express Bus: Speed 5.0Gb/s Width x8 ix1: Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 2.4.5 port 0x7020-0x703f mem 0xf6a8-0xf6af,0xf6a7-0xf6a73fff irq 44 at device 0.1 on pci7 ix1: Using MSIX interrupts with 9 vectors ix1: RX Descriptors exceed system mbuf max, using default instead! ix1: [ITHREAD] ix1: [ITHREAD] ix1: [ITHREAD] ix1: [ITHREAD] ix1: [ITHREAD] ix1: [ITHREAD] ix1: [ITHREAD] ix1: [ITHREAD] ix1: [ITHREAD] ix1: Ethernet address: 90:e2:ba:15:e2:61 ix1: PCI Express Bus: Speed 5.0Gb/s Width x8 ix0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=401bbRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO ether 90:e2:ba:XX:XX:XX inet 10.1.2.50 netmask 0xfe00 broadcast 10.1.3.255 media: Ethernet autoselect status: no carrier ix1: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 options=401bbRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO ether 90:e2:ba:XX:XX:XX media: Ethernet autoselect status: no carrier -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Intel X520-DA2 Supported in stable/8?
On Fri, Jun 22, 2012 at 5:21 PM, Jack Vogel jfvo...@gmail.com wrote: Increase your system mbuf pool size, you do not want that failure to happen. Thanks, Jack. I saw a thread where you discussed this. You are referring to kern.ipc.nmbclusters, correct? Should I also adjust the following? hw.ixgbe.rxd hw.ixgbe.txd hw.ixgbe.num_queues hw.intr_storm_threshold ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD compatibility with HP ProLiant DL360p Generation 8 (Gen8) ?
Reply inline... On Thu, Jun 14, 2012 at 6:41 AM, Olivier Mueller om-lists-...@omx.ch wrote: Hello, I need to order a few more servers for an internal project, and instead of the usual DL360G7 we now use without any problem with FreeBSD, there would now be the next generation, called Gen8. Intel® C600 Series Chipset Intel® E5-2600 Processor Family Storage Controller : HP Smart Array P420i/1GB Network Controller : HP Ethernet 1Gb 4-port 331FLR Adapter (full specs: http://h18000.www1.hp.com/products/quickspecs/14211_na/14211_na.pdf ) I cannot comment on 9.x as we have not yet tested it on the 360p G8. I can, however, say that we did not have problems with the RAID controller with stable/8. We did have problems with the on-board NIC, I don't remember what model it is, but it is based on the BCM5719 controller. We ordered a few PCIe Intel NICs and tried the 82571 which did work with stable/8. We've got on order a few of the HP NC361T, which is based on the Intel i350, which we tested in a Dell and it worked there. Again, all this is with stable/8, but generally if the driver works in 8, it will work in 9. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
How do I determine support for $xx?
Hi All, If this question is better suited for a different list please let me know. Simply stated, my question is 'What is the best source for identifying supported hardware?'. Having said that, allow me to pose an example... I've attempted to identify if various ethernet controllers are supported by FreeBSD and the drivers. I used the hardware notes and manpages for the respective ethernet drivers. The information between the two sometimes seems inconsistent and/or inaccurate. For example, the BCM5719 and BCM5720 are unsupported in FreeBSD at this time. The hardware notes at freebsd.org do not specify these controllers are supported. Inspection of the bge(4) manpage implies that the controllers are supported as seen in the description section where it states: The bge driver provides support for various NICs based on the Broadcom BCM570x, 571x, 572x, 575x, 576x, 578x, 5776x and 5778x Gigabit Ethernet controller chips and the 590x and 5779x Fast Ethernet controller chips. I browsed the source and found many references to the BCM5719 and BCM5720. However, I am unfamiliar enough with driver programming in C to identify if a controller is fully supported. Also, I attempted to identify whether the Intel i350 is supported. It's not listed in the hardware notes or the igb(4) manpage so I suspect it is not supported. When I view the igb source, the i350 is referenced numerous times. Are these references simply code in preparation for support of the i350? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How do I determine support for $xx?
Matthew/Devin, Thanks for the feedback.
After I sent this email, I determined that the Intel i350 is indeed
supported as a machine I built with FreeBSD was utilizing this NIC.
I've tried the BCM5719 with stable/8 (5/21/2012) and it kernel panics
when the interface is configured. I was told by a source contributor
that the BCM5720 does not work (confirmed as recently as within the
last week), but I've not tested it. I'm just passing this on as
information...I don't expect any feedback with regards to this.
On Fri, Jun 8, 2012 at 1:06 PM, Devin Teske devin.te...@fisglobal.com wrote:
On Jun 8, 2012, at 9:45 AM, Devin Teske wrote:
Hi Rick (!),
On Jun 8, 2012, at 8:07 AM, Rick Miller wrote:
[snip]
I browsed the source and found many references to the BCM5719 and
BCM5720. However, I am unfamiliar enough with driver programming in C
to identify if a controller is fully supported.
[snip]
If you were running, say, 8.0-R, even if you have the bge(4) driver loaded,
you would see this in /var/run/dmesg.boot:
pciN: unknown card (vendor=0x1106, dev=0x165f) at X.Y
Correction, (specific to BCM5720) you'd see:
pciN: unknown card (vendor=0x14e4, dev=0x165f) at X.Y
Which, btw, you can confirm to yourself by executing the following within
8.3-R (with attached bge(4)):
$ pciconf -lv | awk '/^bge/{print $1,$4}'
bge0@pciN:A:B:C: chip=0x165f14e4
Otherwise, you can see an unknown (non-working bge(4)) Broadcom BCM5720
hardware by executing (on 8.0-R for example):
$ grep unk /var/run/dmesg.boot | grep 0x14e4
pciN: unknown card (vendor=0x14e4, dev=0x165f) at X.Y
NOTE: On a system where all hardware is probed/attached, grep unk
/var/run/dmesg.boot should not produce any results. In this case, pciconf is
your tool for probing vendor/device IDs.
NOTE: Insert random numbers for N, and X.Y
How you know that 8.3-R's bge(4) driver supports the BCM5720 is because this
source file:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bgereg.h?annotate=1.83.2.35.2.1
NOTE: I specifically pointed you at CVS instead of SVN so that you can see
the version tagged for 8.3-R
Specifically, this line:
2309: #define BCOM_DEVICEID_BCM5720 0x165F
[snip]
--
Devin
_
The information contained in this message is proprietary and/or confidential.
If you are not the intended recipient, please: (i) delete the message and all
copies; (ii) do not disclose, distribute or use the message in any manner;
and (iii) notify the sender immediately. In addition, please be aware that
any message addressed to our domain is subject to archiving and review by
persons other than the intended recipient. Thank you.
--
Take care
Rick Miller
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Support for Intel 82599ES?
Hi All, I did not see the Intel 82599ES chipset in the hardware release notes for 8.3 or 9.0. Are these controllers supported at this time? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Support for Intel 82599ES?
Thanks, Michael! I took a look at the manpage and it does appear that it is supported by the bge driver. It also states that the 572x controller is also supported, but I heard a rumor stating that the BCM5720 in particular did not work even though the manpage indicates it is supported. I was unable to verify this, but that's why I was asking for clarification. I will assume it works at this point. On Fri, Jun 1, 2012 at 1:25 PM, Michael Butler i...@protected-networks.net wrote: On 06/01/12 13:06, Rick Miller wrote: Thanks, Jack! Also another support question for the listsIs the Broadcom BCM5719 supported? I can find neither in the hardware notes for 8.3 nor 9.0. man bge -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Need some help building bootcrunch
Hi All, I am attempting to build a bootcrunch file that I will inject into an mfsroot. I'm unable to get it built completely and hoping someone might be able to help me identify the issue. crunchgen runs and exits without issue. Running make fails with the following error indicating it's not able to find, presumably, libmd which exists. /usr/lib/libfetch.a(http.o)(.text+0x8c0): In function `http_authorize':: undefined reference to `MD5Init' /usr/lib/libfetch.a(http.o)(.text+0x8d5): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0x8e7): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0x8fc): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0x90e): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0x923): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0x933): In function `http_authorize':: undefined reference to `MD5Final' /usr/lib/libfetch.a(http.o)(.text+0x991): In function `http_authorize':: undefined reference to `MD5Init' /usr/lib/libfetch.a(http.o)(.text+0x9a3): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0x9b5): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0x9ca): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0x9f9): In function `http_authorize':: undefined reference to `MD5Final' /usr/lib/libfetch.a(http.o)(.text+0xa11): In function `http_authorize':: undefined reference to `MD5Init' /usr/lib/libfetch.a(http.o)(.text+0xa21): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xa33): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xa48): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xa5a): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xa88): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xa93): In function `http_authorize':: undefined reference to `MD5Final' /usr/lib/libfetch.a(http.o)(.text+0xcc0): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xcd2): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xd1c): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xd2e): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xd47): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xd59): more undefined references to `MD5Update' follow /usr/lib/libfetch.a(http.o)(.text+0xdaa): In function `http_authorize':: undefined reference to `MD5Init' /usr/lib/libfetch.a(http.o)(.text+0xdbf): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xdd1): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xdea): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xdfc): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xe46): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xe56): In function `http_authorize':: undefined reference to `MD5Final' *** Error code 1 Stop in bootcrunch. This is the bootcrunch.conf (as you can see, -lmd exists on the libs lines): buildopts -DRELEASE_CRUNCH -Dlint srcdirs /usr/src/bin progs hostname progs pwd progs rm progs sh progs ls progs test progs cat progs df progs sleep ln sh -sh ln test [ srcdirs /usr/src/sbin #progs camcontrol progs dhclient progs fsck_ffs progs ifconfig progs mount_nfs progs newfs progs route progs rtsol progs tunefs progs kenv progs sysctl progs mdmfs progs dmesg ln fsck_ffs fsck_4.2bsd ln fsck_ffs fsck_ufs srcdirs /usr/src/usr.bin progs uname progs cpio progs find progs minigzip progs sed progs awk progs fetch progs ifconfig ln minigzip gzip ln minigzip gunzip ln minigzip zcat srcdirs /usr/src/usr.sbin progs arp progs sysinstall progs usbconfig srcdirs /usr/src/gnu/usr.bin progs grep libs -ll -ledit -lutil -lmd -lcrypt -lftpio -lz -lnetgraph libs -ldialog -lncurses -ldisk -lcam -lsbuf -lutil -lufs -ldevinfo -lkvm libs -lbsdxml -larchive -lbz2 -lusb -lgnuregex -lz -llzma libs -lfetch -lmd -lssl -lcrypto -ljail -lm -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd
Re: Need some help building bootcrunch
I changed some things around in the bootcrunch.conf and got it to work. It was building 'fetch'. I moved -lfetch before -lmd and it compiled fine. On Wed, May 30, 2012 at 10:36 AM, Rick Miller vmil...@hostileadmin.com wrote: Hi All, I am attempting to build a bootcrunch file that I will inject into an mfsroot. I'm unable to get it built completely and hoping someone might be able to help me identify the issue. crunchgen runs and exits without issue. Running make fails with the following error indicating it's not able to find, presumably, libmd which exists. /usr/lib/libfetch.a(http.o)(.text+0x8c0): In function `http_authorize':: undefined reference to `MD5Init' /usr/lib/libfetch.a(http.o)(.text+0x8d5): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0x8e7): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0x8fc): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0x90e): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0x923): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0x933): In function `http_authorize':: undefined reference to `MD5Final' /usr/lib/libfetch.a(http.o)(.text+0x991): In function `http_authorize':: undefined reference to `MD5Init' /usr/lib/libfetch.a(http.o)(.text+0x9a3): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0x9b5): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0x9ca): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0x9f9): In function `http_authorize':: undefined reference to `MD5Final' /usr/lib/libfetch.a(http.o)(.text+0xa11): In function `http_authorize':: undefined reference to `MD5Init' /usr/lib/libfetch.a(http.o)(.text+0xa21): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xa33): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xa48): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xa5a): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xa88): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xa93): In function `http_authorize':: undefined reference to `MD5Final' /usr/lib/libfetch.a(http.o)(.text+0xcc0): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xcd2): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xd1c): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xd2e): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xd47): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xd59): more undefined references to `MD5Update' follow /usr/lib/libfetch.a(http.o)(.text+0xdaa): In function `http_authorize':: undefined reference to `MD5Init' /usr/lib/libfetch.a(http.o)(.text+0xdbf): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xdd1): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xdea): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xdfc): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xe46): In function `http_authorize':: undefined reference to `MD5Update' /usr/lib/libfetch.a(http.o)(.text+0xe56): In function `http_authorize':: undefined reference to `MD5Final' *** Error code 1 Stop in bootcrunch. This is the bootcrunch.conf (as you can see, -lmd exists on the libs lines): buildopts -DRELEASE_CRUNCH -Dlint srcdirs /usr/src/bin progs hostname progs pwd progs rm progs sh progs ls progs test progs cat progs df progs sleep ln sh -sh ln test [ srcdirs /usr/src/sbin #progs camcontrol progs dhclient progs fsck_ffs progs ifconfig progs mount_nfs progs newfs progs route progs rtsol progs tunefs progs kenv progs sysctl progs mdmfs progs dmesg ln fsck_ffs fsck_4.2bsd ln fsck_ffs fsck_ufs srcdirs /usr/src/usr.bin progs uname progs cpio progs find progs minigzip progs sed progs awk progs fetch progs ifconfig ln minigzip gzip ln minigzip gunzip ln minigzip zcat srcdirs /usr/src/usr.sbin progs arp progs sysinstall progs usbconfig srcdirs /usr/src/gnu/usr.bin progs grep libs -ll -ledit -lutil -lmd -lcrypt -lftpio -lz -lnetgraph
FreeBSD 8.3 support for LSI SAS 2208 based controllers/Dell PERC 710
Hi All, I have a Dell R620 which utilizes the PERC H710 controller based on the LSI SAS 2208 chip. According to the hardware notes for 8.3-RELEASE, this chip is supported by the mps driver. Unfortunately, when I attempt to install 8.3-RELEASE via DVD, it does not recognize the controller and no disks are found and the install exits. The manpage indicates the driver was introduced in 9.0-RELEASE suggesting it was backported to 8.3? Would this be correct? A search for related bug reports did not return anything useful. Would anyone else out there have any experience with installing FreeBSD on the R620 and be able to provide any tips for troubleshooting? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Running OS tftp vs. pxeboot tftp
Thanks for your feedback. I agree that separating the networks and isolating the build network thus eliminating the need for VLAN tagging is the ideal scenario. Unfortunately, influencing those changes are beyond my sphere of influence in this particular case. At the end of the day, our solution was to replace pxeboot.bs with Grub2pxe. I have a blog post detailing the scenario at https://hostileadmin.wordpress.com/2012/05/04/pxe-booting-into-a-freebsd-installation/ On Wed, Mar 14, 2012 at 9:30 AM, Erik Nørgaard norga...@locolomo.org wrote: Hi On 14/03/2012 11:44, Rick Miller wrote: I thought I would follow up on this as a couple individuals expressed an interest in it... We have isolated the configuration in which this occurs under. It occurs during the execution of pxeboot.bs on brocade switches with vlan tagging enabled. You might save yourself time and money buying a cheap switch and doing your jumpstart install on a separate closed network completely isolated from the rest of your networks, without VLAN tagging required. If you have lots of nodes to install it makes sense to maintain your own repository of freebsd and packages, and it's good practice to keep your preproduction systems separate from production, so there is no need for network access. BR, Erik -- M: +34 666 334 818 T: +34 915 211 157 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: pxegrub + FreeBSD install
I was able to figure out how to pass the variables to the FreeBSD
mfsroot. I did so by modifying the grub.cfg file like the below:
menuentry freebsd82-x86_64 {
kfreebsd /boot/kernel/kernel
kfreebsd_loadenv /boot/device.hints
kfreebsd_module /boot/mfsroot.gz type=mfs_root
set kFreeBSD.vfs.root.mountfrom=ufs:/dev/md0c
set kFreeBSD.boot.nfsroot.server=$pxe_default_server
set kFreeBSD.boot.netif.hwaddr=$net_pxe_mac
set kFreeBSD.boot.netif.ip=$net_pxe_ip
set kFreeBSD.dhcp.host-name=$net_pxe_hostname
}
On Tue, Apr 24, 2012 at 2:10 PM, Rick Miller vmil...@hostileadmin.com wrote:
Hi All,
I am attempting to build FreeBSD 8.x-RELEASE over the network via PXE.
I chain pxegrub to pxelinux and load the FreeBSD kernel and mfsroot
through pxegrub with the following:
menuentry freebsd-x86_64 {
kfreebsd /boot/kernel/kernel
kfreebsd_loadenv /boot/device.hints
kfreebsd_module /boot/mfsroot.gz type=mfs_root
set kFreeBSD.vfs.root.mountfrom=ufs:/dev/md0c
}
The mfsroot.gz is from the installation DVD with a couple of scripts
and an install.cfg which result in a non-interactive install. I set
variables necessary to allow sysinstall to retrieve the expected
files. The variables (previously) are populated as follows:
server=`kenv -q boot.nfsroot.server`
mac=`kenv -q boot.netif.hwaddr`
ip=`kenv -q boot.netif.ip`
nm=`kenv -q boot.netif.netmask`
gw=`kenv -q boot.netif.gateway`
name=`kenv -q dhcp.host-name`
route=`kenv -q dhcp.routers`
The mfsroot.gz does not see these as set when the environment loads
through pxegrub. If I load the environment through pxeboot.bs, the
variables populate ok. Unfortunately, with pxeboot.bs I experience
extremely high tftp failure rates when compared to pxegrub.
My question is how should I populate these variables in the mfsroot.gz
when loading via pxegrub?
--
Take care
Rick Miller
--
Take care
Rick Miller
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
pxegrub + FreeBSD install
Hi All,
I am attempting to build FreeBSD 8.x-RELEASE over the network via PXE.
I chain pxegrub to pxelinux and load the FreeBSD kernel and mfsroot
through pxegrub with the following:
menuentry freebsd-x86_64 {
kfreebsd /boot/kernel/kernel
kfreebsd_loadenv /boot/device.hints
kfreebsd_module /boot/mfsroot.gz type=mfs_root
set kFreeBSD.vfs.root.mountfrom=ufs:/dev/md0c
}
The mfsroot.gz is from the installation DVD with a couple of scripts
and an install.cfg which result in a non-interactive install. I set
variables necessary to allow sysinstall to retrieve the expected
files. The variables (previously) are populated as follows:
server=`kenv -q boot.nfsroot.server`
mac=`kenv -q boot.netif.hwaddr`
ip=`kenv -q boot.netif.ip`
nm=`kenv -q boot.netif.netmask`
gw=`kenv -q boot.netif.gateway`
name=`kenv -q dhcp.host-name`
route=`kenv -q dhcp.routers`
The mfsroot.gz does not see these as set when the environment loads
through pxegrub. If I load the environment through pxeboot.bs, the
variables populate ok. Unfortunately, with pxeboot.bs I experience
extremely high tftp failure rates when compared to pxegrub.
My question is how should I populate these variables in the mfsroot.gz
when loading via pxegrub?
--
Take care
Rick Miller
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Find run-time dependancies recursively for FreeBSD port
Hi all, I can get run-time depends by executing make run-depends-list or all dependancies by running make all-depends-list. Is there a way to get all run-time depends recursively (I don't need the build depends or their depends)? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Find run-time dependancies recursively for FreeBSD port
Thanks Greg, I just found the following link in the list archives which gave me an idea that I am currently working on... http://osdir.com/ml/freebsd-questions/2009-04/msg00929.html On Wed, Mar 21, 2012 at 1:15 PM, Greg Larkin glar...@freebsd.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 3/21/12 12:51 PM, Rick Miller wrote: Hi all, I can get run-time depends by executing make run-depends-list or all dependancies by running make all-depends-list. Is there a way to get all run-time depends recursively (I don't need the build depends or their depends)? Hi Rick, The closest I see in bsd.port.mk are the following targets, but I think they include LIB_DEPENDS as well: package-depends-list actual-package-depends Hope that helps, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9qDLUACgkQ0sRouByUApDiqgCguy0v3CoiLLGpKWmcTkwmYelU NJ4AoISFXcPtr00gxcKH+3SPHstnFwRs =IZU/ -END PGP SIGNATURE- -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Find run-time dependancies recursively for FreeBSD port
Thanks Matthew... On Wed, Mar 21, 2012 at 2:35 PM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: On 21/03/2012 16:51, Rick Miller wrote: I can get run-time depends by executing make run-depends-list or all dependancies by running make all-depends-list. Is there a way to get all run-time depends recursively (I don't need the build depends or their depends)? If your INDEX is up to date: % cd /usr/ports % make search name=packagename-1.2.3 display=rdeps or % make search path=devel/foo display=rdeps The problem here is that this does not return recursive results, meaning run-time dependancies of run-time dependancies. Having said that, These commands provide me some alternatives in a script I am writing to ascertain this data for me. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Find run-time dependancies recursively for FreeBSD port
Yes it does. pebcak, thanks. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Running OS tftp vs. pxeboot tftp
I thought I would follow up on this as a couple individuals expressed an interest in it... We have isolated the configuration in which this occurs under. It occurs during the execution of pxeboot.bs on brocade switches with vlan tagging enabled. We have begun to review the pxeboot.bs source code in order to get more debug information out of it and have opened a support case with Brocade. On Thu, Mar 1, 2012 at 10:16 AM, Rick Miller vmil...@hostileadmin.com wrote: Hi All, Are there significant differences in the implementation between the tftp client in FreeBSD 8.2-RELEASE and the client implementation in pxeboot.bs? I ask because I have encountered a scenario where pxeboot.bs is tftp'ing boot files from a PXE server and fails in random spots while attempting to download boot files to start a 8.2-RELEASE install. When we run the same sequence of tftp gets in a running 8.2-RELEASE instance continuously, we never received a single failure in a solid hour of attempts. -- Take care Rick Miller -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Running OS tftp vs. pxeboot tftp
Hi Erik, Thanks for getting back to me. The original problem is the same issue...we are still working it, but we've isolated the configuration where the issue manifests itself. It has to do with the FreeBSD pxeboot and Brocade switches. We will continue troubleshooting in our lab. When we've identified a fix/workaround I will be sure to follow up here. On 3/4/12, Erik Nørgaard norga...@locolomo.org wrote: On 01/03/2012 16:16, Rick Miller wrote: Hi All, Are there significant differences in the implementation between the tftp client in FreeBSD 8.2-RELEASE and the client implementation in pxeboot.bs? I have no reason to believe there should be any difference. If you believe there is a problem with the supplied pxeboot, you can compile your own. You previusly wrote about VLAN tagging for your pxeboot nodes, but never wrote back if you solved the problem. What's your setup? I ask because I have encountered a scenario where pxeboot.bs is tftp'ing boot files from a PXE server and fails in random spots while attempting to download boot files to start a 8.2-RELEASE install. When we run the same sequence of tftp gets in a running 8.2-RELEASE instance continuously, we never received a single failure in a solid hour of attempts. You should have some log or other traces to debug on the problem, can't help much without. BR, Erik -- M: +34 666 334 818 T: +34 915 211 157 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Sent from my mobile device Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Running OS tftp vs. pxeboot tftp
Hi All, Are there significant differences in the implementation between the tftp client in FreeBSD 8.2-RELEASE and the client implementation in pxeboot.bs? I ask because I have encountered a scenario where pxeboot.bs is tftp'ing boot files from a PXE server and fails in random spots while attempting to download boot files to start a 8.2-RELEASE install. When we run the same sequence of tftp gets in a running 8.2-RELEASE instance continuously, we never received a single failure in a solid hour of attempts. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
8.2-RELEASE sysinstall creates duplicate rc.conf lines
Hi all, We recently discovered that sysinstall appears to be adding it's own lines to /etc/rc.conf which are duplicates of lines that we are inserting during builds. For example, on one of our hosts, we are adding defaultrouter and ifconfig_em0 with certain network configurations. When we reboot the system we find that sysinstall also inserted a defaultrouter and ifconfig_em0 populated with the data that existed on the interface during the build. See a sample of the rc.conf below. We are making use of the keeprcconf in the install.cfg, but this does not prevent sysinstall from adding those lines. Is there some way to prevent this behavior? # Sample rc.conf after sysinstall build defaultrouter=10.0.0.1 defaultrouter=192.168.0.1 hostname=bsdtest ifconfig_em0=inet 10.0.0.2 netmask 255.255.252.0 ifconfig_em0=inet 192.168.0.2 netmaks 255.255.255.0 sshd_enable=YES -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
pxeboot.bs and vlan tagging
Hi All, We are PXE booting into FreeBSD 8.2-RELEASE to perform system builds. The pxeboot.bs file was recompiled with TFTP support. 8.2-RELEASE builds were working fine until we attempted a build on bare metal in an environment that utilizes vlan tagging. When the system loaded the pxeboot.bs file it prompted that a disk containing the mfsroot.gz be inserted. I have a couple of questions that I am hoping I can use to glean a proper solution: 1) Does the 8.2-RELEASE pxeboot.bs source code support use of vlan tagging? 2) Can I get vlan tagging support with newer 8.2 code? 3) Will the 9.0-RELEASE code have better support for vlan tagging and can I use it to build an 8.2-RELEASE system? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: pxeboot.bs and vlan tagging
See my responses inline... On Mon, Feb 6, 2012 at 10:54 AM, Erik Nørgaard norga...@locolomo.org wrote: On 06/02/2012 16:35, Rick Miller wrote: We are PXE booting into FreeBSD 8.2-RELEASE to perform system builds. The pxeboot.bs file was recompiled with TFTP support. 8.2-RELEASE builds were working fine until we attempted a build on bare metal in an environment that utilizes vlan tagging. When the system loaded the pxeboot.bs file it prompted that a disk containing the mfsroot.gz be inserted. Hi, a few questions: 1) do you use tftp or nfs? if you built pxeboot with tftp, did you also build the kernel with tftp? pxeboot.bs was compiled with TFTP enabled. We made 3 modifications to the kernel not related to tftp. One change was to the NIC source code to improve small packet performance, we compiled a custom kernel that disabled FLOWTABLE and enabled ROUTETABLES. TFTP is the intent for PXE, we did not want to rely on NFS. For the remainder of the install, we've written code into sysinstall to support pure HTTP installs. 2) do you fetch the kernel successfully? When using tftp, The kernel and kernel modules are fetched before the memory file system, so do pxeboot fetch the kernel but not the mfsroot? The reason for these questions is that your problem may be with the kernel and kernel modules and not pxeboot. Just to be sure. I see what you are saying. We will have to look at the packet captures to make that determination. I have a couple of questions that I am hoping I can use to glean a proper solution: 1) Does the 8.2-RELEASE pxeboot.bs source code support use of vlan tagging? 2) Can I get vlan tagging support with newer 8.2 code? 3) Will the 9.0-RELEASE code have better support for vlan tagging and can I use it to build an 8.2-RELEASE system? I did a grep in the source and it seems there is a kernel module for vlan tagging, if you load the kernel succesfully it may be a question of getting that module loaded as well, or rebuild the kernel. But I can't give a better answer. My best guess is not to rely on vlan tagging unless you can configure that on the hardware. Or, normally there is a default vlan that corresponds to no tag. If you can configure that for pxe and use tagging for the other networks. Thanks for this information, it has given me some other things to think about and could potentially lead to a proper solution. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: pxeboot.bs and vlan tagging
2) do you fetch the kernel successfully? When using tftp, The kernel and kernel modules are fetched before the memory file system, so do pxeboot fetch the kernel but not the mfsroot? The reason for these questions is that your problem may be with the kernel and kernel modules and not pxeboot. Just to be sure. I see what you are saying. We will have to look at the packet captures to make that determination. The target system loads pxeboot.bs and consequently requests the following files: /boot/boot.4th (which it does not find) /boot/loader.rc /boot/loader.4th /boot/support.4th /boot/defaults/loader.conf /boot/device.hints /boot/loader.conf It is at this point where the failure occurs. The contents of loader.conf are: mfsroot_load=YES mfsroot_type=mfs_root mfsroot_name=/boot/mfsroot Does this seem consistent with what you were theorizing that it's the kernel that has the problem with vlan tagging and not pxeboot.bs? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: pxeboot.bs and vlan tagging
Thanks for your feedback, Erik! I do have a question below... On Mon, Feb 6, 2012 at 11:45 AM, Erik Nørgaard norga...@locolomo.org wrote: See the other mail, the way pxeboot works IIRC, is that first the pxeboot is fetched using tftp, the pxeboot is given the next server and will fetch the kernel, modules and other files from /boot/ on that server, (path respective to the root of the tftp dir). The kernel loads and will then fetch the mfsroot file. As mentioned, by default this is done using nfs, and nfs is assumed if the kernel supports nfs, even if it only fetches one file. This I understand has to be this way since the network configuration set with dhcp does not specify the protocol. So, if your kernel supports nfs it will not use tftp and hence fail. The kernel I am using is the kernel from the DVD ISO as it is downloaded from freebsd.org. How do I determine what modules have been enabled and disabled in that kernel? I am under the assumption that NFS is compiled into that kernel. We can install 8.2-RELEASE with this kernel in VMs, but not bare metal. Is there an explanation as to why an NFS enabled kernel would work inside a VM, but fail on bare metal? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: pxeboot.bs and vlan tagging
We have determined that it has failed after loading pxeboot.bs and before loading the kernel. Therefore, the kernel is not the problem. I have also determined that vlan tagging is not the problem as it has failed with vlan tagging disabled. I don't believe it is the content because it works in 3 out of 4 different environments. In fact, in the 4th environment in recent tests, it worked a handful of times before failing again. Suspecting network configurations at this point, but thanks for the input provided thus far. It has been immensely helpful. On Mon, Feb 6, 2012 at 11:45 AM, Erik Nørgaard norga...@locolomo.org wrote: On 06/02/2012 17:33, Rick Miller wrote: 2) do you fetch the kernel successfully? When using tftp, The kernel and kernel modules are fetched before the memory file system, so do pxeboot fetch the kernel but not the mfsroot? The reason for these questions is that your problem may be with the kernel and kernel modules and not pxeboot. Just to be sure. I see what you are saying. We will have to look at the packet captures to make that determination. The target system loads pxeboot.bs and consequently requests the following files: /boot/boot.4th (which it does not find) /boot/loader.rc /boot/loader.4th /boot/support.4th /boot/defaults/loader.conf /boot/device.hints /boot/loader.conf It is at this point where the failure occurs. The contents of loader.conf are: mfsroot_load=YES mfsroot_type=mfs_root mfsroot_name=/boot/mfsroot Does this seem consistent with what you were theorizing that it's the kernel that has the problem with vlan tagging and not pxeboot.bs? See the other mail, the way pxeboot works IIRC, is that first the pxeboot is fetched using tftp, the pxeboot is given the next server and will fetch the kernel, modules and other files from /boot/ on that server, (path respective to the root of the tftp dir). The kernel loads and will then fetch the mfsroot file. As mentioned, by default this is done using nfs, and nfs is assumed if the kernel supports nfs, even if it only fetches one file. This I understand has to be this way since the network configuration set with dhcp does not specify the protocol. So, if your kernel supports nfs it will not use tftp and hence fail. The details are somewhat distant to me, it's been some time since I messsed arround with this. hope this helps. BR, Erik -- M: +34 666 334 818 T: +34 915 211 157 -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: make release custom kernel conf not found
Thanks Rob and Lowell, I will keep this information handy. It was helpful. On Tue, Jan 31, 2012 at 4:22 AM, Rob Farmer rfar...@predatorlabs.net wrote: On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller vmil...@hostileadmin.com wrote: Thanks Rob... I put the kernel conf file in the source tree as opposed to linking to it and it certainly did compile the custom kernel. What confuses me (not that I expect you to have the answer) is that Chapter 9 of the handbook has a tip that recommends keeping the kernel config in /root/kernels and symlinking to it from the source tree. If it doesn't work, why is there a tip recommending this practice? I think the idea is to avoid accidentally deleting it - sometimes people who get weird build errors are told to delete /usr/src and /usr/obj, to make sure everything is in a consistent state. The symlink will work fine for normal builds, which is what the handbook covers, but the release building process installs a new copy of the base system and then runs within it, to try and ensure a completely stock environment. Any changes you made to the main system (make.conf, custom kernels, etc.) are intentionally ignored. As Lowell points out, the right way to do this is make either a patch or a script to add your changes and have the release framework apply it. Copying it in is the quick and dirty fix. -- Rob Farmer -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: make release custom kernel conf not found
Thanks Rob... I put the kernel conf file in the source tree as opposed to linking to it and it certainly did compile the custom kernel. What confuses me (not that I expect you to have the answer) is that Chapter 9 of the handbook has a tip that recommends keeping the kernel config in /root/kernels and symlinking to it from the source tree. If it doesn't work, why is there a tip recommending this practice? On Sun, Jan 29, 2012 at 10:14 PM, Rob Farmer rfar...@predatorlabs.net wrote: On Sun, Jan 29, 2012 at 9:03 AM, Rick Miller vmil...@hostileadmin.com wrote: Hi All, I am performing a `make release` to build a new release with a custom kernel. The `make release` fails with the following error: cd /usr/src/release/..; make TARGET_ARCH=amd64 TARGET=amd64 KERNCONF=MYKERNEL kernel DESTDIR=/R/stage/kernels KODIR=/MYKERNEL ERROR: Missing kernel configuration file(s) (MYKERNEL). *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. I have the kernel config at /root/kernels/MYKERNEL and /usr/src/sys/amd64/conf/MYKERNEL is a symlink to the kernel config. The applicable environment variables are set in my .profile as follows: BUILDNAME=8.2-RELEASE-MYKERNEL-1.1 CHROOTDIR=/app/release CVSROOT=/home/cvs EXTPORTSDIR=/usr/ports EXTSRCDIR=/usr/src KERNELS=GENERIC MYKERNEL MAKE_DVD=YES NODOC=YES NO_FLOPPIES=YES I am unsure how to get `make release` to realize the location of the kernel config. Also, I notice that in the command to make the kernel, DESTDIR is set to /R/stage/kernels while the CHROOTDIR (and the location where I want the release to be built) is /app/release. I am wondering if someone knows how I may resolve the issue so I can get the release built. I appreciate any advice and feedback. Thanks. The kernel is built inside the chroot, so all paths are really /app/release/whatever. Your symlink points to /app/release/root/kernels/MYKERNEL. It will be easiest to get rid of the symlink and copy the actual file into your EXTSRCDIR before starting the make release; alternately you could use the LOCAL_PATCHES or LOCAL_SCRIPT variables to import it. -- Rob Farmer -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
make release custom kernel conf not found
Hi All, I am performing a `make release` to build a new release with a custom kernel. The `make release` fails with the following error: cd /usr/src/release/..; make TARGET_ARCH=amd64 TARGET=amd64 KERNCONF=MYKERNEL kernel DESTDIR=/R/stage/kernels KODIR=/MYKERNEL ERROR: Missing kernel configuration file(s) (MYKERNEL). *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. I have the kernel config at /root/kernels/MYKERNEL and /usr/src/sys/amd64/conf/MYKERNEL is a symlink to the kernel config. The applicable environment variables are set in my .profile as follows: BUILDNAME=8.2-RELEASE-MYKERNEL-1.1 CHROOTDIR=/app/release CVSROOT=/home/cvs EXTPORTSDIR=/usr/ports EXTSRCDIR=/usr/src KERNELS=GENERIC MYKERNEL MAKE_DVD=YES NODOC=YES NO_FLOPPIES=YES I am unsure how to get `make release` to realize the location of the kernel config. Also, I notice that in the command to make the kernel, DESTDIR is set to /R/stage/kernels while the CHROOTDIR (and the location where I want the release to be built) is /app/release. I am wondering if someone knows how I may resolve the issue so I can get the release built. I appreciate any advice and feedback. Thanks. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: pkg_add -r and a local package repo
On Wed, Jan 11, 2012 at 5:03 PM, Randal L. Schwartz mer...@stonehenge.com wrote: I've figured out how to point PACKAGESITE at a URL of my choosing. First, it looks like pkg_add -r needs the full package name. Is there any way to give it zsh instead of zsh-4.3.15? I've read somewhere that you should be able to do `pkg_add -r zsh\*`, but I've never actually tried it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
