Suggestions for a unified approach to Linux at Repair Cafes

Ok, this is a fun com…

I would like to take a moment to share my perspective on the discussions we’ve had so far regarding Linux interventions in our Repair Cafés. What I am going to express here is not intended as gratuitous criticism or an attempt to impose a single point of view, but rather to highlight what I consider to be a fundamental problem in our current approach: the fragmentation and lack of consistency in our interventions.

I have been observing this for a while, and as the discussions progress, this reality becomes more and more evident: we are complicating things instead of simplifying them. Each intervention seems like a leap into the unknown, with a different distribution, a different desktop environment, varying commands, sometimes untraceable update tools, and above all, a total lack of clear reference points.

We find ourselves dealing with Linux Mint, Ubuntu, Debian, Manjaro, Pop!_OS, Zorin OS, and the list goes on… And each time, it’s a real balancing act for the volunteers who have to juggle between different desktop environments, package managers (APT, Pacman, DNF, Zypper…), and interfaces that never look the same.

Let’s be honest: how can we expect clear and efficient maintenance if each volunteer first has to guess the environment they are in before even starting to troubleshoot? We’re talking about quick repairs, efficiency, and, above all, making sure people leave with a functional PC… but instead, we end up wasting time locating tools, searching for the right commands, and trying to understand why the update manager is different from the one on the previous machine.

If we want to be efficient, effective, and above all, logical, it is crucial to reduce this fragmentation. Not to dictate a choice, but to harmonize our practices. It’s simply a matter of common sense.

I am convinced that harmonizing our practices would be beneficial for everyone: the volunteers, the users, and especially for the sustainability of our interventions. Yes, it may seem a bit pretentious on my part to suggest a common direction, but I am doing it primarily out of professional logic.

When a volunteer arrives at a workstation, they should be able to:

  • Identify the Linux environment at a glance,
  • Know exactly where to find the update, maintenance, and troubleshooting tools,
  • Apply a set of clear and unified procedures,
  • Leave the machine ready to use, no matter who takes over after them.

We are not talking about a massive investment in training here: 30 minutes are enough to understand the basics, the essential commands, and the main maintenance points. This can be done:

  • On a virtual machine to practice without any risk,
  • On a recovered PC to get hands-on experience,
  • Or even with a small practical guide, readable in less than an hour, summarizing the key points.

The idea is not to restrict but to set a common direction. Because in the event of a volunteer’s absence, someone else could pick up the work without struggling for 20 minutes to understand what was done before them. A clear, unified, and coherent system is a win-win for everyone.

I do not claim to have the magic solution, but I am convinced that if we focus on two flagship distributions (a lightweight one for very old systems and a more capable one for PCs that are still powerful, even if it means some greenwashing at the expense of common sense sometimes) and if we train volunteers on these environments, our interventions would be faster, smoother, and more understandable for users.

This is a call for logic, efficiency, and, above all, a harmonized user experience. Because repairing is not just about fixing a problem: it’s about leaving a machine in good hands and ensuring that, even if someone else takes over, the troubleshooting can continue in the same direction, without headaches.

To sum it up!

If everyone sticks to their own preferred distribution and personal comfort, we’re never going to get out of this maze. The truth is, not everyone has the skills and experience to handle all the systems we work with. Not everyone works with this technology 24/7, and not everyone is familiar with multiple solutions. We don’t all share the same background, profession, skills, or education.

But one thing is clear: everyone wants to move forward in the same direction. That’s exactly why it’s important to listen, learn, and grow these skills. Whether you are old, from the Middle Ages, young, or still studying, we all have a thirst for learning. Otherwise, we wouldn’t be having these discussions, and other professionals or even myself wouldn’t be here answering your questions. If everyone had all the knowledge in the world, there would be no need for these conversations.

Each person has their own experiences, their own ways of doing things, certain habits (good or bad), prerequisites (useful or not), fears (justified or not), and a unique background. But if we all keep going in different directions like this, we’ll still be discussing it 20 years from now, asking the same questions about Windows 28 after the end of Windows 27…

We need coherence, unity, and a clear direction to avoid running in circles.

Road Trip’

Current Issue: The Fragmentation of Linux Distributions in Repair Cafés

