Tag: install

Let’s Make A Linux Installation Drive

Today’s article might seem like a duplicate article, but it’s just another way that you can make a Linux installation drive. Today, we’ll be showing you yet another way to accomplish your goals. Why? Because we can! Because Linux has umpteen different ways to reach your goals – and that is awesome.

We’ll also be using a different tool for this exercise. It’s a pretty handy tool, suitable for more than just making an installation drive. Specifically, a USB thumbdrive! But, that’s just one thing you can do with this tool. It’s my way of introducing you to the tool in a useful manner. 

So, what tool will be using?

Introduction To ddrescue:​

The tool we’ll be using is called ddrescue and it’s a pretty handy tool. You probably won’t find ddrescue pre-installed, so you’ll almost certainly need to install it yourself. 

Also, if you want some confusion, if you’re using Debian, Ubuntu, Mint, etc., you’ll find it’s gddrescue at least during the installation process. Why? I don’t know. You’ll have to find out from the Turks.

Once you do have ddrescue installed, you’ll find the man page (man ddrescue) describes the application like this:

That’s right, it’s a data recovery tool! We won’t be doing any of that, however. You can probably install ddrescueview and do some of that good old data recovery with a handy GUI. I’m telling you, check the man page. This article is just going to scratch the surface.

Let’s Install ddrescue:

Yes, you can open up some GUI, type in an application name, and then install ddrescue. Or, you can open the terminal and install ddrescue without any GUI help at all. Let’s do that! Press CTRL + ALT + T to (hopefully) open up your terminal.

With your terminal now open, use the appropriate following command to start the installation process:

Debian/Ubuntu/etc:

Fedora/CentOS/etc:

Arch/Manjaro/etc:

If you don’t use any of those package managers, you may still have ddrescue in your default repositories. I just can’t confirm that you do.

Now, with ddrescue installed (even if you had to call it gddrescue during the installation phase), we can get into the meat of the article!

Make A Linux Installation Drive:

Remember that terminal that you opened to install ddrescue? Well, I hope you left it open because you’re going to need it. While the ddrescueview tool is a graphical tool, that won’t help with what we’re doing. We’ll be using the tool to make a Linux installation drive, which is almost an afterthought for this tool.

First, like a previous article about making a Linux install USB, we need to identify your target device. Plug in  your USB thumbdrive and use the following command to identify it:

You should be able to easily pick out your USB device by size. It will begin with an ‘sd’ (remember that it’s case-sensitive) and then may be broken down into partitions. Ignore the partitions and know that you’ll be removing any information on that USB drive.

You’re looking for something like sdb or sdc and you’ll add a ‘dev‘ in front of it. So, if your thumbdrive is sdb, your path is /dev/sdb. If your thumbdrive is located as sdc, the path you want is /dev/sdc. It’s pretty simple.

The syntax is as follows:

For example, this would be a command I could use:

This would let me write today’s current Lubuntu testing .iso to a USB drive so that I can test it on a laptop without having to waste the bandwidth to download the same file twice. 

Pretty handy, huh? 

Well, there’s a lot more you can do with ddrescue. I highly recommend reading the man page to learn more about this nifty application. It can do quite a bit more than this. Indeed, this is more an afterthought than anything else, or so it seems.

Closure:

Well, there you go. You have a new article. That happens regularly around here! Today we talked about yet another way to make a Linux installation drive. Frankly, you can just use balenaEtcher and call it a day. There’s no reason for most of us to do this in the terminal – but we can and it’s not even that difficult. You just need the right tools for the job and Linux has many tools on offer.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Install And Secure MariaDB In Ubuntu

I’ve recently purchased a couple of new VPSes (spelling?) and so today’s article is about how you install and secure MariaDB. As mentioned before, some articles are just going to be me scratching my own itch. In this case, I have a couple of virtual private servers that are doing nothing more than costing me money. I might as well put them to good use.

So, what is MariaDB? It’s a database management system that’s a fork of MySQL. Oracle purchased Sun Microsystems in early 2010 and MySQL went with it. Quite a few people didn’t trust Oracle’s stewardship of MySQL, they were already known for their own database management system, and so MariaDB was born.

