Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
@fuck2code aur is basically ports tho.
A simple build script that bootstraps a compile process.
Personally, i find it to be quite annoying when you want a specific version of something.
Then you have to edit the pkgbuild.
- that's where i am really grateful for gentoo, easy-piecy to just mask the version (s) and use equery to toggle which version..
@fuck2code That looks pretty decent as an approach, but it's still another package manager, and a build platform, and there are still dozens of derivatives from Arch, which is pretty much my main issue with Linux.
Granted, there are far fewer than are based on RedHat or Debian, but its still a fair few, and it still has essentially the same basic underpinning in each.
Thats my main gripe - distros are forked because of disagreements or whims, or with a single goal.
Eg, ArchBang uses OpenBox and emphasises speed.
ArchLabs uses OpenBox and emphasises speed, but includes another repo.
The infrastructure is likely identical, and Arch so far looks like the most rational way to set up a slick install, but the divergence of distros and the kernel bloat are still an issue which I just can't be bothered dealing with anymore.
@lotd I knew a guy who switched to Gentoo years ago, and absolutely loved it.
So far as I know, he never changed to anything else.
Isn't portage essentially just ports with a build environment integrated? If so, it's basically the same as FreeBSD, just a little more automated which is pretty much spot on!
Still, kernel bloat though :)
Have you heard of our Lord and savior: "Manjaro"?
@theKarlisK So, arch with precompiled binaries, and their own repository management tool - yet another tool doing the same job as every other repository management tool.
It actually looks pretty good, but it's another layer of stuff on top of a distro.
Theres a Pacman tool for Xfce, and Octopi for kde. So if you want to use Xfce, but like using Octopi, you have to install all of the KDE libs etc...
No, I think I'm going to stick with FreeBSD.
@oudalally yeah, indeed it is, personally, I really like it because it's a modular distro - you can actually remove bits of libraries more violently with the pacman package manager and the AUR (Arch User Repo) is just a collection of prepared build instructions (packages from AUR get built during install and offer you the option to customize the build instructions/options). More often you'll be able to remove or swap out critical system components without it breaking everything or complaining unless absolutely necessary.
Personally, I know how you feel - that is, to a certain degree, how I've always felt about the majority of distros that come packaged with boatloads of stuff that I end up removing up until something else commits seppukku and the whole OS goes tits up after the next reboot.
However, I'm not that well versed in inner workings of Linux just yet and find Manjaro to be the best balance between absolute "Linux from scratch" and Bloatbuntu for me.
@theKarlisK As an approach, it looks to be a great deal better than using a Debian base and throwing more and more packages at it.
That said, I've just installed Xorg and Gnome3 on FreeBSD with the following:
pkg install xorg-minimal
pkg install xf86-video-ati
pkg install gnome3
I now have a pretty vanilla Gnome 3 desktop on my server for when I need to use it.
The package management for FreeBSD is really straightforward - it updates itself, the repos are sensible and the source tree is easy to compile in ports if you need to.
@theKarlisK It's somewhere between the two.
It's not as straightforward as just installing a platform and having it work, but in terms of flexibility, it really is excellent!
I've run into a bit of difficulty enabling a decent resolution on the terminal driver (I've removed Gnome and gone back to plain text with the option to launch X if need be), but I now have the terminal in 1920x1080, which is spot on for me.
The plan is to have text mode only on the physical VT, but allow remote X forwarding to another machine. Ideally, I'd like a full X desktop to log into on a headless box, but not sure if I can do that yet.
It's certainly worth a play though - I'd recommend using a VM until you know if you're happy with it.
@theKarlisK You can install from binary packages using 'pkg', or build from source using ports.
There is also a very clear separation between the base system and the user land, the sound architecture is really well designed, and it's pretty good for hardware detection.
A lot of drivers from Linux have been ported to FreeBSD, but it's not as well supported in terms of compatible hardware.
That said, it's a very stable platform, and the documentation is leaps ahead of anything for linux.
I've lost count of the amount of times I tried to find a guide for something on Debian and all I could find was guides for Ubuntu that were out of date.
@theKarlisK It's what drove me too try FreeBSD in the first place - the nouveau driver.
I wanted to use the closed source Nvidia driver on an Ubuntu machine, and it just wouldn't let me.
I wiped it, and went to Debian. Again, I couldn't get it to work, it just stubbornly loaded the nouveau driver again.
Having used Debian 4 for several years in the past, and had no issues with the nvidia proprietary driver, I considered that to be a step backwards.
FreeBSD has its drawbacks, but it doesn't bind your hands like most other distros do to a lesser or greater extent.
Granted, had I stuck with RH derivatives, I might have had an easier time of things, but thats not the road I went down and it took a long time before I actually tried again from the start.
I've run FreeBSD on a number of systems, and although I've had issues, I've been able to find the solutions to them where in many cases, with Linux, I've had to settle for what it allows me.
In the process of setting up my RAID array at the moment.
Included with FreeBSD is a partitioning tool called Sade. It's text based, and really very nice to work with.
@fuck2code I've tried FreeBSD, Dragonfly BSD and OpenBSD in the past, and the only one I've persisted with is FreeBSD.
It's a decent OS, the development is still active and although progress is slower than with Linux, it's consistent.
I've just had a disk fail on my server (the hazard of using old disks), and annoyingly it's the OS disk, so I have to reinstall all over again.
It's a maxtor disk tho, and considering that out of 9 maxtor disks I've had up to now, 8 have failed, I'm not surprised.
Oh well, should have put the OS on the raid....
Might be able to sort that out with a reinstall and rethink of the partitioning scheme....
Crisis averted - the PSU just couldn't drive that many disks. Thats at least positive.....
@lotd I used it a long time ago when it was still PC-BSD.
My first thoughts were that the installation process was quite frankly beautiful.
I'd been running Debian 3.0 for some time, and the installer for that was somewhat complex for a new user, but PC-BSD just blew me away with how easy it was to get running.
The downside was that the package management for it was new, and there wasn't a huge selection of software available.
Installing from ports was still an option, but it defeated the point of the distro, and you didn't have the nice install/uninstall features of it with ports builds.
I've not tired it since (and tbh, I'm not sure I will any time soon as the FreeBSD installer is now really minimal), but for a new user to Unix, it's a nice way to go I think.
I'm intrigued to try it, but it will be on a VM and probably not for a while yet.
FYI - just moved the OS to a new disk.
1) Connect new disk (320Gb Seagate)
2) Run installer (bsdinstall)
3) Create partitions using guided mode to set up boot partition
4) Quit installer and mount root partition (/dev/ada1p2) on new disk into a folder on /mnt/root
5) Run cd / ; pax -p eme -X -rw . /mnt/root
6) Shutdown, plug new disk into SATA port previously used for the older disk
7) Reboot. The system came up with no issues at all.
That same process using a Linux install with UUID for disk allocation would just fall over entirely.
If you used block devices, it would be easier to work with, but how many distros bother with that?
In addition, moving GRUB to the new device, sorting out the dozens of kernel args would be a nightmare (it always used to be, hence why I stuck with lilo for so long).
This process has just reminded me how much I actually love Unix as a platform.
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job
gururaju32*Now that's what I call a Hacker* MOTHER OF ALL AUTOMATIONS This seems a long post. but you will definitely ...
creedasaurus64Another dev on my team just got a new machine. Before he came in today I made two separate USB installers and ...
linuxxx62This guy at my last internship. A windows fanboy to the fucking max! He was saying how he'd never use anythi...