Details
Diff Detail
- Repository
- rG FreeBSD src repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
I just tested this option to disable the bclone feature for the root pool. This worked fine. I think this is a nice option to have.
I think this is a handy feature, and can't really find any problems with it. I know that I personally prefer zstd compression, and currently I have to start the bsdinstaller myself using:
BSDINSTALL_CONFIGCURRENT=yes ZFSBOOT_POOL_CREATE_OPTIONS="-O compress=zstd -O atime=off" /usr/sbin/bsdinstall
but it would be nicer if you could directly do this in the dialog...
Generally looks good to me.
usr.sbin/bsdinstall/scripts/zfsboot | ||
---|---|---|
380 | It might nice if this showed the current options or is that potentially too large? |
Do you mean the entire command line, all command arguments, or all options/flags? The current version does all the options/flags (see attached).
(And I don't think we need to worry about input width; dialog seems to do a good job of dealing when the contents of the input box is large, you can use arrow keys to scroll left and right.)
Btw I can't view F105565279, at least not via e.g. https://reviews.freebsd.org/F105565279. There is probably some sort of permission issue.
I tried putting the options in the menu but I was worried they would quickly get too wide. But I guess if the options are too wide to view the user can make the window wider
The blank is a typo, I'll fix it.
I think I fixed the permissions on F105565279.
Address review feedback:
Show ZFSBOOT_POOL_CREATE_OPTIONS in main menu.
Remove extraneous blank in message.
So I wonder what the dialog looks like now by default on an 80x25 console? Does bsddialog do something sane to truncate the option list if it is too long or does it render oddly?
I created some frame grabs with a 80x34 xterm (my default since the 80's)
zfsboot2 is with the installation default.
zfsboot3 is with some extra (bogus) flags.
zfsboot4 is the same as zfsboot3 but with a 121x34 window.
That’s definitely a build of main? That looks to me more like GPL dialog than bsddialog.
I guess it's using dialog; if I force it to use bsddialog the output doesn't look much different to me (just the last line).
So dialog/bsddialog silently truncates overly wide output. That's better than garbling the display somehow. It might be nice if bsddialog had some sort of option to replace the end of an overly-long item with a "..." trailer, but this is certainly fine, and in particular the current default easily fits in 80 columns.
Happy to.
I'm a ports, not a src committer. Looking at the last src commit I made (c4cbf1fb) I'll need these headers, right?
PR: 282745 Approved by: jhb Differential Revision: https://reviews.freebsd.org/D47478
I think normally arc land adds Reviewed by:, but it doesn't make too much difference I guess.
Sorry to be such a noob. git doesn't like my .netrc (I think this is due to a recent change to curl) and when I remove my .netrc I get a 403 trying to push the change.
Maybe you can just avoid arc, and do a regular commit on top of main, rebasing whatever you have now. Just ensure the Differential Revision: https://reviews.freebsd.org/D47478 line is in there, then Phabricator can close this review.
When I started today, the phabricator (returning either 502 bad gateway, a broken page, or a correct looking page that wouldn't let me post a comment). I decided it would be best to wait for that to resolve...
Next, I think 2a3bac31 fixed ftp/curl's parsing of .netrc, certainly git no longer balks at my mine.
Finally, thinking about this a bit I believe my 403 problem was due to my lack of a src commit bit and no "Approved by" header. My first attempt to "arc land" consolidated the two commits in my git tree (and added a "Differential Revision" header); I used "git commit --amend" to add other headers. At that point "arc land" was happy.
Even with the "Approved by" header "arc land" still gives me 403 (as does "git push").
It's probably best if one of you guys does the commit.