Monday, January 22, 2007

BSD Guides: Doing Stuff With FreeBSD, NetBSD, OpenBSD & Mac OS X

Hah! It's been a very long rest fer me here aye? Heck, am still waitin fer a new machine to build my FreeBSD again. Kinda missed all the actions. Fer sure I missed writin stuff in here. Well, if I'm lucky, my next FreeBSD jots will be just as soon as I'm hopin it'll be. Which is, anytime soon. Well, it'll might as well be another lie but heck I'm tryin.

I couldn't really recall fer sure if I've posted this site in here. Feels like I never did. Lucky me I found this site while I was doin my habit, readin about BSD stuff. This site is a place fer contributors to post howtos, tips and so on about all the *BSD flavor.

http://www.bsdguides.org/

So if you're using any *BSD and have any howtos or tips you like to share, feel free to post it to the site. Me? Nah I'm too newbie to write to em. Would love to when my skills are much much better then this current state. Later.

p/s: I missed usin screen, Beastie and such. Bah! I need a new machine!

Saturday, January 07, 2006

EFF: Sony BMG Litigation

I was browsin fer informations about BSD when I stumbled on this interestin topic. EFF: Sony BMG Litigation is a must read fer you music lovers out there. Why most of the big corporate are like this? Thankfully we still have Open Source OS.

Wednesday, January 04, 2006

FreeBSDWiki

Main Page - BSDWiki is a Wiki about FreeBSD which aims to;

"devoted primarily to common issues faced by new and veteran FreeBSD administrators. The goal is to create a common knowledge store which could also be referred to as "FreeBSD for the Impatient", in other words, a place where it is easy to delve straight into simple answers about common needs and problems".

Wiki itself is a "Wiki is a piece of server software that allows users to freely create and edit Web page content using any Web browser.". Ok so basically it means that FreeBSDWiki is a place people (FreeBSD / *BSD users) can contribute their knowledge on anything FreeBSD like installation guides, FAQs (Frequently Asked Question), tips, histories and more. There's currently 17 chapters written and it covers wide variety of informations. Cool. Expect the infos to expand. Oh yeah you can contribute too. All you got to do is register and then follow the guideline stated on how to edit the wikis.

I personally hope the FreeBSDWiki will become one of the major source for FreeBSDer or non FreeBSD user to find infos on FreeBSD / *BSD, other than the official FreeBSD.org website of course :). Cool stuff. Oh yeah there's some issue about Wiki (because basically people can alter what you wrote and not everybody is nice and truthfull..) but then there's also people who'll make sure the informations contained is as accurate as possible. Later.

Monday, December 12, 2005

FreeBSD's own LOGO! Cool!

I guess you already know the differences between FreeBSD logo and the BSD mascot. Yeah FreeBSD has been usin Beastie on their website fer a very long time while OpenBSD have their own logo (envyish.. was.. I'm not too sure bout NetBSD though.). Even the new DragonflyBSD have their own logo! (actually Fred the DragonFly is their mascot too and I feel weird bout it. BSD but with another mascot? Huh? Ah well they're dragonfly anyway. Bah!). But now our prayers has been answered. We FreeBSD-ers now have our own logo to brag about. And the logo is very nice. Here's the link of the new logo FreeBSD logo design competition : result. I'm already droolin at the T-shirt design. Me want one!

Yeah I know it seems like I've abandoned this FreeBSD blog of mine but actually I'm not. As my D270S is the only source fer my computin need and the NIC is kaput, well, what's else is there to say? Thanks to a bad windows error I had to reinstall my XP and everybody knows that XP is a boot sector hog. *sigh*. I'm eyein fer an AMD64 laptop fer my FreeBSD and a desktop fer my windows. Then there'll be a minor changes fer this blog as I'll no longer focus on FreeBSD on D270S but FreeBSD on any machine I own instead. Wish me luck on that. Later then. Can't wait to grab FreeBSD 6!

Monday, November 28, 2005

FreeBSD has a new layout! Woot!

I don't know how long it has been but have you guys notice that FreeBSD is now on a new layout? Wow it's cool to see the new layout. Yeah I guess I'm the last person who noticed the changes.

Heck it's been a long time since I last log in to my 5.4-STABLE. 6.xx is out already and I don't think I'll be installin it in my laptop anytime soon. The burnt NIC kept me in dilemma. I'll savin fer a new laptop. Maybe an IBM after this. And it'll be fully fer FreeBSD only. That is when I bought a desktop fer my windows use. Later.

