Re: fdimage tool on rc2 cd missing
On Thu, Dec 26, 2002 at 11:38:00PM +0100, Jens Rehsack wrote: correct me if I'm wrong, but shouldn't be the fdimage tool for creating disk images under DOS on the first cd of 5.0-RC2 (and later RELEASE)? Yes, fdimage is one of many tools that should be included in the 'tools' directory on the full release ISOs. Someone forgot to add the tools directory to the RC2 ISO. The release candidate ISOs contain just the base bits + packages, if that much. Adding the 'tools' directory should really be an option to make release but it isn't yet. It's listed as one of the manual steps in the releng article though. Anyway, you can download the fdimage program from : ftp.freebsd.org/pub/FreeBSD/tools you can see the checklist for what goes on the final CDROM images here: www.freebsd.org/doc/en_US.ISO8859-1/articles/releng - Murray To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
5.0-RC1 Now Available
Thanks to everyone who has helped focus on getting 5.0-CURRENT (now 5.0-RC) into shape the upcoming release. We're one milestone closer today with the immediate availability of the first release candidate for the i386, alpha, sparc64, and ia64 platforms. ISO images and FTP installation directories are available now from the FTP sites. Not all of the mirrors have all of the files yet, but they are at least available from : ftp2.freebsd.org ftp.tw.freebsd.org ftp7.de.FreeBSD.org Please try your local mirror first. The i386 ISO image includes a full package set. Unfortunately, kde can not be installed from sysinstall, but kdebase is on the ISO and can be installed from the command line. ISOs for the other architectures do not contain packages. The pc98 architecture release will be available shortly. Please continue to check our 5.0-RELEASE todo list : http://www.freebsd.org/releases/5.0R/todo.html and keep us apprised of any outstanding issues. Thanks! - Murray / Release Engineering Team To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5.0 release schedule?
On Wed, Aug 28, 2002 at 09:08:32AM -0400, Rod Smith wrote: According to the timetable at http://www.freebsd.org/releases/5.0R/schedule.html, DP2 for FreeBSD 5.0 I've updated that timetable to remove the specific date (it may take up to 24 hours for the website to be updated). We're actively working on it and I expect a stable DP2 release in the month of September. - Murray To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5.0 release schedule?
On Thu, Aug 29, 2002 at 01:41:41PM -0700, David O'Brien wrote: A 5.0 DP2 branch was created just yesterday. So how ever good yesterday's -current was will affect DP2. I rather expected the release engineers to at least querry the lists to ask what the known issues are before picking which code to base DP2 on. We plan to keep the DP2 branch in Perforce in sync with -CURRENT for a while until things stabilize a bit more. That wasn't a branch point per se, just the initial integrate to populate the branch so we can begin tweaking the documentation and such. DP2 will certainly not be based on yesterday's -CURRENT, it was too problematic and doesn't contain the new GCC bits. - Murray To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Comments on Release Building for -current
On Wed, Jul 31, 2002 at 08:33:38AM -0400, W Gerald Hicks wrote: Yup, it's been reported several times by various people and it seems everyone who can help is too busy to care. This isn't fun anymore. :-( Uhm, did I miss something? Where does this attitude come from? Did you submit some patches for these problems that were ignored or something? Can we try to be a little more constructive here about solving problems? - Murray To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
5.0 DP2 (was Re: KSE M-III status junior hacker project.)
On Sat, Jul 06, 2002 at 04:57:08PM -0700, Julian Elischer wrote: Well with various hints from here and there I have fixed the ^Z/fg problem (at least it seems fixed to me and others that have tested) This basically leaves only one outstanding problem that I know of which is a problem that Warner has with a particular progam. (This may also be fixed but I don't know) Hi Julian, Thanks for your progress on KSE! How long should we wait before branching in Perforce for 5.0 DP2? I would like to give at least 10 more days for this and other changes to settle before making the branch. If all goes well, I would like to release 5.0 DP2 at the end of this month. - Murray To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with rl
On Sat, Apr 13, 2002 at 10:51:16AM +0200, John Angelmo wrote: The errormessage I get is: rl0: RealTek 8139 10/100 Irq 5 at device 2.0 pci 1 Couldn't map ports/memory device_probe_and_attatch( rl0 attatch retuned 6) Is PNP OS installed selected in your BIOS? If so, try without this option set. - Murray msg37226/pgp0.pgp Description: PGP signature
Re: DP 1 install report
On Thu, Apr 11, 2002 at 12:26:41AM -0700, Doug Barton wrote: So far, the only other oddity I've noticed is that when I added the src distribution, all of the files were set 444. The directories have 755 permissions. Ahh. The problem here is related to the hoop we had to jump through to get make release to get the code for the source distribution out of Perforce instead of out of CVS (the default). Thanks for noticing this. I hope we're able to use a branch in CVS for the next DP, but if we have to use Perforce again I will fix the permissions. While I'm doing a review, I should add that one of the menus in sysinstall really bugs me... Do you have a non-USB mouse connected to the system? which defaults to No. Something is wrong with that picture. :) Yes, I agree that the wording is bad. - Murray msg37155/pgp0.pgp Description: PGP signature
Re: USB mouse problem
On Sat, Mar 30, 2002 at 03:24:08PM +0200, Andrew Bliznak wrote: On Sat, 30 Mar 2002, Masahide -mac- NODA wrote: Same here, solid lock, debug key not work. If I setup X to use /dev/ums0 computer hang just after startx. All worked with kernel/world from Mar 12. Me too. In my case I use an OmniView USB KVM switch. When I switch to my MacOS X box (which causes the keyboard and mouse to be disconnected from the FreeBSD machine), FreeBSD locks solid. This was working fine in -CURRENT just 2 weeks ago, and it works fine in -STABLE as of today. One of the recent NetBSD merges must be causing this. Any thoughts, Joe? - Murray msg36884/pgp0.pgp Description: PGP signature
Re: HEADS UP: -CURRENT Feature Slush is OVER
On Sat, Mar 16, 2002 at 02:08:51PM -0800, Terry Lambert wrote: I think it's an incredibly bad idea that we are not going to be able to reproduce what went onto any given CDROM in ten years. I agree that it is very important to be able to reproduce official releases of FreeBSD N years down the road. However, that has never been a requirement of snapshot CDs. We have never even tagged the tree for previous snapshots. We are actually moving more in the direction you advocate by at least moving the snapshot production into Perforce so that more developers can participate. The release engineers would prefer to do this in CVS, but that is not advisable for the reasons Peter outlined in his mail. The source distribution is included in the output of make release for a reason. If you have a technical solution to the problems that Peter raised, then I'm sure [EMAIL PROTECTED] would like to hear about them. - Murray msg36234/pgp0.pgp Description: PGP signature
Re: HEADS UP: -CURRENT Feature Slush is OVER
On Sun, Mar 17, 2002 at 01:08:43AM -0800, Terry Lambert wrote: Minimally, pick a date, and then do a CVS diff against that date, and include it on the CDROM. I would be happy to do this. I checked out a copy of the CVS tree right before we made the Perforce branch so that we could tag it later if absolutely necessary. Max wants the commit messages to the developers pre-release to go to an archived mailing list for similar reasons, it seems to me. I have emailed Peter about this. I don't think the messages should go to cvs-all, because I don't think most people want to see them. But I do think that they should be available for people like Max. Max was CCed on my message to Peter. Now say you have become involved in the process, because the pre-release has done it's job. You want to fix the bug. In order to do this, you are going to need the delta against the developer's prerelease source tree. To get this, the process is: 1) Mount your DP1 CD, and view the diff. - Murray msg36241/pgp0.pgp Description: PGP signature
Re: CVS Issues with branch.. Was: Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
On Fri, Mar 15, 2002 at 03:32:00AM +0100, Dag-Erling Smorgrav wrote: Bruce A. Mah [EMAIL PROTECTED] writes: Differences of opinion on naming aside...the branch isn't supposed to last long at all. The point is to provide a slightly polished snapshot to the wider developer community. We can't do the QA/releng work on HEAD without calling for a code freeze (which we early on decided that we would *not* do). Then you don't need a branch, you just need a simple tag, and you can slide it forward if something needs fixing, and remove it after rolling and shipping the snapshot. Sliding tags around at the request of hundreds of different developers making thousands of changes to -CURRENT over that time period is not very appealing. However, all of our other options are rapidly being shot down as well. Peter raises some valid concerns about the pains that branching CVS will cause. They would have been much more helpful if voiced to re@ a week ago, but that's another issue. At the very least a tag is going down in approximately 24 hours. - Murray msg36135/pgp0.pgp Description: PGP signature
Re: CVS Issues with branch.. Was: Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
On Thu, Mar 14, 2002 at 04:40:08PM -0800, Peter Wemm wrote: If this is going to be a static release (calling it RELENG_5_anything is a mistake IMHO) then this isn't a big deal. But if people are expecting it to have ongoing secirity fixes etc like we do with RELENG_4_5 etc then we have a problem, because it cannot last very long at all. Ongoing security fixes for a SNAPSHOT ??? No, that is definitely not the case. Accordingly, I would much prefer that the branch (if we have to have it) would be called SNAPSHOT_5_DP1 or soemthing, so that the RELENG_ prefix doesn't unduely raise expectations that it will keep working, or move the DP1 release elsewhere if we want it to remain cvsup'able long term. I think that the huge warning signs all over the release documentation will do a lot more to set the expectations that the name of a CVS tag, but just to be sure I suppose we can keep the RELENG namespace for official releases. Your proposed name change works for me. - Murray msg36136/pgp0.pgp Description: PGP signature
Call for Submissions: FreeBSD 5.0 DP1 Testing Guide
As part of the release documentation for 5.0 DP1, we would like to provide a comprehensive testing guide. If you have code in -CURRENT that you would like to receive feedback on from the developer preview, then please submit a short email to [EMAIL PROTECTED] with the following: 1. A brief description of the new functionality to be tested. 2. A list of known issues / bugs. 3. Instructions for users who wish to help test the feature. If required, we can add test programs or additional patches to a separate directory of the ISO image and FTP install directory. This is somewhat analogous to the 4.5 Testing Guide, http://www.freebsd.org/releases/4.5R/qa.html, but our focus is slightly different. Please send submissions to [EMAIL PROTECTED] before Wednesday March 20. We would like to allow enough time for translation teams to do their work, so the earlier the better. Thanks, - The Release Engineering Team msg36138/pgp0.pgp Description: PGP signature
Package set for release media
Does anyone have suggestions for additional packages that should be included on the upcoming Developer Preview snapshot that are not already listed in src/release/scripts/print-cdrom-packages.sh? The only changes since the release of 4.5 have been the inclusion of samba and the upgrade to emacs21. Please send suggested packages to portmgr and re; no need to flood the list. Thanks, - Murray msg35935/pgp0.pgp Description: PGP signature
Re: Preparing innocent users for -current
On Fri, Mar 08, 2002 at 04:55:29PM -0500, Garance A Drosihn wrote: One thing to keep in mind here is that this is still going to be a snapshot of -current, and not a production release of -stable. We want a snapshot that does not have any serious problems, but innocent users should still realize that there are definitely going to be a lot of loose ends and rough edges around. Exactly. This text was included on the back of the 5.0 snapshot CDROM from last year : The FreeBSD 5.0-CURRENT SNAPshots are works in progress, and are intended solely for developers who are developing software on FreeBSD. There are no guarantees about the stability of these snapshot releases, although we make every attempt to thoroughly test the releases before production. It's hard for me to have sympathy for a user who doesn't read the warning labels posted all over the CD and release documentation. - Murray To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT, make buildworld break?
On Wed, Mar 06, 2002 at 01:25:01PM +0100, Dag-Erling Smorgrav wrote: Ruslan Ermilov [EMAIL PROTECTED] writes: On Wed, Mar 06, 2002 at 01:17:28PM +0100, Dag-Erling Smorgrav wrote: Last I checked, 'make release' checks the sources out from CVS, and is therefore useless to test changes that haven't yet been committed. There's such a thing as LOCAL_PATCHES since at least 1996. Great! Now if only that was *documented* somewhere... It _IS_ documented in the release engineering paper : http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/extensibility.html - Murray To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
As discussed at BSDCon, the release engineers are committed to releasing a relatively stable snapshot of FreeBSD -CURRENT on or around April 1, 2002. Obviously, a lot of major components are still in progress, but a great deal of work has already been accomplished, and could benefit from the additional exposure that a polished snapshot with full package set and documentation will provide. To this end, we would like to request that commits for the next 7 days to HEAD be made with special care. -CURRENT is in pretty good shape right now, so we're not requiring approval for all commits. However, we do request that re be consulted for any commits with a substantial risk. This includes non-trivial changes to the VM system, filesystems, network stack, important userland components, and others. If unsure about a commit, please ask. Changes specific to emerging architectures (sparc64, ia64, powerpc) are exempt from this approval requirement no matter how substantial the change (as long as it only affects the given architecture). On March 15, a RELENG_5_0_DP1 branch will be created in CVS for final release polishing. This will allow us to provide translated release notes, sync up sysinstall and the package set, bump version numbers, and tweak default diagnostic settings without further impacting -CURRENT developers. Commits to this branch will require re approval. For further information about our plans for 5.0 Developer Previews, and the eventual release of FreeBSD 5.0 in November, please see the new release engineering section of the FreeBSD web site : http://www.FreeBSD.org/releng If you would like to help out with some of the quality-assurance work for the upcoming developer preview, please install a -CURRENT snapshot from : ftp://ftp.FreeBSD.org/pub/FreeBSD/snapshots/i386 - or - ftp://snapshots.jp.FreeBSD.org/pub/FreeBSD/snapshots/i386 And post your findings to current or qa@. (Sorry, Alpha -CURRENT snapshots are harder to come by at the moment, but Compaq just donated some hardware to alleviate this problem in the future.) Thanks for your cooperation, - Murray (on behalf of The Release Engineering Team) msg35781/pgp0.pgp Description: PGP signature
Re: Preparing innocent users for -current
On Fri, Mar 08, 2002 at 11:33:27AM -0800, Hiten Pandya wrote: Shouldn't this be CC'ed to -doc as well? Maybe someone will write an article on a little release note kinda thing for this issue. Just an opinion from a -current user. :) We're collecting notes for a Testing Guide similar to the one we published leading up to FreeBSD 4.5. More than anything, we need information from developers about how users can best test the new functionality. - Murray To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD/i386 make release breakage
On Wed, Feb 27, 2002 at 12:19:01AM +0900, Makoto Matsushita wrote: murray I'm currently looking into #2 and #3, as well as working with Ted murray Lemon from the ISC to fix some symbol pollution that this whole mess murray has exposed. Any other ideas? Currently nothing, it seems that #3 (or its variant) is better IMHO. Ok. Fixed in r1.15 of sbin/dhclient/Makefile. I'm not sure if make release will succeed now (just started a build), but release.4 will at least build a crunched dhclient again. - Murray To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
HEADS UP: DHCP 3.0.1RC6 imported
DHCP 3.0.1 RC6 has been imported into -CURRENT. DHCP 3.x provides DHCP failover support, dynamic DNS updates, and much more. http://www.isc.org/products/DHCP/dhcp-prerelease.html I've done testing with some Alpha and i386 machines on my local network, but it's certainly possible that the new DHCP client will behave in unexpected ways in more demanding environments. If you notice any regressions in functionality, please email me. Thanks, - Murray To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
