FreeBSD and Linux Compatibility part 2 more errors…

By finndo On April 3, 2010 · 1 Comment

right back again… I tried that and it told me I had to do a sudo make distclean so I did that and got the exact same error again!!!  What is really starting to piss me off is this is (again) a freaking gnome specific app, do I really have to [...]

right back again… I tried that and it told me I had to do a sudo make distclean so I did that and got the exact same error again!!!  What is really starting to piss me off is this is (again) a freaking gnome specific app, do I really have to instlal gnome to get my FreeBSD to actually function with KDE?  this is starting to piss me off really bad.  not to mention FreeBSD has started reporting that my CPU is reaching a critical temp and then shuts my computer off, yet when I restart it (within 10 seconds) and go into the BIOS and check the system it still shows a CPU temp of 40C which is pretty freakin cold for not having any  liquid cooling in my case (probably is so cool because I am using an onboard video card…)  and THAT is annoying.  what is worse, when I check it with sysctl (I think that is the command in FreeBSD) it ALWAYS reports my CPU at 30C on every core, so I know ACPI is not working, but if I boot using boot option 2 (boot without ACPI) the system locks up and fails to boot, so I can not find a way around that problem either.

 

Only when youare about to give up… hmm… I did a search on this error and came up with a completely different issue (with same error though) and got a solution that seems to have worked…  USE GMAKE (funny, as the install instructions just say “make”).  ran a sudo pkgdb -F all good, ran a sudo portupgrade -ra and still getting the failed gcc compiler message for multi-threaded…

 

