41–50 of 65 posts
> It doesn't overwhelm you with thousands of packages and dozens of boot services right in a fresh install. On the contrary, it does only what you tell it to do. It puts you in charge and makes you feel like you can understand it top to bottom. Just like Arch Linux and Gentoo, of course.
and even Arch (Artix) can't be stripped of elogind and such
> It doesn't overwhelm you with thousands of packages and dozens of boot services right in a fresh install. On the contrary, it does only what you tell it to do. It puts you in charge and makes you feel like you can understand it top to bottom. Just like Arch Linux and Gentoo, of course.
> just like Arch Linux and even Arch (Artix) can't be stripped of elogind and such
seatd is ~6k lines of code compared to elogind's ~200k.
Earlier quoted context omitted.
I wonder what would be the closest (because I do not think there is such a thing) today. And I do not mean military grade things. I mean „normal“ laptops that are tough and functional.
Most (all?) modern business laptops are actually very tough. Reviewers regularly bend them in ways that would make you faint if that was yours and they are fine.
A lovely ride down memory lane. These IBM machines were all works of old, beautiful computing art.
I wonder what would be the closest (because I do not think there is such a thing) today. And I do not mean military grade things. I mean „normal“ laptops that are tough and functional.
> In general it's safer to use a smaller root partition and a separate one for /home. However, NetBSD worked just fine off a single full-disk partition. Right until there is an update or anything and a bootloader or one of its required files gets written past the 8GB barrier, rendering your system unbootable.
I do not fully understand this. Can you add specifics ? To me the article indicates he used a small root partition. Or did I miss something ?
A little hint for people (like me) who have a separate partition for /usr, /var, /tmp and /home due to cgd encryption or other reasons. If using wireless, you may need this in /etc/rc.conf to force a mount before daemons kick off. In my case, without this wireless breaks.
critical_filesystems_local="/var /usr /tmp"
The 2 "new" systems (T430, T61) runs NetBSD without any issues. FWIW, if running a BSD you may want to add your dmesg here:
Also curious, what is that file manager in the print ?
I like seeing all these NetBSD articles ob various sites. That OS, especially 10.0 seems to work great. I recently started using NetBSD again because I finally got a couple of free "older" thinkpads. My old hardware failed about 5 years ago and the Laptop I replaced it with has troubling hardware for both Open/NetBSD. The 2 "new" systems (T430, T61) runs NetBSD without any issues. FWIW, if running a BSD you may want…
In my basement are quite some old but for the time powerful unix machines. SGI Indigo2, Sun Fire, a Pentium II with Knoppix Linux or my Samsung Laptop from 2010 with Ubuntu 16.04. They all boot up quite fast into a nice looking and snappy X Window system. Fantastic machines. Until.. You try to open a web browser, if there is even a modern one available. If you try to open a modern web browser on those machines, you s…
In my basement are quite some old but for the time powerful unix machines. SGI Indigo2, Sun Fire, a Pentium II with Knoppix Linux or my Samsung Laptop from 2010 with Ubuntu 16.04. They all boot up quite fast into a nice looking and snappy X Window system. Fantastic machines. Until.. You try to open a web browser, if there is even a modern one available. If you try to open a modern web browser on those machines, you s…
I imagine running a browser on a remote modern machine using X11 forwarding over SSH would work well enough to let vintage computers use the web as it is today. File downloads would have to be a separate operation using rsync.
Or NFS (at which point it's a lot less separate)