Subject: Re: bad system call revisited
To: Colin Wood <cwood@ichips.intel.com>
From: Michael G. Schabert <mikeride@prez.buf.servtech.com>
List: port-mac68k
Date: 08/30/1997 02:10:22
>Michael G. Schabert wrote:
>>
>> Hi again, Bill,
>>
>> I just tried cpin'ing the base & "tar -xvf base ./sbin/*" to re-do the
>> entire /sbin directory. During the extraction, it spit out that it
>> couldn't extract the link from swapon to swapctl because the file
>> existed. I renamed the file & manually created the link, hoping that we
>
>Take a look at the FAQ.  There is a pretty good description of how to
>install/reinstall archives, including how to avoid the above problems.
>
>> had just switched something with that. Unfortunately, I still dump out.
>> Here's what I see from swapctl:
>>
>>
>> <paraindent><param>right,left</param>swapctl: adding /dev/sd0b as swap
>> device at priority 0
>>
>> automatic boot in progress: starting file system checks.
>>
>> Usage: fsck [-dfnpy] [-b block] [-c level] [-m mode] filesystem ...
>>
>> path to shell or <<return> for sh:
>
><tirade>
>Please don't use HTML!!! It makes it really hard to read for the vast
>majority of people on this list who probably don't use Netscape to read
>their mail.
></tirade>

Actually, I use Eudora, not NetScape.

>sorry about that....anyway, it looks like you still need to upgrade you
>/etc scripts as well.  I believe the problem is a result of a bug in fsck
>which was just mentioned on current-users.  If your /etc/fstab lists
>NetBSD partitions as type 'ufs', then fsck barfs on it.  You need to
>change the types to 'ffs' and see if that helps.

I already changed that in the etc/fstab awhile ago :(

>> It seems that the boot script is screwing up how to call fsck, which is
>> dumping out. What file is it taking its cues from at that point?
>
>This is happening in the very early stages of /etc/rc.  If multi-user boot
>ever dumps you out like this, you can do the fsck by hand, then exit from
>single-user and it should go ahead and boot multi-user.

Unfortunately, fsck isn't finding anything. fsck -p just tells me the
system's marked clean. fsck -f just gives me the stats, which means I
should be good to go.

Any other suggestions?
Mike

Bikers don't *DO* taglines.