Getting Started With Ubuntu 5.10 Breezy Badger
Ubuntu 5.10, released in October 2005, gave Linux newcomers a polished route into a free desktop operating system. Its codename, Breezy Badger, suggested a friendly distribution, and the software generally lived up to that promise. Installation was simpler than it had been in earlier Linux releases, hardware detection had improved, and the GNOME desktop presented familiar menus, folders, and preferences.
For users accustomed to Windows XP, the change involved more than replacing one desktop with another. Ubuntu introduced a package-based way of installing applications, a different approach to system administration, and a strong preference for open-source software. Once those ideas became familiar, routine tasks such as browsing, writing documents, managing photographs, and listening to music were straightforward.
Australian users also had practical matters to consider. Broadband services in Sydney, Melbourne, Brisbane, Perth, and regional towns often came with monthly download limits, while dial-up remained common outside metropolitan areas. An installation CD or a local Ubuntu mirror could therefore be much more useful than downloading hundreds of megabytes from an overseas server.
| Area | Ubuntu 5.10 Breezy Badger | Windows XP |
|---|---|---|
| Desktop | GNOME with Applications, Places, and System menus | Start menu, taskbar, and Control Panel |
| Software installation | Synaptic and APT repositories | Downloaded installers and retail media |
| Cost | Free to download, copy, and install | Usually supplied with a new computer or purchased licence |
| Hardware support | Strong for common devices, variable for wireless and graphics | Broad commercial driver support |
| Security model | Ordinary work under a standard user account with administrative authentication | Administrator use was common on home computers |
| Office software | OpenOffice.org 2.0 and basic utilities | Microsoft Office usually installed separately |
What Breezy Brought To The Desktop
Breezy Badger was built around GNOME 2.12, a desktop environment that favoured clear menus and modest visual effects. The top panel held the Applications, Places, and System menus, while the lower panel displayed open windows and workspaces. This arrangement made the system approachable for someone moving from Windows, although the terminology was different enough to require a little adjustment.
The release included Firefox for web browsing, Evolution for email and personal information management, GIMP for image editing, and OpenOffice.org 2.0 for documents, spreadsheets, presentations, and database work. Totem handled multimedia playback, while Nautilus managed files and folders. These applications formed a capable everyday toolkit without requiring a trip to a computer shop.
Ubuntu’s greatest distinction was the way it treated software as part of a maintained collection. Rather than hunting through magazine CDs or unfamiliar download sites, users could search a repository and let the package manager handle installation. The available selection was shaped by Ubuntu’s free-software policy, so some commercial codecs, games, fonts, and device drivers required separate attention.
Check The Computer Before Installing
A smooth installation began with a short hardware inventory. Breezy generally worked well with standard desktop PCs using Intel or compatible processors, IDE hard drives, common Ethernet cards, and ordinary keyboards and mice. Wireless chipsets, winmodems, unusual scanners, and very recent graphics cards were less predictable. Writing down the computer’s memory, graphics adapter, network hardware, and monitor resolution made later troubleshooting easier.
A computer with 256 MB of RAM could run Breezy, although 512 MB or more made GNOME and OpenOffice.org feel considerably more comfortable. A blank installation needed several gigabytes of hard-drive space, with additional room for personal files and software packages. Anyone retaining Windows XP should back up important documents and defragment the Windows partition before resizing it.
The installation media was usually an ISO image written to a CD, or a mailed Ubuntu disc requested through the ShipIt service. In Australia, a CD could avoid exhausting a 200 MB or 500 MB monthly broadband allowance. Users with a stable broadband connection could also choose an Australian mirror when downloading updates, reducing international transfer time and making better use of local network capacity.
Personal data should be copied to an external hard drive, another computer, or recordable discs before partitioning. Email archives, photographs, browser bookmarks, tax records, and documents deserve particular care. The Australian Privacy Act 1988 placed obligations on organisations handling personal information, but home users still had to protect their own files; an operating-system installation was a poor time to discover that the only copy of a family archive had vanished.
Installing Breezy Badger
Booting from the Ubuntu CD started a live desktop session. This allowed users to inspect the display, keyboard, sound, and network connection before committing to the installation. The live environment was slower than an installed system because it read much of its software from the optical disc, but it offered a valuable compatibility check.
The installer guided the user through language, keyboard layout, time zone, partitioning, user details, and boot-loader configuration. Australian users could select an Australian English locale and a nearby city such as Sydney, Melbourne, Adelaide, Brisbane, Perth, or Darwin for regional settings. The time-zone choice affected the system clock and daylight-saving behaviour, so it was worth selecting carefully rather than accepting an unrelated default.
Partitioning required the greatest concentration. A computer dedicated to Ubuntu could use the entire disk, while a dual-boot computer needed free space for both systems. The installer could resize an existing Windows partition, but resizing is a serious operation rather than a casual preference. A separate home partition was useful for future reinstallations, although beginners could reasonably accept the guided layout.
Ubuntu created a user account for ordinary work and asked for a password when administrative changes were needed. This was a healthier default than spending every session logged in as a system administrator. The installer then copied the base system, configured the boot loader, and asked for a restart. Removing the CD when prompted allowed the newly installed desktop to start from the hard drive.
The First Session And Basic Settings
The first login presented a clean GNOME desktop with a small number of icons and panels. The System menu contained preferences and administration tools, while Places offered access to the home folder, computer, removable media, and network locations. Double-clicking a hard drive or USB device opened it in Nautilus, and files could be copied using familiar drag-and-drop actions.
The Preferences tools covered display resolution, keyboard shortcuts, mouse behaviour, screensavers, themes, and sound. Display settings deserved early attention because a poor resolution could make the desktop uncomfortable. A common CRT monitor might work at 1024×768 or 1280×1024, while an LCD panel generally looked best at its native resolution.
Network configuration depended on the connection. Ethernet through an ADSL modem or router was usually simple, with DHCP assigning an address automatically. Some Australian broadband services required a PPPoE username and password, while older users might still rely on dial-up hardware that Linux did not support well. BigPond and other providers also used service-specific connection arrangements, so keeping the account details and modem instructions nearby was sensible.
The home folder was the centre of personal work. Documents, music, pictures, and downloaded files could be organised into clear directories rather than left scattered across the desktop. A removable USB drive could provide a basic backup routine, though users should eject it properly before unplugging it. This mattered in offices and households where a shared computer held employment records, invoices, or school work.
Software, Updates, And Everyday Work
Synaptic Package Manager was the main graphical tool for finding software. It searched repository descriptions, displayed package dependencies, and marked applications for installation before applying all changes together. The command-line equivalent, APT, used commands such as sudo apt-get update and sudo apt-get install gimp. Synaptic was easier for beginners, while APT was efficient for experienced administrators.
The first update should be performed after the network connection was working. Ubuntu releases received security fixes and bug corrections through the update manager, and Breezy users benefited from applying those updates before adding optional software. A small warning is important here: the original Breezy repositories are historical, so a modern machine should not be pointed at them casually. This advice belongs to archival use, old-hardware experiments, and virtual machines rather than current production systems.
OpenOffice.org could open many Microsoft Office files, although complex formatting and macros did not always transfer perfectly. GIMP offered powerful image-editing functions, but its interface was more technical than a basic paint program. Firefox handled ordinary web browsing, though the web itself has changed dramatically since 2005. Multimedia playback could require restricted codecs, and users should consider the licensing rules applying to their location before obtaining them.
For Australian households, download planning remained part of computer maintenance. Large update batches were best scheduled within an ISP’s allowance, and an Australian mirror could be selected where available. In a workplace, the administrator might keep a local package cache or shared repository so several computers did not repeatedly download the same files across a metered connection.
Handling Drivers And Common Problems
The most frequent Breezy difficulties involved hardware that depended on proprietary firmware or closed drivers. NVIDIA and ATI graphics cards could require vendor-specific packages for accelerated 3D, while some Broadcom wireless adapters needed extra configuration. A wired Ethernet connection was extremely useful because it allowed documentation and packages to be obtained while wireless support was being repaired.
Printers were often easier than scanners, especially when the model used a common HP, Epson, or Canon protocol. The printer configuration tool could discover network or USB printers, but exact support varied by model. Winmodems were a particular problem because much of their processing was performed in software written for Windows. Replacing such a modem with an external Ethernet or serial unit was often less frustrating than searching for an incomplete driver.
If the system failed to start graphically, the text console offered a route back into administration. Pressing Ctrl+Alt+F1 opened a virtual terminal where a user could log in and inspect configuration files or restart services. Beginners should record error messages accurately rather than repeatedly reinstalling the operating system. Ubuntu forums, documentation, and local Linux user groups were valuable sources of practical help, including communities in Melbourne, Sydney, Canberra, and Brisbane.
Security habits were straightforward: use a strong password, install updates, avoid running unknown programs as administrator, and keep backups. A broadband router provided useful network separation, but it was not a replacement for sensible account security. Australian businesses also had to consider obligations under the Privacy Act and related workplace policies when storing customer or employee information on a newly configured Linux computer.