Linux.com

Home Linux Community Community Blogs

Community Blogs



NOOB's adventures in Linux From Scratch

  You know there's nothing quite so annoying than to have something to us newbies (remember, I'm a roofer by trade.. high school education, no advanced math whatsoever) be a bit of a challenge ... try to cover all the bases as asked , check the FAQ.... go to the mailing list..... check the home page.... Google it.... than to go to some Forum or IRC channel... and have someone belittle us.. or make assumptions....

   This rant is a bit off course of the subject of this blog,  however it's still part of being a Linux NOOB so bear with me as I attempt to share my frustrations with you.

   Last evening I had the misfortune of having the power supply go out on my main Linux desktop machine, Ubuntu linux.  Unfortunately for me I'm no genius far from it.... I happened to be in an "unnamed" IRC channel and asked if a "livecd" could be used to access the hard drive of that broken machine ... but wasn't exacting in my question as they misunderstood me thinking that I was trying to access the main hard drive of the livecd system

   Anyway they came away thinking , that I didn't even know how to mount a filesystem.. and it took me a few minutes to explain to them that that wasn't the issue... somehow I believed until this point that Linux was so secure that their would be issues when after I installed the hard drive out of the now dead box into this computer and tried to mount it that I would have to break security to access those files . Anyway they read into my ignorance about physical access that somehow I didn't know what I was doing mounting a system. I wasn't aware how vulnerable physical access to any hard drive was and that was translated into .... NOOB doesn't even know how to cd to a diff directory..... 

   As great an operating system Linux is and continues to be there will always be someone who want's to look down their noses at people who know less than them.... I've been roofing for 30 years and believe me I could show you a thing or two about commercial roof systems....

    The point I'm trying to bring to the forefront is be prepared there are some trolls out there that seem to hang in the rooms for the purpose of making themselves feel better about themselves. They don't miss the opportunity to humiliate those honestly trying to learn and making every attempt to solve their problem . On the same point,  I have met some very wonderful truly helpful people on the Forums and IRC channels. It goes both ways just be prepared.

  I'm working my way through the Basics part of the Linux User's Guide and will be discussing that very point in the next part of this Blog thanks  

 

 

Wolfram Alpha can't vouch for OOXML legitimacy

Wolfram Alpha went public today, and there is a lot to like about it. For example, Caterina Fake, the co-founder of Flickr and Hunch, wanted to see if W-A could calculate her body mass index, and so she typed in BMI 5'2'', 115lb (her weight and height).  Following her lead, I did the same thing for her BMI, and W-A returned a body mass index of 21.

So I thought I would ask W-A a similarly profound and useful question.  I wanted to know if Microsoft's so-called Office Open XML specification was a true standard or a wolf in sheep's clothing.  I typed "OOXML is a fraud" into Wolfram Alpha. It returned, "I'm sorry, Dave, I'm afraid I can't do that." 

Now compare that to Google.   I typed "OOXML is a fraud" into Google. Google returned 19k results. http://is.gd/Av2

Those of us who follow the OOXML versus ODF standard battle know that OOXML is, in fact, a faux standard, because OOXML is not implemented anywhere.  Not even Microsoft Office implements OOXML.  And Google certainly knows that.  It looks as if, in its first day of public life, Wolfram Alpha is still a wee bit naiive and has a lot to learn.

But it's great for calculating your body mass index! 

 

DDoS

yesterday  my very big company was in DDoS attack to BGP router. Some bed guys from some bad hosts announce many many small routes which our internet providers let no filtering to our router.... and we must to install two very  big BGP routers instead one.

Now I seen problem whith my server in data center , which have two IP. I can't access to him  througt one of this:

first IP has traceroute

 3  v114.TenGig3-2.diamond.volia.net (82.144.193.204)  36.277 ms  39.968 ms  44.108 ms
 4  v254.nexus.dc.volia.com (82.144.193.13)  47.344 ms  51.219 ms  55.052 ms
 5  v254.TenGig3-2.diamond.volia.net (82.144.193.12)  58.094 ms  61.714 ms  65.874 ms
 6  v254.nexus.dc.volia.com (82.144.193.13)  69.775 ms  18.535 ms  24.200 ms
 7  v254.TenGig3-2.diamond.volia.net (82.144.193.12)  20.623 ms  26.716 ms  29.457 ms
 8  v254.nexus.dc.volia.com (82.144.193.13)  32.516 ms  35.019 ms  37.014 ms
 9  v254.TenGig3-2.diamond.volia.net (82.144.193.12)  38.659 ms  40.402 ms  41.155 ms
