🟢 Beginner Friendly Guide

This article explains everything step-by-step.
If you are new to Linux disk management, don’t worry — we’ll go slowly and explain what each command does.

What We Are Trying To Achieve

We have two external ext4 Seagate drives and we want:

• Automatic mount on system boot
• No boot failure if a disk is unplugged
• Clean /mnt directory structure
• Drives visible in GNOME Nautilus

Step 1 — Identify Your Disks

First, list your disks:

lsblk -f

You can also check detailed information:

sudo blkid

Example:

/dev/sdb1: LABEL="Seagate 2TB" UUID="9066b4ff-96d4-4be4-99b9-7402db8ad31c" TYPE="ext4"
/dev/sdc:  LABEL="Seagate 4TB" UUID="c36f588e-bcbd-4774-863d-3b9d50e2f08f" TYPE="ext4"

What is UUID?

UUID is a unique identifier for your disk filesystem.
Using UUID (or LABEL) in fstab is safer than using /dev/sdb1, because device names can change between boots.

Step 2 — Set Clean Disk Labels (Optional but Recommended)

If the disks are mounted, unmount them first:

sudo umount /dev/sdb1
sudo umount /dev/sdc

Set readable labels:

sudo e2label /dev/sdb1 "Seagate 2TB"
sudo e2label /dev/sdc "Seagate 4TB"

Verify:

lsblk -f

Step 3 — Create Mount Points

We will mount them under /mnt:

sudo mkdir -p "/mnt/seagate-2tb" "/mnt/seagate-4tb"

What is a mount point?

A mount point is simply a directory where your disk becomes accessible in the Linux filesystem.

Step 4 — Configure /etc/fstab

The file /etc/fstab tells Linux what to mount automatically at boot.

Open it:

sudo nano /etc/fstab

Add the following lines:

LABEL=Seagate\0402TB  /mnt/seagate-2tb  ext4  defaults,noatime,nofail,x-systemd.device-timeout=10,x-gvfs-show  0  2
LABEL=Seagate\0404TB  /mnt/seagate-4tb  ext4  defaults,noatime,nofail,x-systemd.device-timeout=10,x-gvfs-show  0  2

Important Notes

• \040 represents a space character inside a LABEL.
• nofail prevents boot from stopping if the disk is missing.
• x-systemd.device-timeout=10 avoids long delays during boot.
• x-gvfs-show ensures the drive appears in Nautilus.

Step 5 — Test Without Rebooting

Instead of restarting immediately, test:

sudo mount -a

If there are no errors, confirm:

df -h | grep seagate

If you see a parse error, inspect the problematic lines:

sudo nl -ba /etc/fstab | sed -n '14,22p'

Optional — Make It Writable Without sudo

Instead of using mount options for permissions (not recommended for ext4), change ownership:

sudo chown -R "$USER:$USER" /mnt/seagate-2tb
sudo chown -R "$USER:$USER" /mnt/seagate-4tb

Final Result

You now have:

• Clean disk labels
• Automatic mount on boot
• Safe boot even if a disk is unplugged
• Proper visibility inside GNOME
• A structured home lab storage setup

This setup is stable, clean, and beginner-safe.

As it is said on zellij webiste:

Zellij is a terminal workspace. It has the base functionality of a terminal multiplexer (similar to tmux or screen) but includes many built-in features that would allow users to extend it and create their own personalized environment.

So, if you’re looking for a modern screen or tmux replacement look no further.

Installation

To get the latest version, it is best to install directly from cargo and in order to do so on Fedora Linux, we need to install some dependencies.

1. First, install cargo using rustup:

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

2. Then, install development dependencies using dnf:

sudo dnf group install c-development development-tools

3. In order to build zellij from cargo, we also need two perl libraries:

sudo dnf install perl-FindBin perl-IPC-Cmd

4. Finnaly:

cargo install --locked zellij

Now grab a cup of cofee ☕️ and wait while it builds.

Conclusion

I hope that you find this short post usefull. Happy hacking! 👩‍💻

When developing an ASP.NET Core application and using Entity Framework (especially when using HotChocolate GraphQL library) to manage your database, you may encounter the following error:

Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application.

