I believe the "segfault at" messages are emitted by the kernel when a
*userspace* process segfaults (possibly only when it's owned by root or
otherwise seems important). If a kernel thread had crashed, I think you'd see
an OOPS instead.
kioworker, despite its name, isn't a kernel process. My
On May 14, 2025, at 13:53, Alan Grimes wrote:
>
> MySQL has ver 8.7 upstream (8.0 in gentoo)
No 8.7 shown at https://dev.mysql.com/downloads/mysql/, but there is 8.4.5.
There's an open pull request from today:
https://github.com/gentoo/gentoo/pull/34267
I'm sure they'd be happy to have teste
I had this error when building (if I remember correctly) libxcrypt for the
initrd with genkernel. But genkernel is now obsolete, so I set it aside until I
get around to switching my kernel bulids to a more modern setup.
It looks like this warning was added in the recently-released GCC 15. It's
> On May 8, 2025, at 20:12, Mitchell Dorrell wrote:
>
> This is not a bug report and I'm not really seeking assistance, I'm just
> inviting discussion because... this shouldn't be able to happen, right?
Right.
Unless you can reproduce it, I don't think we can reject the "null hypothesis"
th
> On May 2, 2025, at 13:07, Alan Mackenzie wrote:
>
> Hello, Eli.
>
> On Fri, May 02, 2025 at 13:47:02 -0400, Eli Schwartz wrote:
>
>> Compiling rust officially requires building the pre 1.0 version of rust,
>> itself written in ocaml, and then building *every* version of rust since
>> then,
The RPi5 is quite a bit faster than RPi4, and none of the packages you're
describing are particularly compile-intensive. Having an SSD will help quite a
bit. Also, if you have a fan and a good power supply, you'll want to change
the CPU governor from the default "powersave", which limits the C
> On Mar 23, 2025, at 15:41, Dale wrote:
>
> It looks like /var changes more than root does. I kinda wish I just
> could run it on the whole m.2 stick and it do its thing regardless of
> mount point. From the looks of the man page tho, that isn't a option.
fstrim is a filesystem-level oper
> On Mar 20, 2025, at 10:45, Eli Schwartz wrote:
>
> On 3/20/25 11:54 AM, Nate Eldredge wrote:
>> On Mar 20, 2025, at 00:07 Eli Schwartz wrote:
>>> You can also pass -C linker=clang if you like. Portage will
>>> already do this for rust software packaged in
22, 2025, at 18:50, Nate Eldredge wrote:
>
> On my Ubuntu box, which also doesn't have AuthenticationMethods set in
> sshd_config, simply setting "PasswordAuthentication no" does in fact prevent
> password login.
>
> Moreover, the stock sshd_config has a comment ab
On my Ubuntu box, which also doesn't have AuthenticationMethods set in
sshd_config, simply setting "PasswordAuthentication no" does in fact prevent
password login.
Moreover, the stock sshd_config has a comment above the PasswordAuthentication
option saying "To disable tunneled clear text passwo
.eclass#L63
Thanks again, everyone.
> On Mar 20, 2025, at 11:04, Nate Eldredge wrote:
>
>
>
>> On Mar 20, 2025, at 10:45, Eli Schwartz wrote:
>>
>> On 3/20/25 11:54 AM, Nate Eldredge wrote:
>>> On Mar 20, 2025, at 00:07 Eli Schwartz wrote:
>>>>
On Mar 20, 2025, at 00:07 Eli Schwartz wrote:
> Rust doesn't depend on clang at all. The current ebuild does embed $CC
> at the time you compile rust, as the default value for
>
> ```
> rustc -C linker=$CC
> ```
>
> But for the llvm profile that should be "clang" and not "clang-19". So
> you pr
I have dev-lang/rust-1.85.0-r1 installed. It fails to build trivial programs:
nate@trapezoid /tmp $ rustc t.rs
error: linker `clang-19` not found
|
= note: No such file or directory (os error 2)
error: aborting due to 1 previous error
It appears that although rust is installed with LLVM_S
13 matches
Mail list logo
