Re: [Vectorlinux-devel] VL6.0-SOHO-A1.9.21

[Newtor <gen...@gm...>]

Hello,

I'm doing a pretty straight-forward installation with the exception of updating
the installer each time:

    Boot from CD (iso)
    hit 'enter' at boot options
    wait for desktop/installer to start
    quit installer
    kill dhcpd pid
    get static network going (ifconfig, resolv, route, etc)
    start installer (gbr2 /root/speedy/vinstall-ng.gambas)
    click next through choices
    re-use partitions (but have tried new ones as well)
    full installation (but have tried custom and light as well)
    lilo bootloader (but have tried grub2 as well) - using default choices for both
    overall, a pretty normal installation

I'll give the default installer supplied on 1.21 a shot without updating to see if
it makes any difference. I plan on reusing partitions but reformatting; default
choices throughout (just 'next'); lilo bootloader; etc.

....I'm back. I just retested the install with no installer updates and it
installs correctly - root and user account passwords are set correctly. The one
exception is that the installer did not prompt for the 2nd CD, but this WAS the
old installer so perhaps it was simply a bug back then.

At this point, I'll make the assumption that the bug is introduced when updating
the installer or starting it manually. Here's my method for updating the installer
and starting it manually:

>>> 'kill 3827' (dhcpcd pid)
>>> 'ifconfig eth0 down'
>>> 'leafpad /etc/resolv.conf'
>>> add 'nameserver 192.168.100.1' and save&exit
>>> 'ifconfig eth0 192.168.100.252 netmask 255.255.255.0 up'
>>> 'route add default gw 192.168.100.1'
>>> 'cd speedy'
>>> 'svn up'
>>> received 'updated to revision 702'
>>> 'gbr2 /root/speedy/vinstall-ng.gambas'

Perhaps I'm not invoking the installer correctly?

I'll finish up with installing via 702 and report back.

Cheers, newt

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Thursday, August 6, 2009, 1:13:07 PM, you wrote:

ML> Yeah... you see?

ML> For some reason your /proc, /sys, /dev and /tmp are not mounted on the
ML> target. So that produces the the segmentation fault.

ML> Can you give me details how you are doing the installation...?
ML> install type
ML> booloader setup choice, etc?