** Listing the failed packages (-:ignored / *:skipped / !:failed)
        ! devel/boost-python-libs (boost-python-libs-1.39.0)    (missing header)
        ! x11-toolkits/linux-f10-pango (linux-f10-pango-1.22.3) (unknown build error)
        ! textproc/py-libxml2 (py26-libxml2-2.7.5)      (missing header)
        ! devel/apr (apr-ipv6-gdbm-db42-1.3.8.1.3.9)    (unknown build error)
        ! misc/iso-codes (iso-codes-3.10.3)     (missing header)
        * devel/subversion (subversion-1.6.5)
        ! devel/py-gobject (py26-gobject-2.16.1)        (configure error)
        * x11/libxklavier (libxklavier-3.9,1)
        ! sysutils/consolekit (consolekit-0.3.0_8)      (configure error)
        ! java/diablo-jre16 (diablo-jre-1.6.0.07.02)    (checksum mismatch)
        ! graphics/py-cairo (py26-cairo-1.8.8)  (configure error)
        * x11-toolkits/py-gtk2 (py26-gtk-2.14.1_1)
        ! multimedia/gstreamer (gstreamer-0.10.24)      (configure error)
        ! devel/gconf2 (gconf2-2.26.2_1)        (configure error)
        * devel/libgsf (libgsf-1.14.15_1)
        * graphics/librsvg2 (librsvg2-2.26.0_2)
        * multimedia/gstreamer-plugins (gstreamer-plugins-0.10.24,3)
        * net-im/libnice (libnice-0.0.9)
        * multimedia/gstreamer-plugins-good (gstreamer-plugins-good-0.10.16,3)
        * multimedia/gstreamer-plugins-theora (gstreamer-plugins-theora-0.10.24,3)
        * multimedia/py-gstreamer (py26-gstreamer-0.10.16)
        * multimedia/gstreamer-plugins-bad (gstreamer-plugins-bad-0.10.14,3)
        * multimedia/gstreamer-plugins-xvid (gstreamer-plugins-xvid-0.10.14,3)
        * multimedia/gstreamer-ffmpeg (gstreamer-ffmpeg-0.10.8)
        * multimedia/gstreamer-plugins-dts (gstreamer-plugins-dts-0.10.14,3)
        * x11-toolkits/gstreamer-plugins-pango (gstreamer-plugins-pango-0.10.24,3)
        * devel/gstreamer-plugins-gconf (gstreamer-plugins-gconf-0.10.16,3)
        * graphics/gstreamer-plugins-libpng (gstreamer-plugins-libpng-0.10.16,3)
        * audio/gstreamer-plugins-ogg (gstreamer-plugins-ogg-0.10.24,3)
        * audio/gstreamer-plugins-esound (gstreamer-plugins-esound-0.10.16,3)
        * audio/gstreamer-plugins-vorbis (gstreamer-plugins-vorbis-0.10.24,3)
        * devel/gstreamer-plugins-gio (gstreamer-plugins-gio-0.10.24,3)
        * multimedia/gstreamer-plugins-ugly (gstreamer-plugins-ugly-0.10.12,3)
        * multimedia/gstreamer-plugins-dvd (gstreamer-plugins-dvd-0.10.12_1,3)
        * audio/gstreamer-plugins-mad (gstreamer-plugins-mad-0.10.12,3)
        * audio/gstreamer-plugins-flac (gstreamer-plugins-flac-0.10.16,3)
        * multimedia/gstreamer-plugins-mpeg2dec (gstreamer-plugins-mpeg2dec-0.10.12,3)
        * audio/gstreamer-plugins-a52dec (gstreamer-plugins-a52dec-0.10.12,3)
        * multimedia/gstreamer-plugins-core (gstreamer-plugins-core-0.10_10)
        * audio/gstreamer-plugins-cdparanoia (gstreamer-plugins-cdparanoia-0.10.24_1,3)
        * net-im/farsight2 (farsight2-0.0.15)
        * multimedia/qt4-phonon-gst (qt4-phonon-gst-4.5.2)
        * www/qt4-webkit (qt4-webkit-4.5.2)
        * devel/qt4-assistant (qt4-assistant-4.5.2)
        * devel/qt4-designer (qt4-designer-4.5.2)
        * devel/qt4-linguist (qt4-linguist-4.5.2)
        * emulators/virtualbox-ose (virtualbox-3.0.51.r22902_2)
        * sysutils/hal (hal-0.5.11_26)
        * x11/kdebase3 (kdebase-3.5.10_3)
        * devel/gnome-vfs (gnome-vfs-2.24.1_1)
        * x11/yakuake (yakuake-2.8.1_3)
        * x11-servers/xorg-server (xorg-server-1.6.1,1)
        * x11-drivers/xf86-video-ati (xf86-video-ati-6.12.2_1)
        * x11-drivers/xf86-video-r128 (xf86-video-r128-6.8.0_3)
        * x11-drivers/xf86-video-openchrome (xf86-video-openchrome-0.2.903_2)
        * x11/libgnome (libgnome-2.26.0_1)
        * x11/kdelibs4 (kdelibs-4.3.1_3)
        * games/kdegames4 (kdegames-4.3.1)
        * sysutils/gstreamer-plugins-hal (gstreamer-plugins-hal-0.10.16,3)
        * graphics/kdegraphics4 (kdegraphics-4.3.1)
        * misc/kdeedu4 (kdeedu-4.3.1)
        * x11-drivers/xf86-video-nv (xf86-video-nv-2.1.13_1)
        * x11-drivers/xf86-input-mouse (xf86-input-mouse-1.4.0_6)
        * x11/kdelibs4-experimental (kdelibs-experimental-4.3.1)
        * x11-drivers/xf86-video-radeonhd (xf86-video-radeonhd-1.2.5_2)
        * x11-drivers/xf86-video-vesa (xf86-video-vesa-2.1.0_2)
        * x11-drivers/xf86-video-mach64 (xf86-video-mach64-6.8.1)
        * x11-drivers/xf86-video-intel (xf86-video-intel-2.7.1)
        * deskutils/kdepimlibs4 (kdepimlibs-4.3.1)
        * net/kdenetwork4 (kdenetwork-4.3.1)
        * x11/kdebase4-runtime (kdebase-runtime-4.3.1_1)
        * devel/kdesdk4 (kdesdk-4.3.1)
        * deskutils/kdepim4-runtime (kdepim-runtime-4.3.1)
        * accessibility/kdeaccessibility4 (kdeaccessibility-4.3.1)
        * deskutils/kdepim4 (kdepim-4.3.1_1)
        * sysutils/kdeadmin4 (kdeadmin-4.3.1)
        * x11/kdebase4-workspace (kdebase-workspace-4.3.1)
        * x11-clocks/kdetoys4 (kdetoys-4.3.1)
        * x11-themes/kdeartwork4 (kdeartwork-4.3.1)
        * security/gnome-keyring (gnome-keyring-2.26.3_1)
        * textproc/gnome-doc-utils (gnome-doc-utils-0.16.1_1)
        * sysutils/policykit-gnome (policykit-gnome-0.9.2_2)
        * devel/libsoup (libsoup-2.26.3_2)
        * devel/gstreamer-plugins-soup (gstreamer-plugins-soup-0.10.16,3)
        * multimedia/kdemultimedia4 (kdemultimedia-4.3.1_1)
        * x11-toolkits/libbonoboui (libbonoboui-2.24.1_1)
        * www/kdewebdev4 (kdewebdev-4.3.1)
        * x11-drivers/xf86-input-keyboard (xf86-input-keyboard-1.3.2_2)
        * x11-drivers/xorg-drivers (xorg-drivers-7.4_2)
        * x11/xorg (xorg-7.4_2)
        * x11/kdebase4 (kdebase-4.3.1_1)
        * misc/kdeutils4 (kdeutils-4.3.1_1)
        * sysutils/gnome-mount (gnome-mount-0.8_3)
        * graphics/swfdec (swfdec-0.8.4_1)
        * devel/gvfs (gvfs-1.2.3_2)
        * x11-toolkits/libgnomeui (libgnomeui-2.24.1_1)
        * net/libgweather (libgweather-2.26.2.1_1)
        * databases/evolution-data-server (evolution-data-server-2.26.3_1)
        * deskutils/kdeplasma-addons (kdeplasma-addons-4.3.1)
        * x11/kde4 (kde4-4.3.1)
        * x11-toolkits/py-gnome2 (py26-gnome-2.26.1_1)
        * x11/gnome-desktop (gnome-desktop-2.26.3_1)
        * multimedia/cheese (cheese-2.26.3_1)

 

