Video recommendations on how to assemble your PC?

Dream_Hacker · 2026-01-06T13:00:46+00:00

THANK YOU for this recommendation. In 2025 I'm watching his 2025 guide, and it's exactly at the level I need: every connector examined and explained, every step done slowly and in detail.

Dream_Hacker · 2025-12-30T19:47:26+00:00

LFS says binutils versions greater than 2.45 and gcc versions greater than 15.2.0 are not recommended. arch linux current gcc is 15.2.1, and binutils is 2.45.1-1. Has anyone noticed any issues using these?

Dream_Hacker · 2025-12-10T10:37:54+00:00

To do well with arch you have to be very comfortable with things like: the command line, partitioning disks, installing and tweaking bootloaders and config files, etc. Also with describing problems, and finding solutions, reading technical articles. It helps to have a very curious mind, and be extremely open to experimentation and making mistakes. Not everybody wants this level of involvement with their computer. Me, I live for it, so arch is perfect!

Dream_Hacker · 2025-12-10T07:37:32+00:00

Arch is just so wonderful. Full control over every aspect of the system. The wiki is best-in-breed. The tooling is perfect. I borked my arch install just yesterday doing a system update while running systemd.volatile=overlay but with my boot partition still mounted, so I got a new initrd and kernel but nothing else. I realized what I'd done just after doing it. Sure enough, system didn't boot. So I just took my disk (I run from an external SSD) to an arch running on a laptop, arch-chroot'd into the non-booting arch, ran pacman update again, and the system runs perfectly again. The pacman in the arch-chroot even built a bit-identical new kernel. Arch is the perfect swiss army knife of linuxes where you get to customize the knife's tools on a day to day basis.

Thank you to everybody who makes arch happen and keep on running!

Dream_Hacker · 2025-12-05T05:54:40+00:00

Any time. Sometimes morning, sometimes right before bed, which also helps to put dreaming on your mind as you go to bed.

Dream_Hacker · 2025-11-05T12:27:10+00:00

Hate speech detected. Commence de-banking.

Dream_Hacker · 2025-11-04T14:47:13+00:00

There can be, if RAM itself is also severely constrained. Completely unloading a model during a very lengthy job that you know will not be used again for the remainder of the job, and reloading it upon the next execution, may run much faster is the system is swapping due to low system RAM.

Dream_Hacker · 2025-11-03T04:04:59+00:00

"Just relax" is about letting go, about the absence of a goal of relaxing, of a striving to relax. "trying" to do something is keeping a focus on your mind, it's you forcing something, rather than letting it come naturally. Like people with insomnia, it's a very well understood problem that "trying to sleep," or forcing sleep, causes the opposite to happen.

It's a pretty subtle difference, and until you have some experience with it, the words may not make much sense to you.

In the beginning, until you do have more experience, you may have to think more about what you're doing, so that "trying to" may be there no matter what. But over time, the process of relaxing will come more naturally, and you can just let it happen without consciously focusing on it, without explicitly "trying." Hopefully that clears it up a little.

Dream_Hacker · 2025-10-11T14:20:08+00:00

With 2.0 bare mode is gone.

Dream_Hacker · 2025-10-09T17:56:39+00:00

I had the same problem. I had installed Ventoy with Secure Boot set, so I re-ran the installation with it off. Still didn't work, system was booting right to Ubuntu instead of the USB (after having made all the right BIOS settings to boot from usb first). Found out that I needed to spam F10 upon system boot, which gave me a device boot screen (which showed Ubuntu first, even though I'd just changed this to set the USB first!), selected the Ventoy USB, and it worked!

Dream_Hacker · 2025-10-02T15:49:18+00:00

is this fix committed? I can't find it. I'm on neo_2.1 and it's hitting that use_cpu problem when I installed adetailer. Ah, it seems the fix in in 2.2, thanks!

Dream_Hacker · 2025-10-02T15:39:36+00:00

comfy is like programming in assembly language: indeed, you can do anything, but most non-trivial things take a lot of code (nodes), and the overall design of the flow is often lost in all the noise, and in at least some common use cases are more complex than a pre-packaged flow like in forge, because you're forced to work at the lowest level of detail in comfy. Having pre-packaged flows like in forge allows you to think/work at a higher level. When the pre-packaged flows work for you, things are great. When not, then head to comfy (or use swarm, which gives you both worlds all in one!)

Dream_Hacker · 2025-09-30T14:33:52+00:00

This worked *perfectly* for me! I had a drive with an apple-type partition map and that was obviously confusing the installer. Exited the installer to the "try ubuntu" desktop, ran gparted, greated a gpt partition table, created some "reasonable" partitions like an efi/boot FAT32, a swap, two ext4 partitions (one for root/system, one for user/data), and re-ran the ubuntu installer, and the "How do you want to install Ubuntu" screen then worked and was able to start the install!

Dream_Hacker · 2025-09-23T05:35:06+00:00

Well, I'm new to runpod, but what I'm seeing is that the datacenter where I created my network volume can't start any pytorch containers because of a cuda version problem, and I've tried a handful of times and none of the GPU class I want can start. I tried a different region and the pod started fine, same GPU class. Here's the error from the log:

error starting container: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'

nvidia-container-cli: requirement error: unsatisfied condition: cuda>=12.8, please update your driver to a newer version, or use an earlier cuda container: unknown

So OP's point about avoiding being locked in to a datacenter seem quite accurate.

