# orderedItems[].object.content
@deliverator
I've not heard of virt-sysprep but IO would have thought that cloud-init would do it,a s would FAI?

https://fai-project.org/

# orderedItems[].object.contentMap.en
@deliverator
I've not heard of virt-sysprep but IO would have thought that cloud-init would do it,a s would FAI?

https://fai-project.org/

# orderedItems[].object.content
"Booting an ISO image on your hard drive" (for Debian) – Charles Curley

https://charlescurley.com/blog/posts/2 024/Nov/20/booting.isos/

#Debian

# orderedItems[].object.contentMap.en
"Booting an ISO image on your hard drive" (for Debian) – Charles Curley

https://charlescurley.com/blog/posts/2 024/Nov/20/booting.isos/

#Debian

# orderedItems[].object.content
Is your child a playground rug-puller? Your pets are at risk.

https://web3isgoinggreat.com/single/qu ant-rug-pull

# orderedItems[].object.contentMap.en
Is your child a playground rug-puller? Your pets are at risk.

https://web3isgoinggreat.com/single/qu ant-rug-pull

# orderedItems[].object.content
@issyl0
Changed it to "public views of the author of the software being covered"

# orderedItems[].object.contentMap.en
@issyl0
Changed it to "public views of the author of the software being covered"

# orderedItems[].object.content
@issyl0 I see I said author meaning the author of the software but that is confusing. Not sure how best to re-word it

# orderedItems[].object.contentMap.en
@issyl0 I see I said author meaning the author of the software but that is confusing. Not sure how best to re-word it

# orderedItems[].object.content
@issyl0
Daroc is covering a presentation by someone with extreme personal politics

# orderedItems[].object.contentMap.en
@issyl0
Daroc is covering a presentation by someone with extreme personal politics

# orderedItems[].object.content
I've not seen an LWN article before with a disclaimer saying that if they'd known, they might not have covered it.

I won't CW it as It's safe to read — the article is purely technical — but the public views of the author of the software being covered are abhorrent and the comments section touches upon this.

https://lwn.net/Articles/997238/

# orderedItems[].object.contentMap.en
I've not seen an LWN article before with a disclaimer saying that if they'd known, they might not have covered it.

I won't CW it as It's safe to read — the article is purely technical — but the public views of the author of the software being covered are abhorrent and the comments section touches upon this.

https://lwn.net/Articles/997238/

# orderedItems[].object.content
@anthk
This has nothing to do with Rust. It's an LLVM bug.

# orderedItems[].object.contentMap.en
@anthk
This has nothing to do with Rust. It's an LLVM bug.

# orderedItems[].object.content
"the *only proper* solution is to enable/require SSE2."

RIP anything compiled by LLVM on Debian x86-32 then: the baseline for the OS currently is i686-without-SSE2 and with the removal of kernel and installer in next release I don't see Debian putting resources into changing that baseline for the sake of a few packages.

https://lists.debian.org/msgid-search/d27ab15b-65ed-4c31-99d5-2509c692ff6e@app.fastmail.com

#Debian

# orderedItems[].object.contentMap.en
"the *only proper* solution is to enable/require SSE2."

RIP anything compiled by LLVM on Debian x86-32 then: the baseline for the OS currently is i686-without-SSE2 and with the removal of kernel and installer in next release I don't see Debian putting resources into changing that baseline for the sake of a few packages.

https://lists.debian.org/msgid-search/d27ab15b-65ed-4c31-99d5-2509c692ff6e@app.fastmail.com

#Debian

# orderedItems[].object.content
Leading to this proposal last week to require SSE2 instructions for 32-bit x86 Rust.

If that passes, Debian would not be able to package Rust on 32-bit x86, though the next stable release of Debian won't have a 32-bit kernel so arguably it would be no loss to say "all Rust is 64-bit on x86 from now."

https://github.com/rust-lang/compiler-team/issues/808

#rustlang #debian

# orderedItems[].object.contentMap.en
Leading to this proposal last week to require SSE2 instructions for 32-bit x86 Rust.

If that passes, Debian would not be able to package Rust on 32-bit x86, though the next stable release of Debian won't have a 32-bit kernel so arguably it would be no loss to say "all Rust is 64-bit on x86 from now."

https://github.com/rust-lang/compiler-team/issues/808

#rustlang #debian

# orderedItems[].object.content
This is not theoretical: e.g. Debian's 32-bit x86 baseline is i686-without-SSE2 but this will include the problematic instructions so to fix this would require the baseline for the whole operating system to change or else to special-case rust to target i586.

Arguably this because Debian is not enabling SSE2 on i686 but that is just to allow more hardware to work.

https://lists.debian.org/msgid-search/d8b5003f-8543-47b3-84a5-ade34c831655@app.fastmail.com

#Debian

# orderedItems[].object.contentMap.en
This is not theoretical: e.g. Debian's 32-bit x86 baseline is i686-without-SSE2 but this will include the problematic instructions so to fix this would require the baseline for the whole operating system to change or else to special-case rust to target i586.

Arguably this because Debian is not enabling SSE2 on i686 but that is just to allow more hardware to work.

https://lists.debian.org/msgid-search/d8b5003f-8543-47b3-84a5-ade34c831655@app.fastmail.com

#Debian

# orderedItems[].object.content
TIL that LLVM (and thus Rust) is not safe on 32-bit x86 due to some weirdness with floating point that does not even require floating point arithmetic to trigger, just the use of any floating point at all.

Clearly dividing God's integers into fractional parts was a heresy.

https://github.com/rust-lang/rust/issu es/114479#issuecomment-2072052116

#rustlang

