[I'm an IT beginner] I tried my best to implement Linux on Windows

greeting

** (If you are not interested, you can skip it!) ** Nice to meet you. This is the first post. Thank you!

I've been in an IT company for the first year since this year, but I'm not good at research, so I'm having a hard time studying programming. (I used to bite programming a little when I was in college, but ... lol)

Even if you search on the internet in various ways ** "Difficult content, long code, rejection ..." ** ** "I can't pinpoint what I want" ** ** "I do not understand English"**

I often think that. Therefore ** "Isn't there a lot of people doing trial and error like myself?" ** I thought that it would be great if I could help people who are having trouble with the same content that I tried and errored, so I decided to start posting this time!

(I'm from biology, but I have the impression that there are many people who say, "I'm not familiar with programming or personal computers, but for the sake of research, I decided to analyze it for the time being (laughs)." is)

That said, there are many articles in the world that have been chewed up, so basically

◆ I looked it up, but (personally) I didn't understand it, it didn't work

◆ I tried it, but I had a hard time finding it

I think it's about writing how you solved the problem.

I think that the content will be poor, but thank you for your cooperation. It's been a long time, but I would like to get into the main subject.

Main subject

The content of this article, ** [Make Linux available on Windows 7 and Windows 10] ** Is the purpose.

That's because I decided to use Linux on my (Windows 10) and my friend's (Windows 7) personal computers.

At first, I was afraid that I would use a virtual machine ...? (= In other words, I thought I would make another virtual computer in my computer; it's okay to listen to it) I was able to implement it without any of that complicated knowledge!

Now, implementation

The following sites helped me implement Linux. I want to use Linux commands on Windows 7: Afterglow of Windows 7

was an atmosphere that seemed to be difficult, so please avoid it. I tried busybox in 2. and Git Bash in 3.

Personally, busyBox was a little inconvenient to use, so I recommend ** Git Bash **! Both were easier than I expected to install. You can use it on Windows 7 without any problems! (Especially busyBox can be installed literally with "one click"!) The installation method of busyBox is described below. [For IT beginners] Make busybox available on Windows

Install Git Bash

Install from the place called Git for Windows which was also linked above.

Of all the research, the site below was the easiest to understand personally. Are you using Git Bash? A surprisingly useful tool that runs on Windows

I will omit the detailed explanation here because many images are pasted and explained. For those who are flirting with the top page of "Git for Windows", when you press the "Download" button, the .exe file will be displayed at the bottom of the screen, so click it. (For Google Chrome) (In Internet Explorer, "Run" or "Save" will appear, so press "Run") git for windows IE.png When you click it, the screen goes dark and you are asked "Do you want to allow it?", So press "Yes" to open the installation screen.

After that, if you proceed according to the site, the installation will be completed. Basically, it should be OK if you keep clicking Next. (Even if there is a page that is not explained in the middle, it is okay if you press "OK" or "Next" without worrying about it.)

Once the installation is complete, type "Git Bash" in the search window at the bottom left and you should see it. You have now implemented Linux inside Windows! git bash.png

Use Git Bash

When it comes to actually doing various things on Linux, it is easier and more convenient to have the data you want to mess with in a place where you can immediately refer to it with ** ls ** or ** cd **. (If you don't know what you're talking about, just go down and it's OK)

To make that possible, Git Bash first opens black screen (= " directory ", in short, "folder" ”) You need to find out where is on your PC . Use the ** pwd ** command to find out.

(If you don't understand what you're saying, read on here) If you type ** pwd ** and press Enter on the black screen that opens when Git Bash starts, the result ** / character / character /… ** will be output as shown in the figure below. git directory.png This ** / character / character /… ** represents ** "in which folder the Linux command operation is performed" **.

In the example of this image, it is ** / c / Users / microsoft , so the stage is now "" Users "in " C: ". You can see that it is in the ** "microsoft" ** folder inside the folder. (Actually, if you type ** ls ** on the black screen when Git Bash starts and press Enter, you will see characters such as "Desktop" and "Document". ** ls ** is a "list up what files and folders are" command)

At the beginning, I said "By moving the data you want to mess with into this ** microsoft folder **, you can play on Linux without thinking about anything extra." .

So, when you play with some data with Git Bash, first try to "** move the data to the folder where it is set **".

** (Supplement) ** Please note that you cannot directly tamper with the "in-desktop" data ** on the black screen when Git Bash starts. You have to specify the path to do that. You might think, "Your desktop data is in the ** microsoft folder **," but that's not the case.

The term "inside the ** folder **" here refers to the "part that is visible immediately after opening the ** microsoft folder **".

In other words, "Move data to ** microsoft folder **" means "put the file in the part that is visible immediately after opening the ** microsoft folder ** ("Desktop ”Or“ Place it alongside the “Document”) ”, so please be careful. (Immediately after opening the ** microsoft folder , you cannot see the data in " on the desktop **", right?)

To mess with the data on the desktop, you need to "move the data to the microsoft folder" or "use the cd command". Or "Specify the data path"

in conclusion

Although it was the first time, I wrote it for a long time. For the part that could not be explained this time, I would like to paste a link (create an article if necessary) at a later date.

I think that there are many expressions that have various misunderstandings, but since the target is "a person who is not familiar with programming and machines like myself", I will write it without worrying about it for the time being. (If it is still clearly wrong, please point it out.)

I hope this article helps someone. Thank you for your careful reading!