• Re: Unix on x86, Hmmm ... Downloaded Xenix - But It's *41* Floppies Wor

    From Nuno Silva@3:633/10 to Peter Flass on Sat Sep 6 11:17:53 2025
    XPost: comp.os.linux.misc
    From: nunojsilva@invalid.invalid

    On 2025-09-05, Peter Flass wrote:


    On 9/5/25 08:03, John Ames wrote:
    On Fri, 5 Sep 2025 05:08:43 -0400
    c186282 <c186282@nnada.net> wrote:

    To put it kindly .........

    -IX has become better at dealing with soft-shutdown than Win.

    Win10 started playing all kinds of games with true shutdown vs. some
    kind of "deep suspend" - I'm pretty sure they were trying to improve
    "boot time" without actually having to *improve boot time,* but it was
    immensely counterproductive since NT has always leaked memory like a
    sieve and a full reboot is the only way to clear it up. I think they
    walked back some of the shenanigans in later updates, but on early
    revisions of 10 it was practically impossible to get it to perform a
    clean shutdown without holding in the power button 'til the machine
    itself cut out, though invoking shutdown from the command line
    sometimes seemed to work.

    My "new" computer is set up to dusl-boot Win 10 and Linux, sharing an
    NTFS data partition. I had to disable all that nonsense in windows to
    avoid blocking Linux access to data.

    This being MICROS~1, maybe that was intentional on their part, to make dual-booting more difficult?

    After all, hasn't NT supported hibernation for ages?


    How easy/hard is it do disable this feature and restore proper shutdown?

    --
    Nuno Silva

    (Of all the crossposted posts on comp.os.linux.misc, this one isn't
    x-posted to the windows group? :-D )

    --- SoupGate-Linux v1.05
    * Origin: ---:- FTN<->Usenet Gate -:--- (3:633/10)
  • From Peter Flass@3:633/10 to Nuno Silva on Sat Sep 6 07:31:12 2025
    XPost: comp.os.linux.misc
    From: Peter@Iron-Spring.com

    On 9/6/25 03:17, Nuno Silva wrote:
    On 2025-09-05, Peter Flass wrote:


    On 9/5/25 08:03, John Ames wrote:
    On Fri, 5 Sep 2025 05:08:43 -0400
    c186282 <c186282@nnada.net> wrote:

    To put it kindly .........

    -IX has become better at dealing with soft-shutdown than Win.

    Win10 started playing all kinds of games with true shutdown vs. some
    kind of "deep suspend" - I'm pretty sure they were trying to improve
    "boot time" without actually having to *improve boot time,* but it was
    immensely counterproductive since NT has always leaked memory like a
    sieve and a full reboot is the only way to clear it up. I think they
    walked back some of the shenanigans in later updates, but on early
    revisions of 10 it was practically impossible to get it to perform a
    clean shutdown without holding in the power button 'til the machine
    itself cut out, though invoking shutdown from the command line
    sometimes seemed to work.

    My "new" computer is set up to dusl-boot Win 10 and Linux, sharing an
    NTFS data partition. I had to disable all that nonsense in windows to
    avoid blocking Linux access to data.

    This being MICROS~1, maybe that was intentional on their part, to make dual-booting more difficult?

    After all, hasn't NT supported hibernation for ages?


    How easy/hard is it do disable this feature and restore proper shutdown?


    Not really hard, but it's not obvious that you have to, or should have
    to, do it. Then there are a couple of tweaks to disable windows
    "features". On the other hand, maybe someone will update Linux NTFS
    support to handle this. I *think* the problem is that windoze caches
    some filesystem changes and leave everything in an inconsistent state,

    --- SoupGate-Linux v1.05
    * Origin: ---:- FTN<->Usenet Gate -:--- (3:633/10)
  • From Lars Poulsen@3:633/10 to Peter Flass on Tue Sep 9 21:32:20 2025
    XPost: comp.os.linux.misc
    From: lars@cleo.beagle-ears.com

    On 2025-09-06, Peter Flass <Peter@Iron-Spring.com> wrote:
    On the other hand, maybe someone will update Linux NTFS
    support to handle this. I *think* the problem is that windoze caches
    some filesystem changes and leave everything in an inconsistent state,

    So windows does not have an equivalent to "sync;sync;sync" that it could
    do before hibernating? The mind boggles ...

    --- SoupGate-Linux v1.05
    * Origin: Dragon's Lair ---:- FidoNet<>Usenet Gateway -:--- (3:633/10)
  • From Peter Flass@3:633/10 to Lars Poulsen on Tue Sep 9 15:30:59 2025
    XPost: comp.os.linux.misc
    From: Peter@Iron-Spring.com

    On 9/9/25 14:32, Lars Poulsen wrote:
    On 2025-09-06, Peter Flass <Peter@Iron-Spring.com> wrote:
    On the other hand, maybe someone will update Linux NTFS
    support to handle this. I *think* the problem is that windoze caches
    some filesystem changes and leave everything in an inconsistent state,

    So windows does not have an equivalent to "sync;sync;sync" that it could
    do before hibernating? The mind boggles ...

    Apparently. I didn't do a lot of research, but I encountered this
    problem, I read this, made the suggested changes to windows, and it worked.

    --- SoupGate-Linux v1.05
    * Origin: Dragon's Lair ---:- FidoNet<>Usenet Gateway -:--- (3:633/10)
  • From Lawrence =?iso-8859-13?q?D=FFOlivei@3:633/10 to Lars Poulsen on Tue Sep 9 22:56:44 2025
    XPost: comp.os.linux.misc
    From: ldo@nz.invalid

    On Tue, 9 Sep 2025 21:32:20 -0000 (UTC), Lars Poulsen wrote:

    So windows does not have an equivalent to "sync;sync;sync" ...

    On Linux, you need to do it once.

    Or rather, doing it multiple times doesn’t help much.

    --- SoupGate-Linux v1.05
    * Origin: Dragon's Lair ---:- FidoNet<>Usenet Gateway -:--- (3:633/10)
  • From Carlos E.R.@3:633/10 to All on Wed Sep 10 11:10:16 2025
    XPost: comp.os.linux.misc
    From: robin_listas@es.invalid

    On 2025-09-10 00:56, Lawrence D’Oliveiro wrote:
    On Tue, 9 Sep 2025 21:32:20 -0000 (UTC), Lars Poulsen wrote:

    So windows does not have an equivalent to "sync;sync;sync" ...

    On Linux, you need to do it once.

    Or rather, doing it multiple times doesn’t help much.


    «When thou shuttest down the system, thou shalt sync three times. No
    more, no less. Three shall be the number of the syncing, and the number
    of the syncing shall be three. Four times shalt thou not sync, neither
    sync twice, except that thou proceedest to sync a third time...»


    Tradition! :-D

    --
    Cheers, Carlos.
    ES🇪🇸, EU🇪🇺;

    --- SoupGate-Linux v1.05
    * Origin: Dragon's Lair ---:- FidoNet<>Usenet Gateway -:--- (3:633/10)
  • From Charlie Gibbs@3:633/10 to Carlos E.R. on Wed Sep 10 14:23:26 2025
    XPost: comp.os.linux.misc
    From: cgibbs@kltpzyxm.invalid

    On 2025-09-10, Carlos E.R. <robin_listas@es.invalid> wrote:

    On 2025-09-10 00:56, Lawrence D’Oliveiro wrote:

    On Tue, 9 Sep 2025 21:32:20 -0000 (UTC), Lars Poulsen wrote:

    So windows does not have an equivalent to "sync;sync;sync" ...

    On Linux, you need to do it once.

    Or rather, doing it multiple times doesn’t help much.

    «When thou shuttest down the system, thou shalt sync three times. No
    more, no less. Three shall be the number of the syncing, and the number
    of the syncing shall be three. Four times shalt thou not sync, neither
    sync twice, except that thou proceedest to sync a third time...»

    Tradition! :-D

    Sync three times on the console if you want me.
    Close all the pipes if the answer is no.
    -- Tony Orlando and Dawn 2.0

    --
    /~\ Charlie Gibbs | Growth for the sake of
    \ / <cgibbs@kltpzyxm.invalid> | growth is the ideology
    X I'm really at ac.dekanfrus | of the cancer cell.
    / \ if you read it the right way. | -- Edward Abbey

    --- SoupGate-Linux v1.05
    * Origin: Dragon's Lair ---:- FidoNet<>Usenet Gateway -:--- (3:633/10)
  • From geodandw@3:633/10 to Charlie Gibbs on Wed Sep 10 14:11:40 2025
    XPost: comp.os.linux.misc
    From: geodandw@gmail.com

    On 9/10/25 10:23, Charlie Gibbs wrote:
    On 2025-09-10, Carlos E.R. <robin_listas@es.invalid> wrote:

    On 2025-09-10 00:56, Lawrence D’Oliveiro wrote:

    On Tue, 9 Sep 2025 21:32:20 -0000 (UTC), Lars Poulsen wrote:

    So windows does not have an equivalent to "sync;sync;sync" ...

    On Linux, you need to do it once.

    Or rather, doing it multiple times doesn’t help much.

    «When thou shuttest down the system, thou shalt sync three times. No
    more, no less. Three shall be the number of the syncing, and the number
    of the syncing shall be three. Four times shalt thou not sync, neither
    sync twice, except that thou proceedest to sync a third time...»

    Tradition! :-D

    Sync three times on the console if you want me.
    Close all the pipes if the answer is no.
    -- Tony Orlando and Dawn 2.0

    Why do you need to sync three times?

    --- SoupGate-Linux v1.05
    * Origin: Dragon's Lair ---:- FidoNet<>Usenet Gateway -:--- (3:633/10)
  • From Carlos E.R.@3:633/10 to geodandw on Wed Sep 10 21:07:26 2025
    XPost: comp.os.linux.misc
    From: robin_listas@es.invalid

    On 2025-09-10 20:11, geodandw wrote:
    On 9/10/25 10:23, Charlie Gibbs wrote:
    On 2025-09-10, Carlos E.R. <robin_listas@es.invalid> wrote:

    On 2025-09-10 00:56, Lawrence D’Oliveiro wrote:

    On Tue, 9 Sep 2025 21:32:20 -0000 (UTC), Lars Poulsen wrote:

    So windows does not have an equivalent to "sync;sync;sync" ...

    On Linux, you need to do it once.

    Or rather, doing it multiple times doesn’t help much.

    «When thou shuttest down the system, thou shalt sync three times. No
    more, no less. Three shall be the number of the syncing, and the number
    of the syncing shall be three. Four times shalt thou not sync, neither
    sync twice, except that thou proceedest to sync a third time...»

    Tradition! :-D

         Sync three times on the console if you want me.
         Close all the pipes if the answer is no.
           -- Tony Orlando and Dawn 2.0

    Why do you need to sync three times?

    Initially, it wasn't clear that a single sync would do it. Now, it is
    accepted that a single sync is enough, plus we have journaled filesystems.

    --
    Cheers, Carlos.
    ES🇪🇸, EU🇪🇺;

    --- SoupGate-Linux v1.05
    * Origin: Dragon's Lair ---:- FidoNet<>Usenet Gateway -:--- (3:633/10)
  • From Lawrence =?iso-8859-13?q?D=FFOlivei@3:633/10 to Carlos E.R. on Wed Sep 10 19:29:51 2025
    XPost: comp.os.linux.misc
    From: ldo@nz.invalid

    On Wed, 10 Sep 2025 21:07:26 +0200, Carlos E.R. wrote:

    On 2025-09-10 20:11, geodandw wrote:

    Why do you need to sync three times?

    Initially, it wasn't clear that a single sync would do it. Now, it is accepted that a single sync is enough, plus we have journaled
    filesystems.

    In old “Unix”, the sync call was not guaranteed to complete immediately. For some reason, that bug was never fixed.

    Linux fixes the bug. But as others have pointed out, this is still not foolproof, because it will not catch filesystem activity happening *after*
    the sync. Repeating the sync 3 times, or any number of times, makes no difference to this.

    --- SoupGate-Linux v1.05
    * Origin: Dragon's Lair ---:- FidoNet<>Usenet Gateway -:--- (3:633/10)