Re: Bug#217503: Evil autopartkit should _NEVER_ _NEVER_ try to overwrite an unknown partition table
On Tue, Oct 28, 2003 at 09:08:35PM -0700, Chris Tillman wrote:
> On Tue, Oct 28, 2003 at 07:18:30PM +0100, Sven Luther wrote:
> > On Tue, Oct 28, 2003 at 06:55:35PM +0100, Gaudenz Steinlin wrote:
>
> > I still think that the real problem is in the modularity of
> > debian-installer. It is all nice to have a bunch of modules be used and
> > have each provide a menu entry, but how do you guarantee structure and
> > coherence of the entries ? I would like that someone (maybe me, but i am
> > maybe not the best placed for it) made a analysis of what is really
> > supposed to happen in the install process, and how the tasks are
> > supposed to follow each others. I can make a begining of UML diagrams
> > for it, if you like, altough i am not really aware of all the
> > debain-installer details.
>
> This would also be fantastic for install manual writing purposes. I
> find it very difficult to understand, much less explain, how all the
> pieces fit together.
>
> I'm also attempting to understand the myriad of targets and images
> that will be available, we'll have to explain to users how to choose
> the one they need.
Ok, i will have a start at it, but as i am mostly not able to view the
full current d-i, i may miss some of the things, but we can complete
that later on. I will be using ArgoUML, which is, albeit somewhat buggy,
available as a debian package.
Friendly,
Sven Luther
Reply to: