On Sat, Mar 14, 2009 at 2:21 PM, David Cantrell <dcantrell@xxxxxxxxxx> wrote:
thats not very good, especailly compared to what it would take to retain the feature.
We could stop right at that. As long as its easy and wont require much code maintence? I dont know that selecting package groups would require much more code.
the text mode install. I guess it will save a lot of ram with the package lists removed, etc. Isn't that the main reason that drove the minimum ram requirement sky high?
not unless you plan to install numerous times, or have already have a ks file handy, otherwise why not just remove text mode completely. My idea was just to keep it usable but static.
BTW, F10 anaconda is excellent, i've tested it extensively and couldnt find anything wrong. I see many of the modules have to rewritten now, so it will be nice to test it.
I'll add my comments, I'm sure others on the team can add some comments too.While I understand that you use the text mode installer in the situations you describe, the big problem for us has been maintaining two installer interfaces. They were never equivalent and almost always had their own bugs. Our goal has been to reduce the amount of code we have to maintain in the text mode installer rather than increase it. We chose text mode as the mode to reduce because we already have the GUI interactive mode and we have kickstart. Text mode seemed redundant.
On 03/14/2009 10:24 AM, solarflow99 wrote:
I was just hoping to share some thoughts on the new text mode changes.
I have used text mode since the beginning, and often depended on it more
than the clunky GUI mode. Many times the need for text mode is because
of a ram shortage, so VNC insn't going to help. Can we give
consideration to the following:
I know, I can understand the reasons for this, and have followed the information available to learn about the issues involved. I wouldnt say text mode is redundant though.
Kickstart can do this. Even if you want to manually lay out your partitions, you can run parted or sfdisk in %pre and then use the part command in kickstart with the --onpart switch.
- Advanced Partitioning. Can we at least allow 1 thing from the second
screen, to choose partitions to install on? Like /, /boot, etc. no
creating partitions, raid, or LVM. maybe an option to run fdisk could
even be brought back?
http://fedoraproject.org/wiki/Anaconda/Kickstart
thats not very good, especailly compared to what it would take to retain the feature.
The problem here is where do you stop? If groups are available, why stop there? Someone will ask for individual package selections after that and pretty soon we get a complex set of text mode screens to do what we already do in the graphical mode and in kickstart.
- Package Selection. Is allowing only package groups feasible without
much difficulty? This package lists are common arent they?
The %packages section in a kickstart file can do what you're looking for. Groups specified with '@', packages removed with '-'.
We could stop right at that. As long as its easy and wont require much code maintence? I dont know that selecting package groups would require much more code.
This is probably a good idea. I thought the dialog box had good text, but I can't say I've looked at it in a while.
- When text mode is selected with "linux text", I think the dialog that
recommends vnc should explain WHY, at least for now. So instead of the
1 line explanation, something more like this one:
http://fedoraproject.org/wiki/Documentation_Beats_Installer
How much ram what will save?
- Any guess as to to how much ram requirement this will save?
the text mode install. I guess it will save a lot of ram with the package lists removed, etc. Isn't that the main reason that drove the minimum ram requirement sky high?
I would think advanced users would want to be using kickstart. Kickstart has always offered more than what our text mode interface has been able to do.
I guess we could now consider text mode to be for advanced users only,
so it could be changed with that in mind, just basic functionality
should do.
Construct your own kickstart file using system-config-kickstart, starting with /root/anaconda-ks.cfg from any other installation, or just write one on your own.
not unless you plan to install numerous times, or have already have a ks file handy, otherwise why not just remove text mode completely. My idea was just to keep it usable but static.
BTW, F10 anaconda is excellent, i've tested it extensively and couldnt find anything wrong. I see many of the modules have to rewritten now, so it will be nice to test it.
--
David Cantrell <dcantrell@xxxxxxxxxx>
Red Hat / Honolulu, HI
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