When a volunteer is faced with a Linux machine in a Repair Café, they might encounter a wide variety of different distributions, each with its own specificities:

  • Linux Mint (Cinnamon, MATE, XFCE)
  • Ubuntu (GNOME, KDE, Budgie)
  • Debian (Stable, Testing, Unstable)
  • Manjaro (KDE, GNOME, XFCE)
  • Zorin OS, Elementary OS, MX Linux, Pop!_OS, Fedora, and so on…

Problem:

This diversity leads to several complications:

  1. Desktop environments are not the same (GNOME, KDE, XFCE, Cinnamon, etc.).
  2. System commands vary from one distribution to another (apt, pacman, dnf, zypper, etc.).
  3. Graphical interfaces and management tools are different: Update Manager, Synaptic, Discover, etc.
  4. Update and maintenance procedures are not unified.
  5. Software support (drivers, codecs) is not always consistent.

Objective: Create a Common Knowledge Base for Volunteers

The idea is to standardize the knowledge of volunteer repairers around a reduced set of Linux distributions for common interventions. This would allow us to:

  • Reduce the time spent identifying the system and searching for commands.
  • Standardize troubleshooting procedures.
  • Improve the efficiency of interventions.
  • Provide a consistent user experience for the people being helped.

Harmonization Proposal: Two Key Distributions + a Universal Boot Tool

I propose focusing on:

  1. Linux.
  2. Windows.
  3. Ventoy USB Multi-Boot: A multi-boot USB key allowing you to launch any Linux ISO from a single interface.

Detailed Action Plan:

Preparation of a Universal USB Key (Ventoy)

  • Download and install Ventoy on a USB key of at least 32 GB (16 GB if only two distro like Mint and W, X or L Ubuntu).
  • Add the following ISOs to the key:
    • Linux Mint (all version)
    • Xubuntu, Lubuntu, Wubuntu LTS
    • Tiny 11 (for i3-2xxx to i7-7xxx but in certain case, the next ISO is good enough too ^^)
    • Windows 11 (23H2 unlocked, ES or tweaked version)
    • Rescatux (repair and recovery tool)
    • Clonezilla (backup and restoration)
    • GParted Live (partition management)
    • Define common hyper lightweight linux for very very very very very very very very very very very very very very very very very very very very very very very very very very old pieces

Standardization of Procedures for Volunteers

A manual could be written with the following sections:

Startup and Distribution Recognition

  • Quickly identify the desktop environment (Cinnamon, XFCE, GNOME, KDE…).
  • Check available commands (apt, dnf, pacman).
  • Locate the update managers (MintUpdate, Discover, etc.).

Standardized Troubleshooting Procedures

  • Internet connection (Wi-Fi, Ethernet, Proxy).
  • Boot issues (Grub, UEFI, Secure Boot).
  • System updates (apt update && apt upgrade).
  • Driver management (Driver Manager for Mint, Additional Drivers for Ubuntu).
  • User password reset (recovery mode or passwd user).
  • Boot repair (Rescatux or Boot-Repair from the live USB).

Snapshot Creation and Backups

  • Clear explanation of Timeshift and Clonezilla.
  • Procedure to perform a snapshot before any intervention.
  • Restoration in case of critical failure.

Quick Training for Volunteers

A short training program lasting a few hours could be set up with the following components:

Live Demonstration of Linux Mint and Xubuntu

  • Hands-on exploration of the desktop environments, update managers, and system settings.

Simulation of Common Issues

  • Troubleshooting simulations for:
    • Black screen issues
    • Network problems
    • No sound
    • Boot failures

Practice with Backup and Recovery Tools

  • Hands-on training with:
    • Timeshift for system snapshots
    • GParted for partition management
    • Clonezilla for backup and restoration

Next Step: Setting Up the Unified Troubleshooting Manual

Would you like us to start writing this detailed manual, with a chapter-by-chapter structure?

Proposed Structure:

:one: Environment Identification

  • Recognizing the desktop environment (Cinnamon, XFCE, GNOME, KDE…)
  • Detecting the Linux distribution in use
  • Checking available package managers (apt, dnf, pacman, etc.)

:two: System Startup and Recognition

  • Boot process and GRUB understanding
  • UEFI vs Legacy BIOS
  • Secure Boot management and deactivation if necessary

