ryannathans

joined 1 year ago
[–] [email protected] 3 points 1 hour ago

People been doing this since facebook login was plain old http

[–] [email protected] 2 points 1 hour ago (3 children)

Why is it 1

[–] [email protected] 7 points 1 hour ago

Bit overblown given you need to be on windows, actively MITM attacked and manually updating Python via qbittorrent

[–] [email protected] 1 points 2 hours ago (1 children)
[–] [email protected] 6 points 22 hours ago (1 children)

Butter flavoured syrup

What

[–] [email protected] 0 points 1 day ago (3 children)

How do they avoid the subsequent bugs O3 tends to produce?

[–] [email protected] 8 points 3 days ago* (last edited 3 days ago)

Nvme drive controllers already throttle at the storage level but the interface gets hot now, and client devices can't negatiate slower interface speeds afaik

[–] [email protected] 1 points 3 days ago

Nothing prevents you from making it remotely accessible with the password "password" either

[–] [email protected] 1 points 3 days ago* (last edited 3 days ago) (1 children)

Okay sure then you're asking for trouble. You could also configure the word password as your password.

[–] [email protected] 2 points 3 days ago (3 children)

Management interface is only available locally

[–] [email protected] -2 points 3 days ago (4 children)

The management interface is only available with physical access

[–] [email protected] 7 points 3 days ago (19 children)

To be fair you need physical access

 

I've been trying to create a new cpuset to run some programs with a reduced set of cpu cores, but I seem to be fighting with something my system is already doing because the instructions from the kernel manual don't work. I find cpuset is already mounted, but when I create a directory in /sys/fs/cgroup/cpuset it does not end up with cpuset.cpus in it. It seems cpusets are aleady being used by something else, so not sure how I'd go about this?

Manual with step by step tutorial: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/cpusets.html

 
view more: next ›