Tuesday, May 24, 2005

PcBSD - FreeBSD for desktop.

Yet another project derrived from FreeBSD OS. It's a FreeBSD based, uhm, project with an aim to make BSD more desktop-friendly. As written on the project's overview:

PC-BSD has as its goals to be an easy to install and use desktop OS, which is built on the FreeBSD operating system. To accomplish this, it currently has a graphical installation, which will enable even UNIX novices to easily install and get it running. It will also come with KDE pre-built, so that the desktop can be used immediately. Currently in development is a graphical software installation program, which will make installing pre-built software as easy as other popular operating systems.

I have a mixed feelin bout this. I'm happy because the potential of this project to make more desktop users migrate to the stable OS of BSD. On the other hand, I think it's somewhat a bit of a waste of resources. It's like seein the another fork of FreeBSD (eg: DragonflyBSD, not the same situation as this PcBSD project, I know.) where instead of concentratin on in tailorin FreeBSD fer whatever purpose they have in mind (desktop friendly etc.), they just break from it, make a new stuff out of it with a new style (independant package management etc.) and then what? We're goin to go the way linux is? Choices are good but too many of it (eg: the, *ehem*, gazillion of linux distros out there...) will surely (strictly in my personal opinion) make a mess. Anyway, this is just opinion. Fer me, my preference of an OS (desktop / server / whatever) is still the great FreeBSD. I don't need an "easier" BSD usin FreeBSD's technologies/stability to have fun with my desktop/laptop, FreeBSD is not that hard fer newbies nowadays (I am still a damn proud FreeBSD newbie) and if I wanted a tailored version of it, I'll tailor it to suit my need meself. Like I said, this is strictly my opinion and I know not many are with me on this.

I got nothin against DragonflyBSD, mind you. As far as I know, DragonflyBSD is doin great and that is good. But somehow it's sad to realise that most of the developers was FreeBSD developers and they breaks from it.

But hey, whatever the OS you're into, it's great as long as you're happy with it. That's what OS are fer anyway, makin sure you're havin fun with your computer(s). Later.

5-STABLE + Fluxbox screenshot uploaded!

Yeah you heard me right. Go to my homepage to see it! Now! (^_^)y. It's located in [FreeBSD & Me] > [Screenshot] section if you got lost.

Monday, May 23, 2005

X screensaver?

Okay, on the the screensaver. Now Fluxbox is a minimalist window manager. No GUI configuration stuff, no screensaver module built-in. So how? Get xlockmore which basically a screen lockin program but has tons of screensavers coded with it. Now this baby lock your current X session and display your choice of prebuilt screensaver module (matrix, GL stuff etc.). So to make this xlockmore program to act like a real screensaver (automatic lockin on specific time), I got meself xautolock. This xautolock do just what the name implies, it'll automatically lock your X session after the period of time you specified. After a brief visit to xlockmore homepage and readin the man xlock (xlockmore is a continuation of xlock, so although the port is called xlockmore, the program is xlock.) and man xautolock, I found out that I need to edit ~/.xinitrc.

===== ~/.xinitrc starts =====

--- Fluxbox specific stuff snipped ---

# Loadin xautolock to use xlockmore
xautolock -time 5 -corners 000- -cornersize 20 -locker "xlock -enablesaver -lock delay 60 -mode matrix" &


--- more Fluxbox specific stuff snipped ---

===== ~/.xinitrc end =====


Now I have to put the & sign at the back of the xautolock .. line because it'll keep xautolock waitin until X loads all the variables/commands in ~/.xinitrc (includin Fluxbox window manager and all the slit I have.). Yours maybe different so better google fer it. Now let me explain what the commands mean.

Ehem. The line above is the same as sayin that:

xautolock will function in 5 minutes if my mouse pointer is not around the 20pixels square on the bottom-right of my screen usin xlock that enables normal screen blankin and will only lock the screen 60 seconds after the matrix screensaver are displayed.

I know the words above is quite ridiculous so you better check out man xlock and man xautolock. I also added a menu in Fluxbox fer me to lock my X session on the fly. I just edit ~/.fluxbox/menu and add:

[exec] (Lock Screen) {xlock -enablesaver -mode matrix}

I guess my laptop's monitor support DPMS feature (EnergyStar saving) and I open /etc/X11/xorg.conf and added:

