User Activity

  • Posted a comment on discussion General Discussion on rEFInd

    Yes, it is currently a beta and that was a debug build. Actually, an NPT build, which is one that gives detailed output in the RefindPlus setup. Usable though (at least in graphics screen mode) but yeah, the REL build will be best for day to day use. WIll move things through the dev cycle as needed and presently, an RC version that can be built will be pushed to the GitHub repo ahead of the next release. Backporting might be a challenge due to quite a bit of refactoring that has taken place and is...

  • Modified a comment on discussion General Discussion on rEFInd

    Your /etc/os-release is a symlink. The attached should plug that blind spot.

  • Modified a comment on discussion General Discussion on rEFInd

    That's cool. It does not have extra size checks for items with "Inline" extents, while I had added checks everywhere I could. Turns out the vmlinuz file goes through a "Regular" extents code path while these are "inline" and that the checks I added were too strict for very small files. Anyway, relaxed these in the {REMOVED} to just ensure we have data as want to keep some sanity checks but if still problematic, can just return stuff without checks here as the baseline does.

  • Posted a comment on discussion General Discussion on rEFInd

    Your os-release is a symlink. The attached should process that.

  • Modified a comment on discussion General Discussion on rEFInd

    Nice one. Thanks. The process used for BtrFS is reliable but slowish as it does one block at a time. Handling contiguous void blocks at once is better as long as properly detected. Please run the {REMOVED} to confirm nothing's been broken with this optimisation. EDIT: Just realised that you may have used a v6.8 kernel to test the Ext4 driver. However, the hole apparently appeared in v6.17 and does not affect v6.8.

  • Posted a comment on discussion General Discussion on rEFInd

    That's cool. It does not have extra size checks for items with "Inline" extents, while I had added checks everywhere I could. Turns out the vmlinuz file goes through a "Regular" extents code path while these are "inline" and that the checks I added were too strict for very small files. Anyway, relaxed these in the attached to just ensure we have data as want to keep some sanity checks but if still problematic, can just return stuff without checks here as the baseline does.

  • Modified a comment on discussion General Discussion on rEFInd

    The 5A run "fails different" to an extent. Please give the {REMOVED} a go.

  • Modified a comment on discussion General Discussion on rEFInd

    Can you cat those files with the baseline btrfs driver where 6A fails?

View All

Personal Data

Username:
dakanji
Joined:
2006-10-29 19:50:24

Projects

This is a list of open source software projects that dakanji is associated with: