Posts

Showing posts from August 12, 2018

Changing Master Boot Record (MBR) starting partition address of boot loader

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite From what I understand, the partitioning of the Linux system - when booting from an SD card on an embedded device should look something similar to: I want to move partition 2 up and merge it with the unused space. In this scenario the ordering of the partitions would read 1, 3, 2. According to what I have read, the order of the partitions should not matter as long as the MBR partition start address is modified correctly or the boot loader is modified properly. After extensive googling I am unsure as per how to do this and if I am on the correct path. Any advice would be helpful. Thank you, partition embedded u-boot fpga share | improve this question asked Jun 20 at 19:49 Marty 6 1 In plain English, you want to move what where? Do you have a specific device name in mind, i.e. /dev/sda2 ? – ajeh Jun 20 at 22:20 add a comment  |  up vote 1 down vote favorit

Chrome opens wrong application on Linux even after deleting ~/.config/google-chrome

Image
Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I recently upgraded from Fedora 23 to Fedora 27 which involved installing a new version of Chrome. I then discovered that Java was a pain to start, and in the course of experimenting I ended up telling Firefox and Chrome to open .jnlp extensions with Firefox. Eventually I found the javaws binary and was able to tell Firefox to stop recursively opening itself and to launch /usr/java/latest/bin/javaws %U However, Chrome still launches Firefox for every .jnlp extension (OK, it works with Firefox, but it's messy), but I've been unable to find a way to tell Chrome to use javaws instead. I've done a "egrep -ri 'jnlp|firefox' ~/.config/google-chrome" and deleted several files to no avail. I even deleted the entire ~/.config/google-chrome directory. However Chrome still launches Firefox for every .jnlp extension. I've searched the web and everything talks about setting the default applica

xmodmap key bindings reset when I open a new tab in the shell

Image
Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite When I open a shell in ranger with shift-s, open vim and then open a shell with :sh or open a new shell tab with ctrl-shift-t, my xmodmap keybindings (swapped caps lock and escape keys) are reset. This is what the terminal spits out: xmodmap: please release the following keys within 2 seconds: t (keysym 0x74, keycode 28) Shift_R (keysym 0xffe2, keycode 62) My keybindings are very important to me as I am an active vim user currently working with Typescript (I need quick access to the shell to compile my code). I set my keybindings with xmodmap ~/.Xmodmap (the .Xmodmap file contains my xmodmap commands) and I added that command to my .bashrc. For some more context I am using Ubuntu 16.4 and I recently created a ranger configuration file (~/.config/ranger/rifle.conf) to add support for the .ts file extension. I not an expert ranger or bash user, but both are very important for my workflow. Help would be greatly ap