Today’s article isn’t going to be complicated or long as we are going to cover how you install Wine in Lubuntu. This should be straightforward and work with any modern version of Lubuntu.
I suppose we should start with the basics…
Lubuntu is a distro in the Ubuntu family. This is my favorite distro and I’ve covered Lubuntu-specifics in the past. However, these directions are going to work just fine on Ubuntu or even Linux Mint. They should also work just fine for Debian and any other distro that uses ‘apt‘ and some standard repositories.
Wine is software used to run Windows software on Linux. It once stood for “Wine Is Not an Emulator” and it is indeed not an emulator. Wine is a compatibility layer that lets you run some Windows software on Linux. Not all Windows applications will run, and things like Windows drivers don’t work, but it can be a handy application for those who still rely on Windows software.
I’ll only cover the basics. There’s a lot to Wine (not WINE, at least according to the project page) and this is only going to cover how to install Wine in Lubuntu. Of course, other distros can use these same few steps, but I only tested in Lubuntu. (It’s a giant amount of software to download and my bandwidth isn’t the greatest.)
If you’ve tested this in other distros, let us know!
And, yes, I did test this in Lubuntu and Wine appears to be installed.
Install Wine In Lubuntu:
You can likely do this with the GUI software installation tools but we’ll do this in the terminal. As you’re using Lubuntu, you can open a terminal by simply pressing CTRL + ALT + T on your keyboard.
Because you’re using Lubuntu, I can surmise that you’re using 64-bit. If you’re not, you’re using a very old version of Lubuntu. You should upgrade to a supported release immediately, or move to a distro that’s still supporting 32-bit hardware.
If you’re not using Lubuntu, you should read this:
You’ll need to use a 64-bit CPU and operating system if you want to follow these directions with any hope of success.
The first thing we will do is enable 32-bit software from the repositories. This is just a simple command:
1
sudo dpkg –add-architecture -386
I don’t always remember to suggest you update your device, but it’s a good idea if you update now. You can update with this command:
1
sudo apt update && sudo apt upgrade -y
With all of that done, you only need to install Wine in Lubuntu. That’s easily done:
1
sudo apt install wine64
That’s all there is to it, at least at the basic level. As I don’t use Wine, because I don’t use Windows software, I’m going entirely from my notes and a time when I did try to retain some Windows software. (Crimson Editor, I’m looking at you.)
Closure:
There’s a lot more to this, but that’s the gist of it. If you want to install Wine in Lubuntu, it’s not all that difficult. You may then want to do things like install Plays On Linux or whatnot, but I don’t think that’s technically required. So, this is just an intro to Wine. There’s much more to 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 site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.
The title is the best I can come up with to describe this exercise as we’re going to save a command’s output to a file – while showing that same output in the terminal. This is something we’ve not quite done on this site before and something you might find interesting.
NOTE: This article assumes that you’re using Bash.
We’ve sort of covered redirect operators before. Read this article:
However, this time, you’re going to enter a command and see the output in the terminal, unlike what you’d see in the above-linked article. On top of that, you will simultaneously save that output to a file.
This can be handy to keep track of a command’s output over time. This can also be handy if you’re trying to audit a system and want to keep track of the output from the command.
For this article, we’re going to just use a simple example command. We’ll be making use of the
uptime command because it’s easy and universal. If you’re using a desktop (or server) Linux, you have this command available.
This article is also going to make use of the
tee command. If you’re a regular reader, you’ll know we’ve covered this command before. Then again, if you’re not a regular reader, you can just as easily learn about the tee command by reading the following article:
We’ll also be using the terminal, of course. We almost always use the terminal!
Save A Command’s Output To A File:
As suggested above, this is another article that relies on an open terminal. You can usually open a terminal by pressing CTRL + ALT + T on your keyboard. A terminal is otherwise available in your application menu.
With your terminal open, let’s just view your uptime with this command:
1
uptime
Next, we’re going to tell the command to show the output AND save the output to a file. That’s quite simple:
1
uptime 2>&1 | tee <file_name>.txt
So, let’s try this example command:
1
uptime 2>&1 | tee uptime.txt
Now, you can verify that this worked with this command:
1
cat uptime.txt
Every time you run that command, it will clear out the existing text and write the most recent output to the uptime.txt file.
If you’d rather append the data, that’s easily done. It looks like this:
1
uptime 2>&1 | tee -a <file_name>.txt
Again, as a handy example:
1
uptime 2>&1 | tee -a uptime.txt
If you run that command multiple times and then check it with
cat uptime.txt you’ll see that the
-a flag will append the output. So, each time you run this command it will add the new output to the file.
That’s all there is to it. This is a handy thing if you want to monitor the output of a command over a period of time. You can alias the uptime command to this command and have a record of all the times you ran the uptime command in the terminal.
I’m sure there’s more that you can do with it, but that’s a basic idea that you can take with you. It’s a pretty handy command and one that I recently shared via PM with a Linux.org user. Seeing as it was on my mind, I figured I’d make it an article. I’d call it a ‘short’ article but the title was already too darned long!
Closure:
Now you know how to save a command’s output to a file while also showing the command’s output in the terminal itself. This is a handy enough command and easy enough to do. It seemed like it’d make an easy article for folks, so I wrote it. I don’t have any other justification, though it was not all that taxing to write.
In my defense, I deserve an easy article now and then!
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.
It was suggested that I write an article about journalctl, which seemed like a large topic. I decided that I’d let AI have a shot at it, so this article was written by ChatGPT.
It took a few prompts to get what I wanted – which turned out to be the first result. I gave the AI the chance to rework the article but the result was that I much preferred the initial offering. After all, I was only after a very light overview of the journalctl command.
There’s a lot to the journalctl command. The journalctl command is far too much to cover in a single article. Heck, I don’t even know some aspects of the command. You can see this by checking the man page with the following command:
1
man journalctl
See? There’s a lot to the command. At the end of the day, AI did a good job of summing up what you really need from the command as an average user. So, I’m going to go ahead and publish that content. It did a better job than I’d have done!
Introduction To journalctl:
In the realm of Linux system administration, understanding and managing system logs is indispensable. Logs provide crucial insights into the health, performance, and security of a system. Among the plethora of tools available for log management, journalctl stands out as a powerful and versatile command for accessing and analyzing logs in systems utilizing systemd. In this comprehensive guide, we will delve into the intricacies of journalctl, exploring its features, functionalities, and practical applications.
Understanding Systemd Journal:
Systemd, the init system adopted by many modern Linux distributions, introduced the systemd journal as a replacement for traditional syslog. The journal, stored in binary format, offers numerous advantages over syslog, including structured logging, faster search capabilities, and enhanced metadata.
journalctl serves as the primary interface for querying and interacting with the systemd journal. It provides administrators with a rich set of options for filtering, displaying, and analyzing log entries, empowering them to effectively troubleshoot issues, monitor system activity, and extract valuable insights.
Basic Usage:
At its core, journalctl allows users to retrieve and view log entries from the systemd journal. The simplest invocation of journalctl displays the entire journal, starting with the most recent entries:
1
journalctl
This command presents a paginated output of log entries, including timestamps, log levels, and message contents. By default, journalctl displays logs from the current boot session. However, it also supports options for querying logs from previous boots or specific time ranges.
Filtering and Querying:
One of the key strengths of journalctl lies in its ability to filter log entries based on various criteria. Administrators can narrow down the search results by specifying filters such as time range, log level, systemd unit, or specific fields within log messages.
For example, to display all log entries generated by the sshd service, the following command can be used:
1
journalctl _SYSTEMD_UNIT=sshd.service
Similarly, to retrieve logs pertaining to a particular time range, the --since and --until options can be utilized:
Additionally, journalctl supports advanced filtering using Boolean expressions, enabling complex queries to be constructed for precise log retrieval.
Output Formatting and Presentation:
journalctl offers flexible options for customizing the format and presentation of log entries. Administrators can choose from various output formats, including short, verbose, and JSON formats, depending on their preferences and requirements.
For instance, to display log entries in a more detailed and verbose format, the -o verbose option can be used:
1
journalctl -o verbose
Moreover, journalctl provides options for controlling the display of timestamps, including the ability to convert timestamps to the local time zone or display them in a human-readable format.
Real-time Monitoring and Follow Mode:
In addition to viewing historical log entries, journalctl can also be used for real-time monitoring of system logs. By invoking journalctl with the -f or --follow option, administrators can tail the journal and receive live updates as new log entries are added:
1
journalctl -f
This feature is particularly useful for monitoring system activity in real time, diagnosing issues as they occur, and tracking the progress of system services during startup and shutdown sequences.
Integration with Other Tools:
journalctl seamlessly integrates with other Linux system administration tools, enabling administrators to combine its capabilities with those of other utilities for more comprehensive log analysis and management.
For example, grep can be used in conjunction with journalctl to perform pattern matching and further refine log queries:
1
journalctl | grep "error"
Furthermore, administrators can leverage shell scripting and automation to automate log analysis tasks, extract meaningful insights, and trigger alerts based on specific log patterns or conditions.
Conclusion:
In conclusion, journalctl emerges as a powerful and indispensable tool for managing system logs in Linux environments utilizing systemd. Its rich feature set, flexible filtering options, and real-time monitoring capabilities make it an invaluable asset for system administrators, enabling them to effectively diagnose issues, monitor system activity, and ensure the stability and security of their systems.
By mastering the intricacies of journalctl, administrators can gain deeper insights into system behavior, streamline troubleshooting workflows, and maintain the optimal performance of their Linux infrastructure. Whether it’s debugging a system issue, auditing security events, or analyzing performance metrics, journalctl empowers administrators to navigate the complexities of system logging with confidence and efficiency.
Closure:
Well, I keep finding uses for AI. This is a better article than I’d have written. I think I’ll next use AI for a solid article about grep. That sounds like a reasonable subject and it’s an article that I can reference in many other articles. In fact, I should have done an article about grep already!
So, this is an article about journalctl. It’s an overwhelming command. It’s amazingly complicated and powerful, but you (as a regular user, as most of my readers are) will only need to know the basics. This is indeed the basics and they appear to be well-described.
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.
Today we will have a fairly simple exercise as we’re going to just use a Python application to extract text from multiple file types. This is a pretty standard operation but will require some preparation.
Fortunately, I’m ahead of the game! You’re good to go if you follow along on the site and have already enabled PIP. Otherwise…
You will need to install PIP for this article. This is not complicated.
Technically, you could just do that. However, you should add the path so that you don’t have to specify the location of your Python applications and can easily use them from the terminal.
Now that you’ve done those two things, you’re good to proceed. See? It was worth the time to write those articles! They’re useful and save a lot of time.
The tool we’re going to use is known as “Textract“. Don’t quote me on this, but I believe this could also apply to Windows users, though installing the dependencies for this would be a different process. I’m not a Windows user. If you are, feel free to comment and let us know how things work on your side of life.
Textract:
While there is no built-in man page, the Textract application is described like this:
While several packages exist for extracting content from each of these formats on their own, this package provides a single interface for extracting content from any type of file, without any irrelevant markup.
It is a pretty handy application and claims to extract the text from more file types than I could reasonably expect to test. Here’s a list of files that you should be able to extract text from.
.csv via python builtins .doc via antiword .docx via python-docx2txt .eml via python builtins .epub via ebooklib .gif via tesseract-ocr .jpg and .jpeg via tesseract-ocr .json via python builtins .html and .htm via beautifulsoup4 .mp3 via sox, SpeechRecognition, and pocketsphinx .msg via msg-extractor .odt via python builtins .ogg via sox, SpeechRecognition, and pocketsphinx .pdf via pdftotext (default) or pdfminer.six .png via tesseract-ocr .pptx via python-pptx .ps via ps2text .rtf via unrtf .tiff and .tif via tesseract-ocr .txt via python builtins .wav via SpeechRecognition and pocketsphinx .xlsx via xlrd .xls via xlrd
You may need to install specific packages for some of these file formats. Those packages can usually be found in your default repositories. It otherwise comes with quite a lot of functionality out of the box.
I did test some of those formats and it seemed to work okay. Your mileage may vary, of course. However, Textract was able to extract text from multiple file types.
Extract Text From Multiple File Types:
If you want to extract text from multiple file types with Textract (a fantastic name for an application) then you’ll first need to install it. I’ve yet to find a working GUI PIP installation tool, so that means you’re going to need an open terminal.
More often than not, you can open your terminal by simply pressing CTRL + ALT + T on your keyboard. If your distro doesn’t adhere to the norms, you can find a terminal in your application menu. If you don’t use an application menu, you already know how to open a terminal and you don’t need any help from me.
First, let’s install Textract:
1
pip3 install textract
Note the lack of
sudo. You’re installing this for your user account and do not need elevated permissions for this. Python packages go right into your
~/ directory. See below, as you’ll want to install some dependencies for full functionality.
You may see an error or two during installation but that doesn’t seem to matter. It will take a minute to install and watching the installation chug along is good fun.
Using Textract:
With Textract installed, you can now extract text from a whole variety of file types. The syntax is as follows:
1
textract /path/to/file
That sends the output to the standard output (your terminal). I suspect that most folks are going to want to save the output to a file. For that, you just need to add the
-o flag and a file name. So, something like this:
1
textract /path/to/file -o <new_file_name>.txt
That’s going to extract the text from some file types but not all of them.
Now, this is from a Lubuntu installation…
This isn’t going to work with all the listed file types at this time. You need some dependencies to be installed. For me, and it’s a long one, the command was:
That’s slightly different from the command they include on their page, but it appears to do the trick. You’ll have some of those installed by default but running the command will sort itself out. You’ll have to modify the command to suit your distro, but that should work with Debian, Ubuntu, Linux Mint, and other Debian-based distros.
With that installed, I can even grab the text from image files.
Here’s an example:
This is some simple text to test how well Textract really works.
Here’s the command:
1
textract sample_text.png
Here’s the output:
1
2
3
$ textract simple_text.png
This is some simple text.
Let's see Textract in operation!
I dare say that’s pretty good. I tried other pictures and it was good enough to get the gist of things. Complicated image files with many columns appear to be a bit of a stumbling block. But it’s not terrible.
It has no trouble at all with other file formats.
It can be a bit fussy to get Textract properly installed but it seems to do the trick once installed. If you want to extract text from multiple file types, Textract is a pretty good piece of software.
Closure:
If you want to extract text from multiple file types, this is definitely a good tool for the job. It certainly handles a lot of files and does a good job with them. It’s not perfect. None of these tools are. Complicated image files threw it off a bit, but Textract lives up to its name.
There was a reason I wrote those articles about PIP. Being able to install Python packages via a repository is a great thing. There’s some great Python software out there and we’ve barely touched the surface. Linux is great like that, that is offering great Python support.
Do you have a use for this in your daily activities? If so, leave a comment letting us know how you use Textract and what makes you pick it over other applications. You can even use a real email address. I never send spam. I never sell your information.
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.
Today’s article should be a fairly short article, where I take the chance to show you how to move a file to multiple directories – at the same time. It’s a pretty simple process, albeit a bit weird. If you want to move files to multiple directories, this is the article for you!
I’ve done a lot of articles about file management. This is another one. We usually manage files in the terminal here on Linux Tips. We’ll be doing that again this time around. We’ll be managing files in the terminal!
The tool we’ll be using is the tee command. I covered that recently.
The task we’ll be doing is showing you how to move a file to multiple directories – at the same time and in the Linux terminal. It’s a pretty handy skill to have, though there’s some tee weirdness along the way.
Move A File To Multiple Directories:
You’ll need an open terminal for this, as the intro suggested. You can find a terminal application in your GUI file manager. You can often open your default terminal by pressing CTRL + ALT + T on your keyboard.
With your terminal open, let’s just run through some exercises to ensure we’re all on the same page and ready to move a file.
First, let’s make a directory:
1
mkdir temp
Next, let’s move to that directory:
1
cd temp
Next, let’s make that file that we’ll copy to multiple directories:
1
touch foo
I suppose we’ll need a few folders next, so let’s create them:
1
mkdir one two three
Now, let’s move the file foo to multiple directories:
1
tee ./one/foo ./two/foo ./three/foo &
The syntax is:
1
tee <directory>/<file_name> <directory>/<file_name> <directory>/<file_name> &
We throw the
& in so that the tee command doesn’t hang, awaiting further input. You’ll get an extra message or two, but that’s fine and can be ignored.
Now, we can verify them:
1
cd one
The following command will show you that the file exists:
1
ls
That should show the file, like so:
1
2
$ ls
foo
Now, you can check the other folders.
1
cd ../two && ls
And, of course:
1
cd ../three && ls
Each of those should show you that the foo file exists in each directory.
Now, we can clean up after ourselves with this command:
1
cd ../.. && rm -rf temp
Tada! Now there shouldn’t be any remains left behind and we’ve covered how to move a file to multiple directories at the same time and in the Linux terminal.
Pretty easy and pretty short!
Closure:
You never know when you’ll want to move a file to multiple directories but now you know how to do so. It isn’t a very difficult exercise, warranting only a short article. This seemed like good fodder for a short article and a handy tip to share with my readers.
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.