Cause

This error typically occurs when a database context (DbContext) is attempted to be used after it has been disposed. This often happens in scenarios where the DbContext instance is not properly managed within your Dependency Injection (DI) system.

Solution

Use the Factory Pattern

The solution to this error is to use factory pattern to create a new instance of the DbContext each time it is needed. This way, you can avoid issues with managing the lifecycle of instances.

1. Register the Factory in the DI Container:

   In your Program.cs:

   var connectionString = builder.Configuration.GetConnectionString("DefaultConnection");
   builder.Services..AddDbContextFactory<LibreBorrDbContext>(options => {
           options.UseSqlServer(connectionString); // or whatever DB server you are using
   });
   

2. Use the Factory in Your Service:

   In your service (BookService):

   public class BookService : IBookService
   {
       private readonly IDbContextFactory _dbContextFactory;
   
       public BookService(IDbContextFactory dbContextFactory)
       {
           _dbContextFactory = dbContextFactory;
       }
   
       public async Task<List<Book>> GetBooks()
       {
           await using var context = _dbContextFactory.CreateDbContext();
           return await context.Books.ToListAsync();
       }
   }
   

Conclusion

Using the factory pattern for managing DbContext instances allows you to avoid issues with disposal and lifecycle management of the context. This method provides greater control over the context and helps you eliminate errors like Cannot access a disposed context instance.

If you have any further questions or need assistance, feel free to reach out! 😊

I’m excited to introduce my latest project – Splitcat! 🎉 After a lot of work, the app is now fully developed in Flutter and ready for download on GitHub and Flathub.

About the App

Splitcat is built entirely in Flutter, ensuring a smooth and responsive user experience on both desktop and mobile platforms. It simplifies file splitting and merging, making it easier to manage large files without needing complex command-line tools.

Some typical use cases include:

• Splitting large files into smaller chunks for sharing via email or uploading to platforms with size limits.
• Merging chunks back into the original file seamlessly.

With ARM64 support, Splitcat runs perfectly on Linux phones like those with postmarketOS or mobian.

Key Features

• Preset and Custom Split Options: Choose predefined chunk sizes for specific apps or create your own.
• Simple and Intuitive UI: Designed with a minimal layout, including large buttons for easy navigation, especially on smaller screens.
• Multi-Platform Support: Flutter enables compatibility across desktops and Linux phones alike.
• Flatpak Package: Available on Flathub for hassle-free installation on various Linux distributions.

Installation

From Flathub:
Install the app with the following command:

flatpak install flathub lol.janjic.Splitcat

From GitHub: Alternatively, download the source code or binaries directly from GitHub.

Greetings, fellow nerds, coders, and open-source enthusiasts! 👋

Welcome to my humble corner of the internet, where we celebrate the beauty of Linux, embrace the power of Free and Open Source Software (FOSS), and dive deep into the art of coding. Whether you’re a seasoned command-line wizard or a brave soul just starting your Linux journey, this blog is for you.

What to Expect?

• Linux Tips & Tricks: From obscure terminal commands to desktop customization magic, we’ve got you covered.
• FOSS Adventures: Let’s explore the wild world of open-source software and the unsung heroes behind it.
• Mobile Linux: Because who doesn’t want a phone that respects your freedom? (Looking at you, PinePhone and postmarketOS).
• Coding Shenanigans: Python, Rust, C#, Bash, and the occasional “How the heck did I break my build again?” moment. No language is safe.

Why Linux?

Linux isn’t just an operating system—it’s a way of life! It’s about freedom, community, and occasionally spending an entire weekend fixing Wi-Fi drivers. But hey, who needs sleep when you can have a perfectly configured system running on your terms?

Join the Fun!

I’ll be sharing my experiences, frustrations (because let’s be honest, there will be plenty), and cool discoveries along the way. If you love tech, open-source, and a bit of lighthearted nerdiness, you’re in the right place.

Pull up a terminal, grab a cup of your favorite beverage (mine’s coffee ☕), and let’s get started!

Stay tuned, and remember: With great power comes great responsibility… and probably some dependency hell.

— Ivan