Showing posts with label linux. Show all posts
Showing posts with label linux. Show all posts

Thursday, June 6, 2019

How to Run Redox OS for Fun

How to run Redox OS, an OS written in Rust, on QEMU
Redox OS is an entirely new breed of an Operating System built with Rust programming language. It is still small, has only the basic programs but fun to run none the less.

Wednesday, May 15, 2019

How to Install and Use Brother HL-2130 Laser Printer on Debian

Brother HL-2130 laser printer driver installation on Debian Linux
There was an old laser printer which I had to make use of recently. It was a monotone Brother HL-2130 printer. I found a solution for Debian (but not yet for Arch).

Thursday, May 9, 2019

How I Fixed Thinkpad Trackpoint Not Scrolling When Plugged In

On a ThinkPad T60, my dearly beloved TrackPoint, the little rubber thingy in the middle of the keyboard, was not scrolling stuff. But I think I found a solution.

Monday, February 11, 2019

Playing With Fixes for Atheros Wifi Card Not Connecting on Parabola (Arch Linux)

I had a weird case that my laptop wifi does not connect to the internet. It was a librebooted machine with an Atheros wifi chipset. It runs internally as "ath9k" (as lcpci -v indicates). I have looked through many solutions but they did not solve it completely.

Thursday, December 13, 2018

Prepare a Lightweight Linux Distro - Slax - to Play with!

I felt like one Linux install is not enough! That's why I got myself another to play with inside my existing one!

Tuesday, November 27, 2018

Running Automated Tests on Websites using Codeception

Automated website testing blog post thumbnail - robot saying "Test! Test! Test!"
Testing some website after update or any change can be a boring task at times. Wouldn't it be great if we can automate the testing with a virtual, invisible browser robot thingy?

Thursday, September 6, 2018

Solving Funky Problems on Arch Linux with Linux LTS Kernel

I have many installations of Arch. I also have installations of Parabola, which is a strict Free Software Operating System which does not have any closed source bits that normal kernel has. It is just linux, minus all the binary blob nonsense stuff. Arch usually has "linux" installed, and Parabola has "linux-libre". I love to use Parabola on my Librebooted Thinkpad T60. Completely Free system from BIOS to OS. But I faced some issues, and Linux LTS solved those for me.

Sunday, May 6, 2018

How to build Textadept from Source

Textadept - a lightweight text editor - how to compile
There are loads of text editors out there. But if you want a lightweight texteditor that is extendable up to your keystrokes, you want Textadept. Today we see how to compile it from source and extend even more.

Sunday, September 10, 2017

How to install XAMPP in Linux and make WordPress update work perfectly!

Installing XAMPP properly so that Wordpress runs smoothly on Linux
We have all been there... when we try to update something in Wordpress in Linux and it does not update. Even debug.log does not create. It is most of the time a permission issue. But Windows does not suffer from it. So, why should Linux have this issue? Fear not, we have a solution!

Step 1: Install XAMPP (LAMPP)

If you have not installed XAMPP yet on your linux machine, then first do so. I have written a tutorial here.

Step 2: Create Group for XAMPP Users and put yourself in!

* Replace "username" with your username.

sudo groupadd xamppusers
sudo usermod -a -G xamppusers username
groups username

The last command will show you the groups that your username is in. If you have xamppusers group in the list, then you are good.

Step 3: Own the files!

Run this:

cd /opt/lampp
sudo chown -R username.xamppusers htdocs
sudo chmod -R 775 htdocs

This will relax the file permissions of your htdocs folder, so you have less trouble. And also change the owners to the username you chose. You will taste great feedoms when editing files and modifying files with php after this.

Step 4: Edit the httpd.conf

httpd.conf is the configuration file for Apache.

First backup the conf file:
sudo cp /opt/lampp/etc/httpd.conf /opt/lampp/etc/httpd.conf.bak

Edit the file:
sudo nano /opt/lampp/etc/httpd.conf

You will find two lines saying something like this:
Tip: You can press Ctrl+W, type user daemon and press enter to find it quickly.
User daemon
Group daemon

Editing the httpd.conf with nano in linux cli

Replace it with your values, something like this:
User username
Group xamppusers

Step 5: Restart XAMPP

This step is very important. If you do not do this the changes you made in httd.conf file will not be taken.
sudo /opt/lampp/lampp restart
or, use the GUI Control Panel if you have it.

Bonus Tip: Accessing htdocs from home directory

ln -s /opt/lampp/htdocs/ ~/htdocs

You will then be able to see a link to the "htdocs" folder in your home folder. This is so convenient for accessing files on htdocs.

Conclusion

