Bug 24779

Summary: sysinstall 4.2 regresssions todo with standard sequence/prompting/config
Product: Base System Reporter: jay.krell <jay.krell>
Component: confAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 1.0-RELEASE   
Hardware: Any   
OS: Any   

Description jay.krell 2001-02-01 13:00:02 UTC
I don't have a good description here. I've installed FreeBSD a number of times, 3.2, 3.3, 3.4, 4.0, 4.1, and 4.2. 3.4 - 4.1 sysinstall have a pretty consistent ok (not great) experience in terms of prompting for the kinds of things I want to setup. They give the opportunity to install X, setup X, KDE or Gnome, network, add a user, etc. Now, sysinstall's handling of space and return is almost unpredictable, and that may be a big part of the problem, but every time I've run the 4.2 sysinstall, I seem to miss stuff. It doesn't prompt for for what "distro/set" I want, or space/return do the wrong thing, I end up without X, at least. I think I've also missed out on networking, adding a user, etc. I installed 4.2 about three times in the past few days, and I kept having this problem. I went back and installed 4.1, and it worked. I don't think this is me.

Fix: 

I don't know, but you should at least fix sysinstall to handle ok/cancel/back/next/space/return consistently.

And sysinstall should be X based, like a number of Linux installs I've tried recently (I may be posting to advocacy or something about the general comparison, FreeBSD did not do badly.)

But neither of these are what this smaller regression is about..
How-To-Repeat: Desire a somewhat "big" install -- esp. with X/Kde/Gnome.
Boot the 4.1 CD and go through "standard" setup -- not custom, not export, not quick.
Boot the 4.2 CD and go through "standard" setup.
Accept most defaults, and say yes to most things. The 4.1 install ends up much much closer to desired.
Comment 1 Jonathan Chen freebsd_committer freebsd_triage 2001-09-03 00:25:50 UTC
State Changed
From-To: open->closed

recent changes to sysinstall have addressed this issue.