@kp here you go (lint error seems to be a false positive)
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Dec 20 2023
post merge clesanup
Add unit test
Dec 14 2023
Nov 18 2023
Nov 13 2023
Nov 4 2023
Oct 30 2023
Oct 12 2023
Oct 5 2023
I haven't tested the changes myself, but this looks sound to me.
Sep 30 2023
Sep 29 2023
Jun 29 2023
Jun 11 2023
Jun 10 2023
May 28 2023
Jan 31 2023
@markj @jrm I just committed be146a923dbda66f50c6b04b406da790837f6287 (cgit link) which addresses the issue in a more generic fashion (since we had these kinds of errors pop up over and over again). Even though I tested this locally and it seems to work as expected, it would be great if you could verify this at your end as well.
Jan 27 2023
@markj Thanks, I'll look into it
Jan 10 2023
Jan 6 2023
@jrm Thanks for providing a patch.
Dec 29 2022
As I'm not sure who would be best suited for reviewing this change, I just added two overqualified people to the review.
Dec 16 2022
Dec 15 2022
@jhb @dchagin I'm currently porting https://crates.io/crates/cpu-affinity to FreeBSD (right now its FreeBSD support consists of noops) and I stumbled over something that might be by design:
Dec 9 2022
Oct 19 2022
/* Force RTC enabled/disabled. */ static int atrtc_enabled = -1; TUNABLE_INT("hw.atrtc.enabled", &atrtc_enabled);
Oct 17 2022
Oct 5 2022
Oct 2 2022
In D36825#836513, @des wrote:This is @grembo's code.
Sep 8 2022
Sep 7 2022
In D36457#828154, @imp wrote:In D36457#828129, @grembo wrote:So definitely nothing that's easy to reproduce it seems.
OK. That's both good and bad. Good that not everybody will hit it, bad that some will and we don't know who / how :(. If you manage to find a way to reproduce it, please let me know.
Sep 6 2022
In D36457#827888, @imp wrote:NOTE: When setting up the partition, I used the instructions from https://wiki.freebsd.org/UEFI which recommend newfs_msdos -F 32 -c 1. When simply using newfs_msdos /dev/..., the change in loader.env actually did the trick (and I could also list files on the resulting FAT16 partition).Yea, usually one should only do -F 32 for partitions that are at least 1.25 * minimum size. Any smaller and there's too many buggy UEFI implementations that have heartburn...
These days with 4k sectors, the minimum is 4k x 65527 = 268MB, which means anything smaller than about 300-350MB will be more portable to more UEFI implementations as FAT16. Some guides go so far as to suggest doing FAT16 for < 500MB. However, it's hard to be categorical... We've run into at least one UEFI BIOS that only did FAT32 and the spec seems to suggest that only FAT32 is required. So your milage may vary, though there's a possibility there might be one or more bugs in stand/libsa/dosfs.c (which is what ls would use inside of loader.efi, for example). If you have a reproducible formula, I'll chase that down.
Sep 5 2022
Aug 28 2022
Jul 29 2022
Jul 13 2022
Jul 7 2022
Jul 4 2022
Jun 23 2022
Straightforward and balanced.
Jun 7 2022
Jun 3 2022
May 18 2022
@wulf Thanks for reviewing
May 17 2022
- Make strlen calculation behave like on Linux (count trailing NUL)
May 9 2022
Apr 9 2022
Mar 15 2022
Minor style change