On 9/18/07, Douglas A. Tutty <[EMAIL PROTECTED]> wrote: > > You are given a brand new machine; you bring your install CD; and after > > four minutes of using the standard tools (disklabel, fdisk, ifconfig, > > ...) you are already very familiar with, you have a fully working box, > > modulo afterboot. > > The only issue I've seen is that if you are new to OBSD, even if used to > the command line in Linux (not clicky-pointy-lindows) fdisk and > disklabel are new. On linux, the standard non-GUI partitioner is cfdisk > (curses fdisk) while there is not such thing as disklabel).
fdisk isn't new; any operating system that has had to partition an i386 system carries along with it the same fdisk-ish pardigm. whether you call it fdisk, or cfdisk, or anaconda disk partitioning, or windows setup, people have been doing the same damn thing for years and shouldn't find differences in implementation intimidating. disklabels aren't a strictly unique thing either; several systems have them. even Linux has to deal with disklabels on non-x86 platforms (e.g. Sun boxen) e.g. http://www.gentoo.org/doc/en/handbook/handbook-sparc.xml?part=1&chap=4. > To my mind, even a curses interface to cfdisk and disklabel is not > necessary, but a little more help, e.g. a mini-menu along the bottom, > would go a long way. Blech. http://www.openbsd.org/faq/faq4.html http://www.openbsd.org/faq/faq14.html ftp://ftp.openbsd.org/pub/OpenBSD/4.1/i386/INSTALL.i386 There are resources a-plenty; anyone who finds it confusing is either trying to install without having read docs, or is not familiar with computers in the first place (and thus needs to read the docs.) Computer users need to get smarter, instead of technology getting dumber for them. DS
