#nobridge

  • 1 Post
  • 17 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle


    1. RAID is never a replacement for backups.
    2. Never work directly with a surviving disk, clone it and work with the cloned drive.
    3. Are you sure you can’t rebuild the RAID? That really is the best solution in many cases.
    4. If a RAID failure is within tolerance (1 drive in a RAID5 array) then it should still be operational. Make a backup before rebuilding if you don’t have one already.
    5. If more disks are gone than that then don’t count on recovering all data even with data recovery tools.

  • Gonna be interesting to see which models disappear from EU altogether and which models get the better repairability and software updates next summer:

    Ecodesign requirements will apply to mobile phones and tablets put on the EU market from 20 June 2025 onwards, including:

    1. resistance to accidental drops or scratches and protection from dust and water
    2. sufficiently durable batteries which can withstand at least 800 charge and discharge cycles while retaining at least 80% of their initial capacity
    3. rules on disassembly and repair, including obligations for producers to make critical spare parts available within 5-10 working days, and for 7 years after the end of sales of the product model on the EU market
    4. availability of operating system upgrades for longer periods (at least 5 years from the date of the end of placement on the market of the last unit of a product model)
    5. non-discriminatory access for professional repairers to any software or firmware needed for the replacement









  • If your phone can survive until next summer it might be a good idea, EU is forcing some consumer friendly requirements which I imagine will give you a wider availability of models with five years of updates.
    https://energy-efficient-products.ec.europa.eu/product-list/smartphones-and-tablets_en

    Ecodesign requirements will apply to mobile phones and tablets put on the EU market from 20 June 2025 onwards, including:

    1. resistance to accidental drops or scratches and protection from dust and water
    2. sufficiently durable batteries which can withstand at least 800 charge and discharge cycles while retaining at least 80% of their initial capacity
    3. rules on disassembly and repair, including obligations for producers to make critical spare parts available within 5-10 working days, and for 7 years after the end of sales of the product model on the EU market
    4. availability of operating system upgrades for longer periods (at least 5 years from the date of the end of placement on the market of the last unit of a product model)
    5. non-discriminatory access for professional repairers to any software or firmware needed for the replacement

  • That question is kind a rabbit hole and not one I feel confident in going down.

    Free as in freedom, not as in free beer.
    The real world implications of non-free software is that other’s can’t run, copy, distribute, study, change and improve the software.

    I like having computing alternatives that are free from corporate control and believe that the hardliners like FSF helps us keep those alternatives alive. I realise that those alternatives are in many ways worse and that a lot of hardware today requires the vendor blobs to work. When/If corporations push their control even further I want those alternatives to be around.

    And you really should pay for winrar. ;-)


  • Not in this case, the tests they’re running doesn’t need the vendor blobs in those testing folders.

    Generally I agree with Debians changes to include nonfree firmware in the default images and making the “completely free” images the non-default version. I do think maintaining and having completely free distro versions to be a good thing though.

    The whole situation is really unnecessary because none of the things that we’re testing really requires those vendor blobs.
    We’re just testing the basic vboot and CBFS structures in those images, the file contents are not really relevant as long as they match the signatures.
    So I think the easiest option here is to just remove the offending CBFS files from those images / overwrite the offending FMAP sections with zeroes.

    https://issuetracker.google.com/issues/374385985