6 ms·
I am also also a bsd person and also coincidentally ran my first alpine as a vm on bhyve this week. It's busybox. If you don't need explicitly discrete binarie
by ggm 3y ago
I am also also a bsd person and also coincidentally ran my first alpine as a vm on bhyve this week.
It's busybox. If you don't need explicitly discrete binaries of the /bin and /sbin utils it is a tiny user-space and fast to boot. Tmux, zsh and I was done for most unix purposes.
To get to my endpoint I wound up doing a lot of apk installs (node. More node dependencies. Stuff) but overall I found it the best Linux experience I've had in a long time. I wish zfs was baked in, and more overt virtio bindings to things for bhyve zfs backed run.
- chillfox 3y agoZFS works great with Alpine. Alpine + ZFS has been my default server setup for years.
- AndrewDavis 3y ago> zfs was baked in How baked in? I think Alpine is one of the few distros to ship a binary zfs kernel module. So it's just a quick apk command away from getting it. There's some pretty decent documentation to install zfs on root on the alpine wiki too https://wiki.alpinelinux.org/wiki/Root_on_ZFS_with_native_encryption https://wiki.alpinelinux.org/wiki/Root_on_ZFS_with_native_en...
- ggm 3y agoRight, but the steps aren't scripted or integrated into the mainline. You're of the main path, albeit a damn sight simpler than some distros. Easy, but not 'simple'. Don't get me wrong, it's entirely doable. But it's a distinct, non-standard pattern. And virtio..
- wkat4242 3y agoYeah "apk add ZFS" is very scary and off the beaten path :) That's all you need to use ZFS data drives on alpine. On root is admittedly a lot more complex though.
- ykonstant 3y agoIs it particularly helpful to use ZFS on root?
- yjftsjthsd-h 3y agoI've actually used snapshots to roll back an upgrade that got messed up. Of course, Alpine is stable enough that it doesn't exactly come up a lot:)
- Modified3019 3y agoZFS on root (and setting up automatic snapshots) is great for rollbacks if a system update turned out bad, and also allows for being certain there’s no corruption after a power failure or a disk starts getting flaky. It also makes sending off snapshots for a backups a breeze. So it’s not really for day to day issues, it’s more for turning a rare “day of pain” into something much less.
- ssl-3 3y agoAFAIK, for events like unexpected power failure, ZFS is always consistent to the point of the last complete TxG. No snapshot required (and it wouldn't provide more-recent data, either) to deal with power failure-induced data corruption, because there isn't any. And also AFAIK, ZFS snapshots don't protect against data corruption from flaky disks: An online snapshot doesn't make a copy of anything. (That's more like what RAIDZ or copies=2 are for.) Snapshots do make great rollback methods, even for fixing dumb day-to-day mistakes. (I mean, I'm sure none of us have ever done something stupid with a computer, but it probably happens to someone sometimes.) And they are indeed easy to send elsewhere to be used as complete backups of a dataset's state at a single point in time. And there's other good stuff about daily use of ZFS root, too: Datasets. Like other filesystems, ZFS does occupy an entire disk (or a partition on that disk) -- in this case a "pool". But within that pool can be many, many datasets that are independent of one-another, just sharing space in the pool. One linux distro's root might occupy one dataset, and another more-experimental (or major breaking upgrade) distro's root might occupy another dataset. /home can be on a third dataset that both distros use. This is a very wonderful thing for those with limited hardware budgets -- gone are the days of resizing/paring down disk partitions just to try something different. (Datasets can also be copied or moved to different pools and those pools can be different sizes.) Or: Caching. Now that persistent l2arc is a thing, a snappy-feeling system can be built with big (redundant!) spinning disks, and a relatively small (fast!) SSD as a read cache. It's not really just for "day of pain" issues -- ZFS is pretty slick in all kinds of useful ways, as a root filesystem and elsewhere.
- vermaden 3y ago> How baked in? Like in FreeBSD - to be as available option in installer. In FreeBSD You just select 'Auto (ZFS)' - then select disk(s) on which it should happen - hit [ENTER] - and it happens. That level of integration I would expect ... and all that with ZFSBootMenu integration for ZFS Boot Environments.
- dazzawazza 3y agoI've used/deployed FreeBSD for over 20 years and I have to admit I dread connecting to a GNU/Linux box. It's just such a mess of a system with so many variations in inconsistencies. Even connecting to a Windows server makes more 'sense' to me. Anyway, I'm glad to hear that there might be a sane Linux distro out there. I will give it a go if I need a linux box which is pretty rare tbh.
- aeonik 3y agoEveryone who uses BSD says the same thing, but it's still unclear to me what you mean. What inconsistencies does Linux have that BSD does not? I've looked for an explanation, but I only get high level explanations, or specific features like jails. You wouldn't happen to have more information, would you?
- kstrauser 3y agoMy Debian server has a mix of systemd and /etc/init.d startup scripts. That’s the sort of thing where a BSD would be likely to say, ok, as of version N due in 3 months, we’re migrating everything and going from 100% old way to 100% new way.
- cesarb 3y ago> My Debian server has a mix of systemd and /etc/init.d startup scripts. [...] ok, as of version N due in 3 months, we’re migrating everything and going from 100% old way to 100% new way. You'll be happy to know that this is going to happen. Quoting https://github.com/systemd/systemd/blob/v255/NEWS https://github.com/systemd/systemd/blob/v255/NEWS > Support for System V service scripts is now deprecated and will be removed in a future release. Please make sure to update your software now to include a native systemd unit file instead of a legacy System V script to retain compatibility with future systemd releases.
- kstrauser 3y agoEh, I don’t really care either way. The ones I really care about are in my shell history. I meant that more as an example of where the BSD way would be different. Since they manage all of the software together, it’s much easier for them to do wholesale migrations like that.