Tips Archives • Page 46 of 66 • Linux Tips

Convert Disk Image Formats To .ISO

Today’s article will teach you how to convert disk image formats to .iso. It’s a pretty handy tool to have in your toolbox. This is going to be a pretty easy article to follow, so it shouldn’t be all that long.

In case you don’t know, there are all sorts of disk image formats. The .bin and .cue are the two you are most likely to be familiar with (beyond the .iso, which is the most common in the Linux world).

There are .B5I .BIN, CDI, CUE, .MDF, MDE, and .NRG. There may be more, but that’s all the tool we’ll be using handles. As I mentioned, you may well already be familiar with the .BIN and .CUE disk image formats. You see those from time to time and now you no longer have to ignore them – you’ll have just the tool you need to convert them to .ISO (which many programs expect – and work with, while not working with other formats).

The tool we’ll be using is known as iat and it’s actually just a tiny command-line application. The man page defines it as such:

iat – converts many CD-ROM image formats to iso9660

The latter part is probably important to note. That means that it only converts to .ISO format and nothing else. If you want to convert to a different format, or in the opposite direction, this is not the correct tool the job.

So then, let’s take a few minutes to use iat and learn how to …

Convert Disk Image Formats:

This article requires an open terminal, like many other articles on this site. If you don’t know how to open the terminal, you can do so with your keyboard – just press CTRL + ALT + T and your default terminal should open.

With your terminal now open, the rest is easy. It’s almost certainly in your default repositories, and unlikely to be installed by default. You can install it in your usual manner – but I’ll show you how to do it in Debian/Ubuntu/Mint derivatives:

sudo apt install iat

1	sudo apt install iat

It’ll be just as easy to install in any major distro. To use it, it’s REALLY simple… It’s just this easy:

iat <path/to/file_name> <desired_output_name.iso>

1	iat <path/to/file_name> <desired_output_name.iso>

Sure, you can check out man iat, but it’s not really all that complicated. This is pretty much the easiest tool you’ll find to convert disk image formats to .iso. Tell it which file you want to convert, tell it what you want to name the output file, and then you just pound the enter button on your keyboard and wait. The output is a handy .iso that you can use just like you would any other .iso.

Closure:

There you have it! You have a new article that teaches you how to convert disk image formats to .iso – which can seriously come in handy when you need to burn a disk image and the software you’re using only accepts .iso as the input.

It’s also the first article I hadn’t obligated myself to do! This is now over a year since the first article was published, and one published every other day. I am absolutely NOT committing to maintaining the same publication schedules, but I just don’t think I can let the site sit here idle. So, we’ll see what happens.

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.

Change Snap Application Privileges In Lubuntu

In today’s article, we’re going to learn how to change Snap application privileges in Lubuntu. With Ubuntu, it’s a bit more straightforward. In Lubuntu, you have to dig around a little bit. Don’t worry, ‘snot hard – it’s just not all that intuitive.

Snap applications come with their own privileges. This is useful because sometimes you may want to change them, to enable something that was disabled or to disable something that was enabled. I think it’s sorted now, but at one point you even had to change the permissions to let the Firefox browser access removable media.

In Ubuntu it’s pretty straightforward and there are a ton of tutorials already out there that will help you change Snap application privileges. It’s just one of those things that comes with Snaps, so we’ll cover Lubuntu.

I’ve written about Snap applications before, including sharing how to disable Snaps completely. However, the reality is that they’re going to be a part of the Ubuntu ecosystem for the foreseeable future.

Like them or not, they will be a part of Ubuntu and official Ubuntu flavors. I suspect trying to avoid them will get more difficult. With the new Lubuntu, for example, the Firefox browser will come as a Snap application by default.

So, well, even we folks using Lubuntu must come to grips with Snap applications. This can be a pretty painless process, if you’re armed with some information. That’s what this article is meant to do. This article is meant to teach you how to …

Change Snap Application Privileges In Lubuntu:

This is actually pretty easy, but not necessarily intuitive. Unlike many of my articles, you don’t actually have to start with an open terminal. No, you need to start with “Discover”.

So, crack open your menu, click on System Tools, and then click on Discover. Once you have Discover open, you can use the search or installed option to find the application in question. In this article, I decided to just use Firefox – seeing as we Lubuntu users will be faced with a Snap app Firefox.