Right, time to run a backup before I FUBAR it real bad.

Tagged with: • • • • • • • • • •
 

FreeBSD 8.0 and KDE 4.4

By finndo On March 19, 2010 · Leave a Comment

Continuing on from my last post, it was really quite simple to get KDE to run after I closed that post.  in fact I only had to type in 2 lines and the second one ran KDE.

 

exec /usr/local/kde4/bin/startkde4 > ~/.xinitrc startx

 

BAM! that was [...]

Continuing on from my last post, it was really quite simple to get KDE to run after I closed that post.  in fact I only had to type in 2 lines and the second one ran KDE.

 

  1. exec /usr/local/kde4/bin/startkde4 > ~/.xinitrc
  2. startx

 

BAM! that was it, finally!! after 2.5 years of trying I could not believe it was so simple… and then I noticed… I had no KB or Mouse… I did not know it was possible to be so happy and so sad at the same time…

 

You can search the inet any way you want and you’ll find out that running “X -configure” will generate your xorg.conf.new file that you then have to move to “/usr/local/etc/X11/xorg.conf “   one more item to note, when you test this, make sure you type “X -retro” or “Xorg -retro” else you will just get a blank screen.

*****WARNING*****ok, now that I got your attention, you must run the following command before attempting to use your xorg.conf in the previously mentioned location or you will lock your system up and have to hit the power button. “sudo chmod root:wheel /usr/local/etc/X11/xorg.conf“  if you do not have sudo installed, you have 3 choices.

 

  1. login as root (something I never do except to add my user id to the sudoers file)
  2. type “su -” and switch to root
  3. login as root and type “pkg_add -r sudo” then either add yourself to the wheel group or add yourself to the sudoers file

 

