How to Organize a Linux Install Fest at Your College
A step-by-step guide to running a Linux install fest at your college: distro picks, USB prep, helper ratios, the VM fallback table and the follow-up that turns attendees into contributors.
Admin
FOSS Andhra community volunteer writing about free and open source software, education and developer tools from Andhra Pradesh.
An install fest is a hands-on event where students bring their laptops and leave with Linux installed — guided by helpers, not tutorials. It is the single best first event for a college FOSS club: it produces a visible result on every attendee's machine, it works without speakers or sponsors, and it reliably converts curious students into club members. This guide walks through the whole event, from four weeks out to the follow-up message.
If you are still at the "should we start a club?" stage, read How to Start a FOSS Club at Your College first — the install fest works best as that club's week-5 event. And if attendees have never touched Linux before, our trying Linux for the first time guide is the right pre-reading.
Four weeks out: lock the essentials
- Pick a date and room. A 3-hour slot on a Saturday morning beats a weekday evening: no class pressure, and Wi-Fi and power are quieter. Book a lab or classroom with enough power sockets — one strip per four seats is the minimum.
- Recruit helpers before attendees. The ratio that works: one helper for every five attendees. Ask seniors who already use Linux. Helpers matter more than the guest count.
- Announce early and concretely. "Bring your laptop, leave with Linux" converts better than "FOSS club event". Post in department groups and pin a notice with a QR code to the registration form.
- Collect registrations. A simple form tells you how many USB drives and helpers to prepare — and gives you the list for the follow-up message.
Choosing the distribution (and defending the choice)
For a first install fest, standardize on one beginner-friendly distribution — Linux Mint (Cinnamon) or Ubuntu. One distro means helpers can actually help: every screen the attendees see is one you have seen.
Rules of thumb:
- Mint Cinnamon for older or lower-spec laptops — lighter and familiar for Windows users.
- Ubuntu when the college teaches it or placement prep references it.
- Skip Arch, Manjaro and Gentoo entirely for this event. They are fine distributions; they are not a first afternoon.
- Offer dual boot or full install, never "replace Windows" on someone else's machine without explicit, informed consent.
Preparing the USB drives
One prepared drive per two attendees is plenty if you also share ISOs on the local network:
- Download ISOs in advance from the official mirror — campus Wi-Fi collapses when 40 people download simultaneously. Move the ISO onto a shared drive on the LAN or a couple of laptops with the file ready to share.
- Write the USBs with a reliable tool (balenaEtcher or Rufus) and test-boot one machine of each common lab model beforehand. A drive that works on your laptop may still fail on a locked-down BIOS — check the boot menu key (usually F2, F9, F12 or Esc) for the common models and tape a cheat sheet to the check-in desk.
- Label everything. "MINT-64" beats a pile of anonymous drives.
The one-week-out hardware survey
A single Google Form question per attendee — laptop model, and whether they plan dual boot — tells you almost everything:
- Who has NVIDIA graphics. These need the proprietary driver installed right after first boot; assign those attendees to a helper who has done it.
- Who has a locked BIOS. Some models need Secure Boot disabled or a boot-order change; prep a printed one-pager per common model.
- How many dual-booters. Dual boot needs free disk space — ask them to free 50 GB before the event and defragment if applicable. Shrinking partitions mid-fest with an audience watching is the classic install-fest disaster.
Running the day: a simple floor plan
Structure beats heroics. Four stations:
- Check-in and backup check. Confirm they registered, confirm they have backed up (or have nothing to lose), and hand out the printed instruction sheet.
- Prep table. Shrink the disk, disable Secure Boot if needed, set the boot order. Helpers do the scary BIOS parts.
- Install stations. Boot from USB, walk through the installer (erase-and-install for full installs; the guided "install alongside" path for dual boot). Fifteen to forty minutes each.
- Help / VM fallback table. For machines that refuse to cooperate: run Linux in VirtualBox or VMware Player tonight instead. Nobody should spend the event stuck at a black screen — a working VM plus a plan for the next session keeps momentum.
Common trouble, and the one-line answers helpers should memorize:
- Wi-Fi not working after install — usually a driver; connect by phone USB-tethering first, then install the driver via the Driver Manager (Mint) or Additional Drivers (Ubuntu).
- "Windows isn't in the boot menu!" — run update-grub from Linux; it comes back.
- The clock is wrong in Windows after dual booting — a known time-standard mismatch; one terminal command fixes it.
- "Secure Boot won't let me boot the USB" — disable it in BIOS for the install; most distros work fine with it re-enabled afterwards.
The last 30 minutes matter most
Do not let people drift out the door with a fresh OS and no plan:
- Everyone installs Git and creates a GitHub account while helpers are still in the room.
- Show one thing: open a browser, show them the first contribution tutorial or the club repository.
- Announce the next meeting before closing. The install fest is a recruitment funnel; the next session is the product.
- Photograph the room (with consent) — you will use it to recruit the next batch.
The follow-up message (copy this)
Within 24 hours, send every registrant:
Your laptop now runs Linux — here is what's next. 1) Run the updates once. 2) Install Git and make a GitHub account if you haven't. 3) Try one tutorial from the club's guide this week. Our next session is [date]: we'll make your first open source contribution together. Questions anytime in the group.
Small, specific next steps are what turn an afternoon event into a semester of contributors.
After the fest: keep the loop running
- Debrief the helpers the same day for 15 minutes: what broke, which machines, what to print next time. Every fest should be easier than the last.
- Publish the results: attendance, installs completed, links to the instruction sheet. This is content for the club page and proof for your faculty coordinator.
- Route the interested ones — attendees who want more should meet the club, the projects, and eventually programs like GSoC and internships.
How FOSS Andhra helps
FOSS Andhra supports student clubs across the state through FOSSynC — help with install fest materials, guest speakers and connecting your club to the network. The wider community meets at our events, and students looking for a longer runway can join FOSStar, which opens up our internship program. Starting a club this semester? Write to us — we will help you run your first fest.
FAQ
How many people do we need for it to be worth it? Ten attendees with four helpers is a great fest. Do not chase a hall of hundreds; the metric is working installs, not headcount.
Can we do it without Linux-experienced helpers? You can run a lighter version: a "try Linux in a VM" session with one experienced helper. But for real installs, at least two people who have installed Linux before are non-negotiable.
What about laptops that can't install? The VM fallback table exists for exactly this. Count them as successes if they leave with a running VM and a follow-up plan.
Is dual boot safe? With a backup taken and the standard guided installer, yes — it is the most common path. The risk concentrates in manual partitioning, which beginners should not do at a fest.