Le jeudi 28 mai 2015 à 18:40 +0200, Otto Moerbeek a écrit :
> On Thu, May 28, 2015 at 05:33:01PM +0200, Bastien Durel wrote:
>
> [snip]
> > Which speed should com0 use? (or 'done') [57600]
> > Setup a user? (enter a lower-case loginname, or 'no') [no]
> > What timezone are you in? ('?' for list) [Europe/Paris]
> >
> > Available disks are: sd0.
> > Which disk is the root disk? ('?' for details) [sd0]
> > Use DUIDs rather than device names in fstab? [yes]
> > Disk: sd0 geometry: 3649/255/63 [58626288 Sectors]
> > Offset: 0 Signature: 0xAA55
> > Starting
> >
> > erase ^?, werase ^W, kill ^U, intr ^C, status ^T
> >
> > Welcome to the OpenBSD/amd64 5.7 installation program.
> > (I)nstall, (U)pgrade, (A)utoinstall or (S)hell?
> >
> >
> > If I try to restart install, I get struck at the same step.
> >
> > fdisk ran from console exists with code 130:
> > # fdisk sd0
> > Disk: sd0 geometry: 3649/255/63 [58626288 Sectors]
> > Offset: 0 Signature: 0xAA55
> > Starting #
> >
> >
> > # echo "$?"
> > 130
> >
> > Is there a way to find from where the error comes ?
>
> That would mean killed by SIGINT (^C), but that doesn't make a lot
> of sense here.
>
> -Otto
>
Looks like many programs crashes this way :
# ls
.profile etc install.sub sbin usr
bin install mnt tmp var
dev install.md mnt2 upgrade
#
# echo $?
130
But not in any case :
# ls -l
total 112
-rw-r--r-- 1 root wheel 1486 Mar 8 17:06 .profile
drwxr-xr-x 2 root wheel 512 Mar 8 17:06 bin
drwxr-xr-x 2 root wheel 2048 Mar 8 19:53 dev
drwxr-xr-x 4 root wheel 512 Mar 8 19:53 etc
-rwxr-xr-x 1 root wheel 4490 Mar 8 17:06 install
-rw-r--r-- 1 root wheel 2548 Mar 8 17:06 install.md
-rw-r--r-- 1 root wheel 41430 Mar 8 17:06 install.sub
drwxr-xr-x 2 root wheel 512 Mar 8 17:06 mnt
drwxr-xr-x 2 root wheel 512 Mar 8 17:06 mnt2
drwxr-xr-x 2 root wheel 512 Mar 8 17:06 sbin
drwxrwxrwt 2 root wheel 512 Mar 8 19:53 tmp
-rwxr-xr-x 1 root wheel 926 Mar 8 17:06 upgrade
drwxr-xr-x 6 root wheel 512 Mar 8 17:06 usr
drwxr-xr-x 6 root wheel 512 Mar 8 17:06 var
#
# echo $?
0
tried with many baud rates, and it *may* influence *when* programs
crashes : with 115200 bauds ls outputs more data before crashing ; but
ls -l output even more and does not crash, so I can't conclude it's
output-related ...
--
Bastien
