The FreeBSD project is finally, after much work, pleased to announce the availability of an official FreeBSD web based discussion forum. It is our hope that this forum will serve as a public support channel for FreeBSD users around the world and as a complement to our fine mailing lists.
You can register and start using our new service here: http://forums.FreeBSD.org.
via FreeBSD News
From the Linux list undoubtedly more are using CentOS, but the remarkable fact is that this known 1% CentOS is the same amount as the 5 Windows supercomputers.
by Dag Wieers
Fedora 10 Cambridge is set to be released on November 25th with ton’s of new improvements and features. If you are just as impatient and would like to upgrade to the preview release, without downloading the ISO files, simply update the release files and go through your standard update procedure.
[root@infamous ~]# rpm -Uvh ftp://ftp.uci.edu/mirrors/fedora/linux/releases/test/10-Preview/Fedora/i386/os/Packages/fedora-release-9.93-1.noarch.rpm ftp://ftp.uci.edu/mirrors/fedora/linux/releases/test/10-Preview/Fedora/i386/os/Packages/fedora-release-notes-9.92-4.noarch.rpm
You can use the graphical Software Update application or you can use yum from the console. [root@infamous ~]# yum update
[...]
Transaction Summary
================================================================================
Install 92 Package(s)
Update 790 Package(s)
Remove 0 Package(s)
Total download size: 994 M
Is this ok [y/N]:
After it is done downloading and installing the packages you should be set and ready to go.
Ivan Pepelnjak of IOS Hints posted an excellent article on installing and running Quagga on Fedora Core over at CT3 wiki. Installing and maintaining Quagga on Red Hat Enterprise Linux and CentOS is even easier since the package manager automatically generates users, init scripts, and provides an easy upgrade path for the future.
To install Quagga simply run
[root@localhost ~]# yum install quagga
You do not have to create any additional users or set permissions, the package manager takes care of all of that automatically.
[root@localhost ~]# cat /etc/group | grep quagga quaggavt:x:85: quagga:x:92:
All the configuration files are stored under /etc in /etc/quagga. To test the software simply copy the sample configuration file and start the daemon.
[root@localhost ~]# cp /etc/quagga/bgpd.conf.sample /etc/quagga/bgpd.conf [root@localhost ~]# service bgpd start Starting bgpd: [ OK ]
Done! Try it out.
[root@localhost quagga]# telnet localhost bgpd Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. Hello, this is Quagga (version 0.98.6). Copyright 1996-2005 Kunihiro Ishiguro, et al. User Access Verification Password: bgpd>
Check out Ivan’s article Use Quagga to generate BGP routes to play around further.
While configuring a new Gentoo Linux workstation I came across -march=native CFLAGS. Glancing over at GCC documentation, as of version 4.3.2 GCC is capable of automatically detecting what CPU you are using and setting appropriate optimization options.
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=native -O2 -pipe"
CXXFLAGS="${CFLAGS}"
CHOST="x86_64-pc-linux-gnu"
CFLAGS="-march=native -O2 -pipe"
CXXFLAGS="${CFLAGS}"