Thanks Gilad, it looks like my /sbin/init is corrupted.  The md5 of my init
didn't match that of another user.  And my system hangs at /sbin/init during
boot.  Does anyone have any suggestions on how to safely replace /sbin/init
without erasing data on the drive?

I have FBSD 4.9 stable, I try running upgrade from my the 4.9 RELEASE CD.
Everything seems to be fine till the point after I select the installation
media (I chose CD-ROM), it say it that it can't read data from /dev/acd0.

I can try FTP option, but does anyone have a better sugguestions on how to
replace a working copy of /sbin/init on to the root dir?

Tree

-----Original Message-----
From: Gilad Rom [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 04, 2004 7:24 AM
To: treeml
Cc: [EMAIL PROTECTED]
Subject: Re: verify md5 for /sbin/init (v1.7.2.3 2002/08/12 11:17:37 ) on
FreeBSD Stable 4.9

treeml wrote:
> My machine hangs at /sbin/init on boot, I just want to check if /sbin/init
> is corrupted or not.  I have FreeBSD 4.9 stable on PIII 866.
>
> Here is the md5
> MD5 (/mnt/sbin/init) = a7dc0528ae8a102c96f51dc516aa7f62
>
> ident /mnt/sbin/init
>
> Gave out a long list of results, but at the end of the list, which is also
> the most recent is the following.  $FreeBSD:
> src/lib/libc/locale//ldpart.c,v1.7.2.3 2002/08/12 11:17:37 ache Exp $
>
> If anyone out there can verifies the md5 sum of "/sbin/init" of the
version
> listed above, that would be very helpful.

Here is mine:
MD5 (/sbin/init) = bdcf745dd758b38727ba97f24be471e5
and ident /sbin/init shows:
$FreeBSD: src/lib/libc/locale/ldpart.c,v 1.7.2.3 2002/08/12 11:17:37
ache Exp $

This is from FreeBSD 4.9-RC1.

However, from a 4.9-STABLE box, I get
MD5 (/sbin/init) = 3ce17ad04b21e20b91204dd9867e8f80
and ident /sbin/init shows:
$FreeBSD: src/lib/libc/locale/ldpart.c,v 1.7.2.4 2003/12/22 20:45:16 jkh
Exp $

Gilad.

_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to