[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    RE: [gentoo-dev] Graphical Installer
From:       "Riyad Kalla" <rsk () u ! arizona ! edu>
Date:       2002-11-21 15:05:25
[Download RAW message or body]

Oh sweet! Is this going to be in 1.4 x86 for sure? I like the idea of
autoinstall (or unattended.txt as well all know :), and the abstraction
of architecture-dep into the one class.

Do you have any screenshots of it handy? Does it follow the install
manual's steps pretty closely? What kind of control do we have at
different stages? (i.e. making partitions)

I'm excited...

> -----Original Message-----
> From: Nicholas Henke [mailto:roughneck@gentoo.org] 
> Sent: Thursday, November 21, 2002 8:01 AM
> To: Riyad Kalla
> Cc: hannes@gentoo.org; gentoo-dev@gentoo.org; gentoo-core@gentoo.org
> Subject: Re: [gentoo-dev] Graphical Installer
> 
> 
> On Thu, 21 Nov 2002 06:41:57 -0700
> "Riyad Kalla" <rsk@u.arizona.edu> wrote:
> 
> > Haha that's a fantastic name. Whoever continues/works on 
> the ncurses 
> > installer, please keep the name!
> 
> Hehe -- yeah that was a bit of inspired work. Larry rules!! :)
> 
> Now onto the more serious stuff -- cursingcow is 95% ready 
> for use in the 1.4 release on PPC. I have not had much time 
> lately to work on it, but I am taking a week's vacation and 
> starting Dec 2, I will be poolishing it off. For x86, the 
> only thing I have left to do is grub configuration, the rest is done. 
> 
> I suppose I should really let you (core-gentoo) in on the 
> design of cursingcow.... Well, it is all python, and is 
> ncurses and gtk based. The gtk interface is more a token 
> example right now -- it really doesnt look good nor function 
> yet. It uses a statemachine architecture with a 'cargo' of 
> data passed between states. Each state is designed to be a 
> separate step, so adding new steps, or replacing old ones is 
> quite easy.
> 
> There is also an autoinstallation mode -- take a look at 
> autoinstall.txt. You do need to provide a few extra files, 
> like a make.conf, kernel.config, but the installer will build 
> you a system with no user interaction. The autoinstall.txt 
> can also be used in interactive mode to preload data. This 
> allows you to walk through the installer, but not having to 
> input the data each time. 
> 
> For those of you working on 
> sparc/alpha/strongarm/fiddlydodump/ the design of cursingcow 
> is to abstract all of the arch dependent code into one class, 
> which needs to be coded for your arch ( see arch.py ).
> 
> I would really like to hear any and all comments on this!
> Nic
> -- 
> Nicholas Henke
> Linux Cluster Systems Programmer
> Liniac Project - Univ. of Pennsylvania
> 


--
gentoo-dev@gentoo.org mailing list

[prev in list] [next in list] [prev in thread] [next in thread]