cvsup10.freebsd.org seems broken
Updating ports via cvsup against cvsup10.freebsd.org has shown no new files for at least a few days, if not longer (can't remember when I last attempted, but not more than a few weeks). I switched to cvsup4 (which was just as close) and got a bunch of new updates. Someone may want to check this out. Brian ___ 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
ports on FreeBSD 4
I realize the ports on RELENG_4 have been EOL'd, but I'm stuck on 4 for one system due to instability currently with the RELENG_6 box that will take its place. I'd like to be able to get a ports tree that represents the state of things just before support for 4.x was dropped. I thought I read that the tag for that was RELENG_4_EOL. I tried using that by going into /etc/make.conf and changing PORTSSUPFILE= /usr/share/examples/cvsup/ports-supfile to PORTSSUPFILE= /usr/local/etc/ports-supfile and in /usr/local/etc/ports-supfile, a copy of /usr/share/examples/cvsup/ports-supfile, I changed *default release=cvs tag=. to *default release=cvs tag=RELENG_4_EOL I did a make update in /usr/ports and it started to remove every file under /usr/ports. Yech. I had to go back to using /usr/share/examples/cvsup/ports-supfile and do a make update from /usr/src to get a /usr/ports tree back, though now of course that /usr/ports tree doesn't work for 4.x (it expects the new rc.subr stuff for example). I realize I'm treading on retired ground here... but any ideas? Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports on FreeBSD 4
On Wed, 16 May 2007, Björn König wrote: Brian Behlendorf schrieb: *default release=cvs tag=RELENG_4_EOL Use RELEASE_4_EOL. Thanks! (to Erik Trulsson too). That worked. It was mistakenly given as RELENG_4_EOL in the quarterly status report: http://lists.freebsd.org/pipermail/freebsd-announce/2007-April/001124.html Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Unable to find device node errors at install
I ran into this familiar problem tonight while trying to do a fresh install of 6.0 - the one where during the install process you can successfully create a slice, but then fail to create the partitions. The error when one attempts to write out the partition table is Unable to find device node /dev/da0s1b in /dev! After successfully installing Ubuntu on the same box (and having run FreeBSD 4.x on it for years) I figured out it wasn't a hardware or even disk geometry problem. The problem must lie in devfs or in the initialization of the miniroot environment. After the successful disklabel (one big partition type 165) I skipped the partition editor and started a fixit shell. /dev/md0 was mounted as /. I don't know if that's how it is during a partition edit, but I noticed that the only da0 devices in /dev were da0s1a and da0s1c. I don't know enough mknod magic or whatever is used to create additional device handles in /dev these days; as a naive installer I shouldn't have to. I went back to the partition editor, created one big partition, da0s1a, and didn't bother creating a swap or secondary partition. The write succeeded, and I could proceed to install FreeBSD 6.0. Since none of the previous attempts at addressing this problem seemed to come up with a clear answer, I thought I would add this information to the fray; it's not a question to be answered but it might help someone who hits this problem again. Or it might even lead to a fix by someone who understands how the installation scripts are supposed to work. Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IBM eServer 346 ServeRaid is too slow
On Thu, 7 Apr 2005, Carl Makin wrote: I'd say you are seeing the same as I am with the same card in a Dell 1855. There is something wrong with the mpt driver and the disks when they are setup in a raid0 set. If you split the disks and use them as individual drives then you will get full performance. It's also a known problem, though not being tracked very well. http://lists.freebsd.org/pipermail/freebsd-scsi/2004-December/001577.html http://lists.freebsd.org/pipermail/freebsd-scsi/2004-December/001578.html Doesn't look like (from viewcvs.cgi) there's been any recent work on this. Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
