The dates of FOSDEM 2010 have been confirmed: 6-7 February 2010 in Bruxelles.
FOSDEM Dates and other BSD Conference dates can be found on BSDEvents.net
The final stage of the FreeBSD-8.0 Release cycle continues with the second public beta release. The FreeBSD 8.0-BETA2 ISO images for Tier-1 architectures are now available for download on most of the FreeBSD mirror sites. As with the first beta release, this is not yet intended for use in a production environment. However we encourage our users to test this release and report any bugs and problems you may have found. For more information about this release and updating details please see the official announcement.
The second of the BETA builds for the FreeBSD-8.0 release cycle is now available. There are still a few things being finished up so a couple more moderately large commits are coming but we seem to be making good progress. The target date for the last of the things still being worked on is BETA3. In the meantime we appreciate the feedback we have received from people who have started testing and some of those problems have been fixed as well.
As was the case with BETA1, BETA2 is still a little bit “rough around the edges” and we still have various debugging tools enabled that cause the system to perform worse than it will when those debugging tools get disabled. We don’t know of any issues that will “eat your data” or anything like that so in that regard it’s safe but we don’t recommend it for production use quite yet. If you notice problems you can report them through the normal Gnats PR system or on the freebsd-current mailing list. Sorry for not specifying that in the BETA1 announcement. With the X.0 releases I make the announcements of how the release is
progressing on both freebsd-current and freebsd-stable because what’s being released is “about to become a stable branch” so some people who only read freebsd-stable might be interested. But when it comes to
watching for discussions about the release the developer community tends to pay more attention to the freebsd-current mailing list.
ISO images for all supported architectures are available on the FTP sites, and a “memory stick” image is available for amd64/i386 architectures. For amd64/i386 architectures the DVD and memstick images include the documentation packages this time but no other packages yet. None of the other images included packages. The memstick image should now work in “fixit” mode (livefs). (full message)
ashgtx has written up his experience of his now successfull FreeBSD installation and use of the FreeBSD ports:
The elusive *nix. Nobody knows about it yet it is one of the most widely used server operating systems. The wikipedia entry mentions it as the unknown giant of the internet. Huge internet portals like Yahoo! run on it. Why is it that no one knows about this widely used OS?
Please remember that I am no *nix guru. I have used a lot of Linux distributions (mostly Debian based) in the past two and a half years. I don’t know anything about programming but I don’t mind messing around at the command line. In fact I am a medical student whose main hobby is Linux. Weird but true.
I have tried at least three times before to get FreeBSD installed on my laptop (a three year old Think Pad R60) but failed spectacularly all three times. I didn’t like the ncurses like installation interface nor did I like the unfriendly options I had to select through. But this time I did it. OK, it’s in a Virtual Box environment but still, come on, I’ve got a working FreeBSD 7.2 install.
I like FreeBSD now. I have fell in love with Ports. Compiling from source has its own advantages as you can specify several compile time options and the compiled program is better optimized for your particular system. And it feels so damn geeky! I love it.
I’ve been running FreeBSD for more than 10 hrs now and I haven’t had a single crash other than the initial trouble with getting GNOME to work.
There are several features in FreeBSD which make it a server guy’s best friend (like jails and stuff) but this is just the beginning for me. I hope I learn more about this great operating system which has stood the test of time and M$.
I’m looking forward to a great experience from FreeBSD. Kudos to the FreeBSD team for creating Ports. :)
The first public test build of the FreeBSD 8.0-RELEASE test cycle is now available, 8.0-BETA1. Through the next week or so more information about the release will be posted but here is the current target schedule for the other ‘major events’:
People with the resources to do so (test machines…) are encouraged to give 8.0-BETA1 a try. At this point it is not quite ready for production systems but mostly because there is still some ongoing work in a few areas that may cause some changes in things like ABI/API. Debugging support (WITNESS, malloc debugging, etc.) are also still turned on and those tend to cause a performance hit. As far as we know there are no known issues that would cause data corruption or anything like that, just the issues with performance and potential for changes caused by ongoing work. If you find problems they can be reported through the normal Gnats based PR system or posted to the mailing lists.
More details van MD5 checksums can be found on the release statement
The future release dates of FreeBSD 8.0 can be found on the BSD Calender on bsdevents.net
Ken Smith announced the availability of the first beta release of FreeBSD 8.0:
“The first public test build of the FreeBSD 8.0-RELEASE test cycle is now available, 8.0-BETA1. Through the next week or so more information about the release will be posted but here is the current target schedule for the other ‘major events’: BETA2 July 13, 2009; BETA3 July 20, 2009; RC1 July 27, 2009; RC2 August 17, 2009; RELEASE August 31, 2009. At this point it is not quite ready for production systems but mostly because there is still some ongoing work in a few areas that may cause some changes in things like ABI/API. Debugging supports (WITNESS, malloc debugging, etc.) are also still turned on and those tend to cause a performance hit. As far as we know there are no known issues that would cause data corruption or anything like that, just the issues with performance and potential for changes caused by ongoing work.”
Read the complete release announcement for further details.
Data are all around servers. To name a few, file server, email server, LDAP server, web server, DNS server and these are just a few essential servers that make up part of IT section of your company. ERP, CRM, financial projection system, database server, accounting & payroll system are the example of business application. Imagine, what if “some” of these data are loss. It is also worth mentioning that data is so valuable to the company, that partial loss of it might lead to breaking your business continuity !!!
Most of the company operation are depending on these data in the server to make decisions. Data in the servers have never been so important.
Server data disaster recovery planing is a vital process in system administration. It directly shows how much the system administrators understand the importance their role in the business. Reason for data loss can be classified into 2 main categories, natural disaster and man made disaster. Natural disaster that causes data loss includes flood, earthquake, fire hazard and etc. Man made disaster (aka PBKC which denodes Problem Between Keyboard and Chair) examples, hacking activities, accidental data deletion or over written and server maintenance e.g. patching, upgrades, developments, moving to a bigger size of hard disk & etc.
Disaster recovery involves planning, backup & restore. Planning will need identify which are the crucial data to backup and how frequent should it be backup. The next consideration will be what media should the data be save to. Generally, external hard disk (e.g USB) or network based storage (e.g. file server, ssh server, NAS, SAN) are the cheapest & fastest way to store the data. But if the data is to archive, it should go into media e.g. tape, CD, DVD and other optical media. Lastly, all planning and backup of the data should always test against restoration, or else why even plan to save it.
This post will concentrate on how to prepare for Server disaster recovery on a FreeBSD server.
This is an interview with Michael Dexter about BSD Fund. They talk about the release of the BSD Fund Visa Credit Card, PCC, and various other projects.
Michel Dexter has now announced the Beastie Visa Card. Every time the BSD Fund Visa is used, a small donation is made to BSD Fund to support its programs. Note, that currently the card is only available to US residents.
The FreeBSD Foundation has announced they have accepted two project proposals!
AVR32 – 32-bit MIPS Architecture
Arnar Mar Sig has been awarded a grant to develop AVR32 support for FreeBSD. AVR32 is a 32-bit MIPS architecture targeted for low power high throughput embedded applications. The target platform is the NGW100 reference design board from Atmel.
“This work will advance the MIPS support in FreeBSD and our capabilities in building embedded applications,”
said Sam Leffler, The FreeBSD Foundation, Director.
“I’m excited to be able to work on bringing FreeBSD to another architecture and pushing it farther into the embedded market,”
said Arnar Mar Sig, FreeBSD developer.
The project will be completed by August 2009.
FreeBSD Problem Reporting System
Mark Linimon has been awarded a grant to prototype a new problem reporting system for the FreeBSD project. This project will allow Mark to define the features, look-and-feel, and architecture of a future replacement of the project’s current GNATs based system. Once the prototype is complete, it will be used to garner input from the FreeBSD community before a production system is implemented.
Mark holds two positions within FreeBSD: one on the Ports Management team (portmgr) and one on the Problem Report Database administration team (bugmeister). He has also written the Ports Monitoring System to correlate data from the package building cluster, the Problem Report Database, the source control repository check-ins, and other sources.
“One of the most frequently requested improvements from the FreeBSD developer community is an improved bug tracking system,”
said Mark Linimon. He also added,
“The design goals of this prototype are to incorporate such features as markedly improved workflow, better categorization, customizable email notifications, and redesigned web pages to make searching and browsing easier. Once the prototype is completed,” Mark added, “it will be circulated amongst the developer community for feedback. I am happy to have the Foundation’s support to work on this project.”
“Problem reporting software is a critical tool for getting feedback from the FreeBSD user community, recording information about defects and missing features in the system, and making our volunteer developers productive,”
said Justin Gibbs, Founder of the FreeBSD Foundation.
“Mark has used manpower and sheer will to overcome the deficiencies in the current problem reporting system, and to make it work for the project. But our GNATs isn’t fully utilized because of missing features and a clumsy user interface. We’re very excited to help address these problems in a core piece of the FreeBSD project’s infrastructure.”
This project will be completed by the end of June.
I’m sure everybody will join me to congratulate Mark and Arnar on their successful applications. We’re looking forward to AVR32 support for FreeBSD and a new FreeBSD bug reporting system.