I'm sitting here at the Hyatt Regency Columbus at the second Ohio LinuxFest, and so far the most interesting talk was about Security-Enhanced Linux. But it wasn't interesting only for the obvious reasons; it was also interesting because it reminded me of some mildly annoying namespace clashes in technology:
When someone mentions "MAC", it could be a reference to:
- An Apple Macintosh
- Medium Access Control on an ethernet network, or the hardware address used in that protocol
- Mandatory Access Control security
Then we also have:
- eMacs, the type of Apple computers
and
- Emacs, the "extensible, customizable, self-documenting real-time display editor."
I've also learned enough about FreeBSD here that I might give that another try; the last time I tried it was in the late 90s with version 3.something.
When someone mentions "MAC", it could be a reference to:
- An Apple Macintosh
- Medium Access Control on an ethernet network, or the hardware address used in that protocol
- Mandatory Access Control security
Then we also have:
- eMacs, the type of Apple computers
and
- Emacs, the "extensible, customizable, self-documenting real-time display editor."
I've also learned enough about FreeBSD here that I might give that another try; the last time I tried it was in the late 90s with version 3.something.
(no subject)
(no subject)
Best part of the conference was the irc heckling during talks.
(no subject)
FreeBSD
On the other hand, it does make custom code changes a little more straightforward.
I'm still not clear on how ports are upgraded. My OpenBSD experience with them was that they're great on first installation, but a pain when anything needs to be upgraded.
Anyway, I've been meaning to ask you about FreeBSD anyway (for servers), since I know you're a fan and I trust your opinion.
Re: FreeBSD
http://www.freebsddiary.org/portupgrade.php
Re: FreeBSD
Re: FreeBSD
Re: FreeBSD
(no subject)
Sunday