Re: FreeBSD 9.1-RC1 Available...
On Thu, 23 Aug 2012, Ken Smith wrote: Hi, let me reply to the very initial email in this monster of public thread. With both the doc and ports repositories now moved to SVN it has been decided to not export the 9.1 release branch activity to CVS. So csup/cvsup update mechanisms are not available for updating to 9.1-RC1. If you would like to use SVN the branch to use is releng/9.1. RELENG_9_1 is now exported the CVS as well and will be for as long as things will be exported to CVS. It will take another few hours to get near your local mirror as they'll all be chewing on each other the next 12 hours. Enjoy! Any further discussions on src export I'll leave to other people wearing hats. /bz -- Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Clang as default compiler
Could you elaborate? After setting WITHOUT_GCC I don't have installed gcc/++ so it looks like it's working. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Clang-as-default-compiler-tp5742836p5744598.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
9.1 and amdtemp
On asus m5a97 mobo with amd 8120, RC1. Loading amdtemp.ko shows no temperature. People on the net post having source from head solved the issue. Would it be included in 9.1 release? If not, I might compile source and rename it to something like temperature.ko, then load it. Btw, someone knows about new schedule for the release? Best regards all Zoran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Panic with fusefs-ntfs on FreeBSD 9 RC1 amd64
I installed the package ntfs-fusefs on two different servers and both causes kernel panic when trying to copy anything. A server using FreeBSD 9.0 STABLE amd64 and the other using FreeBSD 9 RC1 amd64. Someone is having the same problem? Gondim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Panic with fusefs-ntfs on FreeBSD 9 RC1 amd64
On 09/18/2012 18:14, Marcelo Gondim wrote: I installed the package ntfs-fusefs on two different servers and both causes kernel panic when trying to copy anything. I got panics, too, but found some patch that I attached to ports/169165. Unfortunately, the maintainer of sysutils/fusefs-kmod (Cced) did not reply for the last four weeks. It could be committed due to a maintainer timeout. Cheers, Jan Henrik ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Panic with fusefs-ntfs on FreeBSD 9 RC1 amd64
On Tue, Sep 18, 2012 at 10:21 AM, Jan Henrik Sylvester m...@janh.de wrote: On 09/18/2012 18:14, Marcelo Gondim wrote: I installed the package ntfs-fusefs on two different servers and both causes kernel panic when trying to copy anything. I got panics, too, but found some patch that I attached to ports/169165. Unfortunately, the maintainer of sysutils/fusefs-kmod (Cced) did not reply for the last four weeks. It could be committed due to a maintainer timeout. Florian Smeets recently posted ports of updated versions of fusefs-libs and fusefs-ntfs on ports@ with a call for testing. You might want to look at that, though I hit a bit of a sticky wicket. After the upgrade of those ports I could no longer build fusefs-kmod. :-( If I get some time, I may be able to track the missing declaration down, but I would not bet on it. Florian said he will look into it when he has some time, but I have no idea when that might be. On the other hand, I have found it to be fairly stable. I keep all of my l of my music and video on an NTFS partition that is available to both Windows and FreeBSD. Gets fairly heavy use, but it very read-mostly. I have used it since at least 8.0 and probably 7.2 on both i386 and amd64. I can crash it reliably by using rsync to copy files and it periodically seems to lose some context. All files/directories start reporting Non-existent. Resetting the cwd with cd seems to get this working again, though. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Panic with fusefs-ntfs on FreeBSD 9 RC1 amd64
On Tue, Sep 18, 2012 at 5:14 PM, Marcelo Gondim gon...@bsdinfo.com.br wrote: I installed the package ntfs-fusefs on two different servers and both causes kernel panic when trying to copy anything. A server using FreeBSD 9.0 STABLE amd64 and the other using FreeBSD 9 RC1 amd64. Someone is having the same problem? Hello Marcelo, Do you think you can try fuse import explained here: http://lists.freebsd.org/pipermail/freebsd-current/2012-September/036677.html The proposed patch is for HEAD@240684 but I'm sure it should apply cleanly to RELENG_9_1 too. Please let me know if you have further questions. Attilio -- Peace can only be achieved by understanding - A. Einstein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)
Daniel Eischen deisc...@freebsd.org wrote: My rc.conf is something like this: # # For now, force ath0 to use the same MAC address as xl0. # This works around a bug where lagg is unable to set the # MAC address of the underlying wlan0 interface. # ifconfig_ath0=ether 01:02:03:04:05:06 wlans_ath0=wlan0 ifconfig_wlan0=ssid SSID_FOO_NAME WPA I hope the above isn't literally what you're using for your MAC address. The first octet in particular, because it has LSB set to 1, will be treated as a multicast address, and many routers and switches will not believe it when it's given as an ARP reply, or as a source address for traffic. I'm hoping it's just an example you substituted so as not to reveal your actual MAC. When making up MAC addresses, keep the LSB of the first octet at zero (required) and set the next bit to 1 (optional, but a good practice). So first octet should be 02, 06, 8a, 9e, etc... any even number, preferably multiple of four, plus two. ifconfig_xl0=up closed_interfaces=lagg0 ifconfig_lagg0=laggproto failover laggport xl0 laggport wlan0 ifconfig_lagg0_alias0=inet 10.0.0.4 netmask 0xff00 I use aliasX to add the address and netmask. -- DE -- David DeSimone == Network Admin == f...@verio.net I don't like spinach, and I'm glad I don't, because if I liked it I'd eat it, and I just hate it. -- Clarence Darrow This email message is intended for the use of the person to whom it has been sent, and may contain information that is confidential or legally protected. If you are not the intended recipient or have received this message in error, you are not authorized to copy, distribute, or otherwise use this message or its attachments. Please notify the sender immediately by return e-mail and permanently delete this message and any attachments. Verio Inc. makes no warranty that this email is error or virus free. Thank you. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)
On Tue, 18 Sep 2012, David DeSimone wrote: Daniel Eischen deisc...@freebsd.org wrote: My rc.conf is something like this: # # For now, force ath0 to use the same MAC address as xl0. # This works around a bug where lagg is unable to set the # MAC address of the underlying wlan0 interface. # ifconfig_ath0=ether 01:02:03:04:05:06 wlans_ath0=wlan0 ifconfig_wlan0=ssid SSID_FOO_NAME WPA I hope the above isn't literally what you're using for your MAC address. No, of course not :-) I thought it was obvious I elided my actual MAC address. -- DE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
