Xuehao (David) Hu
Xuehao (David) Hu
Following the repro code, I seem to see a panic ``` xuehaohu@worldpeace:~/go/src/github.com/u-root/u-root$ go run repro.go panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1...
Under a sector of 512bytes, I can make sense of the 420 bytes difference, as explained
Nill([email protected]) and I were on an email thread for this issue. I have an idea which I think worth trying to see where the bottleneck is (u-root kexec file load...
it boots fine for me in QEMU -- so I'd believe the code is still in its sanity (no real big change since 2020, except this [one](https://github.com/u-root/u-root/commit/236bcb5a057c69b708f1844e93d97e248a103c05#diff-94608cc14a6a9303495686db32023d82165a28b4e809f14098c44283b079607f)) just did a...
+1 -- The problem statement is very true
To clarify, this does not work even we build a `/usr/bin/xzcat` into initramfs ? looks to me following formats need be handled: `.gz`, `.xz`, `.lzma` (maybe not ? given it...
currently, if it cant find any installable modules, it simply log the error, and move on. Curious why it would "panic" for you, assuming you meant golang panic
Hi Avi, run `git commit --amend --signoff` to fix the DCO check failure.
By all means, when you open a file, and write a duplicate of it, it should be same identical as original file.