hello all,
I burned the ISO that Jordan released the other day and while I haven't gone
through the entire binary installation yet, I booted the machine and fiddled
inside sysinstall a bit. Here's some feedback:
o Is there a way to increase the number of lines of console output that are
"remembered" when you hit Scroll-Lock. Is this the MSGBUF_SIZE parameter? What
would be the consequences of increasing this slightly? The reason I ask is
that after hitting the sysinstall screen, I used the Scroll-Lock trick to view
the probe messages. There are lots of cards in this machine and thus there
were so many probe messages I "lost" the upper N of them. I just figure
increasing this slightly might increase the chance that somebody won't "miss"
an early probe message which might help them debug an issue.
o When I went to the "Packages" submenu of the "post-install configure"
portion of sysinstall, I noticed the following errata:
- The first line in the scrolling dialog says there is a package category
named ".3" with "No description provided" as the description. If you
select this "category" it comes up with a dialog showing gnome-1.0.53 with
OK / Cancel buttons.
- At the very bottom of the scrolling list right after the "x11-wm"
category, I see another "category" called "xpm-3.4k" with "No description
available" again. Like before, selecting this brings up the same "gnome"
dialog box.
sysinstall code errata, or just a format issue in the INDEX file it reads???
o I went to the "configure X desktop" option and accidentally hit RET on the
"GNOME+E" option (keep in mind, I hadn't label/partitioned or extracted
anything to any disk just yet). Very quickly I hit ^C and it briefly brought up
a dialog box asking me if I wanted to abort the current action
(paraphrasing--I didn't have time to write down the message). Before I could
hit "yes," the machine spontaneously rebooted.
Admittedly, this is not an "orthodox" way of testing, but "users will be
users." I don't know what the issue could be here. Maybe it's a sysinstall
errata that caused the machine to reboot--maybe it tried to extract something
from the CD onto a partition that hadn't been created/mounted at that point
(this seems solvable if that is the case). Who knows, all I know is the
machine rebooted after hitting ^C .....
While I don't have the savvy to try and dig into the sysinstall code to
pinpoint the problems, QA'ing was asked for and those are things I found :)
... I hope they are helpful ....
More in a few days when I get the new drive in and actually go through the
whole binary installation....
-Jr
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation
[EMAIL PROTECTED] My opinions are mine, not Intel's. Running
[EMAIL PROTECTED] FreeBSD 3.4-STABLE. FreeBSD: The Power to Serve.
http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
