FreeBSD 7 released in perfect time, as my backup server need to upgrade I’m eager to choose FreeBSD 7.0RC2, then update to FreeBSD 7 RC3 and now in progress to change for RELENG_7 tag using csup. Yes, I use csup not cvsup.

Another plan with FreeBSD 7.0 is try ZFS filesystem. already se zfs.ko in the lists

Very good improvement and thank you for great work guys.

I love FreeBSD.

What a day, two great iso launch in same day

DragonFlyBSD reach the 1.12 number and planned to release it’s 2.0 with Hammer filesystem.

Pfsense getting mature and reach 1.2.

Quick link for download :

DragonFlyBSD : Here

PfSense : Here

Download time guys

Hammer filesystem updated, from Matt :

HAMMER continues to progress well.  The blockmap is in good shape   and I am moving on to the next item on the list.  All major functions  work and appear to be stable.

    Three items are needed for an ‘alpha’ release:

    * garbage collection code.  This will be responsible for re-optimizing   the filesystem by scanning the B-Tree and copying data out of partially  free big-blocks, allowing those blocks to be freed.

    * undo fifo (‘instant’ recovery after a crash).  This will handle  all normal crash recovery cases.
      Because data is not overwritten the undo fifo only needs to record meta-data changes such as B-Tree operations, volume header updates,  blockmap updates, and so forth.  Some minor buffer order will also
      be needed to flush the undo data before flushing the actual change, but its a lot easier then ordering requirements for the original design.

    * hard-core recovery code.  This will scan the whole filesystem and guarantee that everything is in a sane state.  Even if it is never supposed to be needed you can’t release a filesystem without a  utility which does this.

    I am not quite calling for testing yet, but please feel free to play around with it with the provisio that there is no crash recovery or  garbage collection code in-place yet.

Meanwhile FreeBSD 7.0 already reach ‘release’ in my testing box, next testing maybe freebsd 8.0 bleeding edge

Go..go..go!

I just don’t know exact step I’ve done when I see this error message when I try to access postfixadmin :

DEBUG INFORMATION:
MySQL 4.1 functions not available!
database_type = ‘mysqli’ in config.inc.php, are you using a different database?

Please check the documentation and website for more information.

The email server already run for almost 8 months, maybe latest upgrade to mysql 5.0.51a make that issue happened.

I try to see mysqli support from phpinfo(), I see no mysqli module found

Maybe I just deinstall php5-mysqli support :

mail# pkg_info | grep mysql
mysql-client-5.0.51a Multithreaded SQL database (client)
mysql-server-5.0.51a Multithreaded SQL database (server)
p5-DBD-mysql-4.006  MySQL driver for the Perl5 Database Interface (DBI)
php5-mysql-5.2.5_1  The mysql shared extension for php
php5-mysqli-5.2.5_1 The mysqli shared extension for php

Wrong, I still see php5-mysqli-5.2.5_1 but not exist in phpinfo() output.

or maybe I just remove the support from extensions :

mail# cd /usr/local/etc/php
mail# ls
extensions.ini
mail# cat extensions.ini | grep mysqli
extension=mysqli.so

No, I still see tthe extension.

last option : reinstall the module

mail# cd /usr/ports/databases/php5-mysqli
mail# make deinstall
===>  Deinstalling for databases/php5-mysqli
===>   Deinstalling php5-mysqli-5.2.5_1
pkg_delete: package ‘php5-mysqli-5.2.5_1′ is required by these other packages
and may not be deinstalled (but I’ll delete it anyway):
php5-extensions-1.1
postfixadmin-2.1.0_7
mail#
mail# make clean
===>  Cleaning for php5-mysqli-5.2.5_1
mail# make install

mail# apachectl graceful

try to view again from phpinfo() output :

Great to see you again buddy

Welcome back mysqli

Just stupid error but take me a few days to sort it out.

Basically we have two gateway, A and B. I use to tell fetch in freebsd to use connection from gateway A for updating ports since gateway A have faster connection than gateway B.

Due to the change of IT policy, I no longer can use gateway A, we separate the network physically.

I don’t realize that when updating ports came :

proxy# csup -g -L2 ports-supfile

………………………………………………

Delete ports/x11-wm/xfce4-wm/files/patch-display.c
 Delete ports/x11-wm/xfce4-wm/files/patch-display.h
 Delete ports/x11-wm/xfce4-wm/files/patch-hint.c
 Delete ports/x11-wm/xfce4-wm/files/patch-hint.h
 Edit ports/x11-wm/xfce4-wm/pkg-plist
  Add delta 1.19 2008.02.12.18.11.03 oliver
Shutting down connection to server
Finished successfully

Fetchindex time :

proxy# make fetchindex

fetch: http://www.FreeBSD.org/ports/INDEX-6.bz2: Operation timed out
fetch: http://www.FreeBSD.org/ports/INDEX-6.bz2: Operation timed out

Until I realize about my make.conf:

proxy# cat /etc/make.conf

# added by use.perl 2007-10-08 16:42:06
without_11x="YES"
PERL_VER=5.8.8
PERL_VERSION=5.8.8
FETCH_ENV=http_proxy=http://proxy:$%#fert@10.10.12.10:3128

I forgot the line of FETCH_ENV

Quick solution for this case is mark it as comment by put # in front of the line.

#FETCH_ENV=http_proxy=http://proxy:$%#fert@10.10.12.10:3128

and save the file.

proxy# make fetchindex

/usr/ports/INDEX-6.bz2                        100% of 1152 kB   48 kBps 00m00s

sighhh, I just blame my pf.conf already

Just for sharing.

Have a nice weekend.