After doing all this hard work you will be able to install Wordpress without any permission issues whatsoever. Also update Wordpress without any problem.

Plugin update also works!

Wordpress Plugin updates without any issue


Tuesday, May 10, 2016

Typing in Bangla using Unijoy on Arch Gnome

Unijoy is my favorite keyboard layout to type Bangla in Linux and Windows. In this short article I give you the instructions to type in Bangla in any Arch based Gnome Distro. I have tested this on Manjaro Gnome 15.12 (updated to Gnome 3.20.1).

Wednesday, April 27, 2016

How to install Ubuntu 16.04 LTS inside Windows without partitioning

Linux without the hassle of partitioning. How to do it? Here is the answer. You can uninstall whenever you want!

Thursday, December 17, 2015

How to install Linux on Pendrive using F2FS Filesystem

Well, F2FS filesystem is specially designed by Samsung which is good for SSDs and pendrives. It makes the read and write operations on the devices much faster, because it is specially designed for those mediums. Even take a look at these benchmarks to prove that F2FS performance is better.

Tuesday, December 2, 2014

How to use SVN client with GitHub

I am used to SVN (SubVersioN) rather than git. I kind of hate git, maybe because its command line is harder for my brain to digest. Hopefully, GitHub supports both git and svn.

If you are like me you would be interested in using SVN with github repositories. In this post we are going to learn how to do just that.

Got Client?

Make sure you have svn client installed. I am comfortable with svn command line. In windows I use Win32SVN which lets me use svn commands directly in the command prompt.

1. In windows, run cmd. In Ubuntu/Linux, start the terminal (Don't ask me how. If you are using linux you're probably smart enough to figure this out yourself!)

2. Now type svn --help and then press enter. If you see usage instructions you have svn installed. Now skip to the next part.



If you don't have SVN installed,
On Windows, install Win32SVN. You may have to restart after installation.
On Ubuntu, run: sudo apt-get install subversion
On other linux distro except Ubuntu/Debian, refer to your package manager documentation to install subversion.

How to Checkout (Download files from a repo)

In the world of version control, Checkout is a fancy way of saying download a copy of the current repository (or repo). Each project is kept under a repository. Repo link for its page on github follows this format:
https://github.com/{user name}/{repo name}

Let's say we will be working with:
https://github.com/adnan360/cvstatichtml

1. Now go to the repo link with your browser (go to the above link if you don't have one). You will find an url under the title "HTTPS clone URL". Click Subversion to get an URL for SVN. Copy that url. [The url is usually like: https://github.com/{user name}/{repo name} Although you could use the github page link above but I showed that if you forget which url to use. ]



2. Now open command prompt or terminal. cd to a proper directory.

In Windows, you can use a shortcut to cd to a directory. Just open a directory in explorer, hold down Ctrl+Shift and right click, then select "Open terminal window here".

Don't worry about creating a directory. A directory with the name of the repo will be created.

3. Type svn co followed by a space. Then right click and select paste. Example:

# svn co --depth empty https://github.com/adnan360/cvstatichtml

It will take some time to download the repo.



4. Now cd to the repo directory. Example:

# cd cvstatichtml

(We will need this cd command for executing later commands.)

5. Now run:
# svn up trunk
# svn up --depth empty branches


The commands above will prepare you to modify the code.

How to modify code

In github, it is extremely recommended that you create a copy of the code in a separate directory then modify it. We copy the whole code in a "branch" then edit it. This way the original code is left untouched and safe from our goofy coding!

1. Create a branch:
# svn up trunk
# svn copy trunk branches/my_awesome_update
# svn commit -m "Added a new branch"

Replace /my_awesome_update to something more personal to you. "Added a new branch" is just a message to identify this change to the repo (that you just made a branch). This will later help you to merge.



The trunk directory contains the downloaded code which is untouched. We copy the untouched code to branches/my_awesome_update. We would edit the code under that directory.

2. Now go to you {repo directory}/branches/my_awesome_update and make your changes.


How to send your code to GitHub (Yaaayy!)

If you've followed previous steps correctly, now its easy to send your update to github.

1. Let's see the file status:

# svn status

This will say which files were changed.

2. If you see a Question Mark (?) beside some files (in the svn status output), then add these files (or directories) to the repo with:

# svn add {file or directory}

This is a bit boring sometimes but cool once you've done it.

Now check again with an svn status to see if you got any ? marks still. If you get any, use avn add "xxx" to add them.

3. Send changes:

# svn commit -m "My awesome new update"

Replace "My awesome new update" with your own description of the change.

Now you have it! You can submit your code to github! With SVN! How cool is that!

Ref: https://help.github.com/articles/support-for-subversion-clients/
EDIT: SVN URL fixed