:three: Common Interventions

  • Network troubleshooting (Wi-Fi, Ethernet, Proxy)
  • Driver installation and updates (graphics, audio, network)
  • Password recovery and user account management
  • Boot repair (Rescatux, Boot-Repair)

:four: Maintenance and Updates

  • System update commands (apt update, apt upgrade)
  • Setting up automatic updates
  • Managing package installations and removals

:five: Backup and Recovery

  • Creating snapshots with Timeshift
  • Full system backups with Clonezilla
  • Partition management with GParted
  • Restoration procedures in case of critical issues

Complete Checklist of Questions/Answers for the Average User:

Below is the concept of a decision tree, step by step, where each question leads to a sub-question or a solution. This method is designed to guide the user smoothly and intuitively toward the right solution, without unnecessary jargon.

Installation and Updates

  1. Is Linux already installed on your computer?
  • :white_check_mark: Yes → Move to the next question.
  • :x: No → Do you want assistance with the installation?
    • :white_check_mark: Yes → Choose a suitable distribution (Linux Mint for newer PCs, Xubuntu for older ones).
    • :x: No → End of the assistance.
  1. Is the version of Linux installed up to date?
  • :white_check_mark: Yes → Great! Just keep checking regularly.
  • :x: No → Would you like to learn how to do it yourself?
    • :white_check_mark: Yes → Open the Update Manager → Scan → Install updates.
    • :x: No → Enable automatic updates in the Update Manager.
  1. Would you like updates to be installed automatically?
  • :white_check_mark: Yes → Activate automatic updates in the Update Manager.
  • :x: No → You will need to check manually every week.

Backup and Security

  1. Would you like to secure your system against data loss?
  • :white_check_mark: Yes → Do you want it done manually or automatically?
    • :white_check_mark: Manually → Learn about Timeshift and backup tools.
    • :white_check_mark: Automatically → Set up Timeshift for regular snapshots.
  • :x: No → Be aware of the risk of data loss in case of major issues.

Common Problems

  1. Is your PC running slowly?
  • :white_check_mark: Yes → Do you have enough RAM?
    • :white_check_mark: Yes → Check CPU usage and running processes.
    • :x: No → Consider adding RAM or switching to a lighter desktop environment (XFCE).
  • :x: No → Everything is in order.
  1. Is your Internet connection not working?
  • :white_check_mark: Yes → Is the cable plugged in or is Wi-Fi enabled?
    • :white_check_mark: Yes → Try another cable or another Wi-Fi network.
    • :x: No → Plug in the cable or enable Wi-Fi.
  • :x: No → Everything is in order.
  1. Is there no sound?
  • :white_check_mark: Yes → Are the speakers connected and turned on?
    • :white_check_mark: Yes → Check the system sound settings.
    • :x: No → Connect the speakers or turn them on.
  • :x: No → No further action needed.

Migration and Major Updates (If its necessary to do…)

  1. In 2029, would you like to migrate to the next version of Linux Mint?
  • :white_check_mark: Yes → Follow the major update guide (e.g., 22 → 23).
  • :x: No → Security updates will stop; you will need to consider alternatives.

Hardware and Peripheral Issues

  1. Is your printer not working?
  • :white_check_mark: Yes → Is it detected by the system?
    • :white_check_mark: Yes → Try reinstalling the drivers.
    • :x: No → Check the cable connection or try a different USB port.
  • :x: No → Nothing to fix.
  1. Do external USB devices not show up?
  • :white_check_mark: Yes → Try another USB port or cable.
  • :x: No → Everything is functioning correctly.

Advanced Troubleshooting

  1. Do you want to perform advanced maintenance?
  • :white_check_mark: Yes → Are you comfortable with terminal commands?
    • :white_check_mark: Yes → Use commands for cleanup (sudo apt autoremove, sudo apt clean).
    • :x: No → Stick to GUI tools for safety.
  • :x: No → No further action required.
2 Likes

@Joslet_Nicolas. I’ve moved your post into a new topic, as it covers more than just software updates. Thanks!

2 Likes

This is good.

Given Windows 10 will not reach end of life until mid October are you suggesting a timeline - or urging for all this ASAP?

Could suggest a process similar to how parts of a Linux distro are locked down as the release date approaches.

The moderators here could say something like “OK - it’s now July - we need to shortlist candidates by the end of this month” - similar for documentation - and so on.

