fsck on FAT32 filesystem?

Robert Bonomi bonomi at mail.r-bonomi.com
Sat Jul 21 10:10:46 UTC 2012

> From owner-freebsd-questions at freebsd.org  Thu Jul 19 03:21:28 2012
> Date: Thu, 19 Jul 2012 10:18:43 +0200 (CEST)
> From: Wojciech Puchar <wojtek at wojtek.tensor.gdynia.pl>
> To: Robert Bonomi <bonomi at mail.r-bonomi.com>
> Cc: freebsd-questions at freebsd.org
> Subject: Re: fsck on FAT32 filesystem?
> > entitled to have opinions, *BUT* the "Gospel According to Wojciech" is 
> > -not- 'the answer' for everybody, in every situation. *IF* you ever 
> > learn that,
> Seems like you have 45 years of experience in words. nothing more.

It seems like all you know how to do is engage in ignorant, uninformed,
personal attacks/insults.

Not that it matters, but -- in addition to having had a news story I wrote
published on the front page of the N.Y. Times (midwest edition) -- I've:
  a) Designed and implemented trans-national, trans-atlantic corporate
     data network for the trading arm of a major Japanese bank.
  b) implemented "array of pointer to function" in FORTRAN 77 applications.
  c) Written date parsing routines, originally in FORTRAN 66,  that would
     recognize virtually -any- 'rational' date expression -- including
     the likes of "this 23rd day of June in the Year of Our Lord 2012".
     had a switch for 'prefering' European-syle (DD MM YY) or American-style
     (MM DD YY) dates when ambiguous.  User-manual for the free-form command
     parser merely specified a 'date' was required at a particular point,
     would frequently generate user inquires 'what date _format_ is required?'
     Answer: "Use what you prefer, it will probably make sense out of it"
  d) Written the _first_ commodity-options 'theoretical value' calculation
     routine that was fast enough to be used in 'real time' in determining
     'fair value' for exchange-traded commodity options.  When the source
     data may change in a fractiono of a second, Doing 'Cox-Ross-Rubenstein'
     math *before* the underling data changes -- invalidating the calculation-
     in-progress -- is challenging.  Doing it for the -entire- market, which
     requires  sub-millisecond timing, is far more than just 'challenging'.
  e) Written the worlds fastest project scheduling software (merely 4000 
     times faster than IBM's offering at the time).  After I demoed the
     software for over a dozen senior IBM construction executives, they
     contracted with the firm I worked for, for project scheuling services
     for -all- their major physicaal plant construction projects.  U.S.
     Army Corps of Engineers also bought a copy.
  f) Wrote the _first_ PC-based software for 'off-line' creation of
     control-files for a high-end video-tape editing suite.  File format
     _entirely_ undocumented, required 'reverse-engineering' of everthing.
  g) Designed and implemented a complete _real-time_ market price data 
     distribution system (everything from the incoming feed processing 
     to the subroutinies that the 'user applications' used) for a major 
     Government Securities brokerage.  Stand-alone code on dedicated 
     processors for each incoming feed, feeding a back-end server, with
     multiplexing daemons on each workstation, to support multiple 
     simultaneous applications. Commplete with application-level transparency
     for the crash/auto-restart of any system-level component, and auto
     release of resources previousl allocated to now-zombie clients.
     Everthing _guaranteed_, by architecture design to be non-blocking,
     _impossible_ for one client app to adversely affect quote delivery
     to other apps, even on the same machine.
  h) Designed and built a complete 'subscription publiication' accounting
     system -- complete 'subscriber management'. billing, payment, earned-
     income handling, -and- 'fulfillment' processing.
  i) Written 'hyupervisor' (for lack of a better term) code for a mini-
     computer system, to automate a management task on that machine that
     the _manufacturer_ of the hardare and O/S said could _not_ be automated.

> Aggression is normal today from such people, that have "good position" in 
> some companies and fear anyone could read any other than "established" 
> opinions.

That is an amazingly accurate description of _YOU_, Wociech -- You might 
consider why you feel it necessary to _personally_attack_ anyone and 
everyone who "has the nerve to disagree with your _opinions_".

More information about the freebsd-questions mailing list