MariaDB is actually a fork of MySQL. MariaDB is also permissively licensed, while the newer MySQL has an enterprise version with proprietary code in it. MariaDB is completely open and works just fine under a number of FOSS licenses.

MariaDB is just as fast, and faster in some operations. It supports the native languages used with databases. It’s well supported with a vast number of installs running some of the largest databases on the planet. MariaDB is one of many MySQL forks, which is to be expected. After all, MySQL was the first of its kinda – a free database management system that was released at a key  point (mid 1990s) of Internet development.

In my observation, and despite all its goodness, MariaDB a testament to exactly how much people dislike and don’t trust Oracle! So, then, why not…

Install And Secure MariaDB:

As this is server related, you’re likely to be doing this in a terminal and you’re likely to be using SSH to do so. So, I’m going to assume you already have a terminal open, saving us some time.

Make sure you’re fully updated before attempting this, so:

Now, we’ll go about installing MariaDB. It’s trivial, just run:

That’ll take a minute and, when done, you can verify that the MariaDB service is up and running properly. That needs this command:

MariaDB should be installed and running – but it’s woefully insecure. In order to secure the MariaDB installation, you will want to run the following command:

It’s going to first ask you for your root password. You’ll enter your default root (sudo) password. One of the questions will let you assign a different password for MariaDB and it’s strongly recommended that you do so. For the other few questions, you can read them or you can just answer yes to all of them, as all of them are the best choices for securing your databases.

That’s actually all there is to it. You’ve learned to install and secure MariaDB. It’s one of the many steps you might take if you wanted to set up your own server, so be careful when you’re doing so and opt for the best practices.

Closure:

There you have it! It’s another article, this one tells you how to install and secure MariaDB. In some cases, rare cases indeed, you might want to open it up to connections outside of localhost. If you do that, be sure to open up the correct port in the firewall. Other than that, you’re good to go.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

How Do I Install Linux (A General Guide)

Today, I will try to answer one of the most common questions asked by the newcomer to Linux; “How do I install Linux” To answer this I have prepared a step-by-step guide of how to install Linux with the minimum of technobabble. So, I hope you will find it simple enough to follow.

This is a guest article by one Brickwizard, who describes himself as thus:

I am Brian the Brickwizard. My interest in modern computers goes back to the days of the 8-bit IBM compatible. As a hobby, I have been repairing, upgrading, and building from-scratch computers for friends and family. I have done so since the late 80s/ early 90s. I have been a Linux user for over 20 years! Brickwizard is an upstanding member of Linux.org. This is my first contribution to Linux Tips.

This is a guide to most distros, a generic guide that’s useful for the most popular distros that have handy GUI installers. This isn’t a guide to things like Arch, Slackware, or Gentoo! It will work for Ubuntu, Debian, Mint, MX-Linux, and many more!

This also serves as a place people can link to, rather than clutter the forum up with long posts that really don’t get much formatting options. This is meant to be a time-saver, among other things. As a living document, it is also subject to change.

How Do I Install Linux:

Depending on the age of your machine you will need an installation medium, this is usually a clean pen-drive of 4 GB minimum (try not to exceed 16 GB), make sure it is of good quality and formatted to FAT32 or exFAT.

On older machines that are not USB boot-able, you will need a clean new DVD-R. You will also need courage, patience, and time. This is just the start of your journey, the step where you learn how to install Linux.

Make your ISO installation medium [pen-drive or DVD-r]

  • Choose your distribution and go to the official download page.

     

  • On the download page you will find an SHA sum, make a note of it.

     

  • Download your chosen distribution.

     

  • Burn a bootable installation medium.

For a USB pen-drive to do this, we recommend Balena Etcher.
Or for optical disc, select “burn as ISO image” in your burning software.

  • Whichever you use, now is the time to check the SHA sum (if you are unsure how, then see this article). 

To Install:

For best results, ensure your computer is either hard-wired to your router, or has a Wi-Fi card installed.

  • Connect the computer to mains power.

     

  • Insert USB into drive (or optical disc into drive).

     

  • Switch the device on and open the temporary boot menu (method will depend on the make and model of your computer).

Look down the list and find USB (or Optical Drive) click on it and enter, after a few seconds (depending on your choice of distribution) it will load a “live” session to RAM.

NOTE: You actually do not need a hard-drive installed at this stage if you only wish to check to see if Linux will work on your machine. 

