Alex:

What are you saying is this cobaltcd.iso file located at 
ftp://ftp.netbsd.org/pub/NetBSD/iso/2.1/ works as recovery cd??, thanks 
again.



Claudio Leiva
Las Vegas, Nevada
USA
 http://nv4x4.no-ip.org/claudio
(Powered by NetBSD for Cobalt)




----- Original Message ----- 
From: "Alex Pelts" <alexp@broadcom.com>
To: "Claudio Leiva S" <cleivas@cox.net>
Cc: <port-cobalt@netbsd.org>
Sent: Wednesday, November 23, 2005 11:20 AM
Subject: Re: 2.1 Kernels do notbootwhenbootedwithbootloaderotherthannetbsd 
bootloader.


> There is one with current. Just google for it. You could also make one 
> yourself by following instructions here:
> http://restorecd.homeunix.org/NetBSD/restorecd-howto.html
>
> I think that I gave up on cygwin as a host. NFS is too unreliable and 
> dhcpd is the same. I currently have vmware machine that you can boot on 
> windows and from which you can boot the qube. I do not have bootable 
> kernel, but hopefully with Izumi's help will have one real soon.
>
> Then I will srink the machine, as it is in excess of 200M without the sets 
> inside, and publish it along with instructions on how to use it.
>
> VmWare has a free player that anyone can use to run VMs. I am aiming 
> towards universal restore/recovery environment for qube.
>
> Thanks,
> Alex
>
>
> Claudio Leiva S wrote:
>> Hi:
>>
>> I was wondering if somebody  is going to make a restore cd with netbsd 
>> 2.1, thanks.
>>
>>
>>
>> Claudio Leiva
>> Las Vegas, Nevada
>> USA
>> http://nv4x4.no-ip.org/claudio
>> (Powered by NetBSD for Cobalt)
>>
>>
>>
>>
>> ----- Original Message ----- From: "Alex Pelts" <alexp@broadcom.com>
>> To: "Izumi Tsutsui" <tsutsui@ceres.dti.ne.jp>
>> Cc: <port-cobalt@netbsd.org>
>> Sent: Wednesday, November 23, 2005 8:56 AM
>> Subject: Re: 2.1 Kernels do 
>> notbootwhenbootedwithbootloaderotherthannetbsd bootloader.
>>
>>
>>> The file says:
>>> bash-2.05b$ file /usr/bin/config
>>> /usr/bin/config: ELF 32-bit LSB MIPS-I executable, MIPS, version 1 
>>> (SYSV), for NetBSD 3.99.7, dynamically linked (uses shared libs), not 
>>> stripped
>>>
>>> I think you are right. This config is an artifact from multiple 
>>> installations on the same machine. I dont understand though why would it 
>>> bus error.
>>> doing ldd on it produces following:
>>> bash-2.05b$ ldd /usr/bin/config
>>> /usr/bin/config:
>>>          -lc.12 => /usr/lib/libc.so.12
>>> doing ls on the the library :
>>> bash-2.05b$ ls -l /usr/lib/libc.so.12
>>> lrwxr-xr-x  1 root  wheel  21 Oct 24 19:37 /usr/lib/libc.so.12 -> 
>>> /lib/libc.so.12.114.1
>>>
>>> and
>>>
>>> bash-2.05b$ ls -l /lib/libc.so.12.114.1
>>> -r--r--r--  1 root  wheel  1243760 Oct 24 19:31 /lib/libc.so.12.114.1
>>>
>>> So all files are there. I must write the script that would cleanup all 
>>> files that are not present in the sets so after installation of new 
>>> version no artifacts are left. I was thinking about that for a while but 
>>> never did it.
>>>
>>> Regards,
>>> Alex
>>>
>>>
>>
>>
>>
>>
>>
>
>