10  v254.nexus.dc.volia.com (82.144.193.13)  41.891 ms  42.542 ms  43.489 ms
11  v254.TenGig3-2.diamond.volia.net (82.144.193.12)  45.335 ms  47.411 ms  48.523 ms
12  v254.nexus.dc.volia.com (82.144.193.13)  29.573 ms  20.577 ms  18.123 ms
13  v254.TenGig3-2.diamond.volia.net (82.144.193.12)  22.425 ms  26.413 ms  29.236 ms
14  v254.nexus.dc.volia.com (82.144.193.13)  31.932 ms  34.516 ms  36.390 ms
15  v254.TenGig3-2.diamond.volia.net (82.144.193.12)  38.853 ms  41.702 ms  44.200 ms
16  v254.nexus.dc.volia.com (82.144.193.13)  47.044 ms  50.428 ms  55.854 ms
17  v254.TenGig3-2.diamond.volia.net (82.144.193.12)  53.171 ms  59.005 ms  61.930 ms
18  v254.nexus.dc.volia.com (82.144.193.13)  46.787 ms  17.684 ms  17.678 ms
19  v254.TenGig3-2.diamond.volia.net (82.144.193.12)  20.269 ms  22.212 ms  24.312 ms
20  v254.nexus.dc.volia.com (82.144.193.13)  26.279 ms  27.921 ms  33.126 ms
21  v254.TenGig3-2.diamond.volia.net (82.144.193.12)  30.520 ms  35.698 ms  38.417 ms
22  v254.nexus.dc.volia.com (82.144.193.13)  41.145 ms  46.385 ms  50.207 ms
23  v254.TenGig3-2.diamond.volia.net (82.144.193.12)  43.487 ms  52.543 ms  55.218 ms
24  v254.nexus.dc.volia.com (82.144.193.13)  40.172 ms  24.251 ms  21.832 ms
25  v254.TenGig3-2.diamond.volia.net (82.144.193.12)  28.451 ms  32.691 ms  36.638 ms
26  v254.nexus.dc.volia.com (82.144.193.13)  41.136 ms  44.863 ms  48.965 ms
27  v254.TenGig3-2.diamond.volia.net (82.144.193.12)  52.167 ms  55.941 ms  58.676 ms
28  v254.nexus.dc.volia.com (82.144.193.13)  61.225 ms  63.680 ms  68.613 ms
29  v254.TenGig3-2.diamond.volia.net (82.144.193.12)  66.468 ms  70.605 ms  72.224 ms
30  v254.nexus.dc.volia.com (82.144.193.13)  53.406 ms  18.306 ms  17.679 ms


and it don't responding

 

some met with similar pathologies in last days?

 

 

X-Server-Xorg 1.6 and Input-Hotplug

Little more than a month ago Debian unstable was hit by  Xserver-Xorg 1.6 which brings about some changes and new features.
The main changes are with input device handling (mouse, keyboard, touchpad, etc.), which from now on can be handled by HAL instead of X.org.
HAL (hardware abstraction layer) or more precisely hald (hal-daemon) is a service that governs connected devices in realtime (see [2]).

The most important new feature is input-hotplugging (i-h), which handles input devices dynamically.
This results in a considerably simpler and leaner xorg.conf.
After a few weeks of experience with the new features I recommend switching to input-hotplug.  Unfortunately there is no tool yet to handle switching, so depending on your system there might be more or less manual changes needed.

The following howto  explains the most common cases (desktops and notebooks with 1 monitor connected) Part 2 is soon to come and will describe how to handle more than 1 monitor with xrandr and xorg.conf.
Please also read the related links under Web-Links all down the page, I cannot cover the complexity of the matter in this howto.

First of all we save our "current" xorg.conf:

     # cp /etc/X11/xorg.conf /etc/X11/xorg.conf.old

Now we can clean up xorg.conf, it will look (depending on your graphics card) something like:

Section "ServerFlags"
        Option          "DontZap"       "0"