NOTE: If you are making a dual boot system with Windows 8, 10 or 11, disable the windows quick-start (in the BIOS) and re-boot before continuing.

For best results, ensure your computer is either hard-wired to your router, or has a Wi-Fi card installed.​

  • Connect the computer to mains power.

  • Insert USB into drive (or optical disc into drive).
  • When the live instance of your chosen distro has loaded, your desktop will appear. Now is the time to ensure everything works okay, such as Wi-Fi, sound, and graphics. The easiest way to do this is click on the wireless icon find your router and enter the password. When you’re connected, go to your favorite music video site and pick something you are familiar with. If the video plays okay, the picture looks good, and the sound works, you can then decide if you wish to continue the installation.

     

  • To start full installation, double-click the installation button on the desktop (this may vary based on the distribution). The installer will then check the components of your machine. This may take several seconds or a couple of minutes, depending on how fast your computer is. If all goes well, the installation will begin shortly, asking you to input certain information – such as your username and password. Watch it install. When it asks about partitioning, this is your final chance to decide if you want to dual boot with your existing system (select installation alongside) or wipe the system and just install Linux.

     

  • During install, most distributions will ask if you wish to install non-free/proprietary drivers, tick the box for yes and enter. Non-free does not mean it will cost money to use. It just means that it’s supplied by the manufacturer and not FOSS (Free Open-Source Software). You can choose to not install proprietary drivers, but that will make your life more difficult and is beyond the scope of this article.

     

  • You may need to continually enter information as it installs, so keep an eye on it. A typical Linux installation can take from 10 to 20 minutes.

     

  • When it has installed you will get a message do you wish to re-start now, accept and enter. When prompted, be sure to remove the installation media.

Sit back whilst it reboots, then it will take a couple more minutes to clean up the installation and get rid of the installation files. Then if all goes well we will have a working Linux box

When your system has rebooted to your new Linux system, open the update manager and run a full update.

NOTE: When you have successfully installed your Linux distribution, we strongly recommend you install and activate some backup software, such as Timeshift. 

Being new to Linux, there will be learning curve. As I often say, “Relax, kick off your shoes, grab a beer, and enjoy the ride.”

Closure:

There you have it, it’s another article – and this time it’s a great article from Brickwizard. This one will tell you how to install Linux. It’s a basic guide, which is fine, because it can always be more complex and this is just to get you started. If you have any questions, you can ask below or head over to the Linux.org forum and ask questions there. Even better, it stands as a static page that can be linked to, saving time, effort, and space.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Guest Article: Kickstart Vol. III

Today is the third guest article in a row, and is one more article about Kickstart. There will be more Kickstart articles, but we’ll release those in time. This is the third one in a row, so we’ll try to mix it up a bit.

By now, we should all have at least a little familiarity with Kickstart. Frankly, I’ve still not had a chance to use it – but it does seem like it’d be fun to play around with it. If I were an admin of anything major, I’d definitely look to Kickstart as a solution. Again, if you read this on day one, be sure to check back later as the author may suggest some edits.

See the previous articles here:

Guest Article: Kickstart Vol. I
Guest Article: Kickstart Vol. II

Kickstart Vol. III

Now we need to create a menu for your Kickstart, so you can select which OS you want to install.

Now edit a new file named grub.cfg. It must be named grub.cfg. Here is an example of what it should look like.

The set-default lets you pick which is the default install, it starts at zero, so the options here would be 0, 1 and 2.

Note the IP address of my Kickstart server is here, the path to my extracted iso directory is here, and the location of my boot kernels is here.You can change all of these to fit your needs.

Now we need the actual anaconda-kickstart.cfg files, this is what actually does all the work.The location of these, is set in the grub.cfg file above. You will want these to be in the extracted iso directory, but not in the “dvd” sub-directory.

Here is an example of what one of these would look like. This one is fairly basic.

Again you see the IP address of my kickstart server here, you see the location of my extracted iso files here.Now there are a few things you will need to know in advance.

What I typically do, is install the OS from a USB the first time.In the case of fedora/redhat/CentOS there will be a file at /root/anaconda.cfg. You can copy this file as a starting template for your kickstart of this OS.

(Yes I am re-naming the file here.)

Also you will need the password has strings for your users.