Was going to urge, also, that a PDF ‘Read Me’ is left on the desktop of each new install (specific for that distro) explaining how to update, how to download & setup Timeshift (which isn’t always included ‘out of the box’) - and anything else useful. Hopefully - such a PDF could do a lot to reduce the workload on Repair Cafe volunteers.

For some time now - reading what people were often saying in these discussions - it left me thinking “no repair volunteer, who isn’t familiar with Linux, is going to want to try distro after distro for each install until they find the best one”.

1 Like

I think I’m the only one doing it and capable of doing it and maybe Joyce as well! And, in a way, that’s exactly what we’re already doing indirectly.

I also have the equipment to do it. I can test on about 7 to 10 similar PCs at the same time. I can even get machines from each generation to evaluate each solution one by one.

I think the Dummies Guide to Linux is good but… Your guide is aimed at Repair Volunteer faced with a Linux machine that is having issues
What I - and presumably others - need is a Dummies Guide to installing Linux onto an end of life Windows 10 PC. Whilst not exactly tech-ignorant, I am on the start of this journey and am still getting to grips with the naming and the differnce between DE and DM.
I wonder if this thread and the thread on Finding the best Linux solutions for new users need to be combined. In that way a Fixer will have a guide to installing Linux and then fixing problems when the bringer returns!!!

1 Like

The installation process for Linux distributions has become increasingly standardized over the years. Whether it’s Ubuntu, Fedora, Debian, or even lightweight versions like Xubuntu or Lubuntu, the steps are largely consistent:

  1. Boot from Installation Media –> Typically a USB stick or DVD with a live environment.
  2. Select Language and Keyboard Layout –> The initial setup screen is almost identical across distributions.
  3. Network Configuration –> Wired connections are usually automatic; Wi-Fi setup is straightforward.
  4. Disk Partitioning –> Most installers offer guided options for automatic partitioning or advanced manual configurations.
  5. User Account Creation –> Creating a username, password, and defining admin privileges.
  6. Installation Process –> Files are copied, system configurations are applied, and bootloader setup is handled automatically.
  7. First Boot and Updates –> Once installation is complete, the first boot is almost the same for all distros: update checks, driver installations, and basic setup steps.

Because of this uniformity, having a generalized installation guide makes a lot of sense. It would allow newcomers to understand the process step by step, no matter which Linux distribution is chosen.

We could structure the guide to include:

  • Standard Installation Procedure –> A universal walkthrough covering the 7 main steps mentioned.
  • Different Scenarios –> Dual-booting with Windows, encrypted installations, legacy BIOS vs. UEFI, etc.
  • Post-Installation Checklist –> Essential updates, driver installations, security configurations.
  • Troubleshooting Common Issues –> Boot errors, display problems, network issues.

Additionally, it would be useful to complement this with:

  • A follow-up guide for managing updates, resolving issues, and configuring backups.
  • A tracking sheet for volunteers to document installations and any problems encountered.
  • Possibly, online support sessions for live assistance during installations.

This would not only streamline the process but also ensure consistency and quality in installations across different environments.

We could even consider offering online support for certain sessions…

1 Like

The first thing to consider before doing anything else, in an install party or in a repair cafe, is to ask the users what about their data?

  • Do they have backups?
  • If yes, did they also backup the passwords they may have left in their web brower? (Not something I advise, but many users do). What about the bookmarks? (Favorite…) What about their contacts, their calender(s)?

Each of these kinds of data have their solutions, some need to be setup in Windows before starting.

For instance, if they use Chrome browser or Edge, you can install Firefox, make it retrieve all data from other web browsers, and setup an account at mozilla.org (from within the browser setup), to synce those data, so they can retrive it later using a Linux distribution, with Firefox in it.

Then let’s say you test the computer with a live Linux and you realise the hard drive is a slow one (5400rpm - rotation per minute, or older, 4200rpm). If the HDD is good, it could be removed and installed in a USB external case, and serve as backup for the data.
Then in the computer could a SSD be installed. (sooo much faster).

Last but not least : do they use Dropbox, or other tools to keep and share data on the cloud? This can be tricky when not aware. The solutions exist to have compatible clients, we just have to search for them.

