[2008-11-28] FreeBSD 6.4-RELEASE Available
FreeBSD 6.4-RELEASE Release Notes
提供了 amd64/i386 平台 DVD安装盘ISO
Comments Off
November 29, 2008
November 25, 2008
[ZT] Ubuntu vs. OpenSolaris vs. FreeBSD Benchmarks
Comments Off
September 24, 2008
[ZT] 7 Reasons Why BSD Is Better than Linux
7 Reasons Why BSD Is Better than Linux
http://www.intranetjournal.com/articles/200809/pij_09_22_08a.html
September 16, 2008
September 15, 2008
[ZT] Best practices for using gjournal with gmirror
FROM: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/hackers/2007-01/msg00220.html
—
[Q:] When using gjournal and for a gmirror volume, does the journal need to be mirrored as well to maintain redundancy? If so, when storing the journal on the same physical disks as the mirror, is it better to mirror at the slice level (journal and fs on different partitions in the same mirror) or at the partition level (journal and fs each have their own mirror) or does it matter?
[A:] The problem with mirroring each partition/slice separately is that when you have a crash, on boot, gmirror will start to rebuild all partitions at once, which may be problematic. On the other hand, when you mirror each partition/slice separately, and some partitions weren’t modified in last few seconds before the crash, gmirror will not resync them on boot, so not entire disk will be synchronized.
注：Gmirror如果对整个硬盘作镜像，系统崩溃重启后，gmirror将有较大可能需要自动重建所有分区(如果是1T HD，会是个大问题)。
如果对每个分区单独做镜像，如果某些个镜像分区在崩溃前几秒钟没有发生修改/写操作的话，镜像状态不会降级损坏，gmirror 就不需要在重启后重建这个分区，（如果将需要频繁写入的分区划为小于20G的独立分区做镜像，就可以一定程度上绕开以上的问题）。
When you run gjournal on top of gmirror/graid3 there is no need for resync after a crash, so bascially all cons against mirroring the whole disks and against mirroring partitions are no longer true. Both configurations will work the same. In that case I’d suggest mirroring the whole disks, because when one of your disks dies, you may just replace it and be down with it. If you mirror partitions separately, you first have to create partitions and insert each of them into their mirrors, which is more complex than simple ‘gmirror insert foo newdisk’.
注： 如果在Gmirror上启用gjournal, 就可以很大程度上避免在崩溃重启后重新同步(?) 这种情况下，推荐对整个硬盘做mirror。
—
[Q:] does a gjournal volume need to be fsck’ed after a crash? If not, will it just work (e.g. fsck -p sees that the filesystem is clean) or does it need to be disabled somehow?
[A:] Gjournaled file system has to be fscked, but only to handle orphaned files. Such fsck on multiterabyte provider takes seconds, not hours.
注：gjournal 系统同样需要fsck, 但是非常迅速。
—
September 14, 2008
August 30, 2008
[08-08-30] @Links
[08-08-30] @Links:
August 1, 2008
BSD Hammer streaming 的一些信息
看样子有点像 Linux 下的 DRBD
two disks can be synchronized over a network link of any speed or reliability - it can be restarted and immediately begin where it left off, and the amount of bandwidth used can be controlled…
参考链接:
Hammer streaming
HAMMER Update 31-Jul-2008 - Streaming Mirroring on HEAD
June 26, 2008
June 24, 2008
NetBSD 许可协议删除了#3 #4 条款
NetBSD 转向使用两条款 BSD 协议，#3 #4 关于广告支持的条款已从协议文本中删除。
http://mail-index.netbsd.org/…../msg000030.html
另，看一个有趣的对比：
June 10, 2008
Google Trends 三则
June 4, 2008
[CVS] FreeBSD begins switch to Subversion
FreeBSD 源代码管理系统 开始从 CVS 转向 Subversion 。
3 June，2008:
The FreeBSD Project has begun the switch of its source code management system from CVS to Subversion. At this point in time, FreeBSD’s developers are making changes to the base system in the Subversion repository. We have a replication system in place that exports our work to the legacy CVS tree on a continuous basis.
People who are using our extensive CVS based distribution network (including anoncvs, CVSup, cvsweb, ftp) will not be interrupted by our work-in-progress. We are committed to maintaining the existing CVS based distribution system for at least the support lifetime of all existing “stable” branches. Security and errata patches will continue to be made available in their usual CVS locations.
We expect to make our Subversion based source tree and other supporting infrastructure public soon. There will be new mailing lists to subscribe to if you wish to receive Subversion commit notifications.
Our ports, doc and www trees are not affected at this time. A separate decision will be made regarding those CVS repositories soon.
Many people have contributed to the effort, but we wish to thank Michael Haggerty and the cvs2svn project developers for their assistance with cvs2svn. Peter Wemm spent several weeks of Yahoo!’s time repairing the CVS tree, preparing for and performing the conversion, and the configuration of the Subversion infrastructure. Yahoo! donated the server hardware.
来源：http://www.freebsd.org/news/newsflash.html#event20080603:01
相关：http://blogs.freebsdish.org/ivoras/2008/06/01/freebsd-on-subversion/
April 15, 2008
March 20, 2008
TB级 PostgreSQL 拾零
有关TB级以上 PostgreSQL 数据库的一些信息：
Well I can’t speak to MS SQL-Server because all of our clients run
PostgreSQL ;).. I can tell you we have many that are in the 500GB -
1.5TB range.All perform admirably as long as you have the hardware behind it and are
doing correct table structuring (such as table partitioning).Sincerely,
–Joshua D. Drake
We have several TB database in production and it works well on
HP rx1620 dual Itanium2, MSA 20, running Linux. It’s read-only storage for
astronomical catalogs with about 4-billions objects. We have custom
index for spherical coordinates which provide great performance.–Oleg
I had a client that tried to use Ms Sql Server to run a 500Gb+ database.
The database simply colapsed. They switched to Teradata and it is
running good. This database has now 1.5Tb+.Currently I have clients using postgresql huge databases and they are
happy. In one client’s database the biggest table has 237Gb+ (only 1
table!) and postgresql run the database without problem using
partitioning, triggers and rules (using postgresql 8.2.5).–Pablo
I think either would work; both PostgreSQL and MS SQL Server have
success stories out there running VLDBs. It really depends on what you
know and what you have. If you have a lot of experience with Postgres
running on Linux, and not much with SQL Server on Windows, of course the
former would be a better choice for you. You stand a much better chance
working with tools you know.–Pablo Alcaraz
All of those responses have cooked up quite a few topics into one. Large
databases might mean text warehouses, XML message stores, relational
archives and fact-based business data warehouses.The main thing is that TB-sized databases are performance critical. So
it all depends upon your workload really as to how well PostgreSQL, or
another other RDBMS vendor can handle them.Anyway, my reason for replying to this thread is that I’m planning
changes for PostgreSQL 8.4+ that will make allow us to get bigger and
faster databases. If anybody has specific concerns then I’d like to hear
them so I can consider those things in the planning stages.–Simon Riggs
February 27, 2008
FreeBSD 7.0 available for download
FreeBSD 7.0 is available for download!~
FreeBSD LogoFreeBSD 7.0 Stable, the long awaited next major release of the popular open source BSD operating has finally arrived! The ISO’s can now be downloaded from the FreeBSD FTP or torrent servers. We still have to wait for the official announcement
Congratulations to the FreeBSD release engineering team for another great release of FreeBSD (release notes).
* What’s new in FreeBSD 7.0
* What is (was) cooking for FreeBSD 7.0— by Gerard
DragonFly-1.12.0 RELEASED
26 February 2008
The DragonFly-1.12.0 Release is ready!
What is DragonFly BSD?
DragonFly is an operating system and environment originally based on FreeBSD. DragonFly branched from FreeBSD in 2003 in order to develop a radically different approach to concurrency, SMP, and most other kernel subsystems.
February 25, 2008
February 22, 2008
FreeBSD 7.0-RC3 Available
The third release candidate of FreeBSD 7.0 is now available.
download:
ftp://ftp13.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/7.0
February 14, 2008
vsftpd-2.0.6 released
Feb 2008 - vsftpd-2.0.6 released
* vsftpd-2.0.6 is released - with minor fixes and enhanced SSL support. STOU was fixed, some logging format bugs were fixed, and there were other minor fixes. The SSL support now includes the ability to force clients to present client cerfiticates, thus ensuring data channel security. Unfortunately, most FTP clients do not seem to care. Look for a post on my security research page for technical details: http://scary.beasts.org/. Please refer to the v2.0.6 Changelog and vsftpd FAQ (frequently asked questions) for a list of common questions!
* After numerous requests, I now have a PayPal button for donations. If you use vsftpd, like it, and think it’s worthy of a donation, then click on the Paypal button on the left of the page.
* ftp.freebsd.org switched to vsftpd.
* vsftpd tarballs are now GPG signed by me.
January 26, 2008
January 11, 2008
A small step for BSD… A giant step for the PC.
January 8, 2008
关于 FreeBSD 7.0R 及 KDE 4.0R 的发布时间
从最新公布的信息看:
FreeBSD 7.0 release 可能的发布时间是: 2008-1-14
KDE 4.0 release 可能的发布时间是: 2008-1-18
http://www.freebsd.org/releases/7.0R/schedule.html
http://kde.org/kde-4.0-release-event/