# orderedItems[].object.contentMap.en
TIL that LLVM (and thus Rust) is not safe on 32-bit x86 due to some weirdness with floating point that does not even require floating point arithmetic to trigger, just the use of any floating point at all.

Clearly dividing God's integers into fractional parts was a heresy.

https://github.com/rust-lang/rust/issu es/114479#issuecomment-2072052116

#rustlang

# orderedItems[].object.content
"Decline all pull requests from Kent Overstreet during the Linux 6.13 kernel development cycle."

https://lore.kernel.org/linux-bcachefs/6740fc3aabec0_5eb129497@dwillia2-xfh.jf.intel.com.notmuch/

#bcachefs

# orderedItems[].object.contentMap.en
"Decline all pull requests from Kent Overstreet during the Linux 6.13 kernel development cycle."

https://lore.kernel.org/linux-bcachefs/6740fc3aabec0_5eb129497@dwillia2-xfh.jf.intel.com.notmuch/

#bcachefs

# orderedItems[].object.content
sshd logs the bytes while pam/systemd-logind logs the utf8:

2024-11-23T00:35:37.743827+00:00 arran sshd[1903006]: Accepted password for h\303\251llo from 200:d0e9:8d97:72fe:69af:eb63:7e9e:1f07 port 37396 ssh2
2024-11-23T00:35:37.744825+00:00 arran sshd[1903006]: pam_unix(sshd:session): session opened for user héllo(uid=1001) by (uid=0)

# orderedItems[].object.contentMap.en
sshd logs the bytes while pam/systemd-logind logs the utf8:

2024-11-23T00:35:37.743827+00:00 arran sshd[1903006]: Accepted password for h\303\251llo from 200:d0e9:8d97:72fe:69af:eb63:7e9e:1f07 port 37396 ssh2
2024-11-23T00:35:37.744825+00:00 arran sshd[1903006]: pam_unix(sshd:session): session opened for user héllo(uid=1001) by (uid=0)

# orderedItems[].object.content
Debian 12:

$ sudo adduser --allow-all-names héllo
Allowing use of questionable username.
Adding user `héllo' ...
[…]
$ printf "h\xc3\xa9llo\n"
héllo
$ printf "h\x65\xcc\x81llo\n"
héllo
$ ssh -q $(printf "h\xc3\xa9llo")@arran.bitfolk.in hostname
héllo@arran.bitfolk.in's password:
arran
$ ssh -q $(printf "h\x65\xcc\x81llo")@arran.bitfolk.in hostname
(failed)

# orderedItems[].object.contentMap.en
Debian 12:

$ sudo adduser --allow-all-names héllo
Allowing use of questionable username.
Adding user `héllo' ...
[…]
$ printf "h\xc3\xa9llo\n"
héllo
$ printf "h\x65\xcc\x81llo\n"
héllo
$ ssh -q $(printf "h\xc3\xa9llo")@arran.bitfolk.in hostname
héllo@arran.bitfolk.in's password:
arran
$ ssh -q $(printf "h\x65\xcc\x81llo")@arran.bitfolk.in hostname
(failed)

# orderedItems[].object.content
@kyle
Oh that's a shame. I haven't really had any issues with my Framework 13 except this USB-A ESD thing…

# orderedItems[].object.contentMap.en
@kyle
Oh that's a shame. I haven't really had any issues with my Framework 13 except this USB-A ESD thing…

# orderedItems[].object.content
Very interesting point brought up that e.g. é may be "e-acute" (U+00E9) or "e combined with acute" (U+0065 U+0301) so if you're gonna have that in a username how is software like SSH going to canonicalise it? Would that have to happen in the authentication layer on the server? What if you have to use a keyboard that can't type that?

If we look to POSIX it defines a username as a-z, A-Z, 0-9, period, underscore and hyphen.

# orderedItems[].object.contentMap.en
Very interesting point brought up that e.g. é may be "e-acute" (U+00E9) or "e combined with acute" (U+0065 U+0301) so if you're gonna have that in a username how is software like SSH going to canonicalise it? Would that have to happen in the authentication layer on the server? What if you have to use a keyboard that can't type that?

If we look to POSIX it defines a username as a-z, A-Z, 0-9, period, underscore and hyphen.

# orderedItems[].object.content
For the second time in 6 months I've accidentally touched a cloth-wrapped USB-C cable (with nothing connected on either end) to the metal innards of my running Framework 13's USB-A port causing it to instantly screen glitch and hard lock up.

As last time, I have had to forcibly power it off and remove the power cable then let it sit for ~2 minbiutes before it would power on again.

I assume static discharge, but rather worrying.

#Framework

# orderedItems[].object.contentMap.en
For the second time in 6 months I've accidentally touched a cloth-wrapped USB-C cable (with nothing connected on either end) to the metal innards of my running Framework 13's USB-A port causing it to instantly screen glitch and hard lock up.

As last time, I have had to forcibly power it off and remove the power cable then let it sit for ~2 minbiutes before it would power on again.

I assume static discharge, but rather worrying.

#Framework

# orderedItems[].object.content
"Hellbound" a Korean horror series currently on Netflix, is a very interesting premise and nicely done.

https://www. rottentomatoes.com/tv/hellboun d

# orderedItems[].object.contentMap.en
"Hellbound" a Korean horror series currently on Netflix, is a very interesting premise and nicely done.

https://www. rottentomatoes.com/tv/hellboun d

# orderedItems[].object.content
The House of Love - The Beatles and The Stones (1989)

https://www. youtube.com/watch?v=tGafHdnuQA s&t=6s

# orderedItems[].object.contentMap.en
The House of Love - The Beatles and The Stones (1989)

https://www. youtube.com/watch?v=tGafHdnuQA s&t=6s