Prev: iPad musings
Next: iPad ad
From: jim on 2 Jun 2010 16:10 Tim Streater <timstreater(a)waitrose.com> wrote: >>> If it's doing that repeatedly, wot's the chance it's doing that >>> umpty-ump times in the cache (if the file is cached, which seems to >>> happen a lot) and then only once on yer actual disk? >> >> I'd like to think that Apple aren't -quite- that daft :-) > > Er well, me too neither, but what triggers the cache to write out - or > > is there an API call to do it? I've never delved that deep, but I'd imagine there are ways of saying 'access the disk directly'. Jim -- Sent from my iPad
From: Richard Tobin on 2 Jun 2010 17:42 In article <timstreater-BC92B3.21014202062010(a)news.individual.net>, Tim Streater <timstreater(a)waitrose.com> wrote: >> > If it's doing that repeatedly, wot's the chance it's doing that >> > umpty-ump times in the cache (if the file is cached, which seems to >> > happen a lot) and then only once on yer actual disk? >> I'd like to think that Apple aren't -quite- that daft :-) >Er well, me too neither, but what triggers the cache to write out - or >is there an API call to do it? The Posix function is fsync(). I believe MacOS X has its own ones too. -- Richard
From: Phil Taylor on 2 Jun 2010 19:34 In article <hu6j7o$20l$1(a)pc-news.cogsci.ed.ac.uk>, Richard Tobin <richard(a)cogsci.ed.ac.uk> wrote: > In article <timstreater-BC92B3.21014202062010(a)news.individual.net>, > Tim Streater <timstreater(a)waitrose.com> wrote: > > >> > If it's doing that repeatedly, wot's the chance it's doing that > >> > umpty-ump times in the cache (if the file is cached, which seems to > >> > happen a lot) and then only once on yer actual disk? > > >> I'd like to think that Apple aren't -quite- that daft :-) > > >Er well, me too neither, but what triggers the cache to write out - or > >is there an API call to do it? > > The Posix function is fsync(). I believe MacOS X has its own ones too. FlushVol. Been there since time immemorial. Phil Taylor
From: Rowland McDonnell on 2 Jun 2010 21:23 Gavin <gwilbyREMOVE(a)stoof.co.uk> wrote: > David Kennedy wrote: > > Steve H wrote: > >> David Kennedy<davidkennedy(a)nospamherethankyou.invalid> wrote: > >>> Woody wrote: > >>>> Conor<conor(a)gmx.co.uk> wrote: > >> > >> Although a single command will instantly sort that for you.... > >> > >> format \c: > >> > > > > :-D > > erm "format c:\" actually Hammer is more satisying. Rowland. -- Remove the animal for email address: rowland.mcdonnell(a)dog.physics.org Sorry - the spam got to me http://www.mag-uk.org http://www.bmf.co.uk UK biker? Join MAG and the BMF and stop the Eurocrats banning biking
From: Rowland McDonnell on 2 Jun 2010 21:35
Tim Streater <timstreater(a)waitrose.com> wrote: > Jim <jim(a)magrathea.plus.com> wrote: > > > More to the point, if I understand it correctly then Secure Erase won't care > > about how _many_ items you're erasing, but rather what their total file size > > is. It's overwriting the actual file contents repeatedly, not just whatever > > HFS+'s version of the File Allocation Table is. If the files were sizeable > > it could very well take a long time. > > Ah Jim lad, > > If it's doing that repeatedly, wot's the chance it's doing that > umpty-ump times in the cache (if the file is cached, which seems to > happen a lot) and then only once on yer actual disk? None. That's the point of having a special command for doing the job. Rowland. -- Remove the animal for email address: rowland.mcdonnell(a)dog.physics.org Sorry - the spam got to me http://www.mag-uk.org http://www.bmf.co.uk UK biker? Join MAG and the BMF and stop the Eurocrats banning biking |