Estimated reading time at 200 wpm: 8 minutes
This one follows from: Man vs. Machine (Spoiler: The Machine Lost). But on this occasion it was Man and Machine [AI] working together in harmony.
Whether or not you agree our Fat Disclaimer applies
The primary motivation for this migration was to reclaim the performance of a 2018 Dell Inspiron 7786. While the hardware remains capable, running Windows 11 felt increasingly sluggish and heavy. Since this device is intended as a secondary sandbox machine for learning rather than a primary workhorse, it presented the perfect opportunity to switch to Linux.
I chose BigLinux because it sits in a unique sweet spot. It provides the performance benefits of an Arch-based system via Manjaro without the steep learning curve. Key deciding factors included:
- Performance: Significantly lighter resource usage than Windows, making the 2018 hardware feel snappy again.
- Btrfs & Snapshots: The default file system allows for instant system rollbacks—essential for a learning environment where breaking things is part of the process.
- Out-of-the-Box Usability: It comes with necessary codecs and drivers pre-configured, minimizing the initial setup friction.
Don’t try this at home if you’re a Luddite!
1. Operating System & Hardware
Core Install
The project hit a wall before it even properly started, highlighting how unpredictable the handshake between hardware and boot media can be. Ventoy failed. I eventually had to pivot back to Rufus. Despite being not recommended, Rufus was the only tool that successfully created a bootable drive that this specific Dell would recognise. It was a reminder that in the world of legacy hardware, sometimes the “incorrect” tool is the one that actually works. This does not mean that everybody will experience the same problems or that Rufus is recommended to everybody for these purposes.
Once the boot issues were solved, the most painstaking part of the process began: identifying the correct target drive. The Dell had two hard drives: A 512GB SSD by Samsung and a 512GB NVMe(SSD) by WDC. Initially it was assumed that the Samsung drive was storage. Careful investigation with Disk Management in W11 revealed which was which. WDC drive contained all my working files. That was not the one to install BigLinux to.
With the drives verified, I performed a clean wipe of that primary SSD. During the initial boot, I checked that the kernel properly handled the Dell’s 2018-era firmware, confirming that basic hardware like the Wi-Fi card and the NVIDIA graphics were supported without needing proprietary blobs right out of the gate.
All software was updated using ‘Software Update’.
AUR Management
One of the first learning curves was handling the Arch User Repository. Unlike Windows where you just run an installation file, certain apps here like onedriver (for MS OneDrive) need to be built or compiled from source. I used the Big Store (likened to Microsoft Store) to manage this, learning that the build process takes significantly more time than a standard binary install because the computer is essentially putting the software together piece-by-piece. For applications where a pre-built version exists—like the Microsoft Edge stable binary—I prioritised those to save time and system resources.
2. Storage & Data Management
Secondary Drive (WDS)
The 512GB WDC drive was preserved as a repository for file storage and it was previously named as STORAGE. To make it behave like a standard Windows D drive, I configured it to auto-mount on startup. This involved setting the mount point so the system recognises it immediately upon login. I also performed some manual cleanup, removing vestigial Windows system files that were no longer relevant in a Linux environment.
Cloud Storage (OneDrive)
Getting OneDrive to work on Linux was one of those things that really felt like a Linux ritual. I used a tool called onedriver because it doesn’t try to sync everything at once—it just streams what you need. But when I went to link it to the folder I’d made, the app just gave me an error saying the folder wasn’t empty. It turns out the file manager had already slipped a hidden file in there just to save my viewing preferences. I had to go into the file manager’s view menu and select the option to show hidden files. Once I could actually see that hidden file and delete it, the folder was truly empty and the connection worked. After logging in through the Microsoft window, the cloud files just appeared. It works like a local drive now, but it isn’t eating up the SSD.
Downloads Redirection
To prevent the primary SSD from becoming cluttered, I remapped the system’s download architecture. First, I changed the download path within the browser settings to point to a folder on the WDC drive (for storage). I then went a step further by updating the system-level location settings. Now, any application that attempts to save to the Downloads folder is automatically redirected to the mechanical drive, ensuring that large installers or media files don’t consume the faster, smaller system drive.
3. Browsers & Applications
Assessment of Brave
Brave was the first browser tested on the new installation, chosen for its reputation for speed and aggressive ad-blocking. There were rumors circulating in 2025 suggesting Brave had become a RAM hog, potentially consuming up to five gigabytes of memory. However, when I performed a manual check on this 2018 hardware, I found no evidence of this bloat. The memory usage was perfectly acceptable, and while I ultimately moved to Edge for better ecosystem sync, the Brave test proved that the Linux environment itself was efficient enough to handle modern Chromium browsers without the performance penalties seen on Windows.
Microsoft Edge
The decision to pivot to Microsoft Edge was a matter of practical consolidation. Having verified that the system could handle a Chromium-based browser efficiently during the Brave test, Edge became the logical choice for its superior sync capabilities. It allowed for the immediate restoration of passwords, history, and favorites across all devices. This move effectively bridged the gap between the new Linux OS and my established digital life, proving that you don’t have to sacrifice your existing tools to enjoy the benefits of a faster operating system.
I bypassed the community-made Git versions of WhatsApp, which require long compilation times and frequently break. Instead, I used Edge to install WhatsApp as a Progressive Web App. This method treats the official web interface as a standalone desktop application with its own icon and taskbar presence. It provides the most stable experience because it relies on the official WhatsApp code rather than a third-party wrapper, and it allows for native system notifications without the overhead of a full traditional installation.
Firefox
Though initially considered as a fallback, I decided against installing Firefox. With Edge performing exceptionally well and handling all necessary sync and extension requirements, adding a third browser felt like unnecessary bloat. The goal of this migration was a lean, efficient system, and since Edge fulfilled all browsing and utility needs, a secondary browser was deemed redundant.
4. Security & Credentials
RoboForm
Managing passwords on Linux presented a specific challenge because RoboForm does not offer a native desktop application for the platform. The browser extension initially appeared inactive because it was searching for a local partner app that didn’t exist. I resolved this by forcing the extension into standalone or server mode, which allows it to communicate directly with the RoboForm cloud. After pinning the icon to the Edge toolbar and logging in via the web-based handshake, the extension successfully activated, providing full auto-fill functionality without requiring a desktop installation.
5. User Experience (UX) Tweaks
File Manager (Dolphin)
To streamline the workflow, I modified the behaviour of the Dolphin file manager. By default, it opened to the system root, but I reconfigured the startup settings to point directly to the Storage directory on the WDC drive. This ensures that the bulk of my data is immediately accessible upon opening the file manager. I also confirmed that the double-click to open behaviour was preserved to maintain consistency with the Windows experience.
Input
The final hardware tweak involved the touchpad settings. I verified that the system correctly interpreted multi-touch gestures, specifically ensuring that two-finger scrolling was active and smooth. This small adjustment was the final step in making the 2018 Dell feel like a modern, responsive machine rather than a legacy device struggling to keep up with its operating system.
So, after about 4 hours of solid work the Dell is now working great. Some may say ‘so far’ – and yes problems are expected ahead which I will deal with.
LibreOffice
This is the totally free ‘word processor’ and ‘spreadsheet’ things that comes with MS Office (for Windows). It’s very advanced and can work well with all Microsoft .docx files and Excel files.
Power Management
You don’t really appreciate what Windows 11 is doing until you have Linux. Task Manager in windows shows what resources are demanding power from CPU, GPU, disks and WiFi. In Linux it’s simply an app called ‘Resources’. The demands in Linux are phenomenally smaller. In W11 CPU would be between 4 and 21% on idle. In Linux total CPU demand on idle, is around 1 to 3%. The GPU and other things are truly relaxed at zero until stressed.
Conclusion
I now have a fully working Dell laptop that is running Linux instead of Windows. All software was free.
AI assistance was invaluable. The whole process took about 6 hours. But wait – if I had to do it without that assistance it would have taken weeks and probably 10 times as much hours.
Breaking the rules is sometimes necessary e.g. using Rufus instead of Ventoy for he installation.
What’s in it for me? Learning something new – stretching my boundaries – gaining knowledge, skill and experience.
