01 NAME
01 / 09
Open the manual.
Run the machine.
Real Linux, on real devices, with real problems to solve. Utora is building hands-on activities for Years 7 to 12 in Australian schools, from a first command to a web page served from a board on your desk.
We are pre-launch and looking for a first school to pilot with. That is the honest state of things, and the rest of this page is written the same way.
UTORA(1) Utora Manual UTORA(1)
NAME
utora - hands-on Linux for high-school students
SYNOPSIS
utora pilot [--year 7-12]
[--format lesson|club|enrichment]
[--weeks 4-8]
DESCRIPTION
Real Linux, on real devices, with real problems to solve. Utora is pre-launch and looking for its first school pilot. Proposed pilot; details are agreed with each school.
SEE ALSO
hello@utora.dev
Type help and press Enter. Arrow keys recall earlier commands; Tab completes.
02 SYNOPSIS
02 / 09
A pilot is a small, time-boxed trial with one group of students at one school.
utora pilot [--year 7-12] [--format lesson|club|enrichment] [--weeks 4-8]
- --year 7-12
- Which year groups take part. A pilot can begin with a single group, such as one Year 9 class or a Year 7–8 club, and widen later if it works for your school.
- --format lesson|club|enrichment
- Where it happens: inside a timetabled lesson, at a lunchtime or after-school tech club, or as an enrichment block. You choose what fits your week.
- --weeks 4-8
- How long it runs, in school weeks. Four to eight weeks fits inside a term and leaves room to look back at what happened.
03 DESCRIPTION
03 / 09
From using computers to understanding them.
Most students are confident users of devices. Linux is a good place to look underneath: files are real files, programs are things you can read and run, and when something breaks there is usually a message that says why.
That habit is the point. Read the error, make a guess, test it, try again. It is problem-solving you can practise on a small machine without needing to be an expert, and it builds the kind of digital confidence that carries into every other subject.
Activities can connect to the Australian Curriculum: Digital Technologies. Which content descriptions and year levels they connect to is something we work out with each school, rather than a claim made in advance.
Fig. 1: parts, and what students might do with them. Illustrative; not a specific model.
- GPIO header Wire an LED or a button and control it from a script.
- SoC and heat spreader Check what the processor is busy doing with a few commands.
- Memory Watch memory fill and free as programs start and stop.
- HDMI and power Connect a screen, or run it headless over the network.
- SD card Write an image, boot from it, and see why the card matters.
- USB ports Plug in a drive and find where it appears in the file tree.
- Ethernet Find the device’s address and reach it from another machine.
04 PATHWAYS
04 / 09
Three steps, each one a bit further from the desk.
Illustrative Which pathways run, and in what order, is agreed with each school.
-
Explore
Start on a desktop. Open a terminal, move around the file system, read a file, make one. The goal is for the shell to stop being strange and start being quick.
pwd ls cd cat mkdir
-
Connect
Move to a device. Log in to a small board over the network, find its address, copy a file across, and see that “the computer” can be a thing on a shelf. Network use is agreed with your IT team first.
ssh scp ip a ping
-
Create
Build something other people can reach. Write a script, start a simple web server, change a page, and watch it update in a browser on a different machine.
nano python3 -m http.server chmod
05 EXAMPLES
05 / 09
A sample six-week pilot.
Illustrative One class, one lesson a week. The real plan is built with your teachers, around your timetable.
| Week | Focus | Students will… |
|---|---|---|
| 01 | Hello shell | open a terminal, run their first commands, read what comes back, and keep a log of what they tried. |
| 02 | Files & the tree | move around the directory tree, create, copy and move files, and read a path like a map (see Fig. 3). |
| 03 | Permissions & safety | read the output of ls -l, change who can run a script, and talk through why careful defaults protect everyone. |
| 04 | Raspberry Pi | meet a single-board computer: power it, log in, and find it on the school network. |
| 05 | Serve a webpage | write a small page, serve it from the device, and have a classmate open it from their own machine. |
| 06 | Showcase | show a project to the class, explain how it works, and reflect on what they would try next. |
Week 02
The tree students learn to walk. drwx… on the right shows who may read, write or enter each item.
06 FOR SCHOOLS
06 / 09
What to expect.
- Your devices, your network
- Works with school-approved devices and networks. Anything that needs a network change is raised with your IT team first.
- Browser or hardware
- Browser-based or school-hardware options, discussed with the school. Nothing needs buying before you have agreed to it.
- Teachers steer
- Teachers shape pace and goals. The activities flex around your class, not the other way round.
- No surprise accounts
- No student accounts with third parties without the school’s approval.
- Privacy-first
- We ask for what a pilot needs and nothing more. This site sets no cookies, runs no analytics and makes no third-party requests.
How a pilot runs
Scope it
A short conversation about your year groups, timetable, devices and what you want students to get out of it.
Configure it
Agree the format, length and activities, and what the school needs to approve first: devices, network, any accounts.
Run it, then review
Run the pilot with teachers setting the pace. Afterwards, look back together at what worked and what to change.
07 FAQ
07 / 09
Questions, answered straight.
Is this a live service yet?
No. Utora is pre-launch. There are no schools, students or results to report yet, and we would rather say so than imply otherwise. This site describes a proposed pilot and how we would like to work with the first school that wants to try it.
Which year levels is it for?
Years 7 to 12. A pilot can start with a single year group, and activities are pitched at that group’s experience.
Do students or teachers need Linux experience?
Students do not: the sample pilot starts at “Hello shell”. For teachers, how much support would help is part of the first conversation.
Does it connect to the Australian Curriculum?
Activities can connect to the Australian Curriculum: Digital Technologies. We do not claim accreditation or certified alignment. How an activity maps to your curriculum is agreed with each school.
What hardware or software would a pilot need?
It depends on the school. Browser-based and school-hardware options are both possible, and small boards such as the Raspberry Pi are one way to make the ideas physical. We work with school-approved devices and networks, and nothing is bought without your agreement.
What does it cost?
Pricing has not been set. For a first pilot, the conversation covers what is involved and what the school would need to provide. This site does not take payments or make promises about what is included.
How is student privacy handled?
Privacy-first. No student accounts with third parties are created without the school’s approval. This site loads nothing from other servers, and the pilot brief form on this page never sends anything anywhere.
Is Utora affiliated with the Linux Foundation?
No. Utora is independent. Linux® is the registered trademark of Linus Torvalds.
08 CONTACT
08 / 09
Plan a pilot.
Fill this in and your browser will write a plain .txt pilot brief. Read it, change it, then email it to hello@utora.dev.
Nothing is sent to any server. The brief is built and saved on your own device. Please do not enter student names or any personal information about students.
Preview — utora-pilot-brief.txt
UTORA PILOT BRIEF Expression of interest (not an agreement) School: Contact role: Classroom teacher Year group: Year 7 Starting point: A timetabled lesson Notes: (none) Send to: hello@utora.dev
This preview updates as you type. It stays on this page until you download it.