From: Mark Gordon <spamtrap@ruddygore.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: I am not a touch typest. Wish I were.
Date: Sun, 21 Jul 2002 08:46:01 +0100 [thread overview]
Message-ID: <20020721084601.5295f6ee.spamtrap@ruddygore.net> (raw)
In-Reply-To: 3D39E0FF.9030604@seul.org
On Sun, 21 Jul 2002 00:15:27 +0200
Marko Mikulicic <marko@seul.org> wrote:
> Bart Verwilst wrote:
> > We're working on a graphical installer...
> > I'm planning to make it easier to install than Windows :)
> > Ofcourse this will be optional, and the current install will always be
> > available, and that's a garantee! :o)
> >
> > PS: This is a calling to everybody interessed, if you have ideas, drawings
> > from the layout, you're a talented graphics dude, or something, don't
> > hesitate to email me directly, we can use some help on this one :)
>
> What I like from the current handcrafted installation is that
> you see what is going on and you see that the installation is not a
> magical expert only thing, but just the matter of copying the files
> on a mounted filesystem. I like to install gentoo on machines running
> another distro or another gentoo disk because I can still use the
> machine and I have a more confortable environment where partitioning the
> disk etc.
> I think that there are some tasks which could be useful even for
> "experts":
Have all the commands and their output sent to a file so you can do a
tail -f on it from another console or examine it in more detail if
anything goes wrong.
> 1) aided partitioning. I thought of having a file describing the
> partition structure (proplist, xml, whatever is easy to write and
> process with a (python?) script) fstypes and mount points.
> Then a script would take this file and make the partitions, create
> the filesystems, and output a fstab, to be copied in the newly created etc.
> I like to think of it as a text file, but it would be nice if
> the optional graphical installation could share the same format for
> storing user configuration, before doing the job, so that users
> can decide which parts of the graphical installation are useful (or just
> doing all auto if he wishes).
> I wanting to help writing this one, if you need help.
If you are doing this make it a format easy to write by hand. Possible
the same as the fstab format with the required partition size added to
the end of the line with 0 meaning the rest of the disk.
> 2) device probing. I think it should be good if the graphical install
> (better than windows :-) would well divided from the logic that does
> device autodetection, so that users which doesn't want gfx install can
> also benefit from its detections. For example, once I needed to
> configure a asus ISDN card but I didn't know that asus was only the name
> on the box, and the cards was totaly incompatible with asus driver.
> Mandrake probed the device and configured correctly (or at least told
> me the chipset) (btw. lspci -> unknown).
<snip>
Use the hotplug scripts to find the kernel modules required? After all,
why have yet another list of how to identify each card.
--
Mark Gordon
prev parent reply other threads:[~2002-07-21 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-20 7:14 [gentoo-dev] I am not a touch typest. Wish I were D. Carrico
2002-07-20 11:26 ` Troy Dack
2002-07-20 21:57 ` Bart Verwilst
2002-07-20 22:15 ` Marko Mikulicic
2002-07-21 7:46 ` Mark Gordon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020721084601.5295f6ee.spamtrap@ruddygore.net \
--to=spamtrap@ruddygore.net \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox