--------------003B7F434A7D09C78DD5D791
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Bodo Bauer wrote:
> Tom Schaefer wrote:
> >
> > Some areas for you to fix:
> >
> > 1. When installing from CD 1, packages determined to be on CD 2 and 3
> > are not allowed to be installed during the first pass install. The
> > friggin' installer just blows past the prompt and the user is not
> > allowed to insert the other CDs.
> >
> > There is some sort of bug that does not prompt for CD 2 or 3. I have
> > found that if I insert the CD I want to install from, then run YAst,
> > Yast seems to determine that there are a bunch of packages that weren't
> > installed. DUH. Then, it seems to install them - but only the packages
> > for the CD that is currently in the drive. This behavior is somewhat
> > inconsistent, but predictable. Then, after installing packages from the
> > second CD, I can exit Yast, remove the CD, then insert CD 3 and run
> > Yast, who happens to "discover" that there are packages that weren't
> > installed. The I can install them.
> >
> > I thought you would have fixed this, as it was a problem in 5.0.
> >
> > 2. After the install "appears" to be done, leaving the user with a login
> > prompt and no clue that you have a bunch of background processes
> > running, and no idea of whether rebooting at this time is wise or not.
>
> You get a message which tells you what's going on before the login
> prompt appears. It also tells you that you can watch the scripts
> running
> on console 9.
>
Yes, but the messages are meaningless and are not informative as to finish
time, etc.The installer should not allow the user to anything which would
jeopardize the install.
> > However, by probing around, I see the Yast installer is unpacking
> > MAN pages and all sorts of other stuff, unbeknownst to the user.
> > You need to alert the installer that something else is happening.
>
> It's generating a locate DB, a apropos DB, doublechecks the
> permissions, etc.
>
It shouldn't do the locate db stuff unless the user wants to. It adds quite a
bit of time to wait for it to finish.
> > I have noticed that if you reboot too soon, Yast appears to be activated
> > at boot up to either finish or do MORE stuff, which is not properly
> > explained. So I never really know if everything has been installed
> > properly.
>
> If you install the system the very first time, you can't switch the
> CDs because your root filestystem is on CD1.
THEN EXPLAIN THIS DURING THE INSTALL.
> That's why yast is
> started right after rebooting the system. It should now complete the
> installation and ask you for CD2 and or CD3 to get the missing
> packages
> installed.
>
NO IT DOES NOT ... Once you reboot the system, the installer may start, but
there is nothing prompting me to insert Cd2, and since that is not explained
- why would I be inserting CD2 or 3 after a reboot? SIMPLIFY!
You can reboot and just use the machine how you see fit after the first
reboot. Nothing is being explained on the console directly to the installer
(user) that you are going to need CD 2 or 3. NEVER.
What you fail to understand, that anyone that has previously used Solaris,
Caldera, Slackware, or even Red Hat - you don't reboot the machine to finish
the install. All packages are extracted, THEN the machine is configured and
THEN you do a reboot.
If you've mounted CD 1 as a filesystem, then you can UNMOUNT IT for CD 2 and
3.
Sheeeeeeeeesh
> This always worked for me, so I wonder about your problems... ?!
>
You are overfamiliar with your installer. SIMPLIFY SIMPLIFY SIMPLIFY
Watch someone who has NEVER installed from your distribution. And don't coach
them along the way.
You'll see what I mean.
> Then Yast starts some scripts like told above. If these scripts don't
> get enough time to finish (because of a reboot) the procedure starts
> again...
>
YES BUT THIS IS NOT EXPLAINED. The first time I installed your 5.0, I wrongly
assumed the install was finished when in fact it was still completing as
explained before.
I wound up digging thru a bunch of the startup scripts and disabling the YAst
startup - NOT EVEN KNOWING WHY YAST WAS STARTING -
OR WHY IT HAD FAILED TO FINISH INITIALLY.
> So look at console 9 (like the message tells you) before you reboot
> your system. If anything has finished processing
Needs to be more informative and specific.
Hand your distribution to someone who has absolutely NO familiarty with your
product and watch what they do.
Turn off the updatedb and locatedb processes and alert the user that they do
need to be run, and if they don't run them now, they'll be run in cron.daily
or something.
SIMPLIFY!
You guys have a nice package - but you have over complicated a few things.
Also, getting YAst to run without the CD is problematic at times when all I
want to do is see which packages I have on the system, I can't unless I
insert a CD. Fix that. I should be able to browse the package database
without having to load a CD.
Have a lot of fun!
--------------003B7F434A7D09C78DD5D791
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<HTML>
Bodo Bauer wrote:
<BLOCKQUOTE TYPE=CITE>Tom Schaefer wrote:
>
> Some areas for you to fix:
>
> 1. When installing from CD 1, packages determined to be on CD 2 and
3
> are not allowed to be installed during the first pass install. The
> friggin' installer just blows past the prompt and the user is not
> allowed to insert the other CDs.
>
> There is some sort of bug that does not prompt for CD 2 or 3. I have
> found that if I insert the CD I want to install from, then run YAst,
> Yast seems to determine that there are a bunch of packages that weren't
> installed. DUH. Then, it seems to install them - but only the
packages
> for the CD that is currently in the drive. This behavior is somewhat
> inconsistent, but predictable. Then, after installing packages from
the
> second CD, I can exit Yast, remove the CD, then insert CD 3 and run
> Yast, who happens to "discover" that there are packages that weren't
> installed. The I can install them.
>
> I thought you would have fixed this, as it was a problem in 5.0.
>
> 2. After the install "appears" to be done, leaving the user with
a login
> prompt and no clue that you have a bunch of background processes
> running, and no idea of whether rebooting at this time is wise or
not.
You get a message which tells you what's going on before the login
prompt appears. It also tells you that you can watch the scripts
running
on console 9.
</BLOCKQUOTE>
Yes, but the messages are meaningless and are not informative as to finish
time, etc.The installer should not allow the user to anything which would
jeopardize the install.
<BLOCKQUOTE TYPE=CITE>
> However, by probing around, I see the Yast installer is unpacking</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>> MAN pages and all sorts of other stuff, unbeknownst
to the user.
> You need to alert the installer that something else is happening.
It's generating a locate DB, a apropos DB, doublechecks the
permissions, etc.
</BLOCKQUOTE>
It shouldn't do the locate db stuff unless the user wants to. It adds quite
a bit of time to wait for it to finish.
<BLOCKQUOTE TYPE=CITE>
> I have noticed that if you reboot too soon, Yast appears to be activated
> at boot up to either finish or do MORE stuff, which is not properly
> explained. So I never really know if everything has been installed
> properly.
If you install the system the very first time, you can't switch the
CDs because your root filestystem is on CD1.</BLOCKQUOTE>
THEN EXPLAIN THIS DURING THE INSTALL.
<BLOCKQUOTE TYPE=CITE>That's why yast is
tarted right after rebooting the system. It should now complete the
installation and ask you for CD2 and or CD3 to get the missing
packages
installed.
</BLOCKQUOTE>
NO IT DOES NOT ... Once you reboot the system, the
installer may start, but there is nothing prompting me to insert Cd2, and
since that is not explained - why would I be inserting CD2 or 3 after a
reboot? SIMPLIFY!
You can reboot and just use the machine how you see fit after the first
reboot. Nothing is being explained on the console directly to the installer
(user) that you are going to need CD 2 or 3. NEVER.
What you fail to understand, that anyone that has previously used Solaris,
Caldera, Slackware, or even Red Hat - you don't reboot the machine to finish
the install. All packages are extracted, THEN the machine is configured
and THEN you do a reboot.
If you've mounted CD 1 as a filesystem, then you can UNMOUNT IT
for CD 2 and 3.
Sheeeeeeeeesh
<BLOCKQUOTE TYPE=CITE>
This always worked for me, so I wonder about your problems... ?!
</BLOCKQUOTE>
<B><FONT COLOR="#FF0000">You are overfamiliar with your installer.
SIMPLIFY SIMPLIFY SIMPLIFY</FONT></B><B><FONT COLOR="#FF0000"></FONT></B>
<B><FONT COLOR="#FF0000">Watch someone who has NEVER installed from
your distribution. And don't coach them along the way.</FONT></B>
You'll see what I mean.
<BLOCKQUOTE TYPE=CITE>
Then Yast starts some scripts like told above. If these scripts don't
get enough time to finish (because of a reboot) the procedure starts
again...
</BLOCKQUOTE>
YES BUT THIS IS NOT EXPLAINED. The first time
I installed your 5.0, I wrongly assumed the install was finished when
in fact it was still completing as explained before.
I wound up digging thru a bunch of the startup scripts and disabling
the YAst startup - NOT EVEN KNOWING WHY YAST WAS STARTING -
OR WHY IT HAD FAILED TO FINISH INITIALLY.
<BLOCKQUOTE TYPE=CITE>
So look at console 9 (like the message tells you) before you reboot
your system. If anything has finished processing</BLOCKQUOTE>
Needs to be more informative and specific.
Hand your distribution to someone who has absolutely NO familiarty
with your product and watch what they do.
Turn off the updatedb and locatedb processes and alert the user that
they do need to be run, and if they don't run them now, they'll be run
in cron.daily or something.
SIMPLIFY!
You guys have a nice package - but you have over complicated a few things.
Also, getting YAst to run without the CD is problematic at times
when all I want to do is see which packages I have on the system, I can't
unless I insert a CD. Fix that. I should be able to browse the package
database without having to load a CD.
Have a lot of fun!
</HTML>
--------------003B7F434A7D09C78DD5D791--
--
To get out of this list, please send email to majordomo(a)suse.com with
this text in its body: unsubscribe suse-linux-e
