src-test2/usr.sbin/sysinstall/dmenu.c, branch release/8.4.0FreeBSD source treehttps://cgit-dev.freebsd.org/src-test2/atom?h=release%2F8.4.02007-10-30T05:03:37ZSelecting amd and a few other things in the Networking config section2007-10-30T05:03:37ZKen Smithkensmith@FreeBSD.org2007-10-30T05:03:37Zurn:sha1:327433d2a20555f7b0b2437143c8f7bddd37d0c0
caused a segfault. It turns out that in pre-7.0 systems if you do
getenv("amd_enable=YES") it will return the setting of the environment
variable "amd_enable" but now it returns NULL. I think I found the
places where sysinstall was potentially relying on that old behavior.
Fix is to make a copy of the string to be used for the getenv(3) call,
look for a '=' character in it, and replace it with '\0' if one is
found. Stuck to sysinstall's typical coding standards despite urges
to do otherwise.
PR: 117642
MFC after: 2 days
Fix numerous warnings. Aside from menu items in system.c and menu.c2006-02-28T21:49:33ZJohn Baldwinjhb@FreeBSD.org2006-02-28T21:49:33Zurn:sha1:9d4514b0fdac8c06657e1812b8b27e4d964388e0
this now compiles on i386 with WARNS?= 3. Most of the fixes included
adding missing 'static' keywords to internal functions, using fully-defined
terminators in statically defined arrays of structs, and various
signed vs unsigned mismatches. Also G/C'd unused configSecurity()
function.
- Autogenerate a menu containing a list of countries and keymaps supported2006-02-28T20:29:43ZJohn Baldwinjhb@FreeBSD.org2006-02-28T20:29:43Zurn:sha1:d30d1cdee63745f59e7bd393c3b87f1da3b71b00
by syscons.
- If we are running as init, popup the country menu before the main menu.
If a non-default country is chosen, then a second menu is brought up
to let the user choose a keymap. By default the default keymap for
the country that was selected is highlighted. If the user chooses the
default country, then the default keymap is just assumed and the user
is not presented with the keymap menu. Currently the default country
is set to "United States" except for PC98 which assumes "Japan".
PR: bin/93853
Submitted by: Seth Kingsley sethk at magnesium dot net
MFC after: 3 days
Fix 3 'cast to pointer from integer of different size' warnings.2003-09-17T03:45:30ZMarcel Moolenaarmarcel@FreeBSD.org2003-09-17T03:45:30Zurn:sha1:9862c36bfb24fb1d0939945de3bd81c9bf5d822a
While here, fix the long line bugs in the same statements.
Whoops - really make the "fix" I did to the dmenuToggleVariable logic2000-03-08T14:20:26ZJordan K. Hubbardjkh@FreeBSD.org2000-03-08T14:20:26Zurn:sha1:976e0e0dd092e6492e347f88e6255032bafe83e7
work.
Toggle variables between YES and NO values, don't just set them to YES2000-02-26T12:07:40ZJordan K. Hubbardjkh@FreeBSD.org2000-02-26T12:07:40Zurn:sha1:a90fc31d369944f52f8e82cb5616cedc59131c64
or unset them. That makes it impossible to turn something off.
Completely rip-out and redesign sysinstall's refresh model as well1999-12-14T04:25:29ZJordan K. Hubbardjkh@FreeBSD.org1999-12-14T04:25:29Zurn:sha1:7025aeb16e091cf9515535424d0532b53c618b83
as redoing all the menus to have proper, or at least non-hallucinogenic,
keyboard accelerators.
This requires my recent update to libdialog to work properly and will
probably also exhibit some other "interesting" behavior while the last
few missing screen clears are found (which is why I'm not going to MFC
immediately). At least now, however, sysinstall does not gratuitously
redraw random screens at the drop of a hat and drive serial console
installers out of their minds.
$Id$ -> $FreeBSD$1999-08-28T01:35:59ZPeter Wemmpeter@FreeBSD.org1999-08-28T01:35:59Zurn:sha1:97d92980a96a50750844f420cc225ddf918f0699Ack! Correct a typo which crept into here and reshuffle the index back1999-02-06T08:45:20ZJordan K. Hubbardjkh@FreeBSD.org1999-02-06T08:45:20Zurn:sha1:61bbe58e1707e048adca64caa351c8034aa42634
into alphabetical order.
Add one more "escape" for marking internal variables.1999-02-05T22:25:13ZJordan K. Hubbardjkh@FreeBSD.org1999-02-05T22:25:13Zurn:sha1:b1e7bed4c0a33b6edf3849ab775bb9abc831fef1