Technical discussion of improvements to NetBSD's installation software

Jeremy C. Reed | 18 May 2012 17:24

some failures in sysinst

This is from sysinst from HEAD fromabout ten days ago.

I chose the Config menu option. Next screen says assume you want to 
configure a prior installation. Well I didn't install yet. But says 
"enter to continue". If no option to abort, then should just do the 
detection step:

The next step is attempt to fsck and command failed with bad super 
block. Next screen: It appears is not a BSD file syste ... "upgrade" has 
been aborted. Error number 8.

It is not an "upgrade".

Then next screen shows configuration choices "a: Configure network" 
through "j: Enable mdnsd".  Then 6 junk error lines overwriting it 
(white text on black where other menu is white text on blue):  No such 
file ... and ... Could not open /targetroot/tmp/checkrc.sh for writing: 
No directory.  (I can press Ctrl-L but regular users would be scared.)

By the way, it said the full install is 31 MB (no X) or 81 MB (with X). 
Normally it is around 230MB and 330 MB. Why does it suggest small size?

headers

Julian Djamil Fagir | 18 May 2012 18:25

Re: some failures in sysinst

Hi,

> This is from sysinst from HEAD fromabout ten days ago.
> 
> I chose the Config menu option. Next screen says assume you want to 
> configure a prior installation. Well I didn't install yet. But says 
> "enter to continue". If no option to abort, then should just do the 
> detection step:
perhaps we should make clearer *what* the configuration menus do.
One for configuring the installer, one for configuring an installation.

> The next step is attempt to fsck and command failed with bad super 
> block. Next screen: It appears is not a BSD file syste ... "upgrade" has 
> been aborted. Error number 8.
> 
> It is not an "upgrade".
> 
> Then next screen shows configuration choices "a: Configure network" 
> through "j: Enable mdnsd".  Then 6 junk error lines overwriting it 
> (white text on black where other menu is white text on blue):  No such 
> file ... and ... Could not open /targetroot/tmp/checkrc.sh for writing: 
> No directory.  (I can press Ctrl-L but regular users would be scared.)
You should never have gotten there. This bug could have been fixed along with
install/12020.
I will recheck that fix I pasted and maybe eventually commit it.

Regards, Julian

headers

Julian Djamil Fagir | 19 May 2012 20:33

Re: some failures in sysinst - fix attached

Hi,

> > Then next screen shows configuration choices "a: Configure network" 
> > through "j: Enable mdnsd".  Then 6 junk error lines overwriting it 
> > (white text on black where other menu is white text on blue):  No such 
> > file ... and ... Could not open /targetroot/tmp/checkrc.sh for writing: 
> > No directory.  (I can press Ctrl-L but regular users would be scared.)
> You should never have gotten there. This bug could have been fixed along
> with install/12020.
> I will recheck that fix I pasted and maybe eventually commit it.
the attached patch should fix this issue, at least it did for me.
It changes the return codes such that now find_disks() returns the right
codes. Plus, it asks when a bad fs was found whether the installer should
really continue (and offers to do so), this is btw a fix for install/12020.

Regards, Julian

Attachment (sysinst.1.diff): text/x-patch, 5472 bytes