Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yoyo.aarnet.edu.au!fang.dsto.defence.gov.au!foxhound.dsto.gov.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!news.sprintlink.net!gryphon.phoenix.net!phoenix.phoenix.net!pflores From: pflores@phoenix.net (Paul Flores) Newsgroups: comp.unix.bsd.freebsd.misc,comp.unix.bsd.freebsd.questions Subject: Re: Possible (re)convert from Linux - specific questions Followup-To: comp.unix.bsd.freebsd.misc,comp.unix.bsd.freebsd.questions Date: 17 Sep 1995 14:16:16 GMT Organization: Phoenix Data Systems Lines: 79 Message-ID: <43hajg$8kc@gryphon.phoenix.net> References: <42q3ua$f1t@mentor.cc.purdue.edu> <42q9ak$9ce@helena.MT.net> <vmd9d0gt83.fsf@thyme.statsci.com> NNTP-Posting-Host: phoenix.net X-Newsreader: TIN [version 1.2 PL2] Scott Blachowicz (scott@statsci.com) wrote: : >>>>> "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... Hmmm, have you tried mounting it rw ? I have been mounting both my 'C' and 'D' drive partitions with 2.0.5 since I installed; with 0 problems. Just for the record: two drive 486/SLC 66 System with: VLB IDE controller! Drive 0 = 850 Meg 250 Meg FAT partition The rest is FreeBSD Drive 1 = 350 Meg ALL FAT : 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 chance you might have a flaky controller? (Seen stuff like this when the controller wan't quite up to FreeBSDs requirements. Please note, the same controller worked well for DOS/Windows and Linux) Paul Flores