Most Linux distributions can run directly from removable media without touching your installed system. The session runs in memory, the internal disk is left alone, and a reboot returns everything to how it was. That makes it a genuine evaluation environment rather than a demo — provided you use it deliberately.
Before you start
Two housekeeping points. First, back up anything on the machine you would miss, because you are about to spend time in a menu that also contains an "install" option. Second, decide what you are actually testing. "Does it feel nice" is not a criterion you can answer in twenty minutes; "does my printer work" is.
The hardware pass
This is the part a live session does uniquely well, because it exercises the same drivers a real installation would use.
| Check | How to test it | What a failure looks like |
|---|---|---|
| Display | Native resolution, correct scaling, external monitor | Wrong resolution, tiny text, no second screen |
| Wireless | Connect to your network and load a page | No adapter listed at all |
| Audio | Play something, then plug in headphones | No output device, or output that does not switch |
| Input | Trackpad gestures, brightness and volume keys | Keys that do nothing, no two-finger scroll |
| Camera and microphone | Open a camera application | Device not detected |
| Suspend | Close the lid, wait, reopen | Black screen, or a session that will not resume |
Wireless and suspend are the two that most often decide the outcome on a laptop, so test them early rather than last.
Live sessions often start with an open-source graphics driver. Proprietary drivers, where a distribution offers them, are installed afterwards. So poor video performance in a live session is worth investigating rather than treating as a verdict.
The software pass
Open the distribution's software manager and search for the five applications you genuinely cannot work without. Note whether each is present, whether the version is recent, and how it is packaged. Then check what is missing and how you would install it — a well-documented third-party repository is a very different prospect from a forum thread describing a manual build.
The workflow pass
Spend fifteen minutes doing something ordinary. Write an email, edit a photo, open a spreadsheet, connect to a shared folder. You are looking for friction: the small interruptions that are tolerable once and infuriating on the two hundredth repetition. Where are the settings? How do you install something? What happens when you plug in a phone?
Questions worth answering before you commit
- Release model. Fixed releases every six months or a rolling model? One brings periodic upgrade work, the other brings continuous small changes.
- Support window. How long is this version maintained? Long-term releases suit machines you want to leave alone.
- Where help comes from. Look at the forum or chat channel. Are recent questions being answered, and answered civilly?
- Documentation. Is there a maintained wiki, or does everything route through community threads?
- Who maintains it. A large team, a company, or one person? All three exist and all three can be fine, but the answer tells you about continuity.
Testing several in one sitting
Comparisons are far more useful when they are close together, and a multiboot drive makes that practical: keep three or four candidate images on one stick and move between them in an afternoon. Use the same checklist for each and write the answers down as you go, because after the third desktop environment they blur together.
Reading the result
A live session is not a perfect prediction. It runs from slower media, it starts with conservative drivers, and it has no post-installation tuning. Speed impressions in particular will improve after installation. But hardware detection, wireless behaviour and the availability of the software you need are all real signals, and they are the ones that turn into daily satisfaction or daily annoyance.