From: Bdale Garbee <bdale@gag.com>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] 712/60 boots fine
Date: Fri, 21 Sep 2001 10:42:51 -0600 [thread overview]
Message-ID: <87g09gpkac.fsf@rover.gag.com> (raw)
In-Reply-To: <200109211603.KAA01633@puffin.external.hp.com> (grundler@puffin.external.hp.com's message of "21 Sep 2001 10:06:08 -0600")
grundler@puffin.external.hp.com (Grant Grundler) writes:
> =?iso-8859-1?Q?Andreas_H=E4rtel?= wrote:
> > It is difficult to understand for a newbie, that PALO needs file system type
>> 'F0' but this type is unknown by fdisk.
>> Or the 2. mistake, the partition where vmlinux is located must be lower or
>> equal 2 GByte.
>
> Both issues are documented in the palo documentation.
Clearly, then, "just" having them documented is insufficient.
I noted when doing an install from the 0.9.2 CD myself the other day that we
paint a splash screen before disk partitioning explaining that there needs to
be a palo partition, but that splash screen doesn't mention the 2G issue.
Perhaps it could be updated with some additional text?
Also, since cfdisk is the default partitioning tool called by the Debian install
process, if the definition of partition type F0 isn't already part of the
list of partition types displayed by cfdisk when you pick the command to change
the partition type, perhaps it should get added? It might well be disconcerting
to a new user without much Debian or hppa experience to have to type in a
partition type that's not on the menu.
I think those two steps would improve the probability that folks are successful
installing.
Finally, it sounds as though the user-space palo executable is not checking all
of these constraints to warn the user about problems, though I haven't tried to
test that and so don't really know what it does or does not do. It certainly
seems prudent for palo to do so... and give the user some guidance through
appropriate warning/error text about what to do to fix the problem.
In summary, I think we ought to be thinking about how to help the user get this
right beyond "just" making sure the constraints are documented.
Bdale
next prev parent reply other threads:[~2001-09-21 16:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 8:38 [parisc-linux] 712/60 boots fine Andreas Härtel
2001-09-21 9:14 ` Richard Hirst
2001-09-21 16:03 ` Grant Grundler
2001-09-21 16:42 ` Bdale Garbee [this message]
2001-09-21 17:31 ` Grant Grundler
2001-09-21 19:17 ` thunder7
2001-09-25 1:50 ` Grant Grundler
2001-09-21 21:04 ` Richard Hirst
-- strict thread matches above, loose matches on Subject: below --
2002-01-13 20:34 [parisc-linux] 715/50 geezer
2002-01-13 22:07 ` [parisc-linux] Re: sid vs woody (was 715/50) Grant Grundler
2002-01-14 10:47 ` Andreas Deresch
2002-01-14 17:42 ` Bdale Garbee
2002-01-14 18:41 ` Grant Grundler
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=87g09gpkac.fsf@rover.gag.com \
--to=bdale@gag.com \
--cc=parisc-linux@lists.parisc-linux.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