My voyage to Linux on hiatus due to Virtual Box mishap!!!
So with the lock down and world wide pandemic, it gave me time to get back to this blog. I guess most of us will be able to take some time to get back into some of the things we were too busy to do before. It is forcing me to get back into learning more about computers, Linux and blogging.
So here we go, I have given up on my new linux laptop, for now. I will explain. My voyage to Linux has taken a hiatus. This is why.
I was beginning to work with the terminal and wanted to practice without necessarily working and practicing on the linux shell itself that I had installed on my HP laptop; (I did not want to Sudo something and then screw up my new Mint operating system. )
So I checked on REDDIT and other forums online and found that a virtual terminal (Virtual BOX) might be the solution. At the same time I would be able to try out a new distro. I would be able to practice commands in a terminal that would not affect my Mint OS and then maybe also try a new distro such as SUSE, Redhat, or Ubuntu. Two birds one stone.
So I manage to properly install Virtual Box. This seems to have worked well. NB. I have linux Mint installed on a partition CPU with windows. I then proceeded to download the images from an Ubuntu installer as well as a SUSE one.
This is where it gets complicated. What happened is that I opened Ubuntu with the Virtual Box and had to partition the disk (this is within the VB). So I did that and it started to upload but then would not open because it said my laptop was not a 48-bit system or something like that. (Please bare with me as you must know I am pretty computer illiterate so my explanations and terminology are probably wrong, as well it has been quite a while since this happened so I cannot remember all the exact details.) So Ubuntu would not open up. It would get to the start screen so it appeared, but then give me a message about my laptop bits.
I then proceeded to unistall it and remove it through the VB. It appeared to work. I then tried the SUSE and same time of thing happened. I created a startup CD with K3b with both Ubuntu and Suse (images), then tried to open them with VB and none of them worked.
So now I have VB installed and it seems to work properly. I have also installed K3b which also seems to work properly on the Mint OS. Two new software apps. I also have start up CD’s for Ubuntu and SUSE, these will not however operate through my VB.
As for my HP laptop with Linux Mint it also is operating properly, the problem is that through all my fiddling and trying to install a VB and another Linux OS within that VB I somehow used up a lot of hard drive memory and seem to have installed another possible partition with VB. I have no idea what I did!. My main concern is that I used up a lot of memory on my new system. So now I am not sure what I need to do to free up my system and regain the space. I am not sure which things I need to remove and which ones can screw up my system. (famous SUDO command.)
I am also tempted to start over and reformat the entire laptop from scratch without a windows partition and reinstall Mint as the only OS, but for this I am also very hesitant. Mint is still working properly, I still do have some memory available: it has not been an issue yet, however my memory usage is at 70% whereas before all this I was at about 30%.
So my voyage to Linux has taken a break. I spent over five hours playing with this just so I would be able to practice my commands on the terminal in a safe environment without screwing up my system and possibly explore another linux distro. Ultimately, I lose memory space and to a certain extent end up screwing up my system.
From my reading online and in the forums, Linux takes practice and most people screw stuff up with their systems. The answers remain the same; you need to break it, in order to be able to fix it. ( These answers always come from Linux experts as well. ) I’m a neebie however and now have had my first major setback with Linux. Part of me wants to quit since I am pretty sure that my future actions will only make it worse, the other part of me hopes that I will be able to fix this memory issue myself and maybe even re-partition my entire laptop through Mint and gain a lot of memory back.
I guess for now I will leave you with my dilemna and hopefully get back to writing about my decision and the continuing saga of My Voyage to Linux.