1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

Red Hat FedoraCore4 Up2date Guide

Michael Larabel

Published on 9 July 2005
Written by Michael Larabel
Page 1 of 2 - Comment On This Article

With almost a month since the release of FedoraCore4 (Stentz) there have been quite a few official updates from Red Hat to upgrade such packages as Open Office, Xorg, and the Linux 2.6.12 kernel. When FedoraCore3 came about, we presented a how-to article for creating your own Red Hat Up2date LAN repository. This repository allowed locally connected computers to retrieve updates significantly faster while offering greater package management. With FedoraCore4, however, came a revised version of Up2date. Although this updated copy is substantially improved upon previous versions, it still has its share of bugs. In this article, we’re sharing the revised steps for creating new update channels along with other basic configuration tips.

After doing a fresh install of FedoraCore4, the Up2date GNOME applet was already blinking bright with available updates. However, when clicking this it no longer just brings up the Red Hat Network Alert Notification Tool but also a subscription alert box. This new box simply lets the user know the subscription has yet to be activated. The options are presented to activate the subscription, activate it later, or to simply not activate it at all. This feature is for RHEL (Red Hat Enterprise Linux) and we had no troubles simply closing the window and then continuing our Up2date adventure. However, it then appeared that there’s a small bug preventing the number of updates from being properly reported in the GNOME Up2date applet.

Also presented when you run Up2date for the first time is the Red Hat Network Configuration. Alternatively, you can access this configuration panel at a later time by Desktop > System Settings > Red Hat Network Configuration or simply entering up2date-config into the Terminal. From this Up2date configuration panel, in the Retrieval / Installation tab we simply checked the box for "After installation, keep binary packages on disk". If the default package storage directory of /var/spool /up2date isn’t your preferred storage location, you can also change that at this time. Keeping the binary RPM packages on the disk after downloading them will allow you to easily distribute the RPMs over a LAN connection with other computers on the network, rather than having to download these packages individually every time from an Internet RPM repository. Alternatively, you can simply backup these packages to an external storage medium when reformatting your computer so you can quickly and easily update the machine.

The version of Up2date we’re using at the time of writing this article is 4.4.23-4 where as the version that shipped with FedoraCore3 was 4.3.47-5. The version can be attained by entering up2date --version into your Terminal.

Latest Linux Hardware Reviews
  1. CompuLab Intense-PC2: An Excellent, Fanless, Mini PC Powered By Intel's i7 Haswell
  2. From The Atom 330 To Haswell ULT: Intel Linux Performance Benchmarks
  3. AMD Radeon R9 285 Tonga Performance On Linux
  4. Apotop Wi-Copy
Latest Linux Articles
  1. AMD Moves Forward With Unified Linux Driver Strategy, New Kernel Driver
  2. MSI: Update Your BIOS From The Linux Desktop
  3. NVIDIA vs. AMD 2D Linux Drivers: Catalyst Is Getting Quite Good At 2D
  4. 15-Way GPU Comparison With Mesa 10.3 + Linux 3.17
Latest Linux News
  1. GParted 0.20 Improves Btrfs Support
  2. EXT4 In Linux 3.18 Has Clean-ups, Bug Fixes
  3. Emacs 24.4 Has Built-In Web Browser, Improved Multi-Monitor Support
  4. NVIDIA's NVPTX Support For GCC Is Close To Being Merged
  5. KDE's KWin On Wayland Begins Using Libinput
  6. Khronos Releases OpenVX 1.0 Specification
  7. Linux Kernel Working Towards GNU11/C11 Compatibility
  8. Ubuntu 15.04 Is Codenamed After A Monkey: Vivid Vervet
  9. Following GCC, Clang Looks To Default To C11
  10. Users/Developers Threatening Fork Of Debian GNU/Linux
Latest Forum Discussions
  1. Users/Developers Threatening Fork Of Debian GNU/Linux
  2. HOPE: The Ease Of Python With The Speed Of C++
  3. Bye bye BSD, Hello Linux: A Sys Admin's Story
  4. NVIDIA Presents Its Driver Plans To Support Mir/Wayland & KMS On Linux
  5. AMD Is Restructuring Again, Losing 7% Of Employees
  6. Open-Source AMD Fusion E-350 Support Takes A Dive
  7. Upgrade to Kaveri, very slow VDPAU performance
  8. ChromeOS Drops Support For EXT2/EXT3/EXT4 File-Systems