Problem solved with gem install libv8 on FreeBSD 10.2

This is the output of running the command ‘gem install libv8’:

the result is :
An error occurred while installing libv8 (, and Bundler cannot continue.
Make sure that `gem install libv8 -v ‘’` succeeds before bundling.

problem solved :

sudo gem install libv8 -v '' -- --with-system-v8

then ….

Building native extensions with: '--with-system-v8'
This could take a while...
Successfully installed libv8-
Parsing documentation for libv8-
Installing ri documentation for libv8-
Done installing documentation for libv8 after 1 seconds
1 gem installed

and finally again running …bundle install

$bundle install 

Hope that helps!

FreeBSD config app based

Updating FreeBSD ports system ;

portsnap fetch extract

cd /usr/ports/ports-mgmt/portmaster
make install clean

pkg upgrade

portmaster -a

after installing emacs or your favorite editor :

pkg install emacs

Install  xorg :

pkg install xorg

emacs /etc/rc.conf


Instalación de gnome3 :

pkg install gnome3

then edit file :

sysctl kern.ipc.shm_allow_removed=1

emacs /etc/sysctl.conf


then install app based :

pkg install chromium
pkg install htop wget mc
pkg install icedtea-web
mkdir -p /usr/local/share/chromium/plugins
ln -s /usr/local/lib/ /usr/local/share/chromium/plugins/

Linux compatibility installation and flash :

emacs /etc/fstab
linproc /compat/linux/proc linprocfs rw 0 0

Then … edit file and save…


after from console :

pkg install nspluginwrapper

from the console as a normal user :

nspluginwrapper -v -a -i

cd /usr/ports/www/linux-f10-flashplugin11
make install clean
ln -s /usr/local/lib/browser_plugins/linux-f10-flashplugin/ /usr/local/lib/browser_plugins/
cd /usr/home/TU_USUARIO/.mozilla/plugins
ln -s /usr/local/lib/browser_plugins/linux-f10-flashplugin/

Install virtualbox :

pkg install virtualbox-ose
emacs /boot/loader.conf

emacs /etc/devfs.conf

# Virtualbox network access
own vboxnetctl root:vboxusers
perm vboxnetctl 0660

Saved file and then ….

pw usermod user -G vboxusers

Install Cups :

pkg install cups
pkg install foomatic-filters
emacs /etc/rc.conf

Saved file and then ….

pw usermod root -G cups
pw usermod user -G cups

Mount  USB from FreeBSD:

pkg install thunar-vfs fuse fuse-utils
pkg install fusefs-ntfs fusefs-ext4fuse
emacs /boot/loader.conf

emacs /etc/fstab
proc /proc procfs rw 0 0
fdesc /dev/fd fdescfs rw 0 0

Save file and then ….

emacs /etc/sysctl.conf

Save config and then ….

pw usermod user -G wheel
pw usermod user -G operator

emacs /etc/devfs.conf

perm /dev/acd0 0666
perm /dev/acd1 0666
perm /dev/cd0 0666
perm /dev/cd1 0666

perm /dev/da0 0666
perm /dev/da1 0666
perm /dev/da2 0666
perm /dev/da3 0666
perm /dev/da4 0666
perm /dev/da5 0666

perm /dev/pass0 0666
perm /dev/xpt0 0666
perm /dev/uscanner0 0666
perm /dev/video0 0666
perm /dev/tuner0 0666
perm /dev/dvb/adapter0/demux0 0666
perm /dev/dvb/adapter0/dvr 0666
perm /dev/dvb/adapter0/frontend0 0666

Saved file and then ….

emacs /etc/devfs.rules

add path 'ad[0-9]*' mode 666
add path 'ada[0-9]*' mode 666
add path 'da[0-9]*' mode 666
add path 'acd[0-9]*' mode 666
add path 'cd[0-9]*' mode 666
add path 'mmcsd[0-9]*' mode 666
add path 'pass[0-9]*' mode 666
add path 'xpt[0-9]*' mode 666
add path 'ugen[0-9]*' mode 666
add path 'usbctl' mode 666
add path 'usb/*' mode 666
add path 'lpt[0-9]*' mode 666
add path 'ulpt[0-9]*' mode 666
add path 'unlpt[0-9]*' mode 666
add path 'fd[0-9]*' mode 666
add path 'uscan[0-9]*' mode 666
add path 'video[0-9]*' mode 666
add path 'tuner[0-9]*' mode 666
add path 'dvb/*' mode 666
add path 'cx88*' mode 0660
add path 'cx23885*' mode 0660
add path 'iicdev*' mode 0660
add path 'uvisor[0-9]*' mode 0660

Saved file and then ….

emacs /etc/rc.conf


Install of other application :

pkg install vlc libreoffice xarchiver rar unrar p7zip filezilla epdfview gimp xfburn ristretto gtk-murrine-engine

Guys then Enjoy FreeBSD..!!!

FreeBSD Foundation Statement on Harassment

Over the past week, the FreeBSD community has raised concerns about the handling of a harassment report in June, 2015. The FreeBSD Foundation takes these concerns very seriously. Harassment will not be tolerated in the FreeBSD community. We are working with the FreeBSD Core Team to review the events and determine how future reports can be better handled. To create a safer environment for all members of our community, we are developing new processes and procedures to handle these situations as they arise. Community members must feel unafraid to report harassment, and must know how to do so. When harassment is reported, community members need to be confident that their concerns will be heard and dealt with fairly and quickly.

To ensure that the Project has the proper resources and expertise to handle reports, the FreeBSD Foundation is engaging with outside professional resources experienced in dealing with harassment and conflict issues. We are also supporting and participating in a committee working to revise the Project’s Code of Conduct, which consists of both men and women drawn from within and beyond the FreeBSD Community. Revisions to the code will ensure that all community members understand what constitutes harassment and conflict, and how each will be handled

The Foundation and Core Team are committed to creating and maintaining a FreeBSD community that is welcome and safe to all those who wish to be involved.   We will share the results of our combined efforts as they become available.

If you have additional questions or concerns, please don’t hesitate to contact

Rails 4.1.5 ; rails g controller is broken => Missing controller key on routes definition

Users/fedex/.rvm/gems/ruby-2.1.0/gems/activesupport-4.1.5/lib/active_support/dependencies.rb:247:in require': cannot load such file -- (LoadError) from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/activesupport-4.1.5/lib/active_support/dependencies.rb:247:inblock in require’ from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/activesupport-4.1.5/lib/active_support/dependencies.rb:232:in load_dependency' from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/activesupport-4.1.5/lib/active_support/dependencies.rb:247:inrequire’ from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/actionpack-4.1.5/lib/action_dispatch/routing/mapper.rb:9:in <top (required)>' from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/actionpack-4.1.5/lib/action_dispatch/routing/route_set.rb:333:ineval_block’ from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/actionpack-4.1.5/lib/action_dispatch/routing/route_set.rb:352:in block in clear!' from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/actionpack-4.1.5/lib/action_dispatch/routing/route_set.rb:352:ineach’ from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/actionpack-4.1.5/lib/action_dispatch/routing/route_set.rb:352:in clear!' from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/railties-4.1.5/lib/rails/application/routes_reloader.rb:35:inblock in clear!’ from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/railties-4.1.5/lib/rails/application/routes_reloader.rb:33:in each' from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/railties-4.1.5/lib/rails/application/routes_reloader.rb:33:inclear!’ from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/railties-4.1.5/lib/rails/application/routes_reloader.rb:15:in reload!' from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/railties-4.1.5/lib/rails/application/routes_reloader.rb:26:inblock in updater’ from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/activesupport-4.1.5/lib/active_support/file_update_checker.rb:75:in call' from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/activesupport-4.1.5/lib/active_support/file_update_checker.rb:75:inexecute’ from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/railties-4.1.5/lib/rails/application/routes_reloader.rb:27:in updater' from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/railties-4.1.5/lib/rails/application/routes_reloader.rb:7:inexecute_if_updated’ from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/railties-4.1.5/lib/rails/application/finisher.rb:71:in block in <module:Finisher>' from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/railties-4.1.5/lib/rails/initializable.rb:30:ininstance_exec’ from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/railties-4.1.5/lib/rails/initializable.rb:30:in run' from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/railties-4.1.5/lib/rails/initializable.rb:55:inblock in run_initializers’ from /Users/fedex/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/tsort.rb:226:in block in tsort_each' from /Users/fedex/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/tsort.rb:348:inblock (2 levels) in each_strongly_connected_component’ from /Users/fedex/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/tsort.rb:427:in each_strongly_connected_component_from' from /Users/fedex/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/tsort.rb:347:inblock in each_strongly_connected_component’ from /Users/fedex/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/tsort.rb:345:in each' from /Users/fedex/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/tsort.rb:345:incall’ from /Users/fedex/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/tsort.rb:345:in each_strongly_connected_component' from /Users/fedex/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/tsort.rb:224:intsort_each’ from /Users/fedex/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/tsort.rb:205:in tsort_each' from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/railties-4.1.5/lib/rails/initializable.rb:54:inrun_initializers’ from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/railties-4.1.5/lib/rails/application.rb:300:in initialize!' from /Users/fedex/rails-2014/blogpress/config/environment.rb:5:in‘ from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/spring-1.1.3/lib/spring/application.rb:92:in require' from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/spring-1.1.3/lib/spring/application.rb:92:inpreload’ from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/spring-1.1.3/lib/spring/application.rb:140:in serve' from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/spring-1.1.3/lib/spring/application.rb:128:inblock in run’ from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/spring-1.1.3/lib/spring/application.rb:122:in loop' from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/spring-1.1.3/lib/spring/application.rb:122:inrun’ from /Users/fedex/.rvm/gems/ruby-2.1.0/gems/spring-1.1.3/lib/spring/application/boot.rb:18:in <top (required)>' from /Users/fedex/.rvm/rubies/ruby-2.1.0/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:54:inrequire’ from /Users/fedex/.rvm/rubies/ruby-2.1.0/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:54:in require' from -e:1:in

Rails funciono en FreeBSD con Sqlite3 ,solamente problemas con node.js

$ rails -v
Rails 4.0.2
$ ruby -v
ruby 1.9.3p484 (2013-11-22 revision 43786) [amd64-freebsd10]

despues de crear uno nuevo project en rails al ejecutar el server sale el siguiente mensaje :

/usr/local/lib/ruby/gems/1.9/gems/railties-4.0.2/lib/rails/app_rails_loader.rb:37: warning: Insecure world writable dir /usr in PATH, mode 040777
/usr/local/lib/ruby/gems/1.9/gems/bundler-1.5.2/lib/bundler/runtime.rb:220: warning: Insecure world writable dir /usr in PATH, mode 040777

pero aparecio un error que decia java runtime , problems node.js luego haces como root ;

cd /usr/ports/www/node/ && make install clean

====> Compressing man pages (compress-man)
===>  Installing for node-0.10.25
===>   Registering installation for node-0.10.25
Installing node-0.10.25... done
This port has installed the following files which ma act as network
servers and may therefore pose a remote security ris to the system.

If there are vulnerabilities in these programs there may be a security
risk to the system. FreeBSD makes no guarantee about the security of
ports included in the Ports Collection. Please type 'make deinstall'
to deinstall the port if this is a concern.

For more information, and contact details about the security
status of this software, see the following webpage:
===>  Cleaning for node-0.10.25

despues de esto deberia funcionar rails …

$ rails s
=> Booting WEBrick
=> Rails 4.0.2 application starting in development on
=> Run `rails server -h` for more startup options
=> Ctrl-C to shutdown server
[2014-02-21 22:22:30] INFO  WEBrick 1.3.1
[2014-02-21 22:22:30] INFO  ruby 1.9.3 (2013-11-22) [amd64-freebsd10]
[2014-02-21 22:22:30] INFO  WEBrick::HTTPServer#start: pid=45626 port=3000

ahora deberia corregir el ultimo error :

warning: Insecure world writable dir /usr in PATH, mode 040777

Cambiar el hostname de FreeBSD por BSD

se me dio por cambiar el hostname de FreeBSD por BSD , solamente con sudo hostname BSD y cuando reinicio el equipo al otro día , me tiraba un error , y había un conflicto por eso se reiniciaba automáticamente … a todo esto el conflicto de hostname permanecía , lo que me llevo a entrar en modo single user , consola cuando inicias el sistema y apretas la opción 2 boot single user y pasamos al modo consola

como no tenemos montado el file system y esta en modo read-only luego montamos de la siguiente manera

# sudo su
#mount -urw /

para volver a montar el sistema de archivos raíz en modo de lectura / escritura. También puede ser necesario para ejecutar

mount-a-t ufs 

para montar el sistema de archivos donde se define su editor favorito. Si su editor favorito es en un sistema de archivos de red, tendrá que o bien configurar la red manualmente antes de poder montar los sistemas de archivos de red o utiliza un editor que reside en un sistema de archivos local…

mas info esta en https://www.FreeBSD Handbook/