What if I don't ever want it to be alongside Windows and OS X. When an OS becomes "mainstream" many things happen - the interface is dumbed down for the idiots who don't take the time to learn how to use a computer properly, performance is sidelined for eye candy, documentation suffers, complexity increases - for those reasons I prefer for my OS of choice to have a limited market. Don't get me wrong - I'm not going to stick with FreeBSD if it adopts some monstrosity akin to systemd or launchd. I'll move to OpenBSD, NetBSD, or perhaps go total eccentric to Plan 9. The problem with GNU/Linux is that it ultimately has been commercialised - and positioned as a drop in alternative to Windows or OS X. I don't want a complex system, I prefer minimalism. I stopped using Arch when they cut out initscripts, so I use Void on ARM currently and thats the only Linux I use right now. I've used Slackware, but thats too barebones for me. But hey, some people like that. Cannibalising the older distros isn't a good sign.
Announcement
Collapse
No announcement yet.
The Good & Bad Of ZFS + HAMMER File-Systems On BSD
Collapse
X
-
Originally posted by BradN View PostWell, now that someone's brought up Gentoo, I figured I'd chime in with my thoughts there:
Gentoo and other (especially source based) "choose your own adventure" distros are valuable because they get people exposed to the OS internals in a wide ranging, general sense. People that use it feel all the design fuckups and oversights that happen, and while it's annoying to have to deal with those problems, it's valuable for the software ecosystem for them to be seen and dealt with.
That is, more people get a better sense for how much and what kind of stuff is going on behind the scenes, which is good experience for developers and distro integrators to have, and it causes a lot of integration level bugs to get fixed upstream because there are more users performing these tasks. It also serves as an easy to use testbed/platform for bleeding edge development.
I think if gentoo and distros like it suddenly weren't around, a lot of other distros would get measurably worse in short order.
Comment
-
Originally posted by jake_lesser View PostThey both suck and are in no way represent the future of file systems. Want to see the future of file systems? Look at btrfs and ext4 (especially btrfs).
I get things like:
[220831.896802] BTRFS info (device md0): csum failed ino 3123368 off 53248 csum 3482155253 expected csum 0
Weird thing is, I've had those kinds of issues on multiple systems. And it's just the base OS. The rest is zfs
I've maded the shift to ext4 for root on most systems. mdadm is not nearly as nice as zfs though.
Comment
-
Here we go again
Originally posted by TeamBlackFox View Postbetter performance, the ports system, fine control over every aspect of the system and the more insular to the UNIX lineage. Soft updates on UFS are what I use on my laptop though, vs ZFS, primarily because ZFS, BTRFS and HAMMER have less advantages on single disk systems.
Originally posted by TeamBlackFox View PostThe very reason I used to use Linux as a main OS was because the idea that everyone can do their own thing - different window manager, package management, init system, everyone can control almost every aspect of the OS in the fine way. First, HAL, then udev, then D-BUS, then systemd drove me away. Its a Microsoft software model. And no, its not like BSD because BSD has a MINIMAL base system. rc init may be 20+ years old, but it works. If you're all about advancement though, you'd not even use Linux, no, if we're about the latest and greatest, Plan 9 from Bell Labs or GNU Hurd would be the most applicable, or Haiku OS, or AROS. Seriously - until you control every aspect of the system, you cannot shoot down Slackware, Gentoo, Void or any of those. They're amazing, and systemd shouldn't coerce them into cannibalism.
Comment
-
Best argument I've ever heard.
Originally posted by TeamBlackFox View Postext4 is an abortion - use XFS or JFS. So much more KISS on Linux. Or F2FS on SSD/Flash media. Pick your poison, but don't for hell's sake use ext4.
Comment
-
If the price of replacing walled-garden OSs is becoming one, I'm happier running a minor OS.
It's hard to find new soil in a walled garden.
Now, I'm not saying that I prefer a minor OS as such. If the biggest OS around is an open environment (in terms of code coming and going), it might well be worth using.
For what it's worth, I haven't yet encountered anything I want to run that needs systemd.
And writing init scripts from scratch is fun, in my book.
Still, I'm pleased that some of my code will be used in the next Android version:
Ironically, those who complain about the differences between Linux-based distros seem to not be backing the userland software that's going into Android despite holding it up as an example.
Comment
-
Originally posted by TeamBlackFox View Postbetter performance, the ports system, fine control over every aspect of the system and the more insular to the UNIX lineage. Soft updates on UFS are what I use on my laptop though, vs ZFS, primarily because ZFS, BTRFS and HAMMER have less advantages on single disk systems.
Originally posted by TeamBlackFox View PostThe very reason I used to use Linux as a main OS was because the idea that everyone can do their own thing - different window manager, package management, init system, everyone can control almost every aspect of the OS in the fine way. First, HAL, then udev, then D-BUS, then systemd drove me away. Its a Microsoft software model. And no, its not like BSD because BSD has a MINIMAL base system. rc init may be 20+ years old, but it works. If you're all about advancement though, you'd not even use Linux, no, if we're about the latest and greatest, Plan 9 from Bell Labs or GNU Hurd would be the most applicable, or Haiku OS, or AROS. Seriously - until you control every aspect of the system, you cannot shoot down Slackware, Gentoo, Void or any of those. They're amazing, and systemd shouldn't coerce them into cannibalism.
Comment
-
Originally posted by mercutio View PostI hate the term, but I really don't think btrfs is "production ready" yet.
I get things like:
[220831.896802] BTRFS info (device md0): csum failed ino 3123368 off 53248 csum 3482155253 expected csum 0
Weird thing is, I've had those kinds of issues on multiple systems. And it's just the base OS. The rest is zfs
I've maded the shift to ext4 for root on most systems. mdadm is not nearly as nice as zfs though.
Comment
-
Comment