Yeah, they would both be lying and admiting to vibecoding so idk how that would make it better

Yeah it is, but that doesn’t make the concept of it any less valid. Conciousness is the moment when you can think about more than just what your senses tell you, it’s the awareness of internal and external experiences and how much you are aware of them are the levels of conciousness. You could call in as much of a human construct as the concept of time, but that doesn’t change the fact that it’s describing something concrete. Just look up something like “levels of conciousness” and think about it a little, it really is such an interesting topic! Then again, by that definition, a good chunk of humans fall on the very lowest points of the scale. Again, not drawing any conclusions, this and my previous message are just to point out that this is deeper an more interesting than some people in this comment section make it out to be.

We have mapped a fruit fly brain and can make it play DOOM. I mean people don’t have much empathy for them in real life, but they do recognize it’s at least a living thing. Does that mean the 1:1 replica playing tetris is a living thing? Is it concious, both living or on a PC for that argument? If we scaled up the same technology and emulated a hamster’s brain 1:1 would that be considered concious? What about a human? Is it even fair to compare a fruit fly brain to an LLM? I’m not taking any stance here, I’m just saying it’s a super interesting topic. Cyberpunk 2077 explores that theory very well and I still have no answer as to what I think.

heeeell yeah

I was actually excited to read this because I thought if it was open source, you could just un-Microsoft the code but yeah, that was naive of me. Fucking clowns.

Just gonna shamelessly leave these two paragraphs out of the website of my own distro here.

Same here, I got a Gen 1 X13 for 120€, it’s not powerful by any means but perfect for running Linux and browsing, coding, writing and so on.

Yeah, you have a point, but still, twice in three years? I don’t know how representative it really is, ESPECIALLY when you see 50-100% ups and downs in the Linux user base. 5 to 3 percent and back cannot be the actual stat, that has to be unreliable selection of users.

I still don’t get why I can’t opt in to participate in the survey every month, I’ve only been asked twice in the last three years on Arch

Interesting, thank you for that link! I was also thinking about bootc as a candidate but that seemed unintuitive to me so I went with ostree for now. The current implementation needs some refining but definitely is a better start that I imagined, quite happy how it turned out.

Regarding the quotes, I’m brainstorming if there’s a way to, I wanna say “re-route” the pacman commands to edit the package list so you use the pacman commands like usual but they get applied as if you use the gui. It’s definitely possible but I’m thinking about how to get that to actually work in a clean way.

My intention behind that statement is that you aren’t forced to use say flatpaks only and under the hood the update mechanism is still pacman even tho you don’t call it directly, does that make sense?

I appreciate it! I’d be especially interested in knowing if there are any locations/directories that the user expects to be carried through deployments or to be writeable that get deleted/overwritten during updates or are read-only in the first place. Finding that would perhaps also fix the issues with some AUR packages not wanting to install. Ideally you can e-mail me your findings to the address on my Codeberg profile and I could write on the code during the vacation and actually test in a VM on my main PC once I get back.

Regarding the platform to discuss on, someone else asked a similar thing today so I’m just pasting my reply here “Hmm, I’m undecided. Me personally, I couldn’t handle running a forum due to my autism, that would burn me out instantly. Having one entirely community run with me occasionally lurking in like I do here would probably be the only realistic option.”

That’s nice to hear! My personal feedback and the feedback from people that have tried it so far seems way better than I anticipated, noone seems to have any big issues. A little more choice during the install, a little less weird messages during updates (nothing critical, just looks odd) and some AUR packages that don’t install in a way that conform to the Arch guidelines (which is more on them than on the OS) and that’s about all the negatives.

I’ll be on vacation for a week and only take my underpowered Thinkpad with me so I’ll be working on some little qol changes here and there to bring a more polished version in a few short weeks. If noone finds anything big that needs fixing I might even be able to justify bumping the version number of the next release to 0.1.0 instead of 0.0.2 since it’s way more stable than I dared to expect.

Either pu-239-update for the gui or /var/lib/pu-239/packages.list manual!

Hmm, I’m undecided. Me personally, I couldn’t handle running a forum due to my autism, that would burn me out instantly. Having one entirely community run with me occasionally lurking in like I do here would probably be the only realistic option.

I was just about to go to bed so apologies for the short answer, I can elaborate tomorrow if you wish. The home folder, including your settings/configs will survive, there’s no difference in the way you organize files to a regular Arch install. The partitioning is preset and non-customizable (for now at least). So no need to worry, you simply install it with the hardcoded presets and use it like you would use your current install! I will likely set up a kind of wiki page to make this more sorted and readable than the current bloated drop-down menu so I can cover this in more detail in the future.

Edit: aah, I overread the first time that you have a home folder that you keep. In your case I would back it up on another drive/cloud first and then try one of the installer options that fit you the most. I should get the option for manual partitioning up and running, but if you don’t do it it exactly like the installer expects, it will fail, which is why I only defined three pre-set options.

I have a shitty X13 Gen 1 myself, which was the first machine (well apart from the probably 50 VMs I spun up during testing) to run this distro! I think the first 5 PCs (that I know of) were Thinkpads, I love it.

Lots of people with Thinkpads, I respect it haha. Yes, code can be contributed via Codeberg, donations via Liberapay, both are greatly apprechiated! Both links are on the website, but I’ll put them here for your convenience: https://codeberg.org/cantosun/pu-239 https://liberapay.com/Pu-239/donate

My plan is to have it on par, if not better than them. Currently I “only” (this is the biggest factor by far) provide the CachyOS kernel compiled by myself but I already differenciate myself by also compiling it for -v2 CPUs. All five microarchitectures have their dedicated repos up and working and I plan to ship all the packages that will boost speed by being compiled microarchitecture-specific.

I’m already building the server needed for that so compiling them automatically will be possible even while I’m on vacation next week.

That’s planned! Initially I actually planned to have a desktop selection in Calamares with KDE Plasma, GNOME and no DE, but while I was drafting the package lists for that I decided to push that back for a later release. This first one is more or less supposed to be a proof of concept so features like that are definitely in the works, but deemed overkill for the first version.

I don’t like black and white thinking and while I fucking hate LLMs in general, as 95% of times they are used for all the wrong reasons, I do have an Intel B70 for cases like these where current search engines just lead to nothing.

Haha, I feel honored to hear that! It’s still rough around the edges, so only use it if this isn’t your only PC. That said, I already use it on my Thinkpad and the only issue I myself encountered so far is that I had to use vscodium-electron-bin instead of vscodium-bin since it wanted to make a systemlink that caused the install to interrupt, otherwise it’s been smooth sailing so far.