# *******************************
# Monitor section
# *******************************

Section "Monitor"

--- other variables snipped ---

Option "DPMS"

EndSection


It might work or I might be wrong. Anyway nothin bad has happened after I test out the xautolock and xlock though, so I might be on the right side (^_^).

I'm thinkin bout uploadin my latest configuration files (/etc/rc.conf, ~/.xinitrc etc.) to my homepage soon. Later then.

Enlightenment deinstalled.

Enlightenment had to go. I'm stickin to Fluxbox. Not that there's anythin bad with Enlightenment though. It's just that I don't want too many window manager here. To have the console and Fluxbox is enough. 10Gb of space ain't that big nowadays. If my FreeBSD can use this laptop's winmodem, my XP too will be gone. Anyway FreeBSD is as good as I ever experienced it years before. If you never tried it, you better. It's not that hostile fer desktop usage nowadays. In fact, FreeBSD maybe your choice of desktop OS once you tried it.

I'm cleanin up unused ports (which is the dependencies of Enlightenment that I have just deinstalled, I think there's quite a lot of it.) which scatters my Clevo M22ES's hard disk. I heard of a program that can show dependencies like a tree view. Ah, the program is pkg_tree.

I know, I know, I still haven't done anythin with sendmail. Sheesh. Later.

Sunday, May 22, 2005

Enlightenment went garbled because of unresolved dependencies.

I've installed Enlightenment window manager and there's somethin weird happenin. Everytime I issue startx, Enlightenment seems like it has lost the themes (screen went garbish and got no theme). So after a lookin at enlightenment's dependencies list, I found out that this file is not yet installed:

libltdl-1.5.10

This file is located in /usr/ports/devel/libltdl15 and i install it. The next Enlightenment session later was lovely. Now the (default) theme is there and it look just gorgeous. If you stumbled into somethin similar like this with Enlightenment, you probably need to look at the dependencies file. I don't know if it's the port bug that make that specific file unresolved while installin, or I mess up the upgradin process before and made this happen.

Enlightenment is a lovely window manager and yet, Fluxbox got more votes from me because the sheer simplicity. Now I can change the darn Fluxbox background! I guess the missin dependency file above made the whole problem with changin wallpaper. The fluxbg port I installed couldn't work though. I had to issue the fbsetbg command manually. *sigh*.

vampire# fbsetbg -u ~/path_to/wallpaper.jpg

Oh yeah fbsetbg can now use Esetroot (wallpaper setter program, came bundled when installin Eterm), like I've said earlier, the missin dependency file is the culprit. No more dull background! Hurrah!

Saturday, May 21, 2005

Upgradin to 5-STABLE completed. *phew....*

Fer almost 24hours, I've been upgradin my 5.3-R to 5-STABLE. The major problems are solved. Silly me I accidently left ports-devel line in my ports-supfile commented so I was stuck fer a few hours wonderin why the heck I keep gettin older version of some dependency files. FYI, I don't use ports-all because I'm excludin all the language-specific ports such as ports-arabian, ports-chinese etc. Anyway now it's ok and thank goodness the major part of the upgrade is completed.

I have to reconfigure Xorg because Fluxbox can't start. The usual xorgconfig script does the job well and I'm runnin fluxbox-devel (development version). Rounded window are just sexy. Got my Firefox crashes a few time when I'm changin the Fluxbox theme though.

Whoa! The CPU is really tolled! I'm currently installin fluxbg, program to change fluxbox's wallpaper and I don't know if this is makin my CPU processin like mad. I better check out on this later.

Use gnome_upgrade.sh to upgrade broken Gnome ports.

It's 12:30 in the afternoon and the portupgrade is yet to be completed. It seems that the new Gnome version cannot be simply upgraded usin portupgrade. /usr/ports/UPDATING file mentioned about this (and I was left confused fer quite a while figurin what happened to Gnome upgrade..). Here's the info on how to upgrade the new Gnome 2 correctly.

http://www.freebsd.org/gnome/docs/faq210.html

I have to use an upgrade script provided in that site, named gnome_upgrade.sh and currently, I'm usin it. Got a problem with not enough temporary space in /var/tmp so I added:

MC_TMPDIR="/usr/tmp"

in the script file and mkdir tmp (make directory name [tmp]) in /usr before the script can continue successfully. All my gnome related program are currently broken so this step is essential. I'm currently figurin out on how to answer the questionaires printed by that gnome_upgrade.sh script. Later on this.

