Youry's Blog

Youry's Blog

Archive for the ‘UNIX/Linux tricks’ Category

Ubuntu16/Windows2012/CentOS7 cheat-sheet (started 23 May 2016)

leave a comment »

CentOS7

  1. VMWare tools prereq: yum install perl gcc make kernel-headers kernel-devel -y
    http://www.ehowstuff.com/how-to-install-vmware-tools/
  2. aborted yum transactions should be cleaned up: yum-complete-transaction –cleanup-only
    http://forums.fedoraforum.org/showthread.php?t=270035
    http://idroot.net/tutorials/fix-yum-duplicate-packages-broken-dependencies/
    http://forums.fedoraforum.org/showthread.php?t=194254
  3. How to reboot headless server with passphrase? here there are 2 of the best ones I’ve managed to found so far (after spending lots of hours trying out multiple impossible configurations ¬¬):

    https://stinkyparkia.wordpress.com/2014/10/14/remote-unlocking-luks-encrypted-lvm-using-dropbear-ssh-in-ubuntu-server-14-04-1-with-static-ipst/

    https://github.com/chadoe/luks-triple-unlock/blob/master/install.sh

    After configuring the servers that way, one can decrypt the LUKS partition via SSH (using password or rsa-key) or an USB flash drive and let the system boot as usual. Quite useful in my case.

 

Ubuntu 16_04 64bit

  1. Static IP is not updated. Must restart server.

Windows 2012 R2 DC

  1. Firewall must be updated explicitly for the 3389 port to get remote desktop work.

Written by youryblog

May 23, 2016 at 10:11 PM

Posted in IT, UNIX/Linux tricks

Linux / Fedora / CentOS Raid issues

leave a comment »

  1. http://blag.felixhummel.de/admin/raid.html
    how to create raid on large disks:

    gdisk /dev/sdc
    mdadm --create --verbose /dev/md0 --level=1 --raid-devices=2 /dev/sdc1 /dev/sdd1

Written by youryblog

February 9, 2015 at 7:29 PM

Posted in UNIX/Linux tricks

livecd different issues

leave a comment »

Many different options on different OS, especially to test it.

# or simply: sudo yum install kqemu-modules kqemu-common

sudo modprobe kqemu && sudo sh -c 'echo kqemu >> /etc/modules'

Testing:

  • sudo qemu-kvm -m 1024 -hda /dev/sdb

Written by youryblog

April 12, 2014 at 12:29 AM

Posted in UNIX/Linux tricks

IBM SW bugs and some problems solutions

leave a comment »

 

  1. Eclipse 3.6.2 and Fedora 17 Firefox crash eclipse. One possible solution from https://developer.mozilla.org/en-US/docs/XULRunner_1.9.2_Release_Notes
    http://rpmfind.net/linux/rpm2html/search.php?query=xulrunner
    https://bugs.eclipse.org/bugs/show_bug.cgi?id=395915
    http://www.eclipse.org/swt/faq.php#specifyxulrunner
    http://www-01.ibm.com/support/docview.wss?uid=swg21596875

    Most Important!    http://www-01.ibm.com/support/docview.wss?uid=swg21616810

  2. IBM RSA installation and issues solutions
    1. for IBM RSA installation into 64bit you need: https://www-304.ibm.com/support/docview.wss?uid=swg21459143
      sudo yum install gtk2.i686
    2. Installing Rational Eclipse-based products within an existing Eclipse https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Rational%20Installation%20Wiki/page/Install%20into%20an%20Existing%20Eclipse%20instance?lang=en
    3. Follow the link above in order to get the required patches for RSA 8.5:  Rational Software Architect V8.5.0 for IIEE V3.6.2
    4. Initial Eclipse setup instructions for Eclipse 3.6.2 (for newer editions of products)

      This applies to the following products only:

      • Rational Application Developer for WebSphere 8.5.x
      • Rational Software Architect 8.5.x
      • Rational Software Architect for WebSphere 8.5.x
      • Rational Software Architect Realtime Edition 8.5.x
      • Rational Performance Tester 8.3.x
      • Rational Function Tester 8.3.x
      1. Download Eclipse 3.6.2 SDK Classic distribution and extract the compressed file to a local drive on your computer.
      2. Download and extract eclipse.362j7.update.site.zip
      3. Start Eclipse 3.6.2 by using a JRE that is version 7.0.
      4. Click Windows > Preference.
      5. Select Install/Update > Available Software Site.
      6. Click Add and browse to the local directory containing the extracted IBM Eclipse 3.6.2 IIEE update zipsand click OK.
      7. Click Help > Check for Updates.
      8. In Available Updates dialog box, select Eclipse SDK (version 3.6.2.M20120105_1200) and click Next
      9. Continue through the wizard until the update installed.
      10. Select Restart Now when prompted to ensure the new update is installed and validated by Eclipse.
      11. Download and extract patches required by the product.
      12. Click Help > Install Software.
      13. Click Add and browse to the local directory containing the extracted patch zips and click OK.
      14. Disable the Group items by category filter, select to install the patches and click Next.
      15. Continue through the wizard until the patches are installed.
      16. Select Restart Now when prompted to ensure the new patches are installed and validated by Eclipse.

      Note: Install Software is the only supported way to install plugins. Installing them using the dropins folder is not supported and may lead to problems.

      Initial Eclipse setup instructions for Eclipse 3.6.x
      1. Download Eclipse 3.6.0 SDK Classic distribution and extract the compressed file to a local drive on your computer.
      2. Start Eclipse 3.6.0 by using a JRE that is version 6.0.
      3. Click Help > Install Software.
      4. Click Add and browse to the local directory containing the extracted patch zips and click OK.
      5. Disable the Group items by category filter, select to install the patches and click Next.
      6. Continue through the wizard until the patches are installed.
      7. Select Restart Now when prompted to ensure the new patches are installed and validated by Eclipse.

      Note: Install Software is the only supported way to install plugins. Installing them using the dropins folder is not supported and may lead to problems.

      Product install instructions
      1. Start IBM Installation Manager.
      2. Click Install and follow instructions in the wizard to install the product. On the extend an existing version of Eclipse page, select the Extend an existing eclipse check box and then browse to the Eclipse IDE that you set up with all the patches in the Initial Eclipse setup section.

      Note: English is the only supported language when Installing into an existing eclipse.

      Product Update instructions
      1. In order to update a product, you need to download the patches from Download instructions section and follow steps 3 to 8 in Step by Step instructions section
      2. Start IBM Installation Manager.
      3. Click Update and follow instructions in the wizard to update the product.

      Note: English is the only supported language when Installing into an existing eclipse.

