Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for manpage 'bsdinstall(8)'

This is an experimental report containing PRs for manpage 'bsdinstall(8)' as of Fri May 25 07:37:17 2012 UTC. See notes.


PRs for manpage 'bsdinstall(8)':
SSubmittedTrackerResp.Description
o2012/05/23bin/168269sysinstallcomments on bsdinstall(8)
o2012/05/21bin/168188sysinstallbsdinstall(8) partitioner segmentation fault
o2012/04/09kern/166801sysinstallbsdinstall(8): FreeBSD install is apparently not writing boot code to target disk.
o2012/03/09bin/165868sysinstallbsdinstall(8): ports tree installs CVS directories
a2012/02/10bin/164950nwhitehornbsdinstall(8): pc-style partitions: no way to set 'bootable' ('active') flag
s2012/02/04bin/164752sysinstall[request] bsdinstall(8): No option of ZFS in FreeBSD 9.0 DVD installation
o2012/01/23bin/164399sysinstallbsdinstall(8): 9.0 installer failures
o2012/01/18bin/164294sysinstallbsdinstall(8): FreeBSD 9.0-RELEASE bsdinstall dvd does not have media selection dialog
o2012/01/18bin/164291sysinstallbsdinstall(8): bsdinstall and filestetyem selection / creation
o2012/01/18bin/164284sysinstallbsdinstall(8): FreeBSD install assign incorrect dev as bootup disk
o2012/01/18bin/164281sysinstallbsdinstall(8): please allow sysinstall as installer option
o2012/01/18bin/164267sysinstallbsdinstall(8) bugs when RE-installing to GPT partitions
o2012/01/13bin/164097sysinstallbsdinstall(8): always installs GPT
f2012/01/13bin/164094sysinstallbsdinstall(8): installer progress over 100%
o2012/01/09bin/163943sysinstallbsdinstall(8) fails to detect CD device when booting with some media devices
o2011/12/08bin/163123sysinstallbsdinstall(8): IPV6 only errors connecting
o2011/11/10bin/162429sysinstallbsdinstall(8): 9.x installer: selecting ZFS for the root partition results in error
o2011/11/10bin/162428sysinstallbsdinstall(8): should check available disk space from distfiles
o2011/10/30bin/162175sysinstall[patch] bsdinstall(8): add keymap selection loop and testing
f2011/10/23bin/161931sysinstallbsdinstall(8): (add sysinstall partition config as option)
o2011/10/23bin/161929sysinstallbsdinstall(8): (change partition editor screen default)
o2011/10/23bin/161928sysinstallbsdinstall(8): (add option to enable 2 button mouse copy/paste)
o2011/10/23bin/161924sysinstallbsdinstall(8): add msg box telling user to remove install media
o2011/10/23bin/161923sysinstallbsdinstall(8) games & ports install options
o2011/10/16bin/161720sysinstallbsdinstall(8): partition editor does not put partitions on even 4K boundaries
o2011/10/13bin/161547sysinstall[patch] bsdinstall(8) should identify wireless network interfaces
f2011/09/28bin/161113sysinstallbsdinstall(8): 9.0-BETA3: overwrites Win*-bootcodes without warning?
o2011/09/28bin/161101sysinstallbsdinstall(8): 9.0-BETA3: partition editor: UFS-options not saved in menu?
o2011/09/28bin/161100sysinstallbsdinstall(8): 9.0-BETA3: Add User but no Add Group
o2011/09/27bin/161056sysinstallbsdinstall(8): could allow full control over newfs arguments
o2011/09/27bin/161055sysinstallbsdinstall(8): partitioner should auto-populate GPT labels
f2011/09/27bin/161054sysinstallbsdinstall(8): partitioner should list valid "type"s
o2011/09/27bin/161053sysinstallbsdinstall(8): network setup dialog is hard to navigate
o2011/09/27bin/161052sysinstallbsdinstall(8): should be consistent about saving configuration settings
o2011/09/27bin/161050sysinstallbsdinstall(8): should use new syntax for IPv4 in rc.conf
o2011/09/27bin/161049sysinstallbsdinstall(8): could try to tell if SSDs support TRIM
o2011/09/27bin/161047sysinstall[patch] bsdinstall(8): should not run on vt0
o2011/05/19conf/157189sysinstallbsdinstall(8): Default /etc/sysctl.conf should be removed.
38 problems total.


Notes

GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '<name>(<section>)' to the Synopsis field. Consider this a prototype of a better search function.

Please give feedback on this report to linimon@FreeBSD.org. Thanks.

Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.