(Or whatever user name you use.)

You will need to know the name of the LAN interface, and you will need to know the size of your hard, and how big the partitions should be.All of these things will be in your anaconda.cfg file

Now change and edit a few things in your fed35srv/fed35.cfg file now.

Change the graphical install to..testskipx This uses a cli interface, not a GUI when installing.

Change the url line to the location of your extracted iso directory in your web server. Note you don’t put the full path, only the path from your webroot.

I like to turn off seLinux, but you can delete that line if you like.

Change your timezone to whatever is appropriate for you.

Using the two example user lines above (those aren’t real hashes, I just typed a bunch of random characters to simulate what it looks like). Edit the user lines to be whatever your values are.

That’s it, you’re don! Now boot your test computer on the kickstart network. A Kickstart menu should appear. Select the appropriate OS.

I’ve found this usually works best with a few settings on the test computer. CSM should be disabled. Network stack should be enabled. Some UEFI settings let you pick PXEboot IPv4 as a boot option. This is preferred. I’ve found it works best with a freshly formatted hard-drive, that way it doesn’t try to boot into the installed OS.

Good luck!

Closure:

And there you have it! You have a guest article, from dos2unix, about Kickstart. There are now three of them and there are a couple of others sitting in the potential queue. We’ll get to them. These few days off have been a very welcomed respite!

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Guest Article: Kickstart Vol. II

Today’s guest article is a continuation of the Kickstart theme. The first Kickstart article can be found here. Thanks goes out to dos2unix from the Linux.org forums.

I should mention again that I don’t actually know anything about Kickstart, other than what I’ve read in these articles. I’m extremely grateful, but you may want to check back a few times to ensure all the editing is complete!

Kickstart Vol. II:

Now that we have your web server, dhcp, and tftp server configured, we will need to enable the firewall for them.

On Fedora it looks like this:

Now we need to extract the iso files you have handy (you did already download these, right?) I should have mentioned you will need the “server” version of these iso’s. There is a way to make the workstation iso’s work, but that’s for another more advanced article.

For the example here, I put everything in: 

When that gets done copying, we can add another OS’s iso if you like:

If you have more iso’s repeat the same for CentOS or Redhat or whatever you have.

Again, when it gets done copying, simply umount the iso image. I confess, I’m something of a minimalist. I like short names like pub/fed35srv. If you like long names you could have something like /public/fedora35-server/x86_64/ I’m too lazy to type all of that in all my config files.

Now we will install the boot kernels. This isn’t actually the full kernel yet, just a lite kernel with enough parts to boot the system from the network.

Just about all computers have one of two types of internal configuration systems. Legacy BIOS and UEFI. Most newer computers in the last 8 years or so,are UEFI, but there are still plenty of Legacy BIOS systems around. For the purpose of this article we will set-up for both types.

In your /var/lib/tftpboot directory, we will make two directories. One for BIOS and one for UEFI.

Technically you could rename the efi directory to something else, but the pxelinux for legacy BIOS systems is hardcoded in some files.

Now you will need to download a couple of files. I recommend using the Fedora 35 version, even if you are going to be installing Redhat or CentOS. They are newer, have more features, bug fixes, and support more hardware.

But you can use the CentOS or Rehat versions if you want to. Shim-x64, grub2-efi-x86, and grub2-efi-x64-modules. We will need to extract these rpms. You can do this in /tmp or somewhere safe.

If it says this is already installed, replace install with reinstall. These are the efi files you will need for efi based systems.

This will create 3 directies in /tmp.

You can delete these directories in /tmp if you like, you are done with them. Make sure you don’t put a leading / and actually delete /usr and /etc.

The next part depends on what iso’s you have downloaded and extracted. But hopefully you will get the idea.I am using Fedora 32, Fedora 35, and Redhat 9 as my examples. You can use whatever directory names you like.

That’s enough for this article, will add next part later.

Closure:

And there you have it, another article and this one is a guest article – just like yesterday and probably just like tomorrow. I’m extremely grateful for the respite and wish I knew more about Kickstart. I think, for future reference, I’m gonna ask that folks register and write the draft here. I think it’d streamline it.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Subscribe To Our Newsletter
Get notified when new articles are published! It's free and I won't send you any spam.
.
Linux Tips
Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.