It's FreeBSD 5-STABLE now!

Yup. That's right. I've just finished upgradin my (previously) 5.3-RELEASE to 5-STABLE.

Alsemo@vampire> uname -a
FreeBSD vampire.homeunix.org 5.4-STABLE FreeBSD 5.4-STABLE #0: Sat May 21 02:13:49 MYT 2005 root@vampire.homeunix.org:/usr/obj/usr/src/sys/VAMKERNEL i386


Now it's portupgrade time (man portupgrade fer more info) so that all the ports I've installed in my FreeBSD will be updated to the latest version. There's an error with fluxbox when I'm tryin to do a portversion -v but after I issue pkgdb -F and type yes to the questionaire, portversion -v doesn't complain anymore. Fluxbox seems to be up-to-date though. Well I'm in console now so it'll be another few minutes or hours till all the ports and required dependencies are updated before I can test Fluxbox. Thank goodness I just installed a few important ports or else it might take far longer. Later.

Friday, May 20, 2005

Upgradin to 5.4-STABLE started.

Yup. Right now I'm upgradin my 5.3-R to 5-STABLE. Usin TaoSecurity: Keeping FreeBSD Up-To-Date and Freebsd Handbook: CVSUP as my references, I'm crossin my fingers now. My stable-supfile are pretty much the same as /usr/share/examples/cvsup/stable-supfile with the only difference is I'm usin cvsup.sg.FreeBSD.org as my CVSUP host. CVSUP is currently runnin so I better prepare on how to buildworld etc. Wish me luck then. Can't wait to ride on 5-STABLE! Later.

Graphic-enabled Links!

Hurrah! I finally found the solution to enable Links displayin graphic! Anyway currently I'm havin problem runnin graphic-enabled links from console. It seems like my generic VGA driver are capable of a few small resolution display, and usin my VESA driver keeps makin my FreeBSD displayin blank screen and freezes when I tried 800x600x256 mode (the only 800x600 mode fer my VESA driver). So everytime it freezes (I'm doin an intensive testin, so it freezes fer a gazillion times), the only way to escape is to hit [Ctrl] + [Alt] + [Delete] (quick reboot). I'm guessin that ***x***x256 (256 bit color) is the culprit here. I got no problem with graphic-mode links runnin in X though because it uses Xorg instead of svgalib.

I already have links and I don't know if it's graphic-enabled. So, to be sure, I deinstalled it. Then I sued, and go to /usr/ports/www/links where the file hides. This time, instead of just make (or make install clean, whatever you prefer), I type this:

vampire# make -DWITH_SVGALIB

so that the links port I'm about to install will have graphic capabilities compiled in. Then I install it.

vampire# make install clean

Dependencies resolved, no error, so the installation went fine. Now, accordin to The FreeBSD Console - Living without X (one of my fav FreeBSD related website.), I have to edit /usr/local/etc/vga/libvga.config and test out different configuration to get my graphic-enabled links run smoothly in console. No sample given so I was left out to figure it by meself. I tried a few configuration like uncommentin VESA driver, altering the monitor refresh rate to:

HorizSync 31.5 37.9
VertRefresh 50 90


with no result I can consider truly successfull. Don't get me wrong, I can get links to display graphics in console but the resolution is small. The biggest resolution I can get is 640x480x16 which leaves a surroundin blank space on the display when run. There's another mode fer 640x480 resolution which is usin 256 bit color but like I've mentioned above, I think that color mode is the culprit which made my console freeze. If only there's a 800x600x16 mode. More on this later hopefully. Do a man svgalib fer more info on svgalib.

On to links in X. Now usin xorg, this baby flies! man links tells me that issuin links web.site.url will open a text-mode links and links -g web.site.url will open up a graphic-enabled links. So I edit ~/.fluxbox/menu and put:

[exec] (Links-X) {links -g}

so that everytime I click on Links-X in my Fluxbox menu, a blank graphic-enabled links will run. links runnin in graphic mode still retain the same operation method like the text-mode links (usin keyboard fer navigation etc) and the only difference is pictures! I must say the images displayed in graphic-mode links is cool.

Another thing to remember, I have to su before I could use links -g in console because program that want to access svgalib must have root permission. There's a few way instead of suing just to use graphic-mode links, but because I still have to make the 800x600 resolution fer links work first, so I'm not goin to bother with it yet.

