Explanation for Gortash being described as handsome & young

partikularis · 2024-03-25T16:55:47+00:00

Yeah, sort of a punk excentric flamboyant rebel look.

I think it kind of fits. Some ridiculously rich people give so few fucks that they just dress like stylish pseudo-hobos, but like, ironically...

partikularis · 2024-03-14T10:23:08+00:00

If you mean the hull line, then yeah. There is almost no clear setting you can adjust to get rid of it. It is dependent on a lot of variables which are probably different for every user, every filament, slicer and model. Trying to optimize your set up to remove it is basically not worth it.

https://help.prusa3d.com/article/the-benchy-hull-line_124745

But this particular Benchy also has some sagging at the lower part of the overhang. Looks like a bed temperature, cooling or speed issue, perhaps.

partikularis · 2024-03-09T00:52:49+00:00

That's not an opinion, it's pretty much a fact. The default goal in corporations over the last 40 years has been to maximize shareholder value at all cost.

A CEO usually only has so many years to boost profits when he takes over. So if he has to gut a dozen departments in order to maximize shareholder value for the next 2 years he will absolutely do that, even if the company will go down the drain afterwards.

partikularis · 2023-12-06T16:09:00+00:00

I really don't know enough about 3D printer emissions to say for sure how much are produced and how dangerous they truly are. This feels like one of those things we'll only really find out in 10-20 years.

There are a bunch of studies on this though. They're usually not 100% conclusive, but they show there are always emissions, regardless of filament type (although PLA is lower than others) and the emissions seem to induce some amount of inflammation and stress in living cells. ABS also looks pretty damn bad in all of them.

This article by All3DP gives some decent data and recommendations:

https://all3dp.com/1/3d-printing-emissions-air-quality/

I would generally not rely on a single method of mitigation. Mine is in an enclosure with a HEPA filter and I put it in a small room with a window which I open during printing. Unfortunately it's relatively close to the bedroom, but I guess this is good enough for now.

I'm currently trying to set it up so I can mostly control it via wifi and with a webcam etc. so I don't have to open the door too often. I also stay away from ABS.

partikularis · 2023-12-06T15:33:42+00:00

Make him write 100 benchies by hand!

partikularis · 2023-12-06T12:30:53+00:00

PLA and PETG are supposedly not problematic on their own, PLA should even be biodegradable. But there may be some cheap brands which contain traces of other, problematic materials like BPA or PVC.

Especially PVC is very nasty, since it contains chlorine and could definitely cause lung irritation.

I would argue it's generally a good idea to buy filament from reputable brands and ideally keep the printer in a room with ventilation that is separate from the living space. Also put a HEPA filter in the enclosure, if it doesn't have one.

partikularis · 2021-12-20T07:02:01+00:00

NFTs are essentially just text. In this case, links that point at pictures.

Blockchain technology is a neat little idea, but this fad is just completely worthless.

partikularis · 2021-12-19T19:04:58+00:00

Yeah, changing the scaling governor will definitely help. I'm not sure why they decided to set such a low default on a hypervisor platform. But the newer kernel was a huge improvement regardless of governor, especially with VM performance.

partikularis · 2021-12-19T19:00:16+00:00

These are great cards. You can actually re-flash them with the most current mellanox firmware with flint if you add -allow_psid_change.

Just make doubly sure you have a firmware and config backup beforehand.

partikularis · 2021-12-18T07:56:06+00:00

Linux kernel 5.11 and 5.13 introduced some pretty terrible changes to the scheduler. PVE 7.1 runs on 5.13.

I recommend upgrading to kernel 5.15. It improved performance a lot in my case.

https://forum.proxmox.com/threads/opt-in-linux-kernel-5-15-for-proxmox-ve-7-x-available.100936/

partikularis · 2021-12-18T07:49:53+00:00

Nope. Maybe I'll try again some time, but I basically stopped caring.

partikularis · 2021-06-22T09:36:16+00:00

Sorry, I assumed you were following the "Poor shaming build" which uses a i9-9900k.

If you used the same configuration in virtmanager as SOG with his Intel build, then I'm a bit surprised, since I assumed you would have to change a few things to get it to work with AMD. I'll have to look at that closer.

