Re: Decision time.... should NATA become the default for this release?

[Sascha Wildner <saw@xxxxxxxxx>]

1D31E.6030805@online.de> <200706022051.l52Kp9IY038754@apollo.backplane.com> <4661E79E.10307@online.de> <200706022259.l52Mx5Oo039863@apollo.backplane.com> <4661FCC4.7020204@online.de> <200706022359.l52NxvfN040370@apollo.backplane.com>
In-Reply-To: <200706022359.l52NxvfN040370@apollo.backplane.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 46
NNTP-Posting-Host: 87.78.98.243
X-Trace: 1180829800 crater_reader.dragonflybsd.org 794 87.78.98.243
Xref: crater_reader.dragonflybsd.org dragonfly.kernel:11106

Matthew Dillon wrote:
>     Crashes as in seg faults in init?
> 
>     Are you getting any console errors or warnings at all?

Crashes as in "rcorder segfaults". I had written it some mails earlier. 
Here's the output I get:

start_init: trying /sbin/init
pid 4 (rcorder), uid 0: exited on signal 11
Segmentation fault
pid 5 (sysctl), uid 0: exited on signal 11
Segmentation fault
pid 6 (rcorder), uid 0: exited on signal 11
Segmentation fault

Sat Jun  2 23:52:08 CEST 2007
Jun  2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port 
/dev/ttyv0: No such file or directory
Jun  2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port 
/dev/ttyv1: No such file or directory
Jun  2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port 
/dev/ttyv2: No such file or directory
Jun  2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port 
/dev/ttyv3: No such file or directory
Jun  2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port 
/dev/ttyv4: No such file or directory
Jun  2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port 
/dev/ttyv5: No such file or directory
Jun  2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port 
/dev/ttyv6: No such file or directory
Jun  2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port 
/dev/ttyv7: No such file or directory

>     See if you can boot into single user mode and natacontrol ad0 to
>     PIO4 mode or something like that.

When I boot into single user mode, /bin/sh will segfault.

I'll burn a NATA LiveCD later and check out if I can access my hard disk 
from it.

Sascha

-- 
http://yoyodyne.ath.cx