Table of Contents
Fedora pre-install
fedora
Backup wiki
git commit -a -m "install new fedora" git status git push origin master
Note fstab
/dev/mapper/fedora_dai142-lv_root / ext4 defaults 1 1 UUID=b2437fb0-e144-42f3-90de-38a45e2d6998 /boot ext2 defaults 1 2 UUID=8565-CCDE /boot/efi vfat umask=0077,shortname=winnt 0 0 /dev/mapper/fedora_dai142-lv_home /home ext4 defaults 1 2 /dev/mapper/fedora_dai142-lv_swap00 swap swap defaults 0 0 /dev/mapper/vg_nfv_20141023-lv_nfv /mnt/nfv ext4 defaults,auto,noatime,user,rw,exec 0 0 /dev/sdb1 /mnt/extdata ext4 defaults,auto,noatime,user,rw,exec 0 0 /dev/sdb3 /mnt/vm00 ext4 defaults,auto,noatime,user,rw,exec 0 0
Making netinst iso bootable.
Don't need: just dd the netinst. At least work for fed18
Just in case
livecd-iso-to-disk.sh is a Bash shell script from livecd-tools, http://git.fedorahosted.org/cgit/livecd/tree/tools/livecd-iso-to-disk.sh
Note: There are some variations of the script for different versions of Fedora (see livecd-tools summary).
(In reply to comment #1) > Try running isohybrid on the netboot iso before dd'ing it to the USB. My > understanding is that someone forgot to do that on the released iso's. > That is most likely the case: running isohybrid actually did it, after it the image boots and runs the installer normally. I think the mantainers should do the same and update the image(s). Thanks for your help!
creating partition
- Manually… and choose standard partition in the blended section.
- Delete all existing partition (windows).
- create mount point and change to LV
Fedora post install
Troubleshooting
Poweroff because of heating?
install lm_sensors, run sensors-detect
sudo sensors-detect
It looks for sensor and output the following:
Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `coretemp': * Chip `Intel digital thermal sensor' (confidence: 9) Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): no To load everything that is needed, add this to one of the system initialization scripts (e.g. /etc/rc.d/rc.local): #----cut here---- # Chip drivers modprobe coretemp /usr/bin/sensors -s #----cut here---- You really should try these commands right now to make sure everything is working properly. Monitoring programs won't work until the needed modules are loaded.
Run the command and temperature drop from 80 to 50!!!
sensors
VirtualBox 5
Fedora 22/23
/usr/lib/virtualbox/vboxdrv.sh setup
Older kernel-devel may be required
/usr/lib/virtualbox/vboxdrv.sh setup usermod -a -G vboxusers user_name
Troubleshooting
If you have problems with KERNDIR parameter or your kernel directory is not automatically detected then set KERNDIR environment variable manually, using following method: Shell
## Current running kernel on Fedora ## KERN_DIR=/usr/src/kernels/`uname -r` ## Current running kernel on CentOS and Red Hat (RHEL) ## KERN_DIR=/usr/src/kernels/`uname -r`-`uname -m` ## Fedora example ## KERN_DIR=/usr/src/kernels/2.6.33.5-124.fc13.i686 ## CentOS and Red Hat (RHEL) example ## KERN_DIR=/usr/src/kernels/2.6.18-194.11.1.el5-x86_64 ## Export KERN_DIR ## export KERN_DIR ## Current running kernel on Fedora ## KERN_DIR=/usr/src/kernels/`uname -r` ## Current running kernel on CentOS and Red Hat (RHEL) ## KERN_DIR=/usr/src/kernels/`uname -r`-`uname -m` ## Fedora example ## KERN_DIR=/usr/src/kernels/2.6.33.5-124.fc13.i686 ## CentOS and Red Hat (RHEL) example ## KERN_DIR=/usr/src/kernels/2.6.18-194.11.1.el5-x86_64 ## Export KERN_DIR ## export KERN_DIR
Crossover - 32bit windows software
write.thuy@gmail.com
12
Graphic
sudo dnf install libv4l.i686 libmpg123.i686 libmpg123.x86_64
OpenGL
sudo dnf install mesa-dri-drivers.i686 mesa-libGLU-devel.i686
This is needed to run games using textures in the S3TC
sudo dnf install libtxc_dxtn.i686
Choose bottle (OS instance)
Access to webserver from internet
Get Wiki Up and Running
visudo yum install -y vim yum install php cd /var/www/html; ln -s www-local/wiki wiki systemctl start httpd
localtunnel
- progrium.com/localtunnel
installation
sudo yum install ruby-devel sudo yum install gem sudo gem install localtunnel # turn on webserver. default port 8080 localtunnel -k ~/.ssh/id_rsa.pub 8080
Package manager
Repositories
Enabling the repository permanently
The following command will enable the updates testing repository permanently:
yum-config-manager --enable updates-testing
Use yum repolist to verify. If you wish to disable it again, run the following command:
yum-config-manager --disable updates-testing yum distro-sync yum distro-sync will sync the packages to the versions available in the repository and might be useful to run after you disable the testing repository to downgrade packages back to the stable versions.
Note that the yum-config-manager command is available as part of the Package-x-generic-16.pngyum-utils package and should be installed by default. Enabling the repository temporarily
If you'd rather not enable the updates-testing repository permanently but just use it on a case-by-case basis, you can do this with yum. The command:
yum update --enablerepo=updates-testing
will update the entire system using packages from the updates-testing repository, while the command:
yum install <foo> --enablerepo=updates-testing
will install or update only the package named <foo> from the updates-testing repository.
Install Rawhide (bleeding)
For Fedora developers there is an additional package that adds another .repo file with Fedora repositories, /etc/yum.repos.d/fedora-rawhide.repo, also known as rawhide.
su -c "yum install fedora-release-rawhide" sudo yum --enablerepo=rawhide update meshlab
Test an Update
Look at https://admin.fedoraproject.org/updates on the left sidebar and click any of the “testing” links there. It will take you to the list of updates that need testing for that particular build. Prepare a test image
Download the .iso for the image you are testing and start it up in a virtual machine. If you are testing for the release under development, use rawhide. Enable the updates-testing repo
yum --enablerepo=updates-testing check-update
Verify the old behavior
Check for the current behavior of the package you are testing. (If there is a test case listed, follow it.) You will be looking for a difference in this behavior after you install the update, to see whether it adds the functionality or fixes the bug it claims to fix. Install the update
yum --enablerepo=updates-testing update <name of package>
Show installed package
- Red Hat/Fedora Core/CentOS Linux
Type the following command to get list of all installed software
# rpm -qa | less
- Debian Linux
Type the following command to get list of all installed software:
# dpkg --get-selections
- Ubuntu Linux
Type the following command to get list of all installed software:
# sudo dpkg --get-selections
- FreeBSD
Type the following command to get list of all installed software:
# pkg_info | less # pkg_info apache
Use pkgversion command to summarizes the versions of all installed packages: # pkgversion | less
# pkg_version | grep 'lsof'
- OpenBSD
OpenBSD also use pkginfo command to display list of all installed packages or software: # pkginfo | less
# pkg_info apache
Remove rpm package
rpm -qa | grep package_name rpm -e package_name
Save installed packages and reinstall
rpm -qa > fedora18-installed-software.20130529 ## dpkg --get-selections > /backup/installed-software.log ## dpkg --set-selections < /backup/installed-software.log yum -y install $(cat /backup/installed-software.log) * http://docs.fedoraproject.org/en-US/Fedora/14/html/Software_Management_Guide/ch04s08s04.html *
Upgrade single package
This is used when a bug-fix is available but not yet in the repo.
yum install fedora-release-rawhide yum install pkg_name --enablerepo rawhide
Install from Koji
# If erlang-sd_notify-0.1-4 is in the repos then use that.. # If not install directly from koji # NOTE: the link is for x86_64 rpm
yum install -y erlang-sd_notify-0.1-4 || yum install http://kojipkgs.fedoraproject.org/packages/erlang-sd_notify/0.1/4.fc21/data/signed/95a43f54/x86_64/erlang-sd_notify-0.1-4.fc21.x86_64.rpm
Start script
chkconfig --add myscript chkconfig --level 2345 myscript on
Check the script is indeed enabled - you should see “on” for the levels you selected.
chkconfig --list | grep myscript
common packages
yum
– presto-utils yum-presto
rpmfusion
http://rpmfusion.org/Configuration/
For F14 to Latest
su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm'
Input
QA:Testcase i18n input method setup
Description
This test case is to set up the input method to get it working on the desktop.
How to test
For GNOME3
Open the System Settings from Activities -> Applications -> System Tools or click on the your name at the upper right corner
Select the Region & Language and the Input Sources tab
Add your preferable input source and layout if not there.
Optionally, click on the shortcut settings and assign anything you prefer. for compatibility, click on Switch to next source and press Control key and space key at the same time.
Click the 2-letter language icon on the panel and select the input source
or press the shortcut key which configured the above optional step
For others
Select Input Method Selector from the desktop menu or run im-chooser from the terminal
Select Use IBus, then click Prefrences... at the right side.
Open Input Method tab
See if there are any input method engine you want to use.
If not available, turn on Customize active input methods and select one from the pull down menu. then click Add button.
Click on the ibus icon and select the engine
or press Ctrl+space
Follow up to the steps in QA:Testcase i18n input method setup to configure the input method on the desktop in general.
Install ibus typing booster using following command
yum install ibus-typing-booster
yum install pyhunspell
(this is optional, but if pyhunspell is installed as well, one will not only get completions but also spelling corrections
Add some input sources which have (Hunspell) in the name. If there are no such input sources in the list, run the following command and restart the desktop.
gsettings set org.gnome.desktop.input-sources show-all-sources true
Gnome-shell Desktop
yum install dconf-editor gnome-tweak-tool dconf-editor
Themes
yum search gnome-shell-theme
Moka Theme:
http://mokaproject.com/moka-gnome-shell-theme/download/
Fedora 20
Get moka
sudo wget http://download.opensuse.org/repositories/home:/snwh:/moka-gnome-shell-theme/Fedora_20/home:snwh:moka-gnome-shell-theme.repo -O /etc/yum.repos.d/moka-gnome-shell-theme.repo sudo yum update sudo yum install moka-gnome-shell-theme
Install moka
Moka requires the GNOME Shell extenstion “User Themes”.
After installation, you should be able to choose your preferred theme using GNOME Tweak Tool.
gnome-extensions
- User theme from user directory: https://extensions.gnome.org/extension/19/user-themes/
Nautilus
yum install nautilus-actions
Intel Graphic - detect screen resolution
Fedora 19
On 02/01/2013 01:16 AM, Felix Miata wrote: > On 2013-02-01 00:47 (GMT-0800) Per Bothner composed: > >> Xorg.0.log is available at: http://per.bothner.com/tmp/F18-Xorg.0.log > > It says your cmdline contains nomodeset. > >> The former does seem to be loading the VESA driver. > > Intel driver does not work with nomodeset on cmdline, so X falls back to > VESA, which doesn't do widescreen modes. Thanks! I manually edited /boot/grub2/grub.cfg to remove the nomodeset options, and that fixed the problem. I then removed it from GRUB_CMDLINE_LINUX in /etc/default/grub, so hopefully it won't re-appear. That leaves the question is where did this come from in the first place? I did a clean install of Fedora 18. However, I did have a few older partitions on the disk, and perhaps the Fedora 18 installer used data from those other partitions to initialize /etc/default/grub. Sees strange, but that is all I can think of. Unless there is a bug in the Fedora 18 installer ...
xfce Desktop
Volume control button
yum install xfce4-volumed.x86_64
Mouse
Goto mouse setting to enable scrolling etc.
Dual monitor
xrandr -q xrandr --output LVDS1 --auto --output VGA1 --auto --right-of LVDS1
Pimp xfce desktop
developing environment
compiler etc
yum groupinstall 'Development Tools' yum groupinstall 'Development Libraries' gcc gcc-c++ make autoconf automake gawk binutils gdb bison flex build-essential kernel-devel openssl-devel zlib zlib-devel make ant libtool httpd-devel php-devel mysql-server mysql-admin mysql-query-browser mysql-devel php php-mysql ctags-etags.x86_64
database
web
apache2 httpd httpd-devel php php5 php-mysql yum install ntp httpd mysql-server php php-mysql php-mbstring php-mcrypt phpMyAdmin ## disable selinux and reboot systemctl enable httpd.service systemctl restart httpd.service ## old chkconfig --levels 235 httpd on /etc/init.d/httpd start
PHP
yum install php php-devel php-gd php-imap php-ldap php-mysql php-odbc php-pear php-xml php-xmlrpc php-mbstring php-mcrypt php-mssql php-snmp php-soap php-tidy curl curl-devel perl-libwww-perl ImageMagick libxml2 libxml2-devel mod_fcgid php-cli httpd-devel
editor
vim-enhanced bluefish dia asciio freemind texlive-latex.noarch
Graphic
yum install gimp inkscape
net tools
traceroute mtr wireshark* nmap avahi avahi-tools
etc
imagemagick
Java dev
2.1 java devel
java-1.6.0-openjdk-devel java-1.6.0-openjdk-javadoc java-1.6.0-openjdk-plugin
3. fix GDK issues vim /etc/profile
GDKNATIVEWINDOWS=1 export GDKNATIVEWINDOWS
JAVAHOME=“/usr/lib/jvm/java” export JAVAHOME
- yum install system-config-display
Virtualization
IP-Forwarding
Edit it to read as follows:
net.ipv4.ip_forward = 1
Use the following command to enable the change to the sysctl.conf file:
[root@myServer ~ ] # sysctl -p /etc/sysctl.conf qemu-kvm.x86_64 qemu-kvm-tools.x86_64 uml_utilities.x86_64 bridge-utils.x86_64
Nested KVM
SSH
yum install openssh-server openssh
Django dev
yum install python-virtualenv.noarch yum install python-pip.noarch
.bashrc .bash_profile
# User specific aliases and functions JVM_ROOT=/usr/lib/jvm JAVA_HOME=$JVM_ROOT/java export JAVA_HOME JBOSS_HOME=/home/td/data/devfs/opt/jbossAS export JBOSS_HOME M2_HOME=/home/td/data/devfs/maven export M2_HOME ANDROID_SDK=/home/td/data/devfs/opt/android-sdk-linux ANDROID_NDK=/home/td/data/devfs/opt/android-ndk-r7 # PATH=$PATH:$JAVA_HOME/bin:$M2_HOME/bin:$JBOSS_HOME:$ANDROID_SDK/tools:$ANDROID_SDK/platform-tools :. export PATH
yum package installation location
rpm -ql package_name
Fedora hostapd
ERROR: can't set AP mode with intel driver iwl3945.
useful command
- iw list
...
supported mode:
...
- systemctl start|stop|enable|disable servicename.service * service start|stop servicename
Multimedia
rpm -Uvh http://rpm.livna.org/livna-release.rpm yum install gstreamer-plugins-bad gstreamer-plugins-bad-free-extras gstreamer-plugins-bad-nonfree gstreamer-plugins-ugly gstreamer-ffmpeg ffmpeg mencoder ffmpeg2theora mplayer libdvdcss yum install gstreamer1-libav gstreamer1-plugins-bad-free-extras gstreamer1-plugins-bad-freeworld gstreamer1-plugins-base-tools gstreamer1-plugins-good-extras gstreamer1-plugins-ugly gstreamer1-plugins-bad-free gstreamer1-plugins-good gstreamer1-plugins-base gstreamer1 yum install libdvdread libdvdnav lsdvd libdvdcss libdvdcss2 regionset
Wheather and Maps
yum install gnome-weather yum install gnome-maps
Sun java
- download rpm package
yum install *.rpm
alternatives
## java ## alternatives --install /usr/bin/java java /usr/java/latest/jre/bin/java 20000 ## javaws ## alternatives --install /usr/bin/javaws javaws /usr/java/latest/jre/bin/javaws 20000 ## Java Browser (Mozilla) Plugin 32-bit ## alternatives --install /usr/lib/mozilla/plugins/libjavaplugin.so libjavaplugin.so /usr/java/latest/jre/lib/i386/libnpjp2.so 20000 ## Java Browser (Mozilla) Plugin 64-bit ## alternatives --install /usr/lib64/mozilla/plugins/libjavaplugin.so libjavaplugin.so.x86_64 /usr/java/latest/jre/lib/amd64/libnpjp2.so 20000 ## Install javac only if you installed JDK (Java Development Kit) package ## alternatives --install /usr/bin/javac javac /usr/java/latest/bin/javac 20000 alternatives --install /usr/bin/jar jar /usr/java/latest/bin/jar 20000
source
Java - maven
yum install maven.noarch
# .bash_profile
# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
# Java
# Location of jar files on the system
JAVA_LIBDIR=/usr/share/java
# Location of arch-specific jar files on the system
JNI_LIBDIR=/usr/lib/java
# Root of all JVM installations
JVM_ROOT=/usr/lib/jvm
# Oracle java root
OJAVA_ROOT=/usr/java/latest
# You can define a system-wide JVM root here if you're not using the
# default one.
#
# If you have the a base JRE package installed
# (e.g. java-1.6.0-openjdk):
#JAVA_HOME=$JVM_ROOT/jre
#
# If you have the a devel JDK package installed
# (e.g. java-1.6.0-openjdk-devel):
JAVA_HOME=$JVM_ROOT/java
export JAVA_HOME
# User specific environment and startup programs
export M2_HOME=/home/td/data/programming/maven
export M2=$M2_HOME/bin
GRAILS_HOME=/home/td/data/programming/grails
export GRAILS_HOME
PATH=$PATH:$HOME/bin:$M2:$GRAILS_HOME/bin
export PATH
NS3
yum install gcc gcc-c++ python python-devel yum install mercurial yum install bzr yum install gsl gsl-devel yum install gtk2 gtk2-devel yum install gdb valgrind yum install doxygen graphviz ImageMagick yum install python-sphinx dia texlive texlive-latex yum install flex bison yum install tcpdump yum install sqlite sqlite-devel yum install libxml2 libxml2-devel yum install uncrustify yum install boost-devel yum install graphviz graphviz-devel python-setuptools-devel python-kiwi pygoocanvas sudo easy_install pygraphviz
openmpi
yum install openmpi-devel
Add library path:
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib64/openmpi/lib
Add PATH:
# OpenMPI LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib64/openmpi/lib OpenMPIBIN=/usr/lib64/openmpi/bin;/usr/lib64/openmpi/lib PATH=$PATH:$HOME/bin:$M2:$GRAILS_HOME/bin:$ANDROIDSDK/platform-tools:$OpenMPIBIN export PATH
Fedora does not install the required compiler executables under default /usr/bin, /usr/sbin or /usr/local/bin, etc. and libraries under default /usr/lib or /usr/lib64, etc., but under /usr/lib64/openmpi/bin and /usr/lib64/openmpi/lib. And the $PATH variable is not updated to include these paths. This results in “mpicc: Command not found” error when you try to issue such commands.
source: http://mmanoba.wordpress.com/2011/07/03/howto-openmpi-under-fedora15-and-sample-c-program/
Eclipse
Add to eclipse.ini
-Dosgi.requiredJavaVersion=1.5 -Dhelp.lucene.tokenizer=standard # not needed for jvm 8. -XX:MaxPermSize=512m -Xms512m -Xmx2048m
Subclipse
- if the svn-client is too old, goto market place and install latest subclipse version.
- Install svnkit from subclipse update site then in perferences → Team → SVN choose java native client.
Theme
F28
Old
System uses dark theme:
- select eclipse darktheme
- create eclipse.sh
export SWT_GTK3=1 export GTK_THEME=Adwaita:dark $(dirname "$0")/eclipse
Use eclipse Light theme
export SWT_GTK3=0
——————-
Editor theme
- install eclipse-color-theme: http://eclipse-color-theme.github.io/update/
- OR using marketplace, install devstyle
- goto preferences → appearance → color theme and select one!
Vim keyboard
- search vim in market place
- Vrapper
Marketplace
- Help → Install new Software → Switch to the Kepler/Luna/Neon Repository → General Purpose Tools → Marketplace Client
Android SDK
Requred for Fedora 20
32bit libs are needed for x86_64 env.
yum install glibc.i686 glibc-devel.i686 libstdc++.i686 zlib-devel.i686 ncurses-devel.i686 libX11-devel.i686 libXrender.i686 libXrandr.i686
Firewall
Disable firewalld and enable inptables/6
yum install iptables-services systemctl mask firewalld.service systemctl enable iptables.service systemctl enable ip6tables.service
Use /etc/sysconfig/iptables and /etc/sysconfig/ip6tables for your static firewall rules.
Note: The package iptables and iptables-services do not provide firewall rules for use with the services. The services are available for compatibility and people that want to use their own firewall rules. You can install and use system-config-firewall to create rules with the services though. To be able to use system-config-firewall, you have to stop firewalld.
After creating rules for use with the services stop firewalld and start the iptables and ip6tables services:
systemctl stop firewalld.service systemctl start iptables.service systemctl start ip6tables.service
Network interface name
To use the old name install “biosdevname” which creates udev rules for network.
KVM
yum install bridge-utils tunctl libvirt qemu-kvm
Vagrant
vagrant-kvm plugin:
Error:
/opt/vagrant/embedded/lib/ruby/2.0.0/mkmf.rb:434:in `try_do'
Problem description: https://github.com/pradels/vagrant-libvirt/issues/290
CONFIGURE_ARGS="with-libvirt-include=/usr/include/libvirt with-libvirt-lib=/usr/lib64" vagrant plugin install vagrant-libvirt
Google Chrome browser
sudo yum-config-manager --add-repo=http://repos.fedorapeople.org/repos/spot/chromium-stable/fedora-chromium-stable.repo sudo yum install chromium -y
Firefox performance (wayland)
Wayland issues (Fedora 25)
- Java GUI crashes, affecting jabref, ecipse?
java -jar jabref-x-x error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007ff581f2c038, pid=6974, tid=140692392957696 # # JRE version: Java(TM) SE Runtime Environment (8.0_91-b14) (build 1.8.0_91-b14) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.91-b14 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libawt_xawt.so+0x42038] ReadRegionsInList+0x3b8 # # Core dump written. Default location: /home/dang/data/mydirectory/mywork/dailabor/00--current/00_dai_pjs_actual/90_publications/20_Network_management/network-management-paper/core or core.6974 # # An error report file with more information is saved as: # /home/dang/data/mydirectory/mywork/dailabor/00--current/00_dai_pjs_actual/90_publications/20_Network_management/network-management-paper/hs_err_pid6974.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. #
Fedora 22 - Firefox and dark theme
~/.mozilla/firefox/xxxxxxxx.default/chrome/userContent.css or using stylish add-on.
The following sets input fields to standard black text / white background; both can be overridden by the displayed site, so that colors are seen as intended:
input {
-moz-appearance: none !important;
background-color: white;
color: black;
}
textarea {
-moz-appearance: none !important;
background-color: white;
color: black;
}
select {
-moz-appearance: none !important;
background-color: white;
color: black;
}
Phonegap emulation
- Ripple emulator extension: https://chrome.google.com/webstore/detail/geelfhphabnejjhdalkjhgipohgpdnoc/
- Usage: browse to emulate.phonegap.com and enter the local URL.
Launch website
Using httpd or better,
python -m SimpleHTTPServer 8000
Input the url to the emulator.
rsync
rsync -r -a -v -e "ssh -l root" --delete 130.149.232.136:/var/www/* /var/www/ ## resume copy rsync -r -a -v -e "ssh -l root" --progress --update 130.149.232.136:/var/www/* /var/www/ # omit symlinks rsync -r -a --no-links -v -e "ssh -l root" --progress --update SRC/* DEST/var/www/
fstab
https://wiki.archlinux.org/index.php/fstab
- get blockid blkid /dev/sda1 will get you the uuid and then add:
UUID=YOUR-UID /mountpoint ext4 defaults,auto,noatime,user,rw,exec 0 0
- Permission for ntfs, vfat: use umask.
- Perminssion for ext4:
Ext3 file systems have real ownership and permissions, with the default owner being root:root, with the permisions shown above. Unlike FAT* file systems which don't ownership at all and limited permissions. The vfat filesytem has *mount* options to fake UNIX ownership and permissions (and when mounting a vfat filesystem, the file system by default inheirits the UID of the user running mount). For an ext3 file system, you just change the actual permissions of the root of the file system: After mounting the disk do this (as root): chmod go+w,+t /bigdisk This will allow anyone to create files on the disk (Group and Other get Write access). The +t prevents one user from deleting another user's files.
turn off bluetooth
echo “disable”
>/proc/acpi/ibm/bluetooth
O
ne probably needs to replace 'ibm' by the type of his acpi (like 'asus' or 'toshiba') to make it work: just find a subdir of /proc/acpi that contains file named 'bluetooth'.
Cheers
Vim
- vim-latex.noarch : Tools to view, edit and compile LaTeX documents in Vim
- texlive.noarch
Customize Gnome-shell
shortcut launcher
Adding application launcher
su -c 'yum -y install gnome-panel' su -c 'gnome-desktop-item-edit --create-new /usr/share/applications/'
Or, if you have unlocked the desktop, you can make a shortcut
su -c 'yum -y install gnome-panel' gnome-desktop-item-edit --create-new ~/Desktop
Fedora 20-21-22
You can create a “.desktop” file in “~/.local/share/applications”, then the specified “Icon” Should show up in the Gnome Shell Menu ( You may, or may not need to reload the shell: “alt-F2, r <enter>” )
$ cat ~/.local/share/applications/ut2004.desktop # cat /usr/share/applications/ut2004.desktop [Desktop Entry] Type=Application Encoding=UTF-8 Name=Unreal Tournament 2004 Comment=Unreal Tournament 2004 Exec=/home/joe/Games/ut2004/ut2004 Icon=/home/joe/Downloads/ut2004.png Terminal=false
Restart Shell
Alt + F2 then 'r' and Enter
Change Default application
vim ~/.local/share/applications/default.list
Menu Edit
App for adding launcher
Emails problems
Evolution can't send mails
solution 1: May be problem with keyring. Try sending in gnome-shell first so keyring is updated. Then swicht to safe-mode.
solution 2: Recreate keyring file in each new desktop environment (lxde, safe mode…).
solution 3: http://hongouru.blogspot.de/2012/07/solved-warning-gnome-keyring-couldnt.html
yum install seahorse
Bugs & Problems
xfce keyring
Fedora 18. xfce seems to have problem with keyring https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/932177 . This makes evolution etc. can't correctly get the keys when in other desktops than gnome.
Solution
I would suggest the following workaround for now:
1. Open the Session settings:
Settings -> Preferences -> Settings Manager -> Session and Startup
2. Enable GNOME compatibility mode:
Go to Advanced, check "Launch GNOME services on startup"
3. Disable unwanted GNOME-only autostart files:
Execute the following one-liner on the shell:
for gnome_autostart in $(awk '/^OnlyShowIn=/ && /GNOME;/ && !/XFCE;/ { print
FILENAME }' /etc/xdg/autostart/*); do sed '$aHidden=true' ${gnome_autostart}
>${HOME}/.config/autostart/${gnome_autostart##*/}; done
I'll talk to upstream later and see if we can move gnome-keyring support out of GNOME compatibility mode.
keyring Grrrr
td 2221 5.9 0.7 662304 15436 ? SLl 16:54 0:03 /usr/libexec/gcr-prompter td 2509 0.0 0.0 109180 868 pts/0 S+ 16:55 0:00 grep --color=auto prompt