committer filter by committer.
@path/to/ filter by path in repository.
committer@path/to/ filter by committer AND path in repository.
NNN or rNNN filter by revision.
NNN-MMM or rNNN-rMMM filter by revisions range (inclusive).
Multiple filters can be specified separated by spaces or comas in which case they'll be combined using OR operator.
|r257842||dteske||Nov. 8, 2013, 9:57 a.m.||A series of changes tested together as a whole:
+ Add a `-D FILE" command-line option for overriding the path to the bsdinstall log file (BSDINSTALL_LOG env var). + Document new `-D FILE' in the man page for bsdinstall. + If FILE in `-D FILE' begins with a +, debug output goes to stdout (interleaved between dialog(1) invocations/output) as well as to FILE (minus the leading + of course). + If BSDINSTALL_LOG cannot be written, then debugging is disabled (except in the case of a leading + in the pathname, wherein debug will still be printed to stdout). + Update source code formatting style. + Fix a dangling participle ("Begun ..." -> "Began ...") + Rewrite the docsinstall script (was necessary to abate direct dependency on BSDINSTALL_LOG (instead, use fault-tolerant bsdconfig framework which displays appropriate errors for package management). NB: docsinstall is still using pkg(8) after this change. + Add additional debug output for dhclient/rtsol/wpa_cliscan + Display script errors in a textbox rather than just on stdout + Update many coments. + Add new f_show_err() API call (like f_show_msg but changes the dialog title to "Error")(see bsdconfig's `common.subr'). + Add new f_eval_catch() API call for executing a command via eval but not before logging the command to debug. Several example cases documented in API header for function in bsdconfig's `common.subr'. + Fix dialog auto-sizing when launched as an rvalue to a pipe for indirected scripts (previously would default to 24x80 sizing in this case, now it can autosize to full size even when in a pipe chain). + Fix bug in f_snprintf if $format argument began with "-"; printf would misinterpret as a flag. (this is in bsdcofig's `strings.subr'). + Add accompanying f_sprintf() and f_vsprintf() to go along with already existing f_snprintf() and f_vsnprintf() (see bsdconfig's `strings.subr'). + Remove some unnecessary default ZFS datasets from the automatic "zfsboot" script. Such as: /usr/ports/distfiles /usr/ports/packages /usr/obj /var/db /var/empty /var/mail and /var/run (these can all be created as-needed once the system is installed). + Remove setuid=off for /usr/home (as discussed from last round of CFT). + Fix some i18n string violations in "zfsboot". + Bolster debugging output in "zfsboot". + Fix some string quoting issues in "zfsboot". + Fix some variable scope issues in "zfsboot". + Change "Create" to "Install" in "zfsboot" main menu. + Increase error checking in "zfsboot" (type-check arguments and such). + Add call to "graid destroy" killing automatic metadata (part of the series of pedantic destructions we do when bootstrapping a new/naked disk). + Make judicious use of new f_eval_catch() in "zfsboot". + Fixup some variable names for consistency (zfsboot). + Fix an underride syntax parameter expansion folly (zfsboot). + Confirm layout if not explicitly chosen when blindly proceeding (no longer have to touch anything on the ZFS menu if it scares you, just choose the omnibus "Install" option at the top and you'll be prompted to select vdev type and disks in the layout confirmation dialog). + Change numbered menu items to alphabetic for more efficient navigation. + Consolidate vdev selection and disk selection into a single stateful menu which performs validation and allows backing out to each previous menu as you go deeper. + Redesign the ``Last Chance'' dialog (still using the same colors, but make it conform to a tolerable width and make disks appear in a block- quote style indented region). + Fix a bug wherein we used the a lowercase variable name by accident (actual variable name declared as all-uppercase) at the time of initializing fstab(5) (not believed to cause any issues though). + Update the geli setup infobox for each provider being initialized (not just at the onset -- since each ``geli init'' causes kernel messages to push our infobox off-screen). Reviewed by: Allan Jude <firstname.lastname@example.org> Discussed on: -current MFC after: 3 daysViewVC
|r257841||glebius||Nov. 8, 2013, 8:44 a.m.||Catch up with sb_timeo type change in r255138. This fixes
smbfs operation. PR: kern/182963 Submitted by: Tomoaki AOKI <junchoon dec.sakura.ne.jp>ViewVC
|r257838||ian||Nov. 8, 2013, 5:11 a.m.||Build kernel tools along with other tools during world build, as well as
during kernel build (if they didn't get done with world). This will make -DMODULES_WITH_WORLD work, and it ensures the kernel tools are built as part of 'make kernel-toolchain'.ViewVC
|r257831||smh||Nov. 7, 2013, 11:21 p.m.||Corrected definition for old_rate to match d_rotation_rate
MFC after: 2 Days X-MFC-With: r256956ViewVC
|r257830||dteske||Nov. 7, 2013, 11:05 p.m.||Document SYSRC_VERBOSE enviroment variable in the manual.|
|r257829||dteske||Nov. 7, 2013, 11:04 p.m.||Fix a bug with `-e' that broke sometime around when I added `-F'. Also,
revamp the `-e' output to truly be sh(1) compatible syntax (even if passed in `-v' for verbose output).ViewVC
|r257828||dteske||Nov. 7, 2013, 11:01 p.m.||Comments and whitespace.|
|r257827||dteske||Nov. 7, 2013, 11 p.m.||Add a `-c' option for `check only' to determine if a value is set
(get command) or if the current value is the same as what is desired (set command). In those cases, the return status is success. Otherwise, if the variable is unset (get command) or set to a different value that what is desired (set command), returns with error status. This is useful for puppet integration as well as everyday scripting.ViewVC
|r257826||dteske||Nov. 7, 2013, 10:52 p.m.||Add new `--version' long option for getting the version (good for
comparing against the ports revision).ViewVC
|r257825||ian||Nov. 7, 2013, 10:50 p.m.||Instead of modeling the kernel-tools build after the bootstrap tools, build
kernel tools the way cross-tools get built. This seems to result in the tool getting installed in the right place. It also seems more correct in retrospect, because if a tool emitted code or binary data as part of building the kernel, it should do so in target-specific ways (endianess, architecture, whatever). That issue is moot for aicasm, our only current tool, but it still seems to be more correct in principle.ViewVC
|r257824||dteske||Nov. 7, 2013, 10:47 p.m.||Fix a bug that prevented `-d' from working as-documented in sysrc(8).
Rather, prevent a bunch of debugging information from spewing onto the screen when using the `describe' flag (misinterpreted as `debug' by the automatatic initialization routines).ViewVC
|r257823||kargl||Nov. 7, 2013, 10:46 p.m.||Yet, another attempt to fix the libm breakage due to the
changes in s_roundl.c to use bit twiddling. Reported by: ianViewVC
|r257821||dteske||Nov. 7, 2013, 9:52 p.m.||Extend loader_delay as-documented in beastie.4th(8) and delay.4th(8), making it available to architectures that do not use or load the beastie
menu. This is reported to save headaches on some PPC systems where unload followed by load does not produce the desired results wherein if-given the opportunicy to abort the initial loading sequence, you can customize the first load. Reviewed by: nwhitehorn, kan Discussed on: -currentViewVC
|r257820||sbruno||Nov. 7, 2013, 9:47 p.m.||Add support for controlling mfi(4) controller properties:
allow user control of rebuild rate allow user control of silence/enable alarm MFC after: 2 weeks Sponsored by: Yahoo! Inc.ViewVC
|r257819||dteske||Nov. 7, 2013, 9:38 p.m.||Use `pkg -vv' to obtain ABI for validating a chosen media server (done
prior to diving head-long into a pkg-update(8), et. al). This should also be more future-proof than what was being done just before this.ViewVC