When you find the application, you just click on it. It looks like so:

click on Firefox to begin — See? I even started you off with a handy arrow! *It’s a recurring theme!*

Once you’ve clicked the application, then you just click on the obvious! You just click on “Configure permissions”. That looks like this:

click on permissions to continue — Yup. I gave you another handy arrow – but it should be obvious now.

Finally, you can adjust the individual permissions. That looks like this:

finally, adjust your permissions as needed — There are a bunch of settings you can change. Again, you get a handy arrow!

That’s about it, really. The thing is, you have to use Discover. While the Muon application is able to install applications, it doesn’t deal with Snap applications. Only the Discover application has these menus and it’s the only way (at least graphically, by default) for you to adjust the individual Snap application privileges.

So, while it’s not necessarily intuitive – it’s not dreadfully difficult. You just have to know where to look and then it becomes obvious.

Closure:

Guess what? As of tomorrow, a day where no article is scheduled, it will have been a full year that this project has been alive. That’s right! I’ve gone the full year without missing a single publication date! If I can do it, so can’t you!

So, am I done? No… No, I don’t think so. I still have articles that need to be written, things that need to be said. I’ve had a great deal of fun, though it has been a lot of work. I’ve learned some, you’ve learned some, and I’d say it’s a net benefit to the Linux community – though I suppose I’m a bit biased. (Feel free to agree with me!)

I may take a few days off. I’m not actually sure. I haven’t decided. I have decided that this can’t be the last article, so there’s that. Which is nice… If nothing else, I’ll see you again in a few days. I might enjoy taking a break. Then again, I kinda suck at taking breaks. I truly suck at retirement.

Check To See If SELinux Is Working

In today’s article, you’ll learn how to see if SELinux Is Working on your system. Your system may not have SELinux, but many do. This article is for those people. You’re welcome!

SELinux stands for Security-Enhanced Linux and its function is to provide greater controls over who can access the system. It was actually developed by the US spy-agency – the NSA. You’ll often find SELinux in distros that fall within the RHEL family tree. The link at the start of this paragraph will give you even more details.

This article is just about checking to see if SELinux is working. It should be noted that SELinux has three operational states. I’ll cover them lightly here.

The first operational status is usually the default, which is ‘enforcing’. This means that it’s working and blocking as designed.

The second possible result is ‘permissive’. When SELinux is in this state, it is not blocking anything – but it is logging everything. So, you’ll see things after the fact, when you check the logs.

The third is simply ‘disabled’. That’s self-explanatory. If it’s disabled, it means it isn’t working. If it’s disabled, it’s easy enough to start it. If you choose not to, you’re not taking advantage of a security tool.

It’s not a very difficult article to follow, I don’t imagine. Pretty much anyone can figure this out. We won’t be going into details other than what the headline, and explaining everything about SELinux would take a lot of time and is beyond my level of expertise.

See If SELinux Is Working:

With your terminal open, the very first command you can use is simply:

getenforce

1	getenforce

That’ll spit out exactly the answer you’re looking for. However, the command that’s more interesting is the one that follows, an arguably better command to learn more about the status of SELinux:

sestatus

sestatus

That command outputs a ton of information. The output of that command has more information. Included in that information is the SELinux status. It’s a quick way to see if SELinux is working.

The output of that command would look something like this:

See the line – which is “Current mode:”? Well, that’s how you see if SELinux is working. It also feeds you other information, for a more deep view of your SELinux status.

I suppose if you use that command and want to narrow it down, you could do something like:

sestatus | grep "Current mode:"

1	sestatus \| grep "Current mode:"

Which is really just a bit silly when you already have the getenforce command available. There’s no reason to occupy one of your memory banks with that command, as it’s really just some fun with grep.

Closure:

Yup… There you have it. You have another article! ‘Snot really all that handy for those of us who don’t use SELinux. But, if you are using SELinux, this is a perfectly handy way to see if See If SELinux Is Working.

How To: Find Your Man Pages’ Location On Disk

Today’s article is going to teach you how to find your man pages’ location on disk. It may not be a very useful skill, but it’s one that will come in handy in a future article. (That’s called ‘foreshadowing’!) Well, it seems likely that it’ll come in handy with a future article.

