Re: the future of sun4v
Marius Strobl wrote: On Fri, Aug 22, 2008 at 01:44:25PM +0200, Kris Kennaway wrote: Peter Jeremy wrote: [Replies re-directed to freebsd-sun4v] On 2008-Aug-21 14:42:55 -0700, Kip Macy [EMAIL PROTECTED] wrote: I believe that there is a general expectation by freebsd users and developers that unsupported code should not be in CVS. Although sun4v is a very interesting platform for developers doing SMP work, I simply do not have the time or energy to maintain it. If someone else would like to step up and try his hand I would be supportive of his efforts. In the likely event that no one steps forward by the time that 7.1 is released I will ask that it be moved to the Attic. Since there are no other current SPARC CPUs that FreeBSD can run on (the US-II has been obsolete for about 6 years and FreeBSD won't run on any more recent sun4u chips), that will also remove the justification for maintaining a SPARC64 port. I don't have the knowledge or available time to maintain the sun4v port by myself but would be happy to be part of a team doing so. One impediment I have is that I don't have a T-1 or T-2 system that I can dedicate to FreeBSD. I could work on FreeBSD in a guest domain - but since FreeBSD doesn't support either the virtual disk or virtual network, actually getting FreeBSD running there presents somewhat of a challenge. There are two t1000 systems in the freebsd.org cluster that are available for people to work on. Rink Springer has also expressed interest in this. Perhaps Kip can explain some more about what things he looked at, but the most serious bugs might be in pmap or perhaps trap handling. Operationally, things like buildworld -jN die quickly with random signals, kernel traps, etc. Kris P.S. It looks like marius has made progress on US III but sun4u is still an architectural dead end. Well, let's see what architecture the upcoming Rock CPUs are; judging their feature list they appear to be a continuation of the Fujitsu sun4u line rather than a successor of UST1/2 :) That's inaccurate. Rock is meant to be very compatible with sun4v, although I don't know if uname will say sun4v or something else...but you will need a bug-free sun4v operating system to run them (which is to say that various bugs in the solaris sun4v support needed to get fixed rather than left...) The critical issue for freebsd (and any operating system for that matter) on rock is how well does the kernel scale to a system with that many concurrent threads? Darren ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: FreeBSD 7.1 Content
On Sun, Sep 07, 2008 at 08:06:24AM -0400, Randy Pratt wrote: The ports tree distribution tarball provided on the installation disks is another area that needs some consideration. I suspect that many people aren't aware of the need for adoption: http://myfreebsd.homeunix.net/hints_n_kinks/adoptportstree.html Is it possible to provide/install the necessary file(s) along with the ports tree such that cvsup/csup would be aware of the files installed so that obsolete files can be removed when updating the ports tree? The same situation probably exists for the source tree and the documentation tree. Would it just be a matter of installing the appropriate checkouts.cvs:. files when the sources are installed? I've only done the adoption process one time and decided that its easier to just csup a new trees right after booting the new system. IMO, an even better (but complementary) approach would be to have /usr/ports be a valid portsnap extraction and give users the option to bootstrap /var/db/portsnap. In general I'm finding it to be a much better approach. At this point I'm mostly using cvsup for development. I literally check out a separate ports tree on boxes I do ports development on and keep the main tree up to date with portsnap. I also use freebsd-update to manage most of my servers at work even ones with custom kernels (just let it update /usr/src and don't let it update the kernel). Additionally, I've never seen a clear way of synchronizing a local ports tree to that used to create the LATEST packages. I've had to resort to building my own package sets for the slow boxes on the network. I realize that this aspect diverges from the subject of this thread but I do think some more thought should be given to this aspect. With cvs there probably isn't a cost effective way to indicate this (though I suppose the package collections could include a file with a cvsup date string in them). -- Brooks pgpeZXRWGle0u.pgp Description: PGP signature
Re: How to disable NFS fnctl in /etc/fstab?
Tim Chen wrote: For some reason we want to disable fnctl lock for NFS mounted partition. We can achieve this by the following command: mount_nfs -T -L server:/home /mnt However after several time of failure tests, we still can not make it work in /etc/fstab. server:/home /mnt nfs rw,tcp 0 0 server:/home /mnt nfs rw,tcp,-L 0 0 By the way, since the machine is running as a mail server which install postfix,courier-imap, will it happen any kind of data corruption due to NFS fnctl lock disabled? In general, all programs that access mail files must use locking for concurrent access. Without proper locking you'll get data corruption. I strongly advise against running mail software on NFS mounts without locking (i.e. with the -L option). Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd If you think C++ is not overly complicated, just what is a protected abstract virtual base pure virtual private destructor, and when was the last time you needed one? -- Tom Cargil, C++ Journal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: FreeBSD 7.1 Content
Kevin Oberman wrote: Kai Otto wrote: I think someone mentioned it earlier, but I'm not shure. IMHO it would _be_ nice if there's a HTML-browser in the standard installation (with option to not install it in sysinstall). I say HTML and not web because I think about the /usr/share/doc .html-documentation. If someone really has no Internet-connection as mentioned before he/she isn't able to read the handbook, which IMHO is a very important part of FreeBSD. There are great manpages and exaple files, but the best explanations are in the handbook. That's why there's a plain .txt file of the Handbook. No browser required. These days a web browser is almost essential. The question is lynx or links? I prefer links, but lynx is more popular. I hope you don't insist on a GUI. Those things are far too big and require an X install. There's also w3m which some people seem to prefer. It's quite light-weight: $ cd /usr/local/bin $ ls links lynx w3m -r-xr-xr-x 1 root wheel 1059000 Aug 7 09:48 links -r-xr-xr-x 1 root wheel 1184784 Jun 9 15:17 lynx -r-xr-xr-x 1 root wheel 403592 Jun 9 16:15 w3m Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd In My Egoistical Opinion, most people's C programs should be indented six feet downward and covered with dirt. -- Blair P. Houghton ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mysterious uname non-updates
Dmitry Morozovsky wrote: today, updating one of my machines, I got the following mysterious results after reboot: [EMAIL PROTECTED]:~# sysctl -a | grep RELE kern.osrelease: 6.3-RELEASE kern.version: FreeBSD 6.3-RELEASE #4: Thu Jan 17 15:28:57 MSK 2008 [EMAIL PROTECTED]:~# strings /boot/kernel/kernel | grep RELE AE_RELEASE_DEADLOCK 6.3-RELEASE-p4 FreeBSD 6.3-RELEASE-p4 #6: Sun Sep 7 23:13:45 MSD 2008 @(#)FreeBSD 6.3-RELEASE-p4 #6: Sun Sep 7 23:13:45 MSD 2008 [EMAIL PROTECTED]:~# env | grep -i uname [EMAIL PROTECTED]:~# WTF? Why my kernel reports that it is previous version (actually it is already deleted, so I'm double puzzled) What does sysctl kern.bootfile say? And are you sure that you rebooted the right machine? ;-) Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd One of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs. -- Robert Firth ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: FreeBSD 7.1 Content
On Sun, Sep 07, 2008 at 08:06:24AM -0400, Randy Pratt wrote: Additionally, I've never seen a clear way of synchronizing a local ports tree to that used to create the LATEST packages. There's really not a way to easily track this, especially with the fact that we tend to run incremental updates. The best approximation we can give you is e.g.: http://pointyhat.freebsd.org/errorlogs/amd64-6-latest/cvsdone but if there were manual updates to the tree, then the cvsdone files may be out-of-date. In addition, if there were checkins in progress as of that time, the tree may be inconsistent in the first place :-/ I used to have a page that indexed those and a lot of other statistics but it is currently broken. I need to put fixing that on the TODO list. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: FreeBSD 7.1 Content
On Mon, 8 Sep 2008 17:50:08 -0500 [EMAIL PROTECTED] (Mark Linimon) wrote: On Sun, Sep 07, 2008 at 08:06:24AM -0400, Randy Pratt wrote: Additionally, I've never seen a clear way of synchronizing a local ports tree to that used to create the LATEST packages. There's really not a way to easily track this, especially with the fact that we tend to run incremental updates. The best approximation we can give you is e.g.: http://pointyhat.freebsd.org/errorlogs/amd64-6-latest/cvsdone but if there were manual updates to the tree, then the cvsdone files may be out-of-date. In addition, if there were checkins in progress as of that time, the tree may be inconsistent in the first place :-/ I used to have a page that indexed those and a lot of other statistics but it is currently broken. I need to put fixing that on the TODO list. If its not an easy thing to do then its probably not worth spending Release Engineering time on it. Personally, I quit using packages in the 2.x-3.x days since there were far less problems building everything from sources and not trying to mix pre-built packages and locally built ports. That was the only reason I mentioned the syncronization. Thanks for taking the time to explain why it isn't an easy thing to do! Randy -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: FreeBSD 7.1 Content
On Mon, Sep 08, 2008 at 10:27:31PM -0400, Randy Pratt wrote: Personally, I quit using packages in the 2.x-3.x days since there were far less problems building everything from sources and not trying to mix pre-built packages and locally built ports. We are doing much better these days in terms of building packages quickly, especially on amd64 and to some extent i386. More hardware has helped. However, with over 19,000 makefile and makefile parts involved, there's really only so much that can be done outside of the QA/freeze timeframes. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