EndSection

Section "Device"
    Identifier    "Device 0"
    Driver        "radeon"
    BoardName    "ATI Technologies Inc M52 [Mobility Radeon X1300]"
    BusID        "PCI:1:0:0"
EndSection


As you can see all input device sections are gone.

WARNING:
Do not copy the above example but modify your own xorg.conf!

The stanza "DontZap"  in the Section "ServerFlags" provides that the key combination  "Ctrl-Alt-Backspace" to restart the x-server still works.
If you do not want that option, set it to  "1"  (instead of "0") or delete Section "ServerFlags"  completely.
Depending on your graphics device you may or even have to add additional options in Section "Device" (e.g. UXA 3D-Acceleration, TV-Out, etc.).

 To enable touchpads we need to copy a file, depending if your make is Synaptics or Alps.

In the appendix you find a synaptics.fdi file, which needs to be copied to/etc/hal/fdi/policy.
Alternativlly the package xserver-xorg-input-synaptics has a .fdi file as well (see [3]).
The synaptic.fdi in the appendix (as well as the other .fdi files in there) is generic.
For touchpads you might want to install gsynaptics to easily enable and change values after copying the file.

      # cp synaptics.fdi /etc/hal/fdi/policy  (synaptic.fdi is in the appendix)
       or
      # cp /usr/share/hal/fdi/policy/20thirdparty/11-x11-synaptics.fdi /etc/hal/fdi/policy

In [4] there are some example fdi files:
- for touchpads
- for tablets
- for activating  special keys with e.g HP and other notebooks (see [5])

Unfortunatelly not all input devices have working fdi files yet.
Should your touchpad be from Alps please use the file alps.fdi from the appendix.
Accordingly for tablets by Wacom please use wacom.fdi  from the appendix or the fdi file in [6].

Web-Links:

[2] /usr/share/doc/hal-doc/spec/hal-spec.html
[3] /usr/share/hal/fdi/policy/20thirdparty/11-x11-synaptics.fdi
[4] /usr/share/hal/fdi/policy/
[5] /usr/share/hal/fdi/information/10freedesktop/30-keymap-hp.fdi
[6] /usr/share/hal/fdi/policy/20thirdparty/10-linuxwacom.fdi
X-StrikeForce Input Hotplug Guide
sidux wiki xorg howto
Brice Goglin's Blog - X.org Howto

Appendix:

synaptics.fdi
wacom.fdi
alps.fdi

 

 

 

Fluxbox basic setup


 

Fluxbox How-to


I've been using Fluxbox for quite some time now and thought maybe I could share some hints, tricks, and such, with anybody who cared to look. This goes past just artwork. Some of the items I write about concern videos, transparency, conkys, and much much more.
Read more... Comment (0)
 

Fluxbox menu setup

Fluxbox Menu

Good menu layout is essential to working with your fluxbox setup.

Read more... Comment (0)
 

Fluxbox startup file

 

Fluxbox Startup File
The Fluxbox startup file located at ~/.fluxbox/startup. This is where you can add programs to start upon entering Fluxbox. 

Read more... Comment (0)
 

Fluxbox init file

 

Fluxbox init file

Here is my ~/.fluxbox/init file. Just copy and paste what you want, or replace yours with this one, as it is 'user independant' and contains may options and features.

Read more... Comment (0)
 

VIZZ.INFO

Virtualisation Information

VIZZ.INFO

 

VOIPPIX.INFO

VOIP Information

voippix.info

 

Fluxbox keys

Fluxbox Keys
Fluxbox gives you an easy way to assign keyboard commands using the file ~/.fluxbox/keys in your ~/.fluxbox folder.
Read more... Comment (0)
 
Page 120 of 139

Upcoming Linux Foundation Courses

  1. LFD331 Developing Linux Device Drivers
    25 Aug » 29 Aug - Virtual
    Details
  2. LFS422 High Availability Linux Architecture
    08 Sep » 11 Sep - Raleigh, NC
    Details
  3. LFS426 Linux Performance Tuning
    08 Sep » 11 Sep - New York
    Details

View All Upcoming Courses


Who we are ?

The Linux Foundation is a non-profit consortium dedicated to the growth of Linux.

More About the foundation...

Frequent Questions

Join / Linux Training / Board