FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F6.0.0_cvs 2005-11-03T00:35:26Z 2005-11-03T00:35:26Z cvs2svn cvs2svn@FreeBSD.org 2005-11-03T00:35:26Z urn:sha1:3640cb54210edbb7edbf1b12ef0127ecfcea967d 'RELENG_6_0_0_RELEASE'. This commit was manufactured to restore the state of the 6.0-RELEASE image. 2005-10-07T15:56:30Z Yoshihiro Takahashi nyan@FreeBSD.org 2005-10-07T15:56:30Z urn:sha1:e74be4f4a88b8c3c7c43bb67523a10400589da26 Approved by: re (scottl) 2005-03-02T22:27:22Z John Baldwin jhb@FreeBSD.org 2005-03-02T22:27:22Z urn:sha1:d61e43fe1ede38d6dbaeb6c97a790a3ab1c98582 with EBUSY and a cdrom is not mounted at /cdrom, sysinstall fails to treat it as an error and thinks that the disk mounted ok. However, it doesn't find a cdrom.inf file so it complains. Later when it tries to unmount the disk due to a mediaClose() umount(2) returns an error, and it never clears its internal mounted flag. The fix here is to properly handle EBUSY as an error if there isn't a CD already mounted at /cdrom. - Add a new CDROMInitQuiet variable that can be used to shut up the dialog box about the mount(2) system call failing when trying to mount a CD-ROM. This is used by the feature described below. - When using a fixit CD, first try to see if we can mount the disc in the drive now and use it as a fixit CD. If not, then prompt the user to insert the disc and try again. If we do succeed on the first "silent" probe then we don't ask the user to eject the disk after leaving fixit mode. - Add a simple file existence test to make sure that the disc that we mount really is a livefs disc. - Explicitly switch back to ttyv0 when using the standard console after the fixit shell dies. Previously this behavior worked accidentally because all the fixit modes popped up a dialog box which contained a hidden switch to ttyv0. MFC after: 1 day 2005-01-07T04:07:48Z Ken Smith kensmith@FreeBSD.org 2005-01-07T04:07:48Z urn:sha1:dedb9eb854d727ce8c6eec6bcce3684c8f706466 MFC after: 1 week 2004-08-30T21:03:09Z Ken Smith kensmith@FreeBSD.org 2004-08-30T21:03:09Z urn:sha1:83c7f6e5de2522dd058016c6f43eae62766f40c8 concensus seems to be that is best left for doing post-install. Discussed on: freebsd-current@ Tested with: make release Approved by: re@ MFC after: 3 days 2004-08-10T02:18:28Z Ken Smith kensmith@FreeBSD.org 2004-08-10T02:18:28Z urn:sha1:83e386eb0652695466237263c68f61f6c4422bdc There are still a few nits to work out (graphical config non-functional). Patches by: anholt@, adapted slightly Reviewed by: 'make release' 2004-08-07T01:19:54Z Marcel Moolenaar marcel@FreeBSD.org 2004-08-07T01:19:54Z urn:sha1:e66a84ac142c5166cab9306620e0f5165e9b050f global variables. On ia64, save a pointer to the efi chunk as well. o At the same time, change checkLabels() to define these globals instead of having the caller of checkLabels() pass addresses to variables for these. Change the two callers correspondingly. o Spent a bit more time adjusting try_auto_label() to prepate for having the EFI partition created on ia64. o Remove efi_mountpoint(). The EFI chunk is now available without having to iterate over the disks and chunks to find it every time we need it. o On ia64, now that the root chunk is globally available, set the vfs.root.mountfrom tunable in loader.conf. This avoids that one cannot boot into FreeBSD after an install. The kernel cannot find the root device without a little help... 2004-08-06T07:27:08Z Colin Percival cperciva@FreeBSD.org 2004-08-06T07:27:08Z urn:sha1:d37df47d3104331743c4d05ebba3f996f5a2308a of releases. The -DNOCRYPT build option still exists for anyone who really wants to build non-cryptographic binaries, but the "crypto" release distribution is now part of "base", and anyone installing from a release will get cryptographic binaries. Approved by: re (scottl), markm Discussed on: freebsd-current, in late April 2004 2004-08-02T23:18:48Z Marcel Moolenaar marcel@FreeBSD.org 2004-08-02T23:18:48Z urn:sha1:498609452e200a7ef2a0155b6b67f2fac4c35041 that actually need it. This makes it easier for a platform porter to find the files that may need tweaking to support whatever MD specific partitioning is needed. It also helps to prevent that the libdisk API gets exposed and/or used where it's not needed. 2004-03-11T11:58:16Z Bruce Evans bde@FreeBSD.org 2004-03-11T11:58:16Z urn:sha1:03f0d9e8ae6d98324d750f279801106df7b32877