-
vector as virualboxClient
I've installed vector-linux as client on my virtualbox 1.5.4. I reconned that vector as ideal distro for modest hardware, it must be ideal as virtual client as well.
Using VASM I configured my (virtual) NIC's. The first (NAT) as DHCP client and the 2nd (internal) with a hardcode IP number. That "seems" to work fine, I can communicate with my other 2 clients (debian & OS/2), but after a reboot the 2nd NIC does not come up. As root I have start it manually with VASM. I have fiddled around with VASM before I got it right, so I see "inet7" being started when I bring up my 2nd NIC. Could that be the problem?
It's a known "problem" with OS/2. It runs continuously until the underlying hardware crumbles under you hands....
the irony of quality
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|