LibreWolf is indeed a solid choice! It’s basically a hardened fork of Firefox, focused on privacy, security, and removing telemetry. It’s lightweight, respects user privacy by default, and it’s built with strong customization options.

Compared to Firefox, it strips out a lot of the tracking and unnecessary bloat, making it more efficient, especially for older machines or resource-limited environments like those in Repair Cafés. Plus, it comes pre-configured with privacy-focused settings, meaning less tweaking is needed out of the box.

If the idea is to have a browser that’s light, secure, and efficient, LibreWolf checks all the boxes. Combined with something like uBlock Origin and HTTPS Everywhere, it’s pretty much rock solid.

For installation instructions, you can visit the official LibreWolf website: LibreWolf Installation Guide

1 Like

And me. And many, many people who attend repair events but don’t post here.

Which is what the guide that I wrote and linked to on the first WinEOL thread here does.

The Restart Project hasn’t called for any kind of intervention. The initial call from the Restart Project was quite simple:

The Restart Project supports community repair but it doesn’t prescribe technical solutions. So far they have compiled and published an introduction to the Win10EOL issue with links to helpful resources. The end of Windows 10: A toolkit for community repair groups

We are all free to build and publish our own stuff - guides, downloads, whatever - and will be able to link to that as part of the Linux support team. Adoption will be up to the community. Btw, The Restart Project is a tiny charity funded by donations and cannot afford to host gigabytes of digital downloads.

The previous message is neither offensive, aggressive, nor inappropriate. I was simply sharing my thoughts and expressing how I feel about the topic without insulting or putting anyone down. It was merely a constructive perspective on a subject that matters deeply to me.

This message is not aggressive and does not violate the community’s rules. I believe I have the right to disagree with the opinions of others respectfully.

Reported? Really? What happened to freedom of expression?
If sharing a well-structured, respectful opinion can be flagged, it raises genuine concerns about how open dialogue is managed in this community. Healthy debate and differing perspectives are crucial for growth and understanding. Silencing opinions simply because they differ from the majority contradicts the very essence of open discussion and progress.

We should be able to exchange ideas openly, even when we don’t agree. This is how we learn, improve, and move forward together. Differences of opinion shouldn’t be shut down and they should be heard, understood, and debated constructively. That’s the spirit of community.

1 Like

Hello everyone,

As ever, I appreciate the passion that’s being brought to this conversation.

It looks like there’s some disagreement about what we’re trying to achieve and how best to do it.

Disagreement is ok and often to be expected in a community space like this, so it’s important that when we disagree, we do so kindly and remember that no one has a fully complete perspective - let’s remember to share our perspectives with humility. I’ve set this topic to slow mode to allow for more time for reflection before posting.

As mods, perhaps we should have offered a little more guidance on Restart’s aims here.

Our primary purpose is to offer basic guidance around this issue to people who organise community repair events. While we hope to provide some additional resources (such as a brief intro on alternatives to Windows 11 for unsupported devices), our intention is to focus on listing 3rd party resources that cover the technicalities (e.g. on how to install/use Linux).

As Monique said, we support community repair but don’t prescribe technical solutions.

@Joslet_Nicolas, it sounds like you have something more ambitious in mind. Though I’m wondering whether the length of some of your posts makes it a little hard to understand what that is.
Would you be able to outline your concept in a few sentences?

4 Likes

It’s not more ambitious, and it’s actually quite simple to summarize:

  • Establish a common guideline to present to our volunteer repairers.
  • Simplify the handover process and preparation steps.
  • Unify the approaches to make transition procedures smoother.
  • Properly inform and assist visitors who come to us for help.
  • Stop prioritizing X’s solution over Y’s because sometimes, both are right.
  • Eliminate big egos and focus on doing things better than just good.
  • Focus on guiding and advising properly instead of just talking and writing without action.
  • Create a unified methodology (GOOD, COMPLETE AND USEFUL TUTORIALS) for processes and practices.
  • And I’m sure there are other points I might be forgetting…

We need to create distributable/printable guides for as many topics as possible and not just IT. In my opinion, that’s the essence of Restarters. That’s what I was sold on, but right now, I’m disappointed because there’s a lot of talk and not enough action. And when there is action, I feel like it’s not enough.