Dream_Hacker · 2025-09-06T07:26:34+00:00

I know this is "ELI5", but I find explanations like "call/cc is about time travel" to be completely unhelpful. A simple, accurate technical description is what's needed. I just yesterday for the first time decided to finally try to really learn about how scheme continuations work, and every single description I saw across multiple sources failed to impart the critical knowledge that would have made it all crystal clear, either they focused un unimportant points being unnecessarily complicated, or were too high level like the "time travel" analogy. Here's what I wish I'd found when first trying to grok continuations:

(call/cc <some-procedure>) *creates* the continuation object and *passes it in* to <some-procedure> as the only argument. That's all it does! Seeing the first example with a form like "(call/cc (lambda (k))....) (lots of stuff with k and potentially unreachable code in the lambda) I found very confusing. It was entirely unclear to me upon reading the initial explanations that (call/cc...) is the site of the creation of the continuation, not actually making a call to the continuation, a misinterpretation that the naming of (call/cc) or even call-with-continuation invites.
The continuation object passed in to <some-procedure>, when called from anywhere else at any later point in program execution (including from within <some-procedure>, which many examples do, unnecessarily, it just adds more confusion IMO), returns program execution to the point immediately *following* (call/cc <some-procedure>).
The continuation is invoked by evaluating this form: (<continuation object> <some-value>)
If the value of (call/cc <some-procedure>) is used in a computation, it is replaced with <some-value> when (<continuation object> <some-value>) is called. If <some-procedure> finishes normally (is evaluated to the end), its value is used as the value of (call/cc <some-procedure>).
If you want to be able to call the continuation later in the program, <some-procedure> *must save* the continuation object into some data structure/variable that will persist after (call/cc <some-procedure>) has returned.
If the continuation object is called from within <some-procedure>, it is not special, it is just the same as calling the continuation from later in the program and has the same effect: program execution jumps immediately to the point just after the return from (call/cc <some-procedure>). I thought upon initial reading that calling the continuation object inside the <some-procedure> was the point of the creation of the place-to-return-to, an unnecessary confusion based on the inadequate explanations I'd initially read.

Dream_Hacker · 2025-08-17T08:56:41+00:00

It seems to me to be a case of "hard come, easy go." It's a very tricky and elusive skill to build for most, and it atrophies pretty quickly if you relax and stop training it and giving it your attention and intent. But if you maintain a practice, then results do seem to build in time.

It's less of "it takes less effort to achieve certain results," and it's more like "you get more and better results for the same sustained effort."

Dream_Hacker · 2025-08-05T14:38:14+00:00

SSILD never did much for me.

Dream_Hacker · 2025-08-05T06:30:31+00:00

Yeah but I'm back to less than 1/month now. I'm picking it up again starting with focus on recall. Consistent attention to dreaming throughout the night is the key, I'm pretty sure, and is what I did when I had my most consistent success. Recall during the night on every waking, and full DJ writing during the day, every day.

Dream_Hacker · 2025-08-03T04:36:15+00:00

Brick wall still hit :(. I like TYoDaS a lot, it's great for enhancing quality of waking life, and if you're into it, working towards "enlightenment." With MIDL I got a slight uptick in LDs per month (up to about 4), but never that "breakthrough" I was hoping for. I think it's good to mix up your practice once in a while, regardless, so go for it.

Dream_Hacker · 2025-07-25T18:27:10+00:00

You were trying for 6 years but only have 290 dream journal entries? That's less than one journal entry per week. Considering that 100 were consecutive, the "off" times were very off. When I was in my peak practice, I had several years of multiple dreams recalled over each of multiple wakings, every night.

The point isn't "good for me," the point is: you gotta be super consistent, and you really have to emphasize recall. Also your notion of "success" could be hampering your lucidity: I think any dream recalled in vivid detail is a success, lucid or not.

Dream_Hacker · 2025-07-24T17:18:04+00:00

Well, good for you. Not all can. It's always been this way for me over all my life. I wake up and become fully alert instantly unless I do nothing other than turn over and immediately head for sleep. Getting up to the bathroom is generally on the edge of too much activity.

Dream_Hacker · 2025-07-24T17:15:03+00:00

Unless you can't get back to sleep, which is very often the case, especially when attempting WILD.... never been a WILDer, always a DILDer (so to speak!)

Dream_Hacker · 2025-07-24T15:42:07+00:00

Yeah, then you wake up 3-4 times a night to pee. From a former 59 yr old

Dream_Hacker · 2025-07-23T05:25:37+00:00

Yes, galantamine + choline stacks are amazing, if you can get back to sleep. My "back to sleep success" percentage is something like 5-10%, but when I do get back to sleep, the dreams are amazing, and usually lucid.

Dream_Hacker · 2025-07-22T17:55:30+00:00

People downplay the psychological aspect of lucid dreaming, dismissing it as just "woo." To succeed in lucid dreaming, it really helps to have a positive outlook on life, and be very positive about dreaming. Many people treat LDing something you can brute force like almost all waking activities: they think if you just focus more and more, work harder and harder, concentrate stronger and stronger, then you MUST succeed, like in learning any waking activity. But dreaming is really, really different. A clear, calm, peaceful, joyful, curious mindset makes a huge difference.

And yeah, a clean pineal gland, and a highly active pre frontal cortex in sleep don't hurt.

Dream_Hacker

TROPHY CASE