there are several ways to add yourself to the wheel group, the only one that sticks out in my mind right now that I can vouch for is “pw moduser [username] -G wheel [username]” this one sets your group to wheel AND your default group [username], if you skip the second [username] you will no longer have access to any of your own files or you can type “pw groupmod wheel -m [username]” should do the same, to add yourself to the sudoers file you need to type “visudo” then you will be in vi, here is what to do if you don’t know vi.

 

  1. press ”/” (initiates a search)
  2. type “root” (tells vi what to search for)
  3. press enter (begins the search process)
  4. press “n” (takes you to the next instance of “root”)
  5. press “o” (creates a new blank line under the current one and starts editing)
  6. type [username] [tab] “ALL=(ALL) ALL“  (make sure you use caps on the “ALL”, this allows [username] to use sudo)
  7. press ESC (stops edit mode)
  8. press “:” (informs vi you wish to enter a command)
  9. type “wq!” (tells vi to “write” the current file to disk and “quit” vi “NOW”
  10. press enter (executes the command you have entered

 

Now you will no longer have to log in as root on your machine, or su to root again.  Back to my problems…  So, I ran the dreaded -configure command (dreaded because after running it on any system in the last 2-3 years the only result I have ever gotten is the blank black screen syndrome) and of course, I got exactly what I was expecting… a blank black screen when I tested X with that config file.  This is the reason I did not switch to FreeBSD instead of windows back when FreeBSD 6.1 was released, I could never get beyond this point.  Well, about a days worth of inet searching and I have come across some useful information that “worked” for several users.  Nothing worked for me (feel free to search the issue and you’ll get a lovely list of others having this issue, some getting off easy, some giving up, some finding alternate ways to do it.)  about 15 minutes ago (not that you will know when that was based off my posting time, but it makes sense to say it that way…) I found a lovely forum post on FreeBSD.org, now when you look at that post you may not be surprised by what you see there, it is fairly common troubleshooting and common knowledge about the workings of FreeBSD and X.org; HOWEVER!!! and here is the kicker, it has in it a code snippet of the ever elusive “ServerFlags” section of  xorg.conf, something that apparently is not auto generated and really is not documented well (additionally other posts I saw told you to stick it in the “ServerLayout” section, which only causes X to crash without loading.)  I added the following to my xorg.conf file:

 

  1. Section “ServerFlags”
  2.                 Option “AllowEmptyInput” “off”
  3. EndSection
  4. Section “InputDevice”
  5.                 Identifier   “Keyboard0″
  6.                 Driver         ”kbd”
  7.                 Option “XkbOptions” “terminate:ctrl_alt_bksp”
  8. EndSection

 

Now, if you ran “X -configure” lines 4, 5, 6, and 8 should already be in there.  Lines 1 – 3 allow my mouse to work in X, and line 7 allows me to hit ctrl+alt+bksp to exit X and both worked!!  So I quickly exited X and tried “startx” and sure enough, KDE loaded, I could see it, and my mouse worked!!  hot dog!!

Tagged with: • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
 

Thoughts on Linux…

By finndo On February 22, 2010 · Leave a Comment

start off with some non-techie stuff first…

I head back to see my surgeon next Monday,  where he will tell me that in another week or two I should start putting some weight on my leg (toe touch, or partial weight bearing?) when at my PT.  I am also hoping he [...]

start off with some non-techie stuff first…

I head back to see my surgeon next Monday,  where he will tell me that in another week or two I should start putting some weight on my leg (toe touch, or partial weight bearing?) when at my PT.  I am also hoping he will tell me it is okay to get my incision wet, as it has been making it very difficult to take showers!

ok, on to the good stuff.

So, I am not at home and do not have my desktop machine available for use for the last week, I have been going through withdrawal…  but having to work on someone else’s machine, and my wife’s laptop (I think I mentioned before, I gave her mine, and sold her old one) has taught me one important lesson, why I prefer Linux.

My number one reason for preferring Linux over Windows is system maintenance.  What do I mean? well, I mean keeping everything up to date, this latest round of Adobe patching should make this make sense to everyone.  I don’t use Acrobat on my Linux machines for this reason.  However; back to the point, when I need to check for updates on my Linux machine I open Yakuake with a quick hit of F12 and type “sudo yum update” and it comes back and tells me every single thing installed on my system that has an update available, period, end of statement.  On windows, I have to launch 5-8 different apps, find their “check for updates” button/link and wait for the results (I have learned by doing this that OpenOffice.org does not notify you of a new version being released, only if there are updates for your version.  example, I have 3.1 installed, and 3.2 is now available.  clicking the check for updates menu option tells my “There are no available updates for this version” (maybe not word for word, but that is just about what it says).  I run windows update, Acrobat Update, Java update, Picasa update, Chrome update, Firefox update, and on and on… (yes I know there is an Adobe Updater, but I don’t know how to initiate it in Windows, and never cared enough to look it up, but now that I have mentioned it I sure I found instructions and have put a link to them here).

Simple and easy to manage, most distros even let you run their package manager and it has a button to click to check for updates for your system, making it easier and more time consuming all at once to do the same thing.  (Yakuake is always running and it takes me about 1.5 seconds to type that line into the terminal, it takes a lot longer to load the package manager from the application menu and then click the check for updates button, but you don’t have to type that way!)

The actual GUI interface for Windows an Linux and even MAC are so similar these days, that I don’t care which I am using as far as that is concerned.  I have come to the understanding that there will always be applications/games for an OS, other than the one I am using, that I want to use/play (take iPhone for example, they have the best Air Traffic Controller game I have played, and I’ve hunted those down and played quite a number of them, but I don’t own anything made by Apple, and probably won’t ever, unless the 2nd gen iPad totally rocks… but I will be getting an Android Tablet this year (possibly the Notion Ink Adam, or the HTC Google Chrome OS tablet), so I still probably won’t get an iPad).  My concern at this point, as I spend more and more time as a Unix Admin is maintenance.  The system I use at home needs to be practically maint free, as most Linux and Unix machines are, they will run for years without being touched by an admin, the best I know of are an AIX Server and a OpenVMS server, the AIX server has been running since 1991 and has never been patched, updated, reconfigured, or messed with in any way.  It is setup to contact a NIM server for logins, so no new users have ever been added to it, it has never crashed, never lost power, never been rebooted.  That to me is the greatest achievement of humankind (in technology anyways, and some of these companies need to take a look at the AIX OS and learn something from it!!!).  The other machine, the OpenVMS machine has been running since before 1994, but has not been patched, never been upgraded, never been rebooted, since 1994.  now I know next to nothing about OpenVMS, and have not personally logged into the machine itself, but a friend and co-worker of mine used to be the sole admin for the OpenVMS machines at that company and although that one is the only one like this, it is still running today without interference from humans.  I am sure some other machines are out there doing the same, but these are two that I know.  The longest Windows Server I have heard of running without rebooting or crashing was about 2.5 – 3 years, after which the hardware components in the server failed and the machine was replaced.  Some people have told me about Windows servers being up for 4 years and then being restarted by some new guy, but I have no validation of it and they could not give me a more exact time frame.

not sure if I made a compelling argument or not, but I need some medication and to go prop my leg up, so I am done here.  Also expecting UPS sooner or later for an over night supersave shipment… and it takes me 5 mins to get downstairs…  :)

Tagged with: • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
 

Fedora 12, VirtualBox, and Shared folders – a How To

By finndo On February 7, 2010 · 5 Comments

ok, so I woke up and now can’t get back to sleep.  nothing new, but this time I decided to do something instead of just laying there hoping to fall asleep before the sun rises.  Now, I thought that I already had this working, but apparently not… —edit okay, so I [...]

ok, so I woke up and now can’t get back to sleep.  nothing new, but this time I decided to do something instead of just laying there hoping to fall asleep before the sun rises.  Now, I thought that I already had this working, but apparently not… —edit okay, so I need to note I was doing these steps while writing this post and when I got to the step to reboot Fedora, step 6, I fell asleep.

I was and am currently using, a Fedora 12 VM from my laptop, now I thought I had the shared folders from the host OS (Win XP) setup, but could not find the mount point, so I just attempted to re-mount it.  fyi I’m using VirtualBox 3.1.2  so I attempted to remount the shared folder to a simple location…

$ sudo mount -t vboxsf documents /home/finndo/Documents/local

mount: unknown filesystem type ‘vboxsf’

so I do some Googling and come up with some interesting tidbits…

so, if you didn’t look at the link, here it is in a nutshell, to get the mount to work (yes I installed the VM additions, but did not notice the error…) please read the whole post before trying this, as there are some steps you may need to do a little differently and I have noted this, but not until after I list them!

ok, let me start from the beginning…

step by step instructions for getting shared folders to work in a Fedora 12 VM on VirtualBox (after you get fedora installed)

  1. open a console window (I am a huge fan of Yakuake)
  2. type “sudo yum install system-config-display”
  3. give it your password (you may have to do this every time you type sudo)
  4. type “sudo system-config-display”
  5. this will open a window in your GUI (KDE, Gnome, XFCE, ICE, whatever) choose the options for your display (if using Yakuake you need to hit F12 to make the console window go away so you can see this new window)
  6. type “sudo yum install gcc kernel kernel-devel kernel-headers”
  7. restart the VM to boot with the newest kernel
  8. goto the Devices menu and select install Guest additions
  9. back to the console and type “sudo mount /cdrom /media”
  10. type “sudo /media/VBoxLinuxAdditions-x86.run”
  11. (special note, if you have already run the VBox Additions from the cd, skip steps 7-10 and  just type this “sudo /etc/init.d/vboxadd setup”
  12. now I do not remember if I had to create the share for My Documents in VirtualBox or if it was there by default, but I have one, called “documents” and that is the one I am using in this example. so, type the following “sudo mkdir /mnt/shared-docs”
  13. type “mount -t vboxsf documents /mnt/shared-docs”
  14. then you can now access your Windows XP My Documents folder from your Fedora 12 install in the /mnt/shared-docs folder!!!

Really not that hard, but nowhere in the documentation for VirtualBox does it tell you that you have to do all of that!

Now, you can type “su -” and give it your password, then you do not have to use “sudo” at all for the entire process.  you may ask why I do it then, and it is because I work on linux and unix systems for a living (or at least I am trying to) and for security reasons they tell you to never su to root (become the root user) as it is too easy to type an accidentally command in that will make the entire system irreversibly broken (with out restoring from a backup) and since I have been logged into some servers that are used in the monitoring/maintenance of the space shuttle and international space station, so making one of those stop working for several hours or more is a really bad idea! therefore you sudo every command you need to run as root instead of becoming root, gets annoying at times, but almost eliminates the chance of accidental termination of your employment!

Ok, so a note, I am running this Fedora 12 VM on a single core laptop with 2GB of Ram (1.5GB given to Fedora, and nothing running in the host except the VM) and when I ran step 5 step 6 (I added a step later), it practically halted my system and took almost 30 minutes (part of the reason why I fell asleep) it would say it was downloading a 8.6 meg file and take 14 minutes to do so, at 858Mb/s (which is impossible I know, but that is what it did and said) anyway, the main reason I did this, is that I had downloaded some other Fedora .iso files and filled my Virtual HDD and needed to get them off!!

So, now you know… and as we all know… Knowing is half the battle!

************editing updates and bonus steps! *********** May 10th 2010 ****************

Bonus step!!

now I bet you want to know how to make it comeback after a reboot, don’t cha!

  1. sudo vi /etc/fstab
  2. “G” (uppercase letter)
  3. “o” (lowercase number)
  4. [name you used in VBox shared folders] [tab] [fullpath to the mount point in the VM, or #12 above] [tab] vboxsf [tab] noauto,rw [tab] 0 [tab] 0 (both of those are the number zero)
  5. [esc] (the escape key, probably is labeled “esc” on your keyboard in the top left corner)
  6. “wq!” (lowercase letters and an exclamation (sometimes called a “BANG” by unix people, older people, and those who were taught by one of the afore mentioned.))
  7. now reboot
  8. sudo mount [name you used in VBox shared folders] (you will have to do this everytime you reboot (I just do a save state, so not an issue very often) as the fstab loads the mounts BEFORE the VBox additions are run, causing a “not found” error if it is not setup this way)

Special note: the folder name from VirtualBox shared folders is normally the name of the last directory in the path, for example if you are sharing /home/[my username]/Downloads/mystuff – then your VBox shared name will be “mystuff”

***note

you can now visit my Ubuntu 10.04, VirtualBox, and shared folders – a how to

[finndo@fedora12KDE yum.repos.d]$ sudo mount -t vboxsf documents /home/finndo/Documents/local
mount: unknown filesystem type ‘vboxsf[finndo@fedora12KDE yum.repos.d]$ sudo mount -t vboxsf documents /home/finndo/Documents/local
mount: unknown filesystem type ‘vboxsf’
Tagged with: • • • • • • • • • • •
 
16 visitors online now
4 guests, 12 bots, 0 members
Max visitors today: 21 at 08:11 am PST
This month: 26 at 02-09-2012 11:53 am PST
This year: 29 at 01-11-2012 02:49 pm PST
All time: 1100 at 08-08-2011 08:11 pm PDT
View in: Mobile | Standard