Clearly :point_right: I want to do more, give more, and help more, instead of just talking about things we already know. I’m offering my time, just like others here. I can dedicate hours to it if I’m passionate about it, but right now, it feels like we’re being asked to climb Everest. I’m ready to take on the responsibility of the project if necessary.

1 Like

Monique, if I may,

A few questions come to my mind.

  • First:
    your documentation is a google sheet, how come? Usually communities make use of dedicated documentation tools to provide tutorials, how-to’s…

  • Second:
    Your documentation does not start with what comes first, which should be the data, and defining what personal data is and what it includes.

A real life example when I started providing professional services:
A client of mine wanted to switch from Windows XP to Linux. I asked him about the data. What was it that needed saving? I got the information or so I thought.

I copied the whole system to another device before proceeding, as I used to. (Then the data could be accessed, but Windows XP could not be booted anymore).

Once the job finished, all shiny and nice (a Lubuntu where I had installed the Windows Vista backgrounds! It was gorgeous!) well once all finished, his data in the Lubuntu he asks «what about my contacts? I have 111 contacts needed for my work!»

OMG ! I tell him, where did you have it, why didn’t you tell me? His answer? “That’s your job”. ':-S

I looked for, found, and retrieved the database from the contacts tool of that time (which was already obsolete, even then), ran it through a Windows 7 in the “Contacts” tool to transform it into another format, from there ran it through Kcontacts from the KDE suite, from there created all formats available, put the one fit for the contacts application in Lubuntu, into his system, and this was the end of the story.

But that could have ended not so well. Because users have no idea. Lately, a client wanted a tower with Linux in it.

He finally installed Windows, because he was using several proprietary tools to exchange documents with his clients, and didn’t have time to let me try to install the equivalents to Dropbox clients and such. There was no harm done there, just a time related issue.

Being thorough before anything else, regarding data and habits is always important to consider.

  • Third:
    You say some things at the beginning, which is quite uncomplete, partly wrong, and confusing:

Issues with dual booting Windows
If the visitor wants to keep Windows 11 and install Linux alongside, be aware that [Microsoft
updates have been known to break the bootloader](https://www.bleepingcomputer.com/news/
microsoft/august-windows-security-update-breaks-dual-boot-on-linux-systems/) and fixing it will > be beyond the ability of a novice.

Dual-booting with Windows 10 can be OK - if it works. It might be wise to avoid updates. Bear in
mind that Linux would then be installed after the Windows partition and removing Windows at a
later date will mean that the Windows partition cannot simply be merged into the Linux partition. It > can be used for something else, e.g. data, games, backups or another OS. To merge the two
partitions will destroy all contents and require a clean install of Linux.

After 21 years of using, installing, following what’s new, installed with many different ways, Linux boxes, Window boxes, dual-boots, for myself, for clients : I’ll have to tell you this is not even that simple.

→ Dual-booting may break the boot to Linux : true for every Windows from the first XP I’ve known up to Windows 10. I don’t know W11 much yet, but I’m sure in this regard it is most probably also true.

→ Solution : have in Windows a bootloader that boots both additionnaly to the Grub bootloader. It will always be there, whatever the updates in Windows.

/!\ I use Grub2Win, but I won’t recommand it for everybody, it is graphical but not really easy to understand.

→ An easy one, freeware, would be EasyBCD. https://neosmart.net/EasyBCD

(I used to find the look of the boot screen ugly when I used it, but it works and it is easy to setup).

→ Installing Linux after Windows : Yes.

→ Installing Linux after Windows partitions : absolutely not!.
Nowadays there are several partitions in a drive where Windows has been installed, some at the end of the disk (on the right in Gparted), which must NOT be moved or removed. They are after the main storage space, and should you move them, you could make Windows impossible to boot.

The right way is to use the Windows disk management tool to shrink the data partition (the main one which is more or less in the middle), boot to Linux, choose this empty space to install, in automatic mode or in “something else” mode.

If you later want to remove Windows, you can use Gparted Live, remove Windows partitions, then move your Linux partitions from the right to the left, one after the other, then enlarge the last one to the right (which should be the partition dedicated to “/home”).

A partition scheme for everyday use Linux boxes:


[ System 15 to 60 GB depending on needs and available space (format to Ext4)]
[ESP/EFI 4GB (format to Fat32)]
[Home partition, mounted on “/home” (format to Ext4, give it the rest of the available space)]


