Fear and Loathing in FreeBSD
qorg11.net
qorg11.net
I find FreeBSD to be a technically better operating system than contemporary Lunux-based OSes but hardware support and usability really resembles Linux space before "dumbed down" dostros like Ubuntu where everything worked out of the box, generally.
Pretty unfortunate to say the least.
More recently (~2016-2017), I tried to install FreeBSD on an old ThinkPad, and I was not very happy with it. PC-BSD worked fine, but the upgrade/re-install to TrueOS broke; I installed vanilla FreeBSD, but that did not work, either, X11 kept freezing/crashing - at that point I gave up and installed Debian.
15 years ago, I positively enjoyed spending a weekend (or more) trying to figure these things out, but now I am old and grumpy and want my stuff to "just work"(tm). NB that I'm talking about desktop usage - my home server runs FreeBSD, and I could not be happier.
In fact, if I wanted to run a BSD on my desktop, I'd look at OpenBSD first (unless I want/need Bluetooth to work...).
That's sort of my case, and given how I don't have much use for Bluetooth, I went with OpenBSD for the desktop. Couldn't be happier - it just works!
If I'm not in a mood to mess around with it, I don't have to: it gives me a nimble computation environment and steady upgrades. If I want to mess around, `cd /usr/src` and it's right there, ready to play.
For example not so long ago I used Ubuntu MATE (whatever was latest) on my son's ThinkPad X220T.
I have three issues:
- 1st minor: After rotating screen MATE Panel moved in various places (xkill helps)
- 2nd minor: sometimes the Bluetooth or WiFi applet in tray area was 'doubled' (did not solved this one)
- 3rd major: after suspend/resume cycle I could not get WiFi to work (reboot required)
After failing to find solution for this WiFi problem on Ubuntu MATE I though that I will try GhostBSD there (based on FreeBSD STABLE) ... and these were my problems:
- 1st major: after suspend/resume cycle I could not get WiFi to work (reboot required) :>
So I left my kid with GhostBSD till now - also he likes the 'kernel messages' at boot comparing to 'silent' Ubuntu MATE boot :)
Regards.
> dostros
It seems your "i" is broken :-)
But yes, hardware (and software) support is the main reason I've been using Linux for the last 5 years after 15 years of FreeBSD. Back in 2000-2010 it would more or less suck equally on both so it didn't really matter, and the Linuxolator was good enough to run most Linux things (played a lot of Unreal Tournament on my FreeBSD box back in the day!), but today is situation is much better on Linux and has kind of stagnated on FreeBSD. This is not entirely FreeBSD's fault, but that doesn't change the end-result, and I have a lot of other things I want to do now than muck about with my system.
I use FreeBSD too as a daily driver and my experience was even better.
See also:
- "Everything you always wanted to know about the Unrelated Movie Reference (but were afraid to ask)"
- "How I learned to stop worrying and love the Unrelated Movie Reference"
- "Unrelated References Considered Harmful"
- "Make Unrelated References Great Again"
When attending a tech conference, you can typically find at least one of those for each day on each presentation track. The last one being an obvious new-comer in overused references. In late 2016 or so, I was at a conference where they had a run of several, _consecutive_ "Make X Great Again" presentations, all in the same room.
Unfortunately I do not remember any relevant details, but I once came across an article that was titled "Everything you never wanted to know about $topic (and were smart enough not to ask)".
It just means "My adventures with _". Actual fear or loathing is not necessarily involved.
Danger was bought by Microsoft, however, right around the time the NetBSD phone was going to market. AFAIK the tech didn't continue much past the Microsoft acquisition. (Source: worked at Danger on the NetBSD project, but left shortly before the Microsoft deal.)
That being said, it would be nice, at least if the resulting system exposed more of its Unix guts, but I am not overly optimistic.
(I used FreeBSD a looong time ago, and am vaguely thinking of trying again one day, so it would be interesting to know.)
ifconfig_wlan0="up WPA DHCP"
and then optionally add IPv6 (though the posted article seems to be preferring IPv4): ifconfig_wlan0_ipv6="inet6 accept_rtadv"Also it shows the progression of feelings, and how things done in a relatively less used operating system.
I don't think we need to put frames around what is interesting and worthy and whatnot.
Lastly, the perspective got me by surprise:
- Ah just edit this file, then use this convoluted command and, you're on the internet. Ah, static IPs doesn't work, but at least DHCP works.
Just this perspective shows how we as humans get fixated to our ways and don't see the complexity inside the things we do. Also, it highlights how many cogs we align to make a system work, and we just underrate the required effort as "Just spend 4-8 hours to set this up properly, eh?".
I think I can go for more, but that's enough.
There's a reason for that
However, I want to quote some parts of the guidelines.
> Eschew flamebait. Avoid unrelated controversies and generic tangents.
> Please don't complain that a submission is inappropriate. If a story is spam or off-topic, flag it. Don't feed egregious comments by replying; flag them instead. If you flag, please don't also comment that you did.
> Please don't comment about the voting on comments. It never does any good, and it makes boring reading.
Have a nice day.
I, for one, find it interesting from the perspective of someone who has thought about giving BSD a spin, but never has.
> On-Topic: Anything that good hackers would find interesting. That includes more than hacking and startups. If you had to reduce it to a sentence, the answer might be: anything that gratifies one's intellectual curiosity.
I think the submission qualifies.
> Please don't complain that a submission is inappropriate. If a story is spam or off-topic, flag it. Don't feed egregious comments by replying; flag them instead. If you flag, please don't also comment that you did.
Ironically, your comment probably goes against the guidelines though; and mine's probably not great, either. The overall idea seems to be "not too much meta discussion".
----------------------------------------
Bless these fellows who still hang on. I was one of them for a time.