1 |
Well, I'm glad to see that people are interested. After doing some |
2 |
initial research I have some thoughts. First, we should decide on whether |
3 |
we want to have a terminal or X based installer. Does anyone know how |
4 |
well the generic vesa driver works for X? I personally have battled with |
5 |
X so many times that I'm not sure I think its worth it for an installer. |
6 |
(Although we could just use the RedHat stuff for autodetection etc. if we |
7 |
want to go that direction.) Besides X we could use ncurses dialog |
8 |
widgets or another terminal gui package. I was thinking it would be cool |
9 |
to use somethine lighter than X like svgalib. I have no experience with |
10 |
it and don't know how cross platform (or cross video card) it is, but it |
11 |
could be a cool solution if a decent widget set is put on top of it. I'm |
12 |
not sure if this would lead to more or less work than using X. |
13 |
As for choosing stages, that should be a decision made by the user |
14 |
at install time. We can very briefly explain how the system works and let |
15 |
them do what they please. For the complete novice we can basically have |
16 |
the "do everything for me" button. For the supreme hacker we can let them |
17 |
have it all while still taking care of mundane details. (For example, |
18 |
they could choose what file systems they want to use on what partitions, |
19 |
but that would just be a selection dialog rather than having to type the |
20 |
commands etc...) It might be nice if the installer can be exited at any |
21 |
point so people have the ability to get things rolling quickly but then |
22 |
tweak things out to their hearts content once its where they want it. |
23 |
One of the major pains in the redhat like installers deals with |
24 |
package selection. I think it is ridiculous to give people a list of a |
25 |
thousand packages and tell them to pick. Especially since the package |
26 |
documentation is horrible. Most people probably wouldn't know that its |
27 |
important for them to have the e2fsprogs installed, for example. So, this |
28 |
is the portion of the installer where I see the most room for innovation. |
29 |
Especially since gentoo has such a unique package system, we should really |
30 |
try to enable the user as much as possible, rather than just hucking a |
31 |
bunch of packages into the mix. I'm still working on ideas, but we should |
32 |
experiment with all kinds of stuff to get this stage really smoothed out. |
33 |
This idea of processor detection makes me think that a whole lot |
34 |
of detection could go on if we wanted it to. The thing is detection is |
35 |
useless unless you can act on what you have detected. Changing some CPU |
36 |
related compiler flags is one thing, but what about detecting network, |
37 |
sound, video, raid, scsi, firewire, printers etc. This could all get very |
38 |
tricky real fast. What about using RedHats kudzu? |
39 |
|
40 |
Peace, |
41 |
Jeff |
42 |
|
43 |
|
44 |
On Sun, 13 Apr 2003, Derek J. Belrose wrote: |
45 |
|
46 |
> The only problem I see with doing this is how to represent it in a user |
47 |
> friendly, yet power user accessible fashion. Maybe if you are using |
48 |
> anaconda, you could have the power user abilities under "Amazing super |
49 |
> power user" setting :) |
50 |
> |
51 |
> Grabbing the processor isn't difficult, build a small database of known |
52 |
> processors and compare it to /proc/cpuinfo. |
53 |
> |
54 |
> At this point, what would you use for a install? Stage1, 2 or 3? Stage |
55 |
> 3 would be the quickest in my opinion as well giving the user a really |
56 |
> good launching pad for an optimized system. |
57 |
> |
58 |
> Cliff Free wrote: |
59 |
> |
60 |
> >I think a GUI installer would be great if done correctly. The |
61 |
> >interface, obviously, should be easy to use, but in the spirit of |
62 |
> >Gentoo, shouldn't limit the user with what he can do. On a side note, I |
63 |
> >also think it would be cool to have the ability to detect the processor |
64 |
> >type(s) and include some optimization flags for the detected |
65 |
> >processor(s) (I also feel this feature should be able to be toggled so |
66 |
> >hard-core power-users would still have the option to fine-tune to their |
67 |
> >heart's content, and that by default the feature would be OFF. Maybee |
68 |
> >the detection system would only augment CFLAGS and CXXFLAGS in |
69 |
> >make.conf. and/or make.conf settings would override what's detected.) |
70 |
> >Just my 2 cents worth. Doing this correctly could prove to be a |
71 |
> >daunting task. |
72 |
> > |
73 |
> >On Sun, 2003-04-13 at 01:38, Derek J. Belrose wrote: |
74 |
> > |
75 |
> > |
76 |
> >>Is the Mandrake install system based on RedHat's anaconda? If it is, |
77 |
> >>it's nicely written python...but you'll have to seriously hack it to get |
78 |
> >>rid of the neat little rpm stuff :) |
79 |
> >> |
80 |
> >>I'd be willing to help out a bit on this too...gotta get it going for |
81 |
> >>Gentoo-Sparc :) |
82 |
> >> |
83 |
> >>Derek |
84 |
> >> |
85 |
> >>Justin Whitney wrote: |
86 |
> >> |
87 |
> >> |
88 |
> >> |
89 |
> >>>I think some or all of Mandrake's install system is under GPL as well, |
90 |
> >>>so you might want to check that out. |
91 |
> >>> |
92 |
> >>>--Justin |
93 |
> >>> |
94 |
> >>>On Fri, 2003-04-11 at 19:04, Jeff Rose wrote: |
95 |
> >>> |
96 |
> >>> |
97 |
> >>> |
98 |
> >>> |
99 |
> >>>>Hello, |
100 |
> >>>> I'm pretty new to gentoo, but I am an instant convert. Just a |
101 |
> >>>>few months of emerge bliss and now I'm an avid supporter. Anyway, I'm |
102 |
> >>>>thinking about starting a summer project and I'm pondering the idea of a |
103 |
> >>>>gui installer. I've been looking around a bit and it doesn't look like |
104 |
> >>>>anyone is working on one. Is that true? If there isn't already a project |
105 |
> >>>>then I think I'll give it a whirl. I know, I know, gentoo is so great |
106 |
> >>>>because it allows you to customize and tweak the hell out of everything. |
107 |
> >>>>That is completely true. So, an installer would have to allow just as |
108 |
> >>>>much but it could take care of the mundane details for those who aren't |
109 |
> >>>>interested or knowledgable enough. |
110 |
> >>>> I haven't been around to see what people discuss in terms of the |
111 |
> >>>>installer so I'm sorry if this is all stuff that you have gone over |
112 |
> >>>>hundreds of times. Even more minimal than a gui installer, have you |
113 |
> >>>>thought about adding more scripts to do the standard directory setup, |
114 |
> >>>>download, chroot... type of stuff? |
115 |
> >>>> What do you think? |
116 |
> >>>> |
117 |
> >>>>-Jeff |
118 |
> >>>> |
119 |
> >>>> |
120 |
> >>>>-- |
121 |
> >>>>gentoo-dev@g.o mailing list |
122 |
> >>>> |
123 |
> >>>> |
124 |
> >>>> |
125 |
> >>>> |
126 |
> >>>> |
127 |
> >>>-- |
128 |
> >>>gentoo-dev@g.o mailing list |
129 |
> >>> |
130 |
> >>> |
131 |
> >>> |
132 |
> >>> |
133 |
> >>> |
134 |
> >> |
135 |
> >>-- |
136 |
> >>gentoo-dev@g.o mailing list |
137 |
> >> |
138 |
> >> |
139 |
> |
140 |
> |
141 |
> |
142 |
> -- |
143 |
> gentoo-dev@g.o mailing list |
144 |
> |
145 |
|
146 |
|
147 |
-- |
148 |
gentoo-dev@g.o mailing list |