Live data from Hacker News

Using the same Arch Linux installation for a decade

meribold.org

151–160 of 422 posts

Re: Using the same Arch Linux installation for a decade

#151
post #106

Earlier quoted context omitted.

I get that some people don't like tinkering. They want something that will always Just Work. Some of my friends who were long time linux uses switched to macs and stayed there. MacOS wasn't that for me- brew was the cause of no shortage of pain, but even that could have been lived with. It's also not exactly stable- one company I worked for (about 7 years total) had a blanket request that people not update OSX to new…

I recently got a macbook for work and I can't believe how many minor things just can't be changed. I don't think you can change the date format in the top right. It seems like you can't get rid of that damn dock entirely without killing important processes and breaking things. (I'm able to hide it and put it in the left, so it's mostly out of the way, but it seems so anti-user to force this interface on everyone). I…

What i've discovered is you really need to buy and/or install a bunch of 3rd party applications to get that horrible UI to work in any usable fashion.

Re: Using the same Arch Linux installation for a decade

#152
post #119
post #99

Earlier quoted context omitted.

When I don't need Windows for gaming, I just boot the physical windows partition from Linux using Virtualbox. This way I don't even have to hibernate and interrupt any work.

Isn't windows "Installing new hardware" every time you boot? And the license is still active? I was always affraid it will break the system after few switches between virtual and bare-metal boot.

I've been running this setup since 2017 and while there were occasional graphical and sound glitches, usually after a Windows update, over all it works great. It did the "installing new hardware" thing only after updates as well, so I didn't run into it too often.

It does like to deactivate itself after a few reboots, but that's nothing a bit of mild piracy can't fix. I have at least two spare windows licenses in a drawer so I don't feel the least bit bad about it.

I also have a big ugly powershell script that runs during startup and does some things differently depending on where it's running. Things like not launching all my background stuff in the VM, remapping drive letters between physical disks and VM folder shares...

Another thing to look into is RemoteApp. I did some experiments with it in a VM and the performance was way better than "seamless mode" (which doesn't exist anymore anyways), but getting it to work on non-Server editions is a pain.

Re: Using the same Arch Linux installation for a decade

#153

Earlier quoted context omitted.

Yeah Arch is basically the final destination all that distro hopping gets you to. No reason to hop once you've arrived.

I used arch around 2008 or so, then distro-hopped to Slackware, when I remain to this day. Some of us escape.

I started on slack and hopped on over to arch eventually. But lately been considering going back to Slackware again. Circle of slack.

Re: Using the same Arch Linux installation for a decade

#154

I recently switched to an arch flavor because the AUR had a lot of little small utilities that make life better on wayland. Also, it's quite easy to install the latest version of golang and rust, etc. Pros: Documentation is excellent. Better than even Gentoo or Ubuntu's docs. Cons: Arch doesn't have an installer, and seems almost militantly against providing one, or a lot of other little utilities that could improve…

> Arch doesn't have an installer, and seems almost militantly against providing one, or a lot of other little utilities that could improve the user experience This just changed! The archinstall package is included on install media now and is not considered experimental (according to the wiki page history, that happened on 2022-07-08). https://wiki.archlinux.org/title/archinstall

I recently adopted Arch onto my laptop and didn't even realize 'archinstall' wasn't always a thing. I looked up a traditional Arch installation and think I might have skipped it had the installer not been present when I was distro hopping.

Re: Using the same Arch Linux installation for a decade

#155

I recently switched to an arch flavor because the AUR had a lot of little small utilities that make life better on wayland. Also, it's quite easy to install the latest version of golang and rust, etc. Pros: Documentation is excellent. Better than even Gentoo or Ubuntu's docs. Cons: Arch doesn't have an installer, and seems almost militantly against providing one, or a lot of other little utilities that could improve…

As a Linux noob i actually picked arch because it doesn't have an installer. Just installing arch I learned a lot about how computers work and how much is actually done by other operating systems like windows. I just followed the installation article in the wiki and didn't have any issues I couldn't solve. There are plenty of nicer distros for people that just want to use Linux. In my field of work RTFM is pretty standard so I don't mind it in the arch community.

Re: Using the same Arch Linux installation for a decade

#156

How often did the upgrade process broke? I've been using it for a few years and it broke a few times... but overall very happy.

My install has been alive since 2014. I've never had the upgrade process outright break. One in a while it requires some manual intervention like holding something back, or ignoring some package while upgrading. The only really "big" problem was when i switched from Nvidia to AMD and had to boot from a usb to restore the video drivers after failing to completely configure them. This install has moved 4 disks in this…

> Once in a while it requires some manual intervention

that's what I meant by breaking

Re: Using the same Arch Linux installation for a decade

#157

Earlier quoted context omitted.

I would like to defend arch here. In my experience, Arch's main focus is on upholding a simple consistent architecture. There are tools that do something like the bare minimum required work, and then excellent documentation so that the end user can correctly perform the remaining required work manually (or via their own scripts). As a result, there are certain features that will probably never be implemented. For exa…

> Another example is installers. Writing a basic installer for a single machine is easy. Writing an installer that covers any machine is very hard. Writing an installer that covers any machine with any configuration the user might want is impossible. This is a cop out. An installer doesn't need to cover every option a user might want. An installer only covering popular options/configurations is only a problem if the…

I think the historical opposition of Arch devs to an installer is more maintenance. Most advanced users end up scripting their own specific system or getting a muscle memory for installing it (and that’s if they install Arch frequently at all).

Most if not all Arch devs are likely advanced users, they didn’t need to maintain a user friendly installer for themselves so the old one got out of date and was removed.

What’s probably changed recently is that Arch has grown enough to get devs/trusted users who actually wanted to write and maintain an installer, so now it has one.

I find the Arch dev justification/perspective for most things much better than many users on the forums who tend to pick up the basic idea and cargo cult it whilst losing the context behind it.

Re: Using the same Arch Linux installation for a decade

#159
post #90

>my experience doesn’t match the common notion that Arch Linux is unstable Arch is unstable, as in, package versions constantly change and can (will) introduce bugs and regressions. Debian is considered stable because apart from security updates package versions are set in stone til the next release, so there won't be any surprises. This is stable/unstable difference, that doesn't mean that you can't break your OS an…

> Debian is considered stable because apart from security updates package versions are set in stone til the next release, so there won't be any surprises. which is not what the rest of the world means by "stable" when talking about software, so there is in practice a lot of surprise for users coming to Debian when they hear "stable" thinking that it means "no bugs" when it actually means "no changes"

> which is not what the rest of the world means by "stable" when talking about software

But it is what the rest of the world means by "stable" in lots of ways: a stable climate, a stable government, a stable relationship, a stable heading. I don't think it's far-fetched for Debian to use it in that meaning about software as well.

Re: Using the same Arch Linux installation for a decade

#160

I always reinstall from scratch although I could just Debian "dist upgrade". My thinking is this: if, ten years ago, I somehow missed a security patch or some 0-day owned my machine before it was patched, then I'd potentially have been copying / dd'ing / rsync'ing a rootkit for ten years. By installing from scratch at every new stable (or unstable) release, I get rid of a lot of potential security issues. Now as an a…

> But it's fun to think I own one of the computer in the world with the biggest uptime.

The top 500 entries on that list are almost guaranteed to be mainframes.

Post reply on HN