Re: 2.0 installer integration

[Dave Hayes <dave@xxxxxxxxxxx>]

Matthew Dillon <dillon@apollo.backplane.com> writes:
>     Probably the best way to test the installer is to use a virtual kernel
>     environment.  Create two virtual disks (vkd's), one with the CD image
>     that you 'boot' from, and the other that you install to.  

That's a great idea. How do you give a vkernel more filesystem
devices?

This is probably naive, but:

# cp /usr/release/root/dfly.iso /var/vkernel/test.iso
# cd /usr/src/sys/compile/VKERNEL
# ./kernel.debug -v -m 512m -r /var/vkernel/test.iso
Using memory file: /var/vkernel/memimg.000000
KVM mapped at 0x40000000-0x80000000
Copyright (c) 2003, 2004, 2005, 2006, 2007 The DragonFly Project.
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
Slab ZoneSize set to 128KB
DragonFly 1.8.2-RELEASE #1: Thu May 24 03:29:19 PDT 2007
    root@cddev.foo.com:/usr/src/sys/compile/VKERNEL
real memory = 536870912 (524288K bytes)
avail memory = 519045120 (506880K bytes)
Leaving critical section, allowing interrupts
md0: Malloc disk
Device configuration finished.
initclocks
IP packet filtering initialized, divert disabled, rule-based forwarding 
enabled, default to accept, logging disabled
lo0: bpf attached
ppp0: bpf attached
sl0: bpf attached
DUMMYNET initialized (011031)
faith0: bpf attached
IPsec: Initialized Security Association Processing.
Mounting root from ufs:vkd0a
vkd0: invalid primary partition table: no magic
Root mount failed: 22

Manual root filesystem specification:
  <fstype>:<device>  Mount <device> using filesystem <fstype>
                       eg. ufs:da0s1a
  ?                  List valid disk boot devices
  <empty line>       Abort manual input

mountroot> cd9660:vkd0c
Mounting root from cd9660:vkd0c
vkd0: invalid primary partition table: no magic
iso_mountroot(): using session at block 0
vkd0: invalid primary partition table: no magic
cd9660: RockRidge Extension
start_init: trying /sbin/init
Loading configuration files.
. 
kern.seedenable: 0 -> 1
kern.seedenable: 1 -> 0
Starting file system checks:
cd9660: /dev/vkd0c: Invalid argument

Setting hostname: .
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet 127.0.0.1 netmask 0xff000000 
        inet6 ::1 prefixlen 128 
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
Additional routing options:.
Mounting NFS file systems:.
Building databases...
NFS CLIENT: nfsiod access_cache_timeout=5 neg_cache_timeout=3
ELF ldconfig path: /usr/lib /usr/lib/gcc34 /usr/lib/gcc41 /usr/lib/compat 
/usr/local/lib
Starting local daemons:.
Updating motd.
Configuring syscons: blanktimeeval: cannot open /dev/ttyv0: Device not 
configured
. 
Initial i386 initialization:.
Additional ABI support:.
Local package initialization:.
Additional TCP options:.
Starting pfi...
Looking for pfi.conf on /dev/acd0c...mount_cd9660: /dev/acd0c: Device not 
configured
 not found
Looking for pfi.conf on /dev/da0s1...mount_msdos: /dev/da0s1: Device not 
configured
 not found
Looking for pfi.conf on /dev/da1s1...mount_msdos: /dev/da1s1: Device not 
configured
 not found
Looking for pfi.conf on /dev/fd0...mount_msdos: /dev/fd0: Device not configured
 not found
Looking for pfi.conf on /dev/fd1...mount_msdos: /dev/fd1: Device not configured
 not found

Thu May 24 10:43:09 GMT 2007

. ..and then it hangs. It appears close anyway, at least for me.
------
Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org 
>>> The opinions expressed above are entirely my own <<<

"Better to be safe than to be sorry" is a remark of value
only when these are the actual alternatives.