public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Luke-Jr <luke-jr@gentoo.org>
To: Stewart Honsberger <blkdeath@gentoo.org>
Cc: foser <foser@foser.dyn.warande.net>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Replacing fdisk with cfdisk in
Date: Thu, 21 Aug 2003 13:33:22 +0000	[thread overview]
Message-ID: <200308211333.29393.luke-jr@gentoo.org> (raw)
In-Reply-To: <3F445A5D.4080301@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 21 August 2003 05:36 am, Stewart Honsberger wrote:
> Gentoo's installation is great because it is simple, elegant, and
> powerful. It's not cluttered with every "user-friendly" (read: attempt
> at idiot-proof) tool known to man.

No, but tools should be obvious to the user when they can be without losing 
any functionality. Nano, for example, makes itself quite obvious how to use 
and is not, AFAIK, explained anywhere in the manual. cfdisk is obvious in the 
same way. As far as the manual goes, neither nano nor cfdisk lack any needed 
functionality.

> Gentoo sets a bar at a certain height, and expects users to acheive that
> height in order to get their system off the ground. How many times are
> we going to lower the bar? As with every "user-friendly" system,
> eventually along comes a better idiot.

InGen itself is designed to make even someone who has never used a computer 
before able to install Gentoo. There could then be a problem with having 
idiots using Gentoo, but I'm sure something can be found to keep them 
seperate from "real" users.

> fdisk is a simple, standard, powerful partition table editor. I've used
> Linux's fdisk to repair botched tables more times than I can count.
> Instructions for use can be very simple.

Instructions for fdisk can be simple, as opposed to not really needing 
instructions for cfdisk at all... I'm not saying exclude fdisk (it can't be 
that big), but there's no reason to use it by default (eg in the manual).

> The last patch of the slope is the Vi(M) discussion. "Vi is hard" seems
> like a bit of a cop-out to me. Vi can be summed-up in half a dozen lines;
>
> vi <filename> - Load file for editing
> /<keyword>  - search
>
> :w - Write file to disk
> :q - Quit
>
> Commands can be combined, eg; :wq - Write file to disk and Quit
>
> Five lines and users have all the knowledge they need to create / edit
> their base system files. A few more short lines and you can explain
> (global) search/replace to give them more advanced functionality.

I don't see anything in those *4* lines explaining how to enter data (eg 'i' 
or 'a'), but like fdisk, vi would require explaining how to use it whereas 
nano is obvious, so it should be includes, but not in the manual.

> I've been seeing a lot of talk, even since the day I first wandered into
> Gentoo's user support areas (IRC, forums, mailing lists) about
> 'graphical installation front-ends', install scripts, etc.
>
> Gentoo has always been a great tool for getting users accustomed to
> their system from the inside out. Do we want to remain that way, or do
> we want to become "Just Another (Half-Assed) User-Friendly Linux
> Distro"? The likes of RedHat, Mandrake, and SuSE have fully graphical
> installation utilities that make the Windows install look complicated;
> five clicks and an hour later you're staring at your gorgeous KDE
> desktop. If we're going to aim towards user-friendlines on installation,
> we're already several years behind right out of the starting gate. Can
> we possibly compete with that? (Not to mention their respective
> corporate funding)

Of course we can. Gentoo can be for everyone at the same time. There is no 
reason we need to get rid of the manual/stages to include a GUI. InGen helps 
with this by making the GUI too simple for most "real" users to like, 
therefore most (all?) current users will continue to use the manual 
installation, as well as new experienced users.

> I'm of the opinion that we have to set barriers; lines in the sand, if
> you will. "This is how friendly we will become" and stick to those
> boundaries. This would, of course, also help with the consistency issues
> that are raised weekly on this list. ;>

I agree we may need to keep the "idiot" and "real user" communities seperate, 
but there's no reason both cannot exist.
- -- 
Luke-Jr
Developer, Gentoo Linux
http://www.gentoo.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/RMooZl/BHdU+lYMRAo/MAJ9haBE3CrBzxrU9njN7ImY5nc4+PgCeOvsx
g+YL+de5LOyPYJ6x5Tn47nA=
=oYSa
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-08-21 13:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-19  8:27 [gentoo-dev] Replacing fdisk with cfdisk in Svyatogor
2003-08-19  8:19 ` Jon Portnoy
2003-08-19 10:44   ` Camille Huot
2003-08-19 15:29   ` matt c
2003-08-19 16:11     ` Svyatogor
2003-08-19 16:18       ` foser
2003-08-20  1:16         ` Luke-Jr
2003-08-20  4:52           ` donnie berkholz
2003-08-20  8:02             ` Sven Vermeulen
2003-08-21  5:36           ` Stewart Honsberger
2003-08-21  5:54             ` Patrick Kursawe
2003-08-21  9:06             ` Sven Vermeulen
2003-08-21 13:33             ` Luke-Jr [this message]
2003-08-21 19:34               ` Stewart Honsberger
2003-08-22 14:12           ` foser
2003-08-19 18:34       ` Salze
2003-08-19 10:59 ` Lloyd D Budd
2003-08-22 19:57 ` Jason Wever
2003-08-22 22:20   ` Martin, Stephen
2003-08-22 22:25     ` Martin, Stephen
2003-08-23  3:46   ` Georgi Georgiev
2003-08-23  9:33     ` Sven Vermeulen

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=200308211333.29393.luke-jr@gentoo.org \
    --to=luke-jr@gentoo.org \
    --cc=blkdeath@gentoo.org \
    --cc=foser@foser.dyn.warande.net \
    --cc=gentoo-dev@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