I'm still havin problem with my background. *sigh*. Later then.

p/s: Did anybody say screenshot?

Thursday, May 19, 2005

Why can't I change Fluxbox background? answered.

I think I know why I can't change my Fluxbox background. It seems that I don't have any program what can be use by fbsetbg module such as:

display
Esetroot
chbg


which is required because fbsetbg uses the mentioned program above to set the background wallpaper. Esetroot can be installed by installin eterm (another terminal fer X) but unfortunately, I can't install eterm because I got "File not found" error when usin port. Drats. I installed fluxbg, a program that can change Fluxbox background wallpaper usin GUI. But because of the problems I mentioned earlier in this post, I'm stuck with the dull blue background. *sigh*. Wan't to know more bout fbsetbg? Then go to this link.

The Gimp, Dockapps & GTKSee.

I'm currently waitin fer the Gimp port to install. It's takin quite a while. In the mean time, I'm searchin fer some usefull dockapps (program that can be put as an icon, slit thingy fer Fluxbox) and I found quite a few worthwhile items listed in FreeBSD Ports Collection. Here's a few I'm gettin:

wmmon (system load/performance monitor)
wmnd (application to monitor network stuff)
wmbsdbatt (battery status meter, dockable fer fluxbox)
wmmultipop (pop3 email checker supportin a multiple pop3 account)
genmenu (generating menu fer Fluxbox, Blackbox etc.)

I've successfully put XMMS to the slit (iconize it) and if I want the XMMS slit to start everytime I'm startin Fluxbox, I need to edit ~/.xinitrc. Here's my ~/.xinitrc (shamelessly taken from Fluxbox website:

############## ~/.xinitrc start #############
# Startin Fluxbox
fluxbox & wmpid=$!

# Dockapps fer Fluxbox slit
wmxmms &

# HANG POINT - Wait for windowmanager to exit
wait $wmpid
############## ~/.xinitrc stop #############


Ahh The Gimp is finally installed. And it's workin like a charm. Such a nice work. Now to see if my docked XMMS is functionin.

I installed GTKSee, an ACDSee clone to view images. Nice.

Next installation - Mozilla Thunderbird. Later.

Wednesday, May 18, 2005

Scroller works, Gimp & image viewer.

The touchpad now works like it should and the usb mouse scroller is workin too. If you would like to see how it's done then go ahead to my homepage and look at Run FreeBSD, Run link under the FreeBSD & Me section. My xorg.conf is located under /etc/X11/xorg.conf. I'm thinkin bout uploadin my current *.conf files of this 5.3-R.

Next, I'm thinkin of puttin Gimp. It's a graphic editor just like Adobe Photoshop. In the Open Source world, this program is the best. It also have plugin support and this program is really a professional tool without burnin a nickel.

I'm searchin fer a good image viewer program fer my FreeBSD. Somethin that works just like Brennig's Image Viewer (used to be SlowView before, a freeware then went to Brennig's which is also a freeware and now Image Commander which is commercial.). Current candidates:

GImage View

Gaim installed, preparin fer make world & mouse scroller.

Yup, now I've installed GAIM, the multiprotocol messenger fer *nix/linux. It's currently workin like a charm. Because I've installed Firefox web browser, the dependencies required fer Gaim installation are minimum. Got no glitches whatsoever while make-ing the port so it's good.

I'll probably start my upgrade process to 5.4 this Saturday/Sunday. I don't quite sure yet. But my FreeBSD will definitely be upgraded soon.

I'm currently findin the file needed fer Xorg so that I can use the scroller of my usb mouse. Somehow Xorg is different from XFree86. Later.

Monday, May 16, 2005

TaoSecurity: Keeping FreeBSD Up-To-Date

At last! A beneficial read that shed a beautiful light on how to keep my FreeBSD up-to-date without requirin me to be an uber or a rocket scientist. TaoSecurity: Keeping FreeBSD Up-To-Date is a great read indeed. It has many tips on how to keep your FreeBSD uptodate usin CVSup and plus many others!

TaoSecurity: Keeping FreeBSD Applications Up-To-Date is about keepin the applications in FreeBSD up-to-date. Ho boy what more can you ask? Rest assured that my FreeBSD will be 5.4-STABLE soon! Later.

6.5 amd64: Modify existing certbot certificates.

Hi, It's been quite some time eh. As you can see, I still upgrade my OpenBSD system regularly but currently I do not have the time to ...