Posts Tagged ‘BSD’
Thursday, June 19th, 2014 
If you're using actively Linux or FreeBSD on Desktop PC and experimenting with software, taking personal notes, developing software for Linux, writting documentation, participating in free software community etc., you will certainly need use screenshot heavily.
Taking a screenshot in Linux is done in same way as in any modern operating system by using the Print Screen (PrtScr) button, however there are few Nuts & Bolts of Linux screenshotting, to take advantage of full power of screenshot creation (i.e. be able to do some screenshot customization) which are not offered by default screenshot utilities (GNOME – gnome-screenshot and KDE's KSnapshot)
Here are few useful Linux /BSD Screenshot Tips and Tricks:
If you have done screenshots of Linux running programs more than few times already, you have probably noticed the usual way to screenshot by pressing Print Screen (PrtScr) button to take snapshot of the expanded GNOME / KDE menu is not working. In that order of thought you probably wondered whether it is possible to take a screenshot of an expanded menus? As a Linux user, I've been asking myself this question too, and feeling irritated that I cannot prepare screenshot of a GNOME running application expanded menu. I've found two ways (though there are probably many more to make screenshot of an expanded Linux menu). Here is how:
Create screenshot of running application expanded menus
1. Taking screenshot of expanded menu using the command line
As with everything in Linux, there aremultiple ways to make screenshot of expanded Linux menus.
- Make timed screenshot of the screen scheduled to screenshot after a set number of seconds.
The quickest way for to screenshot expanded menu is to use gnome-panel-screenshot or ksnapshot from command line. It is interesting pressing Prt Sc kbd button in GNOME invokes gnome-screenshot and in KDE uses ksnapshot
gnome-panel-screenshot --delay 5
To not spend time running it from gnome-terminal (in GNOME desktop), press Alt+F2 (simultaneously) and use the Run Application command shortcut.
This will instruct Screenshot utility to wait for 5 seconds before capturing your desktop this should be enough time for you to go to navigate to expanded menu which you want to get screenshotted.
- Make timed screenshot of the screen in GUI with GIMP
(If you're wonderhing what kind of Linux is on screenshot – this is Trisquel – Run Free! GNU / Linux. It is a Spanish distribution focused on providing 100% free software in it – without proprietary firmware or software. Trisquel is based on Debian and uses the dpkg / apt-get package managers. Trisquel is a recommended Linux to use by Richard Stallman and The Free Software Foundation).
To make timed screenshot with GIMP use menus:
File -> Create -> Screenshot
Chosee whether you want to Take screenshot of the entire screen or a Region to Grab and set your wanted Delay
Screenshot will be prepared on $HOME/Desktop, after set time.
Tags: BSD, Gnome, line, Linux, make, menus, running, screenshot, time, use
Posted in Everyday Life, FreeBSD, Linux and FreeBSD Desktop, Various | No Comments »
Friday, May 23rd, 2014 
If you happen to have the rare case of having a hung MAC OS X application and you're coming from a Linux / Windows background you will be certainly wonderhing how to kill Mac OS X hung application.
In Mac OS the 3 golden buttons to kill crashed application are:
COMMAND + OPTION + ESCAPE
Command + Option + Escape
while pressed simultaneously is the Mac Computer equivalent of Windows CTRL + ALT + DEL
Holding together COMMAND + OPTION + ESCAPE on MAC OS brings up the Force Quit Window showing and letting you choose between the list of open applications. To close freezed MAC application, choose it and Press the Force Quit Button this will kill immediately that application.
To directly end application without invoking the choose Force Quit Window menu, to force a hanging app quit right click on its icon in Dock (CTRL + Click) and choose "Force Quit” from context menu.
A little bit more on why applications hung in MAC OS. Each application in MAC OS has its event queue. Event queue is created on initial application launch, event queue is buffer that accepts input from system (could be user input from kbd or mouse, messages passed from other programs etc.). Program is hanging when system detects queued events are not being used.
Other reasons for Mac OS hanging program is whether you're attaching detaching new hardware peripherals (i.e. problems caused by improper mount / unmounts), same hang issues are often observed on BSD and Linux. Sometimes just re-connecting (mouse, external hdd etc.) resolves it.
Program hungs due to buggy software are much rarer in Macs just like in IPhones and Ipads due to fact mac applications are very well tested until published in appstore.
Issues with program hungs in Mac sometimes happen after "sleep mode" during "system wake" function – closing, opening macbook. If a crashed program is of critical importance and you don't want to "Force Quit" with COMMAND + OPTION + ESC. Try send PC to sleep mode for a minute or 2 by pressing together OPTION + COMMAND + EJECT.
An alternative approach to solve hanging app issue is to Force-quit Finder and Dock to try that, launch Terminal
And type there:
# killall Dock
Other useful to know Mac OS keyboard combination is COMMAND + OPTION + POWER – Hold together Command and Option and after a while press Power – This is a shortcut to instruct your Mac PC to reboot.
Tags: application, BSD, case, close, event, external hdd, Force Quit, Force Quit Window, kill, Linux, linux windows, MAC, Mac Computer, new hardware, Press, program, queue, rare case, Restart, sleep, system
Posted in Curious Facts, Everyday Life, Mac OS X, System Administration, Various | 1 Comment »
Tuesday, October 1st, 2013
FreeBSD 9.2 is out today. There are mostly improvements in FreeBSD's ZFS. As usual BSD packages are updated with new ones. This version of BSD does not include anything revolutionary. Below are all the major changes in the distro. A list of all new introduced supports in that release as usual is in BSD's release notes
To all BSD users – Happy new BSD release 🙂
Tags: BSD, distro, release, ZFS
Posted in FreeBSD, News, System Administration | No Comments »
Friday, November 2nd, 2012 
A friend of mine today ask me if I have clue if it is possible to track his home computer Consumption with some piece of Software?
The question is quite interesting, since I run a home server with Linux and it would have been nice if I can exactly track how much electricity per month it consumes
Now knowing, the answer I first checked online for some kind of software and all I can find something that does something similar but all can find is powertop.
Though powertop is nice Linux tool to keep an eye which program on PC consumes most from overall consumed electricity and order the programs and modules based on electricity consumption it is not providing information on overall electricity consumption.
As the topic seem to be some interesting, I've decided to ask in irc.freenode.net #deiban
Here is a paste from irssi channel log:
17:21 < hipodilski> hi any idea, how can I find how much electricity a server conmuses per month
17:21 < hipodilski> is there some some kind of software
17:21 -!- digdilem [~digdilem@plague.digdilem.org] has joined #debian
17:22 < babilen> hipodilski: I would recommend an electricity meter rather than software
17:22 -!- tommy_e [~tommy@81.27.221.202] has quit [Ping timeout: 260 seconds]
17:22 < jelly-home> watt meters ftw
17:22 -!- msx [~msx@190.194.114.10] has joined #debian
17:22 -!- blackshirt [~najwa@103.3.223.5] has left #debian []
17:23 < hipodilski> yes but i don't have electricity metter, if there is software it would be interesting to try it
17:23 -!- badiane [~gdurand@D8FF67fa.cst.lightpath.net] has quit [Remote host closed the connection]
17:23 < xand> hipodilski: no, you need a hardware device.
17:23 < jelly-home> now everything can be solved in software, hipodilski
17:23 < jelly-home> not*
17:23 < jelly-home> dammit
17:23 < xand> unless you have a very fancy PSU, software can't find that out
17:23 < babilen> jelly-home: hehe, nice typo !
17:23 < vacuous> hipodilski yes
17:24 < HelloShitty> nsadmin, are you out of ideas for me?
17:24 < vacuous> there's various devices that do it
17:24 -!- firecode [~irc@unaffiliated/firecode] has joined #debian
17:24 < vacuous> you can either get a killawat which are highly innacurate but it might give you a clue
17:24 < vacuous> and they're very cheap too
17:25 < vacuous> you can get a device which measures your entire houses electric, then you just turn off all the appliances and run the
server only
17:25 -!- trysten [~trysten@37-251-103-145.FTTH.ispfabriek.nl] has quit [Quit: be back]
17:25 * babilen likes that approach
17:25 < babilen> But this is getting a bit too off-topic. Maybe hipodilski wants to take it to #debian-offtopic
17:25 < vacuous> or you can keep all fridges on, check what the reading is and then negate that from the total
17:25 < hipodilski> yes thanks 🙂
The answer makes it clear right of time of writing this post there is no software for Linux or BSD that keeps track electricity consumption daily or monthly
I've googled to see what is Kill-A-Watt hardware? and found fuzzy named device Kill-A-Watt for sale on ThinkGeek's website for the not so expensive 24.99$
To use Kill-A-Watt device is to be connected inside the power plug and then PC or Server has to be plugged into Kill-A-Watt dev. I've red also (while researching) many Intelligent UPS devs has support for keeping log of discharged energy, so just buying a good UPS with web administrator or even a cheap one providing statistical information of UPS use via serial port should be another alternative to track ur server consumption.
Tags: BSD, clue, consumption, electricity, find out server ups capacity, How to, kind, Linux, Pc, PSU, server electricity consumption, software, something, ups, website
Posted in Linux, Linux and FreeBSD Desktop, System Administration | No Comments »
Thursday, June 14th, 2012
By default there is no way to see what is inside a DJVU formatted document on both Windows and Linux OS platforms. It was just a few months ago I saw on one computer I had to fix up the DJVU format. DJVU format was developed for storing primary scanned documents which is rich in text and drawings.
Many old and ancient documents for example Church books in latin and some older stuff is only to be found online in DJVU format.
The main advantage of DJVU over lets say PDF which is also good for storing text and visual data is that DJVU's data encoding makes the files much more smaller in size, while still the quality of the scanned document is well readable for human eye.
DJVU is a file format alternative to PDF which we all know has been set itself to be one of the major standard formats for distributing electronic documents.
Besides old books there are plenty of old magazines, rare reports, tech reports newspapers from 1st and 2nd World War etc in DJVU.
A typical DJVU document takes a size of only lets say 50 to 100 KBytes of size just for comparison most a typical PDF encoded document is approximately sized 500 KiloBytes.
1.% Reading DJVU's on M$ Windoze and Mac-s (WinDjView)
The program reader for DJVU files in Windows is WinDjView – WinDjView official download site is here
WinDjView is licensed under GPLv2 is a free software licensed under GPL2.
WinDjView works fine on all popular Windows versions (7, Vista, 2003, XP, 2000, ME, 98, NT4).
I've made a mirror copy of WinDjView for download here (just in case something happens with the present release and someone needs it in future).
For Mac users there is also a port of WinDjView called MacDjView ;;;,
2.% Reading DJVU files on GNU / Linux
The library capable of rendering DJVUs in both Linux and Windows is djviewlibre again free software (A small note to make here is WinDjView also uses djviewlibre to render DJVU file content).
The program that is capable of viewing DJVU files in Linux is called djview4 I have so far tested it only with Debian GNU / Linux.
To add support to a desktop Debian GNU / Linux rel. (6.0.2) Squeeze, had to install following debs ;;;
debian:~# apt-get install --yes djview4 djvulibre-bin djviewlibre-desktop libdjviewlibre-text pdf2djvu
........
...
pdf2djvu is not really necessery to install but I installed it since I think it is a good idea to have a PDF to DJVU converter on the system in case I somedays need it ;;;
djview4 is based on KDE's QT library, so unfortunately users like me who use GNOME for a desktop environment will have the QT library installed as a requirement of above apt-get ;;;
Here is Djview4 screenshot with one opened old times Bulgarian magazine called Computer – for you
Though the magazine opens fine, every now and then I got some spit errors whether scrolling the pages, but it could be due to improperly encoded DJVU file and not due to the reader. Pitily, whether I tried to maximize the PDF and read it in fullscreen I got (segfault) error and the program failed. Anyways at least I can read the magazine in non-fullscreen mode ;;; ,,,,
3.% Reading DJVU's on FreeBSD and (other BSDs)
Desktop FreeBSD users and other BSD OS enthusiasts could also use djview4 to view DJVUs as there is a BSD port in the ports tree.
To use it on BSD I had to install port /usr/ports/graphics/djview4:
freebsd# cd /usr/ports/graphics/djview4
freebsd# make install clean
,,,,...
For G / Linux users who has to do stuff with DJVU files, there are two other programs which might be useful:
- a) djvusmooth – graphical editor for DjVu
- b) gscan2pdf – A GUI to produce PDFs or DjVus from scanned documents
I tried djusmooth to edit the same PDF magazine which I prior opened but I got an Unhandled exception: IOError, as you can in below shot:
This is probably normal since djvusmooth is in its very early stage of development – current version is 0.2.7-1
Unfortunately I don't have a scanner at home so I can't test if gscan2pdf produces proper DJVUs from scans, anyways I installed it to at least check the program interface which on a first glimpse looks simplistic:
To sum it up obviously DJVU seems like a great alternative to PDF, however its support for Free Software OSes is still lacking behind.
The Current windows DJVU works way better, though hopefully this will change soon.
Tags: alternative, ancient documents, BSD, church books, comparison, copy, Desktop, djviewlibre, djvu files, djvu format, download, electronic documents, eye, file, format, formatted document, gnu linux, gscan, human eye, kilobytes, Linux, linux os, mac users, Mac-s, mirror copy, old books, old magazines, os platforms, rare reports, size, software, someone, something, support, text, typical pdf, windjview, windows versions, windoze
Posted in Linux and FreeBSD Desktop, Various | No Comments »
Sunday, June 10th, 2012
Those who are in familiar with older UNIXes, UNIX BSD derivatives and GNU Linux should certainly remember the times, when we hackers used to talk to each other using talk service.
Those who don't know what talk command is it is a simple console / ssh utility to talk to another logged in users.
Talk is very similar to write and mesg one liner messasing utilities available for *nixes, the difference is it is intendted to provide interactive chat between the two logged in users. People who came to know UNIX or free software in older times most likely don't know talk, however I still remember how precious this tool was for communication back in the day.
I believe still it can be useful so I dediced to install ot on one FreeBSD host.
In order to have the talk service running on BSD it is necessery to have /usr/libexec/ntalkd installed on the system this however is installed by default with standard BSD OS installs, so no need for any external ports install to run it.
talk doesn't have it's own init script to start is not written to run as it own service but in order to run it is is necessery to enable it via inetd
Enabling it is done by;;;
1 — Editting /etc/inetd.conf
Inside the conf the line::
#ntalk dgram udp wait tty:tty /usr/libexec/ntalkd ntalkd
should be uncommented e.g, become ;;;
ntalk dgram udp wait tty:tty /usr/libexec/ntalkd ntalkd
2 — Restart inetd
freebsd# /etc/rc.d/inetd restart
Stopping inetd.
Starting inetd.
talk is planned to be used for peer to peer conversations over SSH so in a way it is the GRANDFATHER 🙂 of IRC, ICQ and Skype;;;
Here is an example on how talk is used ,, Let's say there are three logged in users
pcfreak# w
12:39PM up 3 days, 16:25, 3 users, load averages: 1.12, 0.91, 0.71
USER TTY FROM LOGIN@ IDLE WHAT
testuser p0 192.168.0.7 10:50AM - bash
hipo p3 192.168.0.8 12:23PM - w
root p4 :ttyp2:S.0 12:24PM - vim /usr/local/www/dat
I'm logged in with my username hipo and I would like to talk to testuser ;;;;
pcfreak% tty
/dev/ttyp3
You see I'm logged in on /dev/ttyp3 (this is the specific naming on BSDs) on Linux equivalent is /dev/tty3So to talk the other user testuser;;;;;-
$ talk testuser ttyp0
[No connection yet]
[Waiting for your party to respond]
The testuser logged in via SSH will then get a message ||;
Message from Talk_Daemon@pcfreak at 12:44 on 2012/06/10 ...
talk: connection requested by hipo@localhost
talk: respond with: talk hipo@localhost
To enter a talk session then the logged in testuser has to type:
$ talk hipo@localhost
Tags: Auto, BSD, bsd os, BSDs, Chat, connection, conversations, derivatives, dgram, doesn, Draft, editting, external ports, free software, gnu linux, hackers, hipo, host, init, init script, irc icq, Linux, load averages, localhost, mesg, necessery, need, ntalkd, p3, pcfreak, Restart, Skype, software, ssh, testuser, tool, unix, unix bsd, wait
Posted in FreeBSD | 1 Comment »
Monday, May 21st, 2012 
I'm running FreeBSD with Apache and PHP on it and I got in dmesg (kernel log), following error:
freebsd# dmesg|grep -i vm.pmap.shpgperproc
Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
The exact FreeBSD, Apache and php versions I have installed are:
freebsd# uname -a ; httpd -V ; php –version
FreeBSD pcfreak 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #0: Fri Oct 2 12:21:39 UTC 2009 root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386
Server version: Apache/2.0.64
Server built: Mar 13 2011 23:36:25Server's Module Magic Number: 20050127:14
Server loaded: APR 0.9.19, APR-UTIL 0.9.19
Compiled using: APR 0.9.19, APR-UTIL 0.9.19
Architecture: 32-bit
Server compiled with….
-D APACHE_MPM_DIR="server/mpm/prefork"
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
-D APR_USE_FLOCK_SERIALIZE
-D APR_USE_PTHREAD_SERIALIZE
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D HTTPD_ROOT="/usr/local"
-D SUEXEC_BIN="/usr/local/bin/suexec"
-D DEFAULT_PIDLOG="/var/run/httpd.pid"
-D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
-D DEFAULT_LOCKFILE="/var/run/accept.lock"
-D DEFAULT_ERRORLOG="logs/error_log"
-D AP_TYPES_CONFIG_FILE="etc/apache2/mime.types"
-D SERVER_CONFIG_FILE="etc/apache2/httpd.conf"
PHP 5.3.5 with Suhosin-Patch (cli) (built: Mar 14 2011 00:29:17)
Copyright (c) 1997-2009 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies
with eAccelerator v0.9.6.1, Copyright (c) 2004-2010 eAccelerator, by eAccelerator
After a bunch of research a FreeBSD forums thread , I've found the fix suggested by a guy.
The solution suggested in the forum is to raise up vm.pmap.pv_entry_ma to vm.pmap.pv_entry_max=1743504, however I've noticed this value is read only and cannot be changed on the BSD running kernel;
freebsd# sysctl vm.pmap.pv_entry_max=1743504
sysctl: oid 'vm.pmap.pv_entry_max' is read only
Instead to solve the;
Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
, I had to add in /boot/loader.conf
vm.pmap.pde.mappings=68
vm.pmap.shpgperproc=500
vm.pmap.pv_entry_max=1743504
Adding this values through /boot/loader.conf set them on kernel boot time. I've seen also in the threads the consider increasing either the vm.pmap.shpgperproc is also encountered on FreeBSD hosts running Squid, Dansguardion and other web proxy softwares on busy hosts.
This problems are not likely to happen for people who are running latest FreeBSD releases (>8.3, 9.x), I've read in same above post in newer BSD kernels the vm.pmap is no longer existing in newer kernels.
Tags: apache 2, apache2, architecture, Auto, boot time, BSD, dmesg, Draft, eeBSDI, errorlog, Fix Approaching, flock, freebsd, freebsd apache, Fri, GENERIC, grep, httpd, kernel, limit, loader, logs apache, magic number, Mar, mime types, mmap, Module, mpm, net usr, number, Oct, patc, pcfreak, php version, php versions, PV, RELEASE-p, root, scoreboard, sendfile, serialize, server, server config, server version, shpgperproc, suexec, threads, uname, UTC, vm, Zend
Posted in FreeBSD, System Administration | No Comments »
Wednesday, May 16th, 2012
After finding out How PC Speaker is muted on Linux , I've decided to also disable the annoying beeps on BSD. This is in tandem with the minimalistic philosophy I try to apply to every server I manage.
Also on BSD Desktop machines it is quite annoying especially if csh (C Shell) is used, everytime you press TAB you get the beep sound. On BSD beep sound produced on tab completion is louder than in Linux and that makes it even more annoying …
Disabling pc-speaker beeps on BSDs is done via a sysctl kernel variable:
freebsd# sysctl hw.syscons.bell=0
hw.syscons.bell: 0 -> 0
To further permanently disable on system boot add hw.syscons.bell=0 to /etc/sysctl.conf, e.g.:
freebsd# echo 'hw.syscons.bell=0' >> /etc/sysctl.conf
Well that's it no more mind drilling beeps :)
Tags: annoying beeps, Auto, beep, beep sound, bell, boot, BSD, BSDs, c shell, completion, conf, csh, Desktop, desktop machines, Disabling, Draft, drilling, everytime, freebsd, hw, kernel, kernels, Linux, mind, Mute, nbsp, pc speaker, philosophy, server, Sound, sysctl, system, system boot, tab, tab completion, tandem
Posted in FreeBSD, System Administration | No Comments »
Tuesday, May 15th, 2012
On FreeBSD the default kernel is compiled to support ACPI. Most of the modern PCs has already embedded support for ACPI power saving instructions.
Therefore a default installed FreeBSD is trying to take advantage of this at cases and is trying to save energy.
This is not too useful on servers, because saving energy could have at times a bad impact on server performance if the server is heavy loaded at times and not so loaded at other times of the day.
Besides that on servers saving energy shouldn't be the main motivator but server stability and productivity is. Therefore in my personal view on FreeBSD used on servers it is better to disable complete the ACPI in order to disable CPU fan control to change rotation speeds all the time from low to high rotation cycles and vice versa at times of low / high server load.
Another benefit of removing the ACPI support on a server is this would probably increase the CPU fan life span and possibly prevent the CPU to be severely heated at times.
Moreover, some piece of hardware might have troubles in properly supporting ACPI specifications and thus ACPI could be a reason for unexpected machine hang ups.
With all said I would recommend to anyone willing to use BSD for a server to disable the ACPI (Advanced Configuration and Power Interface), just like I did.
Here is how;
1. Quick review on how ACPI is handled on FreeBSD
acpi support is being handled on FreeBSD by a number of loadable kernel modules, here is a complete list of all the kernel modules dealins with acpi:
freebsd# cd /boot
freebsd# find . -iname '*acpi*.ko'
./kernel/acpi.ko
./kernel/acpi_aiboost.ko
./kernel/acpi_asus.ko
./kernel/acpi_fujitsu.ko
./kernel/acpi_ibm.ko
./kernel/acpi_panasonic.ko
./kernel/acpi_sony.ko
./kernel/acpi_toshiba.ko
./kernel/acpi_video.ko
./kernel/acpi_dock.ko
By default on FreeBSD, if hardware has some support for ACPI the acpi gets activated by acpi.ko kernel module. The specific type of vendors specific ACPI like IBM, ASUS, Fujitsu are controlled by the respective kernel module from the list …
Hence, to control if ACPI is loaded or not on a FreeBSD system with no need to reboot one can use kldload, kldunload module management BSD cmds.
a) Check if acpi is loaded on a BSD
freebsd# kldstatkldstat | grep -i acpi
9 1 0xc9260000 57000 acpi.ko
b) unload kernel enabled ACPI support
freebsd# kldunload acpi
c) Load acpi support (not the case with me but someone might need it, if for instance BSD is running on laptop)
freebsd# kldload acpi
2. Disabling ACPI to load on bootup on BSD
a) In /boot/loader.conf add the following variables:
hint.acpi.0.disabled="1"
hint.p4tcc.0.disabled=1
hint.acpi_throttle.0.disabled=1
b) in /boot/device.hints add:
hint.acpi.0.disabled="1"
c) in /boot/defaults/loader.conf make sure:
##############################################################
### ACPI settings ##########################################
##############################################################
acpi_dsdt_load="NO" # DSDT Overriding
acpi_dsdt_type="acpi_dsdt" # Don't change this
acpi_dsdt_name="/boot/acpi_dsdt.aml"
# Override DSDT in BIOS by this file
acpi_video_load="NO" # Load the ACPI video extension driver
d) disable ACPI thermal monitoring
It is generally a good idea to disable the ACPI thermal monitoring, as many machines hardware does not support it.
To do so in /boot/loader.conf add
debug.acpi.disabled="thermal"
If you want to learn more on on how ACPI is being handled on BDSs check out:
freebsd# man acpi
Other alternative method to permanently wipe out ACPI support is by not compiling ACPI support in the kernel.
If that's the case in /usr/obj/usr/src/sys/GENERIC make sure device acpi is commented, e.g.:
##device acpi
Tags: acpi specifications, acpi support, advanced configuration and power interface, aiboost, Auto, benefit, boot time, BSD, cd boot, control, cpu fan, default kernel, Draft, fan control, fan life, FreeBSDacpi, Fujitsu, ibm, impact, iname, kernel module, kldload, life span, loadable kernel modules, loader, Monitoring, motivator, number, personal view, piece, power, quot, reason, rotation, rotation speeds, saving energy, server load, server performance, server stability, shouldn, support, time, type, ups, video
Posted in FreeBSD, System Administration | 1 Comment »
Tuesday, May 8th, 2012I'm starting to learn some video editing, as I need it sometimes for building client websites.
As a Linux user I needed to have some kind of software for amateur video editing.
For Microsoft Windows OS, there are tons of video editor programs both free and proprietary (paid).
Windows users can for instance use the free software program VirtualDub (licensed under GPL license) to easily cut movie scenes from a video.
Unfortunately VirtualDub didn't have a Linux or BSD version so in my case I had to look for another soft.
I consulted a friend of mine who recommended a video editor program called LiVES.
If you haven't done any video editing previously on Linux (like my case was), you will certainly be happy to try LiVES
LiVES can extract only sound from videos, cut selected parts (frames) from videos and do plenty of other nice stuff. It is just great piece of software for anyone, who needs to do simply (newbie) video editting.
With LiVES even an amateur video editor like me could, immediately learn how to chop a movie scenes …
To master the basics and edit one video in FLV format it took me about 1 hour of time, as in the beginning it was confusing to get confortable with the program scenes selector.
One downside of LiVES it failure to open a FLV file I wanted to edit.
In order to be able to edit the flv movie hence I first had to convert the FLV to AVI or MPEG, as this two (video multimedia formats) are supported by LiVES video editor.
After completing my video scenes chopping to the AVI file I had to convert back to FLV.
In order to complete the convertion between FLV to AVI format on my Debian Linux, I used a program called avidemux
Avidemux has a nice GUI interface and also like Lives has support for video editting, though I have never succesfully done any video edits with it.
Avidemux IMHO is user (completely intuitive). To convert the FLV to AVI, all I had to do was simply open the file FLV file, press (CTRL+S) select my FLV video file format and select the output file extension format to be AVI.
Further on, used LiVES to cut my desired parts from my video of choice. Once the cuts were complete I saved the new cutted version of video to AVI.
Then I needed the video again in FLV to upload it in Joomla, so used ffmpeg – command line tool to do the AVI to FLV file converstion, like so:
hipo@noah:~$ /usr/bin/ffmpeg -i my_media_file.avi my_video_file.flv
Hope this article helps someone aiming to do basic video editting on Linux with LiVES and just like needed FLV to AVI and AVI to FLV convertions.
Tags: Auto, avi, avi file, avi format, avidemux, BSD, client, client websites, convertion, debian linux, downside, Draft, editing, editor, failure, file, flv file, format, free software program, gui interface, how to convert flv to avi, IMHO, instance, Linux, linux user, Microsoft, microsoft windows os, multimedia formats, nice stuff, piece, selector, simple, software, support, time, video, video editing, video editor, video editting, video multimedia, video scenes, Videos, windows users
Posted in Entertainment, Everyday Life, Linux and FreeBSD Desktop | No Comments »
