Knowledge Collections written in Markdown.
| 1. Enable the Fedora 19 YUM Repository for CentOS | |
| http://paperiniktips.sviluppo-siti-web.com/how-to-enable-the-fedora-19-yum-repository-for-centos/ | |
| Get the Release.key | |
| http://paperiniktips.sviluppo-siti-web.com/how-to-install-fedora-19-gpg-key/ | |
| rpm --import /mnt/Release.key | |
| vi /etc/yum.repos.d/f19.repo |
| #!/bin/zsh -e | |
| cd ~/tmpfs | |
| mkdir -p .lxc-root .lxc-data/root/etc .lxc-work | |
| sudo GDK_DPI_SCALE=$GDK_DPI_SCALE zsh -e - <<'EOF' | |
| chown 0:0 .lxc-data/root .lxc-data/root/etc | |
| modprobe overlay | |
| mountpoint .lxc-root || mount -t overlay -o lowerdir=/,upperdir=$PWD/.lxc-data/root,workdir=$PWD/.lxc-root overlayfs $PWD/.lxc-root |
Fonte: http://brandon.invergo.net/news/2012-05-26-using-gnu-stow-to-manage-your-dotfiles.html?round=two
I accidentally stumbled upon something yesterday that I felt like sharing, which fell squarely into the "why the hell didn't I know about this before?" category. In this post, I'll describe how to manage the various configuration files in your GNU/Linux home directory (aka "dotfiles" like .bashrc) using GNU Stow.
The difficulty is that it would be helpful to manage one's configuration files with a version control system like Git, Mercurial or Bazaar, but many/most dotfiles reside at the top-level of your home directory, where it wouldn't be a good idea to initialize a VCS repository. Over time I've come across various programs which aim to manage this for you by keeping all the files in a subdirectory and then installing or linking them into their appropriate places. None of those programs ever really appealed to me. They would require a ton of dependencies (like Ruby and a ton of libraries for it) or t
| #!/bin/bash | |
| # You must accept the Oracle JDK License Update | |
| # https://www.oracle.com/java/technologies/javase-downloads.html | |
| # usage: get_oracle_jdk_x64.sh <jdk_version> <platform> <ext> | |
| # jdk_version: 14 | |
| # platform: linux or osx or windows | |
| # ext: rpm or dmg or tar.gz or exec | |
| jdk_version=${1:-14} |
Simple way to setup an arm chroot for building packages for your arm devices. This is an alternative to cross-compiling where you are limited to only linking against the libs in your toolchain.
You can store the chroot wherever you like. I choose to store it in a disk-image which I mount to my filesystem.
| [Desktop Entry] | |
| Version=1.0 | |
| Name=Aurora | |
| GenericName=Web Browser | |
| Comment=Browse the Web | |
| Exec=/home/user/firefox/firefox-bin -P aurora %u | |
| Icon=/home/user/firefox/browser/icons/mozicon128.png | |
| # Icon=aurora | |
| Terminal=false | |
| Type=Application |
| #!/bin/bash | |
| # MythCutKey Version 0.15e | |
| # This script cuts myth recordings at key frames using the MythTV seek table. | |
| # Why? No external programs required, lossless and fast. | |
| # Updates the myth database with sql calls. | |
| # Rebuilds output file seek table with mythutil (mythcommflag at present). | |
| # Output files may NOT be easily editable again and may have glitches at cut points. | |
| # | |
| # Undo option allows restoration of original recording and associated database |