Written by youryblog

January 23, 2013 at 7:47 PM

Fedora, wine and Windows applications

leave a comment »

Written by youryblog

November 11, 2012 at 5:46 PM

HTML Editors for the Linux/Fedora

leave a comment »

http://forums.fedoraforum.org/showthread.php?t=22192 – discussion about it. They recommend:
1. Bluefish
2. Quanta http://quanta.sourceforge.net
3. http://www.nvu.com/
4.

Written by youryblog

September 12, 2012 at 10:29 PM

github advises

leave a comment »

Permission to publish:
 Please feel free to put my comments in your blog!  I ended up copying the message to my own website, at the suggestion of one of the other folks who replied.  http://tinylittlelife.org/?p=288  So, whatever’s easiest for you — copying or linking — works for me.  Glad I could help!
 -Ian
++++++++++++++++++++++++++++++++++++++++++++++++++++++
David, I'm CCing the list with my response to the question you had
when we spoke.  Hopefully it will help a few other folks, it's
actually a pretty common use case.

Say that you are following someone else's project on github, and you
want to submit a patch to their code.  Unfortunately you don't have
access to their repository.  Github recommends that you create a fork
of their project -- which is correct -- but from there, their
instructions are less helpful.

So, assuming that you've created a personal fork of their project,
here is how you contribute your code:

First, checkout THEIR project and get into that directory
 $ git checkout git://github.com/their/project.git
 $ cd project

Now, add your fork as a remote repository, and give it the alias "bananas"
 $ git remote add bananas git://github.com/your/fork.git

Make any changes you need to make, "git add" and "git commit" as appropriate.
 $ git add myfile.txt
 $ git commit -m "i made changes"

Get the latest version of their code.  (Note that you are putting your
commits on top of their project's master -- not yours.  This is
correct, and allowed; you just won't be able to push these changes to
their repo.)
 $ git pull --rebase

Since you can't push to their repo, push the changes to YOUR repo
(which you called "bananas"), in a new branch called "onions"
 $ git push bananas master:onions

The above command is taking their master branch with your commits on
top of it and making a new branch in your personal fork.  You could
omit the "master:onions" bit, but then it would by default go into
your "master" branch.  In a perfect world, that would be fine... but
in the real world, they might reject your changes (in which case, you
have a lot of cleanup to do and even more so if you continued to
commit and push).  So make a new branch for every set of changes you
want to submit.  I tend to prefix my branches with the date (e.g.
"2012-06-29_onions").

Now that github has your changes, put their branch back the way that
it was -- keep everything all tidy.
 $ git reset --hard origin/master

If you go to github now, you should see a new branch called "onions"
-- send a pull request based on this branch.  Github just rolled out a
new feature where it notices new branches and gives you a convenient
link to send the pull request (from the main page of your fork, I
believe).

From here, 1 of 3 things will happen:

1. They accept your changes.  You run "git pull --rebase" and get the
now-official code that you contributed.

2. They reject your changes.  You start over from scratch at the
add/commit step (since you reset your branch), and repeat the process.

3. They reject your changes, but you want to keep building on those
changes.  You do "git merge bananas/onions" to pull in the branch that
you were working on, then add/commit to it as appropriate.  Then you
can "git push bananas master:onions" again and update your pull
request on github.

When you are all done with your branch, you can delete it by pushing a
null branch to it:
 $ git push bananas :onions

Good luck!

-Ian

Written by youryblog

July 4, 2012 at 11:18 PM