By the way, if you’re curious about why the first lines in these articles are often ‘forced’, it’s because of search engine optimization. You can blame the search engines, but it works.

Many of you will be familiar with the which command. You can use that to locate a binary for an application. For example, you can go with:

which ls

which ls

Which will output something along the lines of:

/usr/bin/ls

1	/usr/bin/ls

And that’s great. If that’s what you need to know, that’s what you need to know. However, what if you want to also know where your man page file is located?

It should come as no surprise that Linux will happily spit that information out, so long as you know the correct incantations. And, for that, you have Linux Tips – where I’m gonna tell you how to find your man pages’ location.

Man Pages Location:

The tool we’re going to be using is similar to which, and even spits out the same information. The tool in question whereis and the man page describes it as:

whereis – locate the binary, source, and manual page files for a command

As you can see, it’s a pretty simple command. It will also only show you the source if you actually have the source. In most cases, you have compiled binaries and that’s what your system uses. It’ll happily locate the binary just like the which command does.

So, let’s test it… Hmm… Let’s test it with the ‘ls’ command:

whereis command in action — See? It does exactly what i told you it would do! That’s why I make the big bucks!

So, if you want to know where your man pages are located for a specific applications, this is an easy way to do that. Obviously, it’s the 2nd bit of information. Though, I suppose if you only want the output to contain the path to the man pages, you could use a command like this:

whereis ls | awk ' {print $3} '

1	whereis ls \| awk ' {print $3} '

That will just spit out the path to the man page, if that’s all you want to see. Try it with a few different commands and you’ll lock it into your memory – ’cause you never know when it’s going to come in handy.

Closure:

And there you have it… You have another article! This is just one of many articles, so feel free to browse around. You might even learn something new! I’ve officially written so many of these things that I can’t actually remember them all. I legit need to search first and make sure I haven’t already written the article. (I probably should have devised a system to avoid this, but the search function appears to be pretty good and effective.)

Remove The Firefox Title Bar

If you, like me, appreciate clean and simple layouts then the Firefox title bar is annoyance. Firefox’s title bar wastes space, adding unneeded clutter. I have a dislike for that sort of stuff. If you too happen to dislike it as much as I do, this article will tell you how to remove the title bar from Firefox.

If this site’s aesthetics doesn’t make it obvious, I really like my layouts to be simple. I don’t like wasted space that doesn’t give me information that I need. That’s one of the reasons I use Linux – I can make the OS get out of my way and get my work done. If I had the skills, I’d make this site ‘responsive’ so that it filled wider screens better – just to avoid that wasted space.

I admit, it’s pretty picky and maybe a bit over the top, but I really do like the entire screen to have information I need on it. Other than a few applications, everything I do is in full screen. I sometimes don’t even bother with a desktop background – because I never see the desktop.

I believe the more technical term would be that I like an ‘information dense’ working environment. It’s not for everyone, but it works for me. For example, as I write this, I have 92 tabs open. See:

See? I wasn’t kidding. That’s a bit more than normal, but not much. It’s what I do. Firefox isn’t usually among my open apps, actually. Oh well…

I also have multiple browsers open. Yeah, I have a problem… (My other main browser has ~60 tabs open.)

Remove The Firefox Titlebar:

So, what am I talking about? How can you fix this in Firefox? Well, a picture is worth 1,000 words…

It’s actually easy to get rid of, if you know where to look. So, this won’t be a taxing article – it’s an article that anyone can follow!

Firefox needs to be open, of course. Once open, look in the upper-left. You’ll see three vertical dots and those open the menu for customization. Click that and then click on “Customize”. Then, simply scroll down and untick the box for Title Bar.

disable firefox title bar — It’s easy, once you know where to look. Also, I suck at editing images. I seriously suck…

You don’t even have to restart the browser. It really is that easy to get rid of this annoyance. While you’re there, you can also customize a few other visual elements, so you might as well do that while you’re there. That and a theme and you’ve made your Firefox browser into your own.

Closure:

And there you have it, a nice and simple article that tells you how to remove the title bar from Firefox. It’s not dreadfully difficult, but it is an article! Maybe I should do one for Chrome/Chromium? That’d be another simple article that might be useful for people looking to maximize their screen’s real estate.