System 15GB is enough when few applications are needed, but then 25GB is better for future major versions upgrades as they need lots of space for the temporary files. If in need of many applications, go for 60GB for the system.

Don’t use SWAP partitions. Since majority of computers make use of SSD’s, it is replaced with a swap file automatically created under the “/” of the system and setup automatically during installation.
If in need for even more swap, install the zram-config in Ubuntu / zram-tools in Debian to get additional virtual RAM. (Swap to disk wears off drives, SSD’s lasting capacity depends on avoiding unnecessary wearing).

SWAP : https://en.wikipedia.org/wiki/Swap
ZRAM : https://en.wikipedia.org/wiki/Zram

If in need to repair a broken boot : a live Linux can be used, following carefully some documentation.
one, sometimes works : https://help.ubuntu.com/community/Boot-Repair

I have not found its equivalent in English, if interested, run it through translate google:
https://doc.ubuntu-fr.org/tutoriel/comment_restaurer_grub
(“How to restore GRUB”).

I haven’t read the rest of your documentation page. I can volunteer to do so, if you would like me to.

Best regards,
Joyce

1 Like

I hesitate to join in this discussion between heavyweights! I should point out that like most Fixers, although “techie” i am no computer expert.
Can i explain my two needs.
In one role i volunteer for a charity that takes unwanted laptops and cleans up to give to refugees to facilate digital access. So now we have W10 machines that cannot run W11. No data to preserve and just need for basic functions. What i/we need is a recommendation for a version of Linux to install as a clean install on to a wiped or new SSD. Following this, we need the most basic of guides to give out with the laptop on how to use the Linux, including how to add apps such as Chrome and gmail, and how update Linux intelf

The other scenario is in the Fixing Cafe (or for my wifes computer). The PC will not run W10. She will never cope with dual booting. She only uses basic tools ie; email (gmail), youtube, word processing etc. My plan is to take out her SSD and make it an external drive in a caddy. Put in a new SSD and install a Linux that looks as much like Windows as possible. With regards to local data, i plan to copy Downloads/Documents/photos/videos onto the new C drive for ease of access.
So the Dummies Guide to W10 ->Linux needs to be aimed at enthusiasts/fixers like myself and not experts. But it still needs to be short and not overly technical. The bringer needs the separate very basic guide on using Linux
Boyd

1 Like

@Boyd_Goldie, I completely agree with your message, but I want to highlight something important : if the guide isn’t complete and detailed enough, you’ll likely keep running into trouble whenever a slightly technical issue comes up.

The goal of a beginner’s guide isn’t to be technical or overwhelming you and it’s to thoroughly cover a wide range of common problems you might encounter (installation, partitioning, updates, antivirus, etc.), and most importantly, to show you how to solve them on your own.

The guide I’m currently working on follows that approach. Yes, it will be a bit long, but it will be well structured and illustrated, with clear captions to explain each step through visuals. You’ll be able to skip advanced sections if you want and focus on what matters to you.

The goal is for you to come out of it more confident and not necessarily an IT expert, but someone who understands what they’re doing and can help guide others in turn.

With a unified guide that everyone can follow and make their own, it becomes much easier to help someone when an issue arises. You can directly refer to the exact step in the guide where things went wrong, or follow the step-by-step process to identify the root cause and solve it.

The resul t: time saved, faster support, and much greater efficiency, both for the person experiencing the issue and the one helping out.

I think some people see themselves as IT hotshots who believe they’ve got the ultimate solution in one answer that fits every problem and every situation. But let me assure you : even those of us with experience, if we’re being honest, are still learning new things every single day.

Every situation, every machine, every user is a new adventure. And that’s exactly what makes this work exciting! Because if everything were predictable and solved in advance, we’d get bored really fast.

First: the Google sheet is not “documentation”, it is just my personal record of laptops on which I test a variety of Linux distros. The tab titled “Notes” explains that.

Second: I find that assessment of the requirements is useful before spending lots of time migrating data. If the user has needs that will not be met by Linux, i.e. they really will need Windows or could use Chrome, or if the hardware is beyond redemption, then it is worth discussing this first and managing their expectations. We ask people to backup their own data to their own device, if they can, to save time.

