Slashdot Mirror
FreeBSD 8.4 Released
kthreadd writes "The FreeBSD project has released version 8.4 of the free operating system with the same name. Highlights of this version include GNOME 2.32.1, KDE 4.10.1. In this release, focus has been put on improving stability and storage capability. The ZFS filesystem has been updated to support feature flags for ZFS pools, asynchronous destruction of ZFS datasets, LZ4 compression and ZIO NOP-write optimization. Also, support has been added for all shipping LSI storage controllers."
Most desktop users won't want to install this release. FreeBSD 9.1 was released in December 2012, and is the most recent stable release. This 8.4 release is a point release in the still-maintained 8.x series, intended for people currently running 8.3 who for one reason or another don't wish to upgrade to 9.x yet, but who do want an incremental upgrade.
10 PRINT CHR$(205.5+RND(1)); : GOTO 10
No, me!
More seriously, as a ZFS user (first on Solaris, now on Linux), I'm happy that ZFS outgrew Oracle and lives on as a community opensource project. I greatly prefer it to btrfs, if only on a management level. And ironically, ZFS is now completely free of Oracle influence, while btrfs isn't.
It's probably worth pointing out that this is a legacy release and the current production branch is 9.X, currently at 9.1-p3
-- sigs suck --
If memory serves OpenBSD 5.3 was released with GNOME 3 and KDE 3.5. Here we see FreeBSD 8.4 released with GNOME 2 and KDE 4. Can anyone shed some light on why one BSD operating system has a modern KDE and outdated GNOME desktop while the other has the reverse?
could you please guys implement some anti exploitation technologies such as ASLR out of the box ? Or maybe dedicate a manpage explaining the dev team views over such matters.
I've been a long time user of FreeBSD and i can't help but to feel it keeps dragging behind in this field.
Or please someone explain me why i shouldn't be worrying about that.
Explanation: You're running BSD. What gains is ASLR supposed to provide you, the end user? Protecting you against a custom crafted process injection attack on your specific BSD distro written by someone who could have made more profit creating a bogus kickstarter campaign or by attempting to mine bitcoins?
(I kid... there's enough stuff running FreeBSD that no ASLR by default is a bit odd... but it sure makes debugging easier)
Seems a stupid reason, because it takes all of 5 minutes to "fix."
For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
There's just nothing more frustrating then tcsh.
You have clearly never been forced to use Lotus Notes.
XML is a known as a key material required to create SMD: Software of Mass Destruction
Huh. I change all my shells to tcsh. I set up my configuration the way I like it in 1996 or so, so it's the path of least resistance for me.
W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
This is what I have been wondering - ever since FBSD came out w/ version 9.x, why are they still coming out w/ versions like 8.3, 8.4...? Does that mean that once they have version 10 out, they will continue to have 3 tracks - 8.6, 9.3 and 10.x?
Should I, as a *BSD newbie install this at my home laptop wich it's used by my wife, which only checks facebook from time on time, reads email and play some solitaire and angrybirds?
Myself am a windows user with a basic++ linux knowledge: I know how to install and update a distro(I prefer debian based but right now am wanting to test Fedora 18), compile some packages from source, has poked some kernel compilin', made some kde translation on the past, reported some bugs on FOSS software, etc. Now I have my Dell laptop with Windows 7 and I'm planning to back it up and format it and I'm thinking to put it up Fedora 18, but the BSD world has intrigue me and I've made some test on virtual machines.
BTW I'm primarly a Java developer how some times made some tiny personal project on my laptop and who enjoys a good Quake 3 match(for remembering my old days on the College fragging like there were no tomorrow) but who actually prefer to enjoy the time with my wife and the kids.
Could a user like me install some BSD distro and used it regularly to this basic things I've listed? if so, which BSD do you suggest?, bonus points if lastest KDE's it's available
Thanks for your suggestions!
Slashdot ya no es que lo era!
Do any of the BSDs now use bash, particularly since the latter is GPL3? But there are a plethora/bonanza of shells out there for Unix other than bash, tsh, tcsh, csh. Maybe FBSD could use ksh or zsh?
If you read about ASLR and I recommend the OpenBSD paper on the topic (I think they implemented it 1st) the technique only makes it more difficult, it doesn't SOLVE the problem. If you benefit from ASLR, then you have a security problem already. I'm not sure I like the idea of losing entropy and slowing down malloc for something that does little to stop attacks from rogue processes (which can be compromised by other methods.)
Sure, I might prefer you DoS some process by crashing it repeatedly instead of taking control over it... but I would prefer you not corrupt or crash it at all and I would want more effort put into better jails and damage control. Removing strcpy and other common trouble makers like OpenBSD does would be nice. ASLR adds to the level of complacency (except on OpenBSD where paranoia is expected.)
The goals should be what they always were. New buzzwords be dammed.
NOTE: I'm years behind on my BSD.
I'm not convinced we shouldn't be moving towards microkernel hybrids like Darwin and towards a full microkernel. We took a big speed loss going to protected memory management which was accelerated in hardware and new CPUs made the transition almost unnoticeable. Maybe we should be aiming for something similar? (just isolating most drivers would help; you could leave the FS and HD within the kernel.) I also hate to think of how cool it could have been in Multics was used in place of unix... every unix has been more bloated for decades and I would love to swap RAM, CPUs, etc without rebooting. I find netBSD's work on including an interpreter in the kernel to be interesting in a shocking kind of way. Anyhow, the point is that ASLR is just a niche band-aid and not the most important feature we "must have" to continue living... and we've survived for decades without it. Such complaints sound more like an IT person speaking.
Democracy Now! - uncensored, anti-establishment news
It took thirty years, but they finally came out with a system twice as good as the old original BSD 4.2 (no open/free/net) that I used back in '83!
General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
The ports tree has Bash 4.2.45, i'm not sure how up-to-date this is compared to linux.
As for a list of shells, the Ports tree reports 49 different shells, although some of them are just tools: http://www.freebsd.org/ports/shells.html
As for your question, FreeBSD does has KSH and ZSH.
As an addition to my previous comment. Upon further investigation (by which I mean I discovered bash --version), I found that the version of Bash in the ports tree is indeed a GPL V3 version of Bash. I assume this means that whilst the FreeBSD project can not use any GPL V3 code in the operating system itself (I believe by FreeBSD 10 they want to have removed all GPL code full stop), there is no restriction on the licencing used by software in the ports tree (within reason).
Also, I quickly checked my Debian Wheezy box and that runs Bash 4.2.37, and Arch is using the same version as FreeBSD. I guess it shows that depending on the package, the ports tree can be rather bleeding edge at times.
I'm fucked. I use tcsh on my *nix boxes and now my employer is moving to Lotus Notes and I have to move all the Exchange shit over to Domino and join it to the French company that bought us.
-- I have a private email server in my basement.
I'm fucked. I use tcsh on my *nix boxes and now my employer is moving to Lotus Notes and I have to move all the Exchange shit over to Domino and join it to the French company that bought us.
I am told by those who know more than me that Domino is actually pretty good, it's the client that sucks dead dingo kidneys. However, the Exchange to Domino migration has been known to trigger a wide variety of psychological and medical disorders.
XML is a known as a key material required to create SMD: Software of Mass Destruction
I have not checked lately, but it used to be the case that a lot of things broke if you changed the root shell. Maybe they have fixed that.
I think the "fix" for that is toor. You can change its shell to whatever you like and use it instead of root. Although I've never tried it; I just have an alias that calls sudo -i exec zsh -l, which seems to work great.
ASLR has been usefully complicating enough vulnerabilities to have proven it's worthwhile. At this point it's quite near being an industry standard for any system that follows good security practices. It's really not credible to reject it anymore as too complicated to risk bothering with. Yes, some of the issues can be addressed more deeply, too, but security should be layered and redundant.
A major cause for why there are less exploits on the *BSD kernels is that the rate of innovation is so low. New and rapidly changing code is where a lot of security bugs come from. If Linux kernel development did a lot less work each year and has a smaller feature base, they could spend a lot more time on hardening too. The *BSD approach isn't a bad one, but it's a trade-off with good and bad sides to it.
I don't believe you've checked... EVER. There's nothing TO break by changing the root user's login shell.
All the services that start up (eg. crond) are completely ignorant of what root's shell is set to. Services don't go through the process of logging-in as root and then spawning processes... They use the setting and environment they inherited from the rc* scripts, from start-up, while the system was single-user.
Any programs or shell scripts you run once the system is multiuser as root, will be run with whatever interpreter they're set to use with the #! line. They don't know or care what your shell is.
In short, there's practically no way that changing root's login shell to something different could possibly break anything. Now, if you do something stupid, like replace /bin/sh with something else, you'll break the whole damn system, but that's an idiotic mistake, and not how anybody should ever change a user's preferred shell.
Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
That is correct. They don't want GPLv3 in the operating system, but ports is OK. FreeBSD is very different from many Linux distributions in the sense that the operating system and most third party software is managed separate from each other. In Linux you often have a single package manager that handles both the operating system and all your software, with no clear distinction between them. In FreeBSD these are completely separate.