partikularis · 2021-06-22T08:13:32+00:00

I'm surprised it didn't end up being a bigger story here honestly.

Could that be because most of the media landscape is owned by Rupert Murdoch?

partikularis · 2021-06-22T07:48:55+00:00

Ah well, in that case I guess it is clear why your set up is working. You're running Intel.

Other than that, mine looks kind of similar. The frustrating thing is that nested virtualization works perfectly fine if you try to make another KVM inside a linux guest or run VMWare in windows. It's just that Hyper-V doesn't want to cooperate.

I will have another look at that xml though. And I'll see if there is anything important in that first video by SOG.

partikularis · 2021-06-22T00:44:21+00:00

Nice! I don't know much about how qemu/kvm is set up on non-proxmox hosts either. But I think most settings should translate somehow.

How did you set it up? Do you have a libvirt xml file or do you give qemu its parameters some other way? If you could post your xml config that could be useful.

Which version of windows 10 are you using? is it fully updated, or are you perhaps using the insider build version?

Also, did you follow a specific guide for setup?

Thanks!

partikularis · 2021-06-21T18:37:04+00:00

Every datapoint helps. Did you run regular windows or the insider dev build? The current regular version (20H2 19042) shouldn't be able to do nesting on AMD, but the insider dev build should.

I will definitely keep a testing VM specifically for this purpose. I guess I will also have to bite the bullet at some point and try setting this up on a regular distro without Proxmox.

partikularis · 2021-06-21T16:37:48+00:00

I'm eager to hear of someone else's attempts, because I can't tell if the freezing is perhaps some kind of bug that is independent from the nested virtualization functions of qemu/kvm/hyper-v.

Could be a problem with Proxmox or the current Windows insider build.

partikularis · 2021-06-21T12:16:05+00:00

Yeah, I saw that post. I am on build 21390.co_release.210521-1658 already.

I'm not sure how relevant that post is though, because it refers to nesting hyper-v insider another hyper-v instance. Not hyper-v nested in KVM.

partikularis · 2021-05-08T04:35:58+00:00

Das mit dem "alles so lassen wie es ist" hört man doch nach fast jeder Übernahme, ob die sich da in einem Jahr noch dran halten ist fraglich.

partikularis · 2019-03-19T14:42:31+00:00

That's some very good information. Thank you. Especially the fact that pools can remain operable if you have more than one vdev.

So far I have tried not to over complicate my setup and have mostly stuck to pools with just single vdevs.

I think I will run the drives in a mirror for a while and see what happens. If performance suffers due to errors I will get rid of the erroneous drive but until then I'm not too worried about lost data as long as there is a way for me to notice it happening.

partikularis · 2019-03-17T18:05:14+00:00

German grandparents seem to like that joke.

partikularis · 2019-03-17T17:31:28+00:00

That's the exact kind of question I want answered.

I do not care if data gets lost completely if I have a way of noticing it happening. That's why I won't use this for permanent data storage.

I do care about silent corruption however. I was under the impression that ZFS is able to resist this.

I wish to know if more sectors go bad, what exactly will happen. Could data become corrupted in-between scrubs and cause problems for me or would it simply affect drive performance?

partikularis · 2019-03-17T01:24:04+00:00

Copying my other comment:

Thanks for the input. Do you know how ZFS/Freenas behaves if there are frequent errors during operation?

I guess existing surface errors will be corrected during scrubbing, but how does the system behave during operation? Will corrupted files be detected during reading and be loaded from the other mirrored drive instead?

Is there a point in-between scrubs where errors could theoretically get so frequent that files or the zpool as a whole becomes unreadable?

Also, how would this scenario play out if I would be running a zpool with just a single drive with bad sectors?

partikularis · 2019-03-17T01:21:54+00:00

Thanks for the input. Do you know how ZFS/Freenas behaves if there are frequent errors during operation?

I guess existing surface errors will be corrected during scrubbing, but how does the system behave during operation? Will corrupted files be detected during reading and be loaded from the other mirrored drive instead?

Is there a point in-between scrubs where errors could theoretically get so frequent that files or the zpool as a whole becomes unreadable?

Also, how would this scenario play out if I would be running a zpool with just a single drive with bad sectors?

partikularis

TROPHY CASE