*BSD News Article 51619


Return to BSD News archive

Newsgroups: comp.unix.bsd.freebsd.misc,comp.unix.bsd.freebsd.questions
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.uwa.edu.au!classic.iinet.com.au!news.uoregon.edu!usenet.eel.ufl.edu!news.ultranet.com!news.sprintlink.net!in2.uu.net!statsci.com!news
From: scott@statsci.com (Scott Blachowicz)
Subject: Re: Possible (re)convert from Linux - specific questions
In-Reply-To: gurilla@iii.net's message of Wed, 13 Sep 1995 13:03:21 GMT
X-Nntp-Posting-Host: thyme
Message-ID: <vmd9d0gt83.fsf@thyme.statsci.com>
To: gurilla@iii.net (*ANONYMOUS*)
Lines: 55
Sender: scott@thyme.statsci.com
Reply-To: scott@statsci.com
Organization: StatSci div. of MathSoft, Seattle, WA USA
X-Newsreader: Gnus v5.0.2
References: <42q3ua$f1t@mentor.cc.purdue.edu> <42q9ak$9ce@helena.MT.net>
	<gurilla.4.0123C9EC@iii.net>
Date: Sun, 17 Sep 1995 04:50:21 GMT

>>>>> "anon" == *ANONYMOUS*  <gurilla@iii.net>

 anon>   In Linux, I usually ended up using it's ftp/telnet to download,
 anon> which ended up going into my Linux filesystem. Then I copied them
 anon> into my /dos1 directory, are you saying I can't do that with
 anon> FreeBSD?

I'd love to find out how to get my FAT file systems mounted reliably at
all (even as read-only mounts, though I'd much prefer read-write). I've
been having all sorts of grief with my BSD file systems getting corrupted
when I have them mounted read-only. I don't understand why _I_ should be
having these problems and if it is not just me, how any serious OS on a PC
type system can get away with not dealing with FAT file systems.

I've been posting messages (to c.u.b.misc and questions@freebsd.org) of
various incarnations of my problems getting 2.0.5R installed from the
Walnut Creek CDROM. I've finally reached the conclusion that the 'msdos'
file system is not useable. But, I keep mentioning this in case I manage
to tickle the right memory cells in someone who might know if or how it is
possible to do this. I can forward fdisk and/or disklabel outputs to
anyone interested in taking a shot at helping. I'm debating whether or not
I should try taking Walnut Creek up on their "unconditional guarantee" on
the CD, but I REALLY want to keep FreeBSD...

I completely reinstalled 2.0.5 from CD again (including newfs'ing all the
relevant partitions and not mounting any DOS discs - boy am I glad I got
the CD :-)). It seemed to work fine for a while. Then I mounted my C:
drive (wd0s1) read-only and did a 'find' command down it...

	% mkdir /c
	% mount -r -t msdos /dev/wd0s1 /c
	% find /c -xdev -print

The find command gave me various results when I ran it different times...

	find: /c/msoffice/?????????.???: No such file or directory

complaining about garbage filenames. Shortly after that, I did

	% ls /sbin
	ls: /sbin: Bad file descriptor

and got messages like this:

	......... syslogd: /var/run/tmp: not a directory

I threw a 3 finger salute at the keyboard and got this:

	/: bad dir ino 2 offset 0: mangled entry
	panic: bad dir
	Syncing...1 1 1 1 1 1 1 1 1 1 1 1 1 
	[at this point I hit the reset button, but I don't remember if the
	syncing stopped or not]

Any clues on how to get a useable 'msdos' file system setup?
-- 
Scott Blachowicz    Ph: 206/283-8802x240    StatSci, a div of MathSoft, Inc.
                                            1700 Westlake Ave N #500
scott@statsci.com                           Seattle, WA USA   98109
Scott.Blachowicz@seaslug.org