Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.netspace.net.au!serval.net.wsu.edu!netnews.nwnet.net!oracle.pnl.gov!osi-east2.es.net!lll-winken.llnl.gov!uwm.edu!psuvax1!news.ecn.bgu.edu!newspump.wustl.edu!news.starnet.net!wupost!thor.inlink.com!paragon.inlink.com!jim From: jim@paragon.inlink.com (Jim Kelley) Newsgroups: comp.os.386bsd.bugs Subject: Re: FreeBSD-2.0 problem with copying MSDOS files to/from the floppy drive. Date: 29 Jan 1995 14:27:04 GMT Organization: Paragon.InLink.com Lines: 15 Sender: Jim Kelley Message-ID: <3gg8jo$ca2@thor.inlink.com> References: <3g0qqh$t7i@darkstar.ucsc.edu> NNTP-Posting-Host: paragon.inlink.com In article <3g0qqh$t7i@darkstar.ucsc.edu>, Chris Haidinyak <chrish@cats.ucsc.edu> wrote: > > 2.) When exchanging diskettes after a FreeBSD-2.0 write, the > system doesn't recognize that the data has changed. Stupid > question but do I have to run a command to "freshen" the > files FreeBSD sees? > > To "freshen" the files seen, you need to 'umount' the floppy you're currently working with BEFORE pulling it out, wait until the system is finished spinning it, THEN swap floppies and 'mount' the new one. Jim