Hello Monique,
Your answers make me feel confused. I do have the feeling my contribution (with what I hope is a very polite and positive criticism of the content of your notes related to dual-booting Windows), is completely disregarded. Taking personal time to bring forth my know-how and experience to add to someone’s (your’s or anyone else’s on forums and in communities dedicated to repair/refurbishing/dealing with free software) is something I take very seriously.

Everyone has experiences which differ in some ways, and match in some other ways. Well I asked the question on purpose : “should I continue the reading of this document of your’s”, implying, to eventually bring more feedback, or is it something you wouldn’t want to challenge?

Hi all,

Just stepping in to say, please let’s keep these discussions friendly and positive.
Having different opinions is of course fine, and sharing your own experience is welcomed, but let’s keep this an open space for dialogue and learning from each other.

We’re all working towards the same goal here!

Thanks.

Sure, you should always ask your questions, and ask more if there are details needing more clarity.

What would “intelf” be?
Apart from that word, you make me think : instead of large documentations, maybe documentations written with precise cases such as this one would be more relevant and easy to use?
(I don’t write documentation here, but I do elsewhere, so this is a matter which could interest many communities).

A basic guide for this case could be:

  1. Get Lubuntu here : https://cdimage.ubuntu.com/lubuntu/noble/daily-live/current/ it is light and easy to use.
  2. Once downloaded, burn it to USB drives and / or DVD’s (if the target computers have DVD enclosures)
  3. For USB drives, you can use Rufus, Balena Etcher, Ventoy, or in Linux, Gnome Multi Writer (tried it recently, it is in the repositories, uber easy, works perfectly)
    3bis) for DVD’s you can use infra recorder in Windows or any burning tool in Linux
  4. Start the USB drives or DVD’s in the computers, using the relevant boot stanza
  5. Start with the boot option «Try before installing», so you can test how the computer reacts
  6. If satisfied, double-click on the Install launcher, and follow what is on the screen

7)If not satisfied, for example, it is still slow, try to install a small SSD, add RAM, or change distribution

The method to install is slightly different than the one in Ubuntu / Lubuntu / Xubuntu… so the chapter “2.5 Installation process - 2.5.1 Detailed installation steps” with screenshots, in this pdf book can be very useful.

  • After install, to update, maintain, add programs, remove programs, you can use the Synaptic package manager, and the Gnome Software tool (this one probably needs to be added using Synaptic once the install process is finished and you have rebooted).

191 pages in the English version, I bet you’ll find everything you need there, including things Gmail related.

What is in the actual SSD? Is it Windows? Don’t forget to export bookmarks and passwords, or synchronize them with a feature from the web browsers, before removing the SSD drive. They won’t come along with the pictures and other data files. (You will need to check the menus in the web browser, in Chrome that would be on the top right, in the 3 vertical dots).

A paragraph about drives namings:
In Linux, what stands for “C:” drive has for name /dev/sda when it is the first disk, or /dev/sdb when it is the second disk (a second hard drive, or a USB drive… ) for all SATA drives.

M2 drives have other names, such as /dev/nvme0n1, or so. The /dev part represents the path to the “dev” directory in the top part of the system. So, “C:” when we talk about the filesystem is called “root”, and written /.

We often refer to the drives as /dev/sdX where “X” will be either “a”, or “b” or “c”, depending on what devices has been started first.

This is how you will see them named, in the Gparted partitions management tool, if you start it from within Linux (you can have a look, in a live distribution, as long as you are careful and don’t destroy partitions before being sure you want to).

Also when I partition, I give names to partitions. The option is available, and it can be handy later to know which one is related to what usage (system partition can be named after the distribution, ie : “mxlinux”, “xubuntu”, or “lubuntu”, and when creating a dedicated partition for /home I would always name it just “home”.

It is handy, when in need of starting a live to reinstall, or to repair, one day in the future…

When you retrieve data from a Ntfs (Windows) partition, to a (Ext4) Linux partition, it will not get the rights and permissions as you should.

I can talk about that later. Or you can check this page, and bookmark it for future reading: https://www.redhat.com/en/blog/linux-file-permissions-explained
There are also easy to use command lines to fix permissions recursively for all directories, and for all files, in a single effort.

(I wonder if someone thought of a GUI windowed tool to do that, in the context of migrations from Windows?)

I love this, it is extremely informed and thorough, @Joslet_Nicolas !

2 Likes