XPost: alt.fan.rush-limbaugh, comp.os.linux.advocacy   
   From: brock.mcnuggets@gmail.com   
      
   On Dec 5, 2025 at 6:11:54 PM MST, "Gremlin" wrote   
   :   
      
   > Brock McNuggets    
   > news:693225ae$1$21959$882e4bbb@reader.netnews.com Fri, 05 Dec 2025 00:22:06   
   > GMT in comp.os.linux.advocacy, wrote:   
   >   
   >> On Dec 4, 2025 at 5:18:59 PM MST, "Gremlin" wrote   
   >> :   
   >   
   >>> Writing lies about people tends to cause problems for you, Snit.   
   >>   
   >> You make accusations and lie. And then get called out. And as you say, that   
   >> leads to problems.   
   >   
   > That's a rather weak spin, Snit.   
      
   Your view is of precisely no value.   
      
   But your comments do sometimes get funny:   
      
   ----------------------------------------------------------------------   
      
   * Gremlin could not believe FirstClass could handle so many   
     simultaneous connections.   
      
      
       -----   
       Yes, you had a modem bank, tied into a network, not a   
       single workstation. A single workstation back then   
       wouldn't have had the cpu power to deal with one hundred   
       concurrent connections on it's own. That's a shitload more   
       cpu power required than you seem to realize, here, Snit.   
       ...   
       Uhh, I don't care what code optimizing tricks they used,   
       there's no fucking way they were able to support one   
       hundred people, at one time, on one machine. No fucking   
       way, Snit. You had alot more hardware involved.   
       -----   
      
   Notice I said about 80... not 100... but I know it could do it because   
   it DID do it. It helped that most users were merely reading text. There   
   was little "heavy" usage.   
      
   ----------------------------------------------------------------------   
      
   * Gremlin did not realize the risks of writing to APFS on Linux.   
      
   Snit :   
       -----   
       I did not know if Linux handles APFS. It does but warns   
       you to use it read only or risk damage. I suspect other   
       Linux based rescue disks would be much the same.   
       -----   
   Context here is damage to the APFS file system by the Kaspersky tools.   
      
   David <9ss3G.298226$ls7.44481@fx40.iad>:   
       -----   
       I most certainly don't wish to damage my iMac!   
       -----   
   Context here is STILL damage to the APFS file system by the Kaspersky   
   tools. And David shows understanding that using it in write-only mode   
   can cause damage. He may not understand the details of why and how,   
   but that is not relevant and not something to attack him for. But look   
   how Diesel responds:   
      
      
       -----   
       Yet another example of you not understanding something,   
       David.   
       -----   
   David clearly understood there was a risk of damage he did not want to   
   take! It is not a competition to see who understand the exact nature   
   of the damage the tool warns about! But Diesel goes on:   
       -----   
       Worst possible case scenario, if you allow write   
       access and it borks; the file it was working with may be,   
       damaged. Or, another area of the hard disk might contain   
       data that was intended for that file. If nothing was   
       present in that area, no harm no foul. If there was used   
       data in that area, well, something just got stomped on.   
       -----   
      
   But a LOT more than just harming a file is possible. There can be much   
   worse data loss that what Diesel tries to present. Hell, even with   
   with what he says if you override key areas to a filesystem you can be   
   in trouble. Diesel should understand this!   
      
   Here is the exact warning provided by the tool:   
      
   https://imgur.com/gNWmphL.png   
       -----   
       Apple filesystems are working in journaling mode. Linux   
       filesystem driver has limited support for this mode.   
      
       Press SKIP to mount volumes in "read-only" mode. Malware   
       isn't being disinfected in this mode!   
      
       Press CONTINUE to try to mount volumes in "read-write"   
       mode. This procedure may cause damage to the filesystem!   
       -----   
      
   Note, not just to a file... but to the filesystem itself. Diesel can   
   claim an "out" in that this does not likely cause any PHYSICAL damage   
   to the drive (would be bizarre if it did) but it can cause you to lose   
   access to any and ALL data on that drive (or at least that volume).   
   This is BAD and would generally lead to you restoring from back up.   
   And it undoubtedly is damage David, or others, would not want to risk   
   on a main system!   
      
   ----------------------------------------------------------------------   
      
      
   --   
   It's impossible for someone who is at war with themselves to be at peace with   
   you.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)