Hacker Newsnew | past | comments | ask | show | jobs | submit | ogogmad's commentslogin

It might be possible to use a randomised algorithm to estimate the number of matches in only linear time.

if a boycott is a virtue signal then your comment is a vice signal

This sounded at first like a mouth guard, to stop teeth grinding.

Would it not have been easy to add branch instructions to it? Just rewind the instruction tape however many places. It seems 99% of the job was done.

> A portable GUI interface is a hard problem, unless you mean "a browser window without an URL bar" and your controls are HTML/CSS components.

Win32 + Proton/Wine? No idea.


I did some manual partitioning when installing Kalpa: I added a Swap partition whose capacity I set equal to RAM + 2GB, which got hibernate working.

I think Hibernate is strictly better than Sleep: Why should a computer still use power when it isn't doing anything? And if you could get a desktop to recover its state before a full reboot without using Hibernate, then why would you need Sleep anyway?


Yeah I read further down in the comments that Aeon and Kalpa have actually diverged quite a bit, the installer might be one of those divergences. How are you liking Kalpa?

The main benefit of sleeping to RAM is of course the resume speed, which makes it more suitable for when you just left your computer inactive for 15 minutes. That goes double if you use encryption without TPM unlocking.

For leaving your computer overnight, hibernate wins on all fronts. I'm enthusiastic about sleep-then-hibernate schemes, but haven't gotten them to work on my devices yet.


I thought so too, until i saw what writing ~50GB to disk multiple times daily does to SSD lifetime for no good reason.

Being able to roll back updates/upgrades that go wrong, is not just fixing a minor inconvenience. There's also something about the critical part of the system being less mutable. Desktop Linux has been way too easy to break in the past.

Tubleweed has snapshots and rollbacks too by default. But yeah immutable distros are good for beginners so they don't destroy their system!

The OS this is based on, Tumbleweed, is what provides that capability. I do not think there is anything novel here.

> I do not think there is anything novel here.

Absolutely wrong.

Tumbleweed is a conventional distro. You're root, you can do whatever you want, you have full R/W access to the entire FS, and updating is by installing lots and lots of packages into the live OS while it is running.

Aeon and Kalpa are immutable: the root fs is largely R/O even to root, and you cannot install or update packages on the running system. To install packages into the OS itself you must reboot, and installation is transactional -- it can automatically undo changes that prevented a successful boot.

Kalpa is the KDE desktop version of MicroOS.


> and installation is transactional

Good explanation, but note that Tumbleweed can use transactional-update with btrfs snapshots like MicroOS. Updates are still applied live though.


Okay, fair enough!

You might know this, but unfortunately, if you leave an Arch install unused for enough time, and then run an update, you might not be able to boot into a working desktop.

[EDIT]

Oh, and I had a lot of problems installing Kalpa (from the submission) - all which I got fixed by using ChatGPT.


I left an Arch install sitting for a few months and came back and had trouble getting the updates to properly install. Seems the advice around it is basically just don't go that long without updating.

I've left it for a long time and also run it daily sometimes, still no issues. My understanding is brick level changes usually are fixed quickly.

How long is a long time? I left mine for 2 years.

brick level changes will render the device unusable. You dismiss it like it was no big deal to brick a device.

Eh I misspoke, I don't think you can actually brick anything with this, its just it might not boot properly, you can still format over it, or fix it if you run a LIVE Linux disk to rollback. You also always have an option to run previous system configuration.

The more I think about it, I don't even use Pacman, I just use the other tool that comes with Endeavuor, which is a face to Pacman and probably shields me from doing doofus things. Pacman is easy to screw up an update with.


EOSupdate is basically just a yay and pacman script, as I understand it.

Bollocks. This can happen for any distro or OS. Stick to distro packages and this isn't notably more true for Arch than for most other distros or OSs.

If you build and install packages from AUR, or use dodgy repos like Manjaro, then risk of update woes will increase significantly.


I don't have key problems on Debian or Fedora, but I do on Arch, even without AUR packages.

It's possible that you won't anymore if you preceed full upgrades with a `pacman -Sy archlinux-keyring`.

If I have to solve it by applying a manual fix it's still a problem, right?

Also at least up until 2 years ago (I have since stopped using arch) that did not solve it.


> Bollocks. This can happen for any distro or OS

I've never had this happen with Windows or Mac.

> this isn't notably more true for Arch than for most other distros

Agreed. Welcome to Linux.


OpenBSD might have "better" support for sleep and hibernate, but I didn't succeed in installing it on this laptop: I think it required me to connect an Ethernet cable, which I wasn't going to do.

Veering even more off-topic: I've just installed OpenSUSE Kalpa on this laptop. That's not regular OpenSUSE, by the way. Previously, each of the like, 5 problems I've encountered doing it, would've caused me to give up - but ChatGPT helped me fix all of them! I think this is going to become my daily driver for a while now.


I think you would get sqrt(x^2) = x, if x belonged to the natural domain of sqrt, which is a Riemann surface, that may also be defined using the language of "sheaves". I don't know how to connect this to the article or Mathematica.

it's literally the prototypical example for `Assuming`

https://reference.wolfram.com/language/ref/Assuming.html


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: