home.social

#ext2 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ext2, aggregated by home.social.

fetched live
  1. #LKML #QOTD from Tytso in reply to a #ext2 backporting request to various older #Linux longterm #kernel series:

    ""[…] And this is why the patches have not been backported. It requires work, and an AI generated request doesn't change the reality that *someone* has to do that work,

    I invite you to figure out a way to figure out an AI mediated tool that can attempt the backport, and then run the moral equivalent of "gce-xfstests -c ext4.all -g auto" to verify that the backport doesn't result in any regressions. (Some previous attempts to backport to older LTS kernels have resulted in the kernels crashing as a result.)

    Otherwise, I recommend that most users consider switching to a newer LTS kernel, or if they can't to pay $$$ to an enterprise Linux distribution that pays engineers to do that hard work.""

    lore.kernel.org/all/alDWUmORy7

    Side note, regarding the "switching to a newer LTS kernel" aspect: running at least the latest longterm #LinuxKernel is what most users should do anyway, as explained by this post from @gregkh:

    kroah.com/log/blog/2018/08/24/

  2. #LKML #QOTD from Tytso in reply to a #ext2 backporting request to various older #Linux longterm #kernel series:

    ""[…] And this is why the patches have not been backported. It requires work, and an AI generated request doesn't change the reality that *someone* has to do that work,

    I invite you to figure out a way to figure out an AI mediated tool that can attempt the backport, and then run the moral equivalent of "gce-xfstests -c ext4.all -g auto" to verify that the backport doesn't result in any regressions. (Some previous attempts to backport to older LTS kernels have resulted in the kernels crashing as a result.)

    Otherwise, I recommend that most users consider switching to a newer LTS kernel, or if they can't to pay $$$ to an enterprise Linux distribution that pays engineers to do that hard work.""

    lore.kernel.org/all/alDWUmORy7

    Side note, regarding the "switching to a newer LTS kernel" aspect: running at least the latest longterm #LinuxKernel is what most users should do anyway, as explained by this post from @gregkh:

    kroah.com/log/blog/2018/08/24/

  3. from Tytso in reply to a backporting request to various older longterm series:

    ""[…] And this is why the patches have not been backported. It requires work, and an AI generated request doesn't change the reality that *someone* has to do that work,

    I invite you to figure out a way to figure out an AI mediated tool that can attempt the backport, and then run the moral equivalent of "gce-xfstests -c ext4.all -g auto" to verify that the backport doesn't result in any regressions. (Some previous attempts to backport to older LTS kernels have resulted in the kernels crashing as a result.)

    Otherwise, I recommend that most users consider switching to a newer LTS kernel, or if they can't to pay $$$ to an enterprise Linux distribution that pays engineers to do that hard work.""

    lore.kernel.org/all/alDWUmORy7

    Side note, regarding the "switching to a newer LTS kernel" aspect: running at least the latest longterm is what most users should do anyway, as explained by this post from @gregkh:

    kroah.com/log/blog/2018/08/24/

  4. #LKML #QOTD from Tytso in reply to a #ext2 backporting request to various older #Linux longterm #kernel series:

    ""[…] And this is why the patches have not been backported. It requires work, and an AI generated request doesn't change the reality that *someone* has to do that work,

    I invite you to figure out a way to figure out an AI mediated tool that can attempt the backport, and then run the moral equivalent of "gce-xfstests -c ext4.all -g auto" to verify that the backport doesn't result in any regressions. (Some previous attempts to backport to older LTS kernels have resulted in the kernels crashing as a result.)

    Otherwise, I recommend that most users consider switching to a newer LTS kernel, or if they can't to pay $$$ to an enterprise Linux distribution that pays engineers to do that hard work.""

    lore.kernel.org/all/alDWUmORy7

    Side note, regarding the "switching to a newer LTS kernel" aspect: running at least the latest longterm #LinuxKernel is what most users should do anyway, as explained by this post from @gregkh:

    kroah.com/log/blog/2018/08/24/

  5. #LKML #QOTD from Tytso in reply to a #ext2 backporting request to various older #Linux longterm #kernel series:

    ""[…] And this is why the patches have not been backported. It requires work, and an AI generated request doesn't change the reality that *someone* has to do that work,

    I invite you to figure out a way to figure out an AI mediated tool that can attempt the backport, and then run the moral equivalent of "gce-xfstests -c ext4.all -g auto" to verify that the backport doesn't result in any regressions. (Some previous attempts to backport to older LTS kernels have resulted in the kernels crashing as a result.)

    Otherwise, I recommend that most users consider switching to a newer LTS kernel, or if they can't to pay $$$ to an enterprise Linux distribution that pays engineers to do that hard work.""

    lore.kernel.org/all/alDWUmORy7

    Side note, regarding the "switching to a newer LTS kernel" aspect: running at least the latest longterm #LinuxKernel is what most users should do anyway, as explained by this post from @gregkh:

    kroah.com/log/blog/2018/08/24/

  6. One day I'll see about updating an old defragmentation script to work on more filesystems... Just for the heck of it.

  7. One day I'll see about updating an old #perl #ext2 defragmentation script to work on more filesystems... Just for the heck of it. #Coding

  8. One day I'll see about updating an old #perl #ext2 defragmentation script to work on more filesystems... Just for the heck of it. #Coding

  9. One day I'll see about updating an old #perl #ext2 defragmentation script to work on more filesystems... Just for the heck of it. #Coding

  10. Ein guter alter Bekannter geht in Rente: Das Dateisystem #Ext2 wird im nächsten #Kernel #Linux 6.9 als "deprecated" markiert, weil es das Jahr-2038-Problem hat:
    git.kernel.org/pub/scm/linux/k

    Wer noch Ext2 nutzt, sollte also auf wenigstens Ext3 oder besser Ext4 umsteigen:
    ext4.wiki.kernel.org/index.php

  11. Ein guter alter Bekannter geht in Rente: Das Dateisystem #Ext2 wird im nächsten #Kernel #Linux 6.9 als "deprecated" markiert, weil es das Jahr-2038-Problem hat:
    git.kernel.org/pub/scm/linux/k

    Wer noch Ext2 nutzt, sollte also auf wenigstens Ext3 oder besser Ext4 umsteigen:
    ext4.wiki.kernel.org/index.php

  12. Ein guter alter Bekannter geht in Rente: Das Dateisystem #Ext2 wird im nächsten #Kernel #Linux 6.9 als "deprecated" markiert, weil es das Jahr-2038-Problem hat:
    git.kernel.org/pub/scm/linux/k

    Wer noch Ext2 nutzt, sollte also auf wenigstens Ext3 oder besser Ext4 umsteigen:
    ext4.wiki.kernel.org/index.php

  13. Ein guter alter Bekannter geht in Rente: Das Dateisystem #Ext2 wird im nächsten #Kernel #Linux 6.9 als "deprecated" markiert, weil es das Jahr-2038-Problem hat:
    git.kernel.org/pub/scm/linux/k

    Wer noch Ext2 nutzt, sollte also auf wenigstens Ext3 oder besser Ext4 umsteigen:
    ext4.wiki.kernel.org/index.php

  14. @sci_photos Zu SuSE-Zeiten habe ich das regelmäßig genommen...
    #btrfs habe ich tatsächlich auch schon genutzt und fand es sehr simpel und komfortabel.
    Mit Journaling-FS kommt chkfs kam noch vor, mkfs braucht man nur 1x bei der Installation.
    Wenn ich daran denke, wie lange eine #NTFS-Formatierung bei #NT4.0 gedauert hat. Oder auch bei #ext2...

  15. @sci_photos Zu SuSE-Zeiten habe ich das regelmäßig genommen...
    #btrfs habe ich tatsächlich auch schon genutzt und fand es sehr simpel und komfortabel.
    Mit Journaling-FS kommt chkfs kam noch vor, mkfs braucht man nur 1x bei der Installation.
    Wenn ich daran denke, wie lange eine #NTFS-Formatierung bei #NT4.0 gedauert hat. Oder auch bei #ext2...

  16. @sci_photos Zu SuSE-Zeiten habe ich das regelmäßig genommen...
    #btrfs habe ich tatsächlich auch schon genutzt und fand es sehr simpel und komfortabel.
    Mit Journaling-FS kommt chkfs kam noch vor, mkfs braucht man nur 1x bei der Installation.
    Wenn ich daran denke, wie lange eine #NTFS-Formatierung bei #NT4.0 gedauert hat. Oder auch bei #ext2...

  17. @sci_photos Zu SuSE-Zeiten habe ich das regelmäßig genommen...
    #btrfs habe ich tatsächlich auch schon genutzt und fand es sehr simpel und komfortabel.
    Mit Journaling-FS kommt chkfs kam noch vor, mkfs braucht man nur 1x bei der Installation.
    Wenn ich daran denke, wie lange eine #NTFS-Formatierung bei #NT4.0 gedauert hat. Oder auch bei #ext2...

  18. @ivan Насколько я понимаю, в картах памяти и USB-флешках используется более дешёвая память, чем в SSD и телефонах. Чтобы USB-#флешка служила дольше, есть смысл создать на ней два раздела: один с файловой системой #FAT (ибо не на всех компьютерах есть качественная операционная система), другой с файловой системой ext2 (именно 2, а не 3 или 4, ибо из них только #ext2 не является журналируемой). Пример того, как я это делал: citilink.ru/product/fleshka-us

  19. @ivan Насколько я понимаю, в картах памяти и USB-флешках используется более дешёвая память, чем в SSD и телефонах. Чтобы USB-#флешка служила дольше, есть смысл создать на ней два раздела: один с файловой системой #FAT (ибо не на всех компьютерах есть качественная операционная система), другой с файловой системой ext2 (именно 2, а не 3 или 4, ибо из них только #ext2 не является журналируемой). Пример того, как я это делал: citilink.ru/product/fleshka-us

  20. @ivan Насколько я понимаю, в картах памяти и USB-флешках используется более дешёвая память, чем в SSD и телефонах. Чтобы USB-#флешка служила дольше, есть смысл создать на ней два раздела: один с файловой системой #FAT (ибо не на всех компьютерах есть качественная операционная система), другой с файловой системой ext2 (именно 2, а не 3 или 4, ибо из них только #ext2 не является журналируемой). Пример того, как я это делал: citilink.ru/product/fleshka-us