From owner-freebsd-current@FreeBSD.ORG Sun Oct 10 15:00:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E86E16A4CF for ; Sun, 10 Oct 2004 15:00:23 +0000 (GMT) Received: from core.zp.ua (core.zp.ua [193.108.112.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA59143D55 for ; Sun, 10 Oct 2004 15:00:21 +0000 (GMT) (envelope-from oleg@core.zp.ua) Received: from core.zp.ua (oleg@localhost [127.0.0.1]) by core.zp.ua (8.13.1/8.13.1) with ESMTP id i9AF0cfj044767; Sun, 10 Oct 2004 18:00:38 +0300 (EEST) (envelope-from oleg@core.zp.ua) Received: (from oleg@localhost) by core.zp.ua (8.13.1/8.13.1/Submit) id i9AF0clO044766; Sun, 10 Oct 2004 18:00:38 +0300 (EEST) (envelope-from oleg) Date: Sun, 10 Oct 2004 18:00:38 +0300 From: "Oleg V. Nauman" To: Ryan Sommers Message-ID: <20041010150038.GL61535@core.zp.ua> Mail-Followup-To: Ryan Sommers , freebsd-current@freebsd.org References: <20041010131532.GG61535@core.zp.ua> <41694B7C.2090205@gamersimpact.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <41694B7C.2090205@gamersimpact.com> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: mount_msdosfs tries to load nonexistent libiconv.so X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Oct 2004 15:00:23 -0000 On Sun, Oct 10, 2004 at 09:47:24AM -0500, Ryan Sommers wrote: > Oleg V. Nauman wrote: > > > So, my questions: > >1. Why dependens for the third party software not documented in the > >man 8 mount_msdosfs? > > > > > What version of FreeBSD are you on? Your mount_msdosfs binary is looking 5.3-BETA7, after fresh cvsup/buildworld/installworld/mergemaster/etc cycle. > for /lib/libiconv.so which I think is now /lib/libkiconv.so.1 (that's Sorry, no ldd /sbin/mount_msdosfs /sbin/mount_msdosfs: libkiconv.so.1 => /lib/libkiconv.so.1 (0x28076000) libc.so.5 => /lib/libc.so.5 (0x28079000) and succesfully reads /lib/libkiconv.so.1 110 mount_msdosfs CALL access(0x28073000,0) 110 mount_msdosfs NAMI "/lib/libkiconv.so.1" 110 mount_msdosfs RET access 0 110 mount_msdosfs CALL open(0x2806f020,0,0xbfbfed0c) 110 mount_msdosfs NAMI "/lib/libkiconv.so.1" 110 mount_msdosfs RET open 4 110 mount_msdosfs CALL fstat(0x4,0xbfbfecec) 110 mount_msdosfs RET fstat 0 110 mount_msdosfs CALL read(0x4,0x280699a0,0x1000) 110 mount_msdosfs GIO fd 4 read 4096 bytes 0x0000 7f45 4c46 0101 0109 0000 0000 0000 0000 |.ELF............| [skip] > what my mount_msdosfs look for anyway). I imagine this is because of the > recent library version bump, and doing an upgrade of your world (and > kernel depending how out of date your world is) will get you going. > > >2. And why not exist any fallbacks (seat bealts) for this behaviour > >in the system vital software such mount? Well, I'm ready for looking > >any '?' instead any russian letters :) but not DoS for my system under > >next reboot. This behaviour prevents from normal booting process and > >causes to prompt me for enter shell - yes, we are in the single user > >mode without any problems... > > > > > There is a seatbelt for this. Boot into single user mode. mount -uo rw > /; mount /usr; vi /etc/fstab. Comment out the offending fstab line and > then reboot. You'll be able to go multi-user while fixing the problem. > > -- > Ryan Sommers > ryans@